Post: #1

I am having a strange problem when buying from or selling items to vendors. I get the proper buy/sell lists and they behave as expected but when I go to "checkout" by clicking "accept" it does nothing. The same also happens if i try to click the "clear" button. Normally your name would appear next to "accept" as if you are signing the bill of sale and the appropriate packet would get sent to the server for processing. None of this happens: no signature and a packet filter hook on packet 0x3b (59) reveals that the packet isn't even sent to the server.

Distance is not the issue as in most cases I am standing either right on top the vendor or within 1 or 2 tiles. If distance was the issue I would still get the signature and a message about not being close enough to the vendor.

Because this problem only recently started (within the past few weeks), I thought maybe it had to do with a recent script change, although none of the script changes had anything to do with vendors. I disabled all custom scripts and only loaded the base with the same results. I loaded a backup copy of the shard from several years ago using an older build of .56b with the same results. I have even tried a new nightly of 56c.

I have tried several different client versions with the same results.

This is happening to all clients on the server, not just me (who has staff privileges)

I am using the 2013 56b prerelease version.

Any ideas on scenarios where the client would not want to send the buy/sell packets to the server, or any ideas why this suddenly might have happened?

Post: #2

Found the issue. We released a file patch where some unused graphics were removed from gumpart.mul (things like the old style chest opening animation from really old clients and some of the unused splash screen images) and apparently either the client relied on something that was deleted or it messed with the index or something even though none of the graphics deleted had anything to do with the buy/sell menu nor looked important (i.e. nothing that looked like it might be hitboxes for certain buttons, etc). At any rate, restoring the client's default gumpart.mul (and idx) fixed the issue. Quite strange.