What she said

If you can code for it, no. Otherwise yes.

Other fun system-annoyances:

ForcedEmpathy - You see the affliction/cure lines of anyone else in your location as if they were happening to you.

Hyperchondria - You get spammed with false cure lines and balance recovery messages.

InnerEarInfection - You lose the balance (eq/balance/channels/whatever) component of your prompt and do not see balance (eq/balance/channels/herbs/elixirs/whatever) recovery messages. You would still get the "You need equilibrium for that" messages as well as the use of your skills. For example:

3455h, 5098m, 5379e, 10p, 13575en, 21225w - invoke circle
Spreading your arms wide, you spin clockwise and visualize a circle of protection. A shimmering
white orb springs up around you.
3455h, 5068m, 5379e, 10p, 13575en, 21195w - invoke circle
Spreading your arms wide, you spin clockwise and visualize a circle of protection. A shimmering
white orb springs up around you.

We already have hypochondria.

Yeah, I'm using the 'pretend' opposite - hyPERchondria.

What point do these afflictions serve other than to annoy our current system coders, as well as making it even harder for new coders to get into the game?

That is indeed exactly the point. To make it extremely difficult to automate curing of at least some nasty afflictions, and reshuffle the importance of a system slightly. Not every player has access to the same client features (although the free systems out there are -awesome- for those who want to seriously get into PvP), and these would be interesting in making sure that sometimes you had to manage your curing semi-manually in addition to your system handling it.

I think most of the top tier combatants have a good enough understanding of afflictions/combat/tactics and so on that these afflictions probably wouldn't matter much to them - they don't seem to rely on systems as much.

I also like the idea of a touch of randomness in some tactics, it makes it less likely that absolute precision is expected and required to survive.

Oh, silly me, neglected to read carefully. Anyway, as stated...those things probably would be codable, though if there was some way to make an affliction such that it was unreliable to automate, that would be awesome.

The only thing those types of afflictions do, is make the systems required to cure them bulkier and more annoying to code with the given lanaguages available.

It doesn't stop it from being codeable.

It would basically be just another version of Choke or Aeon, where the system is stalled until that particular affliction is cured, or a seperate counting system is put in to keep track of the balances you have etc.

edit: Anything that would be impossible to code against, would be equally impossible for a player to heal against manually. I believe they tried to make these "anti system afflictions" allready, with Aeon, the "prickly* sen*ation" pattern, and blackout.

I think almost anything can be near-automated if a complex enough system is developed, I'm just suggesting things that might pose significant challenge to do so!

I mean, doesn't hypochondria have the sole purpose of messing with systems?

Yeah, but hypochondria sucks and is easy to work around.

Anyway, the point is that unless you actually -can't- automate it, it doesn't add any more skill to the game, it just makes coding more annoying. And once someone's gotten it into a free system, it removes the skill part of it from the equation again, so it's a net negative.

But isn't that true of all afflictions?

I find hypocondria to be worse for manual healing, because of the spam and being unable to realy tell whats real and whats not at a good pace.

@avaer What do you mean isn't that true of all afflictions?? Aflictions cause real delays and impedements to both staying alive and killing your opponent. And most arn't annoying to code for at all.

Well...kind of, but they also slow down healing physically, or have effects that matter, or cover up other afflictions, or whatever. They're designed to do a job and give classes options in killing people such that intelligent usage outpaces perfect curing, etc.

Yours could probably do the same thing, but you seem to be intending them to annoy system-users, which isn't a good enough reason on its own because it won't do the whole job.

I don't agree, but fair enough, they're only suggestions!

I won't lie, your suggestions seem like they exist soley to piss off coders. Not to mention some are just ridiculous. Can you imagine trying to cure sap without balance tracking? Hell no.

Affliction classes could use some buffs, but afflictions that exist solely to bog down systems and lag them out is not the way to go.

edit: Forgot to mention, afflictions that break systems solely on their own are bad, bad ideas. Something like losing balance/eq/herb/etc on prompt will (I think) break a lot of systems. They will just stop working because the prompt is suddenly not what it's supposed to be. Screwing with prompts via afflictions = atomic no.

DON'T MESS WITH ME!!!1!




We have plenty enough afflictions already, and I would be so happy to never see another new affliction added to Lusternia for as long as I continue playing. Adding afflictions just to screw up my system, which is already enormously complex and full of holes, is only going to serve to push me right out of the game, and I'm going to take my code with me, crying all the way home.

All (at least those I read) Avaer's affliction suggestions can be summed up in one affliction.
I see two approaches here...

1. AB COMBAT IPWNURSYSTM (13% Apprentice) - You no longer see balance messages, affliction lines or prompt. You are still able to diagnose to make you even angrier because your inability to cure manually was what really killed you.

- OR -

2. AB CELESTIALISM CELESTINESROP (0% Capable) - Deletes all system triggers and variables and calls down a holy Inquisition on the target.

I like the idea of making it so combat doesn't depend on systems. But in Lusternia, the horse is so far out of the barn that he's already built himself an airplane and flown to Honolulu. At this point, making systems harder is a bad bad bad bad bad idea. If anything we need to be getting rid of system-screwing things. The availability of systems like Catarin's and Zarquan's systems is barely a saving grace on the agony of getting started in an increasingly difficult combat arena Render those easily bypassed and you will make the few not already being discouraged even more likely to throw up their hands and wander off to something else.

Because combat is essentially based on systems now, I still don't think that the system-wrecking afflictions would be the way to go. Plus, IG you'd have to be pretty messed up to not know that you have two broken arms, a giant hole in your stomach, drenched in sap, and being snapped in pieces - all at the same time.