Jump to content

DasBlub

Members
  • Posts

    450
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

Everything posted by DasBlub

  1. i'm not 100% sure but you should have a look into src/game/Player.cpp ps: totally wrong section
  2. still awaiting feedback (i'm getting bored from this, still no answer since weeks:()
  3. post full dump on http://paste2.org/ please
  4. nobody an idea? i tried to rebuild the documentation myself with doxygen, but the Doxyfile.in should be processed first with the Makefile, but neither nmake (visual studio) nor mingw32-make (mingw32 make (gcc)) can parse this makefile
  5. why you don't look at the table yourself? just type on the console this or use a graphical client: DESC spell_proc_event;
  6. you don't need an old revision. for the 2.4.3 version there's a branch. use this command after using git-clone: git checkout -b 243 origin/mangos-0.12 this will create you a LOCAL branch which points to the REMOTE branch. to update it use this command: git pull origin mangos-0.12 and to apply your patch: git apply path/to/patch
  7. ok, i did copy+paste from old code can now be found at github: http://github.com/DasBlub/mangos/tree/no_char_delete single commit: http://github.com/DasBlub/mangos/commit/bd83d0332ff099bc276e4410f6ec406099985e28 and as a patchfile (created with git show): http://paste2.org/p/142137 hope some dev will answer here and say if this will go into mangos repo
  8. ok, actually the OLD repo is available here: http://github.com/DasBlub/mangos_old/tree/no_char_delete i've just some problems with creating the patch... -.- i'll try it again and in worst case i'll do copy+paste
  9. i'll do it tonight (in 12hours or so...) i just renamed my repo from 'mangos' to 'mangos_old' because i'm going to set it up new and then create the no_char_delete branch with a single commit (which you can use then as a diff file). i'll do both, a no_char_delete branch for master and one for mangos-0.12
  10. ok, thanks for that info. what is with those "hughe" amount of patches in the patches section? are you going to review them once?
  11. and instead of the case-construct you can use eval(): message1="bla" message2="blub" mess=2 echo eval("echo \\$message${mess}");
  12. just to ask: how long will you keep supporting the mangos-0.12 branch?
  13. keep waiting, i'm bussy with other scripts, will take me some weeks to implement doflee
  14. how it has allready been written in the sd2 forum i'm going to implement it. i'm just waiting for the vid from x-savior (he will send it me just today ('soon' ))
  15. DasBlub

    Launcher Project?

    he does this to learn c++ and btw i hate java (not to be discussed here, neither related to this topic nor to this forum )
  16. DasBlub

    Launcher Project?

    what i'm waiting for is a little concept with a timemanagement until when you wanna have finished what and who will work on it.
  17. updated and still waiting for any answer from a dev... if needed i can recreate the branch so that this would be a single commit.
  18. DasBlub

    [fix] typo

    it fixes a typo. it doesn't change a functionality. it changes a write error
  19. DasBlub

    [fix] typo

    have you even looked at the patch? the only thing this patches changes is adding one little char to a function name...
  20. it's because the pointer in the iterator just was deleted (delete itr->second).
  21. next time add a link to the patch please, actually it's a nice topic but not a patch
  22. DasBlub

    Launcher Project?

    for gui you could use wxWidgets, this is platform independent and it ships also functionalities for networking and multithreading and stuff like that. have a look at this: http://wxwidgets.org/
  23. thanks, that was it (haven't found it in manual, but maybe i looked at the wrong place )
  24. ((Player*)m_caster)->CanFly should be so: ((Player*)m_caster)->CanFly()
  25. updated to newest mangos-0.12 version... http://github.com/DasBlub/mangos/commits/no_char_delete can any dev give once a feedback like "we're reving it in the next week" or "bad patch. removed" or "in git, [70XX]"?
×
×
  • 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