Comments on: iss gohzilla http://www.hammerofcode.com/2008/05/iss-gohzilla/ >>me.become!(:ruby_developer) Tue, 06 Jan 2009 12:26:13 +0000 http://wordpress.org/?v=abc hourly 1 By: xdotx http://www.hammerofcode.com/2008/05/iss-gohzilla/comment-page-1/#comment-29 xdotx Sun, 25 May 2008 06:45:59 +0000 http://www.hammerofcode.com/2008/05/iss-gohzilla/#comment-29 # I noticed minisec goes pretty in depth for its naming system. If my map is static do I need to worry as much about that? Will I just be creating my map in a big set of statements, and not dynamically? ## RFTS has a statically-named system. Just use a few helper functions for creating a system and make each one manually by name. # On extending star system/planets: How to add a “connects to…” linked list for connectivity? ## internally in your planet/system class? Or do you want that information client-side visible? # Will every system be a star with one planet? ## Iif you want it to be. Contained objects are completely optional for all things afaik. I'm fuzzy on the other two. I believe you do need containerids though, and supporting persistence would be a good idea, though it shouldn't be too important. # I noticed minisec goes pretty in depth for its naming system. If my map is static do I need to worry as much about that? Will I just be creating my map in a big set of statements, and not dynamically?
## RFTS has a statically-named system. Just use a few helper functions for creating a system and make each one manually by name.

# On extending star system/planets: How to add a “connects to…” linked list for connectivity?
## internally in your planet/system class? Or do you want that information client-side visible?

# Will every system be a star with one planet?
## Iif you want it to be. Contained objects are completely optional for all things afaik.

I’m fuzzy on the other two. I believe you do need containerids though, and supporting persistence would be a good idea, though it shouldn’t be too important.

]]>