156 2013-04-01 07:25:00 +0200 Player kicked to login screen when using a house door 2013-04-02 16:39:33 +0200 1 1 1 Unclassified Salem Server unspecified PC Windows CONFIRMED --- major --- 1 ldleithoff fredrik deadman555 490 ldleithoff 2013-04-01 07:25:55 +0200 Sample thread: http://forum.salemthegame.com/viewtopic.php?f=10&t=5599 Player attempts to exit or enter a house and gets kicked to log in and unable to reenter the game on the same character. The character is effectively stuck in that place. Workaround: If another character occupies the position when the stuck character is logged in, the stuck character is sent back home (via "blocked position" mechanic"). Reproducability: Seems some buildings are consistently doing this while others aren't. I have seen a couple of threads on this, but nothing concrete. 493 fredrik 2013-04-01 07:34:00 +0200 I'm fairly sure this is caused by the same underlying problem that causes #139. Not marking as duplicate since I'm not entirely sure, but I'd be surprised otherwise. 501 deadman555 2013-04-02 09:36:16 +0200 The funny thing about this is: #139's creator is located in Germany, like I am, too. It happens for all of my german friends, but not for any other ones I know in the game... That's strange 502 deadman555 2013-04-02 09:57:53 +0200 http://imageshack.us/photo/my-images/14/kchfzrqksudmaqydkaygjr.mp4/ This is exactly what happens. Thank you for your time 504 deadman555 2013-04-02 12:42:48 +0200 I just used an american proxy and another german proxy VPN. Both worked fine. Exiting the proxy caused the error again. Reconnected to the VPN Proxy and.. it worked again!... Exited the proxy and it failed again. Reconnected: Works! Now I'm going to use the proxy to play. lol Could you tell me how to fix that problem? We still don't know if it's client- or serverside though. 505 deadman555 2013-04-02 14:44:02 +0200 I'm able to teleport to boston and back, go into houses or mines... Everything workes fine, if i use the proxy vpn. 506 fredrik 2013-04-02 16:39:33 +0200 (In reply to comment #4) > We still don't know if it's client- or serverside though. I'm fairly sure it's neither, but rather caused by problems on the Internet route between the client and the server. That said, however, it may be possible to change the protocol to work around whatever bugs the route has.