Hello - so a while back I had to end up redoing a bunch of scripts after an error, due to poor naming, and ordering.
It actually wasn't a bad thing because I managed to rebuild them faster and much more effective than last time.
But to save myself further heartache - I did want to learn what you guys do when it comes to naming scripts, and how you guys back them up in case of a fatal error.
What I do is just copy and paste scripts onto note pad, and back that up to a hard drive. I have no set way of naming scripts and will constantly rename them to try and let me know what they do.
Script Naming and Back Up procedures?
● ARCHIVED · READ-ONLY
-
-
there isn't much other you can do with VXA-scripts (as opposed to MV-Plugins where renaming is a very bad idea).
However, I suggest (if the script doesn't already contain this info) adding a comment section with the name of the scripter and the address of the website where you got it.
Most scripters place this inside their comments, but there are some who don't (especially for short scripts) and that could cause problems later if you no longer know where you got the script and who to credit. -
Right now, I'm using all custom scripts. If they were already named - I would put the creators name and what they named the script.
I mean I guess I can also do that with my scripts. Except naming is a pain.
Are there any faster ways of backing up scripts other than copy/pasting them to separate note pads? -
My script backup is to copy Script.rvdata2 to dropbox folder. I did it whenever I reached a milestone, like, able to create something difficult. As for naming, idk why it's a problem. Personally I never really have such problem. Bcz I usually deal with the naming I come. I did some mistakes on naming stuff in my battle system script, but I shrugged off and move on (I assume naming here as variable naming).
-
It was about the scripts in the editor. And what to name them - so that you know what it does from it's name, and don't forget it or it's load order.
-
Usually for me, load order doesn't matter. Because I essentially hardcode and overwrite everything. Granted, I know how to script. But I know you know how to as well. I usually separate one feature / function in separate script slot. Having one category each. I grouped one that handle battle system, one that handle small gimmick all together. Here is what it looks like. Some of them only contains few lines of code
Spoiler
For people's script / public scripts. I usually put all of them above my custom one since they're subject to be overwritten by custom one below. Overall my script order and names goes like this
Spoiler
And as for backing up, I put on the below of the main. It's much faster than copy paste into text files. Usually for the case when I want to roll back.
Spoiler -
Ok - I gotta applaud how you can see and use all those scripts and not get dizzy. Though I am gonna keep a note about keeping my custom stuff at the ground floor. This is my current list -

also I absolutely need to make A FUKKEN TO DO LIST. -
Having named them as a class name is bad practice imho. It's better to name it whatever it does rather than that. For example, if I'm going to rename your script list, it goes like
▼ Visual Battlers
VB - Core
VB - Sprite Effects
VB - Gender System(?)
VB - Battler Sprites
Also having one empty slot for gap for each category could help you break down the list. I do this not only in script editor, but also recently on animations. Because I used a lot of custom one, up to the point it's getting harder to track them. In your list, it has no gap, no wonder it's harder to track.