Rpg Maker Developers Group

Motivation: The CTRL+F introduction in MV for the switch selector was honestly an absolute game changer for me. Before, larger projects weren't really manageable at all for me. Once I got past two hundred switches which happens quickly for me when lots of narrative choices and detail interactions on maps add up, it just became impossible to find old stuff anymore. Cue for a repeated 1-2 minute break just to find a switch that I know exist, but that I just can't recall where I put it.

Now even 600+ switches (and I have that many in one project) are somewhat manageable, but it's still not very fun because it's a bit of an unintentional chaos. The search helps, but doesn't fix the underlying issue: even with the best initial ordering with area A's switches in 1-100, area B in 101-200, ... one area will eventually outgrow its range and it will end up in chaos when I need to overflow into unanticipated ranges. (Also compare the "-----Reserved" range in the initial "Skills" MZ database, any large project will eventually run out of that space and clash with the "-----Enemy" marker. It's just how all large projects eventually go.) So, here is what I think would fix that for switches where it is most needed:

Description of the Feature:
I think the following feature would be another game changer for giant projects: Switch Reordering. The idea is to let me move a switch to a different number, but also all associated event uses will be automatically changed so that the original number/slot is "cleaned" for (re)use. Obviously, this would be similarly helpful to have for at the very least also Variables, Items, Skills, Weapons, and Armors, IMHO in descending order of usefulness. But I am proposing it for switches first since again here, I think it would be the biggest game changer for giant projects.

Mockups:
Here is how I think it should work:

Step 1: Open Switch Selector from anywhere

Protected download

Step 2: Pick "Move..." in context menu of switch

Protected download

Step 3: Wait for calculation which collects what will be affected, and what slots are definitely unused

Protected download

Step 4: Pick new slot which can only be one calculated as unused by all event pages in the entire project

Protected download

Step 5: Wait for result while all events have their references to this switch swapped out with new number

Protected download

Step 6: Enjoy! Your switch has now been reordered!

Protected download

I apologize since this has likely been proposed before. But the mockup hopefully is useful to see how it could work in practice.

Possible issues with this feature:

I imagine implementing it such that really all references in any sort of event instruction are reliably changed might be somewhat challenging. Also, plugin commands that somehow indirectly refer to switches (since I think it's not directly possible as recognized @arg @type right now) would still need to be adapted manually. And I'm not sure a new user would understand the usefulness of it.