Next version

[dude11235]

I'm sick and tired of all the people asking what's going to be in the next version so I made this.

1. Dretch ground head-bite will be changed (don't know how)
2. The tyrant is being toned down somehow
3. A bunch of new maps will be included
4. New admin abilities
5. And a bunch of stuff the dev's are not telling us...

On anything I missed please feel free to post it.

[next_ghost]

The above post is purely fictional. Any resemblance to real features, coded or not, is purely coincidental.

Luckily, after this thread dies, nobody will ever read it again. So please, let it die.

[dude11235]

Bump

[n00b pl0x]

how will they include new maps?

[Caveman]

FISH

[Radiohead]

Well, I guess the new maps will be true, and I really hate the gay dretch headbite, FIX IT!!!!

Or not.

[Smokey]

Well, I guess the new maps will be true, and I really hate the gay dretch headbite, FIX IT!!!!

Or not.

hello mr.hugesig 9000.

[kozak6]

That's nothing.

You should see Whale's.

[n00b pl0x]

lol <3 whales sig

[oliver]

dude11235: you managed to miss the first reason for a new Trem release: fixing bugs!

... race conditions when using some in-game menu
... forgetting settings once in a while
... no responsiveness during map loading
... mouse disappears when game can't find the required map

And I guess I have already got used to the many other major and minor annoyances :-/

[gareth]

... no responsiveness during map loading

what kind of responsiveness do you want? it only takes 2 seconds anyway.

[oliver]

... no responsiveness during map loading

what kind of responsiveness do you want? it only takes 2 seconds anyway.

Haven't measured it, but it seems like eternity :-) and at least ten seconds, which is waaaay too long if I see that Nexus6 comes up (which I hate) and want to switch to another server.
Ok... maybe instead of responsiveness, loading the maps in one second would be ok as well :-) but just making the GUI useable during loading seems like a more general solution.

[kevlarman]

dude11235: you managed to miss the first reason for a new Trem release: fixing bugs!

... race conditions when using some in-game menu
... forgetting settings once in a while
... no responsiveness during map loading
... mouse disappears when game can't find the required map

And I guess I have already got used to the many other major and minor annoyances :-/

how exactly are there race conditions in an engine that refuses to use more than 1 thread?

[hodge]

If your not tremulous developer, PLEASE DON'T SPREAD LIES ON WHAT 1.2 WILL CHANGE.

thank you asshat ;-).

[oliver]

dude11235: you managed to miss the first reason for a new Trem release: fixing bugs!

... race conditions when using some in-game menu
... forgetting settings once in a while
... no responsiveness during map loading
... mouse disappears when game can't find the required map

And I guess I have already got used to the many other major and minor annoyances :-/

how exactly are there race conditions in an engine that refuses to use more than 1 thread?

The races are between client and server... Like this: go to armory, press q, quickly buy some gear that you already have. If you buy quick enough, you get the "you can't buy that stuff twice" message _after_ buying something else. This message can't be clicked away then and remains in the foreground till you die (in the game of course :-D ) You can still use the "buy" dialog in the background, though.
Looks like the server sends a reply after buying, and if you click faster than the server ping (ie. 50 to 100 ms) the race condition comes up. Happens fairly often to me in a heated game or slow server. And there are other similar client-server races in Trem.

(Btw. I think it's a WTF for itself to display this "you can't buy this item twice" message at all... If really necessary, play some "negative sounding" sound, but don't annoy the user with a message that he has to confirm).

[Odin]

That's nothing.

You should see Whale's.

Yea, he's got a "whale" of a sig.

*ducks*

[rapha]

INVERTEBRAE

[kevlarman]

dude11235: you managed to miss the first reason for a new Trem release: fixing bugs!

... race conditions when using some in-game menu
... forgetting settings once in a while
... no responsiveness during map loading
... mouse disappears when game can't find the required map

And I guess I have already got used to the many other major and minor annoyances :-/

how exactly are there race conditions in an engine that refuses to use more than 1 thread?

The races are between client and server... Like this: go to armory, press q, quickly buy some gear that you already have. If you buy quick enough, you get the "you can't buy that stuff twice" message _after_ buying something else. This message can't be clicked away then and remains in the foreground till you die (in the game of course :-D ) You can still use the "buy" dialog in the background, though.
Looks like the server sends a reply after buying, and if you click faster than the server ping (ie. 50 to 100 ms) the race condition comes up. Happens fairly often to me in a heated game or slow server. And there are other similar client-server races in Trem.

(Btw. I think it's a WTF for itself to display this "you can't buy this item twice" message at all... If really necessary, play some "negative sounding" sound, but don't annoy the user with a message that he has to confirm).

cg_disablewarnings 1 is your friend.

[Xonya]

If you are sick and tired: don't read, or better, don't visit our lovely forums ever again!

[rapha]

Who did you get NEW shoes from Xonya?