Second Hotfix is Live! (v1.0.2) (Mid-Chapter Event Input Lock Fixes)
Hey everyone!
Second hotfix is now live, and this one is focusing on smoothing out the experience for anyone affected by "losing control" after a mid chapter event triggers (reinforcements, talk events, etc). If you've ever gotten into the state where you could move the camera around, but couldn't click on any units after a mid chapter event, this is the patch for you!
Basically what was happening is during certain events, sometimes I'm assuming a certain character would be on the map. During mid-chapter events, player in put is disabled, and if an exception gets thrown for any reason, the code to return control to the player is not executed. Illyana in chapter 2 for example when the reinforcements come will have the camera pan to her, but if she's dead, that code will throw an error, and player input is not re-enabled!
This has now been fixed for every event in the game. I've wrapped every single event in a try/catch block, and on catching any errors, the event will simply end, and I will re-enable player input. The underlying exception will still be there, so I will continue looking into those, but at the minimum you should be able to continue playing through the chapter.
My main priorities right now are:
1. Making saves sacred. Right now there is one main issue that is causing ripple effects throughout the game, and that is the lack of proper resets on the cached version of a save. In simple terms, when you hit the "Main Menu" button in battle, or get the game over screen, and restart the battle from the main menu, some parameters aren't reset correctly, causing things like keeping your rewards from any chests you opened, doubling items, keeping exp gain, etc. I believe this is also the cause of some other things such as. I've been able to reproduce this somewhat consistently, and I'm hoping to get a fix for it out ASAP. I'm going to spend all of today solely on this issue because I think it'll fix a lot of strange behavior people are seeing. IN THE MEANTIME: I would recommend if you're going to restart a chapter, completely close the game and re-open and then restart to ensure the cached save is properly deleted. You shouldn't have to do this, but it's the best way to avoid this bug until I fix it.
2. Making sure you do not lose progress while you're playing a chapter due to a bug/game freezing. Still have a couple of these to iron out (like poison killing an enemy with a droppable item).
Thank you all for your extreme levels of patience. My goal is to get all of these ironed out by the weekend when most people will have the time to be opening up the game. If you experience a loss of any items/characters and would like me to look at the save, please grab the save file, the player.log, and the player-prev log and send them to me at [email protected] and I can try to manually edit to fix any issues you have!
Local save location: C:\Users\{your_username}\AppData\LocalLow\eBrothers LLC\Those Who Rule\thoseWhoRuleSaveFinalV1_{X}.es3 (Where 'X' is the save slot, 0 if it's a mid-battle "continue save").
Local Player.log and Player-prev.log location: C:\Users\{your_username}\AppData\LocalLow\eBrothers LLC\Those Who Rule\Player.log AND Player-prev.log
Again, thank you all so much for your patience if you've experienced these. I will continue to work to get them ironed out ASAP.
Best,
Eldin T.
Second hotfix is now live, and this one is focusing on smoothing out the experience for anyone affected by "losing control" after a mid chapter event triggers (reinforcements, talk events, etc). If you've ever gotten into the state where you could move the camera around, but couldn't click on any units after a mid chapter event, this is the patch for you!
Basically what was happening is during certain events, sometimes I'm assuming a certain character would be on the map. During mid-chapter events, player in put is disabled, and if an exception gets thrown for any reason, the code to return control to the player is not executed. Illyana in chapter 2 for example when the reinforcements come will have the camera pan to her, but if she's dead, that code will throw an error, and player input is not re-enabled!
This has now been fixed for every event in the game. I've wrapped every single event in a try/catch block, and on catching any errors, the event will simply end, and I will re-enable player input. The underlying exception will still be there, so I will continue looking into those, but at the minimum you should be able to continue playing through the chapter.
My main priorities right now are:
1. Making saves sacred. Right now there is one main issue that is causing ripple effects throughout the game, and that is the lack of proper resets on the cached version of a save. In simple terms, when you hit the "Main Menu" button in battle, or get the game over screen, and restart the battle from the main menu, some parameters aren't reset correctly, causing things like keeping your rewards from any chests you opened, doubling items, keeping exp gain, etc. I believe this is also the cause of some other things such as. I've been able to reproduce this somewhat consistently, and I'm hoping to get a fix for it out ASAP. I'm going to spend all of today solely on this issue because I think it'll fix a lot of strange behavior people are seeing. IN THE MEANTIME: I would recommend if you're going to restart a chapter, completely close the game and re-open and then restart to ensure the cached save is properly deleted. You shouldn't have to do this, but it's the best way to avoid this bug until I fix it.
2. Making sure you do not lose progress while you're playing a chapter due to a bug/game freezing. Still have a couple of these to iron out (like poison killing an enemy with a droppable item).
Thank you all for your extreme levels of patience. My goal is to get all of these ironed out by the weekend when most people will have the time to be opening up the game. If you experience a loss of any items/characters and would like me to look at the save, please grab the save file, the player.log, and the player-prev log and send them to me at [email protected] and I can try to manually edit to fix any issues you have!
Local save location: C:\Users\{your_username}\AppData\LocalLow\eBrothers LLC\Those Who Rule\thoseWhoRuleSaveFinalV1_{X}.es3 (Where 'X' is the save slot, 0 if it's a mid-battle "continue save").
Local Player.log and Player-prev.log location: C:\Users\{your_username}\AppData\LocalLow\eBrothers LLC\Those Who Rule\Player.log AND Player-prev.log
Changelog
- Fix: Full pass on all reinforcement events, and any other mid-chapter events to add safety net for exceptions that could disallow player input. On any issues, the game will fallback to code that returns control to the player. This should fix the issue of people still being able to move the camera, but no other input being allowed, essentially freezing the game. It should also fix when conversations come up mid battle, and you lose input controls. Please report if you still experience any of these issues after the update.
- Fix: Game no longer freezing in chapter 2 on reinforcements if Illyana is dead.
- Fix: Dialogue panel fix in a particlar chapter 13 base conversation.
- Fix: Incorrect labelling of certain chapter 13 base conversations as side quests.
- Fix: Fixed text in Fencer's lunge ability.
- QoL: Default difficulty that shows up at the start of a new game changed from "Veteran" to "Normal".
- QoL: Small tweaks to Indomnitable and Drakkar's Idol ability text to better reflect their reliance on combat.
- Balance: Chapter 7, while meant to be a difficulty spike, is proving a little more challenging than I planned. Reduced the average level of enemies by 1. Replaced the Steel Bows of Longbowman with Iron Bows. Also slight manual nerfs to particular enemies in difficulties other than veteran. Hope this makes the level feel a bit more fair. It's tough to straddle the line of challenging, but fun. I hope this change gets it a little closer to the middle. Please let me know what you think after trying out the changes! You will have to hit "Restart Chapter" to get the new changes.
Again, thank you all so much for your patience if you've experienced these. I will continue to work to get them ironed out ASAP.
Best,
Eldin T.