No, I don't mean to compete with ccoa's UMS. If you see this is not a request for support, please move it to its proper place (since I don't ask for support nor request a script). Thank you.
Here's the story.
I have built my game heavily using AMS when UMS finally rose out. Since I'm too lazy to edit all conversations (with some changes to similar codes, such as \Name to \nm) and some limitations to UMS (before ccoa updated her script, silly me >.<), I decided to merge some UMS features that were not available in AMS.
For my needs, it's completed, but here's my offer for you, AMS users who have the same dilemma and wish to use UMS features on AMS.
If ccoa permits, request here some UMS features which you wish to add to your AMS and I'll work on it. Please be patient as I can't be online too often, but at least I'll check the requests weekly and make them, if any, as fast as I can (merging 2000+ lines of codes into 1500+ is tricky). Also note that I only work on AMS 4 R2 since I find this is the most stable one.
Again, if ccoa permits and there are heavy requests of this, I'll post it in Submitted Script section.
Thank you.
Credit goes to Dubealex and ccoa, with all my respects.
Here's the story.
I have built my game heavily using AMS when UMS finally rose out. Since I'm too lazy to edit all conversations (with some changes to similar codes, such as \Name to \nm) and some limitations to UMS (before ccoa updated her script, silly me >.<), I decided to merge some UMS features that were not available in AMS.
For my needs, it's completed, but here's my offer for you, AMS users who have the same dilemma and wish to use UMS features on AMS.
If ccoa permits, request here some UMS features which you wish to add to your AMS and I'll work on it. Please be patient as I can't be online too often, but at least I'll check the requests weekly and make them, if any, as fast as I can (merging 2000+ lines of codes into 1500+ is tricky). Also note that I only work on AMS 4 R2 since I find this is the most stable one.
- Comic bubble (\t1, \t2, \th)
- These codes: \inc, \ignr, \b, \i
- Shortcuts with no limitations (unless I can figure out why ccoa stricts the shortcuts for some codes)
- Slave windows
- These codes: \inc, \ignr, \b, \i
- Shortcuts with no limitations (unless I can figure out why ccoa stricts the shortcuts for some codes)
- Slave windows
- Disable and enable comic bubble via message text (\cd to disable, \ce to enable, must be on the first line)
- Show event name (very useful to show a message with a very long name). For instance, instead of typing \name[Security Guard] you can use \name[\e[1]], where \e[1] refer to as event 001's name, that is Security Guard. Of course, RMXP may limit event name length, so give me a better suggestion for this.
- Show event name (very useful to show a message with a very long name). For instance, instead of typing \name[Security Guard] you can use \name[\e[1]], where \e[1] refer to as event 001's name, that is Security Guard. Of course, RMXP may limit event name length, so give me a better suggestion for this.
- When using slave windows, the talk icon appears on the slave event first, even though the event has not yet been ready to speak. This is a UMS bug that I'll fix once UMS fixes it.
- Slave codes must be applied immediately for use, otherwise the main message will not close infinitely. For example, this will work:
> \slv[1]Hi there! Long time no see!
> \p[1]\name[\e[1]]So where do you want to go?\slv[1]
This won't:
> \slv[1]Hi there! Long time no see!
> \p[0]\name[\n[1]]I think I'll go for a vacation.
> \p[1]\name[\e[1]]So where do you want to go?\slv[1]
The game will be still running after the first message has finished, but you can't go on the next message, leaving the game seems as hangs (I have debugged this and you can still press any button but nothing happens).
This is also a bug from UMS, so I recommend using proper use of slave windows as I described above.
- Slave codes must be applied immediately for use, otherwise the main message will not close infinitely. For example, this will work:
> \slv[1]Hi there! Long time no see!
> \p[1]\name[\e[1]]So where do you want to go?\slv[1]
This won't:
> \slv[1]Hi there! Long time no see!
> \p[0]\name[\n[1]]I think I'll go for a vacation.
> \p[1]\name[\e[1]]So where do you want to go?\slv[1]
The game will be still running after the first message has finished, but you can't go on the next message, leaving the game seems as hangs (I have debugged this and you can still press any button but nothing happens).
This is also a bug from UMS, so I recommend using proper use of slave windows as I described above.
Again, if ccoa permits and there are heavy requests of this, I'll post it in Submitted Script section.
Thank you.
Credit goes to Dubealex and ccoa, with all my respects.