Reckfell Engine 1.0.0 manual
First project, complete 2D/3D examples, API lookup and development task routes.
Where to start
This manual covers Reckfell Engine 1.0.0. Choose a task, perform it in a small project and check the result. The RU/EN switch opens the corresponding translation of the page; it does not change your game language.
| Your task | Open | Result |
|---|---|---|
| Create a first project | Quick start | A saved project with a visible object, camera and light |
| Understand names and structure | Introduction to Reckfell | Distinguish Entity, level, prefab and resource |
| Learn engine C# workflows | First steps | A script, input, signals and instantiation |
| Build a complete 2D game | First 2D game | Player, enemies, collisions, score and restart |
| Build a complete 3D game | First 3D game | Movement, jumping, enemies and round restart |
New to programming? Start with the beginner route. Used other game engines? Go to key concepts, then choose the task you need.
Solve a problem in your project
| What you need | Where to look |
|---|---|
| Choose a physics body and configure collisions | Physics |
| Handle keyboard, mouse or controller input | Input |
| Create menus and arrange controls | UI |
| Create repeated objects | Prefabs and instances |
| Store player settings and progress | Save data |
| Translate the game and switch languages | Localization |
| Identify a slow frame | Performance |
| Prepare a game for distribution | Export |
Find the exact API
Search for a type or call, such as CharacterBody3D, Entity.GetEntity<T>() or new Vector3(1, 2, 3). In an API result, follow the overload you need: the same method name does not imply the same arguments.
Reading the C# reference explains signatures, required and optional parameters and links to specific members. If an example name cannot be found, check the example language and engine version.
Check results step by step
First run an example with the stated object names, files and settings. Confirm its result before changing one part at a time. When something fails, record the action, first error and engine version. Troubleshooting helps separate C# errors, missing resources, input and physics problems.