@user202729 Well, I;m not answering the challenge anymore (don't understand most sequences), so should be able to get the answers fixed (with a bit of help). Of course, if the next answer is difficult (but not insanely difficult), then that gives us ample time to fix them
Hehe, about 50% of my total edits are on answers on this challenge :P
the plan is to change its bytecount and then do the new sequence in the same language and bytecount and replace the next answer, which happens to be your Husk answer
@Mr.Xcoder Kinda. We're changing the byte count for Nie's Emojicode answer, which is the one before your first Husk answer. So we need to change your Husk answer to calculate the new sequence, while keeping it at 29 bytes
@cairdcoinheringaahing Question: If Nie changes the sequence, can I change the language too (use something other than Husk, while not affecting the byte count)?