Hostile reinforcements
The hostile director adds extra Tensura encounters while you explore the Overworld, Nether and Tensura Hell. It is enabled by default. It does not run in the End, boss arenas, labyrinths or this addon's pocket dimensions.
Written by claude Last edited 5 Oct 2026
Usage
The hostile director adds extra Tensura encounters while you explore the Overworld, Nether and Tensura Hell. It is enabled by default. It does not run in the End, boss arenas, labyrinths or this addon's pocket dimensions.
Progression and pressure
Every 10 seconds, an eligible survival/adventure player gets up to 48 placement attempts. Each proposed encounter uses the strongest living, non-spectator player's EP within 128 blocks of that position, in the same dimension. Creative players do not start encounters, but their EP counts if they are nearby. A powerful player elsewhere on the server has no effect.
The target number of additions is 2 + 4 × min(nearby EP / 5,000,000, 1). Fractions are rounded randomly once per check:
| Nearby EP | Target additions per check | Local threat budget |
|---|---|---|
| 0 | 2 | 8 |
| 1,000,000 | 2.8 average | 11 |
| 2,500,000 | 4 | 16 |
| 5,000,000 or higher | 6 | 24 |
All progression stops at exactly 5M EP. A 15M player gets the same pressure and pool as a 5M player. Raising the config ceiling above 5M is disallowed; lowering it makes the same progression finish sooner. There are no extra ultimate-tier farming targets, and the director adds no health, damage, energy or loot bonuses to individual mobs.
These are target limits, not guaranteed spawns. Tensura's natural day/night probability rolls, biome restrictions, placement rules, lighting requirements and collision checks still apply. Blocked attempts are used up. There are no banked reinforcements or catch-up bursts.
Mob pool
Only these seven ordinary tensura entity IDs are allowed. Each needs both its current species biome tag (tensura:<id>_spawn) and an entry in the live monster spawn table. Datapack removals are respected.
| Minimum nearby EP | Mobs | Threat cost each | Natural habitat |
|---|---|---|---|
| 0 | barghest | 1 | Plains village biomes, forests, taigas, Nether and miasmic plains |
| 0 | army_wasp | 1 | Flower forests and cherry groves |
| 0 | one_eyed_owl | 1 | Forests and woodland mansion biomes |
| 1M | knight_spider | 2 | Deserts, badlands and desert of death |
| 1M | basilisk | 2 | Savannas, mountains and desert of death |
| 1M | lesser_daemon | 3 | Tensura Hell biomes |
| 3M | greater_daemon | 6 | Tensura Hell biomes |
Higher thresholds are 20% and 60% of the configured ceiling. Greater daemons are eligible in only 5% of checks, still have to pass their natural spawn roll, and are limited to one per encounter, one nearby at a time and a 60-second local cooldown.
Hinata, other NPCs, named bosses and structure bosses are excluded. Orcs and hell caterpillar/moth families are omitted because their spawn variants can be more valuable; wolves are omitted because of evolved packs. Black spiders are omitted because they can create additional spiders, including on death, outside the director's cap. Multipart centipedes and serpents are also outside this initial pool. Reinforcements start hostile to the player whose exploration triggered the check; normal species combat abilities remain.
Space, caps and claims
- Spawns start 32–80 blocks horizontally from the checked player and at least 32 blocks from every living non-spectator player. Surface and nearby cave floors are tried; flying mobs also start above valid ground.
- The Overworld's shared world spawn has a 96-block horizontal exclusion.
- A local area can hold at most 12 living reinforcements, subject to the threat budget above. Both the candidate and player surroundings are counted. Tamed reinforcements still count.
- Each dimension can hold at most 64 loaded reinforcements. Ordinary spawns retain their own caps. No chunks are force-loaded.
- Nearby players share spatial cooldowns; forming a crowd does not give each player a separate full encounter. Successful encounters and failed checks save their cooldowns across restarts. The mobs' marks survive saves and chunk unloads.
- Peaceful difficulty and
doMobSpawning=falsedisable additions. - With FTB Chunks, additions are blocked in claimed chunks and in the surrounding one-chunk buffer. A player inside that protected area does not trigger encounters. This affects only director additions; normal Minecraft/Tensura spawning is unchanged. Mobs can still walk into claims from outside, so claims are not an impenetrable mob barrier.
The optional bridge uses FTB Chunks' public claims API through isolated reflection. If FTB Chunks is absent, exploration works normally. If it is installed but its manager is unavailable, additions wait. If API lookup fails, additions stop and one error is logged; natural spawning continues. After repairing an incompatible integration, restart the server.
Rewards
Every added mob receives a persistent reinforcement mark, threat cost, reward multiplier and initial reward ceiling. By default its shared Tensura EP payout is 30%, before Tensura's usual attacker-progression reduction. The original summoned/spawner exclusions still take precedence. A later increase in the mob's EP cannot raise its reward above the saved ceiling.
The multiplier is saved when the mob is created. Changing the config affects newly created reinforcements; existing ones retain their saved value even when the director is disabled. Ordinary mobs are untouched. Combat EP is unchanged. Kill EP, gear EP and abilities that use Tensura's shared EnergyHelper.getEPGain(Mob, double) calculation receive the reduction; Tensura's EP-derived experience calculation also uses it. Item drops remain normal. Other addons that directly read combat EP or grant their own rewards can bypass this shared calculation, so this is not a guarantee against every modpack farming interaction.
Server configuration
File: <world>/serverconfig/tr_raccoon-hostile-director-server.toml. This new config receives the defaults below in existing worlds without migrating or resetting any other config. As with other server configs, an administrator-supplied defaultconfigs template can override fresh-file defaults.
| Key | Default | Meaning |
|---|---|---|
enabled | true | Enable extra encounters |
suppressClaimedChunks | true | Apply FTB claims and one-chunk buffer |
nearbyPlayerRadius | 128 | EP scan, local count and cooldown radius; 96–256 blocks |
minimumSpawnDistance | 32 | Player exclusion; 24–64 blocks |
attemptIntervalTicks | 200 | Check interval and local cooldown; 100–12,000 ticks |
attemptsPerCheck | 48 | Placement attempts; 1–96 |
localMobCap | 12 | Living reinforcements per local area; 1–32 |
dimensionMobCap | 64 | Loaded reinforcements per dimension; 1–256 |
localThreatBudget | 24 | Maximum threat; 6–96, scaling from one third to full |
lowEpPressure | 2.0 | Low-EP target additions; 1–8 |
maximumPressure | 6.0 | Ceiling target additions; 1–12, treated as at least low pressure |
epScalingCap | 5,000,000 | Progression ceiling; 1–5,000,000 |
reinforcementEpRewardMultiplier | 0.30 | New reinforcements' reward fraction; 0–1 |
higherTiers | true | Allow knight spiders, basilisks and lesser daemons, plus the greater-daemon tier |
greaterDaemons | true | Allow the rare greater-daemon tier when higher tiers are enabled |
Admins cannot add arbitrary boss IDs through this config. The audited pool is deliberately closed.
Tensura Modpack Wiki