-
Posts
58 -
Joined
-
Last visited
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Reels
Everything posted by MaxiJonson
-
Version 0.3.0
40 downloads
Allows players to subscribe and unsubscribe to broadcast messages sent by other plugins. This helps manage notification fatigue in servers with multiple plugins sending frequent messages. Works on both Oxide and Carbon servers. Features Personalization: Each player can subscribe or unsubscribe to specific broadcast topics. Flexible Categorization: Topics can be defined by server admins to match broadcast messages using regular expressions, allowing for flexible categorization. This also means that this plugin is non-intrusive and works with existing and future plugins without modification. Message Support: Supports broadcasted (Server.Broadcast) and direct (Player.Reply) messages sent from other plugins. Chat Commands /topic - Shows usage information for the plugin. /topic list - Lists all available broadcast topics along with the player's current subscription status. /topic subscribe <topic name|number> - Subscribes the player to the specified topic. Aliases for subscribe: sub, enable, on /topic unsubscribe <topic name|number> - Unsubscribes the player from the specified topic. Aliases for unsubscribe: unsub, disable, off /topic toggle <topic name|number> - Toggles the player's subscription status for the specified topic. Console Commands broadcastpreferences.testbroadcast [message] - Sends a test broadcast message to the console and all players. If no message is provided, a default test message is used. Can be useful for testing your topic regex configurations. broadcastpreferences.testreply [message] - Sends a test direct reply message to all players. If no message is provided, a default test message is used. Can be useful for testing your topic regex configurations. Configuration The config file is oxide/config/BroadcastPreferences.json on Oxide and carbon/configs/BroadcastPreferences.json on Carbon. Player preferences are saved in oxide/data/BroadcastPreferences.json on Oxide and carbon/data/BroadcastPreferences.json on Carbon. { "Topics": [ { "Topic ID": "raidable_bases", "Display Name": "Raidable Bases", "Enabled": true, "Description": "Raidable Bases notifications", "Subscribe By Default": true, "User ID Match (0=Ignore)": 0, "Message Regex Match (empty=Ignore)": [ "raidable base event has opened", "Destroyed a left over raid base at", "Next automated raid in" ], "Override Steam Avatar User ID": 0, "Stop On Match": false, "Ignore Styles": true }, { "Topic ID": "death_notes", "Display Name": "Death Notes", "Enabled": true, "Description": "Player death notifications", "Subscribe By Default": true, "User ID Match (0=Ignore)": 0, "Message Regex Match (empty=Ignore)": ["^\\[DeathNotes\\]"], "Override Steam Avatar User ID": 0, "Stop On Match": false, "Ignore Styles": true }, { "Topic ID": "inbound", "Display Name": "Inbound Events", "Enabled": true, "Description": "Heli, Cargo, Drops and other inbound events", "Subscribe By Default": true, "User ID Match (0=Ignore)": 0, "Message Regex Match (empty=Ignore)": [ "^Patrol Helicopter inbound", "^Cargo Ship inbound", "^Cargo Ship is approaching the harbor", "^Cargo Ship has docked at the harbor", "^Chinook inbound", "^Bradley APC inbound", "^Travelling Vendor inbound", "^Hackable Crate has spawned", "Cargo Plane inbound", " has activated The Excavator", " has requested a supply drop", " is hacking a locked crate", " has deployed a supply signal", "Supply Drop has (dropped|landed)" ], "Override Steam Avatar User ID": 0, "Stop On Match": false, "Ignore Styles": true } ], "Version": { "Major": 0, "Minor": 3, "Patch": 0 } } Topics: An array of topic objects defining the broadcast categories. The order of topics only matters if the Stop On Match option is used. Topics are evaluated in the order they are listed. Topic ID: A unique identifier for the topic. Display Name: The name displayed in chat to players for this topic. Enabled: Whether the topic is active. Description: A brief description of the topic that players will see in the /topic list command. Subscribe By Default: Default subscription status for players who have not explicitly set their preference. User ID Match: If set to a specific user ID, only messages from that user will be considered for this topic. Set to 0 to ignore user ID filtering. This can be useful that allow you to configure the user ID used when sending messages. You can specify a random user ID that will match the topic, then override the avatar using the Override Steam Avatar User ID setting. Message Regex Match: An array of regular expressions used to match broadcast messages for this topic. You may specify multiple regex patterns for a single topic. The first matching pattern will trigger the topic. Override Steam Avatar User ID: If set, this user ID's avatar will be used in notifications for this topic. Particularly useful when combined with the User ID Match setting. Stop On Match: If true, no further topics will be checked after a match is found for this topic. In practice, you shouldn't really need this option unless you've got two topics with overlapping regex patterns. Scenario: Topic A: ^\\[Important\\] with Stop On Match set to true Topic B: Important Message: [Important] Server will restart in 10 minutes. Player is unsubscribed to Topic A but subscribed to Topic B. Result: The message matches Topic A and stops looking for more topics, so the player does not receive the message, even though they are subscribed to Topic B, because Topic A stopped further processing. Ignore Styles: If true, the plugin will strip any <color> and <size> tags from messages before processing them for this topic. Localization The English lang file is oxide/lang/en/BroadcastPreferences.json on Oxide and carbon/lang/en/BroadcastPreferences.json on Carbon. { "TestMessage": "This is a <color=#ff00ff>test message</color> for <color=yellow>Broadcast Subscriptions</color> <color=#f0f>plugin</color>.", "Usage": "Usage:", "Usage.Description": "Listen or mute broadcasted messages by topic.", "Usage.Command": "<color=#f0761f>{0}</color> - {1}", "Usage.List": "Lists available topics", "Usage.Subscribe": "Subscribes to a topic by name or list number", "Usage.Unsubscribe": "Unsubscribes from a topic by name or list number", "Usage.Toggle": "Toggles subscription to a topic by name or list number", "List.AvailableTopics": "Broadcast Preferences (<color=#bcc2c2>Unsubscribed</color> / <color=#62ed53>Subscribed</color>):", "Topic.NotFound": "Topic '{0}' not found.", "Topic.AlreadySubscribed": "You are already subscribed to '{0}'.", "Topic.NotSubscribed": "You are not subscribed to '{0}'.", "Topic.Subscribed": "Subscribed to <color=#62ed53>{0}</color>.", "Topic.Unsubscribed": "Unsubscribed from <color=#bcc2c2>{0}</color>.", "Topic.ListItemSubscribed": "{0}. <color=#62ed53>{1}</color>{2}", "Topic.ListItemUnsubscribed": "{0}. <color=#bcc2c2>{1}</color>{2}" } Guidelines You can test your regex patterns using online tools like Regexr. Check your regex patterns for ReDoS vulnerabilities using tools like Devina's ReDoS Checker. ReDoS vulnerabilities can lead to server performance issues or crashes. Remember about localization: you may (or may not) want to add translated versions of your regex patterns for different server languages. The plugin obviously cannot translate english regexes into other languages automatically.Free-
- #broadcast
- #chat
-
(and 3 more)
Tagged with:
-
Changed Status from Pending to Fixed Changed Fixed In to 1.16.1
-
Changed Status from Pending to Fixed Changed Fixed In to 1.16.1
-
To better consolidate issues from both Lite and Full versions, please submit any support tickets on Discord. I will still respond to support tickets left on Codefling, but am much more responsive on Discord! https://discord.rustcontracts.com
-
To better consolidate issues from both Lite and Full versions, please submit any support tickets on Discord. I will still respond to support tickets left on Codefling, but am much more responsive on Discord! https://discord.rustcontracts.com
-
Hey, just checking if this is still on your radar... That's probably the #1 recurring request from my players to really engage with Drugs. They want a way to sell their large farm yield with less click and dragging (packaging in bulk)
-
The uploaded version is still 1.0.9
-
- 3 comments
-
- #contracts
- #quests
- (and 19 more)
-
- 13 comments
-
- #contracts
- #quests
- (and 19 more)
-
- 3 comments
-
- #contracts
- #quests
- (and 19 more)
-
Version 1.18.2
497 downloads
Contracts is a time-rotating quest system plugin that allows you to create versatile quests/missions that rotate periodically. Each contract can have one or more objectives, with multiple objective types to choose from. It doesn't stop there: each objective can be augmented with objective conditions, which add additional requirements in order to progress it. This allows you to define versatile and unique quests: You could have quests as simple as "Kill 5 scientists"... or a little bit more challenging quests like "Kill 5 scientists with an assault rifle" or have crazy requirements like "Kill 5 scientists, with an assault rifle OR an MP5, between 25-50m away, while being below 20 HP, while wearing a bandana and riding a horse". The possibilities are endless! Not just another quest plugin Most quest plugins hand out static, repeatable, single-objective quests with no cap on how many you can have active at once and no deadline on finishing them. Players end up completing them passively in the background without ever engaging with the system, like achievements. Contracts turns these side-quests into main quests by putting them on a timer. A limited set of contracts is live at a time, each with a real deadline you define, so players have to decide what to prioritize rather than mindlessly clear a checklist. That's what keeps players logging back in throughout the wipe, when they'd otherwise burn out once progression stalls. Contracts also supports multi-objective quests with layered conditions (requirements), so a single contract can demand more than "kill 10 scientists." Simple objectives stack into real challenges. Features (Lite) The following are the limited features of the Lite version. See the Full version's page for the full feature set. Read more about the Lite edition on the website. Highly customizable quests/missions to help you build your unique set of goals and control difficulty beyond just progression amounts required. Control the flow and order of how contract objectives can be completed. 5 objective types to vary gameplay across your server 5 objective condition types to add as many layers of challenge that you want to your objectives Customizable categories and their rotation period, with the possibility to disable rotations altogether and manually control when contracts rotate. Clean and customizable UI for browsing and tracking contracts. Leaderboard to rank your whole server by Contract Score. (limited) Event logging with JSONL format support Powerful Web editor to make editing your configs a breeze and viewing insightful charts on your JSONL logs Quick Links Full Edition Discord Server Full Documentation Web Editor Roadmap Full Plugin Documentation Contracts is a very large plugin with a growing number of features. Documenting everything on the Codefling plugin page (here) can be very intimidating, inconvenient to read/search and drive new users away when they see a wall of text. For these reasons, I've created a structured, digestable and detailed documentation website with guides for new Contracts users! Check it out: https://www.rustcontracts.com Web Editor Nobody wants to be writing complex JSON structures by hand! Head to the Web Editor at https://editor.rustcontracts.com , drop your data configs and start editing your configs in a convenient UI. The quality of the editor and its extensive features are on par with the quality of the plugin! This isn't just simple forms and inputs. Editor Features Convenient UI: Edit all your contracts, categories and presets in a Web-based UI. No manual JSON editing required. Rich Editing Experience: Validation, undo/redo from anywhere, ID refactoring, autocomplete fields, optional raw JSON editing and more QoL features. Data Persistence: Save snapshots of your configs and restore or download them at a later time (data saved in your browser). Advanced Data Importing: You can import entire data files or choose parts of them to merge into your working config. This makes importing new default contracts or shared contracts into your existing config a breeze. AI Generated Contracts: Use the prompt given by the editor in ChatGPT/Claude and paste its response into the editor to generate a contract. Command Palette: Easily navigate through contracts, categories, presets from anywhere in the editor through the command palette. Stats: View your JSONL logs in pre-made charts to gain insights into your contracts, such as pacing and reward balance. Discord Join the official Discord server for support, announcements and more! https://discord.rustcontracts.comFree- 3 comments
- 1 review
-
- #contracts
- #quests
- (and 19 more)
-
Changed Status from Pending to Closed
-
- 13 comments
-
- 1
-
-
- #contracts
- #quests
- (and 19 more)
-
Hey! Yes, so far, only Raidable Bases is on the roadmap , though it's not in the near future plans, as I want to work on the core features of Contracts before integrating other plugins. More integrations may be possible too, though it entirely depends on whether those plugins expose hooks and APIs for Contracts to hook into to listen for progress events. They would also need to be implemented individually, off the top of my head, I don't see how a custom integration that is entirely config-based would be possible, though I really haven't done any research around it.
-
- 25 comments
-
- 1
-
-
Thank you for your reply! Looking forward to it!
-
Hey! Sometimes, the Excavator's supply drop screen is left turned off all the time. Hovering over it shows the "Request Supplies" prompt, as if it's charged and ready, but pressing E does nothing. Reloading the plugin doesn't change anything. However, unloading the plugin will let the screen turn back on (after turning on Excavator manually) so that I can properly call the supplies. Then I can reload the plugin and it will keep working for a while it seems (at least for the rest of the day, until the server restarts). I'll let you know if I figure out reproduction steps, right now it just seems to break at random. VirtualQuarries.json
-
Hey! There's a command to give multiple wrapping papers at once. So originally, I had my shop let users buy in bulk 10-100 wrapping papers. When you buy it in bulk, it gives you a stack of 100 gift wraps (which is fine), but the problem is if you wrap drugs while the gift wraps are still stacked, it uses the whole 100 gift wraps for a single drug packet. Because of this, i've changed the shop to only sell wrapping paper one at a time, so that stacks never happen, which is pretty inconvenient for large-scale farms. Would it be possible to make it so that gift wrapping on a stack only uses one? Another point that was brought up was the possibility of wrapping multiple drug packets at the same time. Maybe an idea would be that you can drag 100 drug leaves into the stacked gift wraps and then have it so it makes 5 drug packs (assuming 20 per pack). Verbatim feedback from one of the users: Let me know what you think. Thanks!
-
Nevermind it was a config issue on my end. I have a script that automatically populates the config's `List of NPC types that should not be deleted` and one of the NpcSpawn's preset has a "Scientist". So my script added "Scientist" to the list of exclusions, which is why they weren't being removed.
-
I was able to recover my custom spawn points by shifting them like so: Missile Silo: +46 on Y (which is odd considering the monument shifted by +20 Y. Maybe try +20 first and if it doesn't work, add another +26) Military Tunnels: +50 on Y (same as the shift for the monument) However, another thing I just noticed is that default NPCs are not being removed like my config is configured to... Unsure if it's related or I (and my players) just never noticed for a while. Though this bug is happening to all my monuments, not just these two. I'll dig around other support cases to see if this was already reported somewhere
-
Give seed command broken since Rust update
MaxiJonson replied to MaxiJonson's Support Report in Support
Actually, maybe it's not related to that... I tried debugging the value that the DrugsAPI receives, but it's like it's never actually being called // DrugDeals.ConsoleCMD_DD_GiveDrugSeed Puts($"Giving {amount} of {arg.Args[1]} seeds to {target.displayName}"); var item = DrugsAPI.Call<Item>("API_CreateDrugSeed", arg.Args[1], amount); // DrugsAPI.API_CreateDrugSeed public Item API_CreateDrugSeed(string displayName, int amount) { Puts($"CreateDrugSeed: {displayName}, amount: {amount}"); // Output [DrugDeals] Giving 1 of Weed Seeds seeds to MaxiJonson [DrugDeals] ERROR: Incorrect command syntax: givedrugseed <steamid> <drug item display name> <amount> The API log never comes through, as if it never got called... -
Hey, this command used to work, but doesn't anymore since this wipe: givedrugseed 76561198240236336 "Weed Seeds" 10 > ERROR: Incorrect command syntax: givedrugseed <steamid> <drug item display name> <amount> It seems the new `arg` syntax doesn't play well with "Spaced Strings"
-
Changed Status from Work in Progress to Fixed
-
Yeah I actually ended up doing something similar too through the Shop plugin since writing this post!
-
In the meantime, I edited the plugin to add a command that opens it, though it would be nice to have a button in the Black Market (either enableable through the config or automatically shown when the drug dealer is disabled) [ChatCommand("dealer")] private void Cmd_Dealer(BasePlayer player, string command, string[] args) { ShowDrugDealerUI(player); }