-
Posts
131 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Sigilo
-
Version 1.0.1
20 downloads
The OneTimeRewards plugin is designed to provide a one-time reward system for players. It allows server administrators to define a reward group and assign a specific item as a reward to the members of this group. The reward can be claimed by the players using a specific command. Once a player claims their reward, they are removed from the group, ensuring that the reward can only be claimed once. This works well with tebex or other store integration. Just add: When the package is purchased = o.usergroup add {id} groupname For example, you can offer 5 airdrops for x dollars. After the purchase, the player can claim it once via a command. If they buy another, they can claim it again. The plugin is configurable, allowing the server administrators to set the group name, item name, item amount, command name, and the success and failure messages. Usage Instructions Configuration: Configure the plugin by setting the following parameters in the oxide/config file: - GroupName: The name of the group that is eligible for the reward. - ItemName: The name of the item to be given as a reward. - ItemAmount: The quantity of the item to be given. - ItemSkinID: The Skin ID of the item to be given as a reward. - CommandName: The command that players need to use to claim the reward. - SuccessMessage: The message displayed to the player upon successful reward claim. - FailureMessage: The message displayed to the player if they are not eligible for the reward.$2.99 -
If your server for any reason gets disconected from the network for some secconds/minutes (netywork instability, ddos, etc), when you log back in with your admin account, many commands will be disabled like teleport or spectate, and you wont be able to see the server info pressing F1. The solution is to restart the server, or lower the server.encryption to 1, then log in with your admin account and turning it back to 2. Today I had one of my servers in this state, loaded the plugin, reconnected back and it works as intended. This problem that ocasionally interferes with admin work is completely negated by this plugin. Been running it for some hours on a live server, working as intended, no issues on my side.
- 5 comments
-
- #server.encryption 1
- #server.encryption 2
-
(and 1 more)
Tagged with:
-
- 5 comments
-
- #server.encryption 1
- #server.encryption 2
-
(and 1 more)
Tagged with:
-
-
Example Use Scenario: You are using a local trained model to offer in-game support for players, addressing queries about the server and guiding them to alternative support channels. This model could be hosted on your personal computer or another location where it can be online 24/7. In instances when your local model is unavailable, you can seamlessly transition to OpenAI to carry on with the task.
-
- 16 comments
-
- #connect
- #connection
-
(and 3 more)
Tagged with:
-
Your purchase gets you something that works smoothly, tested on populated servers and reflecting a preferred developer's style, as I begin sharing my work publicly. As a long time admin, I lean towards simplicity and functionality, valuing servers that operate effectively over ones with unnecessary extras. This philosophy extends to my plugins as well.
-
-
Version 1.0.3
44 downloads
The KillStreak plugin adds a killstreak system to your server. It tracks players consecutive kills, provides rewards at certain milestones, and maintains a personal and server-wide ranking system. 1. Configuration: Install in your oxide/plugins folder and customize the rewards and killstreak milestones in the configuration file in oxide/config. You can specify the items and quantity for each reward, the message displayed, and whether the kill streak announcement is broadcasted server-wide. If not, it will be sent only to the killer. You can also choose to count npc kills or only pvp kills (default: false) SkinID is supported for the reward items. (see default config below) 2. Permissions: Register the permission killstreak.use to control who can use the killstreak system. 3. Commands: Use the chat commands /ks and /kstop to check your personal killstreaks (current and best) and the server's top 10 killstreaks, respectively. Combines beautifully with https://codefling.com/plugins/kdr-kill-death-ratio Example configuration: { "CountNpcKills": false, "KillsToRestoreHealth": 1, "RewardCommands": { "10": { "BroadcastToServer": true, "Items": [ { "Amount": 5, "Item": "largemedkit", "Skin": 0 }, { "Amount": 5, "Item": "syringe.medical", "Skin": 0 } ], "Message": "Monsterkill!" }, "5": { "BroadcastToServer": true, "Items": [ { "Amount": 5, "Item": "largemedkit", "Skin": 0 }, { "Amount": 5, "Item": "syringe.medical", "Skin": 0 } ], "Message": "Pentakill!" } }, "Version": 1 } If you have any questions or comments contact me via this site or message me directly.$4.99 -
Version 1.8.0
1,450 downloads
The Pop plugin displays the number of connected, connecting, and queued players in a Rust server. It provides commands for individual players to check the server population (/pop) and for broadcasting the server population to all players (!pop) with a configurable cooldown. Features - Displays the number of online, joining, sleepers and queued players (Configurable). - Provides a personal command for individual players to check the server population. - Provides a global command for broadcasting the server population to all players. - Configurable command names, broadcast delay, and color codes for different player statuses. - Supports permissions to control who can use the commands. Permission: pop.use Commands - /pop: Displays the number of online, joining, sleepers and queued players to the player who issued the command. - !pop: Broadcasts the number of online, joining, sleepers and queued players to all players in the server (default 10 min global cooldown). Configuration The configuration options for the plugin are as follows: - Command: The name of the personal command. Default is "/pop". - BroadcastCommand: The name of the global command. Default is "!pop". - OnlineColor: The color code for online players. Default is "#ff686b". - JoiningColor: The color code for joining players. Default is "#ff686b". - QueuedColor: The color code for queued players. Default is "#ff686b". - SleepersColor: The color code for queued players. Default is "#ff686b". - BroadcastDelay: The delay in minutes between broadcasts. Default is 10. - EnablePersonalCommand: Whether to enable the personal command. Default is true. - EnableGlobalCommand: Whether to enable the global command. Default is true. -Show(Online, Joining, Queued and Sleepers): Show or hide the corresponding values. Default config file: { "BroadcastCommand": "!pop", "BroadcastDelay": 10, "Command": "pop", "CustomIconSteamId": 0, "EnableGlobalCommand": true, "EnablePersonalCommand": true, "JoiningColor": "#ff686b", "OnlineColor": "#ff686b", "QueuedColor": "#ff686b", "ShowJoining": true, "ShowOnline": true, "ShowQueued": true, "ShowSleepers": true, "SleepersColor": "#ff686b" }Free -
- 34 comments
-
- #connect
- #connection
-
(and 6 more)
Tagged with:
-
When using a travel command you should be at your base, or naked without anything valuable, because your body will remain in that place the same way that when you manually disconnect from the server. An offline player body depot sounds bad regarding performance. On a normal weekly wipe I receive arround 3k of unique players per server. If 10% of them use this method to travel between servers, keeping 300+ player bodies in a safe zone could be bad. Additionally, you could use this commands to escape pvp, or to fill your inventory with loot when being raided and travel to another server to keep it safe. Anyways if you have some special requirement to fit your particular server, I'm always willing to do some custom work.
- 34 comments
-
- 1
-
-
- #connect
- #connection
-
(and 6 more)
Tagged with:
-
- 34 comments
-
- #connect
- #connection
-
(and 6 more)
Tagged with:
-
- 34 comments
-
- #connect
- #connection
-
(and 6 more)
Tagged with:
-
- 34 comments
-
- #connect
- #connection
-
(and 6 more)
Tagged with:
-
- 34 comments
-
- 1
-
-
- #connect
- #connection
-
(and 6 more)
Tagged with:
-
- 16 comments
-
- #connect
- #connection
-
(and 3 more)
Tagged with:
-
- 34 comments
-
- 1
-
-
- #connect
- #connection
-
(and 6 more)
Tagged with:
-
- 34 comments
-
- 1
-
-
- #connect
- #connection
-
(and 6 more)
Tagged with:
-
This is an example config file for multiple servers: { "Servers": { "server1": { "IP": "155.155.155.155", "Port": 28015 }, "server2": { "IP": "155.155.155.155", "Port": 28025 }, "vanilla": { "IP": "155.155.155.155", "Port": 28035 }, "modx2": { "IP": "12.12.12.12", "Port": 28015 }, "modx5": { "IP": "12.12.12.12", "Port": 28025 } } } as a result, in game you can write: /server1 /server2 /vanilla /modx2 /modx5 to travel to the different servers.
- 34 comments
-
- #connect
- #connection
-
(and 6 more)
Tagged with:
-
is not the same, the one you posted just displays a message that tells you where to reconnect, that wont work for 100% of your clients. Mine reconects you to the destination server after a timer you can set. It also displays a message informing you that you will be reconected. The most important part is that the plugin handles the reconnection, you dont need to write anything on console.
- 16 comments
-
- 1
-
-
- #connect
- #connection
-
(and 3 more)
Tagged with:
-
Version 1.0.2
104 downloads
XTravel: Travel and redirect players to other servers using the Rust Nexus System XTravel is a plugin that allows you to travel between servers using the nexus system with a simple custom chat command. You can configure an unlimited number of destinations in an easy-to-use config file. Just enter the command name (which should be the name of your server), the IP, and the port. Configuration The configuration for the servers can be done in the config file. Here is an example of how to add a server: { "Servers": { "myservername": { "IP": "0.0.0.0", "Port": 28015 } } } In this example, myservername is the command that will be used to travel to this server. Usage instructions To allow a player to use this command, add the following Oxide permission: xtravel.use. In the in-game chat, type: /myservername. For example: /vanilla, /x2, or /coolserverx10. Upon entering the command, a 10-second timer will start, and a message will inform the player that the travel is about to commence. You can cancel the travel during this period by typing /canceltravel. Important note: Player inventories or BP's will not be transferred to the destination server. Admin commands First, add the admin permission: xtravel.admin - /myservername all: It will transport all players in the current server to the destination server. The cooldown cannot be cancelled by players (ex: /serverx2 all). - /myservername steamid: It will transport the specified player to the destination server (ex: /vanillaserver 76561198396973221). The steamid is a 17 digit number. Language files Language files for all messages can be edited in the oxide/lang/en directory. Support If you have any questions or comments, please post them here or contact me directly. Updates The plugin is regularly updated and tested live on multiple servers to ensure flawless operation. Please check the version number in the XTravel.cs file to ensure you are using the latest version.$4.99- 34 comments
- 3 reviews
-
- 2
-
-
- #connect
- #connection
-
(and 6 more)
Tagged with:
-
Version 1.0.1
82 downloads
ServerRedirect automatically redirect your players to another server of your choice on login. Usefull for when you change IP or merge servers. The plugin handles the reconnection, no action is needed by the players. It's 100% automatic. When they log in to the old server, a message will be displayed and they will be redirected to the new IP and port after the timer runs out. No need for permissions, just load the plugin, edit the config with your ip, port, message and timer (seconds) and reload the plugin so it starts redirecting players to your new ip. Example of config file: { "RedirectDelay": 10, "RedirectMessage": "This server has moved IP, you will be redirected in {0} seconds.", "TargetServerIP": "0.0.0.0", "TargetServerPort": 0 }$4.99- 16 comments
-
- 1
-
-
- #connect
- #connection
-
(and 3 more)
Tagged with:
-
- 424 comments
-
- 1
-
-
- #statistics
- #leaderboard
- (and 12 more)