1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Hey Guest, is it this your first time on the forums?

    Visit the Beginner's Box

    Introduce yourself, read some of the ins and outs of the community, access to useful links and information.

    Dismiss Notice

Windows [1865] Killing Traders Cause Crash

Discussion in 'Archive' started by Olimarrex, Jul 30, 2016.

Thread Status:
Not open for further replies.
  1. Olimarrex

    Olimarrex Ballista Bolt Thrower Official Server Admin

    Messages:
    177
    Category: KAG server

    Operating system: Windows 10 x64 bit-operating system

    Build number: 1865

    Description: By sawing a granny (!trader) to death, every player is frozen

    Steps to reproduce:
    1. Go to single player sandbox
    2. Spawn a !saw
    3. Go above the saw and spawn a !trader
    EDIT:
    the screenshot didn't take properly. Though I don't think it'd be much use..
     

    Attached Files:

  2. don't kill traders then

    ps: that's a terrible wallpaper
     
    asger75 likes this.
  3. Olimarrex

    Olimarrex Ballista Bolt Thrower Official Server Admin

    Messages:
    177
    Ikr, I'd changed it aeons ago. But that's the worst excuse... If I said "kag crashes when I launch it" you wouldn't say "don't launch it then" would you... I can understand that killing traders isn't a necessity like launching kag, but it's still an opportunity for griefers, ragers, and anyone else who WANTS to crash a server.
     
    Biurza likes this.
  4. traders are unused in current build, they were replaced by trading posts a while ago. if a modded server wants traders they can fix it themselves
     
  5. Vamist

    Vamist THD Team THD Team Tester

    Messages:
    544
    In sandbox mods, that's how people crash servers.

    People that host normal non-modded servers are screwed.

    EDIT; Like so, Joined a normal sandbox, trader+saw =

    [​IMG]

    Kazaco: See Norill's reply above
     
    Last edited: Oct 21, 2016
  6. fine, fixed
     
Thread Status:
Not open for further replies.