GOKZ replay bots get pulled down as if there is always an antibhop trigger under it

[zealain]

Original report by zer0.k (Bitbucket: zer0k_z, ).

---

Sometimes using !replay, the bot will get pulled down before every jump (except bhops) and sounds like they got pulled down by an antibhop trigger. This will get fixed by reloading the map or the server.

‌

[zealain]

Original comment by zer0.k (Bitbucket: zer0k_z, ).

---

This happens when replay folder content does not match the databases, it’s commonly found in servers with shared databases.

Assuming the server has no replay file but has times in the database, you can reproduce this as follows:

1. Join the server, notice that there is only one or no bot in the server
2. Get the server record to create a replay file.
3. Try to play the replay, either you won’t be able to play it because there is no bot, or the bot will get kicked immediately (if you get 2 records and there are two bots instead of 1) or this happens: https://streamable.com/f2wzxo

This is easily possible in servers that use a shared database. Assuming there is no run on a map:

1. Get server record on that map on server 1
2. Join server 2, change to that map and get a record there
3. Try to play the replay, you will get the same result.

You sometimes cannot open the replay control either.

As far as I know, this can be fixed by reloading the plugin after creating a replay file.

[zealain]

Original comment by zer0.k (Bitbucket: zer0k_z, ).

---

This happens when there are two bots and you try to play a replay.

[zealain]

Maybe fixed with the new replays in 3.0.0?