It would be nice if there were some kind of mini GUI for setting this up because every time we update GameGuru or verify the installation it gets overwritten by the default. We can't use a custom script with a custom filename - unless I've missed something...?

I just copy all mine into a folder m8 and keep it on the desktop so if anything changes i just copy/paste em back in i also keep a copy of the titles now as well

Yes. I make loads of backups so I can normally find one to reinstate as the default . But a novice might be confused if their music suddenly stopped working. I think GameGuru's greatest strengths are visual interfaces and user-friendliness and I think this kind of hurdle undermines that.

Of course, this is extremely minor and the team have much more important things to do right now. But maybe in a year or so they might stumble on this post and decide to do a little tweak.

Thanks, mate, for responding.

[quote]We can't use a custom script with a custom filename - unless I've missed something...?[/qote]


You can't create a custom music script with a different name and have it work right off the bat, but you can create a custom script with a different name and place it in a barrel in your level to override the default script.

Once we've knocked a few voting board items off the charts, I am hoping to slowly introduce the idea of a LUA GUI, which would be a non-coder version of scripting, allowing users to change core parameters of the script logic without ever seeing a line of code. Should be great!!

Overwriting music.lua with your own copy, after update or verify..

Sounds good, but what if music.lua had an update itself?!
You would overwrite that too and miss out on the extra's/bugfixes the update had in itself.
Needs a check on every (non custom) script you rewrote/edited (like music.lua), before overwriting the original after an update/verify.

Sort of a Catch 22..

My best solution.. I have this issue with ai_soldier.lua
I made several changes and saved a copy.
After an update, i rewrite the new script.. using my saved copy.
And make a new copy after rewriting (and testing).
This way i do not have to check 600 lines of code to see if there is a change, but i do need to implement my own changes with every update.
Not a nice solution, but it works for me. I mostly use custom scripts, but for the occasional non custom script, this is what i do.
And yes, i could rename it to ai_soldier_custom.lua.. but that way i won't have the (possible) updates the new script brings.