(Resolved)[XP]UMS Forgets Shortcuts?

[Untitled]

Heya, I'm using Ccoa's Universal Message System (vl8.0, if that means anything), and it's pretty awesome. One thing, though. If I save the game, quit out, and start it back up, then enter a talking event, previously defined shortcuts over 9 are forgotten. So if I type \c10, then the \c1 character will appear, and a 0 will start the message. This is... Well, annoying. Help?

(And while I'm at it, I feel like saying that there's quite a delay between when I win a battle and when the EXP/G/Items window pops up. Is this normal?)

[Blizzard]

Maybe you should be using \c[10].

[Untitled]

Nope, now the command is ignored entirely.

[ForeverZer0]

UMS Instructions (v.8.0): ShowHide

  \b          - toggle bold on and off
  \bopc[i]    - change the back opacity for this message to i (should be 0-255)
  \c[i]       - change the text color
  \c[#IIIIII] - change the text color to the hex code (temporary)
  \e[i]       - place the text box over event i (0 = player, -1 no event)
  \face[name] - changes the face graphic to name.png (leave empty [] for no face)
  \fl         - change face justification to left
  \font[name] - change the font to name, leave empty [] to return to the default font
  \fr         - change face justification to right
  \g          - display the gold window
  \height     - height of the message window, works only in normal mode
  \i          - toggle italics on and off
  \ic[name]   - draw icon name in the window
  \ignr       - Do not write anything on this line, only process codes, must be the first thing on a line 
  \jc         - justify the window to the center, ignored if using \e
  \jl         - justify the window to the left, ignored if using \e
  \jr         - justify the window to the right, ignored if using \e
  \m          - toggle mode between normal and fit window to text
  \n[i]       - display the name of actor i
  \nm[name]   - display the name in the name window, leave empty [] to remove the name window
  \oa[i]      - display the icon and name of armor i
  \oi[i]      - display the icon and name of item i
  \opc[i]     - change the opacity for this message to i (should be 0-255)
  \os[i]      - display the icon and name of skill i
  \ow[i]      - display the icon and name of weapon i
  \p[i]       - pause for i frames before writing the next character
  \pt         - toggle pause display on and off
  \s          - toggle shadowed text
  \shk[i]     - set window shake to i, higher i is bigger shake, 0 is no shake
  \sk[i]      - begin text to be shaken, i is begger shake
  \sk         - end text to be shaken
  \skip       - toggle text skip on and off
  \ta[i]      - center the window over train actor 1
  \t1         - switch to the talk1 comic thingy
  \t2         - switch to the talk2 comic thingy
  \tc         - center the text, must be the first thing on a line
  \th         - switch to the thought comic thingy
  \tl         - left justify the text, must be the first thing on a line
  \tr         - right justify the text, must be the first thing on a line
  \v[i]       - display variable i
  \width      - width of the message window, works only in normal mode
  \w[i]       - wait for i frames after receiving this code, then close the window
  \ws[i]      - change the write speed to i
  \slv[name]  - set this window to be slave window name, or show slave window name
  \inc        - include this window in the last

Not one of them is a \c## command. You need the brackets. If that is still not working, then you either entering invalid values, or you have another script below this one that is overriding the method in Window_Message.

[Untitled]

Ohhhh that's it. And now I see what Blizzard was saying. I need to register the shortcut with brackets, too. Well, then, thanks!

[Blizzard]

Actually it wasn't what I was saying. I have no idea what I'm talking about, I never used UMS. xD I just thought you were maybe trying to use a color command and that they still worked in the UMS.

[Untitled]

Oh, well you helped me figure it out regardless
I don't exactly know what the protocol is here. Lock the thread, ignore it, whatever. But thanks again! Now I'm going to point at my newest thread