Just a couple ideas for Aeon that may or may not be unreasonable.
1. Instead of hindering all commands, aeon allows all commands to go through as normal, but puts a 2 second delay on the "balance" of the action. i.e. your first command goes through normal, but it takes an extra 2 seconds for you to be able to be healed by mana. So, lighting a pipe or taking out herbs goes at normal speed, but attacks and curing are slowed.
2. Aeon works as normal, but doesn't create a "Cue" of commands that overwrite eachother. Everything is just slower, as if you have really bad lag.
Hopefully, I'd like to see something that still does basically the same thing, but doesn't need its own coded subsystem to handle.
Comments
Primary Goals
- Reduce or eliminate the extra burden on system builders that aeon and sap provide.
- Reduce unfun situations where someone can never be able to do anything.
Secondary Goals
- Ensure that guilds heavily reliant on aeon effects can be reworked with the least amount of effort.
- Keep aeon as a unique affliction filling a unique niche (aka not redundant or just a super powered version of other afflictions).
- Keep aeon simple conceptually and from an admin coding standpoint.
- Keep the thematics of aeon as much as possible.
- Keep everything within the Overhaul cures and systems.
The more of these goals that are met, then the more likely it will be considered by the admins.
I'll try to brainstorm some ideas to post later.
The purpose of Aeon for the lusternian classes that have it is not to 'slow down' curing balances, in the sense your solution 2 captures. It's to disallow stacked commands, so that you can't get out of locks. You have to send the melancholy command - wait a second for it to go through (or fail), send the smoke command - wait a second for it to go through (or fail), then send the aeon cure command - wait a second, etc. In a queue based system, you'd send the stacked commands as normal (SM ADD apply|smoke|eat) and they'd all take place as quickly, one second later. Changing things that currently rely on/revolve around aeon to this kind of system would be equivalently disruptive as just dropping aeon. The IREs that have that kind of aeon (retardation) use it for different purposes, and have been slowly phasing it out, afaik.
What third purpose of Aeon am I missing?
Even if this idea went in, the delay should be longer and the balance taken from doing weak aeon shorter. To start with.
It's whatever. I don't really expect anyone to let go of their 0p-aeon spamming bards, it was just a thought about a possible pruning choice.
Forgiveness is the fragrance that the violet sheds on the heel that has crushed it.
Aeon is fine.
Skills that bypass its defense immediately with no real cost or skills that give aeon + 3 affs are what need to be examined.
I assume you mean something like... eat dust, it goes through like normal, but takes 2s longer to regain dust balance. Might be workable in general, though would probably require significant changes to certain guilds. Definitely not much of a system burden, so I like that.
Enyalida has the right of it on the one action at a time thing.
My main concern with aeon is the extra burden it puts on writing a system. Aeon isn't necessarily OP (though certain aeon skills can be), but it can still be bad while not being unbalanced.
The other option I was thinking of was that along with the delayed balance recovery, each action also locks all your balances. But I think at that point you create another system re-coding beast, so it would not be worth it. Better, in my view, to just figure out what exactly would have to be changed for the guilds that rely on one action only rather than the slowness.
Actions of and to the victim are delayed, except actions to the victim don't overwrite each other.
I give you Aeon.
While you have Aeon, I give you asthma plus stun you. The asthma and stun also are delayed by two seconds, OR, immediately hit if aeon is cured.
This would give you two seconds to cure Aeon without being hindered by the other afflictions, but also allow me to stack the other afflictions at the same time.
Ex: I am aeoned, I can queue up smoke steam;stand;hi and not have it cancel my smoke attempt. It will just fire with a delay as with right now.
Imo this would take care of a lot of the coding.
But still, aeon itself is fine.
I can dig that.
Just make something equatable in return.
Aeon is a "problem" by itself, for coding systems.