Jump to content

VladimirMangos

Members
  • Posts

    2813
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

Everything posted by VladimirMangos

  1. add cooldown check into aura cancel handler maybe...
  2. Add or remove spell at click selected by client.
  3. Infact most config options can be absent in to config because default values. Like config options explicitly listed in configs just for documentation for _possible_ modify. In one or another way you need some options documention. It can be in mangos.sql file if store in DB or in current configs.
  4. In any cases you will still need configs for provide DB connections options at least. Personally not see what so cool read option value from DB in comparison config file. Currently config file also can be reloaded with same effect.
  5. no problem, i delte post, but i not see reason ban you
  6. Hmm, by default cooldown set to triggered spell, so for one from randomly selected. Not nice but working sollution maybe set cooldown manually for _all_ spells from array for caster. This will prevent cast alt. spell at next triggering.
  7. only if use old outdated ad.exe from time when old .map files formal has been used.
  8. Yes, this way only possible in current state. Same way used for global loot in normal loot tables.
  9. no reason use dynamic filled vector. You can define in each case { uint32 spells[3] = {...}; triggered_spell = spells[irand(0, 2)]; break; } /*end case*/ }; break; not remember exactly variable name for triggered spell. And you don't must without strong reason do cast spell call instead allow do cast by normal way work code.
  10. Avoid lost allocated memory.
  11. small note:: need LL in end or (better) use U64LIT wrapper
  12. Prospecting/Milling spells normally not provide skillups for related gathering professions. Referenced options control of custom way work. Currently this true/false options. But maybe for custom way work will be better change code for have real chance (float) value 0.0..1.0 for skillup...
  13. as i remember Spell target proccesing code have some negative for target check code. If checks similar then maybe some way for make new function for check possible for reuse and compatibility
  14. I limited in mangos code view to repo html pages so hard for me follow all function uses. So I not sure that I can clarify case when you confirm that offline show state work without call.
  15. player _must_ be added to group if offline. For example, at login raid member other raid members must be show in raid list independent if its offline or not.
  16. static Player* GetPlayer(ObjectGuid guid) { return ObjectAccessor::FindPlayer(guid); } Note about static: ObjectMgr::GetPlayer(guid) better use. Player* ObjectAccessor::FindPlayer(ObjectGuid guid) { if (!guid) return NULL; Player * plr = HashMapHolder<Player>::Find(guid);; if (!plr || !plr->IsInWorld()) return NULL; return plr; } So you right for just get map case.
  17. > HashMapHolder<Player>::Find(guid); Why use it instead GetPlayer
  18. Only with broken script maybe... but script side task check player pointer before call core functions...
  19. Around each printf? this will horrible...
  20. I think use DB query is very bad idea for this. Offline group member must still store in group members list data for own map at last online point (it can do it already, or can be added).
  21. Just for note about VS IDE speed: i install VS 11 developers preview and look like IDE in it have some better performance. But i not test it work at mangos code.
  22. Your VS2010 not have x64 toolset and then it can't build x64 binaries. Or use x86(x32) build mode or look for reinstall VS with x64 tools.
  23. I also support suggestion for UncleNuke mod rights. > Also, I think I'm missing some permissions - I can ban users, but I can't delete posts. Very strange. We in same group look like but i can delete.
×
×
  • 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