A week ago I was working with a group of 32 semi-active alpha testers, now over 2000 beta testers have signed up to try Robo Instructus. I've already received a lot of great feedback that will help improve the game. Thanks very much to everyone that sent in their thoughts!

One main theme that's coming through is the learning difficulty spike that happens at the 5th level. Improving this, then, is the main objective of beta-1.2. This version adds new levels & reworks some to spread out the cognitive load of learning the new concepts. It also better explains variable scoping which becomes quite important around this point.

So please try out these new levels and features and let me know what you think. Steam should update the game automatically.

Beta-1.2

New features

• Add new usable tile "power switch" and new level designed to better introduce the robo_use() function in isolation from other new concepts.
• Rework (previously 6th) level to incorporate power switches and location data stores.
• Add "Scope" primer explaining variable scope rules.
• Rework the first level with direction data stores, try to simplify the necessary concepts used here.
• Reorder code reference primer sections to be less confusing.
  

Other changes

• Rework first level tutorial. Remove initial code which can cause confusion.
• Move game speed tutorial to during 2nd level.
• Don't auto increase from speed 1 -> speed 2 after completing first level.
• Fix error sound triggering twice in some cases when the robot falls.
• Fix render bug in title screen after viewing the code reference.
• Linux: Build with older glibc to support Ubuntu 16.04.
• Replace message images with actual in-game renders.
• Fix quoted message display issue.
• Avoid mipmapping where possible to lower VRAM usage.
• Improve company message wording.
• Move loop-III tutorial one level earlier.
  

Feedback

New issues to investigate

• Support more languages #120
• Tutorial about alternate debugging keys #121
• Auto-correct capitalisation errors #122
• Change flow so unlocks happen after scores #123
• Improve hint explaining the program restarts at each level-variant? #125
• Add copy/paste from code reference #126
• buttons clicks sometimes not working #128
• Improve pause code-phase highlight #129
• Investigate jerky performance (texture vram usage?) #130
• Allow custom color themes #131
• Add profile deletion #133
• `if robo_scan() is 1 or 2` error message missing suggestion #134
• Name levels #136
• Intel shadow image render bug #137
• Index for code-reference primer sections #138