The question is too broad. To create an engine, you would have to plan what the engine you are creating is going to -- functionality, flexibility, formatting, etc. It is not a simply task... Have you done any of those brainstorming work for what you want it to have or to be yet?
Taywin
Posting Maven
2,633 posts since Apr 2010
Reputation Points: 275
Solved Threads: 375
Skill Endorsements: 17
Right now you don't have enough specification to begin thinking about design, even less code. Start with a specification. Think of a few typical games that you would want to implement with the engine. For each game write down what functionality should be in the engine, and what should be defined in the individual game. Combine all the lists of engine functionality. Generalise it as much as you reasonably can. Write down method signatures and parameter specifications for a set of public methods that games could use to access that engine functionality. You should now have something that looks a bit like part of the Java API documentation.
Then, and only then, think about all the classes you need and how to implement those methods.
If you post the method signatures here I'm sure people will help you refine them.
JamesCherrill
... trying to help
8,497 posts since Apr 2008
Reputation Points: 2,583
Solved Threads: 1,454
Skill Endorsements: 29