YesNoOk
avatar

Invalid trigger: CapsLock? (Read 2155 times)

Started by Ogre., October 10, 2020, 10:11:04 am
Share this topic:
Invalid trigger: CapsLock?
#1  October 10, 2020, 10:11:04 am
  • avatar
  • **
    • UK
I have observed that VarSets for elem and adds for "(numbers)" yield an error
when particular "var()" and "Var()" don't possess the *correct capitalization.*
My most recent bout is an error quoted, Invalid trigger: noshadow.
I searched the completely valid assertspecial flag only to find two forms:
noshadow, and NoShadow. Is this the reason for the error?
Re: Invalid trigger: CapsLock?
#2  October 10, 2020, 12:05:46 pm
  • *****
  • Resident Tosspot
  • Pftheh
    • UK
    • plasmoidthunder.neocities.org
Noshadow is not a trigger, it's an AssertSpecial flag. If it's being used as a trigger somewhere, then that's incorrect. What version of MUGEN are you using? As a flag, it's not case sensitive in 1.0 or 1.1.

Oh, I want a diagram. I fucking love diagrams.
Re: Invalid trigger: CapsLock?
#3  October 10, 2020, 09:18:49 pm
  • avatar
  • **
    • UK
Ah, so I must find the instances where noshadow is a trigger :D
Thank you very much! I was stumped, m8
Re: Invalid trigger: CapsLock?
#4  October 10, 2020, 10:03:25 pm
  • avatar
  • **
    • UK
Are triggers from assertspecial allowed to equal anything other than trigger1 = 1? :)
Re: Invalid trigger: CapsLock?
#5  October 11, 2020, 06:35:56 am
  • avatar
  • **
    • UK
I performed a search on all characters, and
set aside from some odd coding like three interger in
IntPersistIndex, and assertspecial in cmd, which seem
legal by Mugen standpoint, some idiots are using
"projshadow = noshadow", and "flag1 =" lol
Re: Invalid trigger: CapsLock?
#6  October 11, 2020, 11:12:55 am
  • *****
  • Resident Tosspot
  • Pftheh
    • UK
    • plasmoidthunder.neocities.org
AssertSpecials accept the same triggers as any other sctrl and will remain active for as long as the triggers return true, so yes, you can use more than just "1" as a trigger.

The .cmd is still a state (state -1, specifically), so there's nothing problematic about putting AssertSpecials (or any other sctrl, really) in there; the only thing to keep in mind is that it's the last minus state processed and it is read by any Helpers that have "keyctrl = 1".

Oh, I want a diagram. I fucking love diagrams.