Deleted

Deleted

You got that by pressing Enter in the middle of the lobby?

aaron_yume wrote:

I don't think this is supposed to happen is it?

I don't know but that level looks like its a pretty gg.

Deleted

There's no way to tell. It could be lag, or it could be a problem with the skin you're using, if it altered more than just the textures used in the lobby. I am not aware of any lag-related phenomena which could allow you to have the team window up while you're walking around, as the counter prevents you from moving or cancelling the request until the list gets displayed.

Deleted

I said:

Aleron Ives wrote:it could be a problem with the skin you're using, if it altered more than just the textures used in the lobby

Being able to open the menu away from the counter could happen if the counter object in the lobby data file was moved or copied to another location.

Deleted

Yes, I misunderstood your post. You were saying that the MOTD window came up while you were trying to view the lobby menu. The MOTD is designed to display as soon as the server detects your position packet saying you are in the lobby, so it didn't display until later because you were lagging and didn't send that packet until you were already at the counter and sending the packet to receive the list of teams. SCHTServ has similar problems all the time, because the MOTD is bugged there and doesn't show up until more than 10 seconds after you enter the lobby most of the time. Usually it just breaks your ability to use the lobby menu, and it forces you to do a soft reset, unless you have a controller. I've never seen the problem let you walk around with the lobby menu.

Deleted

The split function on this forum sucks ass, too. I had to AdBlock all of the image hosting sites, because it loads the entire topic to let you select posts, and I couldn't get the stupid thing to load 40 pages of images to get to the recent posts until I disabled all the pictures. -_-

I don't really see how it is possible to be selecting a team to join at the same time as the MOTD pops up, because you can't select a team to join until you receive the list, and you can't receive the list unless you're not lagging. If you're lag-free enough to receive the list of teams, you're also going to receive the MOTD before you can select one. I think you got some sort of freak accident that would be pretty hard to reproduce. There's also no way I can think of that causing the bug would kill the teams already in progress, because unhandled errors will cause the ship to core dump. If that had happened, you would have been disconnected, too.

Here's how the MOTD stuff works on Sylverant:

1. You select a block to join, which sends a bunch of packets (login negotiation with the block, etc), including your character data (and other stuff afterwards, like your position and such).
   
2. Upon getting your character data, if the ship has a MOTD, it sends a ping packet to the client.
   
3. Upon receiving the ping packet, the client enqueues a ping to reply to the server (this goes after all the other packets that it has enqueued at this point).
   
4. When the server receives this ping, it sends the MOTD in a large message box packet.

There isn't any way you should ever be able to get the actual game list to show up before the MOTD. The menu to pick what option you want, maybe (since that's all client side anyway), but you shouldn't be able to get the populated game list to show up first. Since everything uses TCP, there's a strict ordering to the packets. The server will have to process your character data packet before it can get around to giving you the menu. If for some reason you could manage to make that happen (that it gives you the list of games first which would mean your client would have to get to the point where it requests the list of teams before the server ever sees your character data packet), it should still never get to the point that you can actually select one of those games before the MOTD pops up (once again, strict ordering of packets). You would have had to have sent and received several sets of packets before you can join a game, hence why it shouldn't be possible to join a game before the MOTD pops up.

Unfortunately, because of the way the large message boxes don't send a message box closed packet on the Dreamcast version, there's no way to know when people have finished seeing the MOTD. If there was such a packet sent on the Dreamcast version, this would be much easier (simply don't pay attention to the client's packets until the MOTD is closed). Of course, the versions that do send a message box closed packet can't show one of those message boxes once you join a lobby, or you'll crash...