ESP DOCS

Misc options:
ESP.TeamColor = true/false - whether to use team color
ESP.Players = true/false - show/hide players
ESP.FaceCamera = true/false - whether the boxes should face the direction the player is looking or always face your camera
ESP.AutoRemove = true/false - whether the boxes should be removed when the object is parented to nil (defaults to true)

Overrides:
The ESP supports overriding certain functions, specifically for games with custom teams/characters system. Overriding them works by doing ESP.Overrides.FunctionName = customFunc
For example Bad Business has custom characters which don't use plr.Character, so normally the ESP wouldn't work, however you can easily fix it by doing something like this:
https://pastebin.com/123tGvtL


Result: https://i.vgy.me/9w30QT.png

Full list of overrides and their explanation below:
GetTeam(player) - should return the team object the player is on (can return a table or some other identifier, since it's only used for determining team mates)

IsTeamMate(player) - should return true if "player" is a team mate of the local player

GetColor(object) - only used for objects which don't have Color or ColorDynamic specified, should return a Color3 (or nil, in which case it uses ESP.Color)

GetPlrFromChar(char) - should return the player whose character is char

UpdateAllow(box) - return false if the box should be hidden, otherwise return true, usually used to hide players in lobby areas



Custom Objects
The ESP has a built-in support for easily implementing custom objects, such as chests or cars or whatever by using ESP:AddObjectListener(parent, options)
It will connect ChildAdded/DescendantAdded (depending on options) to the parent, and match the added instances for specified options, and if a match is found, add them to the ESP.
It also works retroactively, meaning it will add instances which were created before the script was ran.


Example 1, Murder Mystery 2 dropped gun ESP:
https://pastebin.com/Bag2VQty


Example 2, R2DA Zombies ESP:
https://pastebin.com/xRDri4HN


Full list of options and their explanation below:
Recursive - true/false, whether to use DescendantAdded instead of ChildAdded or not

Type - the expected ClassName/base class of the object, ex. Model, Part, BasePart, etc.

Name - the expected Name of the object

Validator(obj) - function, should return true if the object should be added to the ESP

PrimaryPart - the name of the part under the object that the ESP should treat as the primary part, can also be a function which should return the part

Color - either a Color3 or a function which returns a Color3 (will only be called once)

ColorDynamic - explained earlier

Name - a string or a function which returns one

IsEnabled - explained earlier

RenderInNil - explained earlier

OnAdded(box) - function, will get called after an object has been added to the ESP by the listener

They are all optional, but you should at least specify Type or Name



Integrating custom drawing objects with the ESP
If you have something like a FOV circle which uses the drawing api and you don't want to make a separate RenderStepped loop just to update it, you can integrate it with the ESP's update loop. It will get updated even if the ESP is toggled off. All you have to do is make a table with an Update function, and then insert it into ESP.Objects table

FOV circle example:
https://pastebin.com/d116Gihq

The reason it's going to update it even if ESP is toggled off is because in the RenderStepped loop it uses "pairs" when ESP is enabled, and "ipairs" when it's disabled. In other words, it only loops through the numerical indexes when ESP is disabled, and regular objects use dictionary keys, so it will only iterate values inserted with table.insert or such raysCool


You're free to use/modify it however you want, just don't claim it as your own. Credits would be cool but you don't have to.
Enjoy!

By - Klrlot22