Jump to content

VladimirMangos

Members
  • Posts

    2813
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

Everything posted by VladimirMangos

  1. it already applied...
  2. yes, this only affect maps, not vmaps
  3. This is not related to your problem. -1000000 is special value reporting that no _any_ data about height. New way for height storing not change anything for like cases. This totally unrelated.
  4. Patch backported to mangos-0.12. Please report any problems with this. Note: new maps for mangos-0.12 not compatible with new maps for 3.0.8a (as expected for different client versions)
  5. In [7294]. Thank you
  6. Possibel yopu use old maps that cleary not compatible I see same reports for old map code at old interpolation array use.
  7. Mangos not expect access to characters DB data by another ways while mangosd work. And you will not avoid problems without rewriting related DB data update code in more slow way. So any attempt use single characters DB by 2 mangosd will end by DB corruption.
  8. At each waypoint for creature with AI called unit.AI()->MovementInform(WAYPOINT_MOTION_TYPE, i_currentNode); So you can provided for creature simple script that will Unsummon self at last point...
  9. you write about lost items. Fxied problem only make its send to mailbox instead equip. Lost description is DB problem like case. Anyway we all make errors, and not always undersatand problem description.
  10. Thank you for fix. I will add it but with small chnages: function already have special arg not_loading for like checks. Added in [7279]
  11. Main reason against implementing any crash chatchers is: You can be sure that data in crash point still not corrupted. Batter crash and do restart with last saved _correct_ data in comparison continue work and use corrupted data later save its and lost character or all characaters progress at least back to last DB backup.
  12. For this not need chnage sources. Look in mangosd.conf options related to copse reclaim.
  13. This stop deley related to requirement save and diconnect players at stop. This required time. Patch added in [7271] Thank you
  14. UPDATE TABLE `realmcharacters`, <---- redundent comma
  15. added, thank you
  16. You can add new shift-link support with bg instance id as data and then added to 'bg end' support for using this shift-link. If you will have bg instance id output/shift link then you can for example .bg tele bg-link_or_id for tele not to specific character but to specific bg... Also maybe in like case good rename .debug bg to .bg debug... ?
  17. ah, you about "a pouch or a quiver". But note: this is not only existed specialized by allowed item types bags. And it's not different from similar for herbs only bags
  18. Talent is spell that apply aura to player. And then it can diabled in same way as any spell: by check in Spell::CanCast that not allow casting for this spell.
  19. Added patch allow this (in case item move to specialized bag (quiver) its must be allowed to place to it. bag swap with item move?
  20. Thank you for clarify. I not have time to fix this currently but i remember this for later fix.
  21. Anyone reset this talent at official servers?
  22. Patch in [7255] Thank you Problem with preparation spells fixed in [7253] Not mangos bug: ALWAYS use InnoDB for characters DB. If you not use this engine then this is not mangos team problem.
  23. In [7252] added some from version of this patch... Thank you
  24. In fact your patch only allowed in original state start bg with only single team minimal requirement but still req. this minimum. But this fixed in added version in [7252] and mangos-0.12. Thank you Ah, i apply version from simple_fixes.... [added] As i check this is same patch at branch. So move to accepted.
×
×
  • 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