Hammer of Code

Hopefully this is more to mithro’s liking I did my best to at least link to one or two of the products of my work for each day.



This Week

• Monday:
• “Shelled out” the ruleset a little more by adding all create* classes. diff.
• Converted from basic Galaxy type to a class with a bonus integer that indicates the bonus garnered for owning the entire constellation/galaxy. commit.
• Added “Armies” Integer to the Planet class. (Later removed)
• Encounter a Bus Error when launching the server in a certain way - filing a bug report next monday. archives.
• Tuesday:
• A large portion of the day was spent trying to debug the bus error using gdb and ddd.
• Mithro taught me some good methods for asking for help/filing bug reports. instructions. help post.
• Wednesday:
• Added code to ensure all objects are visible. commit.
• Made note of a bug wherein client would not download objects. I later found that the Planet’s Frame was not being packed with enough data.
• Thursday:
• Converted “Armies” Integer to a Resource; Reinserted resource setters/getters and Frame packing code. Client now loads and displays universe properly. commit. results (really low res).
• Attempted to phase out Star Systems with Planets and in its stead implement lone Planets. It turns out there is a bug where lone Planets do not display in the client. Reverted the change.
• Did research and gave names to all stars corresponding to their relative positions in their constellations. names.
• Friday:
• Plotted all stars on a measured grid. pic.
• Hard coded those positions into the ruleset. Client now displays constellations in proper configuration. diff.

Next Week:

• Spread out star positions to make it more clear the boundary between constellations.
• Implement an adjacency matrix to represent connectivity between stars. This will provide a 2D-array to iterate down a row to discover a star’s neighbors.
• File bug reports on both:
• The Bus Error I discovered and,
• Planets not displaying without a star system parent.
• Begin implementing basic turn structure (before individual orders.) I believe this top down approach will more properly acquaint me with OrdersQueues and make it easier to implement the individual orders.
• Investigate the drawing of lines while issuing orders. This would allow adjacency lines to be drawn to make it more clear which territories neighbor the selected territory.

This time around I want to try a more brief format for my weekly report.



This week:

• Worked more on turn ordering.
• Create a large number of shell classes. Ruleset still compiles properly but implements little to no actual game logic
• Created a quickstart config file for risk
• Worked with llnz to get tpserver-cpp compiling on OSX

Next week:

• Round out the remainder of the shell ruleset
• Work out ObjectTypes for Universe, Galaxies, Star Systems and Planets as per what has been decided for them. See “Things to include” in risk folder
• If things go well create a method to produce the Risk board when the game is created.

Well the time has come to publish my first weekly report. I wasn’t terribly sure on the level of detail and length that is expected but I still don’t officially have to publish this report anyways, so this will be a practice run. I think its sensible to not subject people spotting this article on Planet SOC not to see every last detail, so anyone interested, read on!

Continue Reading »