Everyone always mentions that people do not read documentation. This is also the case for us as game developers. So what can we do about that? First, it is important not to force everyone to read pages and pages of documentation. Usually, only programmers and other technical folks go through all the effort of reading up on functionality. So what about artists, and designers? Thankfully, solutions already exist: Gyms, Zoos, and Museums. Let’s look at examples, see how they work, how they can be built, and how they improve the development of your games.
- Welcome to GodotFest!/
- Talks & Workshops/
- Gyms, Zoos, and Museums: Your documentation should be in-game/
Gyms, Zoos, and Museums: Your documentation should be in-game
Talk
Godotfest25
25 minutes
English
This session will be recorded
Related
A Peek Under the Hood: Technical Learnings from Halls of Torment
Talk
Godotfest25
Art Direction Crash Course (for non-artists)
Talk
Godotfest25
Beyond the Loop: A Primer on Interactive Music in Godot
Talk
Godotfest25
Building Robust Godot Games with GdUnit4 & GdUnit4Net
Talk
Godotfest25
Building Starfinder: Professional Godot at Scale
Talk
Godotfest25
Collaborative Game Development with Godot: From Studio Model to Community-Built Games
Talk
Godotfest25
Don't ship the wrong game!
Talk
Godotfest25
From Theora to AV1: Transforming Video Workflows in Godot 4
Talk
Godotfest25
GdUni4 live demo + technical overview
Talk
Godotfest25
