Boogaloogaloo
New member
The reason this happens is because creating a new ccs file called "farming/castle" will create a file under the path "ccs/farming/castle.ccs". In my opinion, this is a good thing as it allows me to arrange my ccs directory logically.
The problem is that CustomCombatManager.getAvailableScripts() only reads files in the base ccs directory.
This is the current situation on Linux. It may be the same on Windows because running mkdir "foo/bar" creates a directory bar nested in the new directory foo. However, I can't be sure as I don't really have the tooling to test at the moment.
I've attached a preliminary patch (probably needs work) that will handle files located in directories, and prepend the directory name followed by a forward slash to the ccs script name. The big question is whether this works on Windows because of the differences in pathname handling.
The problem is that CustomCombatManager.getAvailableScripts() only reads files in the base ccs directory.
This is the current situation on Linux. It may be the same on Windows because running mkdir "foo/bar" creates a directory bar nested in the new directory foo. However, I can't be sure as I don't really have the tooling to test at the moment.
I've attached a preliminary patch (probably needs work) that will handle files located in directories, and prepend the directory name followed by a forward slash to the ccs script name. The big question is whether this works on Windows because of the differences in pathname handling.