-
Posts
1,048 -
Joined
-
Days Won
7
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by Khan
-
- 3 comments
-
- #clover
- #st.patricks day
-
(and 7 more)
Tagged with:
-
Version 1.0.1
465 downloads
The No Drop plugin prevents players from dropping items when they are wounded or die. This ensures that all items remain in their inventory system instead of falling to the ground. Features: Prevents active items from dropping on wounded state. Prevents items from dropping on death, including backpacks. Lightweight and optimized for performance. Configuration: This version does not include a config file since item dropping is always disabled. If needed, future updates could add a toggleable setting. Permissions: No permissions are required—this plugin works globally for all players.Free- 1 comment
- 1 review
-
- 1
-
-
- #no drop
- #drop blocker
-
(and 8 more)
Tagged with:
-
-
At the moment the main issue is that customers sometimes buy a plugin expecting the works with section to actually work. But even if you added a yellow notification to indicate that this may not be guaranteed at least then the customer wouldn't be miss-lead in case in that moment support was broken for that listed plugin. Currently the site having a works with section in general is miss-leading for plugins that haven't maintained support.
-
I would argue, that it would give peace of mind to customers & would justify the slight inconvenience to the dev. There could also be auto reject options ( on by default ), etc. But again, just an idea & requires more feedback. A simple poll on discord would provide you with an idea if it'd be something devs would even want at the moment.
-
You should do a poll in Discord and get developer feedback. Poll: Plugin Compatibility System on Codefling Description: Should Codefling introduce a "Works With" verification system that allows plugin developers to opt-in for compatibility with other plugins? Green Verified — Both developers agree to maintain compatibility. Yellow Unverified — One developer has added support, but the other hasn't opted in. Renewable Commitment — Developers can choose 6-month or 1-year support periods. Would you support this system? Yes — Helps users find compatible plugins easily! No — Too much overhead for developers. Maybe — Needs refinement before implementation. Vote below!
-
You could also further push this to be solely up to the devs to support / handle by updating the codefling policy to reflect that. So that at the time a purchase is made if both devs have opted in with a green verified works with then both devs will be required to support it. But if only a yellow check box is next to a works with plugin listed then support is not guaranteed upon purchase. This will keep your 6month warranty in-tact & push the responsibility to devs who have opted in. Also, you can make this a 6-month renew option for devs. So there only obligated to support it for 6-months at a time ( or more ) if you include 1 year option.
-
@Death Then don't make it a moderation issue for codefling. Make it so that a dev can list works with x plugin. Then when that occurs that plugins dev can receive a notification indicating that a dev has marked his as works with & can manually decide to opt in to agree to also maintain 3rd party plugin support with that plugin. ( Basically what we already have now on codefling ) But with the addition / addon--being where the dev is notified of it & can manually choose to opt in for mutual agreed 3rd party support between the 2 plugins. ( And if both have it listed, then a green verified check box will appear next to it on the plugins product page as "verified" to work with each other ) ( And a yellow to indicate that support was added but may not be guaranteed--for those who don't both opt in/one sided )
-
-
@mainloot @Elloco This plugin will never work right on carbon fully, there are still currently multiple bugs with it on carbon that do not occur on oxide & that are not fixable due to how they handle oxide plugins / carbon. Yes the carbon team has made a fair bit of improvements to actually supporting oxide plugins but they still have a long ways to go.
-
- 201 comments
-
- #stacks
- #rust stacks
- (and 22 more)
-
@mainloot Carbon support is impossible, it doesn't support invoking in a custom mono-class because they change the set fields from private to public when an oxide plugin is loaded, also the UI system is slightly different enough which breaks the UI system in this plugin. As well as a few other issues like slight hook differences compared to oxides hook locations resulting in different behavior. So no, carbon support would not be possible.
-
- 9 comments
-
- #khan
- #discordwipeembed
- (and 8 more)
-
- 201 comments
-
- 1
-
-
- #stacks
- #rust stacks
- (and 22 more)
-
Version 1.1.0
38 downloads
With just one tap, you can fully repair your base blocks and base items—no more having to tap repeatedly! Includes permission support and is optimized for top performance, with rotation & demolition support! Features * One Tap Repairs - Supports Base Blocks & Base Items & Vehicles, etc * Rotation - Re-Enables Base Blocks for easy native rotation again! * Demolition - Re-Enables Base Blocks for easy native demolition again! Permissions betterhammer.use ( required to do full 1 tap hit repairs with hammer & to use any features/functions )$4.99 -
- 201 comments
-
- 1
-
-
- #stacks
- #rust stacks
- (and 22 more)
-
- 201 comments
-
- #stacks
- #rust stacks
- (and 22 more)
