[DiscordArchive] Need help debugging a client crash. I know it's...
[DiscordArchive] Need help debugging a client crash. I know it's...
Original source
rektbyfaith
01-07-2025, 03:58 AM #1Archived author: Needle • Posted: 2025-01-07T03:58:16.634000+00:00
Original source
Original source
Thread automatically created by Ninjapleez in <#415944535718494208>
rektbyfaith
01-07-2025, 03:58 AM #2Archived author: Needle • Posted: 2025-01-07T03:58:17.157000+00:00
Original source
Thread automatically created by Ninjapleez in <#415944535718494208>
Original source
The crash occurs on 3.3.5a when calling GetCritChanceFromAgility() or GetSpellCritFromIntellect() on any warlock pet on a specific server.
My best guess so far is that those built-in API functions are expecting some value(s) to be non-null or in a specific range, and an assert is failing, prompting a crash. What I haven't been able to figure out yet is which values are bad.
The server doesn't seem to store or send any specific values related to crit. It seems like it does the calculations to determine what crit chance is on the fly any time it's needed. I haven't been able to find any other related values that seem out of line. For example, Int and Agility seem to be at expected values both on client and server side.
rektbyfaith
01-07-2025, 04:02 AM #3Archived author: Ninjapleez • Posted: 2025-01-07T04:02:28.526000+00:00
Original source
The crash occurs on 3.3.5a when calling GetCritChanceFromAgility() or GetSpellCritFromIntellect() on any warlock pet on a specific server.
My best guess so far is that those built-in API functions are expecting some value(s) to be non-null or in a specific range, and an assert is failing, prompting a crash. What I haven't been able to figure out yet is which values are bad.
The server doesn't seem to store or send any specific values related to crit. It seems like it does the calculations to determine what crit chance is on the fly any time it's needed. I haven't been able to find any other related values that seem out of line. For example, Int and Agility seem to be at expected values both on client and server side.
Original source
Everything else about warlock pets seems fine. They perform as expected in combat and nothing seems out of line about any of their stats or other properties.
This crash doesn't occur on hunter pets, however. It also occurs on DK ghoul pets, but only the talented permanent version.
rektbyfaith
01-07-2025, 04:11 AM #4Archived author: Ninjapleez • Posted: 2025-01-07T04:11:32.707000+00:00
Original source
Everything else about warlock pets seems fine. They perform as expected in combat and nothing seems out of line about any of their stats or other properties.
This crash doesn't occur on hunter pets, however. It also occurs on DK ghoul pets, but only the talented permanent version.
Original source
Use the following code to log the attributes of the warlock pet before calling the crit functions. This will help you identify if any values are out of the expected range.
```local pet = "pet" -- or the specific unit ID for the pet
local agility = UnitStat(pet, 2) -- 2 is the index for Agility
local intellect = UnitStat(pet, 4) -- 4 is the index for Intellect
local critChance = UnitCritChance(pet)
print("Pet Agility: " .. agility)
print("Pet Intellect: " .. intellect)
print("Pet Crit Chance: " .. critChance)```
API Functions:
GetCritChanceFromAgility(): designed to calculate the critical strike chance based on agility. If the server is sending invalid or unexpected values for agility (e.g., negative values, extremely high values, or null), it could lead to a crash when the client tries to process this data.
GetSpellCritFromIntellect(): this calculates spell critical strike chance based on intellect. Again, if the intellect value is invalid, it could cause issues.
i think you mentioned that the same unmodified client does not crash on other servers, compare the output of the above code on both the crashing server and a non-crashing server. Look for discrepancies in agility, intellect, and crit chance.
i have 0 exp with your issue i just looked things up for few hours lol. hope it helps!
rektbyfaith
01-08-2025, 08:18 AM #5Archived author: Exced™ • Posted: 2025-01-08T08:18:54.807000+00:00
Original source
Use the following code to log the attributes of the warlock pet before calling the crit functions. This will help you identify if any values are out of the expected range.
```local pet = "pet" -- or the specific unit ID for the pet
local agility = UnitStat(pet, 2) -- 2 is the index for Agility
local intellect = UnitStat(pet, 4) -- 4 is the index for Intellect
local critChance = UnitCritChance(pet)
print("Pet Agility: " .. agility)
print("Pet Intellect: " .. intellect)
print("Pet Crit Chance: " .. critChance)```
API Functions:
GetCritChanceFromAgility(): designed to calculate the critical strike chance based on agility. If the server is sending invalid or unexpected values for agility (e.g., negative values, extremely high values, or null), it could lead to a crash when the client tries to process this data.
GetSpellCritFromIntellect(): this calculates spell critical strike chance based on intellect. Again, if the intellect value is invalid, it could cause issues.
i think you mentioned that the same unmodified client does not crash on other servers, compare the output of the above code on both the crashing server and a non-crashing server. Look for discrepancies in agility, intellect, and crit chance.
i have 0 exp with your issue i just looked things up for few hours lol. hope it helps!
Original source
This is ChatGPT output. UnitCritChance does not exist in the WoW API. Also, as I've mentioned, I've already checked every pet stat and everything accessible through the API is within expected ranges, aside from the two available non-player crit functions, which are crashing.
rektbyfaith
01-08-2025, 08:37 AM #6Archived author: Ninjapleez • Posted: 2025-01-08T08:37:04.017000+00:00
Original source
This is ChatGPT output. UnitCritChance does not exist in the WoW API. Also, as I've mentioned, I've already checked every pet stat and everything accessible through the API is within expected ranges, aside from the two available non-player crit functions, which are crashing.
Original source
there are few github mentions i was able to grab that from it nothing specific about your issue tho. don't gpt limit coding for legal purpose? xD
that said i have no idea how to assist more since you checked everything else at least that's working.
rektbyfaith
01-08-2025, 08:45 AM #7Archived author: Exced™ • Posted: 2025-01-08T08:45:51.237000+00:00
Original source
there are few github mentions i was able to grab that from it nothing specific about your issue tho. don't gpt limit coding for legal purpose? xD
that said i have no idea how to assist more since you checked everything else at least that's working.
Original source
Please stop clogging my thread with GPT output and terrible defenses of GPT output. It is blatant. It is unhelpful. It actively detracts from the likelihood I actually receive help.
rektbyfaith
01-08-2025, 08:49 AM #8Archived author: Ninjapleez • Posted: 2025-01-08T08:49:02.005000+00:00
Original source
Please stop clogging my thread with GPT output and terrible defenses of GPT output. It is blatant. It is unhelpful. It actively detracts from the likelihood I actually receive help.
Original source
i dont care if its gtp i was trying to help you need to relax brothern. like i said it was copied and i dont have exp in it as stated so wasnt sure if its near correct.
rektbyfaith
01-08-2025, 09:06 AM #9Archived author: Exced™ • Posted: 2025-01-08T09:06:18.062000+00:00
Original source
i dont care if its gtp i was trying to help you need to relax brothern. like i said it was copied and i dont have exp in it as stated so wasnt sure if its near correct.
Original source
do you have access to the server source code or not ?
rektbyfaith
01-08-2025, 03:39 PM #10Archived author: Titi • Posted: 2025-01-08T15:39:18.381000+00:00
Original source
do you have access to the server source code or not ?
1 Guest(s)
1 Guest(s)