-
Posts
74 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Reels
Everything posted by Corvus
-
I remember why now! Even though that's a stack, if you right-click drag one of the AK's out of that stack, it's not broken. This is a weird bug with Rust, if you change the default stack count of normally unstackable items, even though it shows the item as broken, that only represents the state of one of them. Right-click drag one of them out of the stack, and it will be a full durability AK. -
I don't think I've ever tried that. I'm looking into it!
-
Changed Status from Pending to Not a Bug Changed Fixed In to 1.6.7
-
v1.6.7 has blacklisting item and item + skin commands now!
-
Version 1.6.7 resolves this issue.
-
testing a fix.
-
It's not silly, it makes sense. Like probably should already have been a feature, which is silly; on my part.
-
That sounds like an absolutely silly, silly idea. Let me see what I can do.
-
Changed Status from Pending to Fixed Changed Fixed In to 1.14.1
-
Well that's fun. Hopefully that's the last of this issue though.
-
The error message is making me think something weird is going on, if you're seeing version 1.14.1, you shouldn't see EntityFuelSystem_TryUseFuel, because I'm no longer patching the EntityFuelSystem. Could you unload, delete the plugin EasySailing.cs file, and copy a fresh version back to the server? I think I know what's going on, actually. It's a zombie harmony instance. You might have to restart before that fully goes away unfortunately.
-
Something's off, the following no longer exist in 1.14.1: Oxide.Plugins.EasySailing+EntityFuelSystem_TryUseFuel_Patch.Prefix
-
@ALiEN JiM I've released a new version that should address this issue. Let me know if you continue to see any errors. Thanks!
-
I'm looking into it, thanks Jim.
-
no worries, everything working again?
-
Changed Status from Pending to Fixed Changed Fixed In to 1.14.0
-
Hi @Stark This issue was resolved for other users with the same issue in the current version, I'm going to mark this fixed, but if you continue to have an issue, please reopen.
-
Have you tried the most recent version I released earlier today?
-
Are you using RaidableBoats ?
-
I did some testing on my dev server, it's not a simple update after all. There's atleast 3 different variables (smallengine.maxthrustmultiplier, sail.maxthrustmultiplier, and playerboat.velocitymax) exposed via console, but I get mixed results changing them. I wouldn't change them on a live server right away. -
Changed Status from Fixed to Closed
-
Changed Status from No Response to Fixed
-
Changed Status from Pending to No Response Changed Fixed In to 1.13.3
-
Heya, I haven't heard back from you, but I believe the issues you were experiencing were similar enough to what another user had brought to my attention. I'm going to close this support case for now, if you still find you're having the same issue, feel free to reopen. Thanks!
-
Ah, I see what you're saying now. There's a variable that can be set: smallengine.maxthrustmultiplier 1 It defaults to 1, but try setting that from console, that might actually accomplish what you're looking for?
