Server configuration¶
RaG Thunderstruck generates Thunderstruck.json in the server profile directory when the file is missing.
Stop the server before editing the file. Start the mod once after every update and compare the newly generated schema with your existing file before restoring custom values. The public Workshop description predates several later settings, so blindly copying its old example can drop supported options.
Published baseline¶
This is the valid-JSON form of the baseline published on the Workshop page. It is a field reference, not a replacement for the file generated by the installed build.
{
"ThunderstruckItems": [
"rag_shitground",
"Apple"
],
"AllowDamagePlayerAttachments": 1,
"AttachmentsDamageLevel": 3,
"HitChanceRange": 100,
"HitChance": 99,
"ShowWeatherIcon": 1,
"ReducedPlayerHealth": 0.25,
"MinRainIntensity": 0.6,
"MinOvercastIntensity": 0.7
}
Later releases added CanGetHitAgain, AnnouncePlayerHit, and EnableDebugLogging. Preserve the values generated by the current mod unless you deliberately change them.
Settings¶
| Setting | Published value | Effect |
|---|---|---|
ThunderstruckItems |
rag_shitground, Apple |
Class names created at the struck player's position. Invalid or unavailable classes cannot be spawned. |
AllowDamagePlayerAttachments |
1 |
When enabled, a strike also affects worn equipment and the item in the player's hands. Use 0 or 1. |
AttachmentsDamageLevel |
3 |
Target condition for affected equipment: 0 pristine, 1 worn, 2 damaged, 3 badly damaged, or 4 ruined. Requires attachment damage to be enabled. |
HitChanceRange |
100 |
Upper range used by the strike randomizer. This is not itself a percentage. |
HitChance |
99 |
Threshold at or above which the roll becomes a hit. With the published range, 99 and 100 qualify. |
ShowWeatherIcon |
1 |
Shows the thunder icon when both weather minimums are met and the player is not protected. Use 0 or 1. |
ReducedPlayerHealth |
0.25 |
Health fraction used by strike damage. The published value is described as a 75% reduction. Valid range: 0.0 to 1.0. |
MinRainIntensity |
0.6 |
Minimum rain intensity. Winter snowfall compatibility uses this value. Valid range: 0.0 to 1.0. |
MinOvercastIntensity |
0.7 |
Minimum overcast intensity. Valid range: 0.0 to 1.0. |
CanGetHitAgain |
Generated value | 1 allows repeat hits. 0 limits a player to one hit until respawn or server restart. |
AnnouncePlayerHit |
Generated value | 1 sends a server-wide notification naming the struck player. Compatible notification mods and DayZ Expansion can display it. |
EnableDebugLogging |
0 |
Enables diagnostic logging. Leave disabled unless investigating a problem or collecting logs for support. |
Boolean settings should be 0 or 1.
Chance tuning¶
The mod's published explanation treats the random range as inclusive. That makes the approximate qualifying fraction:
This only makes sense when HitChance is between 0 and HitChanceRange. Examples:
| Range | Threshold | Qualifying values | Approximate chance per roll |
|---|---|---|---|
100 |
100 |
1 | 0.99% |
100 |
99 |
2 | 1.98% |
100 |
95 |
6 | 5.94% |
999 |
990 |
10 | 1.00% |
These are per-roll probabilities, not the percentage of players struck during an entire storm. Longer storms create more opportunities.
Item-spawn list¶
Every entry in ThunderstruckItems must be a valid class available on both the server and clients. If a listed class belongs to another mod, that mod becomes an operational dependency for the configured server.
After changing the list:
- validate the JSON syntax;
- restart the server;
- trigger a controlled test strike;
- check the script and debug logs for failed object creation.
Debug logging¶
Keep EnableDebugLogging at 0 during normal operation. Enable it only long enough to reproduce a problem, then disable it again. Debug output from a weather loop can become noisy and is intended for troubleshooting.