-
Posts
211 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by xNullPointer95
-
- 2 comments
-
- #permission
- #manager
- (and 20 more)
-
- 15 comments
-
- 1
-
-
- #skill system
- #level system
- (and 27 more)
-
- 15 comments
-
- 1
-
-
- #skill system
- #level system
- (and 27 more)
-
Howdy 👋, doing custom plugin creations & performance optimizations. Coding experience since 17 years. I started with C# and web development later, but that's also been about 11 years now. (Usually, I worked on desktop applications) Full-time Software Engineer/Developer in the logistics industry (manual and automation logistics software). I've always done Rust plugin development for learning and education purposes. Now since 1 year, I've been actively selling commercially on Codefling. Always trying to play Rust, but always ending up coding plugins or messing around with Rust's limits… 🤣 Portfolio: https://codefling.com/xnullpointer95 Just message me with your request (doesn't matter what it is, as long as it's coding or consultation related). I'll let you know if I can do it, and once we have a full technical specification, I can tell you the price. For faster communication, join our discord. https://discord.gg/rGm7VS5ERc
-
Version 1.0.1
1 download
xFreezeTime xFreezeTime freezes the in-game server time at a configurable hour. It allows admins to enable/disable time freezing, set a custom frozen hour, or instantly lock the current world time using console commands. The plugin automatically applies settings on server startup. Additionally, you can configure events to run at custom intervals, so events like CH47, cargo, or supply drops are not skipped when day/night progression is disabled. You can use any console commands for each configured event trigger. Console Commands xfreezetime - See all available console commands and which permission is required to execute xfreezetime.set <0-24> - Sets the frozen in-game time to a specific hour (e.g. 12, 18.5, 6) xfreezetime.now - Captures the current time and freezes the world at that exact hour xfreezetime.toggle - Toggle the freezing time (Enabled = Freezed Time) xfreezetime.activeevents - List all enabled event triggers + remaining time for next trigger Config { "Enabled": true, "FreezeHour": 12.0, "AnnounceTriggeredEvents": false, "AnnounceMessage": "<color=#e3f542>» Event Triggered:</color> {event}", "LogTriggeredEvents": true, "EventTriggers": [ { "Name": "CargoShip", "Enabled": false, "Command": "cargo.start", "IntervalMinutes": 60.0 }, { "Name": "PatrolHelicopter", "Enabled": false, "Command": "event.run heli", "IntervalMinutes": 100.0 }, { "Name": "CH47", "Enabled": false, "Command": "event.run chinook", "IntervalMinutes": 80.0 }, { "Name": "Airdrop", "Enabled": false, "Command": "supply.call", "IntervalMinutes": 30.0 } ] }$7.90 -
- 15 comments
-
- 1
-
-
- #skill system
- #level system
- (and 27 more)
-
Changed Status from Work in Progress to Fixed Changed Fixed In to 1.1.0
-
Changed Status from Not a Bug to Work in Progress
-
Hi @NukeSter, after analysis i found out that Rust changed scientists model type on oil_rig on previous update, they use Gen2 scientists now, thanks for reporting - I'm already working on a fix.
-
I will check it today night when im at home again.
-
Changed Status from Pending to Not a Bug
-
Lol thanks, thats weird - Alos had vanished active. Thanks for letting me know tho.
-
@NukeSter Will close support request in 24hours if no new feedback arrives.
-
There a spawn group commands. The plugin doesnt prevent them from spawning lol
-
I just tried it in the meantime - It works for me, they dont shoot and dont move.
-
Any feedback?
-
Ok, thank you - Please let me know
-
When you set it to true, did you reload the plugin and wait some time, it takes a short time to get effective.
-
Version 1.0.0
3 downloads
xRespawnProtection gives players a short safe moment right after they got killed. They cannot be damaged by other players for a few seconds (depending on config) after coming back to life. The goal is to prevent instant spawn-kills and make respawning feel fairer. Permission xrespawnprotection.use - Players with this permission get the respawn protection timer. Config { "ProtectionSeconds": 5.0 }$5.00 -
Version 1.0.0
1 download
xWipeRaidProtection Protect your players hard work with this simple and reliable raid protection plugin. This plugin is designed to prevent players from losing everything during wipe periods or unfair raid situations. It helps create a more balanced and enjoyable experience by giving players peace of mind that their bases and items are safer. With easy setup and automatic protection features, server owners dont need to worry about complicated configurations. Once installed, the plugin works quietly in the background to reduce frustration, encourage fair gameplay, and keep your community happy. No datafile - Countdown Time is depending on creation time of new save file (after wipe). Config { "ProtectionHours": 1.0, "AllowLadderPlacement": false, "ProtectionOverMessage": "<color=#55ff88>Global Raid protection is over, happy raiding!</color>", "BlockedDamageMessage": "<color=#ff6b6b>Global Raid protection is active\n</color>» You must wait <color=#ffd166>{0}</color> before damaging bases.", "BlockedLadderMessage": "<color=#ff6b6b>Global Raid protection is active\n</color>» You must wait <color=#ffd166>{0}</color> before placing ladders." }$15.99 -
- 2 comments
-
- #fuel
- #generator
- (and 15 more)
-
Changed Status from Pending to Not a Bug
-
Hello, sure i do thats also the reason why i updated it some days ago. Im pretty sure this comes from another plugin, since i hook into it and cancel the bleeding (doesn't matter from where bleeding was triggered). So if there is any bleeding triggered it will get directly cancelled. Did you consider that the permission name changed to "xnobleeding.use"? If you know why i can help you and check it, otherwise not, since as i mentioned cancel the bleeding (doesnt matter how its triggered).