-
Posts
3,473 -
Joined
-
Last visited
-
Days Won
203
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Steenamaroo
-
- 424 comments
-
- #statistics
- #leaderboard
- (and 12 more)
-
Hi, No, there's no limit at 541, but there are restrictions making only certain types of headshot count. By default headshots don't count against friends/clan mates, or players who are sleeping. There's are also config options PVPHeadshotsOnly - which excludes headshots against npcs and CountHeadshotOnlyIfKill - which only counts headshots which kill a player. The PVPHeadshotsOnly option is reasonably new and the default is true so perhaps your guy was racking up npc headshots and now can't? If so, just set that option to false.
- 424 comments
-
- 1
-
-
- #statistics
- #leaderboard
- (and 12 more)
-
Medical Crates do not work (at least for me)
Steenamaroo replied to jougles's Support Request in Support
If other containers working fine are this loottable is working fine in other containers then I'd guess you have some other plugin modifying that particular container type. Maybe you could unload all plugins then spawn the medical container then load CustomLoot. After a brief wait (and message in console), CustomLoot should populate that container for you. FYI. If you're only giving out medical items then there's no point setting all categories to probability 1, however the plugin is written to ignore categories which have no items with probability greater than zero so, really, it shouldn't make a difference. -
Latest version of Rust Rewards will not load
Steenamaroo replied to Flint Monkey's Support Request in Support
Issues solved in DM. Ended up relating to lang file rather than config. -
Hi, The setting itself hasn't changed but the location of the check has, due to the addition of the Frankenstein clothing options. It used to be this setting was only checked if you had a kit specified whereas now it's checked regardless, because to give frankenstein clothing you'd need Keep_Default_Loadout false (to get rid of the hazmat suit). I've just realised this allows people to create profiles with no weapons so I'll have to juggle that a bit. For now, you'd need to set Keep_Default_Loadout : true for any profiles which aren't being given a kit. Thanks for flagging this! @Psyonide
-
Hi, I did have to tighten up some of my navmesh distance checks to avoid other issues so in some rare cases it may be necessary to move existing spawn points a foot or two either way. If you go into the UI and view that profile "boss" then click through to View Spawnpoints, it should show you the problem ones as red in game, instead of green (not in Ui..in game). For any red ones you can try a few spots in the immediate area, clicking "Check for Navmesh", and if the report is positive then clicking "move here". Hopefully that should clear it up. If not, please let me know!
-
Latest version of Rust Rewards will not load
Steenamaroo replied to Flint Monkey's Support Request in Support
The attached config file is completely empty. Do you have a back up to restore? If so, unload the plugin, copy that file in, then reload. If not, unload the plugin, delete the config file, then reload to get a a new default config. -
Latest version of Rust Rewards will not load
Steenamaroo replied to Flint Monkey's Support Request in Support
I'm not sure what's happened there. I think unload the plugin, close the config file, then reopen it, and see what you have. I guess maybe some change was made with a mistake in it, or something like that? -
Latest version of Rust Rewards will not load
Steenamaroo replied to Flint Monkey's Support Request in Support
Did you make manual changes to the config file recently? That error looks like a mistake in the config file. -
Hi, Yes, the multipliers multiply, so if you have a 2x for something and a 2x for something else you'll have 4x. No, there's no provision, at present, for multipliers based on weapon mods, although it could be done. There's only multipliers for weapons, right now. RustRewards value is a per-profile option in BotReSpawn so you can already increase the value for the harder profiles.
- 1 reply
-
- 1
-
-
Calling kill - but already IsDestroyed!? item_drop_backpack[0]
Steenamaroo replied to Yastreb's Support Request in Support
Hi @shturval I think I've fixed this, but there just hasn't been a public update in a while. I'm planning on releasing one tonight. Thanks for flagging it up! -
Hi, Just remove "ranks", from chatCommandAliases in the config, and reload the plugin.
-
I don't have any sample loottables, no. A default/newly created loottable from CustomLoot provides zero loot, so you start every table from scratch dialling in what you want. Maybe someone else here would be willing to share some of their tables? CustomLoot does a two tier thing, where you lay out probabilities for item categories, then you do probabilities for all the items in each category. You could make it extremely likely that you get something from resources rather than tools, but then make it extremely unlikely that you could scrap over wood, for example. It runs this process for every item that is created.
- 226 comments
-
Hi, No, I'm afraid not. CustomLoot doesn't really work like the vanilla system so it's probably not ideal if you're looking for slight deviations from, or multiples of, vanilla. If you have a very specific idea of what you want to see in certain containers, CustomLoot might be the plugin for those containers.
- 226 comments
-
I could add an option to clear player data but, to be honest, there are probably better ways to achieve what you want. since this would clear the players' UI/notification preferences. Am I right in thinking you want to reward only the players who have re-joined after wipe, or that you want to reward everyone who joins but only once? Either way, that would be a pretty easy standalone plugin to write. I wouldn't mind sorting you out with something, if that's all it is.
-
Hi, BotReSpawn needs navmesh for the npcs to walk around on. This message means BotReSpawn has failed to find random points for that profile. There's a few scenarios where that can happen. That could be because the profile is in the wrong place by mistake, or after a map change, Solution - Use UI to Show All Profiles and check the location of this one is where you expect it to be. Stand in the correct place and click the Move Profile Here button if it isn't. It could be that the profile is in the right place but the spawn radius is set quite small and/or there's a structure or something in the way. This often happens with Dome and SuperMarkets. Solution - Increase profile radius, so there's more open ground available. If you had UseCustomSpawns true and have added custom spawn points manually then I guess you weren't expecting BotReSpawn to look for random points at all. That probably means some of your custom placed spawnpoints are no good, in which case BotReSpawn attempts to fill up the rest of the population with random spawnpoints in the area. Solution - Both of the above, plus use BotReSpawn UI to Edit + View spawnpoints for that profile. The spawnpoints will show up in-game as large numbers. Remove, or replace, any which show red (no navmesh) in game.