Recent Posts81
User Mods / Re: Whore Master 7
« Last post by big fan of fans on November 20, 2022, 05:06:25 AM »I believe I have found two bugs and a fix for one, although I don't have a github or discord. The first bug is likely caused by line 176 of "src/game/cGirls.cpp".
The line in question is in a function that handles girls leveling up and reads:
"int chance = g_Dice % 12;"
I believe that it is supposed to actually be:
"int chance = g_Dice % 11;"
The line is there to generate a random index for the statically created array on the line before. The array contains eleven fixed traits, meaning its indices range from 0 to 10, however the line as it is currently written can instead occasionally generate an index of 11. This makes the bug unreliable to reproduce, as it only happens when a girl levels up to a level divisible by five so she can gain a new trait, but even then only in a little more than one twelfth of the times. When encountered, this bug manifests as the player getting an error message that looks something like this, although substitute arena for any building the girl leveled up in:
"Error when processing building Arena: Could not find trait:" and then some random gibberish.
This is likely happening because the trait array is going out of bounds and trying to read this memory space as a trait, which will obviously not generally produce any meaningful text, nor anything usable to the gain_trait function a few lines down from it. The process buildings phase will then fail for that turn, and the girl will not get a trait for that level. I have reproduced the error for both the previous version, as well as the new version that was posted yesterday. It is hard to be absolutely certain that it fixes it due to the random nature of the bug, but I have not encountered the bug after compiling a version of the game with the above change.
The second bug is the one that I have not explored the cause of and is related to the UI. When the user selects a girl and then clicks the "girl details" button at the right of the screen, they enter into a menu with a button that reads "more details" on the left side of the screen. In older builds, clicking on the button would cycle through several different stats on the left half of the screen, before wrapping back to the original stats. Now, after clicking on it twice, it will produce an error message that reads: "Could not find trait". Then, bits of text from some scripts will show in place of the error text on the red box before finally kicking the user out of the "girl details" menu. The player will then be unable to enter the "girl details" menu again until restarting the game, with the player instead getting only the "Could not find trait" error message any time they try to enter the menu.
Anyway, thanks for the mod, it really improved the game's overall codebase, especially in a lot of ways that are really nice but invisible to the overall player.
Edit:
Alternatively, looking at the commit history for the first section it seems that part was originally supposed to be in a switch with a chance to not produce a trait when it rolled 0. If this original behavior was intended, the lines below can instead be modified by sticking them in an if statement that only runs if it didn't roll 11.
The line in question is in a function that handles girls leveling up and reads:
"int chance = g_Dice % 12;"
I believe that it is supposed to actually be:
"int chance = g_Dice % 11;"
The line is there to generate a random index for the statically created array on the line before. The array contains eleven fixed traits, meaning its indices range from 0 to 10, however the line as it is currently written can instead occasionally generate an index of 11. This makes the bug unreliable to reproduce, as it only happens when a girl levels up to a level divisible by five so she can gain a new trait, but even then only in a little more than one twelfth of the times. When encountered, this bug manifests as the player getting an error message that looks something like this, although substitute arena for any building the girl leveled up in:
"Error when processing building Arena: Could not find trait:" and then some random gibberish.
This is likely happening because the trait array is going out of bounds and trying to read this memory space as a trait, which will obviously not generally produce any meaningful text, nor anything usable to the gain_trait function a few lines down from it. The process buildings phase will then fail for that turn, and the girl will not get a trait for that level. I have reproduced the error for both the previous version, as well as the new version that was posted yesterday. It is hard to be absolutely certain that it fixes it due to the random nature of the bug, but I have not encountered the bug after compiling a version of the game with the above change.
The second bug is the one that I have not explored the cause of and is related to the UI. When the user selects a girl and then clicks the "girl details" button at the right of the screen, they enter into a menu with a button that reads "more details" on the left side of the screen. In older builds, clicking on the button would cycle through several different stats on the left half of the screen, before wrapping back to the original stats. Now, after clicking on it twice, it will produce an error message that reads: "Could not find trait". Then, bits of text from some scripts will show in place of the error text on the red box before finally kicking the user out of the "girl details" menu. The player will then be unable to enter the "girl details" menu again until restarting the game, with the player instead getting only the "Could not find trait" error message any time they try to enter the menu.
Anyway, thanks for the mod, it really improved the game's overall codebase, especially in a lot of ways that are really nice but invisible to the overall player.
Edit:
Alternatively, looking at the commit history for the first section it seems that part was originally supposed to be in a switch with a chance to not produce a trait when it rolled 0. If this original behavior was intended, the lines below can instead be modified by sticking them in an if statement that only runs if it didn't roll 11.
