Originally posted by DJ Bouche

---

Online capabilities while coding the engine first-hand should always be considered, even if they are not active. It's important to consider these early as if you try to create something that's 100% offline, and try to implement the online later down the track with everything designed strictly as offline, you'll either spend more time trying to implement this, have more difficulty, or even end up with limitations.

Sure, leave out the online, but be sure your engine/code is going to be open and accepting to it, and that it's flexible enough to make smooth adjustments for online extensions.

My only concern here is the engine itself. I see many projects with much ambition just slowly die because an adequate engine cannot be made, or no one is willing to do it. So I will really suggest now (I'm not suggesting you discontinue all other work before this is done, but don't pause the engine work before "other" things are done first either), to really find someone capable of doing this, or work could end up being put to loss. Having an engine also gives you another basis to do your design work on and can speak out your limitations and/or suggest the next steps in what you can/can't design.

---