Game Engine Building Environment - The-Source-Eternal/Unwritten3D GitHub Wiki

For various reasons it may be better to build the game first and build the editor in the game before building the external game editor

Building the Game First

Pros and Counter Arguments

######There will be features built specifically in and for our game that are not needed for the game editor/creator itself:

• limiting access to modifying objects for game purposes (e.g. you cant just delete the boss, b/c we want you to use the skills you learned.)

• Counter arguments: ~ Perhaps if the player deletes the boss, they don't get the item they need to finish the level. ~ Other games will have objects they don't want the player to change, perhaps this can be included under that umbrella. ~ Perhaps we want other people to be able to build games where their players can edit the code, so this feature could be useful to them. ~ Perhaps we can just make our own class that disallows user editing. ~ We might want to limit what specifically is or isn't editable about the object, so perhaps we should only do custom scripts of our own anyway.

• Another feature:

Cons and Counter Arguments

This will be confusing to people joining the project:

• Are they joining to make a game, or to make a game editor?
• Will they see doing both at once as scope that's out of control and avoid the project?

• Counter arguments: ~

It is important that we figure out if making the game engine and creator and the game itself is something that's achievable:

• Perhaps we really only have time for the game itself :(

• Counter arguments: ~