Jump to content

  •  

Bug Tracker Migration

June 3rd
Good news everyone! The staff has decided that it is time to slowly kill off this Bug Tracker. We will begin the process of slowly migrating from this Bug Tracker over to our Github Issues which can be found here: https://github.com/HerculesWS/Hercules/issues

Over the next couple of days, I will be closing off any opportunity to create new reports. However, I still will keep the opportunity to reply to existing Bug Reports. Doing this will allow us to slowly fix any bug reports we have listed here so that we can easily migrate over to our Issue Tracker.

Update - June 7th 2015: Creating new bug posts has been disabled. Please use our https://github.com/HerculesWS/Hercules/issues tracker to post bugs. Users are still able to reply to existing bug posts.

- Administration

Issue Information

  • #007142

  • 0 - None Assigned

  • Unable to Fix

Issue Confirmations

  • Yes (0)No (0)
Photo

BuyingStore Closed by @refresh

Posted by Zopokx on 01 April 2013 - 01:59 AM

If you use @refresh when you have your BuyingStore open, it will be immediately closed, unlike it happens with a regular vending shop.

I haven't tested it with @autotrade.

Ind 
changed status to: Confirmed
changed status to: Fixed

actually, not fixed yet. found a bug in the bug o__o XDD paradox

actually, not fixed yet. found a bug in the bug o__o XDD paradox


xDDD I'm laughing so hard right now because of you.

BTW, I hope this new bug^2 won't be too much difficult to fix :)

Ind 
changed status to: Unable to Fix

The problem is that creating it would crash the client (the client is poorly coded at this I guess, trying to tell it to output the window again makes it crash), I tried to get around the issue in many ways e.g. by telling the client the character buying store closed, and then trying to send it to create a new one with same items as the previous -- it would still crash. Had to revert in https://github.com/H...168e079f59fac6e

No problem if this is fault of the damn client (I dream with an open sourced new one :P)

But it is neccesary to know this issue, mainly because possible usage of @refreshall.

huum fair point o-o didn't think about @refreshall -- whats the point of that anyway? -- uhm depending on its use we could add a check on refreshall not to refresh people with buyingstores

Maybe in a event, a GM decide to use @refreshall and every buyingstore in game stops suddenly. (In fact, that was my concern about in the beginning...)

As I said before, I didn't tested with @autotrade (BuyingStore works with @at, isn't it?).

it will close the ones with autotrade too i think

This issue's state should be changed, shouldn't it?