Zandervix at MBO has passed on word from MythDev that they're looking for help with their next phase of Myth development; they're looking for programmers, illustrators, modelers and beta testers. Anyone interested can contact them.
After witnessing how a few mythdev members have treated project magma, I wouldn't volunteer too quickly.
The team on Project Magma did wonderful things with the old myth II code and made a lag free myth II 1.4. For myth II 1.4.1, mythdev became involved, took control, booted out Magma, posted a lot of crap about magma, then they replaced working myth II code with broken myth III code.
I wasn't even involved with the project(nor am I in magma), but I read a number of the posts and it was rather upsetting.
I'm sorry to hear about that. I can't say I've followed very closely what's gone on lately in Myth development, and I haven't been able to try (yet) either the 1.4 or 1.4.1 patches.
However, if I had to choose, the ability to play natively on OS X would probably be my primary concern. If it's true that 1.4.1's networking code is not as robust, that would be a change-- I'd hate to have to choose between OS X native mode and good netplay.
Anonymous wrote on Tue, 08/19/2003 - 21:09:
: After witnessing how a few mythdev members have treated
: project magma, I wouldn't volunteer too quickly.
: The team on Project Magma did wonderful things with the old
: myth II code and made a lag free myth II 1.4. For myth II
: 1.4.1, mythdev became involved, took control, booted out
: Magma, posted a lot of crap about magma, then they replaced
: working myth II code with broken myth III code.
: I wasn't even involved with the project(nor am I in magma),
: but I read a number of the posts and it was rather
: upsetting.
Well best I understand, MythDev is responsible to Take Two for what's done to any of the Myth series. Project Magma had made some good changes to Myth II, but also some extremely controversial gameplay changes, without informing anyone prior to 1.4's release - changing the mechanics of melee battles, what dwarfs did when they died, etc. Much uproar was caused by these changes, so the project was brought back inhouse by mythdev for Myth II 1.4.2 and now Myth II: 1.4.3.
The networking code is actually better now than it had been in Myth II originally. The security mythdev added has reduced greatly the amount of hacking other players' games and such. It's not an issue of robustness, if anything it's moreso now.
Another reason it was brought back in house was that at one point magma had dropped in OpenSource code to handle input routines, something you just can't do in a commercial title, which Myth II still is, since Take Two hasn't released it as freeware or opensource. In essence this, if left in, could have caused legal trouble for Take Two, and truly ended any future for Myth.
As far as posting crap, I believe it was some magma team members that started that, because they didn't like hearing "no you can't do that" from the people that were legally responsible for what they were working on.
Comments
Anonymous (not verified)
Re: bah
After witnessing how a few mythdev members have treated project magma, I wouldn't volunteer too quickly.
The team on Project Magma did wonderful things with the old myth II code and made a lag free myth II 1.4. For myth II 1.4.1, mythdev became involved, took control, booted out Magma, posted a lot of crap about magma, then they replaced working myth II code with broken myth III code.
I wasn't even involved with the project(nor am I in magma), but I read a number of the posts and it was rather upsetting.
narcogen
Sorry to hear it
In reply to: Re: bahI'm sorry to hear about that. I can't say I've followed very closely what's gone on lately in Myth development, and I haven't been able to try (yet) either the 1.4 or 1.4.1 patches.
However, if I had to choose, the ability to play natively on OS X would probably be my primary concern. If it's true that 1.4.1's networking code is not as robust, that would be a change-- I'd hate to have to choose between OS X native mode and good netplay.
Anonymous wrote on Tue, 08/19/2003 - 21:09:
: After witnessing how a few mythdev members have treated
: project magma, I wouldn't volunteer too quickly.
: The team on Project Magma did wonderful things with the old
: myth II code and made a lag free myth II 1.4. For myth II
: 1.4.1, mythdev became involved, took control, booted out
: Magma, posted a lot of crap about magma, then they replaced
: working myth II code with broken myth III code.
: I wasn't even involved with the project(nor am I in magma),
: but I read a number of the posts and it was rather
: upsetting.
Anonymous (not verified)
Re: Sorry to hear it
In reply to: Sorry to hear itWell best I understand, MythDev is responsible to Take Two for what's done to any of the Myth series. Project Magma had made some good changes to Myth II, but also some extremely controversial gameplay changes, without informing anyone prior to 1.4's release - changing the mechanics of melee battles, what dwarfs did when they died, etc. Much uproar was caused by these changes, so the project was brought back inhouse by mythdev for Myth II 1.4.2 and now Myth II: 1.4.3.
The networking code is actually better now than it had been in Myth II originally. The security mythdev added has reduced greatly the amount of hacking other players' games and such. It's not an issue of robustness, if anything it's moreso now.
Another reason it was brought back in house was that at one point magma had dropped in OpenSource code to handle input routines, something you just can't do in a commercial title, which Myth II still is, since Take Two hasn't released it as freeware or opensource. In essence this, if left in, could have caused legal trouble for Take Two, and truly ended any future for Myth.
As far as posting crap, I believe it was some magma team members that started that, because they didn't like hearing "no you can't do that" from the people that were legally responsible for what they were working on.