Hashira
Elite user
-
Joined
-
Last visited
-
This can be retrieved if you are at a trainer via https://wowwiki-archive.fandom.com/wiki/API_GetTrainerServiceInfo but ideally we won't travel there at all first. Before visiting the trainer, this is available via the spell book API: https://wowpedia.fandom.com/wiki/API_GetSpellBookItemInfo - this requires one to walk the whole book, the link contains information about this. `FUTURESPELL` spells are the ones that may be trained in the future. Then the API GetSpellAvailableLevel can retrieve from which level that particular spell can be used. This one can then be used to decide if the spell can be trained. See https://www.townlong-yak.com/framexml/4.3.4/SpellBookFrame.lua#640 for the client side logic.
-
Currently the bot may visit a class trainer even if there is no spell to be trained. It would be nice if in Cataclysm the bot would take into account the spell book information while deciding if it should visit the trainer or not: I guess the training state could be cancelled via "robotManager.Events.FiniteStateMachineEvents.OnBeforeCheckIfNeedToRunState", but I don't see any method in the Spell/SpellInfo/SpellManger that could return if a method is 'learnable' - is this something that can be added to the API ? (and maybe throw an error on other expansions, since WoTLK and lower would need static lists, and MoP and higher don't have training anymore).
-
-
-
Super cool. Is there a list of pre-registered events for `robotManager.Events.Events.CustomEventCancelable` or does it apply to any library function by default ?
-
-
-
-
The `Regeneration` state should have event handlers (`Start`/`Loop`/`End`) in order to allow plugins / fight classes to execute rotations. The use case is as following: - The bot doesn't have food - The bot needs to regenerate HP but has mana In theory the FC could spam heals / potions if they are available, and it would be quite elegant to implement this if special events are added. I know that `FiniteStateMachineEvents.OnBeforeCheckIfNeedToRunState` / `FiniteStateMachineEvents.OnRunState` could be used but I think that native events would be cleaner (it also saves everyone from reinventing the wheel and building boiler plate around the FSM system).
