I am using the msdp example adapted to RoD to echo the time when the WORLD_TIME changes.
The variable DOES change, I can echo it directly or view in variables list to show it, but as an event handler it doesn't trigger.
Any ideas?
win10 & mudlet 3
Thank you.
event triggers not firing
Re: event triggers not firing
Show a screenshot of the event trigger?
Re: event triggers not firing
If I check the variable it DOES change, but the event never triggers.
Thank you.
Thank you.
Re: event triggers not firing
Enable Debug (it's below Search in the script editor) and check the main screen for MSDP messages - what does it say?
Re: event triggers not firing
System Message:
msdp event <msdp.WORLD_TIME> display(msdp)
and this showed in log....
Alias name=run lua code(^lua (.*)$) matched.
Alias: capture group #1 = <lua msdp event <msdp.WORLD_TIME> display(msdp)>
Alias: capture group #2 = <msdp event <msdp.WORLD_TIME> display(msdp)>
LUA: ERROR running script run lua code (Alias6) ERROR:[string "function Alias6()..."]:4: [string
"msdp event <msdp.WORLD_TIME> display(msdp)"]:1: '=' expected near 'event'new line arrived:
not sure if it means anything...
msdp event <msdp.WORLD_TIME> display(msdp)
and this showed in log....
Alias name=run lua code(^lua (.*)$) matched.
Alias: capture group #1 = <lua msdp event <msdp.WORLD_TIME> display(msdp)>
Alias: capture group #2 = <msdp event <msdp.WORLD_TIME> display(msdp)>
LUA: ERROR running script run lua code (Alias6) ERROR:[string "function Alias6()..."]:4: [string
"msdp event <msdp.WORLD_TIME> display(msdp)"]:1: '=' expected near 'event'new line arrived:
not sure if it means anything...
Re: event triggers not firing
As far as I can tell, NO events are actually firing and triggering anything.
The even does show from debug but it doesn't actually trigger the scripts.
This includes using the built-ins (via mudlet manual.. ie. onPrompt and others.)
The even does show from debug but it doesn't actually trigger the scripts.
This includes using the built-ins (via mudlet manual.. ie. onPrompt and others.)
Re: event triggers not firing
Something is wrong here, as events do work in 3.0. I can't tell what from the information so far though. Can you try one of the event examples on the wiki?
- SlySven
- Posts: 1023
- Joined: Mon Mar 04, 2013 3:40 pm
- Location: Deepest Wiltshire, UK
- Discord: SlySven#2703
Re: event triggers not firing
@Vadim That error message is:
LUA: ERROR running script run lua code (Alias6) ERROR:[string "function Alias6()..."]:4: [string
"msdp event <msdp.WORLD_TIME> display(msdp)"]:1: '=' expected near 'event'" - the un-spaced new line arrived is an unrelated badly formatted error message from (void)TConsole::runTriggers(int)
The error is being generated in TLuaInterpreter::parseJSON( ?, ?, "msdp" ) but it might be via __gmcp_merge_gmcp_sub_tables( ... ) which is in the LuaGlobal.lua file (and those external lua files have just caught me out in a different way...!)
It isn't due to a malformed msdp "key" by any chance - say one with two periods next to each other e.g. something like "msdp.room..name"?
LUA: ERROR running script run lua code (Alias6) ERROR:[string "function Alias6()..."]:4: [string
"msdp event <msdp.WORLD_TIME> display(msdp)"]:1: '=' expected near 'event'" - the un-spaced new line arrived is an unrelated badly formatted error message from (void)TConsole::runTriggers(int)
The error is being generated in TLuaInterpreter::parseJSON( ?, ?, "msdp" ) but it might be via __gmcp_merge_gmcp_sub_tables( ... ) which is in the LuaGlobal.lua file (and those external lua files have just caught me out in a different way...!)
It isn't due to a malformed msdp "key" by any chance - say one with two periods next to each other e.g. something like "msdp.room..name"?
Re: event triggers not firing
Even more fun.... I couldn't even raise events from manually registered events. Then all the sudden I can. Now they seem to work except one.
On Reigns of Despair I can't seem to get the affects variable to read correctly. It always showers empty but raises the event constantly as being changed. I see from a mush client script that they are parsing this into a table to be useable. But mudlet shows it empty always.....
On Reigns of Despair I can't seem to get the affects variable to read correctly. It always showers empty but raises the event constantly as being changed. I see from a mush client script that they are parsing this into a table to be useable. But mudlet shows it empty always.....
Re: event triggers not firing
Was this supposed to be fixed? I just tried to use the script and I am also seeing the same issue as above?