Well ive had ti with neocron

[johngreen2000]

I was so excited about comming back, was having fun until 3 dasy ago.

First sync bugged my rhino into a zone with 15 anarchy breed and the rhino gets blown up. I run missions on my psi to get my next symp form 10 to 90 for fsm. make 300k to pay to switch to next, make another 230k for buying parts for my new rhino, lom so i can drive my new rhino, make the rhino, and then bamb rollback. Rollback to just after my rhino blew up but before I made the 700-800k and spent 5 hours running missions.

So I decide ill do it again. Spent almost an entire day running missions, making 700+k and lommed back out. Had to go to work so I didnt even get to drive my rhino. I come home sync for almost an hour, finally get in the game go to MB and start killing warbots, i forgot to grab my hack tool so I park the rhino behind mb run in and get killed by 4 monks camping the zone line. After 2 hours of trign to get back out, i find my rhino got blown up by the above said 4 monks. Pissed off I go back to nc and make 200k for buying more parts to make my third rhino, now that I didnt even get to use my second one. Get 220k buy the parts hand them to my 150ish constructor, build rhino, he fails and 5 piece get destroyed.

I log on my psi and get sniped by some anti city abusing guard line of sight and cannot find a poker for 4 hours.

so in 3 days ive manage to not level at all, lose everything ive worked for,for 3 days, still cant sync in on several character, [ edited ]
Im outta here
Thanks to unreal for the help you gave me on the forums and for being the one perosn who poked me after 4 hours of searching.

[flawl3ss]

[ edited ]

[Mr Kot]

Ouch.

The first problem you mentioned was just sheer bad luck. We were all affected in one way or another by the rollback - the first complete one since first month of retail, btw - so put this one down to being in the wrong place at the wrong time.

The rest of your gripes seem to be aimed at the community. Noticing your start date - December 2002, do i assume that you were a Pluto player? If so, you will have got a shock to discover you shouldn't leave a rhino unattended outside MB or venture outside a safezone without your LE. Welcome to Terra.

Since when do 5 pieces get destoyed on a build? It should only be the datacube at worst. Did you say it was your own char who did the cst? If not, you were scammed.

4 hours for a poke? Did you try TechHaven? There aren't many tradeskillers in Plaza these days if that's where you were waiting.

Sounds like you've been truly unlucky this last 3 days.. usually a sign to take a break and come back in a week to make a fresh start. Tbh, it sounds like the game bugs have only been responsible for a couple of syncs. I get those rarely, but those who get them more than they should should check out their connection. Type TRACERT 62.140.29.50 into your command.com to see if anything shows up there. Chances are its either your ISP or some router on the way to KK servers that could be causing the synching / lagging. I get good days and bad days. The bad days, i just log off until the next day when my ISP usually posts an apology on its website for the "problems some customers may have been having".

Shit happens.

[johngreen2000]

The first problem you mentioned was just sheer bad luck. We were all affected in one way or another by the rollback - the first complete one since first month of retail, btw - so put this one down to being in the wrong place at the wrong time.

The rest of your gripes seem to be aimed at the community. Noticing your start date - December 2002, do i assume that you were a Pluto player? If so, you will have got a shock to discover you shouldn't leave a rhino unattended outside MB or venture outside a safezone without your LE. Welcome to Terra.

-Na i wasnt shocked, but first, i hide the vehicle in the hopes it wouldnt be found, and from what i remember if the owner dies, and stays out of the zone the vehicle will go down to 1% and not blow up..or so i thought. I genreped into mb and stayed there for along time and it still got blown up, either by a bug or my misunderstanding of how the system works.

Since when do 5 pieces get destoyed on a build? It should only be the datacube at worst. Did you say it was your own char who did the cst? If not, you were scammed.

-Yes I have 2 account and I gave the stuff to my cster and 5 parts broke, when I saw that, I immediate wanted to quit.

4 hours for a poke? Did you try TechHaven? There aren't many tradeskillers in Plaza these days if that's where you were waiting.

- Dont have TH I was in NC and to be more specific I wasnt on 4 hours straight, I logged on asked if anyone was poking, waited 10 minute, got on another character for 20-30 minute come back ask if anyones poking, no one is so i log on another character, wait 30 minute came back. Took 4 hours before I found anyone.

Sounds like you've been truly unlucky this last 3 days.. usually a sign to take a break and come back in a week to make a fresh start. Tbh, it sounds like the game bugs have only been responsible for a couple of syncs. I get those rarely, but those who get them more than they should should check out their connection. Type TRACERT 62.140.29.50 into your command.com to see if anything shows up there. Chances are its either your ISP or some router on the way to KK servers that could be causing the synching / lagging. I get good days and bad days. The bad days, i just log off until the next day when my ISP usually posts an apology on its website for the "problems some customers may have been having".

-Ive gone through 3 or so providers since beta, and every time ive come back the synce are no better. Granted Ive never gone through trace route, and that stuff but considering the amount of people complaining about the sync problems I dont think its our side, I think its there side.


heres the traceroute

Tracing route to 62.140.29.50 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 2 ms 2 ms 2 ms 10.33.34.9
3 2 ms 2 ms 2 ms P4-0.LCR-02.DLLSTX.verizon-gni.net [130.81.48.13
4]
4 3 ms 3 ms 3 ms so-7-0-0-0.PEER-RTR1.DFW80.verizon-gni.net [130.
81.17.175]
5 3 ms 3 ms 3 ms so-5-1-0-0.gar2.Dallas1.Level3.net [4.78.234.1]

6 3 ms 3 ms 3 ms ae-1-54.bbr2.Dallas1.Level3.net [4.68.122.97]
7 127 ms 127 ms 127 ms ae-1-0.bbr2.Dusseldorf1.Level3.net [212.187.128.
21]
8 133 ms 132 ms 132 ms so-3-0-0.mp1.Hamburg1.Level3.net [4.68.128.34]
9 132 ms 132 ms 133 ms ge-4-1.hsa2.Hamburg1.Level3.net [195.122.140.164
]
10 133 ms 132 ms 133 ms ge-2-0.edge1.ham1.de.inetbone.net [62.67.234.30]

11 134 ms 133 ms 133 ms 212.162.3.84
12 133 ms 133 ms 133 ms 62.140.29.50

Trace complete.

[johngreen2000]

and my ping results

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>ping 62.140.29.50

Pinging 62.140.29.50 with 32 bytes of data:

Reply from 62.140.29.50: bytes=32 time=133ms TTL=116
Reply from 62.140.29.50: bytes=32 time=133ms TTL=116
Reply from 62.140.29.50: bytes=32 time=133ms TTL=116
Reply from 62.140.29.50: bytes=32 time=133ms TTL=116

Ping statistics for 62.140.29.50:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 133ms, Maximum = 133ms, Average = 133ms

C:\Documents and Settings\Owner>ping 62.140.29.50

Pinging 62.140.29.50 with 32 bytes of data:

Reply from 62.140.29.50: bytes=32 time=133ms TTL=116
Reply from 62.140.29.50: bytes=32 time=133ms TTL=116
Reply from 62.140.29.50: bytes=32 time=133ms TTL=116
Reply from 62.140.29.50: bytes=32 time=133ms TTL=116

Ping statistics for 62.140.29.50:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 133ms, Maximum = 133ms, Average = 133ms

C:\Documents and Settings\Owner>ping 62.140.29.50

Pinging 62.140.29.50 with 32 bytes of data:

Reply from 62.140.29.50: bytes=32 time=133ms TTL=116
Reply from 62.140.29.50: bytes=32 time=133ms TTL=116
Reply from 62.140.29.50: bytes=32 time=133ms TTL=116
Reply from 62.140.29.50: bytes=32 time=133ms TTL=116

Ping statistics for 62.140.29.50:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 133ms, Maximum = 133ms, Average = 133ms

[Lodar]

Leaving Thread, closed.