Meta Manager: switch metas on a timer

What it is

The Meta Manager loads a different meta for you when a timer runs out. The timer can be a quest timer from /myquests, a number of minutes on the current meta, a repeating clock, or a countdown you start yourself. You make a short list of rules, each one "when this happens, load that meta". The manager waits until the bot isn't busy fighting or looting before it switches. A common use is to farm on one meta and hop to a quest meta whenever its timer is up. The manager is off until you turn it on.

How to open it

1. Open the Meta panel: the button with a list of check marks on the RynthCore bar, or type /rc ui open Meta.
2. At the top of the panel, click Schedule (next to Visual and Source).

The basics

1. Turn it on

Tick Manager at the top left, or type /ra metamgr on. When it's off, the status line says "Off - nothing is loaded or polled."

2. Add a rule

1. Click + New Rule at the bottom.
2. When: pick one of the four rule types (see the table below).
3. Fill in the quest name or the number of minutes.
4. Load meta: pick the meta to load. The list shows the metas the Meta panel knows about.
5. Only while this meta is loaded: leave it on (any meta), or pick a meta. See "Only while meta X is loaded" below.
6. Choose Repeat or Once.
7. Click Add Rule.

The Add Rule button stays greyed until you have picked a meta, and named the quest if it's a quest rule.

Rule types

3. Read the rule list

Each row shows:

• the rule number, then its on/off box;
• up and down arrows to change its priority;
• a play/stop button (countdowns only), or a re-arm button when the rule has fired, failed or is holding;
• a bin to delete it;
• what it does, for example quest blightlordlairwait1008 ready -> quest.af, with (on farm.af) if it only runs on one meta and [once] if it's a one-shot;
• on the right, its state.

Hover a row for the full details. Click its text to edit it. Saving an edit re-arms the rule.

Priority: the top rule wins

• Rules are checked from the top down. The first rule that is due wins. That rule gets an amber edge.
• Use the up and down arrows to reorder them.
• Quest rules hold their place. Once a repeating quest rule has fired, it keeps first place for as long as /myquests still shows the quest as ready. The rules below it wait. The idea is that the meta it loaded is busy doing that quest. When the next /myquests shows the quest done (its timer running again), the rule lets go. The row says holding meanwhile.
• Rules above a holding quest rule can still fire.

One-shot vs repeating

• Repeat: the rule fires every time its timer runs out. A repeating countdown starts itself again.
• Once: the rule fires one time, then shows fired and waits until you re-arm it. Re-arm it with the round-arrow button on its row, with Re-arm all at the bottom, or with /ra metamgr reset <#>.

A one-shot that has fired, and a running countdown, are both remembered after you relog.

"Only while meta X is loaded"

With a meta picked here, the rule only counts while that meta is the one loaded. This is how you build a rotation: "on A, go to B" and "on B, go back to A". Names are compared without the file extension, ignoring capital letters.

Be careful with After N minutes on the meta when this is left on (any meta). Any load restarts the clock, including the one this rule makes, so it reloads its meta every N minutes.

Safe switching

When a rule wins, the manager doesn't switch straight away. It waits until the bot is not:

• fighting,
• looting,
• buffing or casting,
• using a portal,
• busy with a vendor or a trade,
• crafting.

The settings at the top control this:

Each switch prints one line in chat, for example:

[RynthAi] Meta Manager: loading quest.af (quest blightlordlairwait1008 ready)

Loading a meta this way is the same as picking it in the Meta panel. The meta starts again from its first state. Your nav route is left alone.

If the meta file is missing or has no rules, you get a line saying it can't be loaded. That rule then shows error and stops trying until you edit or re-arm it.

/ra metamgr commands

You can type these in chat. Metas and Lua scripts can send them too, like any /ra command.

Rule numbers are the numbers shown at the left of each row.

Worked example: farm, then do a quest when its timer is up

Say you farm with farm.af. You also have quest.af, which runs a quest whose /myquests name is blightlordlairwait1008. The run takes about 15 minutes. You want the bot to go and do the quest whenever its timer is up, then go back to farming.

Step 1: find the quest name. Type /myquests and find the quest's line. The name is the first word, before " - ".

Step 2: make rule 1, the way back.

• When: After N minutes on the meta, 20 minutes (a little longer than the quest run takes)
• Load meta: farm.af
• Only while this meta is loaded: quest.af
• Repeat

Step 3: make rule 2, the way out.

• When: Quest ready (/myquests timer), quest blightlordlairwait1008
• Load meta: quest.af
• Only while this meta is loaded: farm.af
• Repeat

Keep the time rule at the top, as rule 1.

Step 4: start it. Load farm.af, start the macro and tick Manager.

What happens:

1. The manager sends /myquests every 5 minutes and counts down between checks. Rule 2 shows the time left on the quest.
2. When the quest is ready, rule 2 turns amber. As soon as the bot finishes its current fight and loot, the manager loads quest.af.
3. The bot does the quest. Rule 2 shows holding until a /myquests check shows the quest done.
4. After 20 minutes on quest.af, rule 1 loads farm.af again.
5. Next time the quest timer runs out, it all starts over.

If the quest run fails: rule 1 still brings you back to farm.af after 20 minutes. Rule 2 then shows holding, because the quest still looks ready. It won't try again by itself. Click its re-arm button when you want it to try again.

Why rule 1 goes on top: a holding quest rule blocks the rules below it. With the time rule above, the bot always gets back to farming.

What /myquests output it reads

The manager reads the normal reply to /myquests. Each quest is one line, like this (the quest text here is made up):

blightlordlairwait1008 - 3 solves (1759190400)"Blight Lord Lair" -1 72000

From left to right:

The quest is ready at "last solved + timer". If you have reached the solve limit, it is never ready again.

It also understands these replies:

• Quest list is empty.: you have no quest timers, so every quest counts as never done (ready).
• The command "myquests" is not currently enabled on this server.: the manager stops asking, and the status line says the server has /myquests turned off. Quest rules can't fire on that server; the other rule types still work.

A quest that isn't in the list at all counts as never done, which means ready.

The manager also reads any /myquests you type yourself, and the one sent at login.

Tips

• Try a Countdown rule first. Set it to 1 minute, press play, and watch it switch. It's the quickest way to see how the manager behaves.
• Use Once for rules you only want to run one time, such as "after 2 hours, load the go-home meta".
• If a quest rule sits on holding for ages, the quest meta probably isn't finishing the quest. Put a time rule above it, as in the worked example.
• /ra metamgr status is handy when the panel is closed.
• Your rules are saved per character, in metamanager.json in that character's RynthAi settings folder.

Known limits

• AC's own chat window shows the manager's /myquests replies. They are kept out of the RynthChat window (see "Plugin order" below), but AC's retail chat window still prints them, about one screenful every 5 minutes. If you hide the retail chat window and use RynthChat, you shouldn't see them. A /myquests you type yourself shows as normal.
• Your PC clock matters. The quest timer comes from the server, but it's compared with your PC's clock. If your clock is a few minutes off, quest rules fire a few minutes early or late. Early means the quest NPC may say you did it too recently. Keep your PC clock synced.
• Checks are every 5 minutes by default, so a quest can sit ready for a few minutes before the manager notices. Lower Poll if that matters (the minimum is 1 minute).
• Quests the server doesn't know about look ready, because a quest missing from /myquests counts as never done. This is rare.
• Right after login, edits made in the panel during the first second or two are ignored while your character's rules load. Make the change again if it didn't stick.
• Plugin order: hiding the manager's replies from RynthChat relies on RynthAi loading before RynthChat in the launcher's plugin list. If the replies do show up in RynthChat, check that order first.