MacroQuest64

Singing_Fool_29 wrote:As my first post here, hello everyone.

Singing_Fool_29 wrote:I've been reading the MQ2 messageboard for about a week looking also at the manual and the WIKI, as well as studying how commands work and also the best methods of macro non-detection.

Singing_Fool_29 wrote:The ideas of what to do and what not to do seem to be scattered all over the board. If I missed a specific thread or manual addition, then I apologize. If such a thing did not exist would it be entirely possible to add that?

Singing_Fool_29 wrote:My ideas for macro building center entirely around authentic keypressing. I would like to do the following with my code:

1)Build macros that randomize anchor points and return points.

Singing_Fool_29 wrote:2)Characters that instead of facing fast use the standard EQ turn keys until they have line of sight, and then checking if they are too far away. Something like:

/if (!LineOfSight[me.x, me.y, me.z : target.x, target.y, target.z]){
/keypress left
}
/if ((LineOfSight[me.x, me.y, me.z : target.x, target.y, target.z]) && (TargetFar == "true")){
/keypress forward
}
** this way the character only turns or moves during combat if it's flagged "cannot see target" or "too far away". It's a little generic but a rough idea of what I was thinking of.

Singing_Fool_29 wrote:3)Characters that only respond to local events such as fizzle, enrage, target too far away, etc. I don't want to depend on commands or stuff that has to be given from myself ingame. I'd like to automate my characters as much as possible within means of non-detection.

Singing_Fool_29 wrote:In asking for help I am really just trying to get some input from seasoned users into whats acceptable and what commands are really high risk of being caught. Also what kind of ingame behavior is a risk of getting caught(not trivial stuff, just things new people would be unaware of, like the /report issue). If at all possible for me to just emulate socials and do all of my work off of natural client recieved information, then so be it.

If you don't want to get caught, don't use blatant hacks. 90% of what you get from the standard MQ package is all but undetectable to SOE, and 90% of the bullshit you hear on other forums of SOE "cracking down" on MQ2 users is exactly that, bullshit.

Singing_Fool_29 wrote:To be more specific, I 6-box. I'd like to automate the actions of my casters and tanks, while I control and pull with my enchanter.

For the moment I would like to focus my energy on the melee bot(s) and what routines would need to be constantly checked. I would like to construct it entirely around true and false statements which determine subroutine actions.

			/if (AUTO_ATTACK_MOBS && ${Me.Class.Name.Equal[Warrior]}) {
				/varset SpawnId ${Spawn[npc radius 40].ID}
				/i msg IRC_CHANNEL ##### MOB HERE !!!! AUTOATTACKING
				/i msg IRC_CHANNEL ASSIST ${Zone.ID} ${SpawnId}
				/call HandleAssistCall ${SpawnId}
			}

|Usage: Leader character use hotkey: /i msg #channel ASSIST ${Zone.ID} ${Spawn.ID}
#event HANDLE_ASSIST "<#1#> ASSIST #2# #3#"
Sub Event_HANDLE_ASSIST(string Line, string Sender, int ZoneId, int SpawnId)

	/if (!${Ini[INI_FILE, BotNet, ${Sender}, NOT_FOUND]}) {
		/i msg IRC_CHANNEL # IGNORING REQUEST!
		/return
	}
	/if (${Zone.ID} == ${ZoneId}) {
		/call HandleAssistCall ${SpawnId}
	}
/return

Sub HandleAssistCall(int SpawnId)

	/if (${Me.Sitting}) {
		|standing up on inc
		/delay ${Math.Calc[${Math.Rand[10]}+1]}
		/if (${Me.Sitting}) /stand
	}
	
	/if (${Me.Class.Name.Equal[Druid]}) {
		/call HandleAssistCallDruid ${SpawnId}
		/return
	}

	/if (${Me.Class.Name.Equal[Cleric]}) {
		/call HandleAssistCallCleric ${SpawnId}
		/return
	}

	|add more classes here..
/return

A_Druid_00 wrote:Technically you don't need a global string variable. A variable already exists that calculates your Heading To a target. So you check your headingto the target, and if you're not +/-XX degrees, then turn towards it.

use the code as u want, just posting to give you some hints on how you _could_ do this

Singing_Fool_29 wrote:Thanks!

I really like it but I'm wondering where the activation comes into play. Do you have to set another if statement if it finds a spawnID within the specified radius?

	/if (${Spawn[npc radius 40].ID} && ${Spawn[npc radius 40].LineOfSight}) {
		/call CheckNeutralZone
		/if (!${Macro.Return}) {

			/if (AUTO_ATTACK_MOBS && ${Me.Class.Name.Equal[Warrior]}) {
				/varset SpawnId ${Spawn[npc radius 40].ID}
				/i msg IRC_CHANNEL ##### MOB HERE !!!! AUTOATTACKING
				/i msg IRC_CHANNEL ASSIST ${Zone.ID} ${SpawnId}
				/call HandleAssistCall ${SpawnId}
			}
		}
	}