Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chat message can only be sent to STATUS_ACTIVE Client #4990

Closed
DorpsGek opened this issue Jan 19, 2012 · 4 comments
Closed

Chat message can only be sent to STATUS_ACTIVE Client #4990

DorpsGek opened this issue Jan 19, 2012 · 4 comments
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

muxy opened the ticket and wrote:

Since r2337 who fixes #4826 its no more possible for the admin protocol to send a chat message to a client who just join the game when receiving the CLIENT_JOIN packet. The message is sent to other players.

Could it be possible to change the status level for the message to be sent to client to STATUS_PRE_ACTIVE ?

Or to have the CLIENT_JOIN packet when the client is at STATUS_ACTIVE ?

Reported version: trunk
Operating system: All


This issue was imported from FlySpray: https://bugs.openttd.org/task/4990
@DorpsGek
Copy link
Member Author

xOR wrote:

It's an issue for me too. My admin port client sends a welcome message to players that have connected (e.g. giving him a link to the server rules). It does that after it learns about a client by the CLIENT_JOIN packet.
Ever since 1.1.4 (or r23337) it is random whether the client receives the welcome message or not, depending on its timing. More often than not there is no message received by the client. Before 1.1.4 welcome message were always received.


This comment was imported from FlySpray: https://bugs.openttd.org/task/4990#comment10770

@DorpsGek
Copy link
Member Author

dihedral wrote:

to me there are two solutions to this issue:
a) allow chat to be sent to STATUS_PRE_ACTIVE clients
b) only show STATUS_ACTIVE clients in the gui, notofy the admin network only when the client is STATUS_ACTIVE, postpone execution of the on_server_connect.scr script

personally i consider a) the better option - the client is connected, has the client list of all other clients and is simply waiting for the sync to complete - chat should still be available to send and receive. The client already seems able to send chat (at least that is what i gather from the code): the server accepts chat as of STATUS_AUTHORIZED

one would have to agree on either STATUS_AUTHORIZED or STATUS_PRE_ACTIVE as of when the client may send and recieve, rather than allowing the one earlier than the other.
personally i think that should be STATUS_PRE_ACTIVE rather than STATUS_AUTHORIZED.

none the less - find patches attached.

Attachments


This comment was imported from FlySpray: https://bugs.openttd.org/task/4990#comment10892

@DorpsGek
Copy link
Member Author

dihedral wrote:

by the way - the patches are server side - just in case you guys want to patch your servers for the time being (if you have not done so already) ;-)


This comment was imported from FlySpray: https://bugs.openttd.org/task/4990#comment10898

@DorpsGek
Copy link
Member Author

Rubidium closed the ticket.

Reason for closing: Fixed

In r23957. Thanks for the patches dihedral.


This comment was imported from FlySpray: https://bugs.openttd.org/task/4990

@DorpsGek DorpsGek added Admin flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) labels Apr 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Development

No branches or pull requests

1 participant