Macro rules need to change. Now.

I made a discord post about this, so I'll just paste it here.

Hello, if you are unaware of the recent boom in "technically legal macros" then you will agree with me. If you are unaware let me present my case.
There are a few clips and videos here that display how overpowered Macros can be. The Wynncraft rules state that "Macros are only allowed to be used to input a single 3-click spell command at a time or to automate chat commands such as the party system. Macros that loop or are designed to do anything else are not allowed as it gives you an unfair advantage. However, macros that loop melee attacks by keeping a mouse/keyboard button pressed down are allowed."

The important part there is "a single 3-click spell command at a time"

This used to be a non issue, with Wynntils having a relatively slow macro to assist anyone who didn't want lasting wrist damage, but recently there is a boom in "technically legal" macros. They allow players to either hold down a button or spam a single button at human speeds (6-12 cps) and have a spell be cast every single time. Recently Wynntils even allowed the holding down of a button to cause the macro to spam itself. This may be a bug, but it is essentially looping a macro. (This only happens when you bind the spell to a non mouse button, but since that is the default for Wynntils I can only assume it is intentional.
The rules on Mods is such: "Any modified client that gives you a gameplay advantage is hacking" which practically defines "technically legal" macros.

before I go further, I wanted to say that:
I use a single macro. I use a 1click=1spell macro for traveling with Charge because i dont want my hands to hurt.
I am not against all macros, only the ones that give players who use them an unfair advantage. I'm not a "click purist" even though I consider unfair macros cheating.

Here is my proposed rule alteration:
2. Macros

Macros are only allowed to be used to input a single 3-click spell command at a time or to automate chat commands such as the party system. Macros that loop or are designed to do anything else are not allowed as it gives you an unfair advantage. However, macros that loop melee attacks by keeping a mouse/keyboard button pressed down are allowed. All macros that can be used on Wynn cannot exceed 6 clicks per second.

If you need further convincing, here are some clips and videos of macros being unfair:
https://youtube.com/clip/UgkxRIovTs6pFFDu6If4IOSEYFbCw7K5IjDU

What macros + Arcanist looks like:
https://youtube.com/clip/UgkxJNUYuKC9eUWXw-ktNhmW-lEQAilr5fgP

My own clip of using the Wynntils macro to fly by holding down a single key and pressing left click once in a while:


If you see nothing else here, see this next video. Wynntils casts at roughly 40 cps when you hold down a button:

(I said "banned" here, I mean limited severely)

 

isnt cps capped at 1 per tick (20)

 

As a person who can only do 6cps, id just use the macro at that point lol

 

That's fair, however it would mean that someone who actually got good at casting spells at high cps would actually have higher dps than someone who simply uses macros. Players with average cps using macros that don't exceed average cps is perfectly fair, and I'm saying that as someone who never used macros.

 

this is a matter worth attention so it's good you're bringing it up

this is not a solution however.
and you should give me another poll option that lets me disagree

the brickwall solution currently is changing the input limit on the server. Doing so would have its own downsides that might affect everyone if its not added into the game 100% perfectly (possible input delay, packet loss, etc).
R-R-R has an input speed cap limitation if you didnt already notice, which may be purposely coded in or simply a Minecraft limitation. Whether this could be applied to left click is another question, but it may just be the simple solution (assuming it isnt a MC problem)


Now you're already getting pretty excited about this whole thing, but I'm not really too alarmed by it.

Currently the only class that really takes advantage of the macro shenanigans is Riftwalker and Arcanist. Dubbed "Macromage", you can sustain infinite spells at ludicrous speeds with zero mana consequences. You even listed a video from one of the lead contributors to its current publicity! Personally, I think it's hilarious. The fact that an absolutely mid class like Riftwalker now has 1mil+ dps options is insane!!

but for every other class..?


Speedy spell spam macros do not really contribute to any other class in Wynncraft, bar Charge Spam Warrior.


-Assassin is mostly controlled, minus Trickster, which has some dumb stuff you can do with Spin Attack and Weightless. Mana Sustain would still be an issue at the speeds capable from macros

-Already talked about Warrior. Other than Charge Spam, it doesn't really benefit outside of the possibly funny shenanigans that would involve charging Sacred Surge; Mana Sustain would still be an issue at the speeds capable from macros lol

-Shaman doesnt care about spell spamming any faster. otherwise Panic Zealot would be cool.

-Archer, maybe? There might be some include macro spell cycles you could do involving some Boltslinger sustain options that fully utilize Recycling. That would become a server TPS issue and the build sounds like it would also be a hella hassle. requires more brainstorming.
the other archetypes dont benefit from insane spellspam. Mana Sustain would still be an issue at the speeds capable from macros

-I do not need to talk about Light Bender


Wynncraft's class and ability system is designed well enough for this not really to be too insane of a complication. Mage, a class that should benefit the most from fastest spell spamming, DOES benefit from this, and this only works for Mage because of Manastorm. Replace Manastorm and you will suddenly care a whole lot less about insane macro spell spam potential.

I'm not arguing for it, but rather pointing out it's not that big of a deal. Surely not one big enough to warrant rule changing and adding yet another thing for the Staff to be on the lookout for lol

 

where's the "how about no" option

sure artemis macro goes crazy but just patch it to not be a machine gun on hold and nobody will care

 

yeah, ik.

 

I don't know how the packets and server backend work but the minecraft client can handle more than one click per keybinding per tick

 

did you mean "if you are aware"? lol

 

Personally, I just made my own macros with up to 20 cps (if I go any further some clicks don’t register, probably because of ping/lag, so I often use 12 cps ones) and put 2 spells at a time at the side buttons of my mouse just so my hands don’t get tired. I don’t have a max level mage so idk about that, but on my assassin and archer it really doesn’t make that much of a difference in spell casting speed since even with trickstrobat weightless doesn’t give enough mana back to sustain a 4 spell/second cycle of spin and dash and acrobat loses damage if you spam multihit because of fatality. Archer also runs out of mana really fast with bomb bomb storm cycle. In my eyes it is more of a convenience for flying with assassin/warrior and long fights instead of a gamebreaking dps boost

 

Why not just nerf mana sustain instead of changing the rules.

 

NO
its bad enough as it is

 

Skill issue.

 

not skill issue

 

How come I never run out of mana then.

 

i kinda agree, cuz like i liked the old wynntils thing with a cooldown, it helped with not messing up strict upper surfing combos, but now it just goes super fast, kinda feel like its past the line on unfair advantages honestly, which is where the line should be drawn. it shouldnt be a massive benefit to mod, it should just be assisting

 

Solution: change wynncraft so that instead of three clicks to cast a spell you can just use swap key, drop key, pick block key, etc

 

:skull: id be even worse at spell combos lolol

 

I meant like one of those keys per spell. So it would be just like wynntils but in vanilla.

 

how the living hell did you read this thread and have "nerf mana sustain" as your takeaway? that has nothing to do with macro inputs at all.