Planet Chili

Here Youll find your answer.
Validation and error checking is a must.

I dont really understand what are you trying to do. But I'll point out some error in the given code. First of all your function is a bool. This means that you have to return a bool value on exit. If your index gets greater than 10 you dont enter the for loop and dont return anything from the functio...

Here is a great article on game loop. Pretty good explained and outlining pluses vs. minuses of each implementation.

I think you should start over with the project. Don't get me wrong. It is just too messy now. You have 2 bases and marines moving between them. For those 3 things you create 5-6 classes and almost each of them inherits from somewhere. And most of the inheritance does not make sense. Like for example...

Yes thats correct. The setMethod sets the value of a given private attribute and the getMethod gets the value of that attribute and returns it. You might as well define just a getMethod without a setter and this way you`ll never be able to change the value of the attribute. class Planet { private: s...

Well glad I could help a bit. Seems as if you have M_distance as a public attribute. That is considered to be bad practices. You want to keep your class elements private is what all the hardcore c++-ers will tell you. Thats why you'll eventually need access modifiers (get and set methods). Like this...

You declare an array of Planet objects and than go with the for loop planet* planArray = new planet[planetNum]; // in order to be able to do that you need // to have a default constructor defined for (int i = 0; i < planetNum; i++) { // you can use here setters the same way as the // getters in the ...

If you do a MMO you should be storing the data on a server not on each client pc.

Thats actually easily solvable with oop. You have two classes. Star and Planet. In the Planet class create a constructor taking those 3 parameters from star that you need. In the main method You create an Object of type star and after that using this object you can access its private components by u...

This approach of creating array in the class is wrong. The last version was working correctly. The only problem with it was that you are creating surfacesequence which consists of multiple surfaces every time you call the Marine constructor. So if you make an array of 10 marines you create 10 times ...