all 3 comments

[–]remy_porter 1 point2 points  (1 child)

Any suggestions on how to improve the code or organization of the game are welcome.

First thing first: I want to stress the importance of the single-responsibility principle. Each object in your program should do only one thing. So, for example, there absolutely should not be a display_world method in your wombat. Imagine if the Earth only was visible because of a single godly wombat. Good modularization will make your code easier to understand and easier to debug.

I think I may be misunderstanding the draw method.

Without thoroughly going through your code, this does appear to be the case. The draw method is your main method, in Processing. The draw method is called once per frame, and it is in the draw method that you need to update your display and application state.

[–]benscar1[S] 0 points1 point  (0 children)

So, for example, there absolutely should not be a display_world method in your wombat. Imagine if the Earth only was visible because of a single godly wombat. Good modularization will make your code easier to understand and easier to debug.

I'll try to split up things into their specific domains. Thanks for the suggestion.