No immediate answer for this is coming up. gmcp table should always be
present and Mudlet does not delete it.
Could you try the next two steps:
* see if it happens on a new profile
* record a video showing the issue, also include that running the script
directly works fine
Apologies for the issue and appreciate your patience in troubleshooting
this.
On Mon, 6 Mar 2017 4:15 am cyril duez, <1660...@bugs.launchpad.net> wrote:
> I just tried 28fda4d and yes, i have still the issue.
>
> --
> You received this bug notification because you are a member of Mudlet
> Makers, which is subscribed to Mudlet.
> https://bugs.launchpad.net/bugs/1660082
>
> Title:
> Error on script registered on GMCP event
>
> Status in Mudlet:
> New
>
> Bug description:
> Hello,
>
> I have created a simple script (called GMCP) which is registered upon
> gmcp.char
>
> It only contains : display(gmcp)
>
> Now when i received the GMCP event i have this message in the debug
> window : "LUA: ERROR running script GMCP (GMCP) ERROR: attempt to call
> a nil value"
>
> I have tested this on the latest release (3.0.iota) and i have built
> the latest commit (e5b832b) but i get the same result.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mudlet/+bug/1660082/+subscriptions
>
> ___
> Mailing list: https://launchpad.net/~mudlet-makers
> Post to : mudlet-makers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~mudlet-makers
> More help : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~mudlet-makers
Post to : mudlet-makers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mudlet-makers
More help : https://help.launchpad.net/ListHelp