.png.a9f77afb0653176492a7ec78168c7ae0.png)
-
Posts
633 -
Joined
-
Days Won
3
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by fullwiped
-
Hello, sorry for the delay. We will publish the update today when we are available.
-
Yes, I think I accidentally deleted the required plugin, that was my mistake. The issue has been resolved. Thank you for your support.
-
A few small suggestions, 1- Cases that contain commands do not really need to be added to REWARDS STORAGE. A config option could allow them to be deposited directly into the economy/sr. This would be more practical and safer for server saves. 2- For Exchange, instead of only using an NPC, a small menu inside the UltimateCases UI could be added (SRewards ⇄ Economics). This would make it easier for players to exchange and open cases faster. Best regards. -
Hi, Some virtual quarries placed 1–2 days ago can’t be removed using the trash icon. After updating from 2.5.4 to 2.5.5, I tested it and removal was working correctly, but after some time the issue appeared again. I confirmed that the virtual quarries have no fuel or resources inside and are stopped, but they still can’t be removed. I also tried c.reload VirtualQuarries, with no effect. No warning or error message is shown.
-
Hello, currently the plugin does not have a feature to detect situations like PvP. I’m not sure if we can add this in the future, I’ll need to look into it. -
Hello, you need to use the editor at this link for personal customization https://chaoscode.io/resources/alphaloot-profile-editor.183/
-
.thumb.gif.5a8abec0c69f8a727d95c0dd998c3617.gif)
Thanks for looking into this, we really appreciate it. Hopefully a proper solution can be found, looking forward to your findings after your tests. -
Thank you!
-
Hello @Iftebinjan, the PvE GUI warning is triggered because bullets hit the armored train while shooting NPCs, not because NPCs are immune to damage. Could you please advise how we can prevent or fix this? We noticed that when we set "Player Can Damage Other Player Buildings" to True, the GUI no longer appears when the train takes damage. However, since we are running a full PvE server, this setting is not really suitable for us.
-
Version 1.0.2
27 downloads
Stack Size Controller – Balanced Configuration Packs Includes 4 different configs. Pick one to use, or use different configs on multiple servers. Some stack values are based on the gather rate; however, overall, resources and similar items are set higher based on player experience and community feedback. Server Compatibility - Suitable for 3x, 5x, 10x and PvE servers - If higher stack sizes are desired, the 3x preset can safely be used on 2x servers without causing major balance issues or technical problems Professionally Designed & Tested All configurations are manually created from scratch and are not auto-generated or simple default edits. Each configuration has been: - Actively tested on live servers for over 2 years - Used on long-running, active servers - Adjusted based on real player behavior and feedback - Balanced with economic flow and recycler outputs in mind The goal is to improve quality of life without breaking progression or server economy. Balanced Design Philosophy Not every item is meant to be stacked. Below are the core principles behind how these configurations are designed. Durability & Skin Safety Weapons, clothing, doors, and certain electrical items are intentionally excluded from stacking. These items rely on durability (condition) mechanics and often support skins. Stacking them may cause condition conflicts, incorrect durability behavior, skin desynchronization, and inventory-related bugs. To maintain server stability and predictable gameplay, these item types are deliberately kept unstacked. Explosives & Economy Control F1 Grenades, Smoke Grenades, and similar explosive items are intentionally excluded from stacking or only increased by reasonable amounts. This approach helps prevent gunpowder inflation, balance abuse, and uncontrolled progression. Stackable Item Categories - Resources (Some resources have been stacked above the normal limits in line with strong player demand, especially wood and stone, among others.) - Components (Excessive stacking has not been applied in order to maintain recycling balance; it has been kept at a controlled and balanced level.) - Food items - Medical items - Ammunition Easy Installation 1. Choose one of the 4 configuration presets 2. Copy StackSizeController.json into your config folder 3. Oxide.reload StackSizeController OR c.reload StackSizeController Required Plugin This configuration pack requires the Stack Size Controller plugin. You can download it for free from uMod: https://umod.org/plugins/stack-size-controller$12.99-
- 1
-
-
- #stack size controller
- #stacks
- (and 25 more)
-
Thank you again for your help, the issue has been resolved.
-
They resolved this issue through a Discord ticket. Thank you. -
With the new update, the config settings broke. The update changed all currency settings and forced them back to scrap as the payment method. Could you please check this issue? "Currency: 0 - item, 1 - Economics, 2 - Server Rewards, 3 - Bank System": 0
-
Great plugin, there’s a small bug: when clicking the HOW TO GET KEYS and REWARDS TO STORAGE buttons, the menus that should open sometimes appear behind the server panel.
-
There is no definitive method for this; you need to open the files with a text editor, manually fix them, and translate the language. -
Hello, unfortunately not every plugin supports Turkish language files. Edits need to be made separately for each plugin/config, and this can take a very long time. For this reason, doing the language translation yourself will give the most accurate result.
-
Hello, could you please explain why the Loot Manager dependency is required? Loot was already working quite well with AlphaLoot, so I was wondering if there is a specific or practical reason for adding an additional plugin dependency.
-
.thumb.png.fd415e6a279abcb86097c1d6ea9f77b2.png)
Hello, when upgraded furnaces are picked up using the hammer, the following log error appears in RCON/BattleMetrics. PeaceDuck failed to pickup assets/prefabs/deployable/furnace/furnace.prefab but no valid error reason was given -
Hello again@ThePitereq, could this issue be related to salt water? Some players mentioned they experienced similar behavior when the pump was outputting salt water. You can see the details in the screenshot below, and I’m also attaching our config. { "Misc - Require Permission": false, "Misc - Pump Item Name": "Submersible Pump", "Misc - Pump Ground Check": false, "Misc - Allow Placing On Water Level": false, "Misc - Allow Hammer Hit Pickup": true, "Water Type - Do Not Update Water Type To Freshwater": false, "Water Type - Do Not Update Water Type When Pressing SPRINT Button": true, "Limit - Default Pump Limit (0, to disable)": 2, "Limit - Permission Limits": { "submersiblepump.admin": 100, "submersiblepump.vip": 20 }, "Craft - Enable Pump Craft": true, "Craft - Chat Command": "pump", "Craft - Require Blueprint For Pump": false, "Craft - Required Workbench Level (0-3)": 1, "Craft - Pump Craft Cost": [ { "Item Shortname": "metal.fragments", "Item Amount": 300, "Item Skin": 0 }, { "Item Shortname": "wood", "Item Amount": 300, "Item Skin": 0 }, { "Item Shortname": "metalpipe", "Item Amount": 1, "Item Skin": 0 }, { "Item Shortname": "gears", "Item Amount": 1, "Item Skin": 0 } ] }
-
We do not use any external plugin for this. It may be a temporary general issue. Thank you for the response.
-
PermissionsManager, QuickSmelt, and Vanish configurations have been added. -
Version 1.0.6
67 downloads
AdminWarn is designed for situations where players clearly violate server rules or require a direct and serious warning. With the latest update, an optional popup warning mode has been added alongside the mandatory acknowledgment GUI. This allows admins to send clean, non-intrusive messages displayed at the top of the screen. News: To avoid disrupting gameplay (such as PvP), you can use: /warnpopup <SteamID> <message> /warnpopupall <message> The core purpose of AdminWarn remains unchanged: forcing players to acknowledge warnings. Each mandatory warning includes a single confirmation button, ensuring the player has read and accepted it. Acknowledgment events are tracked via Discord webhook logs, including whether the warning was confirmed while the player was online or after reconnecting. AdminWarn is built for manual use only. It is not an automated warning system. All warnings are intentionally sent by admins using commands. At the same time, the system works intelligently in the background: - Warnings sent to offline players are stored and automatically shown when they next join, even days later. - For online players, warnings remain active until acknowledged, then are automatically cleared. - All data is fully wipe-aware and automatically cleaned on server wipes. Each warning includes built-in in-game sound effects. No external or custom audio files are used. This is not a chat message. Warnings are delivered as visual UI elements that require acknowledgment or appear as optional popup notifications. Even if a player closes the game, mandatory warnings will reappear on the next login until confirmed. No movement restrictions are applied. Warnings can be sent via: - RCON - Server console - In-game admin console (F1) Performance: AdminWarn is built with an optimized and efficient code structure, making its presence virtually unnoticeable on the server. It runs smoothly during long uptimes and maintains stable hook memory and performance values under normal server conditions. Wipe Behavior: - Restarts: Data preserved (approved warnings are auto-deleted for data optimization) - Server wipe: All warning data automatically cleared - No manual cleanup needed (Most of the time, it is not necessary) Commands Chat & Rcon: Note: Player names are not unique and may include different alphabets or special characters. To avoid ambiguity, using Steam64ID is strongly recommended when sending warnings. warn <SteamID> <message> warn <PlayerName> <message> warn <SteamID1>,<SteamID2>,<SteamID3> <message> warn <Name1>,<Name2>,<Name3> <message> warnall <message> warnpopup <SteamID> <message> warnpopup <PlayerName> <message> warnpopup <SteamID1>,<SteamID2>,<SteamID3> <message> warnpopup <Name1>,<Name2>,<Name3> <message> warnpopupall <message> Permissions Oxide/Carbon oxide.grant group admin adminwarn.admin c.grant group admin adminwarn.admin Discord Webhook Logging - Player name/steamid and SteamURL - Warning message / Timestamp - Read status (online/after reconnect) - Logs warning sending - Logs individual warning acknowledgements AdminWarnLangEn.jsonAdminWarnDefaultConfig.json$17.99- 8 comments
- 1 review
-
- 1
-
-
- #admin
- #admin tools
- (and 47 more)
-
I will try this, thank you!- 299 comments
-
- 1
-
-
- #protection
- #base
- (and 5 more)
-
Hello @Mr01sam I’d like to share a constructive suggestion regarding the raid protection system. In practice, this system is frequently abused for griefing. We have observed players deliberately placing structures and turrets directly in front of other players’ bases to block or harass them under protection. To mitigate this, we have already disabled traps in the configuration. However, this alone has not fully resolved player dissatisfaction. From our experience, the plugin would greatly benefit from a limitation mechanism. Specifically, introducing a configurable TC limit per player or clan would significantly reduce abuse while still preserving the core purpose of offline protection. For example: "Max protected cupboards per player/clan": "1", "Max protected Tugboats per player/clan": "2" This feature would encourage players to prioritize protecting their main base while preventing them from placing protected cupboards in front of other players’ bases to block or disrupt gameplay. There may also be alternative approaches on your side that could help address this issue; I hope you will consider evaluating possible solutions. A feature like this would add meaningful control for server owners and help prevent systematic griefing without weakening legitimate base protection. Best regards
-
Hello, One of our players reported the following behavior with the /pump craft pump. After the player disconnects, sprinklers visually continue spraying water, but planters stop receiving water. The system only starts working again after unplugging and reconnecting the pump power. This seems to repeat over time and requires manual resets. When you have time, could you please take a look at this? Thank you for your work and support.
