[SCRIPTING] HOW TO TEST FOR SCRIPT COMPATIBILITY?

Posts

Pages: 1
Red_Nova
Sir Redd of Novus: He who made Prayer of the Faithless that one time, and that was pretty dang rad! :D
9192
I'm writing a script in Ace that brings forward certain features you can't change by default in the database (maximum battle members, keeping EXP upon changing classes, etc.) for convenient customization, and I wanted to submit it when I think I've got enough to warrant a submission. The problem is that there are loads of scripts that mess with these features as well. Since it's obviously impossible to test every script ever written for compatibility, what are some general guidelines one can follow to make sure that there are as few issues as possible?

Here's what I've done already:

- Tested in vanilla Ace.
- Tested in Yanfly's core and battle engine scripts.
- Tested in Luna Engine Base (which contains Yanfly's core and battle engine).
- Placed script at the very top and very bottom of custom script list.

All of these have produced little to no problems with method overwrites (though there's not much this script actually CHANGES), but the settings can be overwritten by other scripts that adjust the same settings as mine if not placed on the very bottom of the script list. So far, that's the only issue I see, and there's nothing I can do about it.

So, unless there's a step I didn't take, would this be enough testing to justify an initial release?
Just submit it and deal with all that in the aftermath!
Red_Nova
Sir Redd of Novus: He who made Prayer of the Faithless that one time, and that was pretty dang rad! :D
9192
Alright, it's submitted. We'll see what happens!
Pages: 1