Bug 127: (Volt) I logged in and / and /who com...

[BugTracker]

Bug ID       : 127 - I logged in and / and /who com... 
Bug Date     : 2015/01/21 10:11:57
Assigned To  : Volt
Priority     : Medium

Category     : VGClient
Sub-Category : Gameplay: Other
Severity     : Standard
Reproducible : Only seen once

Details:
I logged in and / and /who commands didn't work.

Originated From World: New Telon (1)
Chunk                : Vault of Heroes (174)
Location             : -19224 -29296 32036

[Volt]

Please explain what is meant with "didn't work".
Also, were there other problems for that character at that time?
Also, for anyone reading this post, please post if you have seen this lately. Would be helpful to know if this is "one time ever lately" ("ever lately" transferring to in the last month or so).

[John Adams]

Volt, /who definitely did not work for me the other day. I have no idea why. It has been one of the most stable commands forever. Sadly, in-game chat logging won't auto-log like it did on live when I log in, and I forgot to turn it on so we miss me whining about it (actually might have fixed my /autolog)

From what I remember, I simply logged in and was standing there (that's normally all I do when checking player statuses). I think some people may have came and went while I was online, but I did a /who all and nothing. I did a /who and nothing. I did a / and nothing. Then started whining. I did other commands, like .speed and .setmotd and those did seem to work. Honestly the first time I had NOT seen a game-side slash command not work.

And by this, I mean nothing echoed in the Console Window (though I believe we're lacking much debug logging still, so that could be why).

Hope that helps.

[Moldew]

Just happened again to me today. I logged in this morning, minimized, went about my day. Went back to my screen and the / commands didn't work.

Actually, I just crashed to character login screen too.

Time right now is 2:39PST.

[Xinux]

Not sure this goes here but i figured out why some commands don't work in say New Telon channel.

The packets are being sent back from the world server not the chunk server which is why commands that just kick back text work fine but the one's that kick back opcodes do not. I'm not sure how to fix this maybe create a function in the chunkserver and have it call that instead of building the packet in commands maybe you have some idea's lokked.


opcode 997 is op_ServerTeleportInChunk which need's to come from the chunkserver not the worldserver.

Code: Select all

-- OP_MarketPlace --
1/22/2015 16:08:03
10.15.155.65 -> 10.15.155.64
0000:	00 09 00 B4 02 00 6F 00 00 00 58 00 00 00 0C 00 ......o...X.....
0010:	1B 00 00 00 55 6E 68 61 6E 64 6C 65 64 4D 65 73 ....UnhandledMes
0020:	73 61 67 65 73 43 6C 69 65 6E 74 2E 6C 6F 67 33 sagesClient.log3
0030:	00 00 00 52 65 63 65 69 76 65 64 20 75 6E 68 61 ...Received unha
0040:	6E 64 6C 65 64 20 6D 65 73 73 61 67 65 20 69 64 ndled message id
0050:	20 39 39 37 20 66 72 6F 6D 20 57 6F 72 6C 64 53  997 from WorldS
0060:	65 72 76 65 72 2E                               erver.

[Lokked]

Good to know. This weekend, I hope, I should be able to sort this out. It seems easy enough: The section of code that captures the '"." should detect if the call is coming from the World Client or Chunk Client and act appropriately, which I think is to always send through the Chunk Client. I think there are very few dot commands that require the World Client, but we have a process to send packets in that manner anyways (auto world_client = net.GetClient(client->GetAccountID());)

Good Find, Xinux!

[Volt]

Lokked, just note that the /who command is not a .dot command. Maybe you already was aware of that but I thought Id better make sure.