Jump to content

imblizzspy

Members
  • Posts

    48
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

Posts posted by imblizzspy

  1. mangos has been here ever since 2005, and as you and others may have noticed: there have been thousands of people telling us we suck, and we will sooner or later fail and be shut down by Blizzard.

    There have been numerous projects, including Antrix, Ascent, etc. which at one point started to use and enjoy code created by mangos developers, and always sticked to claim those patches had been built themselves. Guess what? Sooner or later those projects discovered the end of the road because they lacked own efforts.

    And guess what? Every time mangos has offered every of those projects a home, where they could actually learn stuff and do things for real.

    Now let me see... what do you think are the chances that all those emulator teams will team up? Zero. Just for the same reason the topic creator has worked on a closed source emulator which surely contained code by mangos.

    You're correct about everything but antrix/ascent/whatever - they surely used lot's of code and ideas from mangos (vmaps f.e) but the reason those projects are no more is due to burlex's inability to manage such project, his attitude, as well as leechers making money out of it.

    The chances for teaming up are equal to zero.

    The chance of cracking cata? If they keep on randomizing operation codes the last cata patch before 5.x.x is your best bet. But it's not like WoTLK is finished, nor is TBC, not to mention - 1.12.... so why so hasty?

  2. Voice chat isn't implemented. I don't think it's worth spedning time but if you insist then take a loot at old ascent's source code(rev 45xx I believe) and it's VC written by burlex(dunno if it ever worked, besides its pretty old) and mumble voip application.

  3. This is something i have seen happen a few times over the past months. I was wondering, and this goes to the developers if you guys have like an irc or some place apart from the forum to discuss development. Something apart form forum that can help in the development of the project. Since for example, the patches that right now involve changes to the whole project and can in several points enhance it are, and this is just a quick sample:

    +Dual Talent

    +Vehicle Support

    +Summon Properties

    +Player Skils from Blob

    +MtMaps

    and it would be nice to have a faster way to talk about this. The forum is great but for example, some people do not know what to work on sometimes or if they are working on something similar to another dev.

    Yeah, there's an irc channel, but take a look at linux-like way of development proposed by freghar.

    There are tons of patch in under review section atm..

  4. Such complaints led to creation of Tri%#!@ and wasted effort of many people(they usually switch back : S)

    But I perceive your post as very constructive. I'm happy with the current development process, it's not like my opinion matters but I've been wondering for a while how are new developers appointed. It's open-source so I guess it would be better to make subforum for dev apps, or at least promote more than 2 people per year :)

    I've been following Dolphin (GC/Wii emulator) for a while and they promote almost anybody to dev and to my surprise they went from 5-15 fps, glitches, crashes and no audio in games to almost perfect state where games must be frame limited and AA/AF things were implemented so they look and run better than on hardware(it took them 1 year).

    But what I love about MaNGOS is quality. It's amazing.

    "Suggestions: Since allot of developers are busy with their problems. Maybe hire few people who would be, only responsible for finding correct patches and testing them. They can than move them along to developers who can confirm it and apply to the respected branches."

    I like this idea, a Quality Assurance group that would test patches, find mistakes, correct them and eventually report to devs. They could have some special privileges too.

  5. No offense, but no, you can't, unless you also include custom patches designed to fix / remove crashing abilities.

    I have tried several times with a completely clean DB, latest matching revisions of SD2, UDB and Mangos (for TBC) and could barely get an hour or two uptime with ~150 users on. This is on a completely dedicated server with latest OS updates. Might be different for linux (we run our servers on windows server 2003), but I very much doubt it.

    Are these crashes due to the OS or compile then? Not likely: once our testserver ran the same version for around 140 days without crash (mostly as test to see how long we could keep it up - at that point I had to take it down to replace server hardware). Of course, since it was a testserver, it never had more than 5 users online at the same time.

    Certain things players do simply crash the server. In my experience almost all of this is due to aura's / spellcasting / custom objects in the realm, like a Paladins Retribution Aura around revision 8200 crashing the server when he attacks a mob in netherstorm, or a priests reflective shield which somehow also crashes the server in PvP combat, or an attacking mob when you leave an instance or even a corpse in a cleaned up instance. Made a few bugreports about it, but nobody seems to care or is able to find a solution - and I'll admit we are still unsure ourself about what exactly causes crashes sometimes.

    There is actually a discussion going on here about a different release style, with marked milestones and asociated feature-freezes. I would very much like to see something like that, but dev's disagree unfortunately. As it is, we usually compile, put a version up on the testserver, keep a very close eye on the bug report section and if after a week there are no new crash reports for that revision (like these). we update Generally works out :)

    I was talking about 0.12 with mtmaps on linux systems. Try asking leak, barlok and others.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use