Add simple Create Project Structure launcher action #679

BigRoy · 2024-06-20T18:25:07Z

Changelog Description

Add simple Create Project Structure launcher action.

Which creates the folder structure as defined in project settings: ayon+settings://core/project_folder_structure

Additional info

It currently only shows when you're in a project in the launcher but have NO folder or task selected to avoid clutter in launcher.

The label unfortunately is a bit too long to be nicely displayed by default, see screenshot. Any ideas for better icon and shorter label that doesn't get cut off?

This feature request came up a few times:

Ynput Community Forum: How set up custom folder creation when using the launcher
Ynput Community Forum: Default Project Hierarchy mentions the setting but seemed to describe a different feature.
Discord

Testing notes:

Update core addon
Run the launcher action when you enter a project.
Folders should now be generated as per settings.

client/ayon_core/plugins/actions/create_project_folder_structure.py

…re.py Co-authored-by: Jakub Trllo <[email protected]>

alainxi · 2024-06-21T08:29:57Z

Any ideas for better icon and shorter label that doesn't get cut off?

Your icon choice is already very good.

Shorter labels : The "disk" concept is important, to avoid confusion with the project's folder structure in database. Ideas :

Add disk proj struct
Add proj struct on disk
Create Project Structure (the current label, but with a different icon : mdi.harddisk-plus or mdi.harddisk )

…der_structure

LiborBatek · 2024-06-28T09:07:18Z

I can think of these names:

Create Dir
Create PRJ
Project Dir

BigRoy · 2024-06-28T09:15:16Z

I think maybe it's also worth discussing whether it might be nice to shrink the font sizes just a tad there to ensure there's less cut off. I often see it on other applications as well - which may fix the chosen names here as well?

@iLLiCiTiT what do you think?

…der_structure

LiborBatek

Took me a while to realize its not pre-creating the folders from the Project browser/editor but by Ayon Core definition (as mentioned in testing steps:) but after that small confusion all working fine...LGTM

they obviously been matching

LiborBatek · 2024-06-28T09:26:13Z

@BigRoy btw what happens if user trigger Create Project... if those already existing?? I hope it will just skip the creation :) ?

BigRoy · 2024-06-28T09:53:27Z

@BigRoy btw what happens if user trigger Create Project... if those already existing?? I hope it will just skip the creation :) ?

Not sure - since I didn't implement that code myself. But I suspect it would just generate the folders on disk that currently do not exist yet - so if you've adjusted your studio settings to have new folders in the template - then those get added.

Are you afraid to click the button? If so, what is making you scared and what could we do to make it feel less scary? A tooltip? A pop-up before the creation? (Like a confirmation? Which might make it feel more scary even?)

LiborBatek · 2024-06-29T06:56:43Z

@BigRoy btw what happens if user trigger Create Project... if those already existing?? I hope it will just skip the creation :) ?

Not sure - since I didn't implement that code myself. But I suspect it would just generate the folders on disk that currently do not exist yet - so if you've adjusted your studio settings to have new folders in the template - then those get added.

Are you afraid to click the button? If so, what is making you scared and what could we do to make it feel less scary? A tooltip? A pop-up before the creation? (Like a confirmation? Which might make it feel more scary even?)

yeah, some popup would do! informing user whats gonna happen...

LichiMan · 2024-07-09T08:45:06Z

Thanks a lot for this @BigRoy , this is one of the things I was missing from our current pipeline while testing Ayon.

In our current pipeline we always have a folder called 00_MATERIALS where we save a lot of stuff in different subfolders like audio, references (with more subfolders), logos, client_material...

The production team is who usually save there all the material and they need to have the folder structure created to start copying files.

Now my question. As far as I know you can setup the folder structure in ayon+settings://core/project_folder_structure but there's no way to create these folders automatically before this PR, but if you setup a folder structure in that Ayon setting it's because you want it. So, shouldn't this folder structure be created automatically when you create a new project with that Bundle instead of have to go the the Launcher and click on this icon?

Of course, this is just for that folder structure setting and not for the whole folders/tasks you define inside the Project Settings.

BigRoy · 2024-07-09T12:23:14Z

Thanks a lot for this @BigRoy , this is one of the things I was missing from our current pipeline while testing Ayon.

In our current pipeline we always have a folder called 00_MATERIALS where we save a lot of stuff in different subfolders like audio, references (with more subfolders), logos, client_material...

The production team is who usually save there all the material and they need to have the folder structure created to start copying files.

Now my question. As far as I know you can setup the folder structure in ayon+settings://core/project_folder_structure but there's no way to create these folders automatically before this PR, but if you setup a folder structure in that Ayon setting it's because you want it. So, shouldn't this folder structure be created automatically when you create a new project with that Bundle instead of have to go the the Launcher and click on this icon?

Of course, this is just for that folder structure setting and not for the whole folders/tasks you define inside the Project Settings.

It's a good question - but admittedly with site sync a project may be accessible from multiple locations and thus may have already been existing before that 'creation'. Also the project creation may happen in any variety of ways, yes currently most likely is the ayon-frontend triggering this but it may even be automated by the API or e.g. occur due to syncing from kitsu, ftrack or shotgrid/flow (which you may not want to automatically flood a local directory with project folders or not). Also, what if a producer just happens to create a project using the web frontend without access to the physical storage | what would create the project folder and files where?

Anyway, nothing is holding anyone from triggering e.g. this logic anytime the AYON Tray Launcher starts up or whatever - I'd just say that from my perspective I don't think I'd recommend that.

Do note that potentially soon using Web Actions from the front-end it may be possible to trigger an action like this from the web front-end, not requiring to do it via the Tray Launcher UI.

Additionally, having it accessible as a callable action does allow you to update the template in settings, and re-run it again if you happened to have changed the template.

LiborBatek · 2024-07-10T07:55:56Z

I have done one more test run to see what happens if those folders are already present and filled with some content...

The good is, even when re-triggering this Create Proj action nothing happens aka no deleting or similar destructive action.

However still missing that popup info message what are you about to do.... @BigRoy any chance you incorporate it? :)

LichiMan · 2024-07-11T08:11:37Z

It's a good question - but admittedly with site sync a project may be accessible from multiple locations and thus may have already been existing before that 'creation'. Also the project creation may happen in any variety of ways, yes currently most likely is the ayon-frontend triggering this but it may even be automated by the API or e.g. occur due to syncing from kitsu, ftrack or shotgrid/flow (which you may not want to automatically flood a local directory with project folders or not). Also, what if a producer just happens to create a project using the web frontend without access to the physical storage | what would create the project folder and files where?

Anyway, nothing is holding anyone from triggering e.g. this logic anytime the AYON Tray Launcher starts up or whatever - I'd just say that from my perspective I don't think I'd recommend that.

Do note that potentially soon using Web Actions from the front-end it may be possible to trigger an action like this from the web front-end, not requiring to do it via the Tray Launcher UI.

Additionally, having it accessible as a callable action does allow you to update the template in settings, and re-run it again if you happened to have changed the template.

Yes, it makes sense.

I'm still don't know how Web Actions will work but it sounds like a nice way for doing this, better than the Tray Launcher as everything stay in the web front-end, IMHO.

…der_structure

BigRoy · 2024-07-29T23:20:30Z

@iLLiCiTiT any preference where to go from here aside of the icon and label cosmetics?

iLLiCiTiT · 2024-08-02T09:07:27Z

any preference where to go from here aside of the icon and label cosmetics?

Not from my point of view. Code is ok.

The question is, if it is "pipeline ok". Not sure if any artist should be able to run the action?

krishnaavril · 2024-08-05T04:30:37Z

The question is, if it is "pipeline ok". Not sure if any artist should be able to run the action?

Or should the option be like, select the folders/shots on the left pane and choose the option!?
even creating all the folders by artists is also okay, there is no harm I believe, anyway production already carefully adds the shots in ayon web. We are waiting for this option, everytime when we wanted to paste something inside shots its manual, I think this helps a lot

BigRoy · 2024-09-02T12:39:08Z

Just commenting that I'm not working on this currently - so it may be stale until there's more details on how to best proceed with this? I believe Web Actions might take precedence on this and 'replace' it? But maybe @LiborBatek 's comment here is still relevant if there is a time and place for having this also directly in launcher.

@iLLiCiTiT so FYI - I'll hold of changes to this until there's a clear route of action.

…der_structure

MustafaJafar · 2024-09-09T08:50:52Z

For the first glance when I read the PR's description (sorry if it was mentioned before) I had these thoughts:

What will happen if the ayon+settings://core/project_folder_structure doesn't match my actual project structure in the project editor ?
What should be the source of truth for the folder creation ?

alainxi · 2024-09-09T09:25:43Z

For the first glance when I read the PR's description (sorry if it was mentioned before) I had these thoughts:

What will happen if the ayon+settings://core/project_folder_structure doesn't match my actual project structure in the project editor ?

What should be the source of truth for the folder creation ?

I think "Create Project Structure" (on disk, for assets that are not handled by Ayon) should follow "ayon+settings://core/project_folder_structure".

It's really different from the Logical structure (in Editor), which is only for Ayon managed stuff.

Look at Jakub's message on that matter (a year ago) :

This particular settings is at wrong place even in OpenPype...

The same settings are used for 2 features:
1 : Create default folder structure (on disk)
2 : Create default project hierarchy (in project manager)
Which usually cause many troubles..

Found here :
https://discord.com/channels/517362899170230292/890894521817260052/1147160515576082552

BigRoy · 2024-09-09T11:05:35Z

For the first glance when I read the PR's description (sorry if it was mentioned before) I had these thoughts:
* What will happen if the `ayon+settings://core/project_folder_structure` doesn't match my actual project structure in the project editor ?

* What should be the source of truth for the folder creation ?

AFAIK this is not at all about creating folders for "folder" entities or tasks, etc. It's to create generic folders for your project that you may want to populate for "a project". Like e.g. you may - out of the pipeline - have a static "resources" folder, or a static "documents" folder where producers maybe put in some stuff. Etc.

So it's more of a "Please just create me some standard folders for the project" that are not related to actual assets or shots.

…der_structure

MustafaJafar

This works on my side.

But, there are few things to keep in mind:

I can only find it if I've nothing selected in the launcher (which happens when selecting a project) but once I select a folder, I won't be able to unselect it. so I have to return and reselect my project.
I wish if I can see the folders created reflected in the launcher view. and be able to use button Explore here.

(irrelevant to this PR) when using the button Explore here on intermediate folders, it keep telling me Folder does not exist yet.

*** WRN: >>> { ActionsModel }: [  Action trigger FAILED.  ] 
==========================
Folder does not exist yet.
==========================
Traceback (most recent call last):
  File "E:\Ynput\ayon-core\client\ayon_core\tools\launcher\models\actions.py", line 405, in trigger_action
    action.process(selection)
  File "E:\Ynput\ayon-core\client\ayon_core\plugins\actions\open_file_explorer.py", line 26, in process
    path = self._get_workdir(selection)
  File "E:\Ynput\ayon-core\client\ayon_core\plugins\actions\open_file_explorer.py", line 94, in _get_workdir
    raise AssertionERROR("Folder does not exist yet.")
AssertionERROR: Folder does not exist yet.

Anyways, I think this feature/enhancement may come lead to more suggestions/requests/complaints like mine above.

LiborBatek · 2024-09-12T07:52:55Z

@krishnaavril this action is not intended as a substitution for creation of AYON driven project folders (assets, shots etc) but for additional folders predefined in the ayon-core settings ayon+settings://core/project_folder_structure (for resources like plates, footage, offline and other items production might need and to save those in a standard places)

@BigRoy as the confusion already happening I think we definetely should use different naming than Create Project Folders but refer more to Resources folders or similar.

alainxi · 2024-09-12T08:09:00Z

@LiborBatek

I agree we should use different naming than Create Project Folders, to avoid confusion.
For that, the "disk" concept is important.
Here are alternatives (very short ones, to not clutter GUI) :

Add disk proj struct
Add proj struct on disk

…der_structure

MustafaJafar · 2024-10-02T08:20:48Z

@BigRoy @iLLiCiTiT @dee-ynput should we convert this to draft since it may be replaced by a web action?

BigRoy · 2024-10-04T08:27:47Z

@dee-ynput could you answer the remaining questions:

What should be the label on the action? It must be short because as can be seen from the screenshot - it gets cut off. These have come up:

    Add disk proj struct
    Add proj struct on disk
    Create Project Structure (will be cut off after "Project...")
    Create Project Folders (will be cut off after "Project...")

What's a sensible icon to use. I think you can pick one from: https://fontawesome.com/v4/icons/
Should it pop up a confirmation dialog (maybe even explaining which folders would get created; it could even report if they already exist too) to avoid accidental clicks?
Should it appear for ALL users? Or just certain roles? (If so, which?)
Should it have a setting to enable/disable the action completely?

dee-ynput · 2024-10-04T09:00:32Z

Thanks for the summary @BigRoy!

What should be the label on the action? It must be short because as can be seen from the screenshot - it gets cut off. These have come up:

Let's match the setting name "Project folder structure", so: Create Project Folders.
The name being cut off indeed sucks, but that's something we'll fix at UI level (this limitation is a bummer for many other situations)

What's a sensible icon to use. I think you can pick one from: fontawesome.com/v4/icons

The sitemap icon kinda works. I could consider a simple folder icon or the hdd icon...

Should it pop up a confirmation dialog (maybe even explaining which folders would get created; it could even report if they already exist too) to avoid accidental clicks?

Let's add this later if requested 👍
(I do like it)

Should it appear for ALL users? Or just certain roles? (If so, which?)

I need to check with CS team, but worst case would be to have a setting to state if it's managers only or for artists too.

Should it have a setting to enable/disable the action completely?

Having the setting value empty should disable it.
It must be stated in the settings inline help / tooltip.

ynbot · 2024-10-04T09:02:29Z

Task linked: AY-5076 Ayon: Folder creation

…der_structure

dee-ynput · 2024-10-04T09:06:46Z

@BigRoy
After reviewing the CS request:

Should it appear for ALL users? Or just certain roles? (If so, which?)

Let's do it for all users.
The restriction will be implemented if/when we move this to a proper web action 👍

BigRoy · 2024-10-04T09:18:18Z

Let's match the setting name "Project folder structure", so: Create Project Folders.
The name being cut off indeed sucks, but that's something we'll fix at UI level (this limitation is a bummer for many other situations)

Done.

Unfortunately reads like this:

Having the setting value empty should disable it.
It must be stated in the settings inline help / tooltip.

Done.

The sitemap icon kinda works. I could consider a simple folder icon or the hdd icon...

I'll keep sitemap for now.

MustafaJafar · 2024-10-04T09:27:06Z

server/settings/main.py

        title="Project folder structure",
+        description=(
+            "Defines project folders to create on 'Create project folders'."
+            " When empty, the action will be hidden from users in the"
+            " launcher because there is nothing to create."
+        ),


I understand it will create the project structure in the setting.
but, could we be clear that it is an additional structure that is not necessarily related to the project structure in the project editor?

Do you mean like adding "This does not create folder and task entities, but creates project folders on disk unrelated to any entity"? It seems quite long and verbose and still unclear too. Any ideas on how to explain it with less words and more correct?

BTW it is still used for actions that actually do use this setting to create project folder structure, instead of folder structure on disk, e.g. in ftrack. That is in fact original purpose of these settings.

Yes - so you're saying it will not do anything there when empty but it will still be visible/shown as action (it does not get hidden there). Correct?

@dee-ynput thoughts? Is the tooltip just confusing then, or? Or we should start hiding the action there too in the future?

Yes - so you're saying it will not do anything there when empty but it will still be visible/shown as action (it does not get hidden there). Correct?

No, I'm saying that this setting is used for 2 features:

Create folder structure in project.

Create folder structure on disk.

So this: 5065e0e

No idea how it formats it like this haha 🤦‍♂️

That's why the "disk" word is important for the button name.
With "Create Project Folders", people will think it creates folder entities, and they will be surprised to discover it created disk structure.

@dee-ynput ? :)

Do you mean like adding "This does not create folder and task entities, but creates project folders on disk unrelated to any entity"? It seems quite long and verbose and still unclear too. Any ideas on how to explain it with less words and more correct?

I mean something like this.
imo, we may not add all of the that to the tool tip in favor of adding them to the documentation.

Defines project folders to be created when selecting 'Create project folders'. - If you use the exact same structure in the project editor, it will create all the folders. - If you use a different structure, it will add them as additional directories. - If the setting is empty, the 'Create project directories' action will be hidden from users in the launcher. This setting is also used in ftrack addon to create both the folders on disk and the ftrack entities.

If you use the exact same structure in the project editor, it will create all the folders.

If you use a different structure, it will add them as additional directories.

I personally don't understand these? Same structure to what? :)

Anyway, make a decision and I'll be happy to adjust accordingly - so we don't keep this lingering much longer.

I think the new tool tip is much better.

I personally don't understand these? Same structure to what? :)

I was just trying to say that I can use the same structure that I'm using in my project editor like this one
#679 (review)
where I want to create an empty folders for my assets.

MustafaJafar

I think I've found a bug.
Can we use lists in ayon+settings://core/project_folder_structure setting?

I made this

{
    "__project_root__": {
        "Assets": {
            "Characters": {
                "NewRobo": {
                    "work": [
                        "cfx",
                        "concept",
                        "modeling",
                        "walkcycle"
                    ]
                },
                "RoboPoro": {
                    "work": [
                        "cfx",
                        "concept",
                        "modeling",
                        "walkcycle"
                    ]
                },
                "RoboMad": {
                    "work": [
                        "cfx",
                        "concept",
                        "modeling",
                        "walkcycle"
                    ]
                }
            }
        }
    }
}

and I got this error:

*** WRN: >>> { ActionsModel }: [  Action trigger FAILED.  ] 
==============================
'list' object has no attribute 'items'
==============================
Traceback (most recent call last):
  File "E:\Ynput\ayon-core\client\ayon_core\tools\launcher\models\actions.py", line 405, in trigger_action
    action.process(selection)
  File "E:\Ynput\ayon-core\client\ayon_core\plugins\actions\create_project_folders.py", line 29, in process
    project_folders.create_project_folders(selection.project_name)
  File "E:\Ynput\ayon-core\client\ayon_core\pipeline\project_folders.py", line 66, in create_project_folders
    basic_paths = get_project_basic_paths(project_name)
  File "E:\Ynput\ayon-core\client\ayon_core\pipeline\project_folders.py", line 112, in get_project_basic_paths
    return _list_path_items(folder_structure)
  File "E:\Ynput\ayon-core\client\ayon_core\pipeline\project_folders.py", line 90, in _list_path_items
    paths = _list_path_items(value)
  File "E:\Ynput\ayon-core\client\ayon_core\pipeline\project_folders.py", line 90, in _list_path_items
    paths = _list_path_items(value)
  File "E:\Ynput\ayon-core\client\ayon_core\pipeline\project_folders.py", line 90, in _list_path_items
    paths = _list_path_items(value)
  [ Previous line repeated 2 more times ]
  File "E:\Ynput\ayon-core\client\ayon_core\pipeline\project_folders.py", line 85, in _list_path_items
    for key, value in folder_structure.items():
AttributeERROR: 'list' object has no attribute 'items'

alainxi

I have tested with this, which works perfectly :

{
    "{root[work]}/{project[name]}": {
        "DELIVERIES": {
            "ASSETS_FOR_CLIENTS": {},
            "ICON": {
                "OLD": {}
            },
            "MOF_AND_PUB": {
                "OLD": {}
            }        },
        "PREPROD": {
            "ASSETS_FROM_ARCHIVE": {
                "NOM_DU_PROJET": {}
            },
            "ASSETS_FROM_CLIENT": {
                "GUIDELINES_AND_STORYBOARD": {
                    "OLD": {}
                },
                "VIDEOS_AND_SOUNDS": {
                    "OLD": {}
                }
            },
            "MOCKUP_AND_STORYBOARD": {
                "EXPORT": {
                    "OLD": {}
                },
                "WIP": {}
            }
        }
    }
}

I used {root[work]}/{project[name]} instead of __project_root__ , because the later is marked as legacy in the code (and it tries to create the same folder tree on all Anatomy roots, a behaviour that we don't want).

BigRoy · 2024-10-07T14:19:47Z

I used {root[work]}/{project[name]} instead of __project_root__ , because the later is marked as legacy in the code (and it tries to create the same folder tree on all Anatomy roots, a behaviour that we don't want).

Separate from this PR - should we update the default settings @m-u-r-p-h-y @LiborBatek to use {root[work]}/{project[name]} instead? Or?

Add simple Create Project Structure launcher action

0a207ad

ynbot added size/XS type: enhancement Improvement of existing functionality or minor addition labels Jun 20, 2024

BigRoy added 2 commits June 20, 2024 20:25

Cosmetics

905241f

Cosmetics

fbd2735

BigRoy requested review from iLLiCiTiT, LiborBatek, dee-ynput and m-u-r-p-h-y June 20, 2024 18:27

iLLiCiTiT reviewed Jun 21, 2024

View reviewed changes

client/ayon_core/plugins/actions/create_project_folder_structure.py Outdated Show resolved Hide resolved

Update client/ayon_core/plugins/actions/create_project_folder_structu…

18f750f

…re.py Co-authored-by: Jakub Trllo <[email protected]>

BigRoy requested a review from iLLiCiTiT June 21, 2024 07:39

Merge branch 'develop' into enhancement/launcher_action_to_create_fol…

29205b7

…der_structure

Merge branch 'develop' into enhancement/launcher_action_to_create_fol…

1747af6

…der_structure

LiborBatek approved these changes Jun 28, 2024

View reviewed changes

Merge branch 'develop' into enhancement/launcher_action_to_create_fol…

338e6b3

…der_structure

BigRoy self-assigned this Jul 29, 2024

Merge branch 'develop' into enhancement/launcher_action_to_create_fol…

240b2b9

…der_structure

MustafaJafar self-requested a review September 9, 2024 08:37

Merge branch 'develop' into enhancement/launcher_action_to_create_fol…

23f25a0

…der_structure

MustafaJafar approved these changes Sep 10, 2024

View reviewed changes

Merge branch 'develop' into enhancement/launcher_action_to_create_fol…

6b15de5

…der_structure

Merge branch 'develop' into enhancement/launcher_action_to_create_fol…

da28af5

…der_structure

BigRoy added 3 commits October 4, 2024 11:08

Rename action to Create Project Folders

56fb5c4

Hide action if setting is empty

8383fde

Add description to setting

5aa7e9c

BigRoy requested a review from LiborBatek October 4, 2024 09:26

MustafaJafar reviewed Oct 4, 2024

View reviewed changes

Explicit description to describe diff between ftrack and launcher

5065e0e

MustafaJafar requested a review from alainxi October 4, 2024 16:42

MustafaJafar reviewed Oct 4, 2024

View reviewed changes

alainxi approved these changes Oct 7, 2024

View reviewed changes

robertokker mentioned this pull request Oct 9, 2024

AY-5076_Ayon: Folder creation #914

Open

Add simple Create Project Structure launcher action #679

Are you sure you want to change the base?

Add simple Create Project Structure launcher action #679

Conversation

BigRoy commented Jun 20, 2024 • edited by dee-ynput Loading

Changelog Description

Additional info

Testing notes:

alainxi commented Jun 21, 2024 • edited Loading

LiborBatek commented Jun 28, 2024

BigRoy commented Jun 28, 2024

LiborBatek left a comment

Choose a reason for hiding this comment

LiborBatek commented Jun 28, 2024

BigRoy commented Jun 28, 2024 • edited Loading

LiborBatek commented Jun 29, 2024

LichiMan commented Jul 9, 2024

BigRoy commented Jul 9, 2024

LiborBatek commented Jul 10, 2024

LichiMan commented Jul 11, 2024

BigRoy commented Jul 29, 2024

iLLiCiTiT commented Aug 2, 2024 • edited Loading

krishnaavril commented Aug 5, 2024

BigRoy commented Sep 2, 2024

MustafaJafar commented Sep 9, 2024 • edited Loading

alainxi commented Sep 9, 2024 • edited Loading

BigRoy commented Sep 9, 2024

MustafaJafar left a comment

Choose a reason for hiding this comment

LiborBatek commented Sep 12, 2024

alainxi commented Sep 12, 2024

MustafaJafar commented Oct 2, 2024 • edited Loading

BigRoy commented Oct 4, 2024 • edited Loading

dee-ynput commented Oct 4, 2024 • edited Loading

ynbot commented Oct 4, 2024

dee-ynput commented Oct 4, 2024

BigRoy commented Oct 4, 2024

MustafaJafar Oct 4, 2024

Choose a reason for hiding this comment

BigRoy Oct 4, 2024

Choose a reason for hiding this comment

iLLiCiTiT Oct 4, 2024 • edited Loading

Choose a reason for hiding this comment

BigRoy Oct 4, 2024 • edited Loading

Choose a reason for hiding this comment

iLLiCiTiT Oct 4, 2024

Choose a reason for hiding this comment

BigRoy Oct 4, 2024

Choose a reason for hiding this comment

BigRoy Oct 4, 2024

Choose a reason for hiding this comment

MustafaJafar Oct 4, 2024

Choose a reason for hiding this comment

BigRoy Oct 4, 2024

Choose a reason for hiding this comment

MustafaJafar Oct 4, 2024 • edited Loading

Choose a reason for hiding this comment

MustafaJafar left a comment

Choose a reason for hiding this comment

alainxi left a comment • edited Loading

Choose a reason for hiding this comment

BigRoy commented Oct 7, 2024

BigRoy commented Jun 20, 2024 •

edited by dee-ynput

Loading

alainxi commented Jun 21, 2024 •

edited

Loading

BigRoy commented Jun 28, 2024 •

edited

Loading

iLLiCiTiT commented Aug 2, 2024 •

edited

Loading

MustafaJafar commented Sep 9, 2024 •

edited

Loading

alainxi commented Sep 9, 2024 •

edited

Loading

MustafaJafar commented Oct 2, 2024 •

edited

Loading

BigRoy commented Oct 4, 2024 •

edited

Loading

dee-ynput commented Oct 4, 2024 •

edited

Loading

iLLiCiTiT Oct 4, 2024 •

edited

Loading

BigRoy Oct 4, 2024 •

edited

Loading

MustafaJafar Oct 4, 2024 •

edited

Loading

alainxi left a comment •

edited

Loading