Trying my luck whether this is a somewhat minor change eheh... or maybe I can cry "it's an oversight!" lol, anyway:
We can change Event Sheet tab colours at the top of C3, but not the tab colour for script files (or any "files", e.g. plain text files for notes).
Could it be possible to allow updating the colours of script tabs?
Tab colours help a huge amount - Where I've used Event Sheets for years, I gained muscle memory of "Green is 'Gameplay' sheet", "Black is 'Debug' sheet", etc. Even if tabs reordered, it is easy to recall the colour and spot it immediately. Even if reusing a similar "Green" tab, its only 2 greens to look for, they stand out clearly. Lesser-used event sheets remain grey.
I understand if no. I became hopeful it could be a minor addition as I figured an "open script file in C3" has some form of UI data to store for its position in the tab list at the top of C3.
EDIT: I only now discovered collapsing code in scripts... this is GREAT, but sadly, once you save your proj, close, reopen - all collapsed code in scripts are no longer collapsed....
... could this be something C3 could track when saving/closing proj/reopening?
I apologise, suddenly 2 "minor suggestions" that probably are huge/risky (especially since it involves project save data). Tab Colours are certainly the most desired.
.
.
.
Below is miscellaneous stuff I wrote but may be of use
It's been great working with scripts. I have focused hard on learning JS in past months (Slow learner, took me YEARS to comprehend Ashley's Learn JavaScript in Construct tutorials, along with... *gasp*... using AI to answer my excessive noob questions). I have essentially transformed huge amounts of my project into scripts, and it's honestly been extremely fun! Took me a while to comprehend the best setup for "imports/exports" but finally understood, and thus split my scripts even more.
Navigating Tabs, and navigation in long scripts, have been the only things slowing my workflow down. I try to learn as much as I can to improve my workflow, and discover new things all the time within scripting - E.G. Features like "CTRL+Click on a property". Even ol' familiar features are extremely useful when scripting, like C3's "Find" bar.
Tab Colours
My workaround is using dummy event sheets named "=UI=" or "=Input=", set the tab colour, place at left of script tab. Sadly it's a bit wonky to use - tabs jump around when resizing left/right C3 panes, and clicking on tabs will slightly alter tab widths and sometimes readjusts tabs to the next line - this makes my eyes dance around from right to left, not the most optimal but better than nothing.
I even tried making dummy sheets where the tab is pure black, so I could use them as "spacers" or to try and keep tabs on the correct lines. This was painful and I stopped doing this!
Collapsing Script Code
I thought I solved my woe of "navigating long scripts" by splitting into separate script files, but I am over-doing this quite a lot (e.g. 4 scripts for Mouse-related things, simply because it was a nightmare to scroll around when it was just 1 or 2 scripts), but to be able to collapse a long function that I rarely need to look at, is immensely useful - Just wish it remembered it in C3!
I have a feeling this is more tricky than a "minor addition" since it's interfacing with Monaco, which might be a pain.
Could Monaco report back to C3 when the user collapses/expands something in the specific script it was done within, or if another command like "collapse all/expand all" is used, or when opening a project, can Monaco be commanded to auto-collapse scripts based on however Scirra stores the collapsed entries? Who knows.
Besides Monaco, I understand the script could be modified externally - C3 could behave strictly and simply discard the tracked entry of a collapsed line in a script if the expected text does not match the line number?
Lastly, on a random note, I have explored VSCode, gave it a shot, but backed away when I saw weird effects when running my project with "auto-reload on preview" - This has been reported (indeed not a "bug" but it freaked me out to see things revert and I didn't know why/which scripts changed). Will revisit, but overall, I prefer staying within C3, feels far smoother to work with: easily click "preview" in C3, add objects, visit layouts, add/open other "Files" in your project - all without switching between C3/VSCode repeatedly, and without me trying to adapt to a new workflow of dual-monitors with both open (I already have a purpose for my dual monitor).
Anyway yes, thank you for reading yet another wall of text from me.