Lootryx, in game

What it is

Lootryx is an in-game companion to the website. Open its window with //lootryx window to use Home, Find, Linkshell, Me and Settings. Most everyday actions have buttons; the command reference below also covers setup, diagnostics and advanced tools. The small HUD is a separate, optional status overlay.

What you can do in the window

• Home: review actions needing attention, reach Party Finder and events, and check character and DKP information.
• Find: browse Players looking for a party, Parties recruiting members, or the Linkshells directory. Search and filters narrow the current board. Post availability when you want a group; choose Recruit members when you are forming one.
• Linkshell: open auctions, HNM windows, events and standings. More exposes additional records and tools, including polls, bounties, bank records, loot and item lookups. Available actions depend on your role; some management continues on the website.
• Me: inspect separate DKP balances, observed jobs, planned jobs, your wishlist, macro tools and account connection.
• Settings: choose display preferences, align the pointer, configure reporting, inspect connection diagnostics and read or export recent Results. The bell opens notification history and its preferences.

Recruiting more than one person

A recruitment can reserve several places across Any, Tank, Healer, Support and DPS. Set the party capacity and allocate the places after you, the host. A six-person roster has five places to allocate. For example: one Tank, one Healer, one Support and two DPS. When editing, those counts include existing joiners, not just the empty places. Count controls appear when the connected server supports them.

The list shows remaining roles and roster capacity. Joining or accepting an invitation checks that a place is still available. The Lootryx recruitment roster is separate from the actual game party: joining a listing does not send a game invitation. Use My game party or the player contact actions to prepare a command, then send it yourself. Ready checks coordinate the registered roster and do not control the game.

DKP, auctions and HNM windows

If your linkshell uses separate DKP tracks, such as Scheduled and HNM, each balance stays separate. Choose the wallet when opening an auction and check the wallet shown when bidding. A sealed bid is your maximum offer; the final charge follows the linkshell's auction rules and may be lower. A countdown reaching zero is not confirmation that the server has settled the auction.

HNM windows distinguish open, upcoming, stale and unknown records. Log ToD records a death you witnessed, after confirmation. It does not detect kills for you. Refresh retrieves the latest stored records.

Install and update

1. Download the Windower 4 ZIP from the latest release on GitHub.
2. Extract it and copy its lootryx folder into Windower4/addons/. The entry file must be Windower4/addons/lootryx/lootryx.lua, not inside a second nested lootryx folder.
3. While logged into your character, run //lua load lootryx.
4. Open //lootryx window. Use //lootryx help for commands.

To update, replace the addon code and bundled assets with the new package while keeping your existingdata/settings.xml and other saved data. Run //lua reload lootryx afterward. Saved preferences and pointer calibration should remain; notification and Results history are session-only.

On Ashita v4, download the Ashita ZIP from the same release and copy its lootryxfolder into Ashita's addons folder. Run /addon load lootryx, then /lootryx window, and pair from the GUI. Ashita keeps separate per-character settings in config/lootryx/; it does not import Windower settings automatically.

Connect your character

1. Sign into lootryx.com and open your linkshell. Under My Profile, open My Characters, then Connect your addon > Get a setup code. Codes are single-use and expire after ten minutes.
2. In game, open Me > Connection and enter the code, or run//lootryx setup <code> in Windower or /lootryx setup <code> in Ashita, on the character whose name you entered on the website.
3. Check the connection result. Repeat pairing separately for each character you play.

Rather not install the addon? An officer can add your character to your account from the linkshell roster. Attendance captured by anyone else's addon then counts for you, and check-in PINs work without it.

Linkshell features require an active membership and the relevant permissions. Your website role applies in the addon too. Members can bid where permitted; opening auctions requires an authorized role. Hidden or disabled controls do not grant access through slash commands: the server checks requests as well.

Attendance and zone sharing

In Linkshell, open Capture attendance to check the current event before sending names. An open check-in is required. Review the event, closing time and roster preview, then capture. A failed capture is not saved for submission to the next event.

Start a scheduled or unscheduled event

Officers can choose a scheduled event and start check-in, or start an unscheduled run from the addon. Review the title, event type, DKP wallet, scoring policy and check-in window before confirming. The event type selects the wallet through your linkshell's configured mapping; it is not an arbitrary wallet choice. Starting an event does not award DKP. Only one check-in can be open per linkshell; close the current window explicitly before switching events. Members can inspect attendance status and refresh, but cannot start or close check-in.

On the website, open your linkshell, Events, then the event and its Attendance check-in card. Start check-in enables both addon captures and member PIN confirmation. RSVP is separate from attendance. Review attendance before using the separate Score event action.

Forgot check-in and the group has dispersed? The addon cannot reconstruct an earlier roster. Members can use Request late attendance on the website event page for officer review. Approval can award full attendance DKP or top up an earlier partial award, so officers should verify the claim before approving. Record snapshot records names at the current time; it cannot backdate a game observation or recover elapsed attendance time.

Open Settings > Reporting to inspect saved switches and their configured intervals.

• Automatic attendance capture: periodically sends the names in your alliance. It needs an open event check-in to record attendance. It does not create an event or award new DKP on every capture. Time-present tracking must be enabled on the website.
• Share my current zone: periodically reports your character and zone when enabled, with linkshell opt-in required. It sends no coordinates or kill reports and does not award DKP. Zone sharing is not attendance check-in.
• Attendance adjustments: explicitly include a missing player or exclude someone from future captures. Preview the names before reporting. This changes reported attendance only, never your game party. Adjustments affect manual and automatic captures until cleared or the addon reloads.

Automatic reporting choices are saved. Attendance name adjustments are temporary and clear on reload.

Notifications and background checks

The bell shows notifications from the current session. Opening the inbox does not mark everything read. Open an individual notification, mark it read, or use Mark all read. Reloading clears the history.

Preferences separate background checks from chat alerts. Auction checks discover new auctions and server results; recruitment checks discover roster changes, invitations and ready checks. These arrive after a successful check, not instantly. Check-in opening and closing alerts likewise depend on successful attendance status checks. With background checks off, refresh manually to discover changes.

Game-party join and leave alerts use local party data, separately from website recruitment changes. Deadline alerts use the local countdown and can appear before server settlement. Turning off a chat-alert category silences its chat messages while discovered notifications remain in session history.

What it reads and writes

• Reads your character, job and available job levels, party/alliance names, and current zone through the loader APIs.
• Reads your treasure pool when you use the item picker. Drops and witnessed Times of Death require your confirmation; there is no automatic kill or lot detection.
• Reads local item artwork. Windower caches extracted icons in the addon folder; Ashita uses local resource artwork.
• Reads your local macro books for upload. An explicit macro pull can write your own macro files, with backups and protection for the book you identify as active. It never executes those macros.
• Writes its own settings, caches and explicitly exported Results text.
• Sends authenticated reports and requests to Lootryx, including bids, listings, signups, wishlist edits and optional background reporting. It fetches records for the GUI and chat results.
• Looks up the Lootryx hostname through Cloudflare's encrypted DNS (cloudflare-dns.com, reached at 1.1.1.1), because the game client's Lua has no name resolver of its own. Cloudflare sees your IP address and the hostname being looked up. No linkshell or character data is in that request.

These website actions can change records or spend DKP. Review the selected wallet and bid before confirming. The addon source and its GM audit guide are public, so players and server staff can inspect every capability. Phoenix staff reviewed the addon and approved it for use. We do not speak for any other server's rules.

Troubleshooting and limits

• Missing players or parties: check the Players/Parties tab, selected world, search and filter chips. Clear filters and refresh. Your own listing is shown separately.
• Cursor misses buttons:use Settings > Align pointer and follow the targets with your game cursor. Calibration is saved. Recheck alignment after changing display or UI settings.
• Missing updates: inspect the refresh status and notification preferences. Cached results are not evidence that a request succeeded.
• Request already pending: let it complete before retrying. Requests can fail or be delayed. Runtime/network limitations can still cause a visible client hitch; background checking is not a guarantee of hitch-free networking.
• Long chat output: open Settings > Results. Export full text writes lootryx-results.txt inside the addon folder. Open that file to copy the text; this is not a clipboard-copy button. Each export replaces it.
• Connection problems: run //lootryx status and //lootryx selftest. Re-pair on the correct character if needed; never share your signing secret.

Command reference

Generated from the addon's help text for version 0.40.31. In Windower, use//lootryx help all to print it. Ashita uses /lootryx with a single slash, or /lx for short.

Your data

Attendance captures include character and alliance names and a timestamp. Other requests carry the data needed for their action, such as a bid amount, recruitment roles, macro contents or your optional zone report. The signing secret stays in local settings and signs requests; it is not sent with each report. Treat your settings and exported Results as private, and review them before sharing.

You can revoke credentials from the website. Linkshell records require membership permissions; Party Finder and the linkshell directory contain public listings. //lootryx show previews your alliance locally without sending a report.