Variation - Choice between multiple dropship consoles.

[TheMaskedMan2]

Summary (a quick, 2-3 sentence summary): Place a "broken" or "un-synced" dropship console to both LZ's. Allowing marines to repair one, essentially allowing them to choose a different LZ for the FoB if they want.

Benefits (How this will benefit the server and game as a whole): Variation, and different strategies and plans will be viable. Now marines can use LZ2 FoB's for fun and defense. Variaaatiooon! Different strategies.

Details (Description of how you think this would work, the benefits, etc): Basically, let's use Big Red as an example, it originally had two consoles, but the one at LZ2 was removed as marines can't possibly defend two LZ's. Well i'm proposing add that back. As well as ones for Ice and LV respectively. Though this time they will all start "Broken". Essentially being a useless ornament until repaired.

I propose that the dropships be unable to return to the Almayer until one is repaired. To prevent marines from deciding to not activate any to not allow Xenos to attack the ship. Use some fluff speak like "Dropship unable to calculate trajectories without groundside flight stats" or something.

The method of repairing these would essentially require some tools of an engineer, or should that be requiring too much of marines, which lets admit, sometimes it is. A round start squad may not have an engineer, we can just have it take 30 seconds of a marine. "Syncing computers" by clicking it. Furthermore allow only one to be prepared, so it's a simple choice of LZ1 or LZ2. Or both if they really want but in that case I worry some dumb marine will always do that and mess up the defense. Just some thoughts.

Implementation (Optional, if you have an idea how to implement it): Some coding magic, a bit of mapping, with a dash of fluff.

[Sleepy Retard]

+1 adds variation and replayability. Seems good to me.

[Sarah_U.]

I was at first thinking this was the multiple LZ suggestion, but now that I read it, I love it.

+1

This'll grant a ton of dynamic to gameplay and possibly become a great tool into making the repetitive LZ1 last stand into an alternate LZ2 last stand.

[Kwin_Original]

+1 this sounds really nice and more variation is always a better thing

[Nick123q23]

There's a suggestion that is pretty much just this but without the choice. Now that I've read this one, I'd prefer the console being able to be repaired instead. +1

[TheMaskedMan2]

Was thinking more about this and came up with some flavor text devs could use if they decide to implement this.

Examine console: "That's an [LZ1/LZ2] dropship console. Interacting with this for 30 seconds should connect it to the Almayer."

Dropship tries to take off without a console sync'd: "Takeoff trajectories not found. Please get clearance from local flight coordinator terminal"

Fixing console: Logging in... USCM credentials found... overriding... syncing with USS-ALMAYER

Console completion: (This will display an A.I. announcement so it is obvious to everyone what spot was picked) A.R.E.S. : "Flight sync completed with [Colony Name]. Vital ALMAYER information stored on [LZ1/LZ2]. Recommendation: Ensure Protection until Operation completion.

Basically some flavor text for immurshions and lots of context clues to help people understand what the hell is going on without reading wiki guides and stuff.

[Kwin_Original]

+1 for the suggested texts, they sound good

[NoahKirchner]

https://gyazo.com/482ce5c2f3b89e7e459adcc23f8609b6

+1

[TheMaskedMan2]

https://gyazo.com/482ce5c2f3b89e7e459adcc23f8609b6

+1

Shit he has realized my dirty secrets and revealed them to the masses. I gotta make ends meet is all.

[Sneakyr]

Yes please. I want more LZ2 FOBs.

[Nick123q23]

Maskedman's flavor text would be nice, too.

[Swagile]

+ 11111

Some maps, the LZ-2 area is a perfect FOB location, but no one puts anything there because they all know xenos will just rush LZ-1.

[TheDonkified]

+1. Anything that doesn't force LZ1 FOB unless you want to risk xenos just beelining straight to an undefended dropship console.

[Antopathos]

I didn't want to make a new thread, and this is close enough.

I suggest that every map should have more LZs (unpaved ones) than just two, but only one dropship console for the aliens to use. This would:
1) Give the marines more chances to flank the aliens and destroy their hive - LZ2 hardly ever is an option after it is lost.
2) Force the Xenos to play defensively more and increase the importance of runners.
3) Make FOB defense easier when the Xenos aren't dedicated to destroying it.
4) Prevent metarushes

In my opinion, this would make sense, because
1) I can't see such small colonies having a use for two dedicated LZs
2) Those dropships could park pretty much anywhere, even shoot an impromptu LZ through the jungle if they wanted to
3) Metarushing the Almayer from LZ2 leaves the hive and eggs undefended, which the aliens would never do IMO.

Problems with the suggestion:
1) Maps would need to be reworked
2) I don't know if it's possible code-wise to pick your LZ

[Kwin_Original]

+1 to this, sounds very interesting if it could be done

[Jory13]

Bump.

[TehSpoderman]

please god let us do this +11111111111111111111111111

[Renomaki]

Having the ability to SELECT a main landing zone is a nice idea, although I'd want this to be HEAVILY tested if it is considered.

For instance, what if some asshole, without telling anyone, repairs the other LZ's computer? If one computer gets activated, the other should be unable to be activated at all, meaning that once you select a main LZ, that IS your main LZ, and the other will be a secondary LZ as per the norm.

Keep it idiot proof and we'll be golden.