Minecraft Forums

Quote from Mumfrey

I know what you're saying, but any behaviour you're seeing as a result of using the incorrect methods is resulting from a bug or quirk in the way minecraft handles the key bindings and is not by design, therefore I won't add support for it because it's not good to encourage use of bugs - they may or may not be removed or fixed without notice.

I already said above that I will add support for passing variables into those functions so why is this still an issue? I didn't post all that information above to be obstructive, it's just the way Minecraft works and I was trying to explain it clearly (since there are literally zero sources anywhere else on the web that will provide this info) because without reading the Minecraft source it's hard to grasp.

So, yes to adding support for var passing, but no to adding any kind of support for controlling trigger keys with stateful commands.

Quote from Gluzz

I have tried so very long to make it that when I press w I start sprinting, and when I let go of it I stop sprinting but I can't seem to get it. If anyone knows how to do this please let me know. the hard part is that it like overlaps with normal forward key and I don't know how to make it so I don't have to press any other buttons besides w.

$${keydown(forward);sprint();}$$

Quote from MeepDarknessMeep

Is there a reason this won't work? I mean the exec. It won't work no matter what.

OnChat:

IF(PLAYER=MeepDarknessMeep)
EXEC(MeepsProtection.txt)
IFMATCHES(%@&textperson%,Meepcasino)
EXEC(casino.txt)
ENDIF;
ENDIF;

Full onchat:

SET(@&nameperson,"")
SET(@&chatperson,"")
SET(@&titleperson,"")
SET(@&clanperson,"")
IFMATCHES(%CHATCLEAN%,"\[(.+)\]\[(.+)\] (.+): (.+)")
MATCH(%CHATCLEAN%,"\[(.+)\]\[(.+)\] (.+): (.+)",@&clanperson,1)
MATCH(%CHATCLEAN%,"\[(.+)\]\[(.+)\] (.+): (.+)",@&titleperson,2)
MATCH(%CHATCLEAN%,"\[(.+)\]\[(.+)\] (.+): (.+)",@&nameperson,3)
MATCH(%CHATCLEAN%,"\[(.+)\]\[(.+)\] (.+): (.+)",@&textperson,4)
ELSE;
IFMATCHES(%CHATCLEAN%,"\[(.+)\]\[(.+)\](.+): (.+)")
MATCH(%CHATCLEAN%,"\[(.+)\]\[(.+)\](.+): (.+)",@&clanperson,1)
MATCH(%CHATCLEAN%,"\[(.+)\]\[(.+)\](.+): (.+)",@&titleperson,2)
MATCH(%CHATCLEAN%,"\[(.+)\]\[(.+)\](.+): (.+)",@&nameperson,3)
MATCH(%CHATCLEAN%,"\[(.+)\]\[(.+)\](.+): (.+)",@&textperson,4)
ELSE;
IFMATCHES(%CHATCLEAN%,\[(.+)\]\[(.+)\] (.+) : (.+))
MATCH(%CHATCLEAN%,\[(.+)\]\[(.+)\] (.+) : (.+),@&clanperson,1)
MATCH(%CHATCLEAN%,\[(.+)\]\[(.+)\] (.+) : (.+),@&titleperson,2)
MATCH(%CHATCLEAN%,\[(.+)\]\[(.+)\] (.+) : (.+),@&nameperson,3)
MATCH(%CHATCLEAN%,\[(.+)\]\[(.+)\] (.+) : (.+),@&textperson,4)
ELSE;
IFMATCHES(%CHATCLEAN%,\[(.+)\]\[(.+)\](.+) : (.+))
MATCH(%CHATCLEAN%,\[(.+)\]\[(.+)\](.+) : (.+),@&clanperson,1)
MATCH(%CHATCLEAN%,\[(.+)\]\[(.+)\](.+) : (.+),@&titleperson,2)
MATCH(%CHATCLEAN%,\[(.+)\]\[(.+)\](.+) : (.+),@&nameperson,3)
MATCH(%CHATCLEAN%,\[(.+)\]\[(.+)\](.+) : (.+),@&textperson,4)
LOG(TEST!)
ELSE;
IFMATCHES(%CHATCLEAN%,\[(.+)\] (.+) : (.+))
MATCH(%CHATCLEAN%,\[(.+)\] (.+) : (.+),@&titleperson,1)
MATCH(%CHATCLEAN%,\[(.+)\] (.+) : (.+),@&nameperson,2)
MATCH(%CHATCLEAN%,\[(.+)\] (.+) : (.+),@&textperson,3)
SET(@&clanperson,"")
ELSE;
IFMATCHES(%CHATCLEAN%,\[(.+)\](.+) : (.+))
MATCH(%CHATCLEAN%,\[(.+)\](.+) : (.+),@&clanperson,1)
MATCH(%CHATCLEAN%,\[(.+)\](.+) : (.+),@&nameperson,2)
MATCH(%CHATCLEAN%,\[(.+)\](.+) : (.+),@&textperson,3)
SET(@&titleperson,"")
ELSE;
IFMATCHES(%CHATCLEAN%,(.+) : (.+))
MATCH(%CHATCLEAN%,(.+) : (.+),@&nameperson,1)
MATCH(%CHATCLEAN%,(.+) : (.+),@&textperson,2)
SET(@&clanperson,"")
SET(@&titleperson,"")
ELSE
IFMATCHES(%CHATCLEAN%,\[(.+)\] (.+): (.+))
MATCH(%CHATCLEAN%,\[(.+)\] (.+): (.+),@&titleperson,1)
MATCH(%CHATCLEAN%,\[(.+)\] (.+): (.+),@&nameperson,2)
MATCH(%CHATCLEAN%,\[(.+)\] (.+): (.+),@&textperson,3)
SET(@&clanperson,"")
ELSE
IFMATCHES(%CHATCLEAN%,\[(.+)\](.+): (.+))
MATCH(%CHATCLEAN%,\[(.+)\](.+): (.+),@&clanperson,1)
MATCH(%CHATCLEAN%,\[(.+)\](.+): (.+),@&nameperson,2)
MATCH(%CHATCLEAN%,\[(.+)\](.+): (.+),@&textperson,3)
SET(@&titleperson,"")
ELSE
IFMATCHES(%CHATCLEAN%,(.+): (.+))
MATCH((.+): (.+),@&nameperson,1)
MATCH((.+): (.+),@&textperson,2)
SET(@&titleperson,"")
SET(@&clanperson,"")
ENDIF;
ENDIF;
ENDIF;
ENDIF;
ENDIF;
ENDIF;
ENDIF;
ENDIF;
ENDIF;
ENDIF;
IF(PLAYER=MeepDarknessMeep)
EXEC(MeepsProtection.txt)
IFMATCHES(%@&textperson%,Meepcasino)
EXEC(casino.txt)
ENDIF;
ENDIF;
$$<capture.txt>
SET(@&chat2,%@&chat1%)
Set(@&chat1,%CHAT%)
SET(@&chatclean2,%@&chatclean1%)
Set(@&chatclean1,%CHATCLEAN%)
//SET(@&chatclean,%CHATCLEAN%)
//IFMATCHES(%CHATCLEAN%, Meepmath:)
// LOG(Running math.)
// EXEC(Meepmath.txt)
//ENDIF;
//IFMATCHES(%CHATCLEAN%, MeepDarknessMeep: Meepvote:)
// LOG(Running vote.)
// EXEC(MeepVote.txt)
//ENDIF;

IFMATCHES(%CHATCLEAN%,^\[Shop\] (.+) sold 1 (.+) for (.+) Syna to you)
MATCH(%CHATCLEAN%,^\[Shop\] (.+) sold 1 (.+) for (.+) Syna to you,@&playerwhosold,1)
MATCH(%CHATCLEAN%,^\[Shop\] (.+) sold 1 (.+) for (.+) Syna to you,@&soldwhat,2)
MATCH(%CHATCLEAN%,^\[Shop\] (.+) sold 1 (.+) for (.+) Syna to you,@&howmuch,3)
LOG(%@&playerwhosold% sold %@&soldwhat% for %@&howmuch%)
ENDIF;
IFMATCHES(%CHATCLEAN%,"%@&nametotroll%:");IFMATCHES(%CHATCLEAN%,%@&quallen2010%);ECHO(%@&responder%);ENDIF;ENDIF;

EXEC(MeepsProtection.txt,protection)

Quote from 66jarjar66

I'm making a macro that auto-feeds me with baked potatoes when my health gets under 14. I am trying to set the inventory slot so that it goes back to the original item held when done eating, but the slot stays the same as the food! Any fix?

if(HUNGER<15);
set(#slot,%invslot%);
pick(393);
if(ITEM=393);
do(38)
key(use);
loop;
slot(#slot);
endif;
endif;

Quote from Zelfana

Man, the looping works correctly, you just can't put any waits in there as the loop itself takes one tick and you have to call the key every tick for it to work for things that require holding it.

DO(35);
KEY(use);
LOOP;

That would eat one piece of food as it takes 1.5 seconds to eat and there are 20 ticks in a second.


For placing blocks and the like I know what you're saying but that's how Minecraft handles trigger keys so that you don't accidentally spam blocks everywhere. Minecraft itself does the waits between the actions there, other uses of use key work like that loop. In a macro that's not necessary as you can call exactly one key use accurately and only get one block placed. If you need different functionality for different actions you need to make different macros. Not really much else to it. Besides, only block placement works differently, everything else works with the loop like it should.

EDIT: Actually throwable things also works sparingly but the reason is same as block placement.

Attack key has similar things as holding it is meant for mining and clicking single times meant for attacking. That's why they are trigger keys.

Quote from Zelfana

Yeah, that's the only way to get it to work like it does normally. You are replacing your normal keys with macros?

Quote from Zelfana

It is supposed to work like that really. I don't think there is any other "right" way to do it besides having a virtual keybinding that wouldn't have to be on your keyboard and you can configure that in MC's config file manually. Minecraft only supports single keybindings for actions so unless you could bind more than one key for an action the way you have done it is the easiest and basically only way to get the normal functionality without excessive macros.

These kind of problems are one reason to not replace your normal keys with macros. I still have keys open for bindings on my keyboard and will keep normal keys like they are. Except I changed sneak to control because shift+F3 and some other uses of shift. I have a macro for planting crops and the like but it doesn't require me to hold any buttons and I only need to move around. It is faster than the normal holding of right click and removes the unnecessary calls for use so that no accidents happen like flipping levers if you hold the button.

Quote from MegaSniperB

Are you trying to troll him? I don't think you are fully understanding what he is trying to say and you've made a simple yes I can add this to the mod into a 3 page post between you two arguing.

IF(@#aa < 1)
 IF(~CTRL)
  SET(@#aa,2)
 ELSE
  SET(@#aa,1)
 ENDIF;
ELSE;
 SET(@#aa,0)
ENDIF;

Quote from Mumfrey

Good grief, I'm busy for a couple of days doing updates and come back to defense condition 1 between two thread regulars.

[snip]

It's possible, but it's far from trivial for a number of reasons. I won't be adding support for trigger bindings to KEYUP and KEYDOWN, but I *might* add some lower-level commands of the order of PRESS and TYPE that can simulate key up and key down at a lower level.

See, it's hard at times to know where to pitch functionality in terms of how far removed it is from the game mechanics. In general I tend to err on the side of making the commands fairly "raw" since it gives users the most control, but always add a layer of cotton wool so that in theory macros can't affect the state of the game in a way that ordinary interaction couldn't.

The different commands that are there exist to complement and provide access to the different underlying concepts of the key bindings, and while this may seem non-sensical because holding down a key is such a simple concept and why should it be so hard, the reality is that it's a complex system underlying the game and interacting with it needs an appropriate, scaled level of complexity so that the user can appreciate what they are doing and work smarter because of it. I provided that lengthy explanation above so that you could hopefully gain a better understanding of what's going on under the bonnet and see where the difficulties lie.

[snip]

Development of CRAFT took weeks, I've just spent the last few dealing with the (what would appear to the outside observer to be simple) situation with being able to use the slot manipulation functions in the creative GUI, and what you're asking is a similar proposition. So whilst I can add it to the wish list, it's just not feasible in the short term especially factoring in that you can already do what you want using existing mechanisms.

So, added to wish list.

[snip

Can you not achieve this by putting the complex behaviour in the KEY DOWN handler and just putting $${KEY(use)}$$ in the KEY HELD handler with a repeat of 1 ticks?


See above, the short answer is "yes, but not in the near term".

Quote from Mumfrey

It's possible, but it's far from trivial for a number of reasons. I won't be adding support for trigger bindings to KEYUP and KEYDOWN, but I *might* add some lower-level commands of the order of PRESS and TYPE that can simulate key up and key down at a lower level.

See, it's hard at times to know where to pitch functionality in terms of how far removed it is from the game mechanics. In general I tend to err on the side of making the commands fairly "raw" since it gives users the most control, but always add a layer of cotton wool so that in theory macros can't affect the state of the game in a way that ordinary interaction couldn't.

The different commands that are there exist to complement and provide access to the different underlying concepts of the key bindings, and while this may seem non-sensical because holding down a key is such a simple concept and why should it be so hard, the reality is that it's a complex system underlying the game and interacting with it needs an appropriate, scaled level of complexity so that the user can appreciate what they are doing and work smarter because of it. I provided that lengthy explanation above so that you could hopefully gain a better understanding of what's going on under the bonnet and see where the difficulties lie.

Quote from Mumfrey

Not sure, what are you attempting to do? Theoretically it should set it to 1 if it's zero and CTRL was not pressed when invoking the macro.

*hits f*
...
*hits f*
0
0