Posted: Wed Feb 18, 2009 4:45 am
As you all know, a longtime member of our community has given us a "kick in the ass" so to speak about our security system by releasing an alternative client. This made us realize that we can no longer rely on one person who is pretty much absent, and we've got a lot of untapped talent in our community. So, we've decided to create a new community-owned authentication system.
While this debate was ongoing, some members of our community noticed that this alternative client behaved differently in some respects from the latest authorized build. It did not validate the Allegiance install as it should have, potentially allowing some of our players to cheat ingame.
Some may be quick to judge, but we understand that the process of compiling/scrambling/descrambling/decompiling/upgrading/modifying/compiling/scrambling can hardly be predicted
Also, they quickly pulled this copy as soon as they heard of the issue.
So, with Pook's butt properly kicked, he's created a new version of ASGS (2.2) that addresses some of the outstanding issues with version 2.1, and makes sure this non-allegiance-validating client can't be used to cheat in Allegiance..
When I asked Pook what was updated in this, he said "Dude, a lot?"
Pook has been sitting on quite a few fixed issues in order to resolve one outstanding issue. Case in point - remember last year's "We're about to upgrade to .NET 2.0!" announcement? That was a year ago already! The Helpline mods went back and forth with Pook for months as they fixed some bugs and helped trace others. Sorry for the delay, but that's what we get in a donation-based community when someone gets busy.
Let's make sure we can handle anyone going busy.
As we've recently seen, we've got great talent in this community and we can accomplish even greater things. This community-owned security system should give us everything we need to keep moving forward at a quicker pace.
Thanks YP for kicking us in the pants, thanks Helpline staff for your tireless efforts, and thanks Pook for coming out of the shadows bearing gifts!
--TE
While this debate was ongoing, some members of our community noticed that this alternative client behaved differently in some respects from the latest authorized build. It did not validate the Allegiance install as it should have, potentially allowing some of our players to cheat ingame.
Some may be quick to judge, but we understand that the process of compiling/scrambling/descrambling/decompiling/upgrading/modifying/compiling/scrambling can hardly be predicted
Also, they quickly pulled this copy as soon as they heard of the issue.
So, with Pook's butt properly kicked, he's created a new version of ASGS (2.2) that addresses some of the outstanding issues with version 2.1, and makes sure this non-allegiance-validating client can't be used to cheat in Allegiance..
When I asked Pook what was updated in this, he said "Dude, a lot?"
Pook has been sitting on quite a few fixed issues in order to resolve one outstanding issue. Case in point - remember last year's "We're about to upgrade to .NET 2.0!" announcement? That was a year ago already! The Helpline mods went back and forth with Pook for months as they fixed some bugs and helped trace others. Sorry for the delay, but that's what we get in a donation-based community when someone gets busy.
Let's make sure we can handle anyone going busy.
As we've recently seen, we've got great talent in this community and we can accomplish even greater things. This community-owned security system should give us everything we need to keep moving forward at a quicker pace.
Thanks YP for kicking us in the pants, thanks Helpline staff for your tireless efforts, and thanks Pook for coming out of the shadows bearing gifts!
--TE