Jump to content

Search the Community

Showing results for tags 'mangos'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Categories

  • Mangos Zero
    • Enhancement Requests (Zero)
    • Tasks (Zero)
  • Mangos One
    • Enhancement Requests (One)
    • Tasks (One)
  • Mangos Two
    • Enhancement Requests (Two)
    • Tasks (Two)
  • Mangos Three
    • Enhancement Requests (Three}
    • Tasks (Three)
  • Mangos Four
    • Enhancement Requests (Four)
    • Tasks (Four)
  • Mangos Five
    • Enhancement Requests (Five)
    • Tasks (Five)
  • Cross-Core
    • Bugs
    • Enhancement Requests
    • Tasks
    • Sub-Modules
    • Eluna
    • Linux
    • Windows
    • Archived Cross-Core/Other Reports
  • Others
    • Mangos VB
    • Mangos Sharp
    • Third Party Software
    • Website
  • Bug Tracker Archives (Resolved issues)
    • Archived Reports (Zero)(Resolved issues)
    • Archived Tasks (Zero)(Resolved issues)
    • Archived Reports (One)(Resolved issues)
    • Archived Tasks (One)(Resolved issues)
    • Archived Reports (Two)(Resolved issues)
    • Archived Tasks (Two)(Resolved issues)
    • Archived Reports (Three)(Resolved issues)
    • Archived Reports (Five)(Resolved issues)

Categories

  • Development Roadmap
  • Documentation
    • Installation Guides
    • Playerbot AI
    • Standards And Practices
  • Tutorials
    • Advanced
    • Contributing to Mangos
    • Debugging
  • Reference Information
    • ClientFiles
    • Database Info
    • DBC Files
    • Other
    • Packet Info
    • Server Files
    • Server Components

Forums

  • MaNGOS Information
    • Announcements & Releases
    • Covenant-WoW.com Website - Official Mangos Test Servers
  • Community Discussion Areas
    • Introduce Yourself
    • Community Cafe
    • Community Input
    • Community Projects
    • MaNGOS University
  • Community Help and Support
    • Peer to Peer Technical Support
    • Frequently Asked Questions
    • Resources
  • Development & Patch Submissions
    • Development
    • Patch Submissions
  • Eluna LUA Engine
    • Eluna Central
  • International Help & Support
    • International Boards
  • Archived
    • Main Archives
    • Archive of Pre-2012 Forum

Categories

  • Mangos Zero
  • Mangos One
  • Mangos Two
  • Mangos Three
  • Addons
    • Classic Addons
  • World Of Warcraft Patches
    • WoW Patches
    • The Burning Crusade Patches
    • Wrath of the Lich King
    • Client Tools Patchers

Blogs

  • getMaNGOS
  • DBC handling for mangos
  • The Road to Zero Release 21
  • Necrovoice's development blog.
  • What the Heck happened to Antz and MaNGOS in 2018 !!
  • Other Wow Emu Projects

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Core


Skype


Discord


Website URL


AIM


ICQ


Yahoo


Jabber


About Me


Gender


Location


Interests

Found 15 results

  1. Unofficial MaNGOS CMS Hey guys, i'm here to write down some information about a Project which i'm working on, to get some information from community. The project come from a simple need, that could help many people on handling his server information, a Featured CMS for MaNGOS servers. Right now i'm writing based on MaNGOS Zero, maybe the simplest, but i'll sure make it Cross Version. Technical Informations Following the Languages used to develop: Php 7 (after MadMax advices) HTML 5 CSS 3 JavaScript External Framework used: Bootstrap AlertifyJS Swal TinyMCE jQuery CodeIgniter Which are the Main feature of CMS actually? (the percentage reppresent the Development status) 100% - Template Customization System 100% - Module Implementation System 100% - DB Layer Classes 40% - Page Builder 80% - Dynamic Menu Builder 100% - Integrated CMS/Server Login and Registration System 100% - Quest Section 100% - Armory - A Realm Character/Guilds listing section, with Character informations (using DB Layer) Some Implemented Modules: 100% - Realm Status - Realms information, about registered and online users (using DB Layer) 50% - Profile Tile - A tile with shortened user information, let you user know about his Account Status etc. (using DB Layer) 100% - Server Stats - Information about Registered Account and Statistics 100% - Horizontal Menu - A module that get from DB the Menu item and display as a Horizontal Menu 100% - Latest News - A module that show a Slider Carousel with Latest 3 news in Server As soon as possible i'll add a link to download and try by yourself the cms, Future feature that will be implemented (some from community advice): CMS Engine Section Installation Wizard (Not Available for the first release) Character, Guild and Items details [*]Admin Section 60% - Newsletter System 100% - News System [*]Game Master Section 100% - Istant Leveling System Not more available 100% - Character Info modify feature (MadMax) 0% -Invite a Friend Reward System Not More Available 100% - Character and Guild lookup (MadMax) I'm open to get Tips and Advice about how go on with development. Hope you appreciate this project! Cheers! Screenshots: Home Page - Mobile Responsive Home Page - Full Size Profile Tile: Armory Example: Quest Example:
  2. I'm not one for making big posts at MaNGOS but at this time we need to. We desperately need people with C++ (and a bit of cmake) experience to help us with a variety of issues. - The future of Mangos depends on it. I am not an experienced C++ developer and although I can normally work around the code and make fairly simple changes, when things go horribly wrong I can end up stuck. We are also currently down to one developer, apart from myself working across all cores and tools. Mangos needs you help if we are to continue !! Please contact either @madmax or @antz if you feel you can help out.
  3. What is MOTE ? Mangos Online Translation Editor or MOTE for short is a word based translation editor for MaNGOS, it aims to massive simplify the Adding / Editing of Translations for all the MaNGOS tables. Why is it MOTE different to other translation projects ? - It has been designed to be multi-core compatible, therefore sharing the translations of matching text between the cores. - By being word based, rather than entry based, the translation of a word needs only be done once and it becomes available anywhere the English word is used. - A simple user interface makes changing text very easy. The Initial login screen: (guest as the username and password will grant you read only access) The default main screen: Searching for bread* with German translations: Green means it has a translation, Red means is doesn't Clicking on an entry highlights it, and also updates the 'context bar' below the search results The 0123 shows which core it's for. in this example there are two entries, one which is present in all 4, and the other only present in M1,2,3 Double-clicking on an entry opens the translation edit screen: Double-clicking on an entry in the 'context bar' opens a screen to show how it's used: Clicking on either of the EDIT buttons will open the translation edit screen. If you would like to help contribute to the localisation effort, please contact @antz and he will provide you with the app and login credentials.
  4. Hi there, I am trying to compile Mangos on a Debian Server, but I've been unfortunate enough to get a bunch of errors in the process of doing so. I struggle quite a lot with building ACE Itself, is it possible to build Mangos without ACE? I tried to look over the forum for similar topics and I couldn't manage to find any, therefore sorry if this is a repost, or a common question. If you have any guides or tutorials that might be able to walk me through this tedious process, please hit me up with those bad boys. Thanks for your time.
  5. Hello everyone in the mangos community, I am building mangos two with easybuild, following the guide step by step but neither easybuild nor the mysql installer are detecting my visual studio installation. - I have followed the visual studio installation guide step by step on the wiki. - My visual studio version is 2015 as suggested - My windows installation is a fresh windows 7 on a new computer, nothing was installed prior all mangos tools I tried to reboot 2 times, nothing happened, i'm kinda lost right now ... Hope you'll be able to help and ask me anything that might help you understand the case, as I am not used to have problems Sorry in advance for my english which is not my native language, thanks ! Belziere
  6. Hi, little problem I followed the Windows build guide and managed to build Mangos Three, but I'm having problems with the extractor which seems to be missing parts. I can extract the map files and DBC files (I pick all the extraction options), all the creation options are greyed out, so after a few moments I'm left with a DBFilesClient folder and World folder containing a Maps folder, which then contains folders named after the zones, which are filled with *.adt files. When I rebuilt the solution, I had several failures, and I presume they all/most relate to the extractor, as I currently have realmd.exe running fine, but can't start mangosd.exe without these map files. Substitution doesn't seem to work, as it tells me they're from an non-compatible version. If I'm overlooking something, or you need a log file from the build, let me know what you need and where it should be.
  7. hey all once more. i know i do alot of threads but its for its about diffrent things. this time i look into a mangos server i have saved on github, you cant get it anymore for all links are dead. but i saw that i did not upload the datasae with it so i get it for a other repack. even if i dont know how i even get it to git in the first place:) and as allways this is older then current version but i want to might be able to get it up-to-date with normal mangos 2 for this is 3.3.5 i know it works diffrent back in the day this if form about 2012 but i wonder how can i fix the errors that pop up. i know not everything are erros and it do stuff but still. thanks for the help. i whould get a propper DB if i could. but there are no git repos for db or scriptdev. only cores. so its kind of hard to get it right then:) here are the db and the sever log.txt files. its in a rar file due to the db are 149MB database and log file now the log file are only 100kb instead of 230 that it was before. sorry for finding so many things i want to do hehehehe. but i guess thats for i been doing this for so long alot of the old systems dont work or are dead today.
  8. can someone make me world chat C++ script like this My ranks are: 1 VIP 2 Eventor 3 GM 4 Head Gm 5 Developer 6 Owner Ty very much <3
  9. I've been playing with Mangoszero now for almost two months (user only) and think I've got a pretty good feel for how it's to be used as well as some of its limitations. But, I started this adventure with the hope of getting back into development (I was part of the Kernel dev team at Microsoft for W7 but have been retired since 2003). So, as my first foray into the code, I'd like to begin by documenting the module architecture. By this I mean: Command and data flow: what modules are touched when some arbitrary client command, e.g., "/cast Flash Heal") reaches the server (mangosd.exe). Related to #1, how are the modules laid out (e.g., we used to do block diagrams from the user interface, through the main body of the code and back). Whoops. An alarm just went off and I have to drive to the airport to pickup my wife. I should say that I've looked through the various doc resources and have found nothing like this. So, if it exists a pointer to the docs would be very, very greatly appreciated. Cheers,
  10. Hello, dear Community. Would someone tell me how may I add ElunaLuaEngine to a core manually? I don't want to make any kind of advertise and if it is necessary I'll give you the name of the source or the source. I made a thread month ago and as far as I'm aware, Rochet told me that I have to add it "Manually", I've tried to add it with "Git Bash" commands, I was posting threads and nothing. The core is based on Mangos and I'm not sure why it doesn't include Eluna, but since it is Mangos I'm pretty sure that it's possible to add it, but as Rochet said, I've to add it "Manually" Regards, Spectral WoW
  11. For many many years, the Localisation effort for MaNGOS has been almost non-existent outside of the actual core changes to allow localised text to appear. This caused the translation effort to be organised and managed by small groups outside of mangos and over time these projects lost interest and died. In late 2016 we decided to try and change that !! We created a dedicated Github Organisation and Repositories to hold all the localised data, including preparation and installation scripts. This organisation is located HERE Following on from this, @antz has created a tool 'Mangos Online Translation Editor' or MOTE which massively simplifies the translation effort: More information on MOTE can be found HERE If you can help us which translations into the following languages: Korean, French, German, Chinese, Taiwanese, Spanish, Spanish (South American), Russian and Italian We would love your help, as would the MaNGOs community !!
  12. It has been a while since I have been here due to real life once again getting very busy, but I wanted to pop back in and make a small proposition to everybody in the Mangos community, and especially to those in the following categories: Community Manager Senior getMaNGOS Developer getMaNGOS Eluna Developer getMaNGOS Developer getMaNGOS Staff Especially to @antz @madmax @Necrovoice @Rochet2 @Talendrys @H0zen @Tuker @bdebaere (in no real order ) as I feel you all have not only the experience but the passion to provide valuable insights in a shared space. There is a fairly recent Reddit page created by a former The Rebirth moderator, which is also co-moderated by members of other projects such as Kronos, Warmane, Elysium, Nostralia, and is also frequented by members of the Cmangos project such as Killerwife. I feel that this Reddit page captures the feel of the community when we all still were together, aiming for a common goal. Please consider at least reading some of what is posted there, and maybe contribute to a conversation or two. This is a great way for us to reconnect with the community, and to also bring more people in as we try to improve not only Mangos, but the community we are all a part of and love. Please understand that I don't mean to post this as a promotion, but as an invitation. Our community has been broken for far, far too long, and a shared place where we can talk as a council is something that has been badly needed. Here is the link for the page itself, named LegacyRealms: https://www.reddit.com/r/LegacyRealms/ And here is a direct link to their full rule list: https://www.reddit.com/r/LegacyRealms/wiki/rules If anybody is unsure of how to use Reddit, please let me know here or in a private message and I will help. If you want to find posts of a specific topic just click the search bar in the top right of the Reddit page, then check the box that says "limit my search to r/LegacyRealms".
  13. I am going to try to keep this relatively short because this could easily be written into a book if everything was covered. I wanted to talk about some things that are going on in the community as a whole, that some of us here might not know about or understand. WoW emulation has always been a slow and chaotic thing to be a part of, with changes rolled out over periods of years and projects splitting after years of being a single project. When a project splits, it usually does so violently and quickly. I am going to talk very briefly about some subjects & styles of thinking within the community just so people are aware of what they are getting into, and what they will come in contact with. This is largely a work of MY OPINION. While much of this has verifiable facts throughout it, there is a lot that is what I feel I have seen and read by diving deeper into different parts of the WoW emulation community. Intellectual property vs. supply & demand Official legacy servers vs. private servers Open-source vs. closed-source Developers (project) vs. developers (project) Missing knowledge (about how the game worked) Core vs. scripts Blizzlike vs. non-Blizzlike Project members (non-developers) vs. project members (non-developers) Desire vs. action Developers vs. players Players vs. players Paid services vs. free of cost Now, I have arranged this list in the order I will write about the different topics, but also by a very loose order or progression through our time as a community. I will also be adding two quotes from a developer at Cmangos that they put into a discussion on the Reddit LegacyRealms page. Here we go: 1. Intellectual Property vs. supply and demand This is a topic nobody wants to talk about on any side of where they stand. Blizzard undeniably owns the legal rights to World of Warcraft, and all of the material and content officially released under that name from the company. Running private servers is a violation of intellectual property, and punishment can be enforced by law in severe cases. However, the most common legal action is to simply have a server shut down with a "cease and desist" letter, known as a C&D letter or CDL. Private servers came about as a desire to understand how an MMO works, but also as a means to start fan servers, which has been a practice gamers have done for games even before WoW (Dark Age of Camelot, Quake). Emulators avoid legal trouble by not including material owned by Blizzard in the files they distribute. This has not stopped groups from taking the open source tools provided by projects and opening small to large scale server projects. This is because Blizzard does not, has not, and likely never will have official legacy servers but these have long been wanted by the community, which takes us to point 2. 2. Official legacy servers vs. private servers This is a fairly short point to discuss because there is simply little point or need. A person new to the community might wonder why there is little point or need, surely there is hope! Not really. Blizzard has a business model of always moving forward, so you can already see where legacy servers would be a problem. Blizzard does likely still have the source code for World of Warcraft, but much of the official data regarding how the game truly worked is lost or being hidden. To further the problem, the code for classic World of Warcraft is frankly sloppy compared to the modern standards applied by Blizz or even serious indie developers. Bringing an entire 5GB game and server architecture up to modern standards would simply be a huge task (and here we are in the WoW emu scene doing just that). Things were further complicated when the Nostalrius private server team managed to get an audience with Blizz, only to ruin the already shaky reputation of the emulation scene. Private servers fill the gap where there is a strong desire to play legacy versions of the game but no official channel. 3. Open-source vs. closed-source Open-source is where the copyright holder allows the distribution and modification of their software for any purpose or person/group, usually in this case under the General Public License (GPL). Closed-source, or proprietary software is the exact opposite of this, where software may be shared or modified only within the terms of the Terms of Service that are provided by the copyright holder. While World of Warcraft is a closed-source game software, the emulation software projects are open-source software allowing them to be shared and changed at will. Since the great drama of the past where Mangos/Mangoszero split into the Mangos and CMangos projects, we have also seen the birth of other projects, and most notably of those others, Trinity Core. All of these projects are open-source and allow for downloading, sharing and modification. When a group or developer uses one of these projects, however, they might make some changes to the software and then claim that their version is now closed-source. This created a number of issues within the community as any meaningful fixes made by this now closed-source group are not shared back to the server software they used to make the server in the first place (Mangos, CMangos, Trinity Core). These types of server software have come to be known as "cores". The new trend in projects such as Felmyst and Crestfall is to create hybrid cores that no longer fall into the categories of Mangos, CMangos, or Trinity Core. These new cores are of course closed-source. In the modern day emulation community there is a general sense that Mangos, CMangos, and Trinity Core are not high enough quality on their own. Any server that is run using stock open-source cores is looked down upon as being unprofessional and under-developed. 4. Developers (project) vs. developers (project) It has been fairly common within the community for developers to attack other developers and projects through words and distributed denial of service attacks (DDoS). This is also done by fans of projects and non-developer members, but will be addressed later. Many of these old rivalries still hold back the advanced development of emulation technology today. Disagreements are bound to happen, but there is no central meeting point for developers to discuss their projects, or at the very least to share bug lists. This is because if one server were to have more bugs than another, developers could easily attack that less developed server as being inferior, harming the chances of survival. This happeed regularly on public the public Reddit page "wowservers" before only slightly tighter rules were brought into place. In the past, these fights were over IRC, or public forums. Little has changed in this regard. 5. Missing knowledge (about how the game worked) People new to WoW emulation and private servers often ask questions such as "Why can't we get _____ working?". When we first started to build the knowledge of server and game emulation we used a method known as "sniffing". Sniffing refers to the act of "packet sniffing" where a person would use software to watch and log the technical details of their own network activity in an effort to capture valuable technical details of how the game sent data, when, where, and why. This also was used to see what the server was sending back in relation to player actions. Unfortunately for us, the quality of these sniffs were not very good back in classic and TBC and even worse, most of them were not shared outside small groups. Much of the core infrastructure we have today came from low quality packet sniffing and estimated guesswork. There is still to this day quite a lot about how the game works that we don't understand in the form of flags and fields within the database. These could greatly increase the ease and access of implementing fixes to cores, but we simply do not understand them. Worse yet, as with the lack of sniffs, there is a large lack of classic data that is truly valuable or available as even web archives slowly push content out of their servers. Many players attempt to rely on their memory for how things worked, but even experienced players will find there is much they don't remember as well as they thought. 6. Core vs. scripts A lot of people confuse a core and scripts as being the same thing and will say something along the lines of "Server X is no good because they use stock Mangos/CMangos/Trinity Core cores." This is misleading because the core is actually overall less important to the player-game interaction than the scripts are. Scripting makes up a huge portion of what a player will see in regards to how a server operates. Few will ever see the gears turning behind the game. From a developer standpoint, both of these should be equal, but a developer will often prioritise the core and features is has, but a player will largely focus on scripting and especially the quality of that scripting. Here is where there is a large disconnect within the community. Most players will not understand that the core directly influences how diverse and complex scripting can be, but is not the same thing. This is changing quickly within the community as information is shared between developers and players. CMangos does a very good job in this regard as Killerwife is often seen explaining how things work from a developer standpoint. 7. Blizzlike vs. non-Blizzlike The great debate. What Blizzlike means seems to fall into several categories for different people. Firstly there is the idea that Blizzlike should mean "The game works as Blizzard intended it should from a technical standpoint." Second is the idea that "The the game experience should match way the retail version provided by Blizzard was." These don't always go hand in hand and different projects and developers prioritise these ways of thinking differently. This is almost 100% personal preference. Identifying the correct way something worked is a difficult task, so projects seeking a larger player base will often prioritise making the experience of gameplay more Blizzlike than the actual game functions. 8. Project members (non-developers) vs. project members (non-developers) This is not a new problem, but it has become much worse than what once existed. members of the Mangos, CMangos, Trinity Core, or individual server projects such as Kronos, Elysium, Crestfall, Felmyst or Warmane communities regularly attack each other and mock each other for fun and "memes" but also out of actual spite that some members hold towards the other groups. The bandwagon mentality is very strong in the current community and should be accounted for in all situations. This group is sometimes responsible for DDoS attacks on servers and project websites. 9. Desire vs. action A lot of people want to help in terms of developing a server or core, be it directly or as a member of the community by bug hunting and making guides or through other methods. What people want or say they want and what they do is often not the same thing. The general sentiment that is found within the emulation community is "I just want to play the game." Few people actually want to install a core software and seriously work on it or even bug hunt for it. Many become discouraged when a bug is reported, only to be told it isn't a bug or the time it takes to get a reply is too long, let alone a fix. I don't really think there is much that can be done to alleviate this problem, but maybe with people becoming more interested and aware of the way things work we will see people get more involved. 10. Developers vs. players This was touched on a bit earlier, and doesn't need a lot of explanation, thankfully. Mostly this is a disconnect between what a developer sees as what they should be doing, and what a player sees as what the developer needs to do. This also can take the form of actual verbal fights in rare cases such as when the Elysium admin Shenna snapped on the wowservers Reddit page, reply to criticism with absolute anger and expletive-laden lashing out. This type of conflict isn't too common within the community and usually comes in the form of a misunderstanding. 11. Players vs. players Much like the non-developer members of projects, the actual players themselves take this into the games and forums very often and is nearly identical to item number 8. I simply wanted to distinguish explicitly between the player and the non-player, non-developer interested person that sometimes hangs around within the community. Just as number 8, this group is sometimes responsible for DDoS attacks on servers and project websites. 12. Paid services vs. free of cost Finally we arrive at a bit of a newer way of thinking within the emulation community. In the past, most servers would only be successful if they mentioned that they were free and did not provide any paid services. This was also a way to prevent Blizzard from serving a CDL to a server. Now many players are largely becoming tolerant to the idea of paid in-game services. I say tolerant because many also don't seem to like it, but as long as no unfair advantage is given in return for payment, or where play is restricted by a lack of payment, most seem willing to ignore it. This usually takes the form of in-game vanity items such as World of Warcraft Trading Card Game pets, mounts, or other limited promotional items that would be otherwise impossible to get. Other popular paid services include name changes, server transfers, race changes, faction changes and similar functions (despite these usually taking less than 1 minute for a GM to do). Kronos takes this a bit further providing cosmetic and vanity services, as well as character auction where players may trade or sell characters for Kronos-specific currency on the character auction run by the project. Some players dislike this, and others say it prevents scamming that would otherwise happen anyway. Open donations also are considered acceptable by a growing number of players as long as those donations only go to the running costs of a server project. Other projects get targeted as a money racket for debatable practices, such as paying $10 U.S. to skip queues for server entry (Warmane). Many new projects very much see themselves as a business and as professionals. Development is often faster and of a higher quality on these projects, but we again see developers fixing the same bugs that have been fixed hundreds of times now. Finally I would like to just end this post by quoting Killerwife of CMangos with a post that was made on the LegacyRealms Reddit page where they answered questions regarding WoW-emu development. Seen here with this link: https://www.reddit.com/r/LegacyRealms/comments/6h7axd/would_anyone_want_me_to_answer_random_questions/ "1 - The reason is simply long years of development. Some data used in vanilla/tbc was reverse engineered from cataclysm client. Blizzard had what, 20 devs at least during TBC? And thats full time, voa has currently 5 enthusiasts developing several times a week, and the reality is the same with most servers. The reason i think is that Open Source provides a floor for server quality essentially, and as time goes on, it progresses further and further, so that anyone who is capable of cherry-picking will have a half decent server on their hands in no time. There weren't any major turning points, there were on the other hand major setbacks (trinitycore split with mangos, cmangos and mangoszero split). Today its seriously easy to set up a server, MYSQL, C++ and GIT (mangos started with SVN) are more accessible than ever and its super easy for people to start contributing anywhere. Also we have several projects' efforts culminating their skills, experience and progress, which is once again attributed to time spent on the subject (10 years in TBC) 2 - Maybe big servers seem to have it all figured out, but its a big NO. I am sure that if I were to hop on any server, including mine, I would be able to name a plethora of issues. There is a shitton of flags, fields and whatnot, which to this day we have no idea what they do, mainly because some were discovered by some small team and it was never shared. A good example is Zeppelins making horn sound when approaching their stop, this exists from TBC and to this day I haven't seen anyone have it, until I noticed it and implemented it on voa. Same goes with music tracks, for example in Black Temple a unique music packet is sent so that it plays during one encounter, and that encounter only. In terms of biggers thing, for example GameObject casting is a big thing noone has implemented yet, as of what I know. (and believe me, this is a mechanic of global scale) Or I also have not seen several spell attributes named (some of which more than 5000 spells have) which are somewhat generic rules for spells. Or castflags in spell packet, or proper Heartbeat resist, or proper immunities or unapply of Parry talent for shaman, and the list goes on, and on, and on. The reason why we are not done, is because due to egos, there is a shitton of teams who are not cooperating in this effort. This is one of the reasons why I share information, so that noone in my vicinity is working on the same thing my team is working on. To illustrate in terms of content, L4G and Wargate still shoot Prince Malchezaar Infernal out of his hand afaik, VoA doesnt have whole T5 released, Gummy afaik is missing questend emotes from my reports (this is extra funny since its 9 year old tech), Warmane has shoddy WOTLK regressions, and thats just the TBC scene. Also noone has ever properly scripted 40 man Naxx because there is close to no available data on it. I could ramble on, but I hope you saw the points I was trying to make." - Killerwife
  14. I'm having similar issues as others stated running mangosd as a service in Ubuntu. I can start it manually with the same command that is in the service but can not start with systemctl as described in the Ubuntu 16 install guide. My mangosd.service as described in the guide setup: [Unit] Description=WoW 3.3.5a After=network.target mysql.service [email protected] [Service] Type=simple User=mangos ExecStart=/home/mangos/two/bin/mangosd -c /home/mangos/two/etc/mangosd.conf StandardInput=tty TTYPath=/dev/tty3 TTYReset=yes TTYVHangup=yes Restart=on-abort [Install] WantedBy=multi-user.target My console output from systemctl status mangosd: [email protected]:~/two/bin$ systemctl status mangosd ● mangosd.service - WoW 3.3.5a Loaded: loaded (/etc/systemd/system/mangosd.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2017-05-27 17:12:54 EDT; 5s ago Main PID: 2208 (mangosd) Tasks: 4 Memory: 3.2M CPU: 30ms CGroup: /system.slice/mangosd.service └─2208 /home/mangos/two/bin/mangosd -c /home/mangos/two/etc/mangosd.conf [email protected]:~/two/bin$ systemctl status mangosd ● mangosd.service - WoW 3.3.5a Loaded: loaded (/etc/systemd/system/mangosd.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2017-05-27 17:12:54 EDT; 7s ago Main PID: 2208 (mangosd) Tasks: 4 Memory: 3.2M CPU: 41ms CGroup: /system.slice/mangosd.service └─2208 /home/mangos/two/bin/mangosd -c /home/mangos/two/etc/mangosd.conf [email protected]:~/two/bin$ systemctl status mangosd ● mangosd.service - WoW 3.3.5a Loaded: loaded (/etc/systemd/system/mangosd.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2017-05-27 17:12:54 EDT; 9s ago Main PID: 2208 (mangosd) Tasks: 4 Memory: 3.2M CPU: 48ms CGroup: /system.slice/mangosd.service └─2208 /home/mangos/two/bin/mangosd -c /home/mangos/two/etc/mangosd.conf [email protected]:~/two/bin$ systemctl status mangosd ● mangosd.service - WoW 3.3.5a Loaded: loaded (/etc/systemd/system/mangosd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2017-05-27 17:13:04 EDT; 636ms ago Process: 2208 ExecStart=/home/mangos/two/bin/mangosd -c /home/mangos/two/etc/mangosd.conf (code=exited, status=1/FAILURE) Main PID: 2208 (code=exited, status=1/FAILURE) [email protected]:~/two/bin$ My console output from manual start: ***************************** removed above this line for ease of reading ************************************ Player::DeleteOldChars: Deleting all characters which have been deleted 30 days before... Initialize AuctionHouseBot... AHBOT is Disabled. Unable to open configuration file ../etc/ahbot.conf. [Eluna]: Successfully loaded `lua_scripts/extensions/ObjectVariables.ext` [Eluna]: Successfully loaded `lua_scripts/extensions/StackTracePlus/StackTracePlus.ext` [Eluna]: Successfully loaded `lua_scripts/extensions/_Misc.ext` [Eluna]: Executed 3 Lua scripts in 1 ms _______________________________________________________ MaNGOS Server: World Initialization Complete _______________________________________________________ Server Version : 2106009 Database Version : Rel21.6.9 Supporting Clients : 3.3.5a Builds : 12340 Module Status - SOAP : Enabled Eluna : Enabled Warden : Enabled ScriptDev3 (SD3) : Enabled Remote Access (RA) : Enabled _______________________________________________________ SERVER STARTUP TIME: 0 minutes 4 seconds Starting Network Thread Starting Network Thread Max allowed socket connections: 1024 Starting Network Thread World Updater Thread started (50ms min update interval) Remote Access Thread started (listening on 0.0.0.0:3443) SOAP Thread started (listening on 127.0.0.1:7878) mangos> Thanks in advance!
  15. Hi, I cloned Server repo from github and started to build mangos from scratch. When I run the script 'server/sql/mangos.sql', mysql return the following error: I looked into the script and figured out the insert statement line 1327 for creature_template table. The table has 84 columns but the insert statement provide 85 values.
×
×
  • 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