• April 19, 2019, 10:21:34 AM

Author Topic: Train Rain Glitch  (Read 600 times)

Offline Bozz

  • Forum Visitor
  • Posts: 9
  • Don't drive me bananas
    • View backpack
    • View SteamRep
    • View Steam Profile
Train Rain Glitch
« on: December 26, 2016, 08:46:06 AM »
I was playing on trade/idle #4 and some guy brought Train Rain. I always have spawn protection on. When one of the trains hit me (while I had spawn protection), I went under the ground into the endless deeps. I kept on falling, endlessly, Until some guy brought Strange leveling, and the program saw me as idle, and started killing me. I told Reno about the issue, and he said he will take note of this situation.  :o :o :o
-Bozz


Offline tsund4y_ Ƹ̴Ӂ̴Ʒ

  • your local weaboo
  • Forum Poster
  • *
  • Posts: 124
  • ໒( ●ᴥ ●)ʋ u wot m8
    • View backpack
    • View SteamRep
    • View Steam Profile
Re: Train Rain Glitch
« Reply #1 on: December 26, 2016, 09:27:39 AM »
I did see this and idk what we should do as to whether or not we remove the spawn protection command or some how have the train rain not target users with this command on but on thing i do want to see if it does the same thing with an ubered medic (i assume it does) but we should look into this and try to prevent this from happening again.  :)
oh-haiyo~

Offline Hades

  • Retired Staff Member
  • Forum Master
  • *****
  • Posts: 1090
  • Will you be called to my realm next?
    • View backpack
    • View SteamRep
    • View Steam Profile
Re: Train Rain Glitch
« Reply #2 on: December 26, 2016, 11:08:45 AM »
In the meantime should it happen again, there is a console command that you can do. In console should the need arise that you need to have your character die you can simply type in "kill" without the quotes.

Hades

Offline ϟ ☠Lunarium☠

  • High Tier Trader
  • Staff Trainer
  • Forum Master
  • *****
  • Posts: 1220
  • Your Deadly skill is jogging? Mine is Murdering.
    • View backpack
    • View SteamRep
    • View Steam Profile
Re: Train Rain Glitch
« Reply #3 on: September 23, 2017, 04:17:27 PM »
Situation assumed to be resolved.

Topic Locked.