Commands Twice ?

[Kosmos]

I may have missed it, but has the issue been resolved about the OnEvent scripts and having to list commands twice to get them to work the first time you do the event?

[Zonx]

Double listings were only (and still are FAIK) ever needed for show_window and hide_window.

The reason for it is that usually the object using the command doesn't have that command as a property, so the first instance creates the property rather than exicuting the command.

[Deathbane27]

No, the issue has not been resolved. You can't even do a preset property to prevent requiring it.

Originally Posted by Zonx

Double listings were only (and still are FAIK) ever needed for show_window and hide_window.

And /useability, and /say, and /telltarget, and /tellchannel, and /mood, and...

[Zonx]

Ah right, forgot about silly chat commands. I guess that's all show and hide are. So yah in that sense all "chat" commands

[Deathbane27]

That would be every command that requires paramaters, actually.

[Zonx]

Are there any commands that require params and aren't meant to be entered in the chat box? Isn't everything on "The List" from the /list command?

Hehe we're getting all semantical. Lets rephase this. All "SLASH" commands require double listing weather the slash is needed in UIBuilder. Prety sure Slash Command is the correct EQ term to cover all of that stuff. Emotes (which don't require params) would be a subset. UI Commands would be another set, or maybe a superset.

Oh I guess some were discovered through alternet means, but aren't those still slash commands?

[Deathbane27]

Originally Posted by Zonx

All "SLASH" commands require double listing

Eeeeeeeexactly. Unless no paramaters are required.

I don't give a monkey's left buttcheek what you want to call slash commands, but I severely hate the spread of misinformation.