-
Posts
855 -
Joined
-
Days Won
5
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Khan
-
@ZEODE Building support for a stacking API isn't simple, there are many ways I could code. ( No really I've coded like 5 different methods ) Ultimately it comes down to the best way to add support for it without causing performance issues. In version 3x that is coming API support is included in that version along with many new features. I'd also like to state that no other stack plugin in history has ever supported an API for stacks DUE to Performance problems. That being said, Industrial also already greatly causes performance issues which is why I had to build a whole separate plugin to handle stacks exclusively for industrial movements via harmony patching and introducing limit controls, etc. That means whatever API I build into stack modifier I will also need to include in my Stack-Modifier-Industrial plugin because it handles those stacks as a whole other separate entity to ensure smooth performance. It's not a simple thing to achieve without breaking performance.
- 193 comments
-
- 1
-
-
- #stacks
- #rust stacks
- (and 22 more)
-
Changed Status from Pending to Not a Bug
-
This is not a bug, but a plugin conflict/compatibility issue regarding it's ability to allow stacking of it.
-
It's an oxide LANG bug they changed it so you now need the brackets. {0}
-
Changed Status from Work in Progress to Fixed
-
Ya so, after running some debug code. It's a bug with oxides lang file system not fetching the msg's. Working on some kind of work-around for it..
-
Changed Fixed In to Next Version
-
Changed Status from Pending to Work in Progress
-
Many owners use the blueprint unlock plugins to give out all bps as soon as they connect. The problem is that they were not aware that it included DLC items. For example whispers plugin allows owners to give out all without even knowing about the DLC stuff. BP Sharing plugins like the one on umod also do not check for DLC content when team members join and update everyone's BP data in the team.
-
Right, I meant DLC content being unlocked via BluePrint plugins, but some modify the skin data in the BP data as well, so that the default item crafted is different.
-
The itemdefinition data isn't what's being modified death its the player data. They use the BP info to do it.
-
Regarding the blueprint check method. player.blueprints.CheckSkinOwnership(skinItemId, player.userID) This only works if plugins like ( Blue Print Unlock ) aren't modifying that data to read. This means you'd have to wipe BP data and remove the blue-print plugin until the owner/dev has updated it. Blue Print Sharing plugins are also not updated to handle DLC content.
-
@hid333 I don't really follow? By default everything can be white-listed for you to spawn by simply not black-listing the item or category. So wouldn't it just make more sense to setup the black-listed items accordingly? What's the goal here that your trying to achieve? Are you wanting to be able to create white-listed lists with a permission for each list for different user groups / perks?
-
@Voxidious Currently, stack modifier does not support individual modifications of container sizes / stacks. In version 3x ( still in development ) it will along with some additional functionality coming and an updated UI design. It's going to be an add-on plugin like the Industrial Addon for stack-modifier
- 193 comments
-
- #stacks
- #rust stacks
- (and 22 more)
-
Changed Status from Pending to Can't Reproduce
-
None of the stacks are working after the latest update
Khan replied to SlayersRust's Support Request in Support
Changed Status from Pending to Fixed Changed Fixed In to 2.8.19 -
Changed Status from Pending to Closed
-
so a permission is whatever you have set in the config file, i default them to vip and basic to apply a permission you need to grant it by simply adding the plugin's name with a period: "deathmodifier." in-front of whatever you named the permission so for example the defaults are deathmodifier.vip & deathmodifier.basic If you are using the oxide modding framework then you simply assign the permission to whatever oxide group you want to give the perm to. like: o.grant group default deathmodifier.vip etc here is the umod docs on how to handle / use permissions: https://docs.oxidemod.com/guides/owners/permissions
-
Changed Status from Pending to Fixed Changed Fixed In to 2.8.16
-
Version 1.0.0
10 downloads
Discord Error Logger automatically sends plugin errors to Discord with clickable links to create support tickets, including all the necessary details for developers. Say goodbye to digging through log files or watching the console for issues—everything is delivered clearly and conveniently. NOTES: This plugin will auto generate the configuration file for you & auto update it whenever a new plugin is added. Simply configure the plugins data in the config file to complete the setup! This plugin will also auto-unload plugins that spam errors 10 times or more. Set Plugin Title Name to the URL name, example url for stack modifier: WARNING: This plugin currently only supports click-able links from Codefling & uMod plugins only. Error reporting will still function like normal. Config { "DiscordWebhook": "", "EmbedHexColour": "#2C2F33", "TimeFormat": "o", "Configure Plugin Data": { "stackmodifier": { "Codefling or uMod: False = uMod": true, "Plugin Title Name from Website URL": "stack-modifier" }, "guishop": { "Codefling or uMod: False = uMod": false, "Plugin Title Name from Website URL": "gui-shop" }, "noescape": { "Codefling or uMod: False = uMod": true, "Plugin Title Name from Website URL": "noescape" } } }$9.99 -
- 5 comments
-
- 1
-
-
- #stack modifier
- #industrial
- (and 5 more)
-
Should be fixed for oxide, carbon idk.
-
Changed Status from Work in Progress to Fixed