-
Posts
3,756 -
Joined
-
Last visited
-
Days Won
211
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by Steenamaroo
-
Private message me the most recent server log file, please, where you joined the server and tried to open PermissionsManager. I'll take a look and see if anything stands out.
-
Yeah, don't worry about UIs from other plugins. We need a concrete way to confirm that you're auth level 2 admin on the server. The best way to do that is to look at the server log / console when you join. It's as simple as connecting to the server and watching the console. If you can confirm that, then confirm you are typing /perms into chat, and that chat is set to 'Global'. If you did all that and are still having issues, then I'd guess some plugin is interfering with your chat input. Do the following commands to unload all plugins, load PermissionsManager, then test PermissionsManager. console - oxide.unload * console - oxide.load PermissionsManager chat - /perms
-
Make sure you're set to global chat. If you already were, check the console logs from when you joined the server (or disconnect and reconnect) and make certain it says you have auth level 2.
-
Hey, Those settings should work, but the marker is for the profile location - Not a specific npc location. It's so that players know the rough area to scout, rather than the precise location of any given npc.
-
If it's affecting multiple plugins, check to make sure you're still admin on the server.
-
- 458 comments
-
- #statistics
- #leaderboard
- (and 12 more)
-
- 458 comments
-
- #statistics
- #leaderboard
- (and 12 more)
-
Hi, I believe I solved this with another user recently. I'll DM you a copy for confirmation. Thanks for reporting.
-
Failed to execute OnFrame callback
Steenamaroo replied to BetterDeadThanZed's Support Report in Support
Not really. Easiest thing to do would probably be to just back up your data file, then unload the plugin, delete the data file, then reload the plugin. If the errors go away, there is something wrong with your data file. If not then it's something else, but the data file is most likely as it isn't null checked in the code. -
Failed to execute OnFrame callback
Steenamaroo replied to BetterDeadThanZed's Support Report in Support
Hi, Sounds like maybe your data file has an issue. I can add a null check to suppress the error, and should, but that won't fix the problem. Check your data file to see if it's broken or contents are null. -
- 235 comments
-
- 2
-
-
-
Oh.... "A lock-on rocket is loaded..." Yeah, that'll be it ^.
-
Hi, RustRewards has no checks or filters on distance but PlayerRanks does. It ignores kills by explosion or heat, for example, when considering kill distance, to cut out scenarios where a player has thrown a grenade then run, or TPd away. Are the kills in the feed from fire or explosions? If not, maybe this person is using explosive rounds and that's causing PlayerRanks to ignore?
-
- 458 comments
-
- #statistics
- #leaderboard
- (and 12 more)
-
Hi, Thanks for reporting. I'll have to look in to that tomorrow and see what's happening. I'll update you when I know more.
-
Hi, What, specifically, were you looking for? Seems Facepunch have introduced a new npc type in certain areas, including the oilrig, which doesn't inherit from BasePlayer, use .userID, or use traditional inventory. Whether alternative approaches are developed in future I can't really say, but, for now, these npcs are fundamentally incompatible with NPCKits/Kits.
-
- 53 comments
-
- 1
-
-
- #updates
- #steenamaroo
-
(and 5 more)
Tagged with:
-
- 458 comments
-
- 1
-
-
- #statistics
- #leaderboard
- (and 12 more)
-
Hi, If I had to guess, most likely a call from another plugin. If, for example, that was a BotReSpawn npc you killed, you have the choice of RustRewards managing and issuing the reward, though the value set in its UI, or BotReSpawn managing the reward through the 'RustRewardsValue' set in its own UI. It's a per-profile option under the 'Death' tab. The reason, or advantage, is that RustRewards can only see 'BotReSpawn' as one broad type, whereas using BotReSpawn UI to manage the rewards lets you have different reward values for different profiles. If both are enabled + greater than zero, you'd see two separate rewards coming through. There are other plugins which operate the same way, giving you the choice, so that's where I'd look.