Very much the same code wise. Conditions are tied to ini entries, holy's have an "if" statement that fires if the check is True.
In General, Holy is something you wanted checked at all times, regardless of what the macro is doing. Like an instant heal in emergencies. Conditions are only checked when KA is in that cycle of the macro. A holy would see it sooner in theory, as the check is being run more often. If you run holy/downs in
MQ2Melee, they are checked all the time the plugin is on, even if you have no macro running.
- Holyshit are avail in MQ2Melee or MuleAssist.
- Conditions are for KA11 and MuleAssist.
- Downshits are avail in MQ2Melee (ie don't fire this during combat, wait until toon is in "downtime" out of combat then check it.)
MQ2Melee had them first. So a lot of older ini posts would have the KA ini + some code to add to your
MQ2Melee ini for the holy/downs you wanted. You can run both
MQ2Melee and KA, so some people prefer to have a few things on holy still though KA11 is fairly fast at checking stuff. They aren't as required as they used to be, but still a nice option if you need them. Healers and tanks can get some good usages.
eqmule added a holy cycle and ini options to
MuleAssist He suggested limiting it to around 4 holy entries, as this cycle runs often and you don't want to bog down the macro with too many checks.