Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
  • Need help?

    Create a topic in the appropriate section
    Don't write everything in the chat!
  • Take a look at the marketplace

    There you can buy
    everything related to game servers
  • Don't want a ban?

    Please read our rules
    Don't disturb the order!
  • Sell or buy?

    Use services of the guarantor
    We will make your deal safe
  • 0
novrom

Skipping player

Появилась такая ошибка [Logout]: Skipping player  Багемия ИД, already removed

Кула копать подскажите знатоки.

Share this post


Link to post
Share on other sites

7 answers to this question

Recommended Posts








  • 0

SCRIPT       : [Logout]: Skipping player TMPsA2jeoCZUgUCqaqoIo0bn1MTmfaw5cQNkTcIt7KY=, already removed

 

Who can help me

Пожалуйста, Войдите или Зарегистрируйтесь, чтобы увидеть это: Вложение.

Пожалуйста, Войдите или Зарегистрируйтесь, чтобы увидеть это: Вложение.

Пожалуйста, Войдите или Зарегистрируйтесь, чтобы увидеть это: Вложение.

Пожалуйста, Войдите или Зарегистрируйтесь, чтобы увидеть это: Вложение.

Share this post


Link to post
Share on other sites
  • 0

To solve this problem, delete the problematic modification or script. These are the consequences of the work of one of the modification scripts

 

Для решения данной проблемы удалите проблемную модификацию или скрипт. Это последствия работы одного из скриптов-модификаций

Edited by 123new (see edit history)

Share this post


Link to post
Share on other sites
  • 0

I found the official C document, but I can't understand it. I don't know what caused it

Пожалуйста, Войдите или Зарегистрируйтесь, чтобы увидеть это: Вложение.

Пожалуйста, Войдите или Зарегистрируйтесь, чтобы увидеть это: Вложение.

Share this post


Link to post
Share on other sites
  • 0
18 минут назад, yy40097 сказал:

I found the official C document, but I can't understand it. I don't know what caused it

Пожалуйста, Войдите или Зарегистрируйтесь, чтобы увидеть это: Вложение.

Пожалуйста, Войдите или Зарегистрируйтесь, чтобы увидеть это: Вложение.

I repeat what I said earlier. What you see in the screenshots

it is a consequence of the fact that some script or modification has performed some specific action that is not provided for by the original version of the game and its authors. For example, removing a player's corpse immediately after his death. As a result of a combination of certain circumstances, such as the absence of a deceased player's corpse or the last body used by him, when the player exits the server, a verification event occurs, which you noted in the screenshot in your post

And since the player does not have an active body, the game server resets the disconnect event of the player. But for reasons unknown to us, this event is trying to happen again, although it should not happen again (perhaps this is the code used directly by the engine of the game itself, which we cannot look into or change anything). Alas, we cannot change this, and this is only a consequence of a certain combination of circumstances that led to this using any script or modification you added to the game. By default, in a standard clean game without modifications and scripts, such a problem does not occur. Such an error is a consequence of a certain combination of gaming circumstances associated with the use of any modification or script. You can view the code of the game files, but you will not find the cause of the problem there.

Disable modifications and scripts from your server, add one at a time and check. Most likely it's something related to cleaning up corpses immediately after the player's death. But there may be other reasons that I have not met before.

Edited by 123new (see edit history)

Share this post


Link to post
Share on other sites
  • 0
23.05.2022 в 11:15, 123new сказал:

I repeat what I said earlier. What you see in the screenshots

it is a consequence of the fact that some script or modification has performed some specific action that is not provided for by the original version of the game and its authors. For example, removing a player's corpse immediately after his death. As a result of a combination of certain circumstances, such as the absence of a deceased player's corpse or the last body used by him, when the player exits the server, a verification event occurs, which you noted in the screenshot in your post

And since the player does not have an active body, the game server resets the disconnect event of the player. But for reasons unknown to us, this event is trying to happen again, although it should not happen again (perhaps this is the code used directly by the engine of the game itself, which we cannot look into or change anything). Alas, we cannot change this, and this is only a consequence of a certain combination of circumstances that led to this using any script or modification you added to the game. By default, in a standard clean game without modifications and scripts, such a problem does not occur. Such an error is a consequence of a certain combination of gaming circumstances associated with the use of any modification or script. You can view the code of the game files, but you will not find the cause of the problem there.

Disable modifications and scripts from your server, add one at a time and check. Most likely it's something related to cleaning up corpses immediately after the player's death. But there may be other reasons that I have not met before.

Возможно так и есть. Скрипт удаляющий тело после смерти возможно виноват. Буду проверять.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...

Important Information

By using this site, you automaticly agree to our Guidelines and Privacy Policy.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.