Message Boards

It has been too long (and we apologize for that!)

Since 0.4.3, Odamex has been vastly improved in the areas of stability and reliability, some changes including better Mac support, closer vanilla doom emulation, some gameplay changes/improvements, ALOT of crash/resource leak/buffer overrun and bug fixes, plus many more.

We hope to get this out ASAHP so stay tuned!

Okay, as from discussion on irc, we have a problem.

Firstly, Cvars are console variables, which reside on the client and server, they are the ones that affect gameplay and other things.

The problem is: our current implementation.
As of late commits (below r951), we send all server cvars to the client, which results in perfect sync of the client side values. This is what was needed to be done eventually.

However, we have a naming problem, the freelook bug is a good example of this: we have a cvar named allowfreelook, which existed on both client and server, but the clients version was affected by the servers version "through proxy" by changing the sv_freelook cvar, the client could toggle freelook on or off using cl_freelook.

There lies the problem, we now send allowfreelook, which is used by the client and server, it is a variable in the common codebase as well.

We can't:
a) Stop sending allowfreelook (its has a CVAR_SERVERINFO and is needed), that is downright hacky as well.
b) Remove cl_freelook and sv_freelook, then the server would force freelook on or off, depending on its setting.
c) Countless other ways that results in hacky/buggy code.

Now, you may think this only affects freelook overall, but it doesn't, it affects a LARGE amount of other things as well, so what I and others of the team propose is this:

A) Put every single cvar in a single file that exists in the common codebase.
B) Bring back namespaces (cl_* and sv_* prefixes) for cvars (we could use CVAR_SERVERINFO and CVAR_CLIENTONLY instead, but I have not thought this through completely)
C) <add anything else>

There is one disadvantage to all of this, we break alot of older cfg's, BUT, because we aren't at 1.0 and not stable, we can do all of this.

Suggestions, opinions, criticisms?

Here it is, better late than never, the official pictures and video from the Odamex Magfest event.

While they didn't enter the tournament officially, our team had a bonus match and won 5 - 0 against the winning team, not bad eh?

And here they are, The pics and The video.



Thanks to RottKing for taking these pics and the rest of the team for setting it up, great work guys!

Here I have a patch that makes it easy for a user of odamex
to set console variables.

It allows the user to type, for example:

_{set cl_run enabled}

or just

_{cl_run enabled}

If the user just wants the value


_{] cl_run
"cl_run" is enabled.}


With this patch, there is 1 issue that I know of:
enabled/disabled doesn't get saved to config (yet)

Test it out and vote if you like it or not. (the attached
file is a txt, rename it to a patch/diff extension)

Currently we do not have one of these, but I'll list some possible things and their priorities (for the wxWidgets version).

High: Wad downloading, possibly using a heavily modified version of getwad or be rebuilt from scratch.
Low: Multi-language (Launcher supports UNICODE, but the codeblocks project doesn't have it switched on, the reason is that the client and server don't support it.... yet)

Status:

• + Runs on multiple platforms - Need testers for Mac,
  Linux and any other OS

Key:
* - Implemented
+ - Partially Implemented
X - Not Done