TheLuda

If you have troubles with accessing GitHub.com or with GitHub connectivity, there is a Git mirror for Mangos: * http clone URL: http://repo.or.cz/w/getmangos.git * git clone URL: git://repo.or.cz/getmangos.git

I’m officially opening the MaNGOS Lighthouse tracker up for business. This means the old Trac instance is deprecated. It will continue to stay in use internal for now until everyone has transitioned to Lighthouse. We’re still figuring out the new workflow with git, Github, and Lighthouse. We will be working on bringing the same development tools to the new git infrastructure.

GitHub has launched a while ago and the MaNGOS core team took the chance to evaluate both Git GitHub.com. We now have finished our evaluation of Git and migrated the old MaNGOS subversion repository to GitHub.com. The MaNGOS repository now lives at mangos/mangos and you can check out the code with Git using the following command: getmangos@workstation:~$ git clone git://github.com/mangos/mangos.git In ~ 1 minute you will have the full repository on your computer and can use it to work on MaNGOS. If you don’t have git, or don’t enjoy running it on your platform, you need not fear. Git is easy to learn and comes with lots of excellent tools to make you enjoy your daily Git dose. For an introductory view on what Git is and can do for you, visit chttp://git-scm.com/. If you are an experienced user of version control systems, you might want to head over to the Git website. For those who like videos, there also is GitCasts available. This also means that development on the Subversion repository has stopped and will no longer be kept up to date. We’ll keep the Subversion repository around for some time. We hope you’ll enjoy this upgrade to the MaNGOS collaboration infrastructure. We’re really looking forward to the onslaught of marvellous patches that the Git lords have promised us will flow from the mountain now.

All I can say is, we try to make it easier for non-Git users, or less development oriented users. Just give us a bit of time to work out a sane solution.

MaNGOS was and is intended to be a thing for developers. In its' current state, it is not for normal users like Jon and Jane Doe. Unless you see an official announcement, we still consider this to be pre-release software. There is no difference in revision numbers and commit ids. They look different, but that is all just visual. Subversion revisions only have been linear, because we never used branches. Have you considered that revision numbers would not match on Subversion if we commit to branches or tags, because the Subversion revision always is global aka changeset? This is by far not logical and still people did use it. It is not arrogance, it is just a reaction to what people demanded, and if you ask for quicker work, you will have to let us use the tools we as developers need to work quicker, and better. Git is different, but that commit id thing is just like comparing black chocolate to white chocolate. It makes no difference in the end. Whether your mangos demons tell you they are MaNGOS 0.12 revision 6767 or if they tell you they are MaNGOS 0.12 revision 1ccdd8e2b2d7768c0777d9ac34565e3c1b5f1a69, it does not tell you more. In both cases, you will have to look up what that revision means. I'm open for arguments, but I am not open for critics that do not fit the cause. And as I said, the developers have discussed a tool that will map commit ids to normal revision numbers, and embed these into the demons until people have learned to handle the new Git ids. Nothing else to say about the topic.

The version number in Git is the last SHA1 hash aka commit id you see when you execute git log in your repository. The SHA1 hash is unique and exactly identifies which version, branch, etc. you do use.

Did you clone from git://github.com/mangos/mangos.git ? The error sounds like you are trying to use the commiter clone URL.

Do I understand you right, that you can not connect to GitHub.com from China? Seems like you are using a translation service. If you can not connect to GitHub.com, we can set up a Git mirror on some other host, which you can access.

We really appreciate your reactions on Git and the move, but we do not appreciate swear words, or rude behaviour. Let me clarify a few things: * The move was made as a reaction to what the MaNGOS community has asked for. Most people demanded for us being able to handle patches in a better way, faster and more timely close to the patch release. Git is the tool, that allows to fulfill this wish. Nothing else to add. * Subversion was abused by many people as their download tool for MaNGOS. This never was the intention or the purpose of Subversion. If you want binaries to use on your local computer, it would be better to have official builds by the MaNGOS team, or by ScriptDev2 team. * Moving from SVN to Git was not done with the intention of splitting the community into good and bad. Git is a tool, and its best used with command line. But honestly, if you can not use a source control system on the command line, you should not be using MaNGOS or any other server either. Instead you should start to learn that there is more than mouse clicks. Final words: the team already has discussed development of a tool, that will allow normal user to see a linear revision number instead of the SHA1 hashes used by Git. This is work in progress and something we have talked about. In the future, I would prefer to see less whines, and more constructive posts. After all, MaNGOS is about learning, and if you are not willing to learn, then probably a different server project is a better home.

One of the big issues with SVN and SourceForge was the increasing instability. The SVN repository was over 1.4GB in size with full history. Additionaly SVN does not work offline, Git does. You have full diffs and logs even without internet connection. That all is stuff SVN does not have. Plus, many people constantly downloaded from SVN, where it was not necessary. Git is intended for developers, and it is used to ease development process. For "normal" users who just want to run MaNGOS, there will be pre-built binaries once the switch to client 3.0.2 is done.

SVN is still there for a while, until the migration is finalized.

Revision 6767 has been imported from http://mangos.svn.sourceforge.net/svnroot/mangos/trunk/ and is currently pushed to github.com. Due to the size of the import this may take a while, I guess it'll be finished in ~ 10 minutes.

Greetings, for all those of you who currently have write permissions in our SourceForge.net subversion repository, I'd like to ask you to please pay GitHub.com a visit, and register your nickname there. Once your account is registered, and you have an SSH public key added to your account, please visit http://github.com/mangos, and send a message with your old subversion username. You will then be added to the new MaNGOS git repository. Please note that the current source code on SourceForge will be migrated over to github tonight, and all commit privileges on sourceforge will be revoked. Additionally the ticket tracking system formerly known as Trac will stop to exist, too. All issues will be moved to Lighthouse, which means you will need an account there, too. With kind regards, Daniel

Do you have vmaps enabled? I'd disable them with just 1g RAM.

Added in [5975].

This is something you already have proved with your contributions from the past. I hope you will enjoy your stay with us :-D

Welcome! If you are reading this thread, it is very likely that you just have joined one of the teams in the MaNGOS project. This post is intended to give you a quick start on what to do, and where to go first. A few words about privacy The Team Only Discussion section is only visible to people which actively engage in the MaNGOS project. This include developers, moderators, and wiki moderators. The intention of this section is to have a place to communicate without the usual noise in public places. Open Source and community is a pretty thing, but sometimes the community can be a bit distracting, and this is why we have this place. There are a few things to respect, when you are using this section: » Every topic which gets discussed here has to stay here. Never communicate about the contents of the Team Only section with any person that is no member of a MaNGOS team. » While it is acceptable to hide who you are in the public section, we consider it as a sign of trust and respect to communicate with your real name in the private section, at least using your first name. » Any topics covering patches or including patches not yet released to the public, have to stay private. We never hand out pre-releases to avoid confusions and bogus bug reports which we do not need. Useful threads in the private section » coming soon. Work in progress.

Section III - Forum Staff Policies and Expectations: Staff duties are based upon the following* Dealing with Profanity: Mild profanity/swearing is allowed in the context of general speech. Explicit profanity/swearing is not allowed, and under no circumstances will we allow any profanity to be directed toward another person. If you feel a user is out of line please contact an administration with the details, they will issue a warning to the user. * Dealing with spam and potential "jailed" posts: If its a user trying to advertise something move the post to the jail and issue a spam infraction. Posts that are used to flame, harass or harm another person should be reported to an administrator asap. We do not encourage staff to partake in conversation in these types of situations and the administration will handle the issue.* Editing of posts: When a post breaks guidelines and requires editing in order to bring it back under compliance with the rules, the moderator should generally copy the un-edited post to the jail first or issue an infraction which will keep a copy of the original post in the staff area. Only then should the original post be edited after the original content was preserved as evidence. In the private message automatically sent when the infraction is issued the moderator should specify or describe which guideline(s) the post did not follow. * Thread Closing: If a thread has run it's course and posts have begun repeating themes a thread may be closed - if possible, announce that the thread has run it's course before closing so that people may add closing statements - don't forget to thank all users involved in the discussion. If a thread has become a situation where people are simply too personally involved in the issue a thread may be closed and / or jailed. If a thread is a duplicate of another thread, it may be closed (please provide a link to another open thread on the same topic.) It is always a good idea to post an explanation in a thread that is closed. * Jailing of posts/thread: If a post/thread would require a lot of work to bring it into compliance, or if editing the violations would result in a nearly blank post/thread, the post/thread should be moved to the jail instead. * User signatures, avatars and custom user titles: No images or advertising in the signatures unless the advertising is directly related to MaNGOS in some way or is a user's personal site which does not violate the guidelines stated above. If you see a signature that needs moderating, contact an administrator so they can edit it and contact the user via private message. Avatars should be kept clean and inclusive of all people. No porn, racist images, or rtfm types of images. If the user has one of these, send them a private message and ask them to remove the avatar. If the user does not voluntarily remove their avatar contact an administrator to have the avatar removed and possibly issue an infraction. There are a select, small group of users on the forums who have been given the special privilege of creating for themselves a custom user title. This is to thank them for their long-standing commitment to the community and for their consistent, positive contributions. Users receiving this privilege are requested to keep their custom user title light-hearted, advertising-free, and clean...although those who have received this privilege are probably the sort of users who don't need to be told this. * Adult Content/Violence/Illegal Activity: Messages containing offensive / sexually oriented / violent / illegal dialogue, images, content, or links to such will be moved to the backyard or jailed depending on the information it contains, use your best judgement. Messages with links to or suggesting illegal activity will soft deleted by an administrator. These actions could result in a ban for the user. * RTFM/I hate MaNGOS/I hate Ascent threads: As the community has grown these types of threads seem to be more prominent. We need to make sure we can try to steer these conversations into a positive discussion, however in many cases these threads will only end in hurt feelings and will be locked. If the thread cannot be steered into a clean discussion the staff member who locks it needs to be fully supported by staff. * Thread Steering: It will become necessary to steer threads away from becoming damaging towards the poster and other users. Our policy is that we do not allow threads to veer too far off topic, even in community chat, to areas where it would be very easy to get ugly fast; for example, "I hate Ascent" threads. Please do your best to keep posters from getting too personal during heated debates.* Keeping an open mind: Sometimes you will be faced with a thread you might not agree with it's imperative you keep an open mind towards all inclusive people, and keep a neutral focus when replying. It is our duty to steer the conversations back into a positive nature without engaging in negative behaviour. * Posting and moderating in the same thread: This is generally discouraged. If you have participated in a discussion and later find there is a problem in the thread contact the other staff and have someone else who is uninvolved moderate. The exception would be if no one is available, you can close the thread temporarily with a post stating that it will be looked at by a non-involved staff member as soon as possible. If you aren't sure what to do, get an administrator. * Signatures: While we do not have guidelines for staff signatures, please try to keep them moderate and within reason. Staff are chosen by the site administrators. Users who have demonstrated a consistent attitude of friendliness and kindness and who have shown a pattern of helpfulness in their posts may be contacted and invited to serve in an even more official manner. Recommendations can be made by current staff in the staff forums or other users by private message. All recommendations are considered. Due to time constraints and privacy issues the administrators are unlikely to comment publicly on these recommendations. It should be noted that, like all things, this code of conduct will continue to change and evolve with constructive feedback from users and from experience. It is our hope that these policies will create open, honest, and civil discussion. As always, we welcome feedback about any concerns that you may have so feel free to post in the forum feedback section of the forums. It is the users' responsibility to check this page for updates. We require that the forum code of conduct be followed at all times since this is an official MaNGOS resource. Public forum data is released under the GNU Free Documentation License.

Section II - Technical Support Policies: When asking for technical support: * There are no stupid questions. You're not a stupid person simply because you do not know how to do something, or do not have the answer to a question. Everyone was a green user at one point in time. * Try to give information in the title of your post, instead of using a title like "it's broken," use a title that is specific, such as, "Unable to get sound to play in World." A clear title will attract more views to your thread, as it gives a clear indication of the content of the post to the people that are willing to help you. Ultimately this will allow you to get more help of a better quality.* Searching the MaNGOS Forums is a quick way to see if someone has had your issue and if it has been answered. In a forum as large and active as this one, there's a good chance your question has been answered before, and you can get the information you want quickly. * When requesting help, please include as many details as you can. Include as much information as you know. If people are asking for version numbers, consider checking the sources to find out specific information about the revision you have installed. For example, if you're having trouble with MaNGOS, you can search in your SubVersion tree and look up the revision number using svn info to give the people helping you more information. If you do not know how to find out the information that a user is requesting of you, you might want to ask them how to find the information they have requested. Attach screen shots or other files if you think it might be useful. * It's always nice to let the people that help you know that you appreciate their help. It's extra nice if you then share that information to another user that has the same question you just had. If your question is resolved (which is hopefully always the case!), it would be helpful for other users and the people helping you to label which procedure worked for you by quoting or clearly referring to it. Giving feedback as to what procedures worked not only makes the person helping you feel a sense of accomplishment, you will also be helping any other user with your same issue searching for an answer. When answering technical support issues: * Be considerate to the person asking the question. We were all a green user at one point. Yes, some users are harder to help than others, but please be respectful to all users. * Try to avoid acronyms and jargon when giving instructions. New, or "green" users may not be able to follow you, and many will not ask you for an explanation in order to avoid looking stupid. RTFM, "Go look on google" are two inappropriate responses to a question. If you don't know the answer or don't wish to help, please say nothing instead of brushing off someone's question. Politely showing someone how you searched or obtained the answer to a question is acceptable, even encouraged.* If the users' question has been covered in one of the community documents, please give them a description and the links. Some useful sites to point green users are: svn.mangosproject.org/trac/MaNGOS. You can also show the user how to search the forums or tell them about the forum search utility. If you wish to remind a user to use search tools or other resources when they have asked a question you feel is basic or common, please be very polite. Any replies for help that contain language disrespectful towards the user asking the question, i.e. "STFU" or "RTFM" are unacceptable and will not be tolerated.* Always assume the the user has a default installation unless you're told otherwise. If you tell people to use an application outside of the official MaNGOS installation, please give instructions on how to install it. * Always assume that the user is a green user unless you're certain the user is not. Please remember to give detailed instructions some users do not know how to get to a terminal yet. * To avoid confusion and auto-formatting issues, please use CODE tags around terminal commands. If an image speaks a thousand words and can show exactly what you mean, by all means, include an image. * Please wrap long outputs from commands or other text to prevent users from needing to scroll through the content inside CODE tags. * Please remember to do things the MaNGOS way. There are always more than one solution to a problem, choose the one you think will be the easiest for the user. Try to think as a green user and choose the simplest solution. * Explain each step of the solution. If possible, try to teach the user while giving a solution to them. Teaching begets more teaching. * If you're uncertain if a procedure is correct, please tell users so. If your procedure has inherent risks, please tell users what they are. For example, if you're teaching someone how to change a database table, please include a disclaimer that it MAY occasionally cause data loss. * Replies to questions that ask for help running legitimate software (albeit closed source or proprietary) that do not answer the question, but instead instruct the user that they should not be using that software on the grounds that it is not free serve only to frustrate and confuse the user and will be removed to make room for answers to the question the user asked at the moderator's discretion. The goal of this forum is to first provide technical assistance and then to educate users on the benefits of free software.

The MaNGOS Forums are intended to be development forums and a community gathering place for users of MaNGOS. As such, it was decided from the beginning that everything posted here should be completely safe for work, i.e. if your boss is looking over your shoulder he would believe that you are doing some research that could be reasonably construed as work related. When posts in threads are reported to moderators we receive a notice showing which post was reported, by whom, and with whatever explanation they chose to write to us. We read them all and take them very seriously. In an average day we have less than 10 non-spam posts reported. Out of those, all are read by as many of us as are able and about 4 or 5 require some sort of action -- usually we are informed that a user posted in the wrong forum so we simply move the thread to the proper location. If you find a post that you feel is in violation of the spirit or the letter of the forums policy or the MaNGOS Code of Conduct, please use the report post function next to the post number. Please include a clear note describing the problem, this could be one word, "spam," or a couple of sentences explaining a situation. The moderators' and administrators' time is spent primarily trying to do tech-support, help keep the forums running and clear of spam and such, and moderate discussions that are off topic. We are all volunteers and the time we have to spend in these forums varies greatly. Some of us are here for several hours daily, some are here less often, some have great technical skills, others are more skillful at interpersonal communication than with fixing bugs and such. We vary in age from teenagers to people in their 40's (and 50's? I should check...) The administrators and staff keep a careful watch for people who are consistently helpful in their posts with tech support and who regularly demonstrate kindness, patience and good manners and on occasion we issue invitations for those people to join the staff. The big downside is that our time is limited and these forums do not pay us to be here, we all have outside responsibilities that call us away, sometimes for days or even weeks at a time with little to no interaction here. As a result, there is always a juggling act going on among the staff...how do we take care of the needs of such a large, growing community with our limited resources. The answer: we do our best and hope it works. When we find things that violate the forum policy, either because we stumble on them or because they are reported, we generally issue either an infraction or an infraction warning. In either case the user receives a private message with comments written by the moderator who issued it. When we are able we like to send a personal private message, but we are a rapidly growing (and very large) community and our time/resources are limited. This solution isn't as personal as we would prefer, but it generally works. In cases needing more direct involvement we may edit posts or move them to the jail. Sometimes we blow it and make mistakes ... either because we were distracted, we misunderstood (English isn't the first language of all of the staff members), or we just had a bad day. If you notice or believe we made a mistake, please inform us (preferably in the most polite way possible) of the problem in the Resolution Centre and an administrator with jump in to help. If it's just a small thing, feel free to send any of us a private message or just hit the "report post" button and type up a description of the problem. We don't want a lot of impoliteness or rude behaviour, and we generally try to steer conversations to stay to development and tech support related topics -- there are lots of other internet forums available for the sorts of conversations we don't allow here. Yet, community is very important to us, so we want to have a place for that to develop as well ... it's kind of like the break room at work, only without the donuts. Posts are not deleted except by the request/permission of the original poster or in especially egregious cases like posting of porn, etc. In general, offensive posts and spam are put into a section called the jail where staff and the original poster can peruse them, and are only modified to remove stuff like spam links or really offensive things. When the users posting in the MaNGOS Forums police themselves and avoid rules infractions (which is most of the time) the forums run smoothly and are a very pleasant place to hang out and receive good help, and that's how we want it. When users choose not to play nice, that's when we step in--solely to try to ease tensions, eliminate bad attitudes, remove spam, and let the forums fulfill their design and purpose. (Note: for a full job description and staff guidelines please see the forum policy, section III.)

Mirek added, so let's just say: Welcome :-)

Please try to include the following information: * What bug does the patch fix? What features does the patch add? * For which repository revision was the patch created? * Is there a thread in the bug report section or at lighthouse? If yes, please add a link to the thread. * Who has been writing this patch? Please include either forum user names or email addresses. Some additional hints * If there is no bug report thread for a bug fix patch you do want to submit, please create a proper bug report first. * Please make sure, that the patch submitted only contains changes for the particular bug fix or feature addition and no other changes. * Whenever possible, run a git-pull prior to making patches. If possible use the current git revision to create your patch. * Please add comments to your code. If you add new features, try to add Doxygen comments. * If your patch is only small (read: not more than 20 changed lines of code), you can use the CODEBOX tag to include the patch in your post. * For larger patches, use paste2.org to upload your patch.

Greetings, as I am currently rewriting the configure build system from scratch (see theluda-dev branch) I thought it might be good to keep a list of useful documentation resources. Especially as writing portable and reliable GNU autotool scripts is such a horrible thing. So here come my first sites: GNU Autotools * Autobook: Autoconf, Automake, and Libtool* Autoconf: Learning Autoconf and Automake Protocol documentation* OSCAR: the ICQ protocol documentation. You may ask why I add this one. Answer: because OSCAR protocol is a pretty good example of how we could document the communication protocol MaNGOS uses.

MaNGOS is an object-oriented Massively Multiplayer Online Role-Playing Game Server (MMORPGS). It's an educational project, to help developers get familar with large scale C++ and C# development projects. Version 0.6 introduces a lot of improvements, and feature completions since MaNGOS 0.5 has been released. Please note that release 0.6 still is considered alpha quality and not yet ready for prime-time. The following list only gives you a higher level overview, for further details see the ChangeLog file included in the source releases. Version 0.6 news: * MaNGOS development moved to http://sourceforge.net/projects/mangos/ * A lots of speed improvements to data handling and data transfer have been completed. * Mail, auction house, profession, creature, and game object systems have seen a lot of improvements and can be considered feature complete. Some minor bugs still are left. * Rest system has been finished. * Initial pet stable support has been added. * PvP and duel system have seen lots of improvements * Guilds are not just a myth anymore. Coming closer to full guild support. * Taxi and transport system is close to a fully working system. * A lot more has been added. Downloads: The project sources are available for download as compressed archives in GZip and Bzip2 format, and are available for download through the SourceForge.net download system. Get the 0.6 archives from the SourceForge.net download system With kind regards, the MaNGOS project team

Title says it. Gather log files and post them here. Prefered upload location would be filebeam.com. Use mangosonly as password. I will log data by sniffing the new 2.0.1 client on the test realms for the next four weeks until BC gets released. Only log files for that client (and subsequent ones) will be posted here. /~theluda/logs/2.0/ is the URL and you will need to use your account for svn.mangosproject.org, to authenticate.