Sleighyah

>Go to getmangos.eu

>Post question about Trinity

>Profit

http://www.filemaw.com/file/7-mangos-20101230075610.xml

Backup as of right now.

You're welcome.

Mozilla's management technique doesn't suck donkey balls.

Try reading the whole post not just parts...

I did read the whole post. Thanks for checking, White Knight.

Mozilla's management technique doesn't suck donkey balls.

If you want your patch implemented, why don't you just diff it and add it into your source, compile, and profit?

Edited:

My issue is with the way the actual core is written more than anything, so I'm not going to complain about contributors, even though the two are linked in a very major way.

I was in the beta (got a couple of friends that work as interns), I quite liked it to be honest. The old world, anyway. I never got to touch Hyjal but Vash'Jir is outstanding.

If you are a European, and a student, you are lucky.

Damn I knew I shouldn't have moved to Australia.

The problem I see is that the developers expect a standard of coding that can only be achieved by a team working on the patch, not just the one or two developers that usually work on them.

For example, take some of the many vehicle patches out there. The MaNGOS developers (although I could be completely wrong about this) do not want to incorporate these patches due to their inherent instability and incompatibility with current revisions of MaNGOS. However the problem with this logic is that incompatibility issues will only be resolved by incorporating the code into the project, as it is absurd to suggest that for every revision, these patch developers update their code to work, as some of the larger ones (such as vehicle support), are entangled with much of the existing code.

The issue of instability could also be solved by incorporating this, as due to MaNGOS being an open-source project, the problem will be solved, if you let the community have the chance to even try.

I understand the sentiment of this practice, but in reality, it proves to be impractical. MaNGOS itself isn't perfect, so why does it require third party developers to be?

If MaNGOS took a more modular approach, patches would work nicer.

I'm not meaning 'shit codebase restart', but it should be becoming progressively more modular in style.

Edit:

Ah, no auto-merging of posts on this forum. Apologies for double posting.

You can always use your skills for something good, instea ...

This topic makes kitty sad.

I'm a web developer, not an app developer. I don't know much of C or C++.

This not bugs but not implemented features. I think you not understand difference bugs from missing features.

I'm a developer by trade mate, I know what the difference is. My point is that they're not implemented. Regardless of what you want to call them, they've been around since about 3.0 and they're not working. When I replied to Kich0 in my original post, I was saying that functionality in this case wasn't in place. The features are missing. I never mentioned anything about bugs, so please refrain from judging my ability to understand simple differences when it's actually in my day-to-day work.

MaNGOS care about code quality and long-term proper implementation instead of functionality and short-term hacks.

Anyway please stay on topic.

The issue is that in many places this isn't the case. Multiseat mounts don't work yet, for example, or mounts like Invincible or The Headless Horseman's mount are capable of flying in Azeroth (3.x, not 4.x).

Don't even get me started on Death Knights (especially their initiation quest chain).

If you have a router, did you port-forward ports 8085 and 3724 to your LAN IP (e.g. 192.168.0.3)?

I used to have an entire script series written up to do this for me (I'm a web developer by trade). If I get around to rewriting it I'll release a simplified version of it to the community.

I currently have a six-week holiday from my studies, so I'll work on it sometime over the next few weeks.

Aren't flags such as --enable-cli and --enable-ra already active?

There's really not much you can do to get 'the most' out of the install. MaNGOS isn't a chew toy or an application with Easter eggs. How much you make of it is defined by how you use it (ScriptDev2, ACID, database, etc.).

Are the following settings in the correct state?

GM.LoginState = 0

GM.Visible = 1

GM.Chat = 0