How to Parse

Important Notes

[1] This program is hardcoded to an extent, because most aspects are not standardized. This is where your parsing knowledge comes in! This program helps you, but it is not an end-all-be-all for parsing. Do not rely on it like this! If a reskin must be added, or changes have been made to the requirements/reacts, the items checked can be found here. You can make an issue, pull request, or DM me to get it fixed.

[2] Raiders for react and set tables that have multiple accounts will be color coded. Focus on the account that has items, typically alts show up as private profiles. Marking one marks all visible accounts belonging to that raider.

Getting Raid Data

To do this, go to the WebApp and copy the numbers at the end of the URL. An example is https://osanc.net/raid/16537, where the id is 16537

Once you copy the id, click on Input Raid ID, paste the id, and click OK.

If you have the most recent version, this may take 5-10 seconds. Don't spam buttons! They will register after, and the last thing you want is the program to parse sets 10 times. A fix is being worked on for this. If you have the light version, this will only take a couple seconds.

Once this raid is loaded, you will see something like this:

Make sure that the status says RUNNING. Everyone needs to be in the raid first, you can check if raiders are listed after the reacts on the left side of the WebApp.

Parsing Reacts

Make sure to do this first! It is more efficient to handle reacts while you let the program parse sets.

When you click on Parse Reacts, the bar at the bottom will start loading showing that the process has started. Trying to parse anything else will pop up a window stating to wait until the process is finished. You can stop a process with the Stop Process button.

The table that pops up will look something like this:

User Interface Explained

There are four checkboxes at the bottom:

• Remove Good Reacts: removes all reacts you don't have to look at.
• Remove Bad Reacts: removes all reacts that have problems.
• Remove Marked Reacts: removes rows that you mark with the checkbox in the last column.
• Remove Manual Reacts: removes extra reacts that you don't care about (runes/inc).

  Important! Reacts are not standardized. If a react that the program isn't aware of is in the template, this react will show as a manual react where the message will just be a /lock <username>. Checking this box will remove it, make sure that there aren't any present before doing so.

There are specific reacts that the program handles:

• Item Reacts: this includes mseal/slow/etc. If the item is present, it will be marked green. If there is any red, there is a problem.
• Class Reacts: this includes mystic/trickster/etc. If the class is present, it will be marked green.

  Not all class reacts have a T6+ requirement, if the ability is marked red/green then there is a requirement.

• DPS Reacts: this includes Ranged/Wizard/Summoner/etc. All items that are DPS will be marked green. If a class is a Summoner, but the react is for Wizards, the class icon will be marked red. If the character has an exalted skin equipped, this will be automatically counted as 1/4.
• Effusion Reacts: this includes Dex Effusion/etc.

What do I do when I parse?

1. Check Remove Good Reacts and Remove Manual Reacts.

   Make sure the reacts removed by the latter are only runes/inc.

2. Lock each person and check if they brought the react.
3. If not, copy the respective message and whisper them in game.
4. Repeat this for everyone, checking off reacts when they equip it.
5. If they ignore you, or are obviously not bringing the react (reacted mseal, brought wizard), then:
   1. Screenshot their inventory in game
   2. Warn/suspend in game

Parsing Sets

The table for sets should look like this:

User Interface Explained

There are three new checkboxes that can be checked:

• Remove Good Sets: removes sets that meet requirements.

  Note: images for items are loaded locally! If an item appears to be an empty slot, but there is no problem, then there just wasn't an image to use. You can click on the inventory image, ctrl+C, and the string of item names will be put in your clipboard. You can use this to figure out what item doesn't have an image.

• Remove Bad Sets: removes sets that don't meet requirements.
• Remove Private Profiles: removes accounts that could not be parsed.
• Remove Marked Sets: removes rows that you mark with the checkbox in the last column.

There are two colors that items can be marked with:

• Red: this includes a banned item, an item under requirements, or an empty slot.
• Yellow: this is a swapout item, check to see if they have an item that meets requirements (if it's the only thing marked).

At the bottom is a button called View Profile. Select any row and click it to find WebApp and Realmeye metadata.

What do I do when I parse?

1. Check Remove Good Sets
2. Copy each username that has a problem first.
3. Lock them in game and confirm it.
4. Screenshot their set in game
5. Warn/suspend for each
6. If you have time, repeat Steps 3-5 for private profiles/swapouts.

Parsing VC

The table for parsing VC should look like this:

Note: gif avatars do not display properly but they are there.

User Interface Explained

There are three new checkboxes that can be checked:

• Show In Group: removes raiders not in the /who
• Remove In VC: shows raiders not in the raiding VC

  Important: we don't know if they are in lounge. Always do a ;find!

• Remove Celestial: removes those with celestial role (yellow name)

If you need the discord id, click on the avatar of the raider and ctrl+C to copy it.

What do I do when I parse?

1. Check all checkboxes.
2. Lock all IGN's (not nicknames!) in game.
3. Do a find on each one in raid bot.
4. Get proof of them in castle but not in vc.
5. Warn/suspend each one