Jump to content


Photo
Warned

White Rice [STEAM_0:0:48603003]



  • This topic is locked This topic is locked
6 replies to this topic

#1 Ќɨjąj๏µţ€h

Ќɨjąj๏µţ€h

    Member

  • Users
  • PipPip
  • 17 posts

Posted 01 August 2014 - 12:09 AM

White Rice kicked everyone from a lobby that we waited like 30 minutes for it to start. He has also done this on multiple occasions. 

Stem Profile: http://steamcommunit...id/whitericetf/



#2 Magnivore

Magnivore

    Newbie

  • Users
  • Pip
  • 1 posts

Posted 01 August 2014 - 12:10 AM

This in fact did happen. I have the boot print on my hind-quarters to prove it.



#3 The Once and Future King

The Once and Future King

    Advanced Member

  • Members
  • PipPipPip
  • 443 posts
  • LocationWisconsin

Posted 01 August 2014 - 12:11 AM

Here is his steam ID: 0:0:48603003

Lobby#: 174607

 

He started a different lobby immediatly after (I assume we were kicked by him doing that and checking the kick players box on lobby creation.)  Claimed in that lobby's chat that lobby's chat that the server had to update even though there was no update today and immediately after us being kicked his new lobby was up which means that even if there was the server would not have had time to update.

 

The lobby had not even started yet so there are no logs or Demo's for this.


Edited by The Once and Future King, 01 August 2014 - 12:12 AM.


#4 Junktron

Junktron

    Newbie

  • Users
  • Pip
  • 1 posts

Posted 01 August 2014 - 12:18 AM

Yep White Rice Kicked everyone from the lobby and said he had to update the server even though there wasn't an update for TF2.



#5 TheS4rr

TheS4rr

    Member

  • Members
  • PipPip
  • 28 posts
  • LocationVirginia

Posted 01 August 2014 - 12:25 AM

The server white list had to be updated, so it auto restarted and when the server restarts it resets the password to what's set in the client and it kicked everyone. 


  • White Rice likes this

#6 White Rice

White Rice

    Member

  • Members
  • PipPip
  • 18 posts
  • LocationRaleigh, NC

Posted 01 August 2014 - 12:28 AM

Yes the server had a whitelist update, and in order for the white list to take effect the server has an auto restart which resets the password and kicksall. unfortunently it happend right as the lobby started which sucks but what ever happend happend. sorry you guys didnt get to play a lobby, you must be devestated


  • TheS4rr and White Rice like this

#7 Luop90

Luop90

    >implying I have a title

  • +Admins
  • PipPipPipPipPip
  • 1919 posts
  • Location127.0.0.1

Steam Profile

Posted 01 August 2014 - 12:34 AM

Liking your own post... hm.

 

Is there a reason, WhiteRice, that you have an auto-update on the whitelist? Even if it was an accidental kick, you are still responsible for what happened.

 

I talked with him. He has agreed to disable the whitelist updater during lobbies from here on out, to prevent this from happening again. However, if this does happen again, under any circumstances, it will be met with a login ban.

 

WARNED.


Why do mathematicians confuse Halloween and Christmas? Because 31 Oct = 25 Dec!





Also tagged with one or more of these keywords: Warned