Debug - Revision history

Exspes: /* Starting with a debug running = */

2021-05-08T17:19:55Z

Starting with a debug running =

← Older revision		Revision as of 17:19, 8 May 2021
Line 26:		Line 26:
	All output is in the mq2 window, not the mqlog.		All output is in the mq2 window, not the mqlog.

	= Starting with a debug running ==		= Starting with a debug running =

	Entropy can be started with 4 options. All 4 can be different debugs if needed.		Entropy can be started with 4 options. All 4 can be different debugs if needed.

Exspes: /* Options */

2021-05-08T17:19:40Z

Options

← Older revision		Revision as of 17:19, 8 May 2021
Line 19:		Line 19:
	Zone: area		Zone: area
	</pre>		</pre>
	So, to debug Xtarget Healing you would do <code>/debug heal xt<code><br/>		So, to debug Xtarget Healing you would do <code>/debug heal xt</code><br/>

	Debugs are not persistent. They reset to FALSE on a mac start/restart.		Debugs are not persistent. They reset to FALSE on a mac start/restart.

Exspes: /* Options */

2021-05-08T17:19:23Z

Options

← Older revision		Revision as of 17:19, 8 May 2021
Line 19:		Line 19:
	Zone: area		Zone: area
	</pre>		</pre>
	So, to debug Xtarget Healing you would do <code>/debug heal ~~xtM/~~code><br/>		So, to debug Xtarget Healing you would do <code>/debug heal xt<code><br/>

	Debugs are not persistent. They reset to FALSE on a mac start/restart.		Debugs are not persistent. They reset to FALSE on a mac start/restart.

	Some of them produce an excessive amount of output. Be prepared to provide screenshots.		Some of them produce an excessive amount of output. Be prepared to provide screenshots.
	All output is in the mq2 window, not the mqlog.		All output is in the mq2 window, not the mqlog.

	= Starting with a debug running ==		= Starting with a debug running ==

Exspes: Created page with "https://rubberduckdebugging.com/ Debugging in Entropy is very compartmentalized. Personally, I only want to see where I want to see. = Options =

 Buff: cb, ammo, beg..."

2021-05-08T17:18:52Z

Created page with "https://rubberduckdebugging.com/ Debugging in Entropy is very compartmentalized. Personally, I only want to see where I want to see. = Options = <pre> Buff: cb, ammo, beg..."

New page

https://rubberduckdebugging.com/

Debugging in Entropy is very compartmentalized. Personally, I only want to see where I want to see.

= Options =
<pre>
Buff: cb, ammo, beg, unity, aura, crew, buffself, shrink, poison, class, now, temp, bocked, buffgroup, buffraid, drop
Heal: cure, xt, group, pet, self, hurt, tot, dannet, rez
Move: face, tie, stick, stop, home, gtfo
Debuff: debuff, mez
Minion: petbuild, lost, sic, temp, heal
Cast: item, nuke, dot
Loot: loot
Mode: forage, drag, summon, petfarm, harvest, hunt, fish, farm, lush, trainskill, trainspell
Combat: def, target, melee, burn, agro, pull, misc, assist, decision, proc, ttl, sash, status, wait, hardstop, prediction
Other: rest, spire, glyph, fireworks, manarecover, fade, event, watch, tag, safe, intensity, chrwatch, staminarecover, inventoryscan, invis
Admin: build, observe, house, exit, sqledit, e3
Schema: init, s_zone, s_character, s_loot, s_nav, s_shared
Zone: area
</pre>
So, to debug Xtarget Healing you would do <code>/debug heal xtM/code><br/>

Debugs are not persistent. They reset to FALSE on a mac start/restart.

Some of them produce an excessive amount of output. Be prepared to provide screenshots.
All output is in the mq2 window, not the mqlog.

= Starting with a debug running ==

Entropy can be started with 4 options. All 4 can be different debugs if needed.

<code>/mac entropy\start.mac debug:invis debug:aura</code><br/>
Would start the mac with the debug on for the /invis command and aura buffing.