Inventory Bug or Ryzom one ?
Added by Nepherkaan about 9 years ago
<pet_animal3>
 <item slot="2" q="1">tp_kami_the_sunken_city.sitem</item>
 <item slot="3" q="1">tp_kami_frahartowers.sitem</item>
 <item slot="4" q="12850">tp_kami_outlawcanyon.sitem</item>
 <item slot="5" q="28257">tp_kami_fleetinggarden.sitem</item>
 <item slot="6" q="1">tp_kami_restingwater.sitem</item>
 <item slot="7" q="1">tp_kami_forbidden_depths.sitem</item>
 <item slot="8" s="2" q="1">tp_kami_the_abyss_of_ichor_matis.sitem</item>
 <item slot="9" q="1">tp_kami_the_elusive_forest.sitem</item>
 <item slot="10" s="2" q="1">tp_kami_the_under_spring_fyros.sitem</item>
</pet_animal3>
I don't remember clicking 41000 times to buy a ticket ^^.
Replies (7)
    
    RE: Inventory Bug or Ryzom one ?
    -
    Added by vl about 9 years ago
  
  Hello, please give us the id/slot to be able to check that
    
    RE: Inventory Bug or Ryzom one ?
    -
    Added by Nepherkaan about 9 years ago
  
  I've checked, IG, not the same count.
    
    RE: Inventory Bug or Ryzom one ?
    -
    Added by Nepherkaan about 9 years ago
  
  <uid>121343</uid>
<slot>0</slot>
<cid>1941488</cid>
    
    RE: Inventory Bug or Ryzom one ?
    -
    Added by namine about 9 years ago
  
  I think q refers to quality and not quantity (which is s).
And quality is not displayed IG for TPs.
    
    RE: Inventory Bug or Ryzom one ?
    -
    Added by Nepherkaan about 9 years ago
  
  That's right!
Even vl falls in ^^.
So, no 'q' for ticket (useless), and a 's' even for one ticket ?
    
    RE: Inventory Bug or Ryzom one ?
    -
    Added by arc almost 9 years ago
  
  I think this might be the bug why we sometimes ingame get 2 different stacks for the "same" ticket.
It's appearently not the same but one is Q1 and the other Q12850. And the game groups/stacks them accordingly.
Explains alot to me right now. Only question left, where do the odd Qualities come from :)
    
    RE: Inventory Bug or Ryzom one ?
    -
    Added by vl almost 9 years ago
  
  Indeed, there's perhaps an obscure bug somewhere in the server code.
We'll investigate it.
(1-7/7)