Aerotan2008-06-25 07:32:05
Alright, I've decided to kill myse-I mean, write my own curing system from scratch, and wanted to confirm the basics.
My plan of action for this consists of:
A variable for each affliction that's curable. (incurable ones being things like Disfavors, darkmoon (I think), shattered etc.)
a variable for each type of curative, and one for eq (for afflictions that I have a cure that requires eq (fear, for instance))
a trigger that resets all the variables to 0 if I die
a trigger on certain common affliction lines (Pvp only)
a trigger on the DIAG lines
a trigger on the curative restoring stuff's eq return lines
an alias (to be fired by triggers) that runs through afflictions in a predefined series of nested #if statements in the order I'd prefer they were healed, for each type of curative.
On a scale of 1 to 10, how quickly would this get me killed, and would it even work?
Second thing, I'm wondering if it would be feasable or possible to use the area names or room numbers provided by the MAPS and MAPVIEW ON to set up a system to enable or disable certain classes of triggers, macros, aliases, and variables, based on the region you're in as you wander around on whatever task you're up to.
I was thinking of having it do this by dividing things into general regions, like Mountains, Highways, Inner Sea, Undervault, Krokani, Villiages (which really would just disable the other regional classes), etc. and having a variable that holds the current region, and a trigger on the room/area identifier in the map header that switches off the previous area and activates that area if it's not already active. Which would mean I'd need
A variable to hold the current region
A trigger for certain regions and possibly room numbers for areas that for whatever reason don't give the area name (The Razines come to mind.)
An alias to disable that group of triggers if I happen to not be doing anything or if I want to go PVP (and need to turn on EL GIGANTE DEL UN SISTEMA QUE CURA!!!1)
An alias to manually disable the active regional class.
Any thoughts, or anything I'm missing?
My plan of action for this consists of:
A variable for each affliction that's curable. (incurable ones being things like Disfavors, darkmoon (I think), shattered etc.)
a variable for each type of curative, and one for eq (for afflictions that I have a cure that requires eq (fear, for instance))
a trigger that resets all the variables to 0 if I die
a trigger on certain common affliction lines (Pvp only)
a trigger on the DIAG lines
a trigger on the curative restoring stuff's eq return lines
an alias (to be fired by triggers) that runs through afflictions in a predefined series of nested #if statements in the order I'd prefer they were healed, for each type of curative.
On a scale of 1 to 10, how quickly would this get me killed, and would it even work?
Second thing, I'm wondering if it would be feasable or possible to use the area names or room numbers provided by the MAPS and MAPVIEW ON to set up a system to enable or disable certain classes of triggers, macros, aliases, and variables, based on the region you're in as you wander around on whatever task you're up to.
I was thinking of having it do this by dividing things into general regions, like Mountains, Highways, Inner Sea, Undervault, Krokani, Villiages (which really would just disable the other regional classes), etc. and having a variable that holds the current region, and a trigger on the room/area identifier in the map header that switches off the previous area and activates that area if it's not already active. Which would mean I'd need
A variable to hold the current region
A trigger for certain regions and possibly room numbers for areas that for whatever reason don't give the area name (The Razines come to mind.)
An alias to disable that group of triggers if I happen to not be doing anything or if I want to go PVP (and need to turn on EL GIGANTE DEL UN SISTEMA QUE CURA!!!1)
An alias to manually disable the active regional class.
Any thoughts, or anything I'm missing?
Casilu2008-06-25 08:22:21
QUOTE(Aerotan @ Jun 25 2008, 12:32 AM) 525791
a trigger that resets all the variables to 0 if I die
I think that would be bad. Some mages like to use "You have been slain by" triggers.
Malarious2008-06-25 08:28:35
QUOTE(Aerotan @ Jun 25 2008, 03:32 AM) 525791
Alright, I've decided to kill myse-I mean, write my own curing system from scratch, and wanted to confirm the basics.
My plan of action for this consists of:
A variable for each affliction that's curable. (incurable ones being things like Disfavors, darkmoon (I think), shattered etc.)
Or you can use a stringlist. Dark moon targetted is curable, as a room effect its not an affliction, it gives them.
a variable for each type of curative, and one for eq (for afflictions that I have a cure that requires eq (fear, for instance))
Dont believe you need eq to COMPOSE, but you do need it for some things like gedulah. You also need to track balance for certain writhes and such. Will also need to track eq AND bal for enchants and such. Not to mention you can use these eq and bal checks when using skills.
a trigger that resets all the variables to 0 if I die
Or empties the list
a trigger on certain common affliction lines (Pvp only)
Theres a fair few affliction lines. if you mean 'venom' afflictions that tend to give a specific message like, You feel your allergy to sunlight going into remission then yes you will need those, among other things.
a trigger on the DIAG lines
Definitely
a trigger on the curative restoring stuff's eq return lines
You might want illusion protection for using cures too, so illusions will tear your system apart.
an alias (to be fired by triggers) that runs through afflictions in a predefined series of nested #if statements in the order I'd prefer they were healed, for each type of curative.
AKA the queue. This is generally required unless you use less traditional method.
On a scale of 1 to 10, how quickly would this get me killed, and would it even work?
Most of a system is 2 things.. 1) making the mechanics like the queue and 2) putting in the triggers with the like 1-3 lines of code each gets.
Second thing, I'm wondering if it would be feasable or possible to use the area names or room numbers provided by the MAPS and MAPVIEW ON to set up a system to enable or disable certain classes of triggers, macros, aliases, and variables, based on the region you're in as you wander around on whatever task you're up to.
This would probably consume more memory than it would save.
I was thinking of having it do this by dividing things into general regions, like Mountains, Highways, Inner Sea, Undervault, Krokani, Villiages (which really would just disable the other regional classes), etc. and having a variable that holds the current region, and a trigger on the room/area identifier in the map header that switches off the previous area and activates that area if it's not already active. Which would mean I'd need
Same as above.
A variable to hold the current region
A trigger for certain regions and possibly room numbers for areas that for whatever reason don't give the area name (The Razines come to mind.)
An alias to disable that group of triggers if I happen to not be doing anything or if I want to go PVP (and need to turn on EL GIGANTE DEL UN SISTEMA QUE CURA!!!1)
An alias to manually disable the active regional class.
Alias to manually change them would be better. not sure what you plan to use these for though either.
Any thoughts, or anything I'm missing?
My plan of action for this consists of:
A variable for each affliction that's curable. (incurable ones being things like Disfavors, darkmoon (I think), shattered etc.)
Or you can use a stringlist. Dark moon targetted is curable, as a room effect its not an affliction, it gives them.
a variable for each type of curative, and one for eq (for afflictions that I have a cure that requires eq (fear, for instance))
Dont believe you need eq to COMPOSE, but you do need it for some things like gedulah. You also need to track balance for certain writhes and such. Will also need to track eq AND bal for enchants and such. Not to mention you can use these eq and bal checks when using skills.
a trigger that resets all the variables to 0 if I die
Or empties the list
a trigger on certain common affliction lines (Pvp only)
Theres a fair few affliction lines. if you mean 'venom' afflictions that tend to give a specific message like, You feel your allergy to sunlight going into remission then yes you will need those, among other things.
a trigger on the DIAG lines
Definitely
a trigger on the curative restoring stuff's eq return lines
You might want illusion protection for using cures too, so illusions will tear your system apart.
an alias (to be fired by triggers) that runs through afflictions in a predefined series of nested #if statements in the order I'd prefer they were healed, for each type of curative.
AKA the queue. This is generally required unless you use less traditional method.
On a scale of 1 to 10, how quickly would this get me killed, and would it even work?
Most of a system is 2 things.. 1) making the mechanics like the queue and 2) putting in the triggers with the like 1-3 lines of code each gets.
Second thing, I'm wondering if it would be feasable or possible to use the area names or room numbers provided by the MAPS and MAPVIEW ON to set up a system to enable or disable certain classes of triggers, macros, aliases, and variables, based on the region you're in as you wander around on whatever task you're up to.
This would probably consume more memory than it would save.
I was thinking of having it do this by dividing things into general regions, like Mountains, Highways, Inner Sea, Undervault, Krokani, Villiages (which really would just disable the other regional classes), etc. and having a variable that holds the current region, and a trigger on the room/area identifier in the map header that switches off the previous area and activates that area if it's not already active. Which would mean I'd need
Same as above.
A variable to hold the current region
A trigger for certain regions and possibly room numbers for areas that for whatever reason don't give the area name (The Razines come to mind.)
An alias to disable that group of triggers if I happen to not be doing anything or if I want to go PVP (and need to turn on EL GIGANTE DEL UN SISTEMA QUE CURA!!!1)
An alias to manually disable the active regional class.
Alias to manually change them would be better. not sure what you plan to use these for though either.
Any thoughts, or anything I'm missing?
Few notes:
-Make sure you disable anything you arent using (Like I have disabled the Nihilist offense class, domination, demonology, tarot, astrology, and Vector classes since I cant use any of that.
-Have on-enable things as needed such as, you will see a certain message before the affliction, like a hex is thrown then you might see what it is.
-Auto diag and such can be useful but be very careful how you code it or you could find yourself with some repititious things.
-You need a parry and stance system in there
-You should have something to handle pipes
-You will want to check potion amounts and try to track them to an extent
-Have a way to alter your priority for curing, such that against a monk you will apply at lower numbers than normal, etc.
All that comes to mind off the top. This will kill you if you work in one huge span or time or for too long with medium amounts of dedication. Either do alot today, tomorrow, and one more day ish, or do lots of stuff often without being big groups.
Aerotan2008-06-25 08:28:36
QUOTE(casilu @ Jun 25 2008, 04:22 AM) 525802
I think that would be bad. Some mages like to use "You have been slain by" triggers.
Trigger it on '0h'? Though I suppose that would fire on increments of 10 health... Another option is to trigger it on the "You are dead and can do nothing" message you'd inevitably get after you actually die... Though really, I'd issue any mage I caught using "You have been slain by" illusions...
Nezha2008-06-25 08:48:40
QUOTE
Though really, I'd issue any mage I caught using "You have been slain by" illusions...
for what issue? its a perfectly fine way of using illusions.. thats why it exists in the first place.
