Automappers Should Auto-Return

[efgi]

I would suggest that auto-mappers without go-to commands should seek out their host WX, then stop at the edge of their reception range. I feel this addresses frustration of them being stuck out of range while addressing requests they should wander (they would traverse unknown territory in seeking WX reception). This would keep them regularly in range while creating a dynamic mechanic where they can be sent to a point then dragged to explore their WX-seeking route. This is similar to other mechanics (e.g. gardening) where attention and time investment creates a greater reward than set-and-forget creates leseer reward. The current implementation instead leads to stalling, where setting and forgetting halts reward entirely.

Edited March 26 by efgi
parenthetical addition

[efgi]

Coming back this after further rumination, additional behavior states for the first vs second skill point could create additional skill-point value. Skill point investment could change idle  behavior as well as range. Return mode is started after a period of idleness rather than immediatley without command.

 

1st skill: can craft roto-mappers, limited command range, stall-then-return.

2nd skill: expanded command range, wander during idle time, then engage return mode. Devs to balance return-range vs command-range.

Edited March 26 by efgi
Typo

[efgi]

The ability to command out-of-range roto-mappers into range is the perfect balance I hadn't foreseen. Great job Klei!

Edited March 28 by efgi