RTimer
-
Posts
48 -
Joined
-
Last visited
-
Days Won
2
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by RTimer
-
Changed Status from Not a Bug to Closed Changed Fixed In from 1.0.7 to 1.0.8
-
.thumb.png.1ffd081b2085ecf64bc586d6bc9b64b3.png)
It means: “Whether to take the player’s armor (equipment) into account when calculating the damage dealt by the Bomber’s explosion.” In other words, whether the damage should be reduced based on the player’s armor percentage, just like armor reduces bullet damage, etc. -
Changed Status from Pending to Not a Bug Changed Fixed In to Next Version
-
Yes, of course. I will add this feature in the next update.
-
I understand the issue. I’ll think about the best way to handle this and try to address it in one of the upcoming updates.
- 1 reply
-
- 1
-
-
Changed Status from Pending to Not a Bug Changed Fixed In to Next Version
-
Okay, I’ll add this to the config in the next update.
-
Changed Status from Pending to Not a Bug Changed Fixed In to 1.0.7
-
Regarding the map marker, the radius is already customizable in the config under “Map Marker Radius”. You can change the marker radius there, so there shouldn’t be any need to modify the hardcoded value in the code.
-
The smoke, remaining crates, and other event elements no longer disappear instantly right after winning. Instead, I added a short delay before cleanup so players have plenty of time to loot everything safely, especially now that events can spawn multiple crates. This cleanup delay is completely customizable via the Despawn Delay option in your config, which is set to 2 minutes (120 seconds) by default. Hope this helps clarify things!
-
Changed Status from Pending to Closed Changed Fixed In to 1.0.7
-
I'm not sure why that happened, as I couldn't reproduce this bug on my end. If this problem pops up again, definitely let me know (if you have any console errors, please send them over too—they help resolve issues much faster). It might have just been a minor, isolated conflict on the server. Thanks for your time!
-
Did this start happening after updating to version 1.0.7, or has it always been like this? Is this the first time you've encountered it? Also, have you tried restarting the event to see if the map marker appears?
-
Hello! This behavior was intentionally designed as part of the event's mechanics. Players are not supposed to leave the event area while the hacking process is in progress. If they do, the hacking progress is reset and the event starts over. However, you can easily adjust this to better fit your server. In the config file, there are two settings that control this behavior. By default, they are set to fairly strict (low) values: - Maximum Distance (trigger zone) — increase this value to expand the event area. - Return Time — increase the number of seconds a player has to return to the event area before the hacking progress is reset.
-
Fixed in version 1.0.7
-
updated in version 1.0.7
-
Thank you for the detailed explanation, I completely understand the issue now. You are right, that is definitely a bug. I will fix it in the nearest update!
-
Just to clarify how the plugin currently works: new bombers stop spawning as soon as the crate hack timer finishes, so everything is functioning correctly on that front. However, any bots that were already spawned will remain alive in the area until a player comes down, kills them, takes all the loot, and completes the event. If a player dies, those remaining bots will simply stay there until someone else arrives. Would you like us to add a reset feature for this—for example, if a player dies or leaves and no one interacts with or loots the crate within 2–3 minutes, the event automatically resets? Or how exactly would you prefer it to work? Alternatively, if I misunderstood your message and you encountered an actual bug (such as bombers continuing to spawn endlessly even after the hack timer ended), please describe the exact scenario in more detail so I can look into it!
-
Hi, please give me some time; I will definitely resolve your issue soon.
-
I'm already working on it and plan to include it in the next update. Thanks for your patience!
-
Support for Notify has been added in version 1.0.6.
-
Updated in Version 1.0.6
-
I'll be releasing an update soon to add this damage to the config before the big difficulty update. Since it's so important to you guys, I want to make sure you're as comfortable as possible.
-
I'll be releasing an update soon to add this damage to the config before the big difficulty update. Since it's so important to you guys, I want to make sure you're as comfortable as possible.
-
Damage adjustment is definitely coming in future updates, 100%.
