In my version (4.1) weariness is a focusable affliction and I have tried to make that not so, but just taking it off the table did nothing. Anyone know how to tweak that bit?
Cured by kelp. Add it to AK Opponent Tracking folder and OReset, and OScore.
That is not an ordinary star, my son.
That star is the tear of a warrior. A lost soul who has finished his
battles somewhere on this planet. A pitiful soul who could not find his
way to the lofty realm where the great spirit awaits us all.
And I can't find where it actually has the affs that are cured by focus where I can take weariness as focusable out. Everytime my target uses focus it goes down or to 50 if they have 2 focus affs
My version is actually an extremely gutted edition of 2.0.
I just increase the version number of my copy whenever there is a big update to classes (eventually caught up to 4.1 and kept updating beyond that).
That is not an ordinary star, my son.
That star is the tear of a warrior. A lost soul who has finished his
battles somewhere on this planet. A pitiful soul who could not find his
way to the lofty realm where the great spirit awaits us all.
Basically you gotta remove weariness from the focused table and add it to the kelp table from these two scripts:
But not only that, you need to make sure that weariness does not exist in the the ginseng table or any other tables that may have an edible cure that has a focus cure alternative.
You also need to move it from ginseng and mentscore in the oscore table:
But yeah, you'll find many AK users with different versions. I've seen 4.2, 4.3, 4.4.... and they definitely weren't something I updated. And even though they got higher versions, I've seen them carry outdated stuff compared to older AK versions.
It's not really all that surprising since the original developer stopped releasing updates and people just started picking up from whatever was left off from there.
That is not an ordinary star, my son.
That star is the tear of a warrior. A lost soul who has finished his
battles somewhere on this planet. A pitiful soul who could not find his
way to the lofty realm where the great spirit awaits us all.
installed ak, but in the end I couldnt figure out how to get the gui set up properly, so I uninstalled it. now my screen is like this. any way to fix it? (both ak and its akg are uninstalled now )
@Dulcimer Gonna have to go into SETTINGS and fiddle with the Display Border values under the Main display tab. Right Border Width should be the one to fix that up.
@Dulcimer Gonna have to go into SETTINGS and fiddle with the Display Border values under the Main display tab. Right Border Width should be the one to fix that up.
Having never touched AK despite people being adamant I use it. How hard is it to implement Depthswalker and its afflictions? We've a Newbie Depthswalker I'm trying to help, but as far as I'm aware, leach, loop, madness, depression, etc aren't in AK, right? Would it just take a solid hour or so writing everything in? Would I need to go into the internal settings and write in 'leach' and cures for it being kelp? (Then obviously add in every unique affliction)
im late but i have these things if you still want them kythra?
Just reaching out to see if you would share with me your more up-to-date version of AK.
You will also want to add these affs to the 'treed' cure list, and give them a value in the score table (This is VERY IMPORTANT).
The affs are now recognized and tracked by AK. To use them, you need your delivery lines from your attacks. Here's a freebie, using Leach (you will want to use your own thresholds):
TRIGGER:
^As the weapon strikes (\w+), (he|she) seems greatly diminished.$
SCRIPT:
if matches[2]==target then<br>lastinstill="leach"<br> if affstrack.score.parasite<75 then<br> OppGainedAff("parasite")<br> elseif affstrack.score.healthleech<75 then<br> OppGainedAff("healthleech")<br> else<br> OppGainedAff("manaleech")<br> end<br>end
TRIGGER:
^As the scythe comes away, the writhing shadow of (\w+) clings to the weapon.$
SCRIPT:
cecho("<cyan>"..target.." has leach capstone!") OppGainedAff("parasite") OppGainedAff("healthleech") OppGainedAff("manaleech") end if matches[2]==target then<br><code><code>lastinstill="leach"
</code> <br>In that example you're progressively tracking Leach, and when capstone flares, it will give any affs you somehow missed and restore the ones you do have to 100%.<br><br>Go through and add hit + capstone lines for everything. Another useful trigger is timeloop procs:<br><br><pre class="CodeBlock"><code>^A grey miasma flares around (\w+).$Remember the "lastinstill" being set in those attacks? Use that for timeloop procs and basically have it run the relevant function again. Now your loop hits will let you know what they're afflicting with.
(Note that some of this may be conflicting tracking if another DW is in the room hitting your same target, since the messages are not all unique to the user. YMMV. But this has worked for me so far.)
You don't really need to track DW at all to be honest; just put in huge highlights when you see capstones and the rest is watching what someone cures on the way to the capstone effects. Swapping your instill when you need to and smart use of loop are also not things you'll need a script to do for you.
For me, posting an updated AK for free is the problem. People have spent MONTHS of coding to customize AK for themselves. People who don't know how to code can quickly learn if they put their minds to it. I did it in 8 weeks after asking on these forums for help with systems, etc. Since I knew I wasn't getting help it pushed me to code myself.
I messaged/sent tells to @Austere about updating and repackaging it, but alas no response
(Realistically not the best person to do it anyway, my scripts are atrocious to look at)
I think picking apart AK and figuring out what makes it work is valuable, and you're pretty much forced to do that to get it in working order right now. It would be good to have some parts be a lot more obvious though.
@Dhaak it looks like this is something added via that DW script listed earlier in the forums. Search for the 'Disable Instills' trigger and delete the echo.
For me, posting an updated AK for free is the problem. People have spent MONTHS of coding to customize AK for themselves. People who don't know how to code can quickly learn if they put their minds to it. I did it in 8 weeks after asking on these forums for help with systems, etc. Since I knew I wasn't getting help it pushed me to code myself.
Yet you presumably had no problem taking the original version of AK - which probably took more effort to code from scratch than it's taken people to modify - that was released for free and using it.
I think picking apart AK and figuring out what makes it work is valuable, and you're pretty much forced to do that to get it in working order right now. It would be good to have some parts be a lot more obvious though.
I have been taking a look at it for the past few days but this is going to be a slow process. I'v gotten significantly better at Lua since joining Achaea, as my comments might suggest, so I think it shouldn't be too bad. I just have to go through everything and document the flow of it. I also could not find posts by Shecks describing the logic as Austere posted about in the first post (I looked around 2015, 2014) but I understand the percent process of attributing afflictions and then what the statistical chance is they still have it on subsequent multi afflictions considering what cure they ate and its' pool of things it can cure.
I think picking apart AK and figuring out what makes it work is valuable, and you're pretty much forced to do that to get it in working order right now. It would be good to have some parts be a lot more obvious though.
I have been taking a look at it for the past few days but this is going to be a slow process. I'v gotten significantly better at Lua since joining Achaea, as my comments might suggest, so I think it shouldn't be too bad. I just have to go through everything and document the flow of it. I also could not find posts by Shecks describing the logic as Austere posted about in the first post (I looked around 2015, 2014) but I understand the percent process of attributing afflictions and then what the statistical chance is they still have it on subsequent multi afflictions considering what cure they ate and its' pool of things it can cure.
This has been the case for me too - I couldn't even really make functional triggers with Mudlet before I started up again in Achaea a couple of years ago, and just trying to get these functions to work how I want them to has helped a ton. That's why I really advocate picking it apart, even if it's difficult to understand and not the most efficient way of doing things (mostly due to a lot of functionality changes, i.e. expert diagnoser).
I think the most important scripts to look at are the oscore edit functions and the backtrack functions, especially the 'Thought I had Functions'. I... don't fully understand the latter to be honest, but backtracking is really the most complex and important part. The basic tracking logic outside of this is relatively intuitive I think.
I messaged/sent tells to @Austere about updating and repackaging it, but alas no response
He is not around a lot. He has a new-ish kid and whatnot (Pretty sure he's mentioned it here so I don't mean to put his personal business out there). I'm 99% sure that he is less likely to update and code it for new stuff than he is to log in and just kill folks. His time is being spent where it should, honestly.
Oh, I figured there was a good reason. I just don't want to take over someone's work without their permission. I'm chugging alone slowly on my own thing, so someday maybe!
For me, posting an updated AK for free is the problem. People have spent MONTHS of coding to customize AK for themselves. People who don't know how to code can quickly learn if they put their minds to it. I did it in 8 weeks after asking on these forums for help with systems, etc. Since I knew I wasn't getting help it pushed me to code myself.
Yeh, this community sucks at giving free stuff out.. ..
I don't track in the same way as AK, and I'm not going to give out my full tracking with all the bells and whistles for a variety of reasons, but would people be interested in a somewhat basic version of my tracking?
Dunn tells you, "I hate you." (Party): You say, "Bad plan coming right up."
I would be interesting to hear your logic/setup, personally. I also am curious how tracking opponent afflictions turned in to incorporating an attacking protocol? I mean, I understand why these two ideas play off each other it just seems it would be much more complicated to start making kill systems
I don't track in the same way as AK, and I'm not going to give out my full tracking with all the bells and whistles for a variety of reasons, but would people be interested in a somewhat basic version of my tracking?
Yes, yes we would. I'll steal all your good ideas and use them for my own benefit
I messaged/sent tells to @Austere about updating and repackaging it, but alas no response
He is not around a lot. He has a new-ish kid and whatnot (Pretty sure he's mentioned it here so I don't mean to put his personal business out there). I'm 99% sure that he is less likely to update and code it for new stuff than he is to log in and just kill folks. His time is being spent where it should, honestly.
It's not that I don't have time. Ak is essentially ready for a new release, with all new classes minus earth and fire; I've just held off for a long time because of the general whining it's bound to bring about. By in large, the coding community was entirely too entitled last time I was heavy into public things, which contributed to my withdraw of support (read back through the thread or any where else people have discussed hundreds of hours of this hobbyist's code). If release today, I'd get fifty messages a day for the next year bitching about functionality and my personal coding habits. As a self taught coder, my original release saw more complaints than gratitude, and I just haven't been willing to subject myself to the masses again until I can ensure complete, across the board, functionality.
As far anyone considering rereleasing ak, I would encourage you to devote your efforts towards your own system. I -will- release a new ak this year, with way way better logic and tracking. It's on my bucket list after all. It's not that i dont want the help, its just that there's four or five of us that have devoted the past year to updates, so by in large, it's just not needed at this point. It's the tiny issues that concern me (such as limb damage).
If this reply sounds mean, it was not my intention. I just want to ensure another ak doesn't contribute to my dormancy. Some of you have been great, and the encouragement is always appreciated.
Comments
Results of disembowel testing | Knight limb counter | GMCP AB files
My version is actually an extremely gutted edition of 2.0.
I just increase the version number of my copy whenever there is a big update to classes (eventually caught up to 4.1 and kept updating beyond that).
But not only that, you need to make sure that weariness does not exist in the the ginseng table or any other tables that may have an edible cure that has a focus cure alternative.
You also need to move it from ginseng and mentscore in the oscore table:
But yeah, you'll find many AK users with different versions. I've seen 4.2, 4.3, 4.4.... and they definitely weren't something I updated. And even though they got higher versions, I've seen them carry outdated stuff compared to older AK versions.
It's not really all that surprising since the original developer stopped releasing updates and people just started picking up from whatever was left off from there.
http://myjackspace.com/scripts/
Go to AK Opponent Tracking script folder. Both this class script and the oreset function need their aff tables updated.
For instance, with the new affs, your eat table should look something like:
You will also want to add these affs to the 'treed' cure list, and give them a value in the score table (This is VERY IMPORTANT).
The affs are now recognized and tracked by AK. To use them, you need your delivery lines from your attacks. Here's a freebie, using Leach (you will want to use your own thresholds):
TRIGGER:
SCRIPT:
TRIGGER:
SCRIPT:
</code> <br>In that example you're progressively tracking Leach, and when capstone flares, it will give any affs you somehow missed and restore the ones you do have to 100%.<br><br>Go through and add hit + capstone lines for everything. Another useful trigger is timeloop procs:<br><br><pre class="CodeBlock"><code>^A grey miasma flares around (\w+).$
Remember the "lastinstill" being set in those attacks? Use that for timeloop procs and basically have it run the relevant function again. Now your loop hits will let you know what they're afflicting with.(Note that some of this may be conflicting tracking if another DW is in the room hitting your same target, since the messages are not all unique to the user. YMMV. But this has worked for me so far.)
You don't really need to track DW at all to be honest; just put in huge highlights when you see capstones and the rest is watching what someone cures on the way to the capstone effects. Swapping your instill when you need to and smart use of loop are also not things you'll need a script to do for you.
Any ideas how to fix that?
(Realistically not the best person to do it anyway, my scripts are atrocious to look at)
I think picking apart AK and figuring out what makes it work is valuable, and you're pretty much forced to do that to get it in working order right now. It would be good to have some parts be a lot more obvious though.
@Dhaak it looks like this is something added via that DW script listed earlier in the forums. Search for the 'Disable Instills' trigger and delete the echo.
Results of disembowel testing | Knight limb counter | GMCP AB files
I think the most important scripts to look at are the oscore edit functions and the backtrack functions, especially the 'Thought I had Functions'. I... don't fully understand the latter to be honest, but backtracking is really the most complex and important part. The basic tracking logic outside of this is relatively intuitive I think.
He is not around a lot. He has a new-ish kid and whatnot (Pretty sure he's mentioned it here so I don't mean to put his personal business out there). I'm 99% sure that he is less likely to update and code it for new stuff than he is to log in and just kill folks. His time is being spent where it should, honestly.
Dunn tells you, "I hate you."
(Party): You say, "Bad plan coming right up."
It's not that I don't have time. Ak is essentially ready for a new release, with all new classes minus earth and fire; I've just held off for a long time because of the general whining it's bound to bring about. By in large, the coding community was entirely too entitled last time I was heavy into public things, which contributed to my withdraw of support (read back through the thread or any where else people have discussed hundreds of hours of this hobbyist's code). If release today, I'd get fifty messages a day for the next year bitching about functionality and my personal coding habits. As a self taught coder, my original release saw more complaints than gratitude, and I just haven't been willing to subject myself to the masses again until I can ensure complete, across the board, functionality.
As far anyone considering rereleasing ak, I would encourage you to devote your efforts towards your own system. I -will- release a new ak this year, with way way better logic and tracking. It's on my bucket list after all. It's not that i dont want the help, its just that there's four or five of us that have devoted the past year to updates, so by in large, it's just not needed at this point. It's the tiny issues that concern me (such as limb damage).
If this reply sounds mean, it was not my intention. I just want to ensure another ak doesn't contribute to my dormancy. Some of you have been great, and the encouragement is always appreciated.