Lately I've been learning a lot about Python and how it handles objects through another side project, and I'm starting to see where I should go back and rework what I have so far for Architect of Worlds. This comes at a good time, since I've gotten up to generating everything but moons, and that step is looking like it will be a bit more intensive than the text suggests - in terms of programming, that is.
So I think my next step will be to go through the original code, clean it up as much as possible and implement a cleaner data management system. I also want to break out a couple of bits into their own functions so they can be reused whenever necessary...I'm looking at you, orbital placement! Once this is done, I'll proceed to do moon placement.
I also have a couple of questions about the model being presented, since it doesn't appear capable of producing the insane number of moonlets our gas giants have (79 for Jupiter and 62 for Saturn). Mind you, in terms of storytelling, most of those moons are inconsequential, but knowing their total number is helpful, and if I know that, I can place them automatically and develop them from there. So, because my application doesn't involve a human rolling dice and interpreting results, I don't see an issue with rolling up 120+ moons no one will ever care about visiting.
Also, When you roll things up randomly, sometimes you get interesting results that spark creativity. So I'd rather roll up a bazillion moons and risk getting a GM's creative juices flowing than say, "There are a lot of them, and they probably won't be interesting enough to justify the time you'll spend rolling dice to generate them." But that's because of the medium, not a fault in Jon's system by any means.
So that's my plan. I'll keep you updated on progress. Hopefully I"ll have enough put together to use soon!
No comments :
Post a Comment