ZenRaids

Raids:

Set the conditions for raids per biome. By default, no raids are allowed in the Meadows.
Set the number of players that must be online for raids to activate.
Set the key conditions for activating a given raid, both global and per player conditions supported.
Fix Ashlands raids not having per player conditions set in vanilla.
Option to disable per-player "known items" trigger condition for PlayerEvents raid configuration.

Spawn Protection:

Use an interactive light perimeter to prevent monsters from spawning inside your base. However, Keep in mind that the light's protection counts as both spawn prevention and against your raid trigger threshold. Therefore, you have two options:
1. Illuminate your castle to keep the monsters from randomly spawning inside your base.
2. Have a dimly lit castle and reduce the chance of raids but increase the chance of random spawns inside your base.
In Vanilla a workbench can suppress spawns in your base. But what if it was fire instead? Think about that...
Instead, lit fire sources prevent spawns. Keep the torches lit!
Torches are interactive, you can see the radius of their light field perimeter.
ZenSign can help you quickly and easily locate fuel for them.
Fireplace pieces that produce fire keep monsters from spawning, but only if lit. This gives a reason to gamify torch fueling. ZenHoverItem will show you how many game days of fuel is left on a fireplace.

Screenshot Interact

Screenshot Perimeter

Why?

For many lighting torches is a boring chore.

However, putting fuel into fires is boring in vanilla because there is no reward for it other than light. While light is important, it is something you can make due with the bare minimum. Or just sleep through the darkness. Any decent gamer will optimize the resource cost of the torch materials + fuel + cost + and time to fuel vs. doing other more "fun" things. There is no real penalty for a dim castle other than dimness. Resource hoarding takes priority most of the time in a game about survival and resource management.

However, if the penalty for not lighting torches is being interrupted by monsters attacking you while you are trying to walk around your base then you are confronted with a challenge, and now you must decide: Keep the castle dimly lit and save resources but run the risk of monster spawns or spend resources and time to keep the base secure from invaders? Every time you light one, you know you are achieving a positive reward of no monster surprise attacking you. Therefore, making your base more secure. Positive reinforcement makes you consider how to best organize torch layout for quick refueling. Where you stash your fuel matters. (Use ZenSign to easily locate fuel) Plus, then you need to consider what type of torches to place? Iron torches last way longer than wooden torches and only burn resin, but they cost iron. Coal braziers use bronze and can last a long time and uses easy to get coal. But they create smoke and don't work in the rain. Bonfires work in the rain and light up a huge area, but they cost a Surtling Core and burn wood quickly, Etc... How much fuel do you have? What type of fuel do you have? How large is the area you are trying to protect? etc. Different torches have different light radius and therefore protection radius. You don't end up with tons of resin doing nothing. Wood can light a fire but it burns fast!

Coal light sources suddenly have value due to their increased efficiency of wood usage. 1 wood = 1 coal. However, 1 coal can burn for 10 game days! 1 wood can only burn for 2.5 days. However, coal takes longer to make than wood, more steps involved. But it's available everywhere. Resin is not.

In the new scenario coal has a value other than smelting ore. It also acts as a fuel sink to protect your base against monsters. This improves the game's resource economy balance. More gamification and more things to consider in a resource management game.

Consider the table below. Light range, capacity, game days of protection, and fuel availability all matter. Additionally, depending on how and where you design your base, rain and smoke may be considerations. (NOTE: You can use ZenHoverItem to see the fuel days remaining on a fire source when you hover over it)

Fire Sources

Fire Source	Fuel	Range	Capacity	Days	Rain	Smoke	Warm
Campfire	Wood	10	10	25	Yes	Yes	Yes
Iron FirePit	Wood	10	10	25	No	Yes	Yes
Bonfire	Wood	20	10	25	No	Yes	Yes
Hearth	Wood	13	20	50	Yes	Yes	Yes
Brazier	Coal	15	5	50	Yes	Yes	Yes
Blue Brazier	Eye	15	5	50	Yes	Yes	Yes
Hanging Brazier	Coal	15	5	50	Yes	Yes	Yes
Wood Torch	Resin	10	4	20	No	No	No
Sconce	Resin	12	4	40	No	No	No
Iron Torch	Resin	15	6	60	No	No	No
Green Torch	Guck	15	6	60	No	No	No
Blue Torch	Eye	15	6	60	No	No	No
Candle	Resin	0	1	7	Yes	No	No

The Sconce max fuel is reduced from vanilla (6). It burns fuel at half the rate of a wood torch, it provides more protection area than a wood torch, it costs less bronze than a Brazier, it produces no smoke, and it's immune to rain.

Fuel Types:

Wood

Burns quickly (2.5 days for 1)
Easy to get
Need to refuel often
Makes smoke
Vulnerable to rain (Except Bonfire and Iron Fire Pit)
Fire sources only require basic mats to build.

Coal (Colored: Eyes & Guck)

Burns for a long time. (10 days for 1)
Need to process wood to get coal (time cost)
Do not need to refuel as often as wood.
Makes smoke.
Vulnerable to rain
Fire sources require bronze to build

Resin (Colored: Eyes & Guck)

Burns for a long time (10 days for 1) (wooden torch 5:1)
Need to collect it
Do not need to refuel often
Does not make smoke
Immune to rain
Fire sources require metal (except wooden torch)
Most efficient fire sources; do not need to refuel often.

Improve Your Experience

CORE MODS

The full collection of all Zen MODS:

Radically improved QoL
Incredible performance
Pre-configured
100% Gamepad support
Spectacularly immersive

Enjoy!

Sample Config File

## Settings file was created by plugin ZenRaids v0.7.2
## Plugin GUID: ZenDragon.ZenRaids

[Raid Keys]

## [Admin] Append any global keys to the player keys list for triggering a raid.
## This can be useful when using modded content that did not consider raid to be per player progression.
## [restart required for changes to take effect]
# Setting type: Boolean
# Default value: true
Append Global Keys To Player Keys = true

## [Admin] Comma separated list of raidname and biomes it is allowed to spawn in.
## Syntax: raidname:biome1|biome2|biome3, raidname:NONE, raidname:ALL, etc...
## Specify NONE to disable all biomes for a given raid.
## Specifiy ALL to allow all biomes for a given raid.
## Possible biomes: None, Meadows, Swamp, Mountain, BlackForest, Plains, AshLands, DeepNorth, Ocean, Mistlands, All
## If raid name is not defined then vanilla values are used for that raid instead.
## Console command: Zen_RaidRules to view current raid conditions.
## [restart required for changes to take effect]
# Setting type: StringList
# Default value: 
Allowed Biomes = 

## [Admin] Set global keys to activate raids.
## Comma separated list of raid name and keys separated by vertical bar.
## Syntax: raidname:key1|key2|key3, raidname:key1|key2, raidname:NONE, etc...
## Specify NONE to clear all global keys for a given raid.
## If raid name is not defined then vanilla values are used for that raid instead.
## Console command: Zen_RaidRules to view current raid conditions.
## [restart required for changes to take effect]
# Setting type: StringList
# Default value: 
Global Keys - Activate = 

## [Admin] Set global keys to deactivate raids.
## Comma separated list of raid name and keys separated by vertical bar.
## Syntax: raidname:key1|key2|key3, raidname:key1|key2, raidname:NONE, etc...
## Specify NONE to clear all global keys for a given raid.
## If raid name is not defined then vanilla values are used for that raid instead.
## Console command: Zen_RaidRules to view current raid conditions.
## [restart required for changes to take effect]
# Setting type: StringList
# Default value: 
Global Keys - Deactivate = 

## [Admin] PlayerEvents: player key to enable a raid, ALL keys must be set.
## Comma separated list of raid name and keys separated by vertical bar.
## Syntax: raidname:key1|key2|key3, raidname:key1|key2, raidname:NONE, etc...
## Specify NONE to clear the player keys for a given raid.
## If raid name is not defined then vanilla values are used for that raid instead.
## Console command: Zen_RaidRules to view current raid conditions.
## [restart required for changes to take effect]
# Setting type: StringList
# Default value: 
Player Keys All - Activate = 

## [Admin] PlayerEvents: player key to activate a raid, ANY key must be set.
## Comma separated list of raid name and keys separated by vertical bar.
## Syntax: raidname:key1|key2|key3, raidname:key1|key2, raidname:NONE, etc...
## Specify NONE to clear the player keys for a given raid.
## If raid name is not defined then vanilla values are used for that raid instead.
## Console command: Zen_RaidRules to view current raid conditions.
## [restart required for changes to take effect]
# Setting type: StringList
# Default value: army_charred:GP_Queen, army_charredspawners:GP_Queen, army_goblin:GP_Moder, army_moder:GP_Bonemass, army_gjall:GP_Yagluth
Player Keys Any - Activate = army_charred:GP_Queen, army_charredspawners:GP_Queen, army_goblin:GP_Moder, army_moder:GP_Bonemass, army_gjall:GP_Yagluth

## [Admin] PlayerEvents: player key to disable a raid, ALL conditions must be true.
## Comma separated list of raid name and keys separated by vertical bar.
## Syntax: raidname:key1|key2|key3, raidname:key1|key2, raidname:NONE, etc...
## Specify NONE to clear all player keys for a given raid.
## If raid name is not defined then vanilla values are used for that raid instead.
## Console command: Zen_RaidRules to view current raid conditions.
## [restart required for changes to take effect]
# Setting type: StringList
# Default value: army_charred:GP_Fader, army_charredspawners:GP_Fader
Player Keys - Deactivate = army_charred:GP_Fader, army_charredspawners:GP_Fader

## [Admin] PlayerEvents: known items that will trigger the raid.
## Comma separated list of raid name and item prefab names separated by vertical bar.
## Syntax: raidname:prefab1|prefab2|prefab3, raidname:prefab1|prefab2, raidname:NONE, etc...
## Specify NONE to clear all required known items for a given raid.
## If raid name is not defined then vanilla values are used for that raid instead.
## Console command: Zen_RaidRules to view current raid conditions.
## [restart required for changes to take effect]
# Setting type: StringList
# Default value: 
Player Known Items - Activate = 

## [Admin] PlayerEvents: known items that will disable the raid.
## Comma separated list of raid name and item prefab names separated by vertical bar.
## Syntax: raidname:prefab1|prefab2|prefab3, raidname:prefab1|prefab2, raidname:NONE, etc...
## Specify NONE to clear all required not-known items for a given raid.
## If raid name is not defined then vanilla values are used for that raid instead.
## Console command: Zen_RaidRules to view current raid conditions.
## [restart required for changes to take effect]
# Setting type: StringList
# Default value: 
Player Known Items - Deactivate = 

[Raids General]

## [Admin] Minimum number of players required to be online to trigger a raid.
# Setting type: Int32
# Default value: 1
# Acceptable value range: From 1 to 10
Min Player Count = 1

## [Admin] No Raids allowed in these biomes
# Setting type: Biome
# Default value: Meadows
# Acceptable values: None, Meadows, Swamp, Mountain, BlackForest, Plains, AshLands, DeepNorth, Ocean, Mistlands, All
# Multiple values can be set at the same time by separating them with , (e.g. Debug, Warning)
No Raid Biomes = Meadows

## [Admin] These raids are allowed even in NoRaidBiomes. Comma separated list of raid names.
# Setting type: StringList
# Default value: army_eikthyr
No Raid Biomes Exeption Raids = army_eikthyr

## [Admin] For per player events: Ignore item knowledge as a raid condition. (Vanilla: false)
## In vanilla, knowledge of specific items flags you for raids based on that knowledge. 
## If this option is true then it doesn't matter what items you know, per player raids will only be based on player keys.
## This prevents accidentally getting flagged by just picking up the wrong item.
## [restart required for changes to take effect]
# Setting type: Boolean
# Default value: true
Ignore Condition - Known Items = true

## [Admin] Comma separated list of raid names.
## These raids have their activate condition removed so they are never in rotation to be triggered.
## [restart required for changes to take effect]
# Setting type: StringList
# Default value: 
Never Activated Raids = 

## [Admin] Comma separated list of raid names.
## Once activated, these raids have their disable condition removed so they are always in rotation to be triggered.
## [restart required for changes to take effect]
# Setting type: StringList
# Default value: 
Never Deactivated Raids = 

[Spawn Protection]

## [Admin] Workbenches and other objects will no longer protect against monster spawns. (Vanilla: false)
## Instead sources of fire (Fireplaces/Torches) must be lit for spawn protection. 
## If this is off then vanilla behavior applies.
## NOTE: See the detailed explanation in the readme or on thunderstore.
## [logout required for changes to take effect]
# Setting type: Boolean
# Default value: true
Fire Must Be Lit = true

## [Admin] Players can interact with fire sources to see the perimeter of the light's protection.
## [logout required for changes to take effect]
# Setting type: Boolean
# Default value: true
Interact Show Perimeter = true

## [Admin] When "Fire Must Be Lit" is enabled this adjusts the light radius size to use for spawn protection.
## Note: Setting this to 0 will disable all spawn protection.
## [logout requried for changes to take effect]
# Setting type: Single
# Default value: 1
# Acceptable value range: From 0 to 3
Light Range Percent = 1

## [Admin] Number of base pieces the player needs to be near to trigger raids. (Vanilla = 3)
## When Fire Must Be Lit is enabled it removes spawn protection from vanilla pieces.
## Therefor it reduces the number of pieces in proximity to the player that can trigger raids. 
## Higher numbers would reduce the odds of triggering a raid because you are less likely to be near so many.
## However, Keep in mind that a lit light source counts as both spawn protection and towards your raid threshold.
## Therefor you have two options.
## 1. Put lights everywhere to keep the monsters from spawning in your base.
## 2. Have a dimly lit castle and reduce the chance of raids but increase the chance of random spawns inside your base.
## Candles are a good example of a dimly lit castle.
# Setting type: Int32
# Default value: 3
# Acceptable value range: From 1 to 100
Raid Threshold = 3

## [Admin] When "Fire Must Be Lit" is enabled overrides the prefab max fuel for the specified light sources.
## Comma separated list of prefab names and max fuel values.
## NOTE: The Sconce is reduced from vanilla (6) because: 
## it burns at half the rate of a wood torch, it protects more area than a wood torch, 
## it costs less bronze than a brazier, it produces no smoke, and it's immune to rain.
## [logout requried for changes to take effect]
# Setting type: StringList
# Default value: piece_walltorch:4
Fuel Override = piece_walltorch:4

Like My Mods? Donations Welcome

Bitcoin