Hammer of Code

It dawned on me that a number of so called extra ideas I’ve had should be kept track of. Instead of privately keeping a list of future TODOs I decided to create this page to add ideas/contributions I might decide to do later in my project or afterwards. Without further ado here the ideas are:

• XML/bitmap/text-based Map import
  • This would entail the option to specify a file of <undecided> format that specifies to the ruleset WHAT objects to create and HOW they are connected. 
• Find an AI to test the ruleset with
  • This is actually fairly likely and will affect how easy it is for me to test/debug my ruleset.
• Contribute to Ruleset documentation
  • I think that my relevant experience in learning ruleset development will allow me to help future developers to reduce the learning curve.
• Create a set of shell/example classes
  • A good and complete set of ruleset classes will let a developer jump in and simply plug in their logic. This will also aid well versed developers to make new rulesets more quickly
• Make connectivity lines draw outside of orders
  • This is very likely to be impossible because it involves modification of tpserver-cpp itself, but I can still dream.