EVENT #14: ANOMALIES - COORDINATION POST

[abraxasmods]

Event #14 - COORDINATION

OOC event plotting | IC event log

---

This post is for coordination while the event is ongoing, to prevent the IC Event Log from being overrun by OOC mod and player communications. The comments section will contain applicable comments and forms for you to reply to as needed.

Use this post to:

◎ Request NPC involvement or resources
◎ Review any updated developments
◎ Submit noticeable actions
◎ Write rapid IC exchanges

If you have any questions, see the Questions thread on the OOC Plotting Post.

Available Forms

For details on each form, see the sections below.

The DEVELOPMENTS thread will be used by the mods to record important game-wide updates.

Mod Communications

If you have something you want to do related to the event plot, you can communicate and coordinate with us here. This includes NPC meetings, requesting large resources, destroying the environment, or anything else that may require mod permission to proceed. If we can't accommodate a request for any reason, we'll do our best to offer an alternative!

Contact Us

<b>Player Name:</b> <b>Character Name:</b> <b>Request:</b> (Describe what you'd like to do)

IC Exchanges

Use this option if you have an interaction you'd like to play out, but setting up a standard IC thread would be impracticable. For example, if your character wants to speak to several people about an event they witnessed together, you might want to do an IC exchange.

Treat this like an informal IC network thread done in person, where character reactions, snippets of dialogue, and other details can be quickly played out and concluded in-game without committing to a full log thread. Exchanges are game canon, and can count towards Activity Check under the category of a Network thread.

Start an IC exchange

Using the provided form is optional. Begin a thread freeform if you prefer.

<b>Where & when:</b> (Where and when is this exchange taking place?) <b>Purpose:</b> (What's the reason for this exchange?) <b>THREAD START</b> (Write the scenario, your character's actions, and any dialogue as usual)

Notable Actions

Submit any notable actions that are likely to gain attention from other players such as environmental damage or any important wounds made on a Anomalous Beast (such as a missing limb). We will update the Developments comment to help players keep track.

Submit a notable action

<b>Player Name:</b> <b>Character Name:</b> <b>When:</b> (Approximately when is this incident taking place? A day or two into the event, at the end of it, or somewhere in the middle?) <b>Where:</b> (Where is this incident taking place?) <b>What:</b> (Describe the incident) <b>Link:</b> <a href="urlhere">Thread</a> (If applicable. Actions can be submitted without a thread if they're brief or minor, for example if your character is running around screaming about the end of days.)

Comments

[londonbound]

Player Name: Lena
Character Name: Rhy Maresh, Thancred, Stephen Strange, Linhardt

Request: Working with the information provided by the Network as described by Dee here, Rhy and Thancred will both attempt to get this info to Lyle Vela in Nott as soon as it becomes clear that one of the rifts is at the docks there. Thancred in particular will have early knowledge of Watcher in the Water's appearance in Nott, due to Vash's vision, which was shared with him. They will send updates as information is found out about any of the beasts' weaknesses, and as beasts are dispatched later in the event.

Similar to how he helped set up temporary triage centers during the Invocation event, Rhy would also reach out to the same folks he worked with then to provide any assistance he can setting up shelters for displaced or injured civilians. He will be joined in this case by Stephen Strange and Linhardt, who will lend their healing and organization assistance as well.

[abraxasmods]

Hello! Lyle will accept the information and assistance. Though he's familiar with Thancred and Stephen, Rhy may briefly introduce Linhardt to him as they have not met.