-
Posts
2,329 -
Joined
-
Last visited
-
Days Won
9
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by IIIaKa
-
Version 0.1.1
125 downloads
The plugin displays the time until restart in the status bar. Depends on AdvancedStatus plugin. The ability to to add and modify any restart plugins; The ability to automatically generate code for restart hooks; The ability to automatically generate language files for different languages(filled in English); The ability to choose between bar types(TimeCounter and TimeProgressCounter); The ability to specify the order of the bar; The ability to change the height of the bar; The abillity to customize the color and transparency of the background; The ability to set a material for the background; The ability to switch between CuiRawImageComponent and CuiImageComponent for the image; The ability to get images from the local folder(*SERVER*\oxide\data\AdvancedStatus\Images); The abillity to set own image and customize the color and transparency of the image; The abillity to set sprite instead of the image; The ability to customize the color, size, font and outline of the text. { "Is it worth generating restart hooks? 0 - disabled, 1 - one-time activation, 2 - always enabled": 2, "List of language keys for creating language files": [ "en" ], "The type of the bar(TimeProgressCounter or TimeCounter)": "TimeCounter", "The height of the bar": 26, "The display order of the bar": 10, "The background color of the bar(HEX or RGBA)": "#E5423F", "The background transparency of the bar": 0.7, "The background material of the bar, leave empty to disable": "", "The URL of the bar image": "https://i.imgur.com/rAiHloW.png", "The local image of the bar, leave empty to use URL": "RestartStatus_Default", "The sprite image of the bar, leave empty to use local or URL": "", "Is it worth using a raw image for the bar?": false, "The color of the bar image(HEX or RGBA)": "#E5423F", "The transparency of the bar image": 1.0, "The outline color of the bar image(HEX or RGBA)": "0.1 0.3 0.8 0.9", "The outline transparency of the bar image": 1.0, "The outline distance of the bar image, leave empty to disable. Example '0.75 0.75'": "", "The size of the bar text": 12, "The color of the bar text(HEX or RGBA)": "#FFFFFF", "The transparency of the bar text": 1.0, "The font of the bar text(https://umod.org/guides/rust/basic-concepts-of-gui#fonts)": "RobotoCondensed-Bold.ttf", "The horizontal offset of the bar text": 0, "The outline color of the bar text(HEX or RGBA)": "#000000", "The outline transparency of the bar text": 1.0, "The outline distance of the bar text, leave empty to disable": "", "The size of the bar subtext": 12, "The color of the bar subtext(HEX or RGBA)": "#FFFFFF", "The transparency of the bar subtext": 1.0, "The font of the bar subtext": "RobotoCondensed-Bold.ttf", "The outline color of the bar subtext(HEX or RGBA)": "0.5 0.6 0.7 0.5", "The outline transparency of the bar subtext": 1.0, "The outline distance of the bar subtext, leave empty to disable": "", "The background color of the progress bar(HEX or RGBA)": "1 1 1 0.15", "The background transparency of the progress bar": 0.15, "Is it worth making the progress reversible?": true, "The color of the bar progress(HEX or RGBA)": "#E5423F", "The transparency of the bar progress": 0.7, "The OffsetMin of the bar progress": "0 0", "The OffsetMax of the bar progress": "0 0", "The list of restart hooks. Note: After modifying hooks, do not forget to toggle hook generation": [ { "Hook triggered at the start of a restart": "OnSmoothRestartInit", "Argument position containing the number of seconds until restart(counting from 0)": 0, "Hook triggered at the cancellation of a restart": "OnSmoothRestartCancelled" }, { "Hook triggered at the start of a restart": "OnRestartScheduled", "Argument position containing the number of seconds until restart(counting from 0)": 0, "Hook triggered at the cancellation of a restart": "OnRestartCancelled" } ], "Version": { "Major": 0, "Minor": 1, "Patch": 1 } } EN: { "BarText": "RESTART IN" } RU: { "BarText": "РЕСТАРТ ЧЕРЕЗ" }$3.99 -
Welcome to the WipeStatus Plugin Discussion Section! Hello! This section is exclusively for discussing WipeStatus plugin. Encountered Issues? If you're facing any difficulties with the plugin's functionality, feel free to create a topic in the Support section for assistance! Ideas and Suggestions? Have ideas to share or new features to suggest? Feel free to start a discussion by creating a topic in the Support section. Feel free to share your thoughts and experiences - together we can make our plugin even better! -
Welcome to the RestartStatus Plugin Discussion Section! Hello! This section is exclusively for discussing RestartStatus plugin. Encountered Issues? If you're facing any difficulties with the plugin's functionality, feel free to create a topic in the Support section for assistance! Ideas and Suggestions? Have ideas to share or new features to suggest? Feel free to start a discussion by creating a topic in the Support section. Feel free to share your thoughts and experiences - together we can make our plugin even better!
-
You are welcome! -
Hello. This one "TEMP PROP, true - Oxide, false - Carbon" If for some reason you don't have this property, try re-downloading the plugin. This is because, for some unknown reason, one hook doesn't work in Carbon. https://codefling.com/files/support/20021-hooks-doesnt-trigger/
- 76 comments
-
- 1
-
-
- #rust
- #industrial
- (and 25 more)
-
I'm not quite sure which messages in the right top corner you're referring to. You can copy the file '*SERVER*\oxide\lang\en\RealPVE.json' to the 'de' folder as '*SERVER*\oxide\lang\de\RealPVE.json' and then replace all the English expressions with German. It's possible that in the next update, I will add the ability to specify language keys(en, de, nl, ru) for auto-creating language files for them. Non-existent language keys in such files will be filled in English, after which you can change them to the desired language. -
If possible, could you please move the preview button to the right? I've developed a habit and whenever I try to make text bold, I end up clicking the preview button
-
I noticed that if you close a support ticket from Pending to Not Bug(for example) and then edit the main message in the ticket, it becomes Pending again. Of course, there's no point in changing the main message after the issue is resolved, but I just wanted to share this observation.
-
Welcome to the BalanceBar Plugin Discussion Section! Hello! This section is exclusively for discussing BalanceBar plugin. Encountered Issues? If you're facing any difficulties with the plugin's functionality, feel free to create a topic in the Support section for assistance! Ideas and Suggestions? Have ideas to share or new features to suggest? Feel free to start a discussion by creating a topic in the Support section. Feel free to share your thoughts and experiences - together we can make our plugin even better! -
Hello. Do I understand correctly that you want to allow all players to destroy other players twig structures if there is no tool cupboard? Is there a specific reason for this? If allowed, it could create a potential griefing issue, as a tool cupboard cannot be placed immediately and players might simply be prevented from placing one. If you're concerned about server clutter due to twig structures, there is a plugin called TwigsDecay for that.
-
Version 0.1.2
529 downloads
Allows toggling silent item giving(chat notifications and ownership) via Harmony patching. P.S. By default, silent item giving is enabled. The ability to disable item ownership assignment; The ability to disable item give messages via the 'give' command; The ability to disable item give messages via the 'giveid' command; The ability to disable item give messages via the 'givearm' command; The ability to disable item give messages via the 'giveequip' command; The ability to disable item give messages via the 'giveto' command; The ability to disable item give messages via the 'giveall' command; The ability to disable item blueprint give messages via the 'giveBp' command; The ability to disable messages about copying player inventory via the 'copyTo' command. silentitemsgive.admin - Grants access to the command silentgive.toggle silentgive.toggle *boolValue*(optional) - Toggle silent item giving. To access this command, you must be an administrator or have the silentitemsgive.admin permission. Example: silentgive.toggle silentgive.toggle trueFree -
Welcome to the SilentItemsGive Plugin Discussion Section! Hello! This section is exclusively for discussing SilentItemsGive plugin. Encountered Issues? If you're facing any difficulties with the plugin's functionality, feel free to create a topic in the Support section for assistance! Ideas and Suggestions? Have ideas to share or new features to suggest? Feel free to start a discussion by creating a topic in the Support section. Feel free to share your thoughts and experiences - together we can make our plugin even better!
-
Agree with AI-generated code. Regarding AI-generated images: I use them for cover designs in some of my plugins because maintaining my plugins already takes a lot of time. I think it would be reasonable to establish some design guidelines, but banning AI-generated images entirely doesn’t seem necessary.
-
Hello, in update 0.1.4, I added the /myperm command (which can be changed). It displays information in chat about the player's current temporary permissions and temporary group. You can find more details on the plugin page in the commands section. -
I don't have access to that plugin. However, I have added the ability to specify mount poses, the full list is at the bottom of the plugin description. FuelStatus displays status bars only for entities that have a fuel system and where the player is sitting in an allowed mount pose. -
Hello, this plugin is compatible with Carbon, the compatibility section was just auto-filled. Regarding the collected data, you can find the full list in the "Collected Data" section on the plugin's description page. However, this is not a final list, it can always be expanded. Just let me know what additional data you would like to be collected. -
I'm telling you, new plugins are released every day, and I don't see the point in giving special attention to each one. I'm simply asking you to add universal hooks for PvE plugins(2-3 lines), player entry and exit(and bags after death) from the arena. That's it, our interaction ends there, there’s no need for a plugin reference. You're worried about the performance difference between HookMethod and CallHook, but again, your arena isn't running 24/7, players aren’t entering and leaving it by the hundreds every second, and your plugin only allows creating one arena at a time(at least, that was the case last time). And again, I already tested the proposed method back in November last year, everything worked as expected if you notify about player entry and exit, as well as the "entry" of the bag(entity) after death. If I'm not mistaken, you forcibly create it yourself. The RealPVE plugin is subscribed to universal hooks that notify PvE plugins about PvP interactions for players and entities. Nothing more is needed in this regard. You're hard to understand, you say you understand why I don’t want to add your hook to the one(OnEntityTakeDamage) that triggers every time damage is received, yet at the same time, you say you won’t add universal hooks "just for one plugin". But how else am I supposed to know that a player is in PvP mode? Fine, you can also call these hooks not through Interface.CallHook but through RealPVE.Call, but what’s the advantage of a direct dependency? You could simply use Interface.CallHook, and any other plugin could subscribe to this hook in the future as well. That way, you wouldn’t have to do the same thing for every new plugin.
-
Players enter and exit the arena far less frequently than the OnEntityTakeDamage hook is triggered. So, what’s the point of checking whether a player is in the arena every single time OnEntityTakeDamage is called? Instead, you can simply notify all PvE plugins once when a player enters the PvP arena and once when they leave. What is the benefit of your suggestion? Your approach involves a constant check on every damage event.
-
Hello, Adding the 'CanEntityTakeDamage' hook will indeed solve this issue for your plugin, but it's a workaround rather than a proper solution. You seem to be forgetting that a server can have over 100,000 entities(depending on map size and other factors). Every entity takes damage, and multiple entities can take damage per second. Each instance of damage is already processed by the RealPVE plugin, and if we add additional calls to your hook, that will at minimum double the number of calls. Then other plugins will start requesting their own hooks as well, just to avoid handling support requestsб further increasing the number of operations per damage event. Additionally, your arena is not active 24/7, meaning that in most cases, calls to your hook would be wasted. When they are relevant, they still create unnecessary server load. That’s why RealPVE is designed to work with general-purpose hooks(listed in the Developer API section) that allow marking or unmarking entities and players as PvP. This avoids the need for extra hook calls every time something takes damage. These are universal hooks, meaning your plugin doesn’t need to know about RealPVE, nor does RealPVE need to be referenced in your plugin. You simply call these hooks when a player enters the arena(PvP mode) and when they leave(there’s no need to call the hook on death). This makes the hooks not only efficient but also universal, any future PvE plugin, not just RealPVE, can utilize them. Your plugin doesn’t need to care about PvE plugins, and PvE plugins don’t need to care about your plugin. Nobody needs to worry about future plugins breaking compatibility. I’ve thoroughly documented these integrations in the Developer API section, probably more extensively than most other developers do for their plugins. You just need to read the documentation and copy-paste a few lines into the appropriate places, replacing them with your identifiers. Before adding these hooks(in November 2024), I even discussed this with you in private messages, explained their purpose, and asked you to add them. I even pointed out exactly where to insert the three necessary lines. I personally tested everything at that time, and it worked perfectly with those changes. However, you stopped responding. So I don’t quite understand why you are now asking me to add this hook when there is a proper solution that you already know about, one that will save server owners valuable performance.
