ExampleRoutine's logic for Flameblast is to use it as a support skill when you get surrounded. In that case, you have a known amount of mobs around you that you know you're going to hit. As long as your charges aren't set too high, it should get off the cast.
What people want instead is to use it as a primary skill, but the same thing that happens with traps would happen with Flameblast; sometimes the logic works perfectly in the current combat scenario, and other times it doesn't do anything. This is due to mobs moving out of the way, or the bot trying to calculate the best place to use the Skill, but ends up missing or not casting because it's either trying to cast too long and gets interrupted (needs variable charge logic) or is otherwise ineffective because the most optimal location to cast Flameblast is anticipating where to cast it based on whatever mobs you're fighting.
If you want to use it defensively as a melee skill, then yes, all you have to do is change the the NumberOfMobsNear logic to something like: Utility.NumberOfMobsNear(LokiPoe.Me, 25) >= 1 and it should cast it in a reliable manner in melee range. That's why that code is there, for users to change.
If you want to use it offensively as a ranged primary skill, then you'd have to code that yourself, which would be better in a custom CR, since the standard casting logic for Flameblast would most likely not work good enough as a primary skill. In essence, ExampleRoutine chooses the simplest, most easy way to use Flameblast, and provides that implementation. For anything better, it's up to the user, as per the
scope of ExampleRoutine.
