-
Posts
200 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Reels
Everything posted by Delltus
-
Version 1.0.7
104 downloads
DynamicData — Wipe Progression Automation Automate your wipe. Evolve your server. Stop replacing plugin data files by hand every few hours or days. DynamicData automatically deploys prepared JSON data profiles as your Rust wipe progresses. You decide what should change and when; DynamicData follows the timeline, copies the correct file and reloads the target plugin when needed. Start the wipe with accessible settings. Increase difficulty and rewards after 12 hours. Unlock advanced content on day two. Save heavier changes for the next restart. Once the profiles are prepared, every wipe follows the same progression without an administrator watching the clock. Simple filename-based scheduling There is no complicated calendar to configure. The schedule is written directly into each filename: ```text Settings.json Settings12h.json Settings2d.json [email protected] [email protected] ``` These files all update the same destination, `Settings.json`: - `Settings.json` — applied at the beginning of the wipe - `Settings12h.json` — applied 12 hours after the wipe - `Settings2d.json` — applied two days after the wipe - `[email protected]` — ready after four days, then applied on the next restart - `[email protected]` — applied on the next cold server start Days, hours, minutes and seconds can be combined, for example `1d12h30m`. Keep your existing folder structure DynamicData mirrors nested folders into `oxide/data`. ```text oxide/data/DynamicData/RaidableBases/Profiles/Settings12h.json ``` is deployed as: ```text oxide/data/RaidableBases/Profiles/Settings.json ``` Use the same base filename for stages that must replace one another. Use different filenames when the target plugin needs several separate data files. What can you automate? DynamicData is not tied to one specific plugin. It is ideal for any data-driven plugin whose JSON files can be updated and reloaded during a wipe, including: - raid profiles and difficulty progression - loot tables and reward pools - kit rotations and tier unlocks - NPC and event profiles - economy or shop data - custom server plugins Build an early-, mid- and late-wipe experience using the plugins you already own. Reliable unattended operation - Automatically detects the current wipe timeline - Supports live stages and restart-only stages - Handles several files and destinations due at the same time - Reloads a target plugin only when it is already loaded - Remembers completed stages after reloads and rescans - Tracks applied content per wipe and source file - Validates JSON before replacing live data - Restores the previous file if the target plugin fails to return after reload - Rate-limits deployments to avoid a burst of plugin reloads - Uses deterministic jitter to spread scheduled work - Detects newly added or edited profiles automatically - Preserves nested data folders - Requires no third-party plugin Preview before you launch Administrators can inspect the timeline from the server console or RCON: ```text dyndata.list dyndata.simulate 2d dyndata.simulate all dyndata.rescan dyndata.pause RaidableBases dyndata.resume RaidableBases ``` `dyndata.simulate all` shows the full planned wipe without applying future stages. Individual target plugins can be paused while files are edited or tested. Access is available to server console, RCON, auth level 1+ administrators, or users granted: ```text dynamicdata.admin ``` Quick installation 1. Copy `DynamicData.cs` into `oxide/plugins/`. 2. Let Oxide compile and load the plugin. 3. Create `oxide/data/DynamicData/<TargetPlugin>/`. 4. Add your valid JSON profiles with their time suffixes. 5. Run `dyndata.simulate all` to verify the timeline. The target folder name must match the target plugin's runtime name and root data folder. For example, the `RaidableBases` folder targets the loaded `RaidableBases` plugin and `oxide/data/RaidableBases/`. Requirements - Rust dedicated server - Oxide/uMod - No mandatory third-party dependencies DynamicData validates JSON syntax, but every plugin has its own data structure. Test new profiles on a development server before using them in production. Why server owners use DynamicData Your server no longer has to feel identical from wipe day to the final evening. Create a controlled progression, give players new reasons to return and remove repetitive file management from your weekly routine. Prepare the timeline once. Let every wipe evolve automatically.$14.99 -
Yes I just told you
-
rien de plus dans les langs j'ai envoyer ce qui ce produit dans la console j'ai rechercher mais rien trouver
-
https://gyazo.com/f78a315994286762842df98ec393e21e Échec de l'appel du hook « DeleteBar » sur le plugin « AdvancedStatus v0.1.24 » (NullReferenceException : référence d'objet non définie sur une instance d'objet) à Oxide.Plugins.AdvancedStatus.TryGetWatcher (System.UInt64 userID, Oxide.Plugins.AdvancedStatus+PlayerWatcher& résultat) [0x00000] dans <e5015b43679944ce885ddc2e7b625573>:0 à Oxide.Plugins.AdvancedStatus.DeleteBar (System.UInt64 userID, System.String barId, System.String pluginName) [0x00000] dans <e5015b43679944ce885ddc2e7b625573>:0 à Oxide.Plugins.AdvancedStatus.DeleteBar (BasePlayer player, System.String barId, System.String pluginName) [0x0000c] dans <e5015b43679944ce885ddc2e7b625573>:0 à Oxide.Plugins.AdvancedStatus.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x03c2f] dans <e5015b43679944ce885ddc2e7b625573>:0 à Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] dans <42f9bedc659b4f4786eb778d3cd58968>:0 à Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String nom, System.Object[] args) [0x000de] dans <112d89ea5d3348c8b949af0ab1a866d2>:0 à Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] dans <112d89ea5d3348c8b949af0ab1a866d2>:0
-
Je pense que ce serait une bonne idée s'il n'était pas déjà possible d'ajouter un support pour les mannequins vides dans une version antérieure, en utilisant par exemple furnace, un casier, etc., en les équipant aléatoirement grâce au butin disponible. Cela permettrait d'empêcher le modèle de être récupéré afin de respecter les règles des DLC.
-
Failed to call hook 'DeleteBar' on plugin 'AdvancedStatus v0.1.22' (NullReferenceException: Object reference not set to an instance of an object) at Oxide.Plugins.AdvancedStatus.TryGetWatcher (System.UInt64 userID, Oxide.Plugins.AdvancedStatus+PlayerWatcher& result) [0x00000] in <29bb8138d67a466fbf6373731237f3da>:0 at Oxide.Plugins.AdvancedStatus.DeleteBar (System.UInt64 userID, System.String barId, System.String pluginName) [0x00000] in <29bb8138d67a466fbf6373731237f3da>:0 at Oxide.Plugins.AdvancedStatus.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x03be6] in <29bb8138d67a466fbf6373731237f3da>:0 at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <42f9bedc659b4f4786eb778d3cd58968>:0 at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000de] in <112d89ea5d3348c8b949af0ab1a866d2>:0 at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <112d89ea5d3348c8b949af0ab1a866d2>:0 Failed to call hook 'DeleteBar' on plugin 'AdvancedStatus v0.1.22' (NullReferenceException: Object reference not set to an instance of an object) at Oxide.Plugins.AdvancedStatus.TryGetWatcher (System.UInt64 userID, Oxide.Plugins.AdvancedStatus+PlayerWatcher& result) [0x00000] in <29bb8138d67a466fbf6373731237f3da>:0 at Oxide.Plugins.AdvancedStatus.DeleteBar (System.UInt64 userID, System.String barId, System.String pluginName) [0x00000] in <29bb8138d67a466fbf6373731237f3da>:0 at Oxide.Plugins.AdvancedStatus.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x03be6] in <29bb8138d67a466fbf6373731237f3da>:0 at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <42f9bedc659b4f4786eb778d3cd58968>:0 at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000de] in <112d89ea5d3348c8b949af0ab1a866d2>:0 at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <112d89ea5d3348c8b949af0ab1a866d2>:0
-
-
-
- 861 comments
-
- #shop
- #shop ui
-
(and 26 more)
Tagged with:
- #shop
- #shop ui
- #store
- #market
- #server rewards
- #gui shop
- #custom items
- #rust shop
- #mevent
- #market system
- #marketplace
- #buy
- #sell
- #in game
- #economics
- #humannpc
- #market and magazine
- #gui
- #money exchange
- #rust shop plugin
- #shop system
- #best shop
- #best rust shop
- #shop items
- #shop mevent
- #shop in menu
- #shop gui
- #halloween
-
Hello Your plugin interests me very much, however I would need an addition to make the purchase if possible, On the extractable resources, it would be possible to configure for example the paper and have the possibility of assigning a skin to this object to collect that would make the possibilities greater « Ressources extractibles » : [ { « Nom court de la ressource » : « crude.oil », "Nom de la ressource (vide - par défaut)": "", « Chance d'une ressource dans le cratère [0-100] » : 100, « Quantité minimale [pM] » : 5,0, « Quantité maximale [pM] » : 10,0 } ] },
-
Perhaps you add a function so that when a base has no protection that a pvp bubble is created within the limits of the player's tc, having no protection, or add an API allowing you to do this to distinguish a base which has no protection, because I have a pve / pvp server it is impossible to kill it in pve zone despite the fact that the base has no protection I thank you in advance
- 307 comments
-
- #protection
- #base
- (and 5 more)
-
- 30 comments
-
- 19 comments
-
- 1
-
-
- #announcement plugin
- #announce
-
(and 3 more)
Tagged with:
-
- 19 comments
-
- 1
-
-
- #announcement plugin
- #announce
-
(and 3 more)
Tagged with:
-
- 61 comments
-
- #roamtasks
- #roam
- (and 12 more)
-
- 61 comments
-
- #roamtasks
- #roam
- (and 12 more)
