-
Posts
89 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Singularity12
-
Please add config option to disable being targeted by SamSites
Singularity12 replied to SlayersRust's Support Request in Support
Changed Status from Pending to Not a Bug Changed Fixed In to Next Version -
Please add config option to disable being targeted by SamSites
Singularity12 replied to SlayersRust's Support Request in Support
hey not sure if youre the one I talked to on discord, but we found a workaround! and i'll add it into the next update as well -
-
There's not currently a config for it in the config file because this issue hasn't come up yet. I'll add it in the next update, but until then you can easily edit the .cs file yourself if you'd like. On Line 1237, you can change the 300 to something higher like 1000 or even more depending on the height of your map. Just make sure to leave the f; at the end like in the image. float additionalHeight = 300f;
- 1 reply
-
- 1
-
-
Changed Status from Pending to Fixed Changed Fixed In to 1.0.1
-
I updated the plugin to include the tool cupboard by default, which should've always been the case. I also improved the documentation for how you can adjust the plugin to your own liking and that will better explain how to adjust what you want. To help keep things simple in multiple ways, there is no config file. The two changes that can be made are in the .cs file directly. This shouldn't cause much trouble since the plugin is very rarely updated, and there's little need to because of the open ended way it's written. In fact, this is the first update it has gotten. let me know if you need any further help
-
Changed Status from Pending to Closed Changed Fixed In to 2.4.2
-
-
thank you! I'll check that out right now
-
Changed Status from Pending to Closed Changed Fixed In to 2.4.1
-
Changed Status from Pending to Work in Progress
-
In Paraglider, spawn from jet is only set to activate when you respawn. We use the oxide hook OnPlayerRespawn which isn't supposed to trigger when somebody first joins and spawns the first time, only when the click respawn in the death screen. If someone was dead, and then respawns when they join back, I'm assuming that's where the problem is. Because on that respawn, welcome panel will show along with the jet drop triggering since we're relying on similar hooks. Luckily WelcomePanel only show when you first join using OnPlayerConnected hook. (A hook is basically listening for an event that fires and tells our code when to work. Different events and actions in game call on different hooks.) So someone joining for the first time won't be jet dropped, they'll spawn on the beach with WelcomePanel open. If someone disconnects while dead, they will jet respawn when they come back, but WelcomePanel also opens again. So really it's not an issue unless someone already joined the server (and hence likely read the welcome info) AND disconnected while dead, so at least it's a fairly niche issue. (Maybe a bit less so considering how common alt+f4 is in Rust lol). So not really a bug since the code is working as intended, more a slight incompatibility. Regardless, I'll work on this and try to improve the functionality! Unfortunately, as modders we only have access to so many hooks, I can't simply "postpone" the jet drop until after the welcome panel is closed, because I have no oxide hook that states welcome panel has been shut, but I'll look into how David set it up and see if I can implement that compatibility. But an unfortunate issue with that, is this would have to be implemented seperately for any WelcomePanel style plugins like ServerInfo, and only if they first implent the tools for me to access. That makes me think oxide almost needs a hook for when someone has accepted the server rules or dismissed any welcome panel style plugin.
-
thank you for the extra info, I'll fix it soon!
-
-
Changed Status from Work in Progress to Closed Changed Fixed In to 2.4.0
-
Changed Status from Can't Reproduce to Closed Changed Fixed In to 2.4.0
-
actually I found it wasnt refreshing cached permissions immediately when a groups permissions were revoked and that will be fixed in the next update
-
It seems to be working fine for me and there is a check for the permission in the code, but the permission is cached for performance. It's supposed to update when you grant or revoke permissions, and for me it is, but if in doubt you can reload the plugin and it will re-cache the permissions and ensure its working properly. If it's still happening for you, let me know and I'll try harder to reproduce it, but it should work fine
-
Changed Status from Work in Progress to Can't Reproduce
-
Changed Status from Pending to Work in Progress
-
Changed Status from Pending to Work in Progress
-
Changed Status from Pending to Work in Progress
-
Changed Status from Pending to Not a Bug
-
Changed Status from Pending to Not a Bug
-
Changed Status from Pending to Not a Bug