BJ Scripts / Encounter Assistant

Set up your team.
Know what to expect.

An illustrated guide to configuration and everyday use.

Follow the path from your first EA launch to a coordinated encounter. Learn which controls to use, how to reach characters on other computers, and what to check before sending a setup.

EA 1.79 · Guide reviewed October 26, 2026

  1. 1Load & connectEA on every session. OgreIRC across computers.
  2. 2Choose & assignThe right encounter, tags and group roles.
  3. 3Send & observeRead the reports and resolve setup warnings.

Load EA on every session

Start with a working EverQuest II session in Inner Space, the required extensions, and an OgreBot profile that can run your character. Encounter Assistant supplies encounter-specific behavior alongside OgreBot.

Load the required tools in every game session
Figure 1. Load the required tools in every game session.
  1. Install and update the required tools.

    Use your normal installation/update process for Inner Space, ISXEQ2, ISXOgre/OgreBot and BJ Scripts / ISXBJEQ2. Install a matching EA release on every participating computer. This guide assumes those products are already installed and accessible.

  2. Start OgreBot and select the intended profile.

    Check abilities, normal healing and combat settings before applying an encounter setup. For tank recovery, keep the character’s Ogre ability export current. Check encounter notes for required equipment and consumables.

  3. Launch Encounter Assistant in each game session.

    With the standard script layout installed, enter this in the Inner Space console:

    Local command · repeat in each session

    BJ EA

    To stop Encounter Assistant, enter BJ End EA in the InnerSpace console.

    EA initializes BJ Helper and Ogre utilities, loads a group role, and checks the current zone for encounter coding. Allow initialization to finish.

Installed build matters. The normal launcher uses the EA build supplied through ISXBJEQ2. Copying edited source files alone does not replace that packaged build. After an update, reload EA on every participating session.

Check before continuing: EA has loaded without a helper-startup error, and the console reports a group role. A zone with no encounter coding can still be used to check startup.

The pictures in this guide are original teaching illustrations based on the controls and behavior in the source. They use generic roles and sample times. They are not gameplay screenshots; skins and window sizes can vary.

Connect the whole team with OgreIRC

Every computer needs the same communication path. EA receives setup messages locally and each character responds according to its own tags, group and encounter state.

OgreIRC connects the team across computers
Figure 2. OgreIRC connects the team across computers.
  1. Open the OgreIRC connection settings supplied by your Ogre installation.

    Configure the connection on each computer. Use the connection details supplied for your team; no account, server or channel values are prescribed here.

  2. Match the shared fields.

    The IRC host, port, channel and any required server/channel passwords must agree with the connection your team uses. Use a distinct IRC nickname/user for each simultaneous connection and the correct local uplink identity.

  3. Save, connect and check all participants.

    Use your installed OgreIRC controls to connect each computer and make its local sessions available. Confirm every intended participant is connected before sending an encounter setup. Changing EA’s send destination does not establish the IRC connection.

  4. Use Send to Ogre IRC in the EA selector.

    After the team is prepared, confirm that a client on each computer receives the setup and begins its assigned behavior. A response on the sending computer alone does not verify the other computers.

Silent Mode is not a network connection. Silent Group/Raid sends use a relay and must not be relied on to reach characters on other computers. The OgreIRC branch sends through IRC whether or not Silent Mode is checked.

Check before continuing: all participating computers are connected to the shared OgreIRC channel, with OgreBot and EA running in their local sessions.

Open and use the setup selector

Enter the intended instance first. The selector’s list is built for the current zone and available access, so it will not show the whole encounter catalog at once.

While EA is running, this local Inner Space console command opens the selector:

LavishScript:ExecuteAtom[a_EA_ShowSetUpForUISelector]
  1. Left-click the exact setup message.

    Match the encounter and mode in the coverage catalog. Keep the exact EA setup name as listed.

  2. Click Info and review the encounter notes.

    Info requests the selected entry’s available in-game help. For a full checklist of required tags, items and limitations, also read its catalog entry. Some utility or legacy entries have little or no Info text.

  3. Select Send to Ogre IRC.

    Group, Raid and OgreIRC are mutually exclusive choices. The window initially defaults to Send to Group with Silent Mode enabled, so explicitly check the destination.

  4. Prepare the team, then click Send.

    Send dispatches the selection, clears it and hides the selector. Some setups immediately move characters or begin a pull. Reopen the selector and select an entry again for the next command.

Setup selector control reference
ControlWhat it does
Send to Group / RaidUses group/raid chat when Silent Mode is off; uses a relay when it is on.
Send to Ogre IRCSends the selected setup through OgreIRC to the participating team.
InfoRequests help for the selected entry without sending its setup.
Close ×Hides the selector. It does not stop EA or an active encounter.
Right-click an entryRemoves the selected row from the current list. Use left-click to select normally.
Sending the same setup from the console

This OgreIRC example starts the documented EA Thet-em-aua setup. Send it only when the raid is prepared in the correct instance:

Inner Space console · reaches the team through OgreIRC

IRC !c all -raid "Set up for EA Thet-em-aua"

The selector handles this wrapping for you. Do not paste the full IRC !c ... line into EQ2 group/raid chat. Copy buttons on these web pages copy text only; they do not send commands to the game.

Assign tags and group roles

Read the chosen encounter’s assignments before adding tags. A number, an icon, a raid group and an EA group role are separate pieces of information. Their meaning is encounter-specific.

Apply the requested tags

  1. Target the intended character in game.
  2. Apply the required number or icon with the game’s tag controls. For example, these are local Inner Space commands for the currently targeted character:

Example · number tag for the selected tank

EQ2Execute tagtarget 1

Example · icon for the selected main-tank-group marker

EQ2Execute tagtarget shield

Check the tags visible in the group/raid UI, the raid group membership, and the required count of special-job characters. Review old assignments before changing encounters. Do not apply the example tags to every member of the raid.

Group marker versus individual job. Some routines find an icon on any member of a group, then treat the entire group as the marked group. A Star or Sword job can instead refer to the individual carrying that icon. Follow the encounter notes rather than assuming every icon works the same way.

Encounters that use EA group roles

Some encounters, including Kurn’s Tower and selected Velious heroic setups, use EA’s per-character group role instead of the tag scheme above. Startup reports the loaded role. Saved custom roles override these defaults:

EA roleDefault assignment
Role 1Fighter
Role 2Druid or cleric
Role 3Shaman or shaper
Role 4Enchanter
Role 5Predator, rogue, animalist, sorcerer or summoner
Role 6Bard

Check the role reported for each character and the raid group specified by the encounter. Changing a number tag does not change the saved EA role. If you maintain custom roles through your installed BJ Scripts configuration, save the intended role and reload it in that character’s session:

LavishScript:ExecuteAtom[a_EA_ReloadGroupRole]

The reload command reads the saved role; it does not choose or write one. Confirm the new startup-style role message before sending a setup.

Run an encounter

The setup and attempt workflow
Figure 3. The setup and attempt workflow.

Before Send

  • Enter the correct instance and gather the team where the encounter instructions require.
  • Check tags, raid order, group roles and special-job counts.
  • Equip or carry required items on the characters that will use them.
  • Confirm OgreIRC and the intended OgreBot profile on every session.

After Send

  • Watch the console for setup failures, missing assignments, waiting states and encounter reports.
  • Let initial positioning and preparation finish.
  • Follow the encounter’s pull instructions. Some setups pull automatically; others require you to initiate combat.
  • Handle any mechanics listed as manual or unsupported in the catalog.

Sending a setup can act immediately. It is not a preview button. Have the team ready before sending it, even if your intention is only to check configuration.

After a kill, wipe or interrupted setup

  1. Use an explicit encounter Stop entry when one is available. Check its exact name in the catalog or selector.
  2. Recover the team, resolve the reported problem and check settings the encounter may have changed, including camps, targets, cast stacks and loot options.
  3. Re-select and send the appropriate setup for the new attempt. Reload between setup modes when the encounter notes recommend it.

Closing the selector only hides it. OgreBot pause can help control movement, but it is not a universal stop or cleanup for every EA routine. Cleanup varies by encounter; use the documented controls.

Read EA reports in OgreConsole

With OgreConsole available, EA adds an EA button beside Setup. Click it to view encounter reports. The button changes to OC; click that to return to the normal console.

  • EA is a report view. It has no command entry. Switch to OC for normal OgreConsole input, or use the Inner Space console for the commands labeled that way in this guide.
  • Both histories collect while hidden. Switching views or hiding the window preserves them. Reloading OgreConsole creates fresh histories; restarting EA starts a fresh EA report history.
  • Colors identify the message body. EA combat text is yellow, including wrapped lines. Character and timestamp headings remain white.
  • Reports do not force the window open. Open OgreConsole and select EA when you want to monitor. If the EA view cannot attach but the normal console is available, reports fall back there.

Some setup and helper diagnostics still appear in the regular or Inner Space console. An empty EA view alone does not prove that EA failed to load. Likewise, a displayed ability request or timer is not proof that the effect reached every recipient.

Configure when needed

Optional features

These controls are separate from choosing an encounter. Use only the features your team needs, and check the relevant characters’ reports after a change. The IRC examples below belong in the Inner Space console.

Power management

Power management starts disabled, although an encounter may enable it. It coordinates supported shards, hearts, items and fighter power-saving behavior. A 40% minimum-power example:

IRC !c -Raid "EA PowerManagement Enable 40"
IRC !c -Raid "EA PowerManagement Disable"

Characters must have the required abilities/items available; the feature cannot supply missing equipment.

Crystal Gift maintenance

Enable Power Management first and equip Crystal Gift on participating characters. This example uses a 50% power threshold and retains five matching consumables:

IRC !c -Raid "EA PowerManagement CrystalGift Enable 50 5"
IRC !c -Raid "EA PowerManagement CrystalGift Disable"

Maintenance destroys matching excess Crystal Gift consumables above the retained count. Choose that count before enabling it.

Inquisitor mythical group cure
  1. Equip Penitent’s Absolution on the Inquisitor.
  2. Provide a Resolute Flagellant entry in the Ogre cast stack with the matching afflicted-member threshold. The default is 2.
  3. Let EA detect the equipped item automatically. Check Status if you need to verify the mode.
IRC !c -Raid "EA MythCure Status"
IRC !c -Raid "EA MythCure Enable 2"
IRC !c -Raid "EA MythCure Disable"

Thresholds 1–6 are supported. A manual Disable lasts until Enable or an EA reload. Missing or ambiguous matching cure rows must be corrected in the cast stack. Non-Inquisitors ignore these commands. The regular cure is the fallback while the item is unavailable; unequipping the item restores regular curing.

Velious raid debuffs and tank support

For the supported Destiny of Velious raid debuffs, enable OgreBot’s DoV raid debuff option. Enable its allow moving option if the character should close to casting range. The appropriate archetype ability must be available and ready.

Encounter-requested tank recovery and protection helpers use available abilities. Keep tank ability exports current and required abilities ready. These helpers do not add a universal tank-swap rule to every encounter.

Altruism and travel portals

Altruism recovery: EA recognizes the brawler’s normal group/raid announcement in the form Casting Altruism on [recipient]. Here [recipient] means the actual in-game target, not text to paste. EA watches that recipient for feign death, then stands after at least one second at 50% health, or after 30 seconds, subject to encounter-owned holds. Keep EA running on the recipient.

Travel portals: a nearby requester can send an idle, out-of-combat druid or sorcerer this exact tell:

Can I have a port please? I hate walking.

The caster needs EA running, level 25 or higher, and a ready portal ability. The requester must be locally visible to the caster.

Ready for the next pull

Pre-pull checklist

Use this as a reminder for each attempt. Checking a box here does not inspect or change your game.

0 of 7 checks completed

Checklist state lasts for this page visit only.

Find the missing step

Troubleshooting

The setup window is hidden or does not open

Run the local open-selector command in Step 3 after EA finishes loading. If the atom is unavailable, verify EA started successfully in that session. Check the Inner Space console for missing files, skin errors or a BJ Helper startup failure. Reload the installed ISXBJEQ2/EA build through your normal process after correcting the issue.

The list is empty or my encounter is missing

Check the exact zone and its normal/challenge variant. The list depends on both zone and access. Some entries require the raid access supported by the installed Ogre/EA build. Compare the coverage catalog, wait for zoning/initialization to finish, and reload EA if necessary. A familiar instance name does not guarantee a setup exists for every boss.

Only characters on one computer respond

Choose Send to Ogre IRC explicitly. Check the remote computer’s OgreIRC connection, local sessions, EA release and running scripts. Silent Group/Raid relay sends are not a substitute for a shared IRC path. Verify receipt on each computer before relying on coordinated mechanics.

A character is in the wrong camp or does the wrong job

Recheck that character’s number and icon tags, the group’s icon marker, raid order, and the saved EA group role if the encounter uses roles. Read the encounter’s own assignments; default tag conventions are not universal. Correct the assignment and run the documented setup again when the team is ready.

Send did nothing

Check that you left-clicked a list item and selected the intended destination. Send clears the selection, so reopening the window requires choosing an entry again. Check the receiving clients for setup errors. A command for a different zone, access level or legacy mode may not activate the expected routine.

I cannot type in OgreConsole

If you selected the EA report view, click OC to return to the normal console. The EA view intentionally hides command input. Also check OgreConsole’s normal hide-input preference. The commands in this guide labeled Inner Space console can be entered there directly.

The EA report button or reports are missing

Ensure OgreConsole and EA are both running. EA attaches the button at runtime; no vendor file patch is required. If the report view cannot attach, check the normal console for fallback output. Reloading OgreConsole clears its histories and returns to OC. EA does not automatically open or switch the window when a report arrives.

Settings look different after an attempt

Encounter routines can change camps, targeting, abilities and other combat settings. Use any documented Stop entry and inspect the encounter’s cleanup notes. Check the affected OgreBot profile settings before the next pull; do not assume every legacy routine restores every value.

This guide documents the available controls and source behavior in EA 1.79. Interface and connection settings can differ by installed Ogre version. It does not certify live completion of any encounter.

Guide picture

Scroll sideways on a small screen to read the full-size picture. Press Escape or Close picture to return.

Shopping Cart
  • Your cart is empty.