sven wrote:For the project of breaking up CloseAndAttack.lua, you probably want to create a couple new lua files, and then mark all of those files as dependencies of CloseAndAttack.lua by including the appropriate depends calls in CloseAndAttack.lua.
That said, there's a bit of a bug here, because if you're working inside a Mods/ subdirectory, the game is potentially going to get a bit confused by the fact that there are now 2 different CloseAndAttack.lua files that it knows about.
Given the way I set things up; *distributing* mods via the Mods/ subdirectory ought to more or less work; but, *developing* mods is almost certainly more comfortably done by editing the core game files in Lua state\.
As I said in my post on git, in theory, it would be pretty straightforward to write a perl script or something that would automatically export a modder's work into a sharable Mod directory, if we assume that you've been storing your work in git as a 'branch' off the official vanilla version of Lua state.
Unfortunately, this strategy would require that modders get used to using git; and git's a bit of a beast, so perhaps that's a bit much to ask
edit: Though, from your Mod naming convention, I suspect you may already be using git, in some capacity, to manage your own diffs? So maybe it /would/ be useful to write up that export script?
