I am almost inclined to make another account just to hit i like this a second time. But could i have something with more muscle pretty pls? Otherwise great job. Youre a saint.
(This is a joke)
When I saw that we were going from Broil III at 290 potency in ShB to Broil IV at 295 potency in EW, I was shaking with how excited I was. I couldn't believe they were so generous with a whole 5 potency. I'm going to probably scream in excitement when 7.0 comes out and Broil V hits 300 potency, playing SCH going to be WILD once it hits 300!!!
You risk getting reported for spam, as fun as they can be, quite a few of them can be found offending as well.
I encountered a whm with a text macro for each time they put regen on someone last week in msq roulette…
I saw an astrologian in leveling roulette once who had different Yugioh macros for every single card action.
They got kicked as soon as possible because it was so bloody annoying.
In my opinion, I think the best solution to duplicate raises is that a dead player can only have one raise effect at a time, and any other similar effects are not applied/refunded to avoid waste resources and double work.
Raise macros should be bannable behavior.
I've encountered one or 2 that were genuinely brilliant, so I definitely fall into "they had their time, no longer needed and you're probably not as funny as you think you are" camp.
That being said- if this becomes a bannable offense, why not start banning other (potentially) annoying uses of macros ? It starts to become rather difficult to know where to draw the line.
I would rather implement design improvements, perhaps as a previous poster suggested, it could be effects (such as sparkly feathers) that would show when a raise has been placed on someone. That might not solve the issue, but I'm a bit of an optimist - I would hope that after enough times of someone saying the equivalent of "hey Jack- are you blind- can't you see the feathers on Jill?" Jack is going to stop with the raise macro and start looking for sparkly feathers first.
Frankly I can ignore raise macros regardless how annoying...unless they tact on annoying SEs on them. Don't do this. If you MUST have a raise macro...keep it simple. A good example being "Raising <t>". No SEs.
When you deal with human beings, never count on logic or consistency.
Fluid like water. Smooth like silk. Pepperoni like pizza.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.