HumanNPC for Rust (Remod version modded by RFC1920 and Nikedemos)

Adds interactive human NPCs which can be modded by other plugins

Adds customizable, human, non-player characters in-game. Make your cities a little bit more lively!

Download

Requires: Pathfinding, Waypoints

Works with: Kits, GUIShop, NPC Music Player, and a long list of other plugins...

Due to recent changes with Kits 4.0.X, two somewhat temporary commands were introduced:

• 0.3.48: Added /npc_rk -- Removes ALL NPCs from the Kits.json config. Requires reloading of Kits plugin.

  The above was done to undo the command below. In Kits 4.0.9, the logic was reversed from 4.0.8.

• 0.3.47: Added /npc_nk -- Adds ALL NPCs to the Kits.json config. Requires reloading of the Kits plugin.

  In Kits 4.0.8, if an NPC was not listed, the Kits menu would appear on USE. This command was added to populate that list.

Until these are removed, they will persist to either:

1. Add all NPCs to the Kits.json (npc_nk)
2. Remove all NPCs from the Kits.json (npc_rk)

Features

• Fully configurable
• Can say hi when you get close to them
• Can say goodbye when you get away from them
• Can say something when you try interacting with them (USE)
• Can say ouch when you hit them
• Can say that you are a murderer when you kill them
• Multiple messages are supported (random one chosen)
• Set their name
• Set their kits (Kit plugin required)
• Set Waypoints so they can walk around the map
• Set if they are invulnerable
• Set their respawn time if they die
• NPCs can defend themselves
• Set NPC Chasing speed
• Set NPC Damage
• Set NPC Max Chasing distance
• Set NPC Max View distance
• Set NPC Hostility
• Set NPC Evasion when hit
• Have NPC find and sit in a chair it finds in range
• While chasing or using Waypoints, the NPC will try to detect automatically the best ground position (except during evasion, work pending)

Teams

• There can exist many teams.
• Every player/NPC can be a part of one or more teams (or none at all).
• Teams can be friends, neutral or foes towards one another and those relationships can be asymmetrical - meaning, team 1 can consider team 2 friends, while team 2 considers team 1 neutral or foes. There exists a fast Dictionary-based relationship cache for looking up whether User 1 considers User 2 a friend, neutral or enemy. This cache gets re-generated every time something about teams/alignments/members changes. It's generated based upon all the teams alignments and possible conflicts. Members of the same team automatically consider each other friends.
• NPCs have some new properties:
  • bool hostiletowardsarmed
  • bool hostiletowardsarmedhard
  • bool raiseAlarm

Descriptions of these below

Commands

• /npc_add => create a new NPC and edit it
• /npc_edit [id] => edit the NPC you are looking at or specified ID
• /npc_remove [id] => erase the NPC you are looking at or specified ID
• /npc_end => stop editing an NPC
• /npc OPTION VALUE => set a value of an option of your NPC
• /npc_reset => removes all NPCs
• /npc_pathtest => follow NPC path
• /npc_list => list all NPCs
• /npc_way [id] => draws path of the NPC you are looking at or specified ID
• /npc_team => Displays a list of teams, their IDs and their member count
• /npc_team rename [new name] => Gives the team a new name
• /npc_team add [team name, can include spaces] => Adds a team and displays a newly generated ulong ID for it
• /npc_team remove [team name or ID] => Removes a team
• /npc_team empty [team name or ID]
• /npc_team purge => Removes all the team data
• /npc_team member => self-explanatory I hope
• /npc_team member add
• /npc_team member remove
• /npc_team member list
• /npc_team fof [team name or id] => Displays all current 1-sided relationships of the team towards other teams
• /npc_team fof [team name or id] [friend/neutral/foe] [team 2 name or id] => Sets the 1-sided alignment of the team 1 to team 2 (I might implement an optional "mutual" parameter that does the opposite, too - remember, assymetrical relationships)

NPC_ADD
Creates a new NPC, and edits it.
It will be created where you stand, and be looking the same way that you are. Using /npc_add XXXX (npc ID from /npc_list) will clone the NPC to your position

NPC_EDIT
Edit an NPC (not needed if you just did /npc_add) Then you can use the command: /npc

NPC_END
Stop editing an NPC

NPC
By entering the command alone, you will see what values are currently set. Option values:

• attackdistance XX => Distance between NPC and the target needed for the NPC to ignore the target and go back to spawn
• bye reset/"TEXT" "TEXT2" etc => Dont forgot the \", this what will be said when the player walks away from the NPC
• damageamount XXX => Damage done by that NPC when he hits a player
• damagedistance XXX => Min distance for the NPC to hit a player (3 is default, maybe 20-30 needed for snipers?)
• damageinterval XXX => Interval in seconds that the NPC has to wait before attacking again
• enable true/false => Enable (default) or disable the NPC without deleting it (notice that when you are editing a bot it will stay active until you say /npc_end)
• radius XXX => Radius in which the NPC will detect the player
• health XXX => To set the Health of the NPC (limited by rust to max 100)
• hello reset/"TEXT" "TEXT2" etc => Dont forgot the \", this what will be said when the player gets close to the NPC
• hurt reset/"TEXT" "TEXT2" etc => Dont forgot the \", set a message to tell the player when he hurts the NPC
• hostile true/false => Set the NPC Hostile, will attack players on sight (radius is the sight limit)
• ahostile true/false => Set the NPC Hostile, will attack animals on sight (radius is the sight limit)
• invulnerable true/false => To set the NPC invulnerable or not
• kill reset/"TEXT" "TEXT2" etc => Dont forgot the \", set a message to tell the player when he kills the NPC
• kit reset/"KitName" => To set the kit of this NPC, requires the Kits plugin (see below)
• lootable true/false => Set if the NPC is lootable or not
• maxdistance XXX => Max distance from the spawn point that the NPC can run from (while attacking a player)
• name "THE NAME" => To set a name to the NPC
• respawn true/false XX => To set it to respawn on death after XX seconds, default is instant respawn
• spawn new => To set the new spawn location
• speed XXX => To set the NPC running speed (while chasing a player)
• stopandtalk true/false XXX => To set if NPC should stop when a player talks to it, and if true for how much time.
• use reset/"TEXT" "TEXT2" etc => Dont forgot the \", this what will be said when the player presses USE on the NPC
• waypoints reset/"Waypoint list Name" => To set waypoints of an NPC
• hitchance float => chance to hit target
• fireduration float => time to fire
• reloadduration float => time to reload
• defend true/false => attack if attacked
• evade true/false => move if hit while being attacked
• evdist float => how far to move when hit (some randomization is built-in)
• allowsit => Find a chair nearby and sit on spawn
• band NUM => Set band number for external players
• follow => Follow the attacker as they are running out of range (default is true as with older versions)
• sit => Make the NPC sit (toggles allowsit)
• stand => Make the NPC stand (toggles allowsit)
• needsAmmo true/false => needs to have ammo in inventory to shoot
• dropWeapon true/false => Will only drop active item if true
• hostiletowardsarmed => If true, the NPC will look in the players belt and, if it finds any tools, weapons, traps or anything considered "bad" (the list of items is based on categories, but this can be customised/expanded upon), it will attack the player when they cross its interaction radius. If the NPC is supposed to raise the alarm, they will.
• hostiletowardsarmedhard => If true, when performing the strip-search, the whole inventory is checked. Next step, making this work AFTER the player has crossed the NPC's interaction radius. At the moment, you can approach a strip-searching NPC with no weapon, take it out, and they will do nothing.
• raiseAlarm => If true, the npc will send a distress "signal" (along with a chat message), limited to the number of NPCs that answer it (default 0 = no limit). A visibility check in the sphere of radius based on one of the existing distance values is performed. All the NPCs that the alarm raiser can see will receive this call, but not all of them will answer it. Hostile NPCs will only answer alarm calls from their team members (ignoring teams that are friends with their team). Non-hostile NPCs will answer the calls all friends. I might also implement an extra flag like "white knight" that will make an NPC answer every distress call, what do you think?

NPC WAYPOINTS:

You will need to make waypoints with the Waypoints plugin. Create a set of waypoints with NAME and use /npc waypoints NAME when editing your NPC.

NPC KIT:

You will need the Kits plugin. Create a new kit with the kit plugin like you usually do, then:

/kit add NAME "random description" -authlevel2 (the level is set so NO players can use the kit, only admins and NPCs) Then while editing the NPC do: /npc kit NAME (being the same name as the kit ofc)

NPC ATTACK MOVEMENTS & PATHFINDING:

The Pathfinding is still not perfect, but it's getting there. Currently, the main problem isn't really coming from the Pathfinding but from the HumanNPC plugin because of the way i wrote it, so I'll need to rewrite a part of the plugin to make better movements and player attacks.
You will need to download PathFinding for Rust to make the NPC attack movements work. If the NPC can't find any paths for 5 seconds it will stop targetting the entity and go back to its spawn point with full health.

For Developers

Hooks were implemented to allow other plugins to interact with this one. None of them have return values (can be edited if needed). New hooks can be added if they make sense.

Note: All NPC have unique userIDs, (BasePlayer.userID), so you may easily save information of NPC by userID.

Called when the NPC is getting hit

 OnHitNPC(BasePlayer npc, HitInfo info)

Called when the NPC is getting used (pressed use while aiming the NPC)

 OnUseNPC(BasePlayer npc, BasePlayer player)

Called when a player gets in range of the NPC

 OnEnterNPC(BasePlayer npc, BasePlayer player)

Called when a player gets out of range of the NPC

 OnLeaveNPC(BasePlayer npc, BasePlayer player)

Called when an NPC gets killed

 OnKillNPC(BasePlayer npc, BasePlayer player)

Called when an NPC reachs a waypoint and changes to next waypoint

 OnNPCPosition(BasePlayer npc, Vector3 pos)

Called when an NPC respawns

 OnNPCRespawn(BasePlayer npc)

Called when an NPC gets looted

 OnLootNPC(PlayerLoot loot, BaseEntity target, string npcId)

Spawn an NPC; Returns new npcId

 private ulong SpawnHumanNPC(Vector3 position, Quaternion currentRot, string name = "NPC", ulong clone = 0)

Remove an NPC;

  private void RemoveHumanNPC(ulong npcid)

Give an item to an NPC by name

  private void GiveHumanNPC(ulong npcid, string itemname, string loc = "belt")

Set NPC Info

  private void SetHumanNPCInfo(ulong npcid, string info, string data)

Usages

• Make your server more lively with NPCs that talk and interact a bit with players
• Create Epic mobs that spawn every X time and once killed gives loot (use Rust Kits plugin for that)
• Create other plugins that can give quests to players (Hunt RPG is on its way)
• Create other plugins that uses the NPC to manage banks, quests, trades, shops
• Only limited by your imagination - possibilities are infinite!

Configuration

{

{
  "Chat": "<color=#FA58AC>{0}:</color> ",
  "Relocate to Zero at Wipe": true
}

3rd party Resources

HumanNPC Tutorial

TODO

• Area call for help
• Friends list not to atack
• Fix evasion
• Follow / attack timeouts

Not Implementing

• Add bullets animation => not sure I can :/ probably controlled client side
• Different radius for chat & hostile (not going to implement that, too many checks)
• Making this into BotSpawn, et al.