The First Type of AutoSoup Macro's are based on third party macro software.
'heart' condition. Advantage(s):
- This type AutoSoup can not be detected by No Cheat Mods as they are running as a third party application.
- They cannot be paused but they can be terminated quickly.
- They perform a better copy and paste text function than other mods for chatting.
- 'Autosword' can be coded and performed by placing a sword or weapon in hotkey position 1.
- Because these are third party software there no incompatibilities issues from past, current or future releases of Minecraft versions; unless instasoup is incompatible with future releases :-(.
- No increase in Lag as a result of the macro*.
- The AutoSoup Script file can be mobile (backed up) and given to others to use.
Disadvantage(s):
- They are dependent on an external script to work. Hence, they NEED to be turned on!! Don't forget!!!
- These macro's are actually semi-autonomous. They need an input from either a pressed or held down keybind during battle. Hence, the player needs another button.
- They are measurably slower than the other AutoSoup's. This is because the program 'sends' the commands via Keystrokes.
- "The Dropped Sword" glitch occurs when (1) you lower the sleep (delay) time below 200ms in the script file and the server receives lag or (2) you accidentally press the wheel mouse scroll during battle.
- The player is susceptible to kits** that switch the position of the the sword from hotkey position 1.
- During massive lag on servers, spamming the keybinds will have no effect on starting the AutoSoup.
Review:
- Use these Automation software if you really have to. Use AutoSoup Mods and other macros if you can.
Example #1: MacroSoup using AutoHotkey
Description:
Here is the example for MacroSouping; which is one better than manual souping. Negative: you run out of soup quick as you spam the keybind during battle; unnecessarily consuming soup even if you take 1 hit point damage! Another negative is the empty bowls left in the hotkey serving no purpose.
Source Code:
~LShift:: ;THIS IS THE KEYBIND TO MACRO SOUP
Send {3}
Sleep 100
Send {RButton} {1}
Send {4}
Sleep 100
Send {RButton} {1}
Send {5}
Sleep 100
Send {RButton} {1}
Send {6}
Sleep 100
Send {RButton} {1}
Send {7}
Sleep 100
Send {RButton} {1}
Send {8}
Sleep 100
Send {RButton} {1}
Send {9}
Sleep 100
Send {RButton} {1}
return
~s::ExitApp ;THIS IS THE KEYBIND TO TERMINATE THE MACRO
Example #2: MacroSoup with FastDrop (bowl dropping).
Description:
... And here's one better with FastDrop with every consumption of a soup. Positive: FastDropping the emptied bowls allows you to quickly refill with soup from your inventory. Negative: Same problems with macrosouping. In combination with server lag in SMP, the sword may more commonly drop accidentally using this macro.
Example #3: AutoSoup with ImageSearch.
Description:
Finally, we reach a working AutoSoup. With a pressed down keybind, the macro will shoot when the health bar reaches below
Overall, I would not recommend this type of AutoSoup macro.
Example #4: AutoSoup with PixelGetColor.
Description:
This is where AutoHotkey works it's magic. By searching for a single pixel colour on the screen, you can use a binary algorithm for the AutoSoup to detect if your hearts reaches below
Positive: No more dependencies on an external .bmp, .jpg or .png file. It is fairly sensitive so it works on any chunk. Negative: You still have to press-hold a keybind to 'check' if you hit points is below the threshold.
Example #5: Finalised AutoSoup.
Description:
Lastly, here is an AutoSoup that runs completely autonomously so long as the macro file is executed.It can still utilise manually keybind input to 'check' if the health is below a certain hit point. Hotkey Slot 1 is reserved for the AutoSword function and Hotkey Slot 2 is reserved for a compass to find/track other players in SMP server games. The key to this AutoSoup than from Example 4 is the inclusion of the PixelGetColor function at every souping step. Each time the player's hearts is below 6, a soup will be consumed, but it will also check if the hearts has been healed above the level. It is above 6 hearts, it will loop back to the standby step. Also, because this is a true AutoSoup, you can now place more emphasise in concentrating in pvp battles.
.
Positive: It works! No more pressing or holding down keybinds. Technically, this is not just an AutoSoup macro but also a AutoSplash Potion as well. If you have Healing Splash Potion(s), this macro will heal the player so long as you are have healing splash potion(s) in the hotkey and pointing downwards. If you have Negative Splash Potion(s) (instant damage, weakness, slowness), this macro will cast a negative effect on other player(s) so long as you have that potion in the hotkey and pointing towards them. Negative: .It still needs to be alligned with the defaulted loaded screen. Just make sure you don't move it. It does not include quickdropping, but this is to reduce errors and the dropped sword glitch. Lighting still is a factor for the AutoSoup to work since it searches for colour of a single pixel (no way around it). So don't expect this work while underground or in a cave!
P.S I have also coded an AutoSprint as well. "Run, Forest... Run...."
Overall, it works but it is still constrained in not auto-refilling, quickdropping, or crafting more soup. AutoHotkey simply can not performed these tasks without some massive delays or errors.
.... which is why we introduce.... Gen 2: Refilling and QuickDrop....
References:
- Gray, Chris Mallett; Steve. (2013). AutoHotkey. 1.1.13.01. Retrieved 11 October 2013, 2013, from http://www.autohotkey.com/
** An example of such a kit is in SMP gamers, such as minecraftpvp with the free Monk Kit which is capable of randomly switching items from the hotkey and inventory when the player attacks with a Monk rod.
No comments:
Post a Comment