Due in part to the blatent, numerous, and uncontrolable license violations, but also because it's become more trouble to produce ACScript than it's worth, ACScript will no longer be distributed publicly.

From the user demands for features and support to the expectation that we give away the rights to our work and property, ACScript is no longer 'fun' to work on. It no longer provides a net positive experience for the authors. In some ways, the product is a victim of it's own success. Users want the product so badly, that they're willing to go to lengths to get it - even to the point of theft. It's simply too difficult to meet expectations and defend the product while keeping our day jobs.

There are many ACScript users who have made great contributions to the community. We regret that we're no longer able to deliver a useful tool to these people. We'd like to thank those of you who had a positive effect on ACScript for your effort and support - you know who you are.

All ACScript support and information forums on this site will be terminated immediately. There will be no future updates to ACScript. Although most of ACScript will presumably continue working until AC protocol changes take effect, all users are advised to stop running ACScript immediately, since we can not provide any support or assistance with any bugs or problems you may encounter.

Technical Note Regarding Recent EULA Enforcement Issues:

In a rebuttal posted on Crossroad's of Dereth (http://cod.xrgaming.net/?news=1news#TheACScriptCounterpoint), it was stated that there was a check in low level ACScript code that had to be "hacked" before higher level EULA enforcement code could be executed. While there is such code in the system, a recent protocol change caused it to fail. In the login packet a vector triggered by bit flag 0x40 contained, at one point, two values: the user's patron's ID (type 0x19), and the user's monarch's ID (type 0x18). In an effort to verify that this initial check was still working, it was discovered today that type 0x18 no longer contains the monarch ID. This caused the initial check to be ignored.

Our intent was to disable ACScript for license violators, and only invoke negative actions in cases where our binaries had been hacked. While we regret that this part of our code ultimately failed to do its job, we nevertheless feel that the EULA was sufficient warning to all users.

Lax
9/24/2001