To allow commands like !splitplayers (splits players ingame into 2 games) or matchmaking system please implement:

* !join host - when such PM is sent to player from battleroom host or from lobby admin, he joins the new host


To allow easier support for multi-engine please implement check that

* if mod or map hash is 0, don't verify this hash to determine in lobby sync status

It already exists in SL code but atm it uses "IsEmpty" check instead of 0 check and the values cannot be empty (lobby server and existing clients dont support it).

I am having some trouble understanding why this is needed and if it might be asking for trouble to not check if client has map and mod.

Isn't the founder/host required to have the map and mod and send the correct maphash and modhash to server when it creates a battle ?

I might be off here but it sounds like there is a risk players will play on different maps (same name different content) if hashes are ignored.

roger that

done

Thanks

Any progress on !join for SpringLobby?

Bump... it cant be that hard..

... i guess its kicking for SL users then..

NotaLobby v.2.0, Done

NotaLobby works on Linux and implements !join it is superior for ZK so we should recommend it.

Ok .. is there a way to determine lobby of the user so i could tell them to use other lobby?

The player can type "/ver" into #main, and will get "You have SpringLobby v0.141 (Gentoo,amd64)" (or similar ;)

I meant how do i tell it from another user in lobby :)

To change Main protocol a bit

Without changing the protocol.
we can also add some commands by which the user will say you version of lobby. for example, you send to user: /sayver, he sends to you: Spring 85, NotaLobby 2.0

Yeah but client already says the lobby version to server when logging in. So it should be just protocol change to make server tell us :)

bad: server shouts out lobby name/version of clients <= HACK
ok: server shouts out a kind of list of supported features of a client

edited:
this can be cleanly implemented without any change to SL neccesery:

Clients dont support supported list!
How is shouting version bad? I would like that ..

I need to solve very real problem of one client (SL) not being updated and breaking whole matchmaking system...
And there is no compatibility flag for it.. changing protocol is complex and time consuming and forces work upon all other lobby devs.

Publishing client name is simple and cheap.

Atm I resort to abusing CPU speed for my own information about lobby type and capabilities...
now thats wrong..

Do you want to maintain a mapping of version -> capabilities for every existing client?

I've said it before, slaving every client to something you implement outside the server, with no apparent backwards compat, is not a good idea. Ofc I'll be ignored again. Just saying.

This. I've previously voiced my concerns about external entities being able to force players into a battle. The potential for abuse is extremely high on it - just for example: constantly poll new players joining, check if they are smurfs, if they arent, have them get !joined into a zk game with the PM: 'Hey, you seem to be new here. Would you like to try a game of Zero-K? It is the fastest growing game on the Spring engine and you will love it!'