When you design your game systems to be like machines that process data as instructions, you can make changes to the game efficiently, even when it’s running. Make as much of your game as data-driven as possible. This makes it easier to piece multiple components together to build something new. That way, most of your check-ins are at the prefab level, which results in fewer conflicts in the scene.įocus each component on solving a single problem.
This helps a lot with source control with bigger teams, wherein scenes are a list of prefabs and your prefabs contain the individual functionality. As much as possible, every single prefab that you drag into a scene should have its functionality contained inside it. Set up Prefabs so that they work on their own. This allows you to have scenes that have unique behavior that was not present in other scenes, without having to do a hack. Every time you hit a scene, it should be a clean break and load. Create scenes as clean slates: avoid having transient data existing between your scenes.For example, an inventory system should be able to communicate with other systems in your game, but you don’t want to create a hard reference between them, because it makes it difficult to re-assemble systems into different configurations and relationships. Avoid creating systems that are directly dependent on each other.
0 kommentar(er)
