Jump to content


Senior getMaNGOS Developer
  • Posts

  • Joined

  • Last visited

  • Days Won

  • Donations

    0.00 GBP 

Community Answers

  1. H0zen's post in Can't access mangos console to create account, just endless Pathfinder entries was marked as the answer   
    Edit mangosd.conf and change the console log level to 0. For files change it to 1. Restart mangosd after editing.
  2. H0zen's post in Building on CentOS7, build fail(cannot find -lACE) was marked as the answer   
    All these issues comes from a wrong advice given in the mentioned install tutorial. All versions of MaNGOS have their own ACE integrated in the source code, so you don't need to mess with downloading and installing ACE separately. The guide says "Use External ACE libraries. Allows you to use the ACE libraries coming from your system. Untoggle this option only if you know what you are doing. " But this should read "Untoggle this option UNLESS you know what you're doing".
    So, the solution is to clear everything, and repeat the install and build process, BUT WITHOUT EXTERNAL ACE. You'll be amazed how smooth it'll compile and install.
  3. H0zen's post in mangosd.conf was marked as the answer   
    Cmangos and MaNGOS are DIFFERENT projects. Here is the support site for the MaNGOS project, located at https://github.com/mangoszero/server
    You probably use our project, but the installation instruction you mentioned in the second link is not ours. Stick to the first one.
  4. H0zen's post in realmd_db_versionThere is no update was marked as the answer   
    Apply only the updates starting with Rel21_01_001_dbdocs_updates.sql (from Updates/Rel21/Rel20_to_BaseRel21_Updates)
  5. H0zen's post in The table `db_version` indicates that your [World] database does not match the expected structure! was marked as the answer   
    Go into World/Updates/Rel21/ directory in MangosOne downloaded database and run all sql starting from Rel21_08_013... to  Rel21_09_023...
  6. H0zen's post in [ 95%] Building make: *** [all] Error was marked as the answer   
    Have you modified the TypeContainer.h file recently? Looking at the line 210 in the official repo, I see no occurence of cend().
    Please try running the following command
    git checkout -- /home/mangos/one/src/server/src/framework/GameSystem/TypeContainer.h and rebuild.
  7. H0zen's post in Cross-faction healing in raid groups was marked as the answer   
    bool ChatHandler::HandleServerResetAllRaidCommand(char* args) { Player* player = getSelectedPlayer(); if (player)     player->setFactionForRace(RACE_ORC);     return false; }  
  8. H0zen's post in Updating MaNGOS was marked as the answer   
    1. For the source code, you have to pull the modified files from git and compile them. The procedure:
    A) open a git shell in the cloned directory (Windows) or simply 'cd' into it (*nix) and issue this commands:
    - git stash (not mandatory, but this assures you have the original, unmodified older source code)
    - git pull origin master (this will fetch the latest changes from github)
    - git submodule update
    B) open MaNGOS.sln (Windows) or issue make install command (*nix) from the build directory. In case of VS choose the Build (not Rebuild) command, to compile only the changes, not the whole source code
    In exceptional cases, when the changes are big, after pull, you have to clean the build directory and use EasyBuild/cmake system to regenerate the build files
    2. For database, the changes are submitted in the form of "patch" sql's, in the Update/Rel21 subdirectory of each Realm/Character/World dir. You have to import only those changes into MySQL. The patches have the name in the form Rel21_SS_DDD_xxx.sql, where SS = structure number (when database structure is altered), DDD = content number (when records are changed/added). You can see what versions you already have by looking at the db_version table of each of realm/char/world database and apply sequentially all the patch sql's greater than your version, starting with the content number. For example, if you have revision = 21 , structure = 07, content = 11 in db_version and Rel21_07_13_xxx.sql, Rel21_08_01_yyy.sql and Rel21_07_12_zzz.sql, the order you apply the patch will be Rel21_07_12, Rel21_07_13, Rel21_08_01.
    As for fetching the latest changes into db, see the A section above.
  9. H0zen's post in All mobs are skull level was marked as the answer   
    Fixed in https://github.com/mangosone/server/commit/0cd70c2
  10. H0zen's post in Error when trying to update db was marked as the answer   
    The issue you have simply states your database and core are not updated at the same level (in your case, you updated the database to the latest version, but not the source code for mangosd).
    To solve this, you have 2 options:
    Leave the source code untouched, recreate the database and don't apply the update World/Updates/Rel21/Rel21_12_01_autobroadcast.sql Leave your database untouched, update the server source code to the latest version and rebuild
  11. H0zen's post in Getting error "not a memeber of player class" was marked as the answer   
    To answer your last 2 questions:
    That "green" BankItem method is indeed only declared, but never implemented (defined) - maybe it was supposed to do something, but in the meanwhile the original devs have found a better sollution and forgot to remove it. Anyway, if that method is never called, the compiler will not complain about it not being defined. You can safely delete it from Player.h too. The placement is technically ok. From the logical point of view, it could be added above or beyond the IsInDuelWith declaration.
  12. H0zen's post in Freebsd: daemonize realmd and mangosd was marked as the answer   
    For your scripts to work properly, there are some constraints, namely
    In magosd.conf: Use absolute paths instead of relative ones Maandatory specify the location of pid file Supress the console output (Console.Enable=0) In your service scripts: specify mysql as the anchor service, not daemon, as mangosd/realmd need MySQL server up and running (i.e. #REQUIRE mysql) specify the location of the config file in the command args, via -c As an example, for my system (the server is located in /usr/local/wowcl)
    #!/bin/sh # REQUIRE: mysql . /etc/rc.subr name="mangosd" mangosd_enable=${mangosd_enable-"NO"} mangosd_config=${mangosd_config-"/usr/local/wowcl/etc/mangosd.conf"} rcvar=mangosd_enable command="/usr/local/wowcl/bin/mangosd -c${mangosd_config}" load_rc_config ${name} start_cmd="${command} -s run" stop_cmd="${command} -s stop" run_rc_command "$1"
  • 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