Khan
-
Posts
1,144 -
Joined
-
Days Won
10
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Reels
Everything posted by Khan
-
@Hanumann It's still in development I recently got some feedback on the development build and will be working more on it this week.
-
@SlayersRust @Pro100Razor111 I've added config options now, as well as several improvements in the latest update.- 22 comments
-
- 1
-
-
- #console
- #spam cleaner
- (and 9 more)
-
The developer finally released an update earlier today with an API hook for me to use to fix the compatibility bug. I have just released an update myself that should make it work together now /
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Work in Progress
-
Changed Status from Pending to Closed
-
-
Changed Status from Pending to Can't Reproduce
-
there was several rust updates recently, i'm working on an update for it.
-
@ninco90 @Wizz The NoEscape API is publicly documented and has remained consistent without changes, so adding support is straightforward. A developer doesn't need to own or personally use the plugin to implement compatibility they simply need to follow the documented API/hooks. Whether someone owns the plugin shouldn't determine whether they can support it. If a plugin exposes a documented API, that's exactly what it's there for.- 451 comments
-
- 1
-
-
- #builder
- #automation
- (and 9 more)
-
Changed Status from Pending to Not a Bug
-
Changed Status from Pending to Fixed
-
Changed Status from Pending to Fixed
- 1 reply
-
- 1
-
-
That can actually be triggered by any plugin because I harmony patch the vanilla method in general. The only problem is I have no way to track down the plugin causing it. I suggest looking at any plugin that messes with building in general like Bgrade plugins auto-upgrade, object stacking, etc I do not have any problems building with my Bgrade plugin or with vanilla.
-
Yes, flip it around so that 5 is the worst starting point and 1 is the best.
-
You can grant out multiple perms but it will default to the highest level perm which is the first one in the list. So basically you have your ordering wrong. You should be defaulting them to like perm 5 the lowest tier and then letting them buy higher tier perms in the shop like 3 to get perm 3 or perm 1 to get perm 1. etc
-
@Kayotics Is the new update working for you?
-
Changed Status from Pending to Closed
-
I just got home from a doc appointment, i've released another update to fix the previous test update. Let me know if it resolves the problem.
-
sorry i had to leave for a doc appointment and couldn't get back before now to release another update.
-
I did not experience this problem on my test server, is it vanilla bots breaking or 3rd party plugins? I pushed a test update out, so let me know if it resolves the issue.
-
"Entity is NULL but is still in saveList - not destroyed properly? industrial.wall.lamp.red.deployed" I don't like filtering out plugin caused problems ideally the developer should update his code so that when they spawn in the entity it's not set to save by default because there destroying it. for now try the latest update.
-
Changed Status from Pending to Fixed Changed Fixed In to 2.9.97
-
Changed Status from Pending to Fixed Changed Fixed In to 2.9.97
- 1 reply
-
- 1
-
-
Changed Status from Pending to Fixed Changed Fixed In to 2.9.97
