Steenamaroo

Administrator
  • Content Count

    106
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

9 files

  1. Free

    OilrigSpawnFix

    Automatically kills the npc who causes this console spam.
    ""SetDestination" can only be called on an active agent that has been placed on a NavMesh"
     
    No permissions, commands, or instructions. Just install.

    51 downloads

       (0 reviews)

    0 comments

     Submitted

  2. Free

    UpdatesChecker

    Checks for updates for Steenamaroo plugins, and prints to console.
    Reports to console "There is an update available for <plugin name> - Codefling.com".
    Reports for the following :
    UpdatesChecker. BotSpawn. PlayerRanks. PermissionsManager. NPCKits. CustomLoot. InfoScreens. Boom

    282 downloads

       (0 reviews)

    0 comments

     Updated

  3. Free

    BotSpawn

    BotSpawn spawns a set number of Rust AI bots at chosen monuments.
    It also supports bots at server airdrops, supply drops, biomes, custom locations, and 'toplayer' by chat command.
    Offers Facepunch default scientist, murderers, with additional customisation options, including kits.
    * * * * DO NOT UPDATE TO V2.0.00 or later without fully reading the update notes. * * * *
    If you're coming from V1.X.X you may want to install V 2.0.5 first, in order to migrate your old config + data information.

    BotSpawn allows storage of sets of data files.
    Each set has a prefix in their names and a specific set is loaded by setting this prefix in config - DataPrefix = "NameHere",
    Default locations are generated automatically and their settings are held in /oxide/data/BotSpawn/prefix-DefaultProfiles.json. Custom location are added by chat-command and their settings are held in /oxide/data/BotSpawn/prefix-CustomProfiles.json.  
    Optional dependencies -
    Kits - (google uMod Kits) CustomLoot Permissions.
    botspawn.allowed - Required for non-admin use Console commands.
    bot.count - Displays the number of live BotSpawn npcs in console. bots.count - Displays the number of live BotSpawn npcs in console, listed by profile name. botspawn spawn <profilename> - Spawns additional out-of-population npcs, for the given profile. botspawn kill <profilename> - Kills any out-of-population npcs, for the given profile.  
    Notes.
    V2 update notes.
    Your current data is automatically migrated when installing V2.
    Spawns.cs is no longer used, in favour of built-in spawn point records.
    If you use custom spawn points you will need to recreate, or import, these using the new chat commands.

    Default profile names have changed so if you use Parent_Monument for any of your custom profiles,
    you will need to manually change these names to match the new default monument names.

    General notes.
    BotSpawn maintains population based on number of "Bots" in a profile.
    NPCs spawned for airdrops or by 'spawn' or 'toplayer' commands, or by calls from other plugins
    are not considered part of the population and will no respawn on death.

    Without Kits default Scientists/Murders will have nothing in their corpse inventory
    except default Rust random loot - No weapons or clothes.

    All BotSpawn options will govern BotSpawn bots, only.
    The only exception is "NPCs_Attack_BotSpawn" option which prevents outside npcs from attacking BotSpawners.
     
    Configuration.
    "DataPrefix": "default", (tells BotSpawn which data files to load) "DayStartHour": 8, "NightStartHour": 20, "NPCs_Attack_BotSpawn": false, "HTNs_Attacks_BotSpawn": false,(Scarecrows etc npcs will ignore botspawn npcs.) "BotSpawn_Attacks_NPCs": false, "APC_Safe": true, "Turret_Safe": true, "Animal_Safe": true, "Supply_Enabled": false, (spawn 'airdrop' bots for user-called supplys) "Remove_BackPacks_Percent": 100 is always : 0 is never. "Remove_KeyCard": true, (any keycards in bot default loot will be destroyed) "Ignore_HumanNPC": true, (ignore 'bots' from HumanNPCCore plugin) "Ignore_HTN": true/false (botspawn npcs will ignore scarecrows etc.), "Ignore_Sleepers": true/false, "Pve_Safe": true, (bots will not be injured by fire/barbs, etc.) "Max_Chute_Wind_Speed": 100 "Max_Chute_Fall_Speed": 100 *'BotSpawn' are npcs spawned by this plugin.
    *'NPCs' are npcsb spawned by any other means.

    Note - The 'Attacks' global options are preventative.
    False = disable : True = default behaviour.
    Chat commands.
    /botspawn add <customname> - Add a custom profile at your location /botspawn remove <customname> - Remove a custom profile at your location /botspawn move <existingname> - Relocate a custom profile to your location /botspawn list - Show all custom location names /botspawn toplayer <playername> <profile>; - You need to have a custom profile first /botspawn info - Tells you the profile name of the npc you're looking at. /botspawn spawn <profilename> - Spawns additional out-of-population npcs, for the given profile. /botspawn kill <profilename> - Kills any out-of-population npcs, for the given profile. For custom spawn points.
    /botspawn edit <existingname> - Show, and begin editing custom spawn points. /botspawn addspawn - Adds your current location to the spawns for the profile you're editing. /botspawn removespawn - Removes the last-added custom spawn point. /botspawn removespawn <number> - Removes a specific custom spawn point, by number. /botspawn movespawn <number> - Moves a specific custom spawn point, by number. /botspawn loadspawns <FileName> - Imports an exisitng SpawnsDatabase spawns file, and saves. Note: You will need to edit data/BotSpawn.json and set AutoSpawn: "true", as well as any other customisations.
     
    Default locations.
    Events AirDrop Monuments All major monuments are automatically detected and numbered 0/1/2 to allow multiples.
    Biomes
    Arid Temperate Tundra Arctic Note: Radius is irrelevant for biomes Each bot spawns at a random position within the relevant biome.
     
    Options per-profile.
    The following options will be listed once in your data json for each location.
    The only essential setting is AutoSpawn : True. Everything else is preference.
    AutoSpawn- true/false Attacks_Other_Profiles - true/false.* Allow_Rust_Loot_Percent - 100 is always : 0 is never. Bot_Accuracy_Percent 100 is most accurate. Bot_Damage_Percent (dealt)- 100 is greatest amount of damage. Bot Health - 100 is default. Value can exceed 100. Bot Names - [], See below Bot Name Prefix - eg "NPC". Bots - 10 - number of npcs to spawn. Chute - true/false Corpse_Duration: 60 (Seconds) Disable_Radio - true/false. Keep_Default_Loadout - true/false. Keeps Scientist/Murderer attire and weapons, in addition to your custom kits. Kit - [], See below Murderer - True/False Spawns the 'running zombie' murderer prefab instead of Scientist. Peace_Keeper- true/false
    -Bots ignore you if you have no projectile/fire weapon drawn.
    -Melee will do no damage to bots. Peace_Keeper_CoolDown - 5 (seconds) Once aggravated, bots will remain hostile towards you for this period, even if you put away your weapon. Radius - 200 - Size of the area in which bots will spawn. Respawn_Timer - 60 (Seconds). Roam_Range - 40. Aggro_Range - 30. DeAggro_Range - 40. Suicide_Timer - 300 seconds.** Wipe_Belt_Percent - 100 is always : 0 is never. Wipe_Clothing_Percent - 100 is always : 0 is never. Weapon_Drop_Percent - 100 is always : 0 is never. Min_Weapon_Drop_Condition_Percent - 50(%) Max_Weapon_Drop_Condition_Percent - 100(%) Running_Speed_Boost - 0.0 is default. Values of even 1.0 or 2.0 will make a big difference Stationary - true/false - Allows CustomSpawnPoints npcs to exist off navmesh; They will aim and fire but will not move. Announce_Spawn - true/false Announcement_Text - "Custom text here." Spawn_Hackable_Death_Crate - true/false - spawns hackable crate at npc corpse. Death_Crate_CustomLoot_Profile - "CustomLootProfileName Death_Crate_LockDuration - 600 AlwaysUseLights - true/false (ignore time of day) Night_Time_Spawn_Amount - 0 UseCustomSpawns - true/false ChangeCustomSpawnOnDeath - true/false - Killed npc will spawn at his original spawnpoint, or a random one. Die_Instantly_From_Headshot - true/false Instant_Death_From_Headshot_Allowed_Weapons - Shortprefabnames - See below For custom profiles only
    Location - Data only - Do not change manually. Parent_Monument - eg "Dome" Maintains position relative to parent after map seed change.  
    * Murderers will never attack murderers but murd V sci and sci V sci will work fine.
    ** Prevents long term build up of airdrop and toplayer bots.
    ** Does not apply to re-spawning regular bots.

    Kits, Names, and Headshot weapons should be formatted as follows:
    ["kit1"], for single or ["kit1", "kit2", "kit3"], for many.
    ["name1"], for single or ["name1", "name2", "name3"], for many.
    ["lr300.entity"], for single or [ "lr300.entity", "m92.entity" ], for many.

    If there are multiple entries BotSpawn will randomly pick one from the list.
    If the number of kits is equal to the number of bots, BotSpawn will always pair them together in sequence.
    Random names are generated for any blank entries - ["one", "", "three"],.
     
    API.
    Single instance calls.
    These will not respawn (like "toplayer" bots) location is your intended target, profileName is taken from BotSpawn (config or data), and group should be made up and assigned by the user.
    string[] AddGroupSpawn(Vector3 location, string profileName, string group) string[] RemoveGroupSpawn(string group) string NpcGroup(NPCPlayer npc) Long term calls.
    string[] CreateNewProfile(string name, string profile) string[] ProfileExists(string name) string[] RemoveProfile(string name) All returns are string array ["true/false/error", "details message"]
    Also, botspawn can return the Monument Name and a list of live bots, for each AutoSpawn = true monument.
     
    var result = (Dictionary<string, List<ulong>>)BotSpawn?.Call("botSpawnbots");  
    Example call.
    [PluginReference] private Plugin BotSpawn; Vector3 location = new Vector3(0,0,0); string[] Spawn = BotSpawn?.Call("AddGroupSpawn", location, "Dome", "YourNameHere") as string[]; Puts($"{Spawn[0]}"); Puts($"{Spawn[1]}");  
    FAQ.
    Q: There's a million options. Where do I start?
    A: Set AutoSpawn to true for at least one monument in config/BotSpawn.json, then reload the plugin.
    A: Everything else is preference/user customisation.

    Q: My bots disappear or don't move.
    A: It's possible that some belt items and some weapon skins may caused the bots to stop responding.
    A: Try plain weapons only in the belt to troubleshoot.
    A: Failing that, try a different location.
    A: Certain terrain still causes issues for bot spawning.

    Q: Performance sucks.
    A: Try setting ai_dormant = true
    A: If this helps but you'd like to modify the dormancy range, you can specify 'ai_to_player_distance_wakeup_range X'. The default is 160m.
    A: Failing that, please reduce the number of bots.

    Q: My bots won't die?!
    A: Make sure Godmode permissions allow you to do damage.
    A: Same for vanish ^.
    A: If you're running a PVE server, use a PVE plugin which allows you to alter its settings for NPCPlayers.

    Q: I take damage when attacking my bots.
    A: This can also be caused by server, or plugin, PVE settings.

    Q: Will X kill my bots?
    A: Radiation, drowning, falling, and helicopters will not kill your bots.
    A: Turret targeting bots can be toggled. Bradley targeting bots can be toggled.
    A: Fire (campfires etc) will kill your bots. Damage from barbs, cacti etc will kill your bots, but can be prevented with the 'Pve_Safe' config option set to true.

    Q: What weapons can my bots use?
    A: I recommend sticking to basic bullet-weapons, hand tools and melee weapons.
    A: Some weapons may work better than others. Some weapon skins have been known to cause issues and errors.
    A: Please try plain weapons if you're having problems. Scientists are not optimised to use melee, only.
    A: At least one projectile weapon should be given.

    Q: Can I have custom profile locations?
    A: Yes. Your custom locations are stored in data/BotSpawn.json. Use chat command /botspawn add NewNameHere to create a profile at your present location.

    Q: Can I have specific custom spawn points? (underground, etc)
    A: Yes. Use the built in commands to create custom spawn points and set UseCustomSpawns to true, for some profile..
    A: That BotSpawn profile will now ignore radius settings and use the precise spawn points from your file.

    Q: Can I spawn bots at airdrops.
    A: Yes. Airdrop option spawns bots at server drops. Spawn at user-supply call is an additional option.

    Q: My bot kits aren't working.
    A: Console will report if your kit does not exist, or if there is no active weapon there.
    A: Please redeem the kit yourself to an empty inventory, to ensure that you remember to put items in it!
    A: If it's empty, kit yourself out the way you want the kit to be then type: /kit edit NameOfKit and /kit items.

    Q: How can I prove that bots have spawned? I can't find them.
    A: Type bot.count into console.
    A: Respawn timer is taken into account so if you spawn one and kill him, bot.count will show 0 until respawn.

    Q: bot.count console command shows that there are 0 bots.
    A: Double check that at least one monument is set active:true in your config, and reload the plugin.
    A: Also, don't forget their respawn timer. Make sure they aren't all dead when you bot.count.

    3,631 downloads

       (8 reviews)

    21 comments

     Updated

  4. $10.00

    Boom

    Boom is an admin/troll/OP tool which adds c4 explosions to regular weapon damage.
    It's a bit of fun and, with the price tag, an excuse/opportunity to 'donate' and support my real plugins.
     
     
    Details.
    When a player, or turret, has permission any damage that it inflicts with bullets results in a (real) c4 explosion and c4 damage.
    Anything that can be hurt/damaged/broken with bullets will go boom.
    Examples - Animals, players, barrels.
    Trees and nodes, for example, do not take damage and, therefore, do not go boom.
     
    Permissions
    boom.allowed - Allows players to toggle boom.
    boom.turretsallowed - Allows players to toggle boom for their turrets.
     
    Chat Commands
    /boom - Toggles boom on and off for players who have the permission and are not on cooldown.
            Initial use of the /boom command enables the tool and begins 'EnabledMinutes' countdown.
            Subsequent uses will toggle the tool on and off but will not pause the countdown.
    /boomturret - Toggles boom on or off for the turret that a player with the turret permission is looking at, and authorised on.
            Turrets are not subject to a countdown, or cooldown.
     
    Config.
    The config options govern player use of /boom command.
                public int EnabledMinutes = 1; - How long the player can use boom for.
                public int CoolDownMinutes = 1; - How long before player can use boom again.
                public List<string> AllowedWeapons = new List<string>(); - Shortprefabnames of weapons which will make booms.
     
    Notes.
    AllowedWeapons is a List<string> and should be formatted as follows.
    ["lr300.entity"], for single or [ "lr300.entity", "m92.entity", "etc", "etc" ], for many.
    Leaving AllowedWeapons blank enables all weapons.

    6 downloads

       (0 reviews)

    0 comments

     Submitted

  5. Free

    PermissionsManager

    Convenient GUI manager for player and group permissions.
    Allows assignment of player permissions. (online or sleeping) Allows assignment of group permissions. Allows one-click removal of all players from a group.(group page - "Remove All") Allows adding/removing a player from groups. Supports unlimited plugins/permissions/groups Up to 60 plugins per-page. Up to 40 permissions per-page. Up to 40 user groups per-page Permissions.
    permissionsmanager.allowed - Allows players to use GUI, if 'RequiresPermission' is true. Plugin can be used with this permission, or by any Admin : Auth Level 2.
    Chat commands.
    /perms OR /perms player - Opens GUI player list, allowing a player to be chosen. /perms group - Opens GUI group list, allowing a group to be chosen. /perms player <playername> - Opens permissions GUI for the specified player. /perms group <groupname> - Opens permissions GUI for the specified group. Console commands.
    EmptyGroup <groupname> - Removes all players from the specified group. Configuration.
    Global.
    Chat - Title colour Chat - Message colour GUI - Label colour GUI - On colour GUI - Off colour GUI - AllPerPage - Sets All/None option to per-page, or per plugin. Options - GUI Transparency 0-1 Options - Plugin BlockList - ex. "playerranks,botspawn" Block list must be lower case, comma separated, no spaces, and no final comma, as above.
    FAQ.
    Q: I'm trying to revoke permission(Y) for a player, but it says "Inherited".
    A: The player is in a group(X) which is also granted permission(Y).
    Solution: Revoke permission (Y) from group(X) or remove the player from group(X).

    Q: I removed a player from group(X), but they still have permission(Y).
    A: This is the opposite of the above. This player must have been independently granted permission(Y) at some time.
    Solution: Revoke permission(Y) from the player.

    2,838 downloads

       (5 reviews)

    1 comment

     Updated

  6. Free

    NPCKits

    Mange Kits and weapon drop/condition for all default Rust npcs by type.

    General information.
    Give custom Kits to all default Rust npc types, and control what, if anything, becomes lootable when the npc is killed.
    Also has control for dropping weapon on death, weapon condition, and magazine contents.
     
    Optional dependencies.
    Kits.  
    Configuration.
    NPC types.
    Military Tunnel Junkpile Scientist Mounted Scientist (CH47) Compound Scientist BanditTown Murderer ScareCrow CargoShip HeavyScientists Excavator OilRig Options per type:
          "Kits": [],       "Weapon_Drop_Percent": 100,       "Min_Weapon_Drop_Condition_Percent": 100,       "Max_Weapon_Drop_Condition_Percent": 100,       "Dropped_Weapon_Has_Ammo_Percent_Chance": 100,       "Wipe_Main_Percent": 100, - applies to anything placed in main by Kits plugin       "Wipe_Clothing_Percent": 100, - applies to anything placed in clothing by Kits plugin       "Wipe_Belt_Percent": 100, - applies to anything placed in belt by Kits plugin       "Default_Corpse_Loot_Percent": 100 - wipe, or keep, default loot given by Rust  
    Note : Kits follows the same format as BotSpawn kits.
    If multiple are listed, one is chosen at random each time.
    "Kits":["Kit One"] "Kits":["Kit One", "Kit Two", "Kit Three"]  
    API:
    Object hook OnNpcKits(ulong) is provided.
    Return non null to prevent this plugin from giving kits to your spawned npcs.

    383 downloads

       (0 reviews)

    1 comment

     Updated

  7. Free

    CustomLoot

    Formerly NPCLoot.
    Populate npc corpses, containers, and barrels with custom loot.

    General info.
    Users can create as many loottables as required, and assign them to npc/container types by name.

    To create a new loot table, simply set the "lootTable" entry for some container type in config to a new made up name.
    This will create a new /data file of that name, which you can customise.

    The same loot table can be used for multiple corpse types.

    New categories and items are added automatically so, hopefully, data should never need to be wiped.
    Default loottable has all probabilities set to zero and will required customisation.
    I intend to provide some sample loottables for free download in the near future.
     
    Item choice is done by two-tier probability.
    For each spawned item a category is chosen, based on your category probabilities,
    then an item is chosen from that category, based on your item probabilities for that category.
    See notes at bottom for further info on probabilities.
     
    Optional dependencies -
    BotSpawn - V2.0.5 or later. Configuration.
    Global.
    corpseTypePerBotSpawnProfile - true/false allowDuplicates - true/false Include_DM_Crates - true/false NPC types.
    Military Tunnel Junkpile Scientist Mounted Scientist (CH47) Compound Scientist BanditTown Murderer ScareCrow CargoShip HeavyScientists Excavator OilRig BotSpawn * *if Global option 1 is true, this entry is replaced with one entry per existing BotSpawn profile, by name.
    Eg, The Dome 0, Airfield 0, LaunchSite 0, etc.
     
    Container Types
    bradley_crate heli_crate supply_drop dm ammo dm c4 dm construction resources dm construction tools dm food dm medical dm res dm tier1 lootbox dm tier2 lootbox dm tier3 lootbox loot_barrel_1 loot_barrel_2  loot-barrel-1 loot-barrel-2 oil_barrel codelockedhackablecrate crate_basic crate_elite crate_mine crate_normal crate_normal_2 crate_normal_2_food crate_normal_2_medical crate_tools crate_underwater_advanced crate_underwater_basic foodbox minecart trash-pile-1 Options per type:
    "enabled": true/false (governs corpse loot-giving) "lootTable": "default" "minItems": 6 "maxItems": 6 "gunsWithAmmo": true/false "noGuns": true/false "MaxBps": 3 "MaxWeaponCondition: 50 "ClearContainerFirst": true/false Data:
    By default there is one data file : /data/CustomLoot/default.json
    If you specify a unique lootTable name for any corpse or container type,
    a new file will be created in the same folder, by name.
    Eg /CustomLoot/JunkPileLootTable.json
    Each data file contains:
    Blacklist : [] - These items will never spawn, and are removed from loottable.
    Setting to [] will repopulate with default blacklist. AlwaysSpawnList : [] - These items will always spawn, regardless of probabilities.  allowChristmas = false allowHalloween = false allowKeycards = false
    By default all Christmas, Halloween and Keycard items are disabled. Items, grouped by category.
    *Each item has:*
    "probability": 5 "minStack": 10 "maxStack": 50 "skins": [] Categories:
    Ammunition Attire Component Construction Electrical Food Fun Items Medical Misc Tool Traps Resources Weapon Options per category:
    "probability": 5 "allowBlueprints": true  
    API.
    If the called config profile doesn't exist CustomLoot will create it under 'API'.
    Example call.
    [PluginReference] private Plugin CustomLoot; var lootcall = NPC?.Call("MakeLoot", "Npc_Config_Profile_Name"; if (lootcall is string) PrintWarning(string)lootcall);  
    Object hooks are provided to prevent this plugin giving loot to your spawned npcs, or containers.
    Return non-null for the following.
    OnCustomLootNPC(uint) OnCustomLootContainer(uint) Notes.
    *Probability, in both cases above, is relative; There is no scale.
    If there were two categories with probabilities of 9 and 1,
    the first would have a 9 out of 10 chance of being picked.
    Probability of zero effectively means the item, or category is disabled.
    Categories with no enabled items will never be chosen. Their probability is irrelevant.
    Disabled categories will never be chosen. Their probability is irrelevant. 
    Users should never have to manually add, or remove, items in the /data files.
    New items in Rust should be added automatically.
    The blacklist can be used to remove entries from the data file, if that's preferred.
    Reloading is not required to catch up with profile changes made in BotSpawn.

    622 downloads

       (0 reviews)

    3 comments

     Updated

  8. Free

    PlayerRanks

    GUI with personal stats, leaderboard, and per-category stats.
    Tables with personal bests per category, top scoring player per category, and top-30 players per category.
    The same tables can be viewed for clans, rather than players.

    Server-wide top-list per category can be advertised on a timer.
    Tables have clickable headers for ascending/descending sort
    Multiple leaderboard snapshots (top single player for each category) can be taken for SQL/web use.

    Optional uMod dependencies.
    Clans. Economics. EventManager. Friends. PlaytimeTracker.  
    Permissions.
    playerranks.use - Allows players to use GUI, if 'RequiresPermission' is true. playerranks.admin - Allows admin UI and command access. playerranks.excludefromstats - Allows players to toggle /pr optout - taking their stats out of public displays. By default, stats for admins are not publicised.
     
    Chat commands.
    Player commands.
    /pr - Open PlayerRanks GUI /pr chat - Enable/Disable chat announcements. /pr optout - Have your stats removed from, or included in, public displays.
    Requires playerranks.excludefromstats permission. Admin commands.
    /pr save - Save the database /pr wipe - Wipe the database /pr del - Remove all stats for that player's steamID /pr wipecategory <categoryname> - Remove all of user stats for that category Console commands.
    playerranks.save - Save the database playerranks.wipe - Wipe the database  
    Configuration.
    General options.
    displayClanStats - True/False record_ClanMate_Kills - Toggle killing of clan-members contributing to PVPKills. record_FriendsAPI_Kills - Toggle killing of 'Friends' contributing to PVPKills. record_RustIO_Friend_Kills - Toggle killing of RustIO friends contributing to PVPKills. blockEvents - Toggle EventManager contributing to ranks. statCollection - True/False RequiresPermission - Makes user /pr access by 'playerranks.use' permission only. allowadmin - Toggle admin stats in public displays. chatCommandAlias. useTimedTopList - Toggle public broadcast rotation. TimedTopListAmount TimedTopListTimer TimedTopListSize - Font size for chat output. TimedTopListNumbered - Adds ordered numbering to chat output (1st,2nd,etc). deleteOnBan - True/False saveTimer lastLoginLimit - in days.Deletes data for users who haven't logged in since X days ago. Value of 0 means disabled. wipeOnDeath - True/False WipeOnNewMap - Wipes PlayerRanks data base when a new map is detected. useIntenseOptions - Enable/disable.Toggle gathering of information, and displays, relating to: StructuresBuilt ItemsDeployed ItemsCrafted EntitiesRepaired StructuresDemolished Resources Gathered GUI.
    fontColor1/2/3 - Three options available, for title, message, and category.(Will rename soon)
    buttonColour
    guitransparency - 0.0 - 1.0
    Chat Command Alias - Default is "ranks". Change it to whatever you want.
    Categories.
    There is a true/false for every category.
    These can be set via GUI, and prevent data for that category being displayed in-game.
    SQL - optional.
    Database Name Host Password Port Username tablename - Main data table name that PR will create. LBtableName - Leaderboards table name that PR will create. Use MySQL - true/false autoWipe - true/false (wipes SQL with main database) The SQL database will be created on the first save, whether automatic or manually with command /pr save.
    Category List.
    PVPKills PVPDistance PVEKills PVEDistance NPCKills NPCDistance Sleepers Killed HeadShots Deaths Suicides KDR (kill to death ratio) SDR (suicide to death ratio) SkullsCrushed TimesWounded TimesHealed HeliHits HeliKills APC Hits APCKills BarrelsDestroyed Explosives Thrown Arrows Fired Bullets Fired Rockets Launched WeaponTrapsDestroyed Drops looted Structures Built Structures Demolished Items Deployed Items crafted Entities Repaired Resources Gathered Structures Upgraded blockEvents - Toggle EventManager contributing to ranks. Economics** PlayTime** (DD:HH:MM:SS)
    MySQL Only. Online/Offline Status** ActiveDate - Player's last login date. ** - These options are reported by Player Ranks, but not incremented or maintained by Player Ranks.
    Resetting Player Ranks database will not set these entries to zero, as they are read from elsewhere.
    Wipe Playtime Tracker data and/or Economics data to set these to zero.
    Key Binds.
    Personal stats and leader board can be bound to toggle as follows, using H J as examples:
    bind h callPersonalStatsUI bind j callLeaderBoardUI Notes.
    Data for banned players is automatically removed. Heli Kills are attributed to the player who hit the heli the most - not the last hitter. If a player dies from his wounds, the person who wounded him gets the PVP kill. PVP distance is recorded based on the wounding shot.

    844 downloads

       (1 review)

    3 comments

     Updated

  9. Free

    InfoScreens

    Simple set of CUI info pages for Rust servers.
    InfoScreens offers multi-page, and multi-subpage,information viewable by command and also automatically presented when a user joins the server.
     
    ChatCommand
    /infoscreen
    ConsoleCommand
    ISWipe – This clears InfoScreens' record of players who have joined the server.
     
    Configuration
    Global.
    PermaUIButton = false; Creates a permanent 'I' button at screen top right. SideNav = false; - Toggles navigation between top and side. OnlyShowOnce = false; - If true, info is only shown automatically on first-join. NumberOfPages = 4; Automatically creates nav and config entries on reload. GuiTransparency = 0.95; ButtonColour = "0,100,0,1"; ButtonColourSelected = "0,200,0,1"; Colours accept RGBA – maximums 255/255/255/1
    Per-Page.
    VisibleTo - "default,somegroup" Makes a page only visible to the listed groups.
    This is comma separated, with no spaces.
    Each page, by default, has three elements. Two are text and one is image.
    Each element has the following options.
    Text Elements Only.
    "Content": "Some Text Here", - use \n line break for multi-line "FontSize": 16, "FontColour": "255,255,255,1", "AlignTopMiddleBottom": "top/middle/botton", "AlignLeftMiddleRight": "left/middle/right", Image Elements Only
    "URL": "https://...", All Elements
    "GoBehindNav": false, "ShowOnSubPages": "0", "PosBottomToTop": "0.0,1.0", "PosLeftToRight": "0.0,1.0"
      Usage Info.
    The 'Pos...' entries are on a scale 0-1.
    Examples.
    "PosLeftToRight": “0.0,1,0” is full width, left to right. "PosLeftToRight": “0.0,0.5” is half width, left to centre. "PosBottomToTop": "0.0,1.0 is full height, bottom to top "PosBottomToTop": "0.5,1.0" is half height, centre to top Additional elements can be added by copying/pasting/editing name.
     
    'ShowOnSubPages' can be altered and will automatically create next/previous buttons.
    For example, you could have a background image with
    "ShowOnSubPages": "0,1,2",
    then have three content elements showing on “0”, “1”, “2” respectively.
    This will give three sub-pages with different content and the same background, under one nav-heading.

    270 downloads

       (1 review)

    1 comment

     Updated