Jump to content

VladimirMangos

Members
  • Posts

    2813
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

Everything posted by VladimirMangos

  1. With this changes and skips in [9007]. Thanks to all authors
  2. 27521 spell i thionk incorrect base at this remark at well known site: "It has in fact been specifically proven that this has no cooldown" Same for 55381 that have same data. 38299 spell possible must have 12s cooldown (so no proc while active) 55640, 55747, 55768, 55776,57345, 60436, 60442 already have same data in mangos.sql 57352 have diff data but i prefer limit currently to cooldown/and related part 61356 - i near to sure that coolodwn std: 45 instead 90, base at reference for 45 cooldown in same time as 90 and facts that it proc ~ 1 per minute that expected for 50% chance with cooldown
  3. it will applied in still need part and moved from section. No reason have continues threads in cases applied patch. Better create new for new case(s)
  4. Ah, while look for bugreports for some single cases found this thread. Sorry that not find it early...
  5. Why we can need trinity hacks? Anyway we not intresting in this. But we accept sometime patches prepared by mangos community members base at trinity fixes for specific problems. If this not hack fix and provided original author. But in general we not intresting what have trinity or not have. Closed.
  6. Forgot provide name: 48_hand_of_reckoning.diff In any case i will can't review its all in one step. Each patch need 30min-N hours for review/reseach better sollution
  7. DB part better discuss and suggest to used DB project. Also i will fix my fix: make it wild summon. Because it must be allowed used for some options by other from same team.
  8. And this will rejected in any case in original or this form. Hacking in spell dbc data just create problems at next client switch and not help to anything and can be done in proper way without like horriable hacks. Some from suggested patches related to already fixed cases. This is for example. In fact maybe has been better post patches one per bug/patch if it still need. Then its has been reviewed in normal mode.
  9. Summon part of type 12 fixed in [8997], but it need DB and possible core support for specific gossip cases/etc
  10. 1) crit damage reduced for any attacker types, in different from normal damage reduction 2) as i re-check we not reduce this for this type dot in other place.
  11. Reverse enginering client code illegal in some countries so don't must be discussed at this forum.
  12. this aura state can be look at client in some way? For some spell icon...
  13. In [8992]. Thank you. + replaced duplicates by spell chain data use + spell 51521 already have proper class family mask and then not need explicit mask data in table, only cooldown. For anyone recommend use sql update after update sources to next revison after referecned (i fix typo in it).
  14. Possible any. But answered from point: without big differences in code work, rewrites achievment system totally.
  15. master is 0.15 in fact I think about move to dummy but it work in current way. So i let it be in current state.
  16. laise, posting patches in bug threads is oftopic infact...
  17. I can clarify: when i close client in tree form at check and login i also see this buf with dropped line, but it not reapplied at tre foem next cast and never after. This just result auras save.
  18. In [8987] in last version. Thank you. + i also add explicit check swap operation data correctness.
  19. In [8986]. Thank you
  20. It's stored in dbc , so no.
  21. It not work with this code change at master. So 0.12 only change.Added in 0.12 sources. Thank you
  22. In [8985]. Thank you
  23. And how possible restore normal command icon for attack for example if you drop it?
  24. In [8980]. Thank you
  25. Why you see that it broken? I not see any problems with current way work. rejected.
×
×
  • 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