Cahnu
-
Posts
322 -
Joined
-
Last visited
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Cahnu
-
We were able to get this figured out in a support ticket. This was due to a plugin conflict. -
I'm currently working on a fix for this. It looks like this was broken in a rust update at some point where it stops working for some reason after a couple minutes. I'll put an update out out as soon as I get a solution in place for it. -
Changed Status from Pending to Closed
-
Changed Status from Pending to Not a Bug
-
will consider for future update. Thanks
-
Changed Status from Work in Progress to Closed
-
Changed Status from Pending to Not a Bug
-
May be something I add in the future
-
Changed Status from Pending to Not a Bug
-
Hello, I'm not entirely sure I understand the request here. The plugin uses a default bradley. We don't assign any special ID to it. Skin IDs are typically used for assigning a specific skin to an entity. Not a way to identify a specific entity. I also don't see why you should need each plugin to do this. You could just one plugin check when a bradley dies and check it's location or something to identify if it's the event bradley.
-
Changed Status from Pending to Not a Bug
-
Possibly in a future update. If you want to modify the position yourself for the time being you can do it pretty easily. Just look for where the spawn locations are created for the crates. Feel free to reach out if you need help.
-
Hello, I haven't tested with carbon so I'm not sure if that could be playing a part. I also don't have other reports of this issue right now. What happens when you run the manual start command? Do you get any output in the server console? Do you see any chat message for the event starting? I see where you opened a support request in the past saying you were having an issue but then realized you needed the code here:https://codefling.com/files/support/5314-heavy-cargo-ship-cant-destroy-turrets/ So it looks like it was working for you at that point. At what point did it stop working and start behaving as described in this support request?
-
Changed Status from Pending to Work in Progress
-
Changed Fixed In to 1.1.2
-
Plugin has been updated to correct this issue. Please download the latest version and try again.
-
Changed Status from Pending to Closed
-
I added a config setting for this in the latest version. You can change this setting to false to require checks on manual call as well. "Should the event bypass player proximity check and min/max player threshold when starting manually?"
-
This has now been fixed in the latest update. Please download and try again.
-
Changed Status from Pending to Closed Changed Fixed In to 1.3.0
-
Changed Status from Pending to Can't Reproduce
-
Changed Status from Pending to Closed Changed Fixed In to 1.1.0
-
Should now be fixed in latest updated
