Malibu Stacey
Active member
It has came to my attention that this thread doesn't exist and probably should.
Back in September 2019 when certain details about the KoL dev team were made public, some of the people working on sl_ascend decided to step back from KoL. However there were some of us contributors who wished to continue contributing so a new fork was created with a team owner as this allows people to join and leave without affecting development velocity or requiring users to switch to new forks periodically.
As most of the contributors who left back in September 2019 have returned, autoscend can be considered more of a continuation of sl_ascend than a fork (even soolar himself has updated the sl_ascend repo to indicate this and has been contributing to autoscend since he returned to KoL).
It can be found at https://github.com/Loathing-Associates-Scripting-Society/autoscend
Back in September 2019 when certain details about the KoL dev team were made public, some of the people working on sl_ascend decided to step back from KoL. However there were some of us contributors who wished to continue contributing so a new fork was created with a team owner as this allows people to join and leave without affecting development velocity or requiring users to switch to new forks periodically.
As most of the contributors who left back in September 2019 have returned, autoscend can be considered more of a continuation of sl_ascend than a fork (even soolar himself has updated the sl_ascend repo to indicate this and has been contributing to autoscend since he returned to KoL).
It can be found at https://github.com/Loathing-Associates-Scripting-Society/autoscend
- We recommend reading the ReadMe as it contains important information regarding in-game requirements and recommendations. It is the landing page on the GitHub repo link above.
- We would prefer issues to be reported through the issue tracker on GitHub (see link above) or in the #autoscend channel in the ASS Discord server. Posts in this thread are much less likely to get a timely response.
- Contributing code is open to anyone and very much appreciated regardless of skill or ability. Information on how to submit a pull request can be found in the GitHub repo under the docs directory.
- Keep in mind that our support for paths and IotMs depends entirely upon the volunteers who contribute code changes. If it isn't supported yet, it's because no one has written that code yet. Support for newly released IotMs and challenge paths will generally lag behind their release while spading is conducted by the wider KoL community but we very much appreciate feedback on bugs or potential improvements once we have some basic functionality in place.
- We primarily target Standard and the current challenge path (whatever that is) for our development efforts. However this does not mean other paths have no support, it means they are a lower priority. Some older paths will receive more support than others for various reasons and we will endeavour to fix any egregious issues in older paths. However bear in mind that the older the path is, the less well supported it will likely be (cc_ascend was originally created to script Actually Ed the Undying which was the Spring 2015 path).
