-
Posts
1,094 -
Joined
-
Days Won
7
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by Khan
-
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.
-
- 202 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)
-
- 202 comments
-
- 1
-
-
- #stacks
- #rust stacks
- (and 22 more)
-
Version 1.1.0
40 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 )$5.00 -
- 202 comments
-
- 1
-
-
- #stacks
- #rust stacks
- (and 22 more)
-
- 202 comments
-
- #stacks
- #rust stacks
- (and 22 more)
-
Move item kick can happen from any plugin ( kits, sorting plugins etc ) any plugin that is messing with items can cause that, considering it's not actively happening for anyone else or myself in my testing I'd be willing to bet it's another plugin causing it, although it would help to see the server console error of that which would have said what it was from, please make a support ticket & I can help you sort out what plugin that is. ( assuming you have the console error ) ?
- 202 comments
-
- #stacks
- #rust stacks
- (and 22 more)
-
@Kaooa Denied Requests 3 & 5: Explanation Requests 3 and 5 were not added, and I have no plans to do so. Here's why: There is already a configurable timer that you can set for how long the raid lasts once it starts. I typically set this to 5 minutes. When continuous damage is inflicted on the base, the timer resets with each new damage, effectively prolonging the raid (the same applies to combat). For this reason, it doesn't make sense to pass through the raid block or combat block times, as they are always updated in real-time. The provided API hooks already give you everything you need to know to block or allow a player to do something, including auto-canceling an action when a combat or raid block occurs.