Jump to content

pelle

Members
  • Posts

    157
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

pelle's Achievements

Advanced Member

Advanced Member (3/3)

0

Reputation

  1. works on trinity btw., should work on mangos too.
  2. there is probably a wrong dbc value, so soultions are: -edit dbc (illegal procedure) -write something on spelleffects.cpp/spellauras.cpp/unit.cpp -control values in the databse (for exemple the damage of some spell bonuses is inside spell_bonus_data) this is a script/waypoint issue, so from scripts (mangos use scriptdev2) or from db where are set coord of waypoint if your patch file is called patch.diff just patch -p1 < patch.diff
  3. i suggested this ( http://dev.trinitycore.org/trinitycore2/issue/899/fix-overkill-proc-after-vanish ) patch to trinity, should work on mangs too.
  4. i suggest to use this struct "patch -p1 < patch_name.patch" ...far better.
  5. does someone has the original link? thanks
  6. are you sure? i saw the same patch here http://spezies0815.datearea.de/ and it's not your....!
  7. ...and on its data field. the udb's wiki has something on that
  8. for exemple, i did a .patch files of my custom changes, downloaded 0.14 milestone and applied, compiled and all fine....
  9. i suggest to create a "clean" mangos branch (at same rev of you custom one), and the branch patched with your custom. do a .patch with "git diff master..custom > changes.patch" and youll get all your custom changes in a single patch file. now switch to master branch and uptdate, delete custom and make a copy of master ("git branch -f custom") and apply patch ("patch -p1 < changes.patch"). after that check for errors and you can compile. Fell free to comment
  10. in every debug logs i can see many <value optimized out> after some variables, what does it mean? using mangos 0.14 at 8478, on ubuntu server.
×
×
  • 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