Doomsday Engine

Logged In: YES
user_id=717323

There are way too many things going wrong with
multiplayer games in jHexen. Fixing the messy code
might not be worth the trouble.

(originally posted by anonymous SF.net user)

Logged In: NO

>There are way too many things going wrong with
>multiplayer games in jHexen. Fixing the messy code
>might not be worth the trouble.

WTF?! How can you say "... might not be worth the
trouble." ?? SUGGESTION: Make the server save each map's
state when exiting, and when reentering the same map reload
that state and apply it to the map in question. The map state
would be stored with some sort of safety lock that wouldn't
allow the state to load when entering that map in a new
game. Perhaps applying some type of "Game IDs" that would
be stored in the savegames.

Logged In: YES
user_id=773520

Ooops... sorry about that! Forgot to Log IN... bellow message
is mine. ;)

Logged In: YES
user_id=717323

>Fixing the messy code might not be worth the trouble.

OK, I was only half serious when I said that. (I had been
debugging it and it seemed quite hopeless.) The things you
suggested are already being done, and should be working.
After all, much of the multiplayer code in the jHexen dll is
from the original Hexen. However, due to the numerous
changes and the client/server implementation (which is a bit
kludgy at the moment) things are not working like they
should, and the reasons are complicated or hard to find.

It is my intention to see these issues fixed.

Logged In: YES
user_id=717323

Polyobj destAngles were not set when server loaded the
old state of the map from disk.

DDMF-flags that were set only in P_SpawnMobj
(dontdraw, solid) weren't restored when map was loaded.
Now RestoreMobj (sv_save.c) sets the correct flags.

Logged In: YES
user_id=717323

In deathmatch, the maps aren't even supposed to be
restored.