[1.1.2587] Hard to tell why a mech cluster woke up

[East]

TITLE EDITED BY TYNAN

https://clips.twitch.tv/ElegantCarefulFriesAMPEnergy

The mech cluster wakes up for no reasons.
There was nobody there.
I was broadcasting and I was able to record.

This was just after falling, and the countdown remained around 0.7.

[NeverPire]

Unfortunately in your clip we can't see the timer decount, only the proximity detector.

It is something else, but I would like to propose to add in the desctiption of these timers that it triggers the cluster if attacked.

[East]

counter


full video

There is no reason for them to wake up.

https://www.twitch.tv/videos/578763834?t=1h19m37s

[logikzer0]

The countdown activator on that cluster was set for 0.7 hours, which is why it woke up so quickly.  When you un-paused you had it on 3x speed and you can clearly watch as it ticks down on the message on the far right.  0.7 hours is no time at all on 3x speed.

[East]

You're right. I was mistaken. I thought the unit of time was day. And this idea was strengthened because it was a mech cluster that had just fallen. I didn't think it was 0.7 hours instead of 0.7 days.

[Tynan]

We could make this easier to understand.

I think the 'mech cluster has woken up' message should give a reason. Like "Mech cluster has woken up: Countdown activator".