Neat. By any chance do you mind me taking apart your script?
Funny thing is I suck at programing so I never really learned how to make xEdit scripts (will definitely try now tho) but long story short, just for fun I wanted to make my own custom loading screen mod but found it way too bothersome having to one by one manually make the loading screen FORMs, so I spent a lot of effort on reverse engineering on how a loading screen plugin is made from scratch using hexidecimal "coding" with basic windows batch scripting and text file data manipulation. All so I can automate on adding additional custom loading screens without replacing the existing ones, suffice to say a simple xedit script like this would've been much simpler to implement instead HA
Yeah, learn what you can from it. Be warned that it's probably not "Best Practice". I have found my self in that same situation many times before. PM me if you have any questions.
The only limit is how many loading screens there are; which is how many different loading messages there are. So vanilla FNV has 209 different loading messages. The script goes through and replaces the images associated with those messages with images from the folder. If you have more loading screens (which are defined in the game engine as a message plus an image) added with mods then those will be affected as well if you selected them in xedit.
TLDR: The only limit is how many loading screens there are. I could probably add in the functionality of creating new loading screen entries but I think that is a niche functionality.
6 comments
Funny thing is I suck at programing so I never really learned how to make xEdit scripts (will definitely try now tho) but long story short, just for fun I wanted to make my own custom loading screen mod but found it way too bothersome having to one by one manually make the loading screen FORMs, so I spent a lot of effort on reverse engineering on how a loading screen plugin is made from scratch using hexidecimal "coding" with basic windows batch scripting and text file data manipulation. All so I can automate on adding additional custom loading screens without replacing the existing ones, suffice to say a simple xedit script like this would've been much simpler to implement instead HA
I have found my self in that same situation many times before.
PM me if you have any questions.
TLDR: The only limit is how many loading screens there are. I could probably add in the functionality of creating new loading screen entries but I think that is a niche functionality.