It wouldn't really be that hard to write a description function for the actual keybindings and hook it into the token parser. All you'd have to do is pass the function the name of the KeyBinding via the replacement token, get the keybinding from NoxicoGame and return the the key name as a string.
Also, as a minor suggestion, would you be willing to rebind the menu button to ESC? I probably should have brought this up earlier, but I've always found it a bit weird that the menu is assigned to F1 considering that it's usually reserved for help functions. I just think that setting it to ESC would probably help to reduce confusion for first time users as it's the defacto menu button in most games.
Fullscreen is indeed slow. I think it's because of the scaling filter. To be honest, you're not supposed to maximize, but I'll see if I can force it to draw without filtering like that.
The tutorial doesn't account for keymaps. It'd be a bit of a hack to add such a thing, but I suppose it could be done...
Things I noted: 1. When calculating transitions from day to night, for instance in a bed, it goes very slow on "full screen" but as soon as I shrink it to its normal size it runs just fine.
2. The key bindings are different than from the "tutorial". I eventually figured out what they were in full extent by going to the menu. Personally I would like it if the menu key was listed on a sidebar or something, somewhat permanently, as F1 is a non-standard key-press.
