Apparently Blizz changed their ids again for 5.0.12 patch. It did simplify some of the overlap from their previous 5.0.12 ids at least.
I also changed the exe path to use the GAME_EXE_PATH config value, as this value is set using the user-entered path (defaults to the newest version otherwise). Without this fix, ocraft is hardcoded to the newest version only.
Apparently Blizz changed their ids again for 5.0.12 patch. It did simplify some of the overlap from their previous 5.0.12 ids at least.
I also changed the exe path to use the GAME_EXE_PATH config value, as this value is set using the user-entered path (defaults to the newest version otherwise). Without this fix, ocraft is hardcoded to the newest version only.