Repository navigation
Technical Design
Sherk-cell edited this page Mar 22, 2024
·
103 revisions
A TDD serves as a blueprint for your programmers, outlining the game's technical aspects. Here's how to build one on a GitHub Wiki:
- Introduction: Briefly describe the game, genre, target platform (PC, mobile etc.), and core functionalities.
- Game Architecture: Explain how the game will be structured. This might involve components like the game engine, networking (if multiplayer), and data management. You can include diagrams for better visualization.
- Core Systems: Delve deeper into the technical details of major systems: Gameplay Mechanics: How will movement, combat, or resource gathering work?
- Input & Controls: How will players interact with the game (keyboard, mouse, touch)?
- Rendering: 2D/3D graphics engine and rendering pipeline details.
- Physics: How will physics simulations be implemented (if applicable)?
- Networking (if multiplayer): Communication protocols, server architecture, and data synchronization.
- AI (if applicable): Enemy or NPC behavior logic.
- Save System: How will player progress be stored and loaded?
- Data & File Formats: Specify file formats for game data (levels, characters, audio, textures etc.).
- Development Tools & Technologies: List the programming languages, libraries, and frameworks used for development.
- Testing Strategy: Outline how the game will be tested (unit tests, integration tests, manual testing).
-Enemy spawning: At a certain distance away from the base there will be a zone with a certain width and height. For this example its 100x100. Every zone will have an list which contains enemies which it will spawn. After a wave the enemies will get a stronger and the spawners will spawn extra enemies.