Bots are AI controlled characters in Paladins, they participate when a player disconnects from a match or in Training vs AI matches. Players below account level 5 will be automatically queued for these practice matches when attempting to join a casual match. Bots are identified by their generic names, default skins, and walking patterns.
- 1 AI Overview
- 2 Bugs and Oddities
- 3 Champions that are played by Bots in Training
- 4 Champions that are NOT played by Bots in Training
- 5 Bot Nicknames
- 6 Replacing a Disconnected Player with a Bot
- 7 Identifying if a Bot Took over a Player in a Match
- 8 Trivia
AI Overview[edit | edit source]
General[edit | edit source]
- Bots can be seen in Siege, Onslaught and Team Deathmatch training, their behaviours are unique in each gamemode. They also can be manually added in a Custom Match.
- Bots can also use the Voice Guided System, although they are limited to "Hi", "Good luck!", "Oops!", "Sorry!", "That's too bad!", "No problem!", "You rock!", and "Awesome!".
- Bots' champions can not level up, as they will always be level 0.
- Bots will start choosing champions when all the players already locked in.
- Bots will always fill the missing class; e.g. if there's no Frontline, a bot will pick a Frontline champion.
- They can not have custom Cosmetic Items, as they will always use the default skin.
- Bots can only use their default talent and loadout.
- Bots tend to hunt down players that are low on health.
- Bots will use their defense or movement abilities if they are below 50% health and the ability isn't on cooldown.
- Bots will get confused when players get the high ground. Due to lack of available paths, this will result in them standing still.
- Bots will always jump when standing still. This is a way to confirm that the bot isn't stuck.
- Bots may warp to a random available location when they get stuck in a place where they aren't supposed to be. This is more notable in Dragon Arena; if they manage to use the jump pad and land on the middle area.
- Support bots will use their healing abilities when they are low on health, or when two or more allies are low on health.
- Bots will prioritize you if you deal more than 1000 damage when they are cornered.
- Bots will attempt to retreat to their nearby allies (mainly supports and frontline allies) when on low health.
Siege[edit | edit source]
At the start of the match, bots will wander around in their base, some may fire their weapons, and some may use the VGS.
After the round starts, the bots follow a pattern towards the point.
When they capture the point, bots will follow the payload until they reach the objective.
Bots that are defending will stay near the payload until the next round.
Onslaught[edit | edit source]
Bots will stay on the objective until they reach 400 points.
Flank bots tend to stay near their enemies bases if all of their allies are on point.
In this gamemode, all bots, except Frontlines, tend to hunt down players more often than other gamemodes, this is most likely to earn points.
Team Deathmatch[edit | edit source]
Bots will wander around the map trying to find the enemy team. For some unknown reason (presumably a pathfinding error/bug), Jenos and Lian bots idle in their respective spawn locations until they encounter an invading enemy, consequently fixing it.
Example of Bots in Paladins[edit | edit source]
Bugs and Oddities[edit | edit source]
- Willo, Corvus and Drogoz bots may warp to random places when flying.
- Willo bots also tend to get stuck on walls with her Fae Flight, since she has no control with it.
- Bot Ash's Siege Shield has no cooldown. It isn't confirmed if it's intentional.
- Bot Jenos can use Through Time and Space while sliding. (This is patched)
- Bots may get stuck on their horses if they die from an Environmental Death with their horse.
- Bots also could use their ultimate while on their horse with this glitch.
- Terminus' bots can get infinite ultimates if they die while using their calamity blast.
- Bots can get stuck on certain paths, this is most likely the map's fault.
- When appearing outside of Training, Bomb King bots may often fail to detonate their bombs.
- Seris bots stand still when using her Shadow Travel.
- Inara bots don't have an animation when using her Seismic Crash.
- When using Exile, Atlas bots will only shoot once, they will always cancel their ultimate after they fire their first shot.
- Evie bots will jump and turn around when they are using Ice Block.
- Tyra bots will always throw their Fire Bomb first before firing their weapon after spotting an enemy.
- Sha Lin bots will keep toggling their Crippling Arrow on and off when in combat.
- Lian bots can regain 100% Ultimate Charge if they kill 2 enemies with Enlightment and use it instantly.
- One out of the 5 bots in Team Deathmatch will remain at the spawn point for an indeterminate amount of time.
- Vora bots can't incapacitate/execute targets with their Harbinger's Wrath unless they're extremely close to eachother, also the bot behaves like if they were using Vora's Deadly Scythe during their Ultimate.
- Yagorath bots are more likely to get stuck than the other bots.
- Bots can choose Grohk only if they are in your team in Training. It isn't known why Grohk bots can't be your enemy, unless if you're in a Custom Match.
- Ruckus bots have a propensity to shoot their weapon until they unload their entire ammo when they spot an enemy. They also have a slower reaction time than the other bots.
- Bots used to retreat when an enemy got extremely close to them, but after Version 0.68, this feature mysteriously disappeared, it's still unknown, whether it stopped working or was simply removed.
Champions that are played by Bots in Training[edit | edit source]
Androxus • Ash • Barik • Buck • Cassie • Evie • Fernando • Furia • Grohk • Grover • Inara • Jenos • Khan • Kinessa • Lian • Lex • Maeve • Makoa • Mal'Damba • Moji • Pip • Ruckus • Torvald • Tyra • Viktor • Vivian • Willo • Ying • Zhin
Champions that are NOT played by Bots in Training[edit | edit source]
Bot Nicknames[edit | edit source]
Replacing a Disconnected Player with a Bot[edit | edit source]
If a Human Player loses connection or quits a match, a Bot will take control of said player, this solution is an attempt to avoid 4v5s and overall unfairness.
Identifying if a Bot Took over a Player in a Match[edit | edit source]
No Cosmetic Titles[edit | edit source]
When a bot takes over a player, their title will disappear, an important tip is to pay close attention to your allies titles. (If they have one)
Suddenly Saying "Hi" or "Good luck!" with the VGS in the Middle of a Match[edit | edit source]
If they are in the spawn room, Bots will say "Hi", and if they are out of the spawn room, Bots will say "Good luck!".
Going Directly to the Capture/Control Point[edit | edit source]
Bots will always "rush" to the point, no matter the role. Pay attention to your suspicious teammate if they're going aimlessly towards the point.
Idling on the Capture Point[edit | edit source]
Bots stay on the point until they spot an enemy or until Victory.
The Player didn't Connect to the Match[edit | edit source]
On the Loading Screen, every Loading Frame has a "crystal" on the bottom indicating if the player successfully connected to the match. If the crystal is still not glowing after everyone in the Match is ready, they could've disconnected.
No Talent and Loadout Selected[edit | edit source]
If a player couldn't connect to the match, they will have no Loadout equipped until they reconnect.
Trivia[edit | edit source]
- Ogre is named after HirezOgre.
- Drybare is named after Drybear.
- Vangaurd may be a misspelled version of "Vanguard". It isn't confirmed if it's intentional or not.
- Bots get less ultimate percentage than human players. This can be confirmed during the beginning of a TDM match.
- If a bot managed to get Top Play, their respective champion wouldn't say their Top Play line.
- Bots don't leave their horse until they see an enemy.
- Bots that replace human players don't earn assists, this can be confirmed when viewing the Scoreboard.
- Their credits are also halved.
- Bots were named differently during Closed Beta and Open Beta.