PLANE FIND AND REPLACE CODE

But if you somehow return a smoldering wreck to your chief that just barely made it back, no repercussions, and you get a sparklingly new plane in no time. Now I'm experiencing with limited respawn-ability: if a player plane is destroyed, its (plane) slot is blocked (no repair) for the remainder of the mission. People like that a lot, as it balances the risk/reward for player CSAR missions towards the end of the mission, when the pilot pool is becoming shallow (it also requires players who can fly choppers well enough to survive a battlefield rescue, so be careful when you add that feature to a mission)

Then I limited the number of player-pilots that can be lost during a mission, with the ability to rescue ejected player pilots via CSAR and refill the pilot pool.

PLANE FIND AND REPLACE CODE

BIG fail, as people don't like waiting around for 30 minutes until they are picked up (and a big personal defeat because that was some of the best code I ever wrote ) They (the player) were blocked from re-slotting until a CSAR (player or AI) rescued them. Some ideas work well, others flopped badly with my players (we are talking small-group, short (2-3 hours) coop missions here, no big servers / campaign)Īt first, I experimented with blocking pilots who were shot down and successfully ejected.

I'm currently experimenting with repercussions for loss of pilots and airframes in multiplayer missions. What I'm trying to understand is what the fun aspect is with this (what makes it fun) and how it could be implemented (how this would feel from a player's perspective). I love to design missions, and aspects like this can help me design more fun missions. This comment intrigues me from a playability standpoint.

The repair could be more fun if it was tied to the damage model

Plane find and replace