Store Page
Invisible, Inc.
All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

Invisible, Inc.

Store Page
Invisible, Inc. >  Workshop > qoala _'s Workshop
Not enough ratings
Vigilance Protocol
Description Discussions0 Comments2 Change Notes
   
Award
Favorite
Favorited
Unfavorite
mod
File Size
Posted
7.654 KB
24 Jan, 2024 @ 4:38pm
1 Change Note ( view )
Required items
This item requires all of the following other items
Created by
qoala _
Offline
See the collection (may be hidden)
430 Unique Visitors
16 Current Subscribers
3 Current Favorites

Subscribe to download
Vigilance Protocol

Description
MEMO TO EMPLOYEES

This is a reminder not to talk to guards while they're on duty. It's a violation of corporate policy. And thanks to a new collaboration between FTM and Plastech, guards will be directed to investigate anyone attempting to distract them from their rounds. Don't be that person.

Feel safe, knowing that you're protected by the finest that technology has to offer!

---

Vigilance Protocol is a new challenge mode that installs a permanent Daemon on the level. Agents that distract a non-alerted guard will have their position relayed to that guard at the start of the next turn.

Includes an optional mode (selectable at campaign start as "POST-MID ALARMS") for use with Programs Extended alarms and the DLC extended campaign. The 1st alarm level from OMNI Foundry onwards with those settings spawns a guard as normal, but now instead of triggering Countermeasures, will install Vigilance 2.0 and change up guard patrols.
2 Comments
< >
qoala _  [author] 26 Jun @ 10:16am 
Programs Extended recently added an option to disable Alarm 1 Countermeasures itself. I'll need to check if I need to change something to be compatible with that.
Wolfram 2 Jun @ 2:35pm 
the "POST-MID ALARMS" option didn't work for me on my recent campaign with Programs Extended's extended alarms. At the OMNI Foundry, on Alarm 1 Countermeasures triggered instead of Vigilance. I have a log file saved if needed. I wonder if PE's recent update caused a conflict in mod loading order where VP's logic for overwriting spawnGuards isn't being run as expected.