What is your problem? How do I update to latest macro without breaking anything? What did you do to cause the problem? I almost broke my macromod on ECC. What happened? See above. What should have happened? ECC macros should have not almost exploded. (Mainly the question is, how do I solve the problem?" <Pre-made tag to alert @314 of the report>
helo i am from 'PMC' and i would liek op ty memes aside, these are really cool, I'll have to download them when my internet is back to normal.
I love the idea of a macro switching automatically tool according to what your looking at. But personally, I would not use that in mining, because it might interfere with the equipment of a sword when in combat with a mob. But it can be very useful in a demolition. I will probably modify it and make it toggle-able.
just copy and replace whatever file was updated (commands.txt is most of the time updated after every time) The updates (Which 314 posts on the thread) say what files were changed, so just copy and replace
Would this need a new module, or would it fit an existing one? If yes, which? What is your idea? My suggestion would be added to the mining module. When I mine, I frequently: Repair my tools Smelt my ores Sell my ores (/sell goldi | /sell ironi | /sell diamond | etc) Sell my junk to keep inventory clean (/sell dirt | /sell sand | /sell diorite | etc)\ Why do you think it should be added? I suggest these commands are bound to the "z, x, c, v" keys (or something similar.. maybe automated) so that mining is as close to automated as it can be (legally). For example, when mining you would simply press z (repair tools), x (sell junk), c (smelt ores), and v (sell ores) in that order to clear your inventory instead of being forced to type a long list of commands. Of course these functions would require many donation features, but the mining module is designed for users who own an efficiency 7 pick and I would imagine the majority of the eff7 users have these features. These functions would also take a bit more for users to add, but of course they would be totally optional. @314
I am slightly busy at the moment so I am not sure how soon I can include it into the PMC... but for the keybinds, just add: Repair all: Code: /repair all (No macro file needed, just the keybind) Smelt all: Code: /smeltall (No macro file needed, just the keybind) Sell valuables: Code: $${ ECHO("/sell coal") WAIT(1000ms) ECHO("/sell iingot") WAIT(1000ms) ECHO("/sell gingot") WAIT(1000ms) ECHO("/sell lapis") WAIT(1000ms) ECHO("/sell redstone") WAIT(1000ms) ECHO("/sell diamond") }$$ Sell leftovers: Code: $${ ECHO("/sell stone") WAIT(1000ms) ECHO("/sell granite") WAIT(1000ms) ECHO("/sell diorite") WAIT(1000ms) ECHO("/sell andesite") WAIT(1000ms) ECHO("/sell dirt") WAIT(1000ms) ECHO("/sell gravel") }$$ WAIT() added to prevent an automated kick for spamming. Including these into an automated loop would conflict with the tool switcher - I, personally, have found that the EXECUTE() command does not help with this problem while others reported it does... ._.
Oh, I had already written exactly what you put here. I was just suggesting it because it helped me so much I wanted others to have it as well.
I'll see whether I can find a way to fix EXECUTE(), then I might be able to include a loop command for everybody. ^_^
Would this need a new module, or would it fit an existing one? If yes, which? It would fit within ToolSwitch. What is your idea? Add a section for a Sword, where hitid = Zombie, Skele, etc (whatever the proper ids are). Assuming such a thing exists of course. I'm newer to MC, so not sure that will work? Why do you think it should be added? Having to type /, then backspace, then .tool to be able to equip a weapon is slow. I'm sure there's a way to macro it, but why not extend the ToolSwitch module to rock more. <Pre-made tag to alert @314 of the suggestion>
@314 if you're busy I can get this update out by tomorrow that @Torzon wanted (Anyone know if HITID works with mobs? If not, what other var works?)
That is the problem, I don't think hitids work for entities and I don't know what could be used instead.
