Welcome to the Achaea Forums! Please be sure to read the
Forum Rules.
Server Side curing customization question.
I've read that server side curing is great if you know how to tweak it. Can I take this to mean maybe a few aliases that change priorities based on what class you're fighting against?
If I wanted to go about doing this, where would I begin?
0
Comments
1. Part of the allure of server side curing was that I could use any client. I understand Mudlet is the best, but I thought if my system was effectively server side curing, I could rely on CMUD for offense and make it myself without having to learn LUA. I can't even recall how to make a targeting alias in Mudlet.
2. Being Australian, latency is a factor. Server side curing solves that for me. At least as far as defense goes.
Edit: Third thought.
3. If I did end up using Mudlet it would have a lot of pros in its favor. Like being able to have an affliction tracker out of the box in the form of AK. The mapper is an obvious advantage, even though I do have a converted map using the old Imapper that works here and a conversion tool that turns the provided map file into a readable format for it so it works in any client. Then there's also the multiple GUI's and other scripts people have published.
Still though... It's all coming down to having to learn a whole new language when I've already got to relearn the game. Hrm...
You can theoretically use curingsets for individual classes, but the game by default only allows you a limited number, and you can pay credits to expand this. This is completely silly and I wish it wasn't the case. You can run toggles clientside to quickly rearrange your prios to fit the class you want, though. I recommend using a NDB script of some variety if you want to avoid toggling between sets manually.
As an example, if paralysis is above asthma and at places 4 and 6 respectively, you could CURING PRIORITY ASTHMA 3 to toggle asthma above paralysis, and then CURING PRIORITY ASTHMA 6 to put it back (or CURINGSET CLONE FROM DEFAULT). If you want automatic toggles, you can use gmcp events on affliction gain and loss to run the commands mentioned before, using your client of choice. As a class-related curingset example, you could theoretically have something like a serpent set, and do CURINGSET SWITCH SERPENT, where you'd have things like impatience higher than normal, etc. Use CURINGSET SWITCH DEFAULT to swap to your default set, don't use clone here as it will wreck whatever you have setup.
I came from CMUD when I retired to Achaea and have spent my time getting familiar with Mudlet, it's a big hurdle at first but becomes relatively intuitive quickly; in the long term I would recommend getting familiar with it if only because of the extensive resources available. But you don't need it to have a fully functional curing system.
But in certain scenarios would'nt that mean I would not be able to change my priority fast enough and might end up eating something I would like to have changed before sending eat <herb>.
Scenario: I have paralysis and asthma, impatience. I get hit by slickness and anorexia and tree balance is out and I get herb balance back. My system in such scenario would bump asthma up in priority above paralysis unless I got multiple kelp cures then it would bump impatience otherwise just leave it and cure paralysis. This could be easily changed on the serverside curing also. But if it's faster then my local system sending the priority change it would eat a bloodroot and cure paralysis, right?
Edit: Same scenario without anorexia for example.
Results of disembowel testing | Knight limb counter | GMCP AB files
Assuming we're not talking absolute garbage latency. If you've got a 1 second delay on all of your commands it's going to happen a lot more often.
Results of disembowel testing | Knight limb counter | GMCP AB files