PDA

View Full Version : Evo 2.1 - The same old bugs?


Xio
08-12-05, 16:01
hey everyone,
i had played NC1 pretty hardcore a long time ago (like many), started in beta and loved the game.

last night i experienced one of those infamous neocron nights.... where one bugs leads onto another bug which inevitably leaves the players screwed and annoyed - and not wanting to play.

my circumstances started with a CTD whilst trying to zone into a dungeon, which led to spawn in the middle of the zone me dying to all the mobs around - losing an item i had no way to recover.
this in turn led to my inventory becoming bugged.
which led me to sell a Mislabeled item, to the vendor.

i spoke to a GM. and as always, they acknowledge the bug is there, but are unable to help. even told of their friends having lost high-end items under the same circumstance!

needless to say, several YEARS ago, this is the kind of thing i used to encounter. i clearly remember this bug, but after such a long time i thought it might have been fixed 0.0

the YEARS old memory leaks are there, the game is still bug ridden to the point of frustration.

i love the game concept, i always have, but why-o-why, do KK persist with such poor programming? and continue to release engine updates when the old game-ending bugs (imo), which have not been fixed after YEARS of development are so blatantly obvious?

can someone tell me why they would EVER want to pay for a game like this?
will these things ever get fixed? and most of all does KK care?

an old frustrated NC fan.... who hoped for at least *some* improvement in the quality of the game.
xio :(

fbishop
08-12-05, 16:13
Man, thats sad to hear. I was thinking about coming back as well, but now... :(

Zefrian
08-12-05, 17:41
i am playing for now round about 3 years. You mentioned the bug with the Items-with-wrong-Icon-after-Genrep-by-death. This bug is still there, thats true. It can be easily identified by trying to wear your Armor and implants again. If you get an message like "You cant use this item" or similar, then there it is. This bug happens by coincidence, and therefore it's very difficult to debug. Simply relogg. This costs only 20 seconds.

The memory leak problem has been improved. That's my personal opinion.