-
Posts
2819 -
Joined
-
Last visited
-
Days Won
96 -
Donations
0.00 GBP
Content Type
Bug Tracker
Wiki
Release Notes
Forums
Downloads
Blogs
Events
Everything posted by antz
-
Encrypted Letter - quest 3102
antz commented on caligineux's bug in Archived Reports (Zero)(Resolved issues)
@caligineux - Do you have GitHub userid ? so that we can credit you correctly. If you have the email address that goes with it, can you pm me with it ? -
enum WardenCheckType { MEM_CHECK = 0xF3, // 243: byte moduleNameIndex + uint Offset + byte Len (check to ensure memory isn't modified) PAGE_CHECK_A = 0xB2, // 178: uint Seed + byte[20] SHA1 + uint Addr + byte Len (scans all pages for specified hash) PAGE_CHECK_B = 0xBF, // 191: uint Seed + byte[20] SHA1 + uint Addr + byte Len (scans only pages starts with MZ+PE headers for specified hash) MPQ_CHECK = 0x98, // 152: byte fileNameIndex (check to ensure MPQ file isn't modified) LUA_STR_CHECK = 0x8B, // 139: byte luaNameIndex (check to ensure LUA string isn't used) DRIVER_CHECK = 0x71, // 113: uint Seed + byte[20] SHA1 + byte driverNameIndex (check to ensure driver isn't loaded) TIMING_CHECK = 0x57, // 87: empty (check to ensure GetTickCount() isn't detoured) PROC_CHECK = 0x7E, // 126: uint Seed + byte[20] SHA1 + byte moluleNameIndex + byte procNameIndex + uint Offset + byte Len (check to ensure proc isn't detoured) MODULE_CHECK = 0xD9 // 217: uint Seed + byte[20] SHA1 (check to ensure module isn't injected) }; The code above is lifted from Warden.h - These are the types is checks that can be processed by Warden
-
Warden is a automated cheat checker which when enabled will check for any exploits being used on the client machine. - It's not perfect, but adds an additional level of security to the server.
-
We have had two branches: Release20 and develop21. develop21 was supposed to be a temporary dev branch, but has been in use for over a year. Well, as of today they are now merged as a single master branch !! I have updated Appveyor and Travis (our test tools) to point to the new branch.
-
Our work towards the 2016 Roadmap didn't quite go to plan ! Instead the time was spent fixing up specific long term bugs and correcting missing / broken content. To that end, most of the main points of the 2016 roadmap are carried over to 2017
-
Goals for 2017 For 2017 the following are what we would like to achieve: Release Version 21 for Zero, One and Two containing all the recent updates and fixes we have. Release Version 21 for Three and Four - which will involve a massive amount of work to get these cores up to date. Redo the server commands to make them a bit more standard and obvious. Break out AHBot into its own daemon process Develop a mangos update daemon, which allows the ability to apply DB content and minor updates automatically Create Editors for the other xxxdocs systems (we currently only have a dbDoc Editor) Normalise the character DB and remove data blob fields Continue to standardise the code across the cores where its appropriate to do so. Document where it differs and why. Move some hardcoded values from the core into the DB, possibly some enums as well. Implement Stormlib library for Zero, One and Two and remove mlib Apply the Unified Extractor to Three and Four (requires stormlib) Look at removing DBC usage from the Core and change the extraction process to include importing into a DB for use by the core. Including Multiple locale support. This would facilitate the removal of stormlib / mlib from the core and only be needed by the extraction tools. Finish implementing the database localisation and allow localised db content to be loaded and edited. Including a localisation editor to allow localised translations to be created/edited by users. Look at Adapting EAI to match SAI functionality. As well as some of the more obvious ones: Clear down reported bugs on the Project Tracker. Improve the World Database with updates and corrections. Improve the Wiki Documentation. Include some example Eluna scripts to assist those starting out learning to script with Eluna. Include some custom Eluna scripts to help showcase it's abilities. Finally, we would like to get into a twice yearly Release cycle of more major releases. MangosVB (Formerly Spurious) RoadMap for 2017 Add RealmDB from c++ Mangos and modifying MangosVB to be compatible with it. Work out how to get MangosVB to use the standard Mangos map format. Finishing warden functionality (so it can use/read signatures from DB) Merge all of the changes from Zero to One and Two Investigate into voice functionality for One / Two Doing spells.. implementing them like stealth and getting a proper DB script system in place Getting it compiled and running under unix (using mono)
-
Mangos Zero branches are now merged
antz commented on antz's blog entry in The Road to Zero Release 21
Something we initially overlooked was the Appveyor and Travis configurations - These are the automated test systems for the code !!! Although the files in the repos were modified to point to the new branch name there was something else that needed to be done. - In both Appveyor and Travis they needed to be told which branch to get their config settings from, so they also needed to be updated. -
I spent most of yesterday in hospital having a minor operation done, since i'm home and a little drowsy.... decided it's best if I don't touch anything important
-
@Unkle Nuke has completed the merging of the various branches of Mangos Zero server and database repos and I'd like to express my gratitude for his work on that as it was not an easy task. You might want to re-clone your repos to ensure that you now have the latest changes !! He is now turning his attention to Mangos One and Two to perform his magic there too !!
-
With Mangos Zero (and too a lesser degree Mangos One and Two) we have been developing on the develop21 branch, while the master branch has remained untouched. This was only supposed to be a short term thing and has ended up being continued for over 2 years. Part of the changes will be to merge the two branches into a single branch again (master) and we will only use another branch when adding special development tasks which require group input. @Unkle Nuke has volunteered to help make this happen as his knowledge of git is vastly superior to my own.
-
It's been a long long time since we last did a full release of Mangos (any of the cores) and it's long overdue. This is a blog to explain what we're doing and why, plus should hopefully act as a guide for when we do this next time.
-
mangos zero Windows installation guides
antz replied to madmax's topic in Peer to Peer Technical Support
Glad you got there in the end -
mangos zero Windows installation guides
antz replied to madmax's topic in Peer to Peer Technical Support
@rsouzalmt EasyBuild is located in the win folder of the server repo -
Configuring the Client to point to your server These instructions vary slightly based on the version of the client you are using. For Classic / MangosZero or TBC / MangosOne, realmlist.wtf is in the root of the game folder. For Wotlk / MangosTwo, Cata / MangosThree or Mop/ MangosFour, realmlist.wtf is in the data/{locale} (i.e. enGB) off the root of the game folder. For Wod / MangosFive, config.wtf is in the wtf folder off the root of the game folder. 1) Open the file realmlist.wtf (config.wtf for Wod) using Wordpad. you will see lines like: SET locale "enUS" SET portal "us" SET realmList "us.logon.worldofwarcraft.com" SET patchlist "us.version.worldofwarcraft.com" 2) You need to change the realmlist and patchlist lines to the address of your server, Either: The value used for localaddress if you are inside the network (i.e. a LAN user) or The value used for address if you are connecting to the network from outside the network (i.e. a WAN/Internet user) Assuming this is a Local LAN user and the address of the server on the network is 192.168.1.209, you would change the lines too: SET realmList "192.168.1.209" SET patchlist "192.168.1.209" 3) Now save the file, then close Wordpad
-
Configuring the Realm Database 1) Open a command prompt and type IPCONFIG. 2) Find the IP address shown against IPv4 Address: (In this example 192.168.1.33) - This is your local address 3) Open a browser and visit: http://www.whatsmyip.org/ - You should see a message like: Your IP Address is: 170.21.133.118 - This is your external IP address and will be different on your system !! 4) Using your normal Database management tool, open your realm database (default name is realmd) 5) Open the table realmlist 6) Enter your external IP address (170.21.133.118) into the field 'address' and your local IP address (192.168.1.33) into the field 'localaddress' 7) Save your changes
-
Configuring MaNGOS Once all the files are on the server it's now time to pull things together. This can be one of the most frustrating steps to do, but with a little patience it’s easy. 1) Navigate to the folder where you copied the compiled mangos server and data files 2) Open mangosd.conf with WordPad 3) Find the following lines:- DataDir = "." LogsDir = "." Change these to:- DataDir = "data" LogsDir = "logs" 4) Find the following 3 lines:- LoginDatabaseInfo = "127.0.0.1;3306;root;mangos;realmd" WorldDatabaseInfo = "127.0.0.1;3306;root;mangos;mangos0" ScriptDev3DatabaseInfo = "127.0.0.1;3306;root;mangos;mangos0" CharacterDatabaseInfo = "127.0.0.1;3306;root;mangos;character0" You need to change the following:- root to the username you use for the database. mangos to the password for the user for the database. Then you need to set the name of the databases to the names you created earlier: realmd = The Realm database name mangos0 = The World database name used by both the World database and ScriptDev3 Engine character0 = The character Database name 5) Save the file then Close WordPad 6) Open realmd.conf with WordPad 7) Find the following line:- LoginDatabaseInfo = "127.0.0.1;3306;root;mangos;realmd" You need to change the following:- root to the username you use for the database. mangos to the password for the user for the database. Then you need to set the name of the databases to the names you created earlier: realmd = The Realm database name. 8) Save the file then Close WordPad. 9) Open aiplayerbot.conf with WordPad 10) Find the following line:- AiPlayerbot.Enabled = 1 Change this to: AiPlayerbot.Enabled = 0 11) Save the file then Close WordPad.
-
Extracting Game Data This guide assumes that you have copied the contents of the tools folder (the result of a build of the source code) into the root of your client folder. i.e. Where launcher.exe and wow.exe are located !! 1) Run 'ExtractResources.sh' and follow the onscreen prompts, you should choose the option to extract everything. 2) You will be asked how many CPU's to use for extracting MMaps (1 to 4) - The more CPU's the faster the MMaps extraction 3) You will then be asked whether you want to delay MMap extraction, just press enter for no delay. 4) A summary will be shown of your choices, press enter to start or CTRL+C to cancel the script 5) Several hours later you should see a message similar to: Finished creating MoveMaps 6) Navigate to the client folder and select the DBC, Maps, MMaps and VMaps folders and move them to your server folder 7) The “Buildings” folder can be deleted.
-
How to use EasyBuild EasyBuild is a 'Helper' utility to simplify the cmake build process. It also will check any of the prerequisites needed for MaNGOS and show you the current status. 1) On starting the app the following screen is shown, click 'Check Now' 2) If any of the required 3rd Party libraries are missing, it will tell you and provide links to them to download. You can also click on the 'DOWNLOAD ALL REQUIRED LIBRARIES' button which will display the following screen: Here you can tick the libraries you want and download / install them all at once. Care should be taken to not mix 32/64 Bit versions (apart from OpenSSl which doesn't care). 3) Once all the prerequisite libraries are installed, the 'Build Options' button becomes available. Click the 'Build Options' button to show the next screen. 4) The Following screen sets the modules and options to be included in the MaNGOS server. Build Folder: This is the folder where the required visual studio solution files will be created. *NOTE: NO SPACES IN PATHNAME* Output Folder: This is the folder where all the final files will end up. *NOTE: NO SPACES IN PATHNAME* OS Version Build: Either Win32 or Win64 - This is normally selected automatically ! Visual Studio Version: This selects the version of Visual Studio installed, if there are multiple versions install - they can be selected here. Build Type: Specifies whether to open visual studio with either Debug or Release Logging Level: Selects the level of logging to be shown onscreen - Show full log is the default Pre Generate Options: 'Delete Build Folder' - This clears the build folder before building, Ticked by default. Post Generate Options 'Open .sln Folder' - This will open the Visual Studio build folder. 'Build Mangos' - This will build mangos using msbuild with the progress messages appearing in easybuild. Ticked by default. 'Open Output Folder' - This will open the output folder on completion of the generation step. 'Open .sln File with VS' - This will automatically launch Visual Studio and open the project once the generation step is complete. Server Build Options 'Include Main Server' - Builds the mangosd daemon which is the main world server. 'Include Login Server' - Builds the realmd daemon which is the main authentication server. 'Include Extraction Tools' - Builds the client data extraction tools. 'Include SOAP Library' - Includes the SOAP library in the Main server. 'Include PlayerBot AI' - Includes the PlayerBot AI library as part of the Main server. Scripting Engines 'Eluna Scripting Engine' - Include the Eluna LUA scripting engine as part of the Main server 'ScriptDev Engine' - Includes the ScriptDev3 scripting engine as part of the Main server. 5) Click on the 'BUILD PROJECT' button to generate the Visual Studio Solution files. If you had 'Open Solution File' ticked, Visual Studio will open automatically. Otherwise the Output folder will be opened TROUBLESHOOTING If when you click 'BUILD PROJECT' button you get the following message: The C compiler identification is unknown The CXX compiler identification is unknown CMake Error at CMakeLists.txt:35 (project): No CMAKE_C_COMPILER could be found. CMake Error at CMakeLists.txt:35 (project): No CMAKE_CXX_COMPILER could be found. Here is the solution. When you're installing Visual Studio 2017/2019 Community on a new system you need to install the desktop development kit c++ with it. Especially the Windows SDK needs to be installed right (you can do that within the install-wizard of visual studio). After doing that the error disappears and you can build your solution!
-
Installing VS2015 Community Edition NOTE: Before continuing, we would advise using VS2022 or VS2026 to build MaNGOS rather than this ancient version. This install assumes that the Windows OS is patched to the most recent, VS2015 is a bit picky on the version it will install on now (blame MS not us). 1) Download the installer from: VS2015 Community Edition Other Versions can be downloaded from: VS - Older Versions 2) There are some settings which must be changed from the defaults for MaNGOS to work correctly !! NOTE: Skipping steps 3 and 4 will prevent MaNGOS from building correctly. 3) Change the option from 'Default' to 'Custom' 4) Expand 'Programming Languages' and tick 'Visual C++' 5) The rest of the install is standard. 6) It should also install any VS updates as part of the install. 7) To check that the VS2015 is correctly installed, try to create a new c++ solution (Win32 Project). 8) You may get asked to pick some default project settings, just click through. If you get to a screen similar to the following, then you are good to go and you will be able to build mangos.
-
Installing Mangos on Windows There are multiple ways of installing MaNGOS, this method will be using EasyBuild (a MaNGOS written tool) to simplify the process. 1) Although there are several pieces of third party software that are required to be installed, only two need to be installed prior to running Easybuild. Git (See HERE for the Install Guide) and Visual Studio (See HERE got the Install Guide) Both need to be installed before continuing. If you don't have them installed... go do that now !! The rest of the third party software required for MaNGOS are: Cmake (See HERE for the Install Guide). Only 32 or 64 Bit can be installed, not both. OpenSSL (See HERE for the Install guide). Both 32Bit and 64Bit can be installed together. You need the full rather than the lightweight version. MySQL (See HERE for the Install guide). Only 32 or 64 Bit can be installed, not both. 2) create a folder to hold all the source files i.e. Mangos_Files 3) Select the folder created above in explorer and right click on it, then select 'Git Bash here' 4) Clone the MaNGOS server and database GitHub repositories into folders in this folder (See HERE for a guide for cloning the repos) 5) Using explorer navigate to the server folder created above. 6) Navigate into the Win folder and double-click EasyBuild(If building MaNGOS three, run 'Patch_Easybuild_Mangos3' as the administrator before running EasyBuild). 7) Click CHECK NOW and let EasyBuild check for the MaNGOS dependencies. If your missing one, download and install it. 😎 Once MaNGOS finds everything it needs to build, click BUILD OPTIONS. If you want to change anything such as whether to build the extractions tools or not. The defaults are fine so we click on BUILD PROJECT. This will take a while so be patient. 9) If you look in the _install folder, all the require files you need on the server are there. 10) The contents of the tools folder need to be copied to where the wow client is located ready for the extraction process (see below). 11) Copy the remaining folder and files from this folder to your server folder 12) Extract the client data using extractresources.sh (See HERE to a guide to extracting the client data) 13) Now it's time to set up the database. 14) Select the folder created above in step 2 and then select dbzero(for MangosZero). 15) Double-click on InstallDatabases.bat 16) The initial settings as defaulted for the typical settings required for a new server setup but you might not want to create a new user right now so you press P then press N to continue. 17) The next few prompts are ask you to supply some key information to connect to your MySQL server, the text in square brackets [] are the default values if nothing is typed. Some of the settings are: Server Name / Address Username Password Port Character Database Name World Database Name Realm Database Name 18) The script will then proceed to populate all the databases and finish up looking like the following 19) At this point the database is now fully loaded. 20) On the server where you copied the files earlier, rename the 4 .conf.dist files as .conf 21) Now it's time to start configuring the server, first stop is adjusting the settings in the .conf files as described HERE 22) Now we need to configure the Realm Database to use the correct IP addresses as described HERE 23) Now the moment of truth... 24) Double click realmd.exe from the server folder, you should see a screen like: 25) Double click mangosd.exe from the server folder, you should see lots of messages like: 26) You now need to create an account to allow you to login to your server from the client: Type: ACCOUNT CREATE username password expansion (Where expansion is one of the following: 0 = Classic, 1 = TBC, 2 = WOTLK, 3 = Cataclysm, 4 = MOP, 5 = WOD, 6 = Legion) - This is also the max allowed expansion this account can use! NOTE: for mangos Zero, omit the expansion parameter. 27) and now for the the final step..... 28) One of the client files (realmlist.wtf) will need to be adjusted to point to your server, a description of how to do this is HERE 29) Start the your client(wow.exe),do NOT use the launcher, enter the account information created above and enjoy.
-
Installing GIT on Windows 1) First off, install Git 2.11.0 from the following location: 32 Bit 64 Bit or select another version from: General Downloads 2) Once downloaded run it ! 3) The install will display a variety of screens as shown below: 4) Git is now installed !
-
Changed Status to Completed Changed Implemented Version to 21.11
-
Fixed in commit https://github.com/mangostwo/server/commit/33a98b4868b7ad7cf4b934a53803bec14410b299
-
Changed Status to Completed Changed Implemented Version to 21.11
-
Fixed in commit: https://github.com/mangostwo/server/commit/33a98b4868b7ad7cf4b934a53803bec14410b299
Contact Us
To contact us
click here
You can also email us at [email protected]
Privacy Policy | Terms & Conditions

You can also email us at [email protected]
Privacy Policy | Terms & Conditions
Copyright © getMaNGOS. All rights Reserved.
This website is in no way associated with or endorsed by Blizzard Entertainment®
This website is in no way associated with or endorsed by Blizzard Entertainment®