Jump to content

Recommended Posts

Posted

I received a ban today for the dispatcher mode, which lasts until Sunday evening. Apparently, I was either AFK or trolling or blocking tracks on DE1 at the Lazy LC station on Tuesday. I can't remember doing anything like that.

The only situation I can remember right now is that at a certain point, no more trains could be sent to and from Przemiarki. The AI there either crashed or had other problems. This led to a train jam at the station there. The AI was supposed to send several trains to Lazy LC, but it didn't.

Is there any historical data available that might help me better understand this ban?

 

image.thumb.png.0b871bbda7a69a1d19e7b6865c403eb2.png

Posted

 

22 hours ago, elyday said:

I received a ban today for the dispatcher mode, which lasts until Sunday evening. Apparently, I was either AFK or trolling or blocking tracks on DE1 at the Lazy LC station on Tuesday. I can't remember doing anything like that.

The only situation I can remember right now is that at a certain point, no more trains could be sent to and from Przemiarki. The AI there either crashed or had other problems. This led to a train jam at the station there. The AI was supposed to send several trains to Lazy LC, but it didn't.

Is there any historical data available that might help me better understand this ban?

image.thumb.png.0b871bbda7a69a1d19e7b6865c403eb2.png

 

Hello, for historical information and what happened at your station, you can check it out via the Simrail.pl community project.
https://simrail.pl/players/logsm

More specific details about the ban must be provided by the moderator who banned you.

 

Posted (edited)

 

Hi Elyday,

there have been multiple reports that the dispatcher at Lazy LC was AFK. After reviewing the available logs from those incidents, we found that a few trains were stuck at LC and were not dispatched as they should have been.

Between 19:17 and 19:35, there was only one single button press logged. No other operational inputs were recorded during that time. In addition, there was no communication via text chat during this period, despite multiple trains being affected.

The dispatcher left the station and rejoined, but no corrective action was taken afterward. Unfortunately, some of the public protocols are no longer available.

AFK behavior while on duty, causing operational disruption, combined with a complete lack of communication, constitutes disruptive conduct. For these reasons, the ban is justified.

 

 

Edited by CookieMonster
  • Like 1
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

Terms of Use Privacy Policy