Jump to content

fullwiped

Creator
  • Posts

    492
  • Joined

  • Days Won

    2

Everything posted by fullwiped

  1. fullwiped

    IQAlcoholFarm

    Will this plugin be compatible with the Carbon mod in the future? @Mercury
  2. fullwiped

    raid times

    Thanks. The only issue here might be that players could see 23:59 and go to sleep, not realizing that the raid will continue for another 2 hours, which might disappoint them a bit.
  3. fullwiped

    raid times

    "Saturday": [ { "Start Raid Block(Hours)": 10, "Start Raid Block(Minutes)": 0, "Stop Raid Block(Hours)": 23, "Stop Raid Block(Minutes)": 59 }, { "Start Raid Block(Hours)": 23, "Start Raid Block(Minutes)": 59, "Stop Raid Block(Hours)": 2, "Stop Raid Block(Minutes)": 0 } ], "Sunday": [ { "Start Raid Block(Hours)": 10, "Start Raid Block(Minutes)": 0, "Stop Raid Block(Hours)": 23, "Stop Raid Block(Minutes)": 59 }, { "Start Raid Block(Hours)": 23, "Start Raid Block(Minutes)": 59, "Stop Raid Block(Hours)": 2, "Stop Raid Block(Minutes)": 0 } For example, is this the kind of setting you mean? So that raids start at 10:00 AM and end at 02:00 AM? @AhigaO
  4. fullwiped

    horse

    Hello Whispers88, I hope you're doing well. Some of our players have requests related to "horse dung," as shown in the screenshot. Could a config setting be added for this?
  5. fullwiped

    raid times

    I really liked your plugin, and I have a humble suggestion for you. I think the UI should be much simpler. For example, a small bar could be added on top of UPKEEPTIME. I believe this would fit your plugin perfectly. It could simply be added to the existing UIs—just a suggestion, of course.
  6. fullwiped

    raid times

    "Start Raid Block(Hours)": 12, "Start Raid Block(Minutes)": 0, "Stop Raid Block(Hours)": 23, "Stop Raid Block(Minutes)": 59 In the current config, raids work correctly when set to end at 23:59. This means raids start at 12:00 PM and last until 23:59. However, I want raids to continue until 01:00 or 02:00 at night. I want the raid block period to be from 02:00 to 12:00. How can I set this up?
  7. fullwiped

    Admin Menu

    The alternative to this plugin was consuming an incredible amount of RAM and putting a strain on my servers. This plugin, however, doesn’t cause any issues with RAM usage, which is great. I'm not sure if a feature for temporarily muting users can be added, but it could be very useful.
  8. fullwiped

    Admin Map

    Admin Map is really useful, and I like it a lot. Without it, monitoring and tracking players on the server was really difficult.
  9. fullwiped

    traps and turrets

    Changed Status from Work in Progress to Fixed
  10. fullwiped

    traps and turrets

    @nivexThe number of turrets in buildings has been significantly increased. You can download the new update.
  11. Open the .cs file with Notepad, press CTRL + F, and search for OY to find it easily.
  12. fullwiped

    traps and turrets

    Changed Status from Pending to Work in Progress Changed Fixed In to Next Version
  13. fullwiped

    traps and turrets

    Of course, I will add more traps when I find the time.
  14. fullwiped

    traps and turrets

    Good news.
  15. fullwiped

    traps and turrets

    Hello, in future updates, I might add a few more traps without putting too much strain on the CPU and RAM. Thanks for your suggestion
  16. This command: "Remove Only Listed": false was set to true on my end. I changed it to false, and the issue seems to be resolved. However, the player's name is now changing from blue to green. In RCON, the following error appears. Perhaps this information could contribute to improving this great plugin. Have a nice day! (00:31:32) | Failed to call internal hook 'OnBetterChat' on plugin 'BetterChatGradients v1.0.3' [2030528761] (Object reference not set to an instance of an object) at Dictionary<string, object> Oxide.Plugins.BetterChatGradients.OnBetterChat(Dictionary<string, object> dict) in /home/rustserver/serverfiles/carbon/plugins/BetterChatGradients.cs:line 66 at object Oxide.Plugins.BetterChatGradients.InternalCallHook(uint hook, object[] args) in BetterChatGradients.cs/Internal:line 40 (00:31:32) | Failed to call internal hook 'OnPlayerChat' on plugin 'BetterChat v5.2.14' [2032160890] (Object reference not set to an instance of an object) at FormatSettings Oxide.Plugins.BetterChat+BetterChatMessage.GetOutput() in /home/rustserver/serverfiles/carbon/plugins/BetterChat.cs:line 687 at CancelOptions Oxide.Plugins.BetterChat.SendBetterChatMessage(BetterChatMessage chatMessage, ChatChannel chatchannel) in /home/rustserver/serverfiles/carbon/plugins/BetterChat.cs:line 163 at object Oxide.Plugins.BetterChat.OnPlayerChat(BasePlayer bplayer, string message, ChatChannel chatchannel) in /home/rustserver/serverfiles/carbon/plugins/BetterChat.cs:line 107 at object Oxide.Plugins.BetterChat.InternalCallHook(uint hook, object[] args) in BetterChat.cs/Internal:line 173
  17. Hello, @Reheight I have received reports from players that the /tag command does not work when the server restarts. I checked, and it was not hiding the prefixes. Then, I ran the following command in RCON: c.reload PrefixVisibility After this, it started working. To investigate the issue occurring at server startup, I also tried running: c.reload BetterChat After executing this, I tried using /tag to hide the prefixes again. Although it displayed the message "Your tags will no longer appear in chat", it still did not work. However, when I reloaded PrefixVisibility again using: c.reload PrefixVisibility The /tag command started working properly, and the prefixes were successfully hidden. Is there a solution for this issue? It seems that BetterChat loads later than PrefixVisibility during server startup, which might be causing this problem. I appreciate your advice and assistance. Thank you!
  18. Changed Status from Closed to Fixed Changed Fixed In from 3.1.35.2 to 3.2.0
  19. The new update offers a more stable loot system, especially for Crate Normal 2. You can download and use it. Best regards.
  20. fullwiped

    Carbon

    After a BattleMetrics auto-restart, all mods stopped working. Is there a reason for this? I haven't encountered this issue before.
  21. Version 2.0.1

    42 downloads

    This custom package, created by us, includes 100 handcrafted bases across three difficulty levels, ranging from Easy to Hard. Note: The building skins in the package showcase images may differ from the spawned bases or use the default building skin. If you're looking for a more advanced pack, you can get the upgraded version here, which includes 210 bases ranging from Easy to Nightmare along with the Loot Tables package: https://codefling.com/bases/raidable-bases-mega-pack-loot-tables-210-bases Warning: The Raidable Bases plugin requires the Copy Paste plugin to function. You must install both for this bases pack to work. Raidable Bases (Paid): https://codefling.com/plugins/raidable-bases Copy Paste (Free): https://umod.org/plugins/copy-paste This Raidable Bases package includes: (In addition to the bases, it includes a well-configured config file that can be uploaded to /serverfiles/oxide/config, but its usage is optional. It also contains 5 different profile configs that can be uploaded to /oxide/data/RaidableBases/Profiles. These are also well-configured and optional to use. The usage of both is entirely up to you.) 40 Easy Bases 30 Medium Bases 30 Hard Bases WARNING: TWO DIFFERENT INSTALLATION METHODS (PLEASE READ BOTH AND APPLY ONLY THE ONE THAT FITS YOUR NEEDS) INSTALLATION GUIDE 1 (If you do not have a custom configuration and are not a professional in server configurations, choose this option. However, if you already have your own configuration and profile settings and do not wish to use the optional configs we provide—in other words, if you only need the bases—use the second installation guide instead.) Step 1: Place the Config File From the extracted ZIP files, locate the config folder and find the RaidableBases.json file. Move it to the following directory: /serverfiles/oxide/config Step 2: Place the Bases From the extracted ZIP files, locate the copypaste folder and move it to the following directory: /serverfiles/oxide/data Step 3: Place the Profiles Folder From the extracted ZIP files, locate the profiles folder and move it to the following directory: /serverfiles/oxide/data/RaidableBases Why Are Profiles Important? The profiles folder contains crucial settings that allow you to: Enable/disable the dome Enable/disable NPCs Adjust the number of lootable items These are just a few examples—there are dozens of important settings that directly affect how raid bases function. The config file alone is not enough—these files play a major role in customizing your raid bases. I strongly recommend reviewing each difficulty setting (Easy to Hard) inside the profiles folder and adjusting them based on your needs. Step 4: Restart the plugin via RCON: o.reload RaidableBases INSTALLATION GUIDE 2 (Use this installation method if you do not want to use our configurations and instead prefer to use your own config files and your own /oxide/data/RaidableBases/Profiles configurations.) In this case, you only need to add the bases. To do this, use the following commands in RCON: Step 1: You can add bases one by one or in bulk. After executing the commands in RCON, the bases will be registered inside the Profiles configuration. If you do not want to deal with these adjustments, it is recommended to use Installation Guide 1 instead. A- Example RCON commands: rb.config add "Easy Bases" fullwipedeasy31 rb.config add "Hard Bases" fullwipedhard31 B- Commands to Integrate Raid Bases in Bulk via RCON: rb.config add "Easy Bases" fullwipedeasy31 fullwipedeasy32 fullwipedeasy33 fullwipedeasy34 fullwipedeasy35 fullwipedeasy36 fullwipedeasy37 fullwipedeasy38 fullwipedeasy39 fullwipedeasy40 fullwipedeasy41 fullwipedeasy42 fullwipedeasy43 fullwipedeasy44 fullwipedeasy45 fullwipedeasy46 fullwipedeasy47 fullwipedeasy48 fullwipedeasy49 fullwipedeasy50 fullwipedeasy51 fullwipedeasy52 fullwipedeasy53 fullwipedeasy54 fullwipedeasy55 fullwipedeasy56 fullwipedeasy57 fullwipedeasy58 fullwipedeasy59 fullwipedeasy60 fullwipedeasy61 fullwipedeasy62 fullwipedeasy63 fullwipedeasy64 fullwipedeasy65 fullwipedeasy66 fullwipedeasy67 fullwipedeasy68 fullwipedeasy69 fullwipedeasy70 rb.config add "Medium Bases" fullwipedmed31 fullwipedmed32 fullwipedmed33 fullwipedmed34 fullwipedmed35 fullwipedmed36 fullwipedmed37 fullwipedmed38 fullwipedmed39 fullwipedmed40 fullwipedmed41 fullwipedmed42 fullwipedmed43 fullwipedmed44 fullwipedmed45 fullwipedmed46 fullwipedmed47 fullwipedmed48 fullwipedmed49 fullwipedmed50 fullwipedmed51 fullwipedmed52 fullwipedmed53 fullwipedmed54 fullwipedmed55 fullwipedmed56 fullwipedmed57 fullwipedmed58 fullwipedmed59 fullwipedmed60 rb.config add "Hard Bases" fullwipedhard31 fullwipedhard32 fullwipedhard33 fullwipedhard34 fullwipedhard35 fullwipedhard36 fullwipedhard37 fullwipedhard38 fullwipedhard39 fullwipedhard40 fullwipedhard41 fullwipedhard42 fullwipedhard43 fullwipedhard44 fullwipedhard45 fullwipedhard46 fullwipedhard47 fullwipedhard48 fullwipedhard49 fullwipedhard50 fullwipedhard51 fullwipedhard52 fullwipedhard53 fullwipedhard54 fullwipedhard55 fullwipedhard56 fullwipedhard57 fullwipedhard58 fullwipedhard59 fullwipedhard60 Step 3: Restart the plugin via RCON: o.reload RaidableBases EXTRA IMPORTANT INFORMATIONS: We do not use a dome, NPCs, or arena walls around raid bases on our servers, and in the ZIP file we provided, these features are also disabled by default. If you want to enable them, you will need to adjust the settings accordingly. For example, to enable the dome, follow the steps below: Navigate to: /oxide/data/RaidableBases/Profiles Open the files inside the Profiles folder with a text editor. Locate the following settings: (This is already set to false because it is required for markers to appear on the map.) "Spawn Silently (No Notification, No Dome, No Map Marker)": false, "Create Dome Around Event Using Spheres (0 = disabled, recommended = 5)": 0, Change the value from 0 to 5 as shown below: "Create Dome Around Event Using Spheres (0 = disabled, recommended = 5)": 5, In our setup: - Timed events and purchasable events are disabled. - After a wipe, easy bases will start spawning 30 minutes later. - Nightmare bases will begin spawning 48 hours (2 days) later. Imagine starting the game with just a torch in hand and immediately encountering a nightmare base on the shore. You’d likely quit the game right away—this setting is crucial for us to avoid such scenarios. Configuration Example: serverfiles/oxide/config "Maintained Events": { "Always Maintain Max Events": true, "Max Maintained Events": 30, "Enable X Hours After Wipe (0 = immediately)": { "Easy": 0.5, "Medium": 1.0, "Hard": 3.0, "Expert": 24.0, "Nightmare": 48.0 All of our bases from Easy to Nightmare are equipped with turret protection. If you do not want turrets to spawn in your raidable bases on your server, you can use the following method. Go to the file path /data/RaidableBases/Profiles, open the JSON files inside with a text editor, and apply the following: "Kill These Prefabs After Paste": [ "assets/prefabs/npc/autoturret/autoturret_deployed.prefab", "autoturret_deployed" ], If you need not only these bases but also the loot tables for the items that will spawn inside them, check out our one-of-a-kind, exceptional Raidable Base Loot Tables at the link below: https://codefling.com/customizations/raidable-bases-loot-tables-pack (Our loot tables are designed to cater to different server types, including Vanilla (1x) servers as well as 2x, 3x, 5x, 10x, and higher multipliers to match various loot requirements.) If you are satisfied with this package, you can support us by leaving a 5-star review on the site where you purchased it. Your feedback motivates us to continue improving and providing even better configurations for dedicated server owners like you. Thank you! Support: FULLWIPED DISCORD
    $39.99
  22. Version 2.0.1

    49 downloads

    This custom package, designed by us, features 210 handcrafted bases across five difficulty levels, ranging from Easy to Nightmare. Note: The building skins in the package showcase images may differ from the spawned bases or use the default building skin. This MEGA PACK is an upgraded version of the FullWiped-110 base pack we previously offered. If you've already purchased the FullWiped-110 bases, you only need to buy the expanded package, which includes 100 new bases ranging from Easy to Hard. Get it here: https://codefling.com/bases/raidable-bases-pack-100-bases-expanded-package-from-easy-to-hard Warning: The Raidable Bases plugin requires the Copy Paste plugin to function. You must install both for this bases pack to work. Raidable Bases (Paid): https://codefling.com/plugins/raidable-bases Copy Paste (Free): https://umod.org/plugins/copy-paste This Raidable Bases package includes: (In addition to the bases, it includes a well-configured config file that can be uploaded to /serverfiles/oxide/config, but its usage is optional. It also contains 5 different profile configs that can be uploaded to /oxide/data/RaidableBases/Profiles. These are also well-configured and optional to use. The usage of both is entirely up to you.) 70 Easy Bases 60 Medium Bases 60 Hard Bases 10 Expert Bases 10 Nightmare Bases WARNING: TWO DIFFERENT INSTALLATION METHODS (PLEASE READ BOTH AND APPLY ONLY THE ONE THAT FITS YOUR NEEDS) INSTALLATION GUIDE 1 (If you do not have a custom configuration and are not a professional in server configurations, choose this option. However, if you already have your own configuration and profile settings and do not wish to use the optional configs we provide—in other words, if you only need the bases—use the second installation guide instead.) ▶ Step 1: Place the Config File From the extracted ZIP files, locate the config folder and find the RaidableBases.json file. Move it to the following directory: /serverfiles/oxide/config ▶ Step 2: Place the Bases From the extracted ZIP files, locate the copypaste folder and move it to the following directory: /serverfiles/oxide/data ▶ Step 3: Place the Profiles Folder From the extracted ZIP files, locate the profiles folder and move it to the following directory: /serverfiles/oxide/data/RaidableBases Why Are Profiles Important? The profiles folder contains crucial settings that allow you to: Enable/disable the dome Enable/disable NPCs Adjust the number of lootable items These are just a few examples—there are dozens of important settings that directly affect how raid bases function. The config file alone is not enough—these files play a major role in customizing your raid bases. I strongly recommend reviewing each difficulty setting (Easy to Nightmare) inside the profiles folder and adjusting them based on your needs. ▶ Step 4: Restart the plugin via RCON: o.reload RaidableBases INSTALLATION GUIDE 2 (Use this installation method if you do not want to use our configurations and instead prefer to use your own config files and your own /oxide/data/RaidableBases/Profiles configurations.) In this case, you only need to add the bases. To do this, use the following commands in RCON: ▶ Step 1: You can add bases one by one or in bulk. After executing the commands in RCON, the bases will be registered inside the Profiles configuration. Note: If you do not want to deal with these adjustments, it is recommended to use Installation Guide 1 instead. A- Example RCON commands: rb.config add "Easy Bases" fullwipedeasy1 rb.config add "Hard Bases" fullwipedhard1 B- Commands to Integrate Raid Bases in Bulk via RCON: rb.config add "Easy Bases" fullwipedeasy1 fullwipedeasy2 fullwipedeasy3 fullwipedeasy4 fullwipedeasy5 fullwipedeasy6 fullwipedeasy7 fullwipedeasy8 fullwipedeasy9 fullwipedeasy10 fullwipedeasy11 fullwipedeasy12 fullwipedeasy13 fullwipedeasy14 fullwipedeasy15 fullwipedeasy16 fullwipedeasy17 fullwipedeasy18 fullwipedeasy19 fullwipedeasy20 fullwipedeasy21 fullwipedeasy22 fullwipedeasy23 fullwipedeasy24 fullwipedeasy25 fullwipedeasy26 fullwipedeasy27 fullwipedeasy28 fullwipedeasy29 fullwipedeasy30 fullwipedeasy31 fullwipedeasy32 fullwipedeasy33 fullwipedeasy34 fullwipedeasy35 fullwipedeasy36 fullwipedeasy37 fullwipedeasy38 fullwipedeasy39 fullwipedeasy40 fullwipedeasy41 fullwipedeasy42 fullwipedeasy43 fullwipedeasy44 fullwipedeasy45 fullwipedeasy46 fullwipedeasy47 fullwipedeasy48 fullwipedeasy49 fullwipedeasy50 fullwipedeasy51 fullwipedeasy52 fullwipedeasy53 fullwipedeasy54 fullwipedeasy55 fullwipedeasy56 fullwipedeasy57 fullwipedeasy58 fullwipedeasy59 fullwipedeasy60 fullwipedeasy61 fullwipedeasy62 fullwipedeasy63 fullwipedeasy64 fullwipedeasy65 fullwipedeasy66 fullwipedeasy67 fullwipedeasy68 fullwipedeasy69 fullwipedeasy70 rb.config add "Medium Bases" fullwipedmed1 fullwipedmed2 fullwipedmed3 fullwipedmed4 fullwipedmed5 fullwipedmed6 fullwipedmed7 fullwipedmed8 fullwipedmed9 fullwipedmed10 fullwipedmed11 fullwipedmed12 fullwipedmed13 fullwipedmed14 fullwipedmed15 fullwipedmed16 fullwipedmed17 fullwipedmed18 fullwipedmed19 fullwipedmed20 fullwipedmed21 fullwipedmed22 fullwipedmed23 fullwipedmed24 fullwipedmed25 fullwipedmed26 fullwipedmed27 fullwipedmed28 fullwipedmed29 fullwipedmed30 fullwipedmed31 fullwipedmed32 fullwipedmed33 fullwipedmed34 fullwipedmed35 fullwipedmed36 fullwipedmed37 fullwipedmed38 fullwipedmed39 fullwipedmed40 fullwipedmed41 fullwipedmed42 fullwipedmed43 fullwipedmed44 fullwipedmed45 fullwipedmed46 fullwipedmed47 fullwipedmed48 fullwipedmed49 fullwipedmed50 fullwipedmed51 fullwipedmed52 fullwipedmed53 fullwipedmed54 fullwipedmed55 fullwipedmed56 fullwipedmed57 fullwipedmed58 fullwipedmed59 fullwipedmed60 rb.config add "Hard Bases" fullwipedhard1 fullwipedhard2 fullwipedhard3 fullwipedhard4 fullwipedhard5 fullwipedhard6 fullwipedhard7 fullwipedhard8 fullwipedhard9 fullwipedhard10 fullwipedhard11 fullwipedhard12 fullwipedhard13 fullwipedhard14 fullwipedhard15 fullwipedhard16 fullwipedhard17 fullwipedhard18 fullwipedhard19 fullwipedhard20 fullwipedhard21 fullwipedhard22 fullwipedhard23 fullwipedhard24 fullwipedhard25 fullwipedhard26 fullwipedhard27 fullwipedhard28 fullwipedhard29 fullwipedhard30 fullwipedhard31 fullwipedhard32 fullwipedhard33 fullwipedhard34 fullwipedhard35 fullwipedhard36 fullwipedhard37 fullwipedhard38 fullwipedhard39 fullwipedhard40 fullwipedhard41 fullwipedhard42 fullwipedhard43 fullwipedhard44 fullwipedhard45 fullwipedhard46 fullwipedhard47 fullwipedhard48 fullwipedhard49 fullwipedhard50 fullwipedhard51 fullwipedhard52 fullwipedhard53 fullwipedhard54 fullwipedhard55 fullwipedhard56 fullwipedhard57 fullwipedhard58 fullwipedhard59 fullwipedhard60 rb.config add "Expert Bases" fullwipedexp1 fullwipedexp2 fullwipedexp3 fullwipedexp4 fullwipedexp5 fullwipedexp6 fullwipedexp7 fullwipedexp8 fullwipedexp9 fullwipedexp10 rb.config add "Nightmare Bases" fullwipednight1 fullwipednight2 fullwipednight3 fullwipednight4 fullwipednight5 fullwipednight6 fullwipednight7 fullwipednight8 fullwipednight9 fullwipednight10 ▶ Step 2: Restart the plugin via RCON: o.reload RaidableBases EXTRA IMPORTANT INFORMATIONS: We do not use a dome, NPCs, or arena walls around raid bases on our servers, and in the ZIP file we provided, these features are also disabled by default. If you want to enable them, you will need to adjust the settings accordingly. For example, to enable the dome, follow the steps below: Navigate to: /oxide/data/RaidableBases/Profiles Open the files inside the Profiles folder with a text editor. Locate the following settings: (This is already set to false because it is required for markers to appear on the map.) "Spawn Silently (No Notification, No Dome, No Map Marker)": false, "Create Dome Around Event Using Spheres (0 = disabled, recommended = 5)": 0, Change the value from 0 to 5 as shown below: "Create Dome Around Event Using Spheres (0 = disabled, recommended = 5)": 5, In our setup: - Timed events and purchasable events are disabled. - After a wipe, easy bases will start spawning 30 minutes later. - Nightmare bases will begin spawning 48 hours (2 days) later. Imagine starting the game with just a torch in hand and immediately encountering a nightmare base on the shore. You’d likely quit the game right away—this setting is crucial for us to avoid such scenarios. Configuration Example: serverfiles/oxide/config "Maintained Events": { "Always Maintain Max Events": true, "Max Maintained Events": 30, "Enable X Hours After Wipe (0 = immediately)": { "Easy": 0.5, "Medium": 1.0, "Hard": 3.0, "Expert": 24.0, "Nightmare": 48.0 All of our bases from Easy to Nightmare are equipped with turret protection. If you do not want turrets to spawn in your raidable bases on your server, you can use the following method. Go to the file path /data/RaidableBases/Profiles, open the JSON files inside with a text editor, and apply the following: "Kill These Prefabs After Paste": [ "assets/prefabs/npc/autoturret/autoturret_deployed.prefab", "autoturret_deployed" ], If you need not only these bases but also the loot tables for the items that will spawn inside them, check out our one-of-a-kind, exceptional Raidable Base Loot Tables at the link below: https://codefling.com/customizations/raidable-bases-loot-tables-pack (Our loot tables are designed to cater to different server types, including Vanilla (1x) servers as well as 2x, 3x, 5x, 10x, and higher multipliers to match various loot requirements.) If you are satisfied with this package, you can support us by leaving a 5-star review on the site where you purchased it. Your feedback motivates us to continue improving and providing even better configurations for dedicated server owners like you. Thank you! Support: FULLWIPED DISCORD
    $69.99
2.1m

Downloads

Total number of downloads.

9.7k

Customers

Total customers served.

140.5k

Files Sold

Total number of files sold.

3m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.