Project

General

Profile

Bug #2202

effectinfo.EffectString and effectinfo.NumEffectStrings not working correctly

Added by Kranok 4 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
vbulletin_issue_id:

Description

ISXEQ2 v20220210.0001

Seems to be any effect (Beneficial or Detrimental). I'll use "Membership Benefit" as an example:

echo ${Me.Effect[Query, MainIconID == 955].IsEffectInfoAvailable}

FALSE

echo ${Me.Effect[Query, MainIconID == 955].IsEffectInfoAvailable}

TRUE

echo "${Me.Effect[Query, MainIconID == 955].ToEffectInfo.Name} - ${Me.Effect[Query, MainIconID == 955].ToEffectInfo.Description} - ${Me.Effect[Query, MainIconID == 955].ToEffectInfo.NumEffectStrings}"

Membership Benefits -  - 327680

echo "${Me.Effect[Query, MainIconID == 955].ToEffectInfo.EffectString[1]}"

*hangs*

 

The empty string for "Description" is correct and seems to work correctly for other buffs/detriments.  Here, NumEffectStrings is 327680, or (0x50000).  The actual number should be 5.  However, even if you already know that, accessing one either gives random data, or hangs the client.

#1

Updated by Amadeus 4 months ago

  • Status changed from New to Feedback Required
  • Assignee set to Amadeus

I believe that it should be fixed in version 20220210.0002.

#2

Updated by Kranok 4 months ago

Amadeus wrote:

I believe that it should be fixed in version 20220210.0002.

Confirmed, thanks Amadeus.  Works correctly in the updated version.

#3

Updated by Amadeus 4 months ago

  • Status changed from Feedback Required to Resolved

Also available in: Atom PDF