Hi, welcome to the forum.
WOW, this is impressive! Good work! Especially on getting an external Lua library to work.
Would it help if we modified Lua's require() function to look for binary modules in the plugin's folder first? That should make distributing the plugin much easier.
The natural idea that comes to mind is - assign an arbitrary block in Minecraft to be output of an IO pin - so that when that block becomes powered, the output pin is turned on.
This could be done by letting the user specify the blocks, then simply remembering them in an array and reading their state in OnWorldTick() - since there are only a small number of outputs, it shouldn't be too performance-crippling to check the few blocks. I'm not sure though if we have any method allowing you to access the redstone-power state of a block. Tigerw should know more.
Podle jmena a komentaru v kodu soudim, ze kolega?
Also, you don't need to require the other files in your plugin, all the Lua files in the plugin folder are loaded by MCS (in alphabetical order, except for Info.lua, which is always loaded last) before the Initialize() function is called.
WOW, this is impressive! Good work! Especially on getting an external Lua library to work.
Would it help if we modified Lua's require() function to look for binary modules in the plugin's folder first? That should make distributing the plugin much easier.
The natural idea that comes to mind is - assign an arbitrary block in Minecraft to be output of an IO pin - so that when that block becomes powered, the output pin is turned on.
This could be done by letting the user specify the blocks, then simply remembering them in an array and reading their state in OnWorldTick() - since there are only a small number of outputs, it shouldn't be too performance-crippling to check the few blocks. I'm not sure though if we have any method allowing you to access the redstone-power state of a block. Tigerw should know more.
Podle jmena a komentaru v kodu soudim, ze kolega?
Also, you don't need to require the other files in your plugin, all the Lua files in the plugin folder are loaded by MCS (in alphabetical order, except for Info.lua, which is always loaded last) before the Initialize() function is called.