Home | What IS Qodot? | Setting Up Your Project | The Game Manager Autoload | What's an Entity? | Base Classes and Property Definitions | Solid Entities | Point Entities, Part 1 | Point Entities, Part 2 | Game Configuration | Forge Game Data | Textures! | Finally. TrenchBroom. | Building the QodotMap | Helpful Resources | Frequently Asked Qodots
Qodot extends the Godot editor to import Quake .map files, and provides a data-driven framework for converting the entities and brushes contained therein into a custom node hierarchy.
I know you all came here to learn more about entities but I think it's best to get the right headspace for what Qodot actually does and what it doesn't do. That way we can better understand how to work with it to make our games, and not fall into disappointment or frustration over misunderstandings.
Qodot is, at its core, an interpreter.
Qodot will not make your game for you. Qodot does not make doors, it does not make players, it does not make buttons.
It comes with a set of example entities and FGD, but these are better viewed as what they were intended: examples to show you what you can do with Qodot. This guide will help you learn how to create your own that work for your specific game needs.
Qodot does not compile maps into BSPs. It has no concept of vis, no concept of lit, no concept of bsp. It will not automatically cull faces and sort out occlusion for you. Godot does not work like the early BSP engines. You cannot use Qodot to map for Godot the same way you map for Quake.
This is not a weakness of the plugin. This is a strength. What you map is what you get. This makes it more reliable than a compiled BSP, since you get to choose what faces get culled and how your collision is generated. This guide will help teach you how to take advantage of this.
Qodot builds maps by parsing through map files that use the Quake 1 or Half-Life 1 formatting. It does this through a combination of understanding brush construction and Entity Definition resources. What you put in is what you get out.
Understanding this concept will hopefully put you on the right path forward to being able to use this wonderfully flexible tool to make some incredible games.
Home | What IS Qodot? | Setting Up Your Project | The Game Manager Autoload | What's an Entity? | Base Classes and Property Definitions | Solid Entities | Point Entities, Part 1 | Point Entities, Part 2 | Game Configuration | Forge Game Data | Textures! | Finally. TrenchBroom. | Building the QodotMap | Helpful Resources | Frequently Asked Qodots