zzuegg: > Application → LegacyApplication → SimpleApplication chain comes into mind Would be nice to finally reconcile this somehow during the “clean break” transition. For those not familiar with the history, the intent was to move all/most of the things provided by the original base classes (root nodes, gui nodes, etc.) into AppStates that were included by default (and could therefore be completely left out for apps that didn’t need them or wanted to setup their own.) Using protected fields the way SimpleApplication does has been a constant source of confusion for new users and a maintenance nightmare. (Think of every new user that ever include an entire application in some child class because they didn’t know how to get the ‘magic fields’ otherwise.) It made writing quick demo code less verbose but at the expense of not really teaching anything. Worth considering finally reconciling all of that and (at worst) leaving SimpleApplication around as a backward compatibility layer or something. (Even the name of that class has caused problems.)