Odamex

[QuiescentWonder]

You can get the latest Odamex build right from the SVN here: https://sourceforge.net/project/showfiles.php?group_id=187433&package_id=218892

As of this writing (r90) most of the immediate show-stopper bugs (like the launcher not working) have been fixed.

NOTE: This project is not connected with the makers of Odamex in any way, it's just the latest build from the SVN by an enthusiast. Also, the offered builds are only Win32.

UPDATE: I'm going to move this over from SourceForge to my hosting as soon as I possibly can (need to register a new domain, can't until my next credit billing period starts) and hopefully will have the entire process automated. Right now I have to run a batch file, then manually change odamex-0.1a-rXX.zip to the right name. What I mean is, within five minutes of a revision you will be able to download a Win32 packaged release. I'm thinking about having a few different versions, maybe one packaged with FreeDoom, but I'll have to figure that out later. Right now I just need to figure out how to start the process as soon as a revision is uploaded to the SVN, name the package appropriately and then upload it via FTP with some release notes (changelog). For now I'll only release daily, or twice daily builds to SourceForge.

[LexiMax]

Thanks for this. The problem with doing 'enthusiest builds' however is that in a couple of days they end up being behind the SVN by at least a dozen commits. Thus, it goes without saying that compiling it yourselves is prefered.

[Naked Snake]

I dunno, an auto-compile script would kick ass for people like me who have no idea how to compile stuff and the like.

[Manc]

Naked Snake said:

I dunno, an auto-compile script would kick ass for people like me who have no idea how to compile stuff and the like.

The bigger problem comes in distribution. We've already spoken about using sourceforge for this, and I can't imagine this project being active on there for very long because sf is not the place for continuous uploads. And on top of it all, some revisions are really not meant to see the light of day beyond pure testing purposes. Usually you'll have no issue connecting old clients to new servers and vice versa, but not always.

We plan on providing revision builds weekly and then version releases when it hits a stable point. This way criss crossed version conflicts can be reduced. We always HIGHLY recommend you get them from us unless you're looking for a specific branch or fork. You can't be too sure if anything's been added to these, not to mention the source code is not provided in these.

[Naked Snake]

Mancubus II said:

The bigger problem comes in distribution. We've already spoken about using sourceforge for this, and I can't imagine this project being active on there for very long because sf is not the place for continuous uploads. And on top of it all, some revisions are really not meant to see the light of day beyond pure testing purposes. Usually you'll have no issue connecting old clients to new servers and vice versa, but not always.

We plan on providing revision builds weekly and then version releases when it hits a stable point. This way criss crossed version conflicts can be reduced. We always HIGHLY recommend you get them from us unless you're looking for a specific branch or fork. You can't be too sure if anything's been added to these, not to mention the source code is not provided in these.

Oh, I didn't know you guys were doing weekly builds. Rock on, looks like I'll be getting new Odamex from the official source.

[chilvence]

Naked Snake said:

...people like me who have no idea how to compile stuff and the like.

svn co http://odamex.net/svn/root/ ./odamex
cd odamex
make

And dont quote the entire previous post! Quote button bad! Use only in case of extreme circumstance!

[kristus]

More like, there's no point in quoting a post that you're posting a reply to right after.