Kingdom Come: Deliverance Message Board  

Only one, people are perhaps reporting without fully testing?

Seeing how the patch did not update WHGame.dll (The Cry-Engine .dll files, here bundled together as a singular file.) nor KingdomCome.exe

Scripts.pak, GameData.pak and Developer.pak that's about it, system.cfg too since it contains the version number the game displays and whdlversions.txt as a collection of version numbers for different parts of the game.

Sorry guys, I'm in the cloister so I've been unable to test everything, some stuff work like no weight, but other stuff doesn't. That is unless there is a script that's preventing me from having groschen in the cloister. Just ignore me, not in the best position to say.

[Edited by Dancid, 2/20/2018 2:04:03 PM]

Could be that part of it is due to changes to the asset script files perhaps and not from code changes in the exe or .dll files, Cry-Engine does doe a lot via scripting far as I know but I wouldn't expect the trainer to be affected by that but I guess it can be depending on how the developers have put it all together.

I have tested the following with the 1.2.2 trainer on 1.2.5: Health, Stamina, Weight, Inf Arrows. All work without issue. Hope this helps to clear up the situation regarding stamina and weight.

Now that I'm out of the cloister, I Can confirm that everything works except unlimited horse stamina. I've actually never gotten that one to work even prior to the patch. 😢

Yeah.. everything works besides Horse Stamina, which never worked in the first place.. so why are there 17 update requests and someone spent 5k on a priority update? Odd.

I;d honestly just hold off 0x90. Patch 1.3.0 is suppose to be coming out in a few days or next week anyways.

[Edited by Grubbs008, 2/21/2018 12:25:43 AM]

I thought there were 2 different versions, a retail one and a steam one (and then the GOG one coming out soon), so I thought both versions utilized different files, which might be the reason it works for some and not for others?

I could of course be entirely wrong.

So today they reverted the patch. I'm back at 1.2.2 now.