Khan
-
Posts
925 -
Joined
-
Days Won
6
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Khan
-
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.
-
Looks like your map dev named all the map placed ones the same name possibly, that or another plugin. Tell them to name them all different to fix it. That or you could try unloading the plugin, deleting the config then load it. -
@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 -
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
14 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 -
@laodu Latest update adds language support. Please test first on a test server ( big update ).- 5 comments
-
- 1
-
-
- #stack modifier
- #industrial
- (and 5 more)
-
Should be fixed for oxide, carbon idk.
-
Changed Status from Work in Progress to Fixed
-
Changed Status from Pending to Not a Bug
-
Changed Status from Pending to Closed
-
If you are using the multiplier then you must offset the stack size be either 1 up or 1 below vanilla for it to not over-ride it. Example: Scrap default 1000 so set it to 1001 or 999 If you toggle on the disable function for the item it blocks stacking for that item all-together as designed.
-
Changed Status from Pending to Not a Bug
-
update 2.8.11 was pulled. previous update was restored.
-
Latest update should resolve this issue.
-
Latest update should resolve that, if it does not then check console for errors or plugin conflicts.
-
Changed Status from Pending to Fixed Changed Fixed In to 2.8.11
-
That would be due to the first update you downloaded that caused that. The second update doesn't cause that. ( That was the whole reason for the 2nd update )
-
Changed Status from Pending to Not a Bug
-
Changed Status from Pending to Not a Bug
