Hollow Knight is mainly characterized by dual-purpose design and general minimalism. A particular feature is the use of fluid builds based on charms that can be (un)equipped rather than a skill tree. However, changing builds can be too much blind trial and error while experience becomes too abundant too early in the game. One solution to this could be requiring the user to pay with experience when (un)equipping charms.
2008 – Tales of Design & User Experience 