A game's code is supposed to have its own error type (that can wrap over ggez::GameError) but you are forced to unwrap/expect all your errors in EventHandler's draw and update methods (because you can't turn them into GameError), right? Is this documented somewhere?

Related to ggez/ggez#421

I don't know if this is the right place to put this, but I can't think of a better one.
The wiki page on RAM often uses an ellipsis instead of having a description, seemingly with varying meaning.
For example, the 03FFC range. What does it do? I can't seem to find info on it anywhere, and the only thing about it on the page is this:
`| 03FFC | ...

Server say chat doesn't work with Steam CS Beta Client.
It only print the letter "s" in the chat.

This apply to autoexec config such as the LIVE for war server and so on...

I have no idea if RegameDLL have this bug.

CodeFactor found multiple issues:

Complex Method

src\CollisionDetector.cpp:74-155

Redundant blank line at the start of a code block should be deleted.

[testsrc\EntityContainerTest.cpp:169
](https://www.codefa

It would be very useful to have a few snippets with a step by step tutorial on how to create a new project. It would allow a quicker intro/adoption to LDK.

Maybe a wiki page, or just adding something to the README would be enough. No need for complicated stuff, just a few lines of code and a description of necessary steps to have a window drawing something.

Wiki pages that needs to be written:

How to make a game with Bubba-3D

• Project setup Linux
• Project setup Windows
• Render your first mesh
• Make your gameobject move
• Control your gameobject
• Collision detection and response
• Handling input
• Add configuration for new controller
• 2D UI tutorial

How to extend Bubba-3D

• How to write tests
• As a