After their hard work at NCsoft, and two full weeks after C4's release, they have changed the text on 3 NPCs in gludin. Thank you and enjoy your play in L2.
the extremly ineffective gameguard program was also updated, with what we will never know. i reckon it's some extremly dubious update, as not only did they not mention it on the mainpage, but totally neglected to announce the weekly downtime like they usually do.
Perhaps after enough of us whining, they will release some late patch notes that plactate the less informed player base, and delete posts like mine like they always do.
I can happily report that I was able to buy Dice from the NPC in Fioran, and that dice work as intended, I even bought one of each and they roll happily :)
I tought I'd never be able to experience rolling dice since I just activated my account and kind of missed 3 chronicles in a row :O
According to another thread, Mistryl says that the PTS is back up and they are attempting a fix on it.
according to common sense, the spoil fix required 5 key strokes to fix one line of text and does not require 2 weeks of preparation for another week of testing on the public test server.
The question still remains, where are our patch notes?
according to common sense, the spoil fix required 5 key strokes to fix one line of text and does not require 2 weeks of preparation for another week of testing on the public test server.
This, folks, is what we in the business call "talking out of one's ***". Let's give him a big hand!
I can happily report that I was able to buy Dice from the NPC in Fioran, and that dice work as intended, I even bought one of each and they roll happily :)
:eek: They were supposed to be reactivated but still not purchasable. Don't let them know it's still bugged! *laugh*
according to common sense, the spoil fix required 5 key strokes to fix one line of text and does not require 2 weeks of preparation for another week of testing on the public test server.
Yep. They just find the line that says "Spoil = bugged", highlight it, and type "works" over it. Tada, five keystrokes!
:)
Did you see the last thread that talked about this? Crash bugs are nasty to trace and fix.
according to common sense, the spoil fix required 5 key strokes to fix one line of text and does not require 2 weeks of preparation for another week of testing on the public test server.
Yep. They just find the line that says "Spoil = bugged", highlight it, and type "works" over it. Tada, five keystrokes!
:)
Did you see the last thread that talked about this? Crash bugs are nasty to trace and fix.
On another board the 'error' has been worked out more then 1 week ago and everything that needs to be fixed is a typing error in a single line. So infact it would be as easy has finding a highlighted line (the internal id has been posted and pointed out) and changing something amazing big like 5 characters. This is not the first time that the client crashes due to some easy typing mistake.
enjoy the pm's i sent both of you.
Some of us actually do know what we are talking about.
I can't post it here on the public part of the boards, because it would force me to explain about abunch of tos breaking things like decrypting the client which is a big no no.
Before you hit the report button out of spite, remember, all i sent you was an image i innocently found and decided to share with my favorite board warriors ^.^
enjoy the pm's i sent both of you.
Some of us actually do know what we are talking about.
I can't post it here on the public part of the boards, because it would force me to explain about abunch of tos breaking things like decrypting the client which is a big no no.
Before you hit the report button out of spite, remember, all i sent you was an image i innocently found and decided to share with my favorite board warriors ^.^
I assume that you can guarentee that this **** doesn't break anything else? If so, I stand corrected. However, I will also assume that NCSoft is testing this fix for a reason (i.e, it's just not that simple).
I assume that you can guarentee that this **** doesn't break anything else? If so, I stand corrected. However, I will also assume that NCSoft is testing this fix for a reason (i.e, it's just not that simple).
I assume that you can guarentee that this **** doesn't break anything else? If so, I stand corrected. However, I will also assume that NCSoft is testing this fix for a reason (i.e, it's just not that simple).
That should be enough to add 1 and 1 together in this case of bug. If you still deny that, i can only call that blind faith into NCSoft. I think the best 'past' example given for that sort of NCSoft problem was, that they rather made a login announcement then fixing the wrong description of BSOE:Clanhall.
That should be enough to add 1 and 1 together in this case of bug. If you still deny that, i can only call that blind faith into NCSoft. I think the best 'past' example given for that sort of NCSoft problem was, that they rather made a login announcement then fixing the wrong description of BSOE:Clanhall.
I have absolutely no idea what you are trying to say to me here. I read this like 4 or 5 times and I still have no clue.
That should be enough to add 1 and 1 together in this case of bug. If you still deny that, i can only call that blind faith into NCSoft. I think the best 'past' example given for that sort of NCSoft problem was, that they rather made a login announcement then fixing the wrong description of BSOE:Clanhall.
I have absolutely no idea what you are trying to say to me here. I read this like 4 or 5 times and I still have no clue.
I assume you read the thread on blah, which explains in detail what the problem is?
That should be enough to add 1 and 1 together in this case of bug. If you still deny that, i can only call that blind faith into NCSoft. I think the best 'past' example given for that sort of NCSoft problem was, that they rather made a login announcement then fixing the wrong description of BSOE:Clanhall.
I have absolutely no idea what you are trying to say to me here. I read this like 4 or 5 times and I still have no clue.
I assume you read the thread on blah, which explains in detail what the problem is?
No, I've tried to read that site but it's too juvenile.
He sent an image. I have no idea where it was from. I wouldn't have gone to that site anyway.
So basicly you don't want to know it and blame others randomly of 'talking out of their [censored]'. Its not like you'll ever find informations released about that sort of stuff around here.
He sent an image. I have no idea where it was from. I wouldn't have gone to that site anyway.
So basicly you don't want to know it and blame others randomly of 'talking out of their [censored]'. Its not like you'll ever find informations released about that sort of stuff around here.
But you'll accept it from a site that promotes adena sales and cheating?