Some players say the obelisk gets used too early and the team loses the real benefit. Others think taking it down fast is fine if it helps control the fight. What timing actually makes sense here?
When should you pop the obelisk in battle?
Answers
The whole thing is timing, not just speed. If you burn it immediately every wave, you can waste the shield or any other buff window before the enemy actually shows up. That means the team gets a brief advantage when nothing is happening, then loses it right when the fight starts.
A better move is usually to leave it up long enough that the effect lines up with contact. If the obelisk also has attack or tether based effects, that matters even more, because early killing can cut off damage or reduce how many targets get hit. Fast is not always better here.
Reply to this answer
I think the practical answer is to leave it alive until the wave is actually engaged, then finish it when the shield or damage window is about to matter most. If you kill it before the enemies arrive, you are basically spending your advantage on empty air.
That said, there are cases where killing it early is fine if your team needs space, line of sight, or just wants to simplify the map. So it is not always wrong, just often mistimed.
CloudKicker:
That makes sense. I was mostly trying to point out that the buff window is getting wasted before anyone can actually use it.
Reply to this answer
Short version, if the obelisk gives a shield, damage, or some kind of zone effect, you want it active when enemies are already committed. A lot of players treat it like a loot box they need to open right away, but the mechanic is closer to a setup tool.
Also, if the effect only hits tethered or nearby tanks, then early destruction can shrink its usefulness a lot. So the smarter play is usually to let it do its job first, then kill it when the value is spent.
Reply to this answer
I get the frustration, but I would not make this a hard rule. Sometimes leaving it up too long lets the other side use it against you, especially if they can push into the area and turn the timing back around. So the real question is whether your team can hold the space long enough to cash in on the effect.
If the answer is yes, then delaying the kill is smart. If the answer is no, then cutting it down fast may still be the safer call. The mistake is treating every wave the same.
CloudKicker:
Fair point. I was thinking more about the common case where people delete it before the enemy even arrives, but yeah, map control changes the call.
Reply to this answer
A lot of this comes down to coordinating the kill with enemy spawn timing. If your team can stall for a few seconds, you get way more from the obelisk than from just rushing it down. That is especially true when the shield or proc is meant to swing the first contact.
So I would treat it like a trigger, not a target. Hold it until the fight is actually starting, then use it to force the other side into a bad trade. If teammates are burning it too early, they are probably throwing away the strongest part of the mechanic.
Reply to this answer
Add your answer
Answers are reviewed before publication.
StashMode:
Yeah, this is the part people miss. They see a structure and rush it, but the value is in making the enemy fight under the effect, not just deleting it on sight.