You're entirely correct in all your points... except the shooting part... I've beta-tested this for a while, with hundreds of people. Most of them gave me interface suggestions -- however, it's important not to pounce on every interface idea a user has but think about them in aggregate, and also thi...

I would definitely use this library at some point. I've made crude graphing stuff in the past, for my own mini-projects...

Google it :P

I was talking about your screenshot on Jan 15. I figured the rest were cut-outs, guess I was wrong.

Is it multiplayer yet??

What makes you think I have the resources for a hand-crafted sprite? :P

If I re-made the game in 2D it would be bland and hard to navigate. Not to mention all the time and effort to redo everything in 2D. It's not just a switch...

This game just wouldn't work or be fun in 2D. :[

It is an immense task.

I haven't finalized all the details, so you could help since you seem to brainstorm a lot here. I would welcome ideas as to how you think it should work, just going by the pictures.

Any crazy thing.

I am going to add this to my Capitalopoly tick engine. Thank you again for this excellent code. Edit: I've slightly reformulated this so that it fits inside a namespace and removed the globals: namespace math_parser_namespace ' Uncommenting the DEBUGGING_ macro makes subroutine split print tokens on...

Make it multiplayer and remove the thick window border.

I have stopped development on this in September to work on my Capitalopoly game. I may be interested in continuing development on this soon, but I will need more manpower, so I am wondering if anyone might like to work with me on this project. Please note though, that this project is not open source...

My version. I kept the entire logic bit together, and I pre-subtracted the initial value of "elements". Now it's just subtracted at the end of the loop... dim as integer index = 2, elements = 1 // Scan for two separate elements \\machine\share\restofpath do while ((index <= len(path)) anda...

Interesting how my delete[] rant led to a terrible bug. :D

fxm: I see. Well, I don't think that is the best way to do it because it's not compartmentalized: educationSystem should not be removing or adding all the parts individually; in fact, my example is centered around the idea that educationSystem should only add/remove references, not the actual data.....

Ha, well..... that's weird. I guess the destructor code doesn't chain correctly when delete[] is used? Have you tried a single variable and just "delete"?

You stuck my game in, hehe...

Looks like that obligates me to write a follow-up entry/info for this... and get to work on new features and eye candy!