{"id":78,"date":"2025-08-11T21:18:15","date_gmt":"2025-08-11T21:18:15","guid":{"rendered":"https:\/\/blogs.scummvm.org\/prime\/?p=78"},"modified":"2025-08-11T21:18:15","modified_gmt":"2025-08-11T21:18:15","slug":"week-10-queen-and-pink-engines","status":"publish","type":"post","link":"https:\/\/blogs.scummvm.org\/prime\/2025\/08\/11\/week-10-queen-and-pink-engines\/","title":{"rendered":"Week 10: Queen and Pink Engines"},"content":{"rendered":"

This week I worked on adding keymapper support to the Queen<\/strong> and Pink<\/strong> engines. On top of that, I also got my Neverhood<\/strong><\/a>, Prince<\/strong><\/a>, and Queen<\/strong><\/a> keymapper PRs merged.<\/p>\n

\n

Queen Engine<\/h3>\n

The Queen engine was moderately challenging<\/strong>. It came with a good number of keys, but the real twist was the variable keybinds<\/strong> for some actions. these depended on the language of the player\u2019s copy of the game. This was somewhat similar to what I encountered earlier in the Sherlock engine.<\/p>\n

Another tricky part was that the keybind selection logic<\/strong> was embedded deep in the engine code. To make it compatible with the keymapper, I had to refactor the code<\/strong> so that the language-based key selection happened in the keymapper section instead. This made it accessible for usage in the keymapper initialization.<\/p>\n

Some sections of the game also needed keymapper toggling. <\/strong>those were relatively straightforward to set up.<\/p>\n

\n

Pink Engine<\/h3>\n

Pink, at first glance, seemed simpler<\/strong>\u2014fewer than 10 keys in total. But as always, appearances can be deceiving.<\/p>\n

In the game, you can\u2019t move your character freely. Movement only happens when you click an interactable object or character, at which point the character walks to the target and interacts with it automatically.<\/p>\n

The key actions didn\u2019t just trigger standard gameplay\u2014they altered this entire interaction sequence<\/strong>. For example:<\/p>\n