1

(9 replies, posted in Bugs)

C:\Users\CJ>tracert game-live.perpetuum-online.com

Tracing route to game-live.perpetuum-online.com [195.228.152.156]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  routerlogin.net
  2     8 ms     7 ms     8 ms  cpc65578-sgyl33-2-0-gw.18-2.cable.virginm.net
  3    13 ms     6 ms     9 ms  sgyl-geam-1b-ge329.network.virginmedia.net [81.97.50.173]
  4     9 ms    10 ms     9 ms  sgyl-core-2b-ae2-0.network.virginmedia.net [195.182.178.94]
  5    12 ms    22 ms    13 ms  leed-bb-1b-ae5-0.network.virginmedia.net [81.97.48.81]
  6    18 ms    19 ms    21 ms  leed-bb-2a-ae2-0.network.virginmedia.net [62.254.42.121]
  7    21 ms    14 ms    12 ms  leed-bb-1c-ae0-0.network.virginmedia.net [62.254.42.126]
  8    21 ms    19 ms    19 ms  62.252.224.238
  9    21 ms    23 ms    23 ms  ae13-xcr1.lnd.cw.net [195.2.10.241]
10    23 ms    23 ms    23 ms  ae15-xcr1.lns.cw.net [195.2.30.114]
11    30 ms    23 ms    23 ms  ldn-b5-link.telia.net [213.248.100.25]
12    26 ms    52 ms    21 ms  ldn-bb2-link.telia.net [80.91.249.181]
13    97 ms    33 ms    60 ms  hbg-bb2-link.telia.net [80.91.247.168]
14    53 ms    51 ms    51 ms  win-bb2-link.telia.net [80.91.246.25]
15    61 ms    61 ms    58 ms  bpt-b4-link.telia.net [80.91.250.65]
16   150 ms   147 ms   147 ms  magyar-ic-151712-bpt-b4.c.telia.net [213.155.129.6]
17    94 ms   164 ms   142 ms  xe-10-1-0.ic0-ip3.net.telekom.hu [81.183.0.96]
18   142 ms    97 ms   142 ms  xe-11-3-2.ic1-dplex.net.telekom.hu [81.183.0.35]
19     *        *      242 ms  81.183.2.210
20   189 ms   244 ms   188 ms  195.228.152.156

Trace complete.

2

(9 replies, posted in Bugs)

Issue is back today sad

ping -t game-live.perpetuum-online.com

Pinging game-live.perpetuum-online.com [195.228.152.156] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 195.228.152.156: bytes=32 time=242ms TTL=114
Reply from 195.228.152.156: bytes=32 time=249ms TTL=114
Reply from 195.228.152.156: bytes=32 time=238ms TTL=114
Reply from 195.228.152.156: bytes=32 time=188ms TTL=114
Request timed out.
Reply from 195.228.152.156: bytes=32 time=240ms TTL=114
Request timed out.
Request timed out.
Reply from 195.228.152.156: bytes=32 time=190ms TTL=114
Reply from 195.228.152.156: bytes=32 time=240ms TTL=114
Request timed out.
Reply from 195.228.152.156: bytes=32 time=191ms TTL=114
Reply from 195.228.152.156: bytes=32 time=236ms TTL=114
Request timed out.
Request timed out.
Request timed out.
Reply from 195.228.152.156: bytes=32 time=240ms TTL=114
Reply from 195.228.152.156: bytes=32 time=188ms TTL=114
Request timed out.
Reply from 195.228.152.156: bytes=32 time=189ms TTL=114
Reply from 195.228.152.156: bytes=32 time=245ms TTL=114
Request timed out.
Request timed out.
Reply from 195.228.152.156: bytes=32 time=235ms TTL=114


Hmm seems like lots of packets not getting there:

Ping statistics for 195.228.152.156:
    Packets: Sent = 77, Received = 45, Lost = 32 (41% loss),
Approximate round trip times in milli-seconds:
    Minimum = 188ms, Maximum = 262ms, Average = 219ms

3

(8 replies, posted in Open discussion)

Just some words
on the Internet.
Go kill stuff!

I find I agree with Crepitus on his points about the actual multiboxing.

The 'issue' I think you are trying to solve, is one group turning up with twice as many bots as another, even though the same number of flesh-things are behind the controls. That is a problem of bot numbers and has nothing to do with the numbers of humans involved.

The number of different fits you can make by using a support bot for extra utility and options brings a lot of gameplay and complexity and I don't see why you would want to remove it, other than as a crutch to help balance the game for low population combat, something it is plainly not geared towards.