NerdyVampire Posted March 11 Share Posted March 11 (edited) I suggest whenever the hivebot beacon fires during a 25+ pop round, it creates a beacon in two distinct locations, due to the following reasons. We are dealing with a hivebot event-chain, so seeing more beacons spawn to cement the increased activity, would add some extra spice. On high pop security often have enough manpower to deal with it without even involving other departments (medical and engineering), which is a shame. It is possible to respond very promptly when the officers are already armed, as the event gives a specific location. One of the most exciting events can be put down in less than 3 minutes, which makes it feel less special than it ought to. Two beacons forces a prioritized response, which involves a bit more decision making, and whichever is not prioritized would add a little extra difficulty. It would also allow engineering and security to "split" the responsibility in certain situations. I would consider 25+ players a nice split. That usually translates to a pretty full security and moderately full engineering department. Edited March 11 by NerdyVampire 6 Link to comment
Fyni Posted March 11 Share Posted March 11 Hivebots are one of the best random events in my opnion because they involve Security, Engineering and often Medical. Given the current arc, I think this is a great idea. 2 Link to comment
OolongCow Posted March 12 Share Posted March 12 As long as it checks for on-ship, active crew, I'm fine with this suggestion. Just checking for 25 players on the server regardless of status is definitely a bad idea, though. Link to comment
NerdyVampire Posted March 20 Author Share Posted March 20 On 12/03/2024 at 01:21, OolongCow said: As long as it checks for on-ship, active crew, I'm fine with this suggestion. Just checking for 25 players on the server regardless of status is definitely a bad idea, though. That's a good point. We need a minimum amount of active on-board crew for this to make sense. Link to comment
Fluffy Posted April 18 Share Posted April 18 https://github.com/Aurorastation/Aurora.3/pull/18984 Link to comment
Fluffy Posted May 3 Share Posted May 3 The PR was merged, therefore this suggestion is considered implemented Locking and archiving Link to comment
Recommended Posts