Plugin execute a script on main lua file

Hi all,
I want to have a plugin executing a simple script on the main .lua file as if it was inside that file.
The function is actually being executed, but the value returned is not the same as if the function is called from the same lua file.

How can I acomplish this?

Thank you

If the function is being executed, then it's working. To know why it's returning something other than what you expect, I think we need to see your script file.

It's a pretty simple script, ill try to make it short:

I have this on the beginning of the main .lua file:



Then something like this on a login:



I also have a simple getter for this value:



If I try this



from prompt, i get the correct true return. The problem is that when I call getCanStab() from a plugin, its returning the default value (false).

You are better off using a MUSHclient variable, and not a Lua variable (ie. use SetVariable). Then in the plugin use GetPluginVariable with an empty plugin ID to find the main variable value.

Hi Nick,
when you say I'm better off using global variables you mean there isnt another way? I have over 100 variables, making all of them global would be a lot ot work...

What is calling your onLogin function? I think the problem you're encountering is that plugins and the world don't share the same script space. Just because onLogin is being called by the world doesn't mean that canStab is being set to true for the plugin. Nick's suggestion of using GetPluginVariable with an empty ID to get the world's stored variables is one way around that.

Oh, I thought the script had an unique space... that's what is happening then. The onLogin function is being executed from a regular trigger on my world, not from the plugin.

Thank you guys, gonna try the global variables...

Each script (in each plugin) has a unique script space, plus one for the main script file. They might even be different languages (eg. VBscript, Lua, JScript).

However there is a module that lets you easily access MUSHclient variables from Lua:

https://github.com/nickgammon/mushclient/blob/master/lua/var.lua

It should be part of the MUSHclient download. See http://www.gammon.com.au/modules for more information (scroll down to the var.lua part).

Your original question mentioned one variable. There could be other ways, why are you trying to share 100 variables between a plugin and global script space? Maybe that can be redesigned.

There are ways for the main script file (or main triggers and aliases) to communicate with plugins. One is CallPlugin.

This lets you pass information down to plugins.



Another is to "Execute" an alias, which the plugin then captures.

For example:



That could match an alias in your plugin (TellMyPlugin *) which might execute the rest of the line as Lua code. That could be dangerous, but it is an example of what you might do .

Having separate script spaces is supposed to be a feature. Putting aside the fact that the plugin might be using a different language than the main script file, it stops you accidentally using some variable (eg. "counter") in different plugins and not realizing they are interacting with each other.

Thanks for the info, I didn't know that module. That will sure help in other situations...



I tried to make it a little simpler than it really was. The specific function I was working on uses 5 'global' variables, which isn't bad to expose as global. The 100 I mentioned are all variables I use on script file, but I'm sure I don't need all of them exposed.



So many possibilities. I liked and tried this execute as an alias and it worked perfectly. Just a small issue, and I'm not sure it was just a feeling, I noticed a little delay on the execution of the alias, but nothing too bad.

Thanks again for all the info you two.

CallPlugin would probably be faster (I think Fiendish uses it a lot). However the alias idea should not be noticeably slow.

I used the alias approach to make the other way, the plugin calling a function on the main script file, using the main script space, which is what I wanted on the first place.