Combuctor (native Bagnon)

Combuctor (native Bagnon)

2M Downloads

Bag slots scrambling placement

Thrumbar opened this issue ยท 10 comments

commented

Items in bags scramble up messing up order I placed them in requiring RL to fix . Others are leaving comments on Curse about this as in the following

"I'm also getting the same bug with bags re-ordering themselves and as a post below says, it seems to be the last three bags.

They seem to re-order themselves when you take a portal / enter/leave a dungeon.

If after a portal you do a /reload then it seems to order properly again."

commented

They seem to re-order themselves when you take a portal / enter/leave a dungeon.

Anything like that it seems, I'm getting it on hearthstone & on engineering transporter devices.
Edit: oh, also, infrequently, opening bags draws some contents at random(ish) places outside the container boundary after taking a portal etc.

commented

Same thing here...scrambling of all the items in the bas... :/

commented

i have placement bug too
4 x 30 slot bags
video https://youtu.be/2ww2EAqWTsE

commented

Completely new codebase makes this a deprecated issue.

commented

Does the issue remains with the latest version, 5.3.1?

commented

yes, @Jaliborc ,the issue remains with the latest version, 5.3.1

I am a Chinese players
and When I was just coming into the game,
I received this information:

Message: Interface\AddOns\Combuctor\main.lua:279: bad argument #1 to 'pairs' (table expected, got nil)
Time: 07/17/13 08:45:23
Count: 5
Stack: [C]: in function pairs' Interface\AddOns\Combuctor\main.lua:279: in functionUpdateFrames'
Interface\AddOns\Combuctor\events\itemFrame.lua:99: in function `method'
Interface\AddOns\Combuctor\events\itemFrame.lua:24: in function <Interface\AddOns\Combuctor\events\itemFrame.lua:21>

Locals: (_temporary) = nil
(_temporary) = "table expected, got nil"
= defined =[C]:-1

commented

That is another unrelated issue. I mean the scrambling, does it persists?

commented

@Jaliborc ,yes,it persists.

commented

This issue still persists as of the latest patch. If I recall correctly, it appeared with the advent of CRZ. I'm not sure if this is a latent bug in the client that Combuctor should take a pro-active measure to fix, or if it's a latent bug in Combuctor because of the change in the API.

Either way, is there any interest from Tuller or Jaliborc in fixing this? If not, will a patch be accepted if I can find and fix the issue?

commented

Patches should always be accepted.