So we want to bring Team Fortress to AvP2. It shouldn't be too difficult, all of the weapons we need are already in AvP2, and configuring armor and run speeds and whatnot isn't too hard. What we need, however, is input on how this should go down, and modders to make the more difficult things happen, like possibly adding new weapons and more importantly, new GAME MODES, like Capture the Flag or Assault, things that teams do that aren't Team Deathmatch. However, this is AvP2 Fortress, so everything should have an AvP2 twist to it. Like Preds and Aliens on the teams realistically, but not whorishly. No Predator rocket-launcher guys, for example, but a Predator as the Spy, a class that's supposed to cloak and primarily use a knife anyway. -- SMID

Post news Report content RSS feed The mod gets two new damage types and a TODO list

Team volumes and spy hacking sentries, they both rely on two new damage types. We also define a TODO list.

Posted by on

The test last Saturday confirmed that the team volumes approach will help a lot in enforcing the use of sentries for defending the base only, instead of being used to spawn kill the enemy team. Although not all maps were fitted with this latest object, "Rooftops" was, and the results are encouraging.

The team volume is a damage volume that disables the sentries that are not part of the team that owns that volume. That will make sure there are no sentry spawn kills, which would be more painfull since we introduced the spawn delay.

The same damage types were then added as weapons for the infiltration units (our predator spy) as a special hacking device. This will allow the unit to successfully take down enemy defenses without raising too much attention: the sentries just get deactivated instead of emitting smoke or getting destroyed as they do when they are damaged.

Speaking of the delayed spawning, the test on Saturday showed that work is (still!) needed to polish the feature. An inspection over the code showed that I was using the wrong respawn function. Also, Moose_Head pointed out that with the current system, I am retrieving the flag from killed flag carriers (or from people that switched classes using F1) too late, leading to this kinf of results:


The flag gets spawned in the wrong locations

Discussions over this last test are carried over on our forums.

In regards to the videos that got recorded, one of them shows the blue team sentries after being hacked by Vemarkis:


As for the whole test session:



I know that this video would usually spell the end of the news article. We're making an exception now, and we'll end it with the list of features that need to be implemented (many thanks for the feedback given by our testers, this stuff really helps!):

1) MUST DO. These are bugs that break the gameplay.

  • team volume, to disable enemy sentries in your own base
  • simple triggers, to fix domination points (and flags!) getting stuck.
  • crashes when server changes level. Could be caused by disconnecting players?
  • own flag status
  • trim down the respawn mechanism. We might be able to handle the game without some of the work done for each respawn, thus reducing the respawn lag.


2) SHOULD DO
. These would help adopting the mod, and give it a longer lifetime

  • custom launcher, to allow user content being played with the mod
  • autoupdate utility, usefull to deliver patches
  • hints: when respawning, you get a random message displayed, advertising some of the features available for a given class
  • at least one pickup in each base. With small teams, if no one is a support class, life can be tough.
  • some custom acheivements: people react quite well to rewards. I say we reward: the highest score player (meaning most flag captures), the player with least deaths, the player with most frags. Any other suggstions here?


3) NICE TO HAVE
.

  • repair the mechanics of EVAC, to keep it compatible with standard evac maps. We can always simply ditch the standard EVAC maps and keep the game mode as it is with the Fortress maps
  • ALT-FIRE ammo right when spawning.
  • extra weapons (tranquilizer gun for medic, spy hacking ability against sentries)

The list may suffer changes, according to the feedback given. Having a list however is a good thing on it's own: it helps fighting off feature creep.

Post comment Comments
TheHappyFriar
TheHappyFriar

Really like that you setup the sentries to not spawn kill. How long after a player spawns will they attack?

Reply Good karma Bad karma+1 vote
Herr_Alien Author
Herr_Alien

Because of the team volume surrounding each base, when an enemy turret is dropped in your base, it becomes inactive. It does not attack. Not now, not ever, as long as the turret is labeled from the opposite team.

Now, since turrets can also be picked up, if an enemy engineer drops a turret in your base, it's actually giving you a present: the turret itself.

No man's land is however fair game.

Reply Good karma+1 vote
TheHappyFriar
TheHappyFriar

that's sweeeeet! :D is there some indicator saying when you're dropping a turret in a base so you don't accidentally do it?

Reply Good karma Bad karma+1 vote
Herr_Alien Author
Herr_Alien

Well, no. But, taking a sentry from your base, and then go across the whole map just to place it? I think that should be a clear indicator in itself. I mean it's not like you accidentally dropped in in the enemy base.

You can place however turrets in your own base, and in no man's land. The enemy base is off limits for your team's sentries.

Reply Good karma+1 vote
Post a comment

You are not logged in, your comment will be anonymous unless you join the community. Or sign in with your social account:

Icon
Aliens vs. Predator 2
Creator
Herr_Alien
Contact
Send Message
Homepage
Moddb.com
Release date
Mod watch
Start tracking
News
Browse
News
New
Post news
Share
Related Games
Aliens vs. Predator 2
Aliens vs. Predator 2 First Person Shooter