For my current method of code distribution, see this thread instead.
I've decided to change the way I 'distribute' the Lua code I've been working on. Until now, I've started a thread for each 'type' of module/library that I've made, with the intention of posting updates to each thread when necessary. The trouble is that I never really did this, even for the General Library, which would get extra code whenever I wrote something and thought that it was likely to be useful in other contexts. I also had issues synchronizing multiple copies of 'foundational' modules.
My new strategy is to upload to Github a couple folders from a Test of Time installation that I plan to use for code creation. The lua folder will contain modules that (if working properly) shouldn't need to be changed by the scenario designer (and are likely to be shared between projects). The files in the folders of LuaTestScenario would have to be changed by the scenario designer for the specific needs of the scenario.
This is the repository.
This will make things easier for me, and will make it easier for others to get the latest version of the code I've produced. If you want to double check that the code is recent, simply bump this thread and ask me to sync the code. The process should be quick and easy for me.
The downside is that you might find stuff that is incomplete or just experimenting and testing. Feel free to ask if you're not sure.
I'll use this as my main "Lua Library" support thread (stuff to do with the lessons should be asked in that thread), though I may move an extensive conversation to a dedicated thread. This includes bug reporting/fixing and questions about how to use the modules. You can also ask that I prioritize work if you are likely to have a use for it in the short to medium term.
I've decided to change the way I 'distribute' the Lua code I've been working on. Until now, I've started a thread for each 'type' of module/library that I've made, with the intention of posting updates to each thread when necessary. The trouble is that I never really did this, even for the General Library, which would get extra code whenever I wrote something and thought that it was likely to be useful in other contexts. I also had issues synchronizing multiple copies of 'foundational' modules.
My new strategy is to upload to Github a couple folders from a Test of Time installation that I plan to use for code creation. The lua folder will contain modules that (if working properly) shouldn't need to be changed by the scenario designer (and are likely to be shared between projects). The files in the folders of LuaTestScenario would have to be changed by the scenario designer for the specific needs of the scenario.
This is the repository.
This will make things easier for me, and will make it easier for others to get the latest version of the code I've produced. If you want to double check that the code is recent, simply bump this thread and ask me to sync the code. The process should be quick and easy for me.
The downside is that you might find stuff that is incomplete or just experimenting and testing. Feel free to ask if you're not sure.
I'll use this as my main "Lua Library" support thread (stuff to do with the lessons should be asked in that thread), though I may move an extensive conversation to a dedicated thread. This includes bug reporting/fixing and questions about how to use the modules. You can also ask that I prioritize work if you are likely to have a use for it in the short to medium term.
Last edited: