So folks, mainly Lua coders
I'm looking for ideas for features to put in the next iteration of the DLL.
So far I'm planning to create AddPersistScript() in much the same vein as you can use BindKey() with the added feature that you can make a script persist only for the life of that Lua state or for the entirety of the game session. In either case, it will not affect the user's configuration and won't persist after a game shutdown.
The next thing will be TickDelayed scripts, this will allow you to declare a script (first run or persistent style) which will not be executed until a configured number of ticks have passed. This means that if your script depends on a number of game Lua classes, you can ensure that it only executes itself after they've been setup.
Any other suggestions?
I'm looking for ideas for features to put in the next iteration of the DLL.
So far I'm planning to create AddPersistScript() in much the same vein as you can use BindKey() with the added feature that you can make a script persist only for the life of that Lua state or for the entirety of the game session. In either case, it will not affect the user's configuration and won't persist after a game shutdown.
The next thing will be TickDelayed scripts, this will allow you to declare a script (first run or persistent style) which will not be executed until a configured number of ticks have passed. This means that if your script depends on a number of game Lua classes, you can ensure that it only executes itself after they've been setup.
Any other suggestions?
Aucun commentaire:
Enregistrer un commentaire