Hey Daimonin Dev Peeps,

I was helping out a noob earlier today (erm, Friday, that is). They had DL'd the client on Thursday (28 Feb) and joined and when they logged in today (with the new human male graphics) their character (a human male) wasn't displaying.

I can't remember this player's name but they said that their game was working fine on Thurs but not today. I imagine that something happened in the x-fer/update of the new graphics, and along with Opty, we advised him (he was running Debian .9.7, IIRC) to delete all of the files in his /cache dir and, failing that, just wipe out the install and re-DL/isntall everything again.

But there might be an issue out there with people running Linux DLing the client with the new graphics update.

Wish I had more info. I asked the player if they had joined the forums and when they responded in the negative I advised them to do so and post about it, so maybe they'll read this post and can provide more information.

Tnx!

yeah for some reason when i joined (on ubuntu linux- debian based), instead of showing the "loading" image, it just showed nothing untill the new graphic loaded.  So i don't know whats up with that, but it may be a small glitch.

I can't confirm any of this behavior.
I just tested it on ubuntu with the package (0.9.7.1 (!!!)) from the website and a new character.
Got the load tiles, and the images were correctly displayed.

Perhaps the problem is that apparently some people are stubbornly still connecting with the mapmaker client. Which has no truecolour support and so that image (RGB) won't be displayed.

Someone was doing this last night.

I guess we should have gone with 0.9.8 not 0.9.7.1 (or even better 0.10.0 ) so outdated clients cannot still connect.

I use an old client (I think 0.9.7) that I have compiled when B4 was not yet released. I don't have any reason to recompile if my old client works, do I? Hopefuly I saw this thread and now I know I must recompile but I think there should be some check between the client and the server to ensure that people are being told when their clients become too old.

smacky: the 'external' version number has nothing to to with ability to connect, its the internal protocol version.
Fontus: i have forgotten why we didn't change the protocol version this time, so old client would be refused. maybe it was that the new mapmaker package was (and still is) not ready. maybe it was because we had planned to do some 'real' protocol changes relativly soon after, which were delayed by the new website. But you are right, we need to adress this.

Hm, I understand that. Maybe I din't make my point very well or am still misunderstanding something.

AIUI the 0 means beta. So until v1.0 it'll always be 0.xy.z.

xy is the protocol version. Client and server must have a matching protocol to connect to each other.

z is the (optional) patch level. This does not affect connectivity.

Hence 0.97 clients can connect to 0.97.1 servers. But 0.97 clients could not connect to 0.98 servers (the 0.10.0 thing was a joke).

Well, to totally confuse you:
The protocol version of the current trunk (with endian patch) is 991024, the mainserver, and 0.9.7.1 has 991023 ;-)