Angelic_EU

I think you read wrong.

I propose the change in the mechanic, or the methodology, in doing something; not the substance itself. What I was saying was similar to suggesting people to use folks and knives to eat steaks instead of chopsticks. I never say I want a different steak to go with my folk and knife.

THANK YOU!! soooo much for the neat clarification! People went off the tangent a bit in some of the posts.

If I filter out the off-topic discussions, I think most of us agree that it will be a good quality of life improvement if the casting/buffing mechanism is to be changed. I know some would prefer to keep using the current one-to-one casting mechanism; and some fear that an AoE casting would give them the buff(s) they don't want (on this point, mostly because of some buffer use horrid colours for the already headache inducing shields; or more specific case, the +recharge component of a SB).

I believe that the change I propose here is going benefit more people given the current direction of the development of CoX gameplay: faster, bigger groups, more dynamic. That said, compromise can be made on technical ground to cater those who prefer the existing one-to-one mechanism.

Lets just look at shield buffs for now and leave mez prots and SB aside; and all buffs mentioned here are self-excluding from the point of view of the buffer (I still don't understand why people think changing it to an AoE cast would mean changing it to self-including as well - I have never even hinted that). Originally I suggested to have a MM-upgrade style mechanism. Although I did not spell out the details exactly, a MM-upgrade style, in my mind, is essentially: click on one recipient (say a tank at the front line or a group of blasters huddle up at a distance) and everyone else, including the recipient but excluding the caster, within a certain radius will receive a shield. Some mentioned that endurance usage would be a problem. In my view, it needs not be. Testings are needed to find an acceptable balance between endurance, recharge, range, and radius. But at this stage, in principle, this is how an AoE cast would look like.

Then someone suggested a Terra-Volta-bubble-machine style of mechanic. I found it quite interesting and conceptualised some details. Essentially it is to change the click-cast mechanism to a toggle mechanism, which will be similar to Grant Cover from Shield Defence. Some people wrongly assumed that it would be a Dispersion Bubble style toggle and went on and on about it. It would not be a self-affecting toggle and I would prefer the toggle to be invisible. Leaving the consideration of end usage to a later day, I think this mechanism is going to benefit the buffer most as it gives him more time to do something else - essentially a care-free mechanism. At the same time, it will benefit the recipient in a way that, so long as the toggle is running, he can go near the buffer to get his shields. It is a win-win situation. The problem is that some recipient may not want certain kinds of shields for whatever reason; then they have to keep avoiding the caster.

So, I suggest an 'Opt-Out' function for buff. Perhaps add to the Team or League windows an 'Opt-Out' button whereby one can choose to not receive any shield-buff from the team. This is opinion one. Opinion two would extend the Opt-Out further to everyone else. So never again would you get any headache inducing buff that you don't want at all. Finally opinion three would be just to disable the graphic of the buff - as in you still get the defence/resistance bonuses from the shields; you just can't see they are there. Option three is my favourite.

Back to the casting mechanic. Finally I suggested to use the ML/RAs style mechanic. To be fair, it is just the same as the abovementioned MM-upgrade mechanic but with the centre of origin back to the caster himself (and again, the caster will not be affacted by the cast). Someone quickly point out that this mechanic may leave out those who are out of range. It is not a new problem anyway. ML and RAs have a longer recharge so missing out seems to be an obvious annoyance. For the new mechanic, a careful balance between end, recharge and range will easy mitigate the problem. Besides, as mentioned above, the caster can always announce it before casting the buff - like some people alreay do with their ML and RAs.

So there you have it: 3 suggestions for a new shield buffing mechanic. Most of the problems discussed so far can simply be resolved by adjusting end usage, recharge and range to an acceptable level. And a minor adjustment of playstyle. I still believe that benefits of an AoE casting mechanism outweigh all the problems it might have.

Option 2 would be a Mind Link/RAs style mechanism; probably with buff duration last longer than the current 4 minutes. So, if someone does not want the buff, just avoid the group hug.

You are assuming too much at this stage.

Besides, there will be a way to get around this if the end cost is too high. No need to be bogged down with fine technical details yet. Lets work on the theme work first and conceptualise the GoL should it be implemented.

I would love to agree with you, besides the tautologies. But I have seen this argument before used by MM, corr, certain types of dom and def, and even brute supporters too.

I would love to see Kheldians are that strong. But I am still unconvinced. A team in this game normally (I stressed 'normally') requires teammates with extreme specialities. One Kheldian just cannot do it on its own.

No you are wrong.

They are not even mechanically identical. Besides, the point of the suggestion is to dispense with the casting mechanism substituting something convenient to operate - particularly in a fast pace and large team running around in a chaotic environment.

I think what we are talking here is to do without casting altogether, nevermind normalising the time. At this stage, the crux of the suggestion is to change the tedious select-click-cast mechanism into a toggle mechanism. Once the toggle is up, whosoever within the toggle area will receive a buff, or a shield.

Lets use FF as an example. Currently, you need to select someone, click on, say, Deflection Shield, rooted, and wait for it to cast on your subject; then repeat again for the next one, and the next, and so on. But what we are saying here is to change Deflection Shield (along with other similar powers) into a toggle with a radius of however big. Whoever steps inside that toggle area (or I called it 'catchment area' above) will receive a Deflection Shield without the FFer needing to select that person, click, rooted and cast anymore.

While that person is within the Deflection Shield toggle radius, a Deflection Shield will always be on him so long as the toggle is running. If that person is stepping out of the toggle radius, or the buffer dies, the Deflection Shield will expire after 4 minutes (or however it is meant to be). Of course, it is renewable once that person steps into the toggle radius again. All the FFer needs to do is to run the toggle and perhaps manage his Endurance. He can then be more engaged into the trial/tf/sf/mission. Also, on a side note: buffing roots the buffer down regularly. Nevermind being tedious and laborious, it is just not fun to be in a fast pace trial/tf/sf while being rooted down every so often. (that reminds me of a Apex tf with my kin. Being rooted down while trying to SB my team got me kill more often than I actually trying to fight Battle Maiden.)

I think that makes buffers' job a lot less mechanically repetitive and mental tedious. The recipients get their buffs - and so long as the toggle is running, he can go and get it himself. It is a win-win suggestion.

WINNING!!!

I think that is a very good idea. Have the shields (ice, fire, FF, sonic, whatever else) run as toggles with a spherical catchment area where if, say, a teammate or league member falls within which they will receive new shields. If that person run off the catchment area, the shields wear off in accordance with their current life-span (4 minutes or however long). Conversely, if that person stay within the catchment area, the life-span will always be at its maximum.

As to SB, from my experience (I use my kin rather too often in the last 2 years), most of the time, people can do well without it. I know some people hate SB for its +speed. As to the +recharge and +recovery portions of it, they are really nice touch but not exactly game breaking. Most people want a Kin for other of its powers. So personally, I wounld not mind SB uses the catchment area buffing method along with all other shields. If being OP is a real concern for most people - for example, SB will come by too easily - shink the catchment area or lower the +recharge portion or even shorten its life-span a bit - just a bit though.

As to mez prot, I don't mind it is to be remained as a click one-to-one cast, or change it to a Mind-Link style buff, or use the abovementioned catchment method (but may be with a small radius: 10' to 15' may be). Personally, I prefer the last option.

Anyhow, whichever casting method is to be taken, I do think that buffing method needs a bit of a reworking.

Can you cast shield or SB on yourself when you are soloing?

Besides, it can easily get around the problem by keeping the traditional one-to-one casting buttions while adding a AoE-cast button as an optional extra to it.

And if technology allows, end will be calculated to the number of recipent - may be with a upper cap just in case. So it will cost one unit of end if just one recipent nearby; two units if two; and so on until max number is reached. (Edited: which is similar to what Edana suggested)

Great guide! Superb!

By the way, roughly speaking, which Alpha, and others incarnate slots, goes well with each pet set? Except Merc, I have one of each set. They are well-slotted and now I am working on their incarnates.

Thanks all!