Unity Concord - Research Notes and Planning

[ghost]

There's a lot of different components involved with Unity Concord, so creating this discussion to provide a centralized location for both research notes and technical discussion for its future implementation.

Requirements to Join a Unity

---

1. Player must have completed at least 10 RoE objectives
2. Player must then enter one of the following zones:

Southern San d'Oria / Northern San d'Oria / Port San d'Oria
Bastok Mines / Bastok Markets / Port Bastok
Windurst Waters / Port Windurst / Windurst Woods
Western Adoulin / Eastern Adoulin

3. Player must set objective, "All for One," and then speak to a Unity NPC

Unity Leader Values

---

The below indices are used only in CCharStatsPacket() for determining a player's membership in Unity Concord. Rankings are ordered in the same manner, however do not specify an index.

0. None
1. Pieuje
2. Ayame
3. Invincible Shield
4. Apururu
5. Maat
6. Aldo
7. Jakoh Wahcondalo
8. Naja Salaheem
9. Flaviria
10. Sylvie
11. Yoran-Oran

Packet Reference

---

CCharStatsPacket() (pseudo-code):

    ref<uint32>(0x58) = ([unity_accolades] << 10) | ([unknown] << 5 | [unity_leader_index]);
    ref<uint16>(0x5C) = [evaluation points this week]; // Partial Personal Eval
    ref<uint16>(0x5E) = [evaluation points last week]; // Personal Eval

Notes:
Wiki makes reference to a two week period for Unity Leader trust eligibility. This aligns with the following timeline:

1. Player attains minimum partial personal evaluation (Week 1) - Trust is granted!
2. Player has personal evaluation that meets requirement (Week 2) - Trust remains!
3. Player does not meet requirement for either personal or partial (Week 3) - Trust is removed!

Therefore, operating on the assumption that either evaluation will allow the use of a Unity Leader Trust.

One evaluation point is the equivalent of earning 1000 accolades within that weekly timeframe. To remain consistent with storing values, I would propose storing the following values per character:

• Unity Leader
• Accolades gained last week
• Accolades gained this week

---

Unity Rankings "packet" TBD:

Unity rankings are comprised of 64 "packets," though as of current research, the majority of these appear to either be empty, or contain garbage data from non-status update packets being sent in the meantime. All are required for rankings to be displayed (and perhaps act as a counter/timer), though only four contain ranking data. Basic structure is as follows:

    this->type = 0x63;

    // CMenuUnityPacket: Update Type 0x0000
    this->size = 0x8C;

    ref<uint8>(0x04) = 0x07; // Switch Block 7
    ref<uint8>(0x06) = 0x88; // Variable Data Size
    ref<uint8>(0x08) = 0x00;
    ref<uint8>(0x09) = 0x00; // Type 0

Note: bytes 0x08 and 0x09 are both part of a "sub-id" of the packet, and they are broken out in testing for clarity due to packet byte orders. 0x09 is the least significant byte for this counter, while 0x08 is most significant. The starting range is 0x00 00, and ending range for this series is 0x01 1F.

Full rankings are determined by two packets in the sub-ID (0x00 01, 0x00 02). These align with total members in unity from last evaluation, and total evaluation points (respectively).

Number of members (0x00 01):

    ref<uint8>(0x04) = 0x07; // Switch Block 7
    ref<uint8>(0x06) = 0x88; // Variable Data Size
    ref<uint8>(0x09) = 0x01; // Type 1

    ref<uint32>(0x0C) = 0;
    ref<uint32>(0x10) = 10; // Pieuje
    ref<uint32>(0x14) = 10;
    ref<uint32>(0x18) = 10;
    ref<uint32>(0x1C) = 10;
    ref<uint32>(0x20) = 10;
    ref<uint32>(0x24) = 10;
    ref<uint32>(0x28) = 10;
    ref<uint32>(0x2C) = 10;
    ref<uint32>(0x30) = 10;
    ref<uint32>(0x34) = 10;
    ref<uint32>(0x38) = 10; // Yoran-Oran

Similarly, number of evaluation points:

    ref<uint8>(0x04) = 0x07; // Switch Block 7
    ref<uint8>(0x06) = 0x88; // Variable Data Size
    ref<uint8>(0x09) = 0x02; // Type 2

    ref<uint8>(0x0A) = 0x00;
    ref<uint8>(0x0B) = 0x00;

    ref<uint32>(0x0C) = 0;
    ref<uint32>(0x10) = 4200;
    ref<uint32>(0x14) = 4100;
    ref<uint32>(0x18) = 4000;
    ref<uint32>(0x1C) = 3900;
    ref<uint32>(0x20) = 3800;
    ref<uint32>(0x24) = 3700;
    ref<uint32>(0x28) = 3600;
    ref<uint32>(0x2C) = 3500;
    ref<uint32>(0x30) = 3400;
    ref<uint32>(0x34) = 3300;
    ref<uint32>(0x38) = 3200;

This same format is used for partial unity ranking, with sub-id values of 0x01 01 and 0x01 02

---

Unity Chat Status (0x118)

Byte 4, 0x00 = Disabled, 0x01 = Enabled (set from Unity Information Menu)

0x11B

Byte 4 appears to follow Unity Chat Status Byte 4, perhaps request for chat? There are limits to the amount of users that can be participating in Unity chat per zone.

---

Unity Event IDs

Zone	Needs 10 RoE Objectives	All for One not set	All for One set	Unity Joined
Southern San d'Oria	3528	3525	3526	3529
Bastok Markets	597	594	595	598
Windurst Woods	878	875	876	879
Western Adoulin	5148	5145	5146	5149

TODO

---

[ ] Finish capturing Event IDs for Unity NPC
[x] Find condition for unlocking "All for One" in RoE objective list
[x] Implement core system for tracking Unity Rankings
[ ] Apply bonuses for accolades based on Unity Ranking
[ ] Captures, captures, and more captures for Unity NPCs post-joining

[ghost]

Unity Warp Event Options captured so far (Event Finish after confirming warp)

[ghost]

Ref for missing conditions: http://wiki.ffo.jp/html/35677.html

[ghost]

Initial implementation has been completed. Closing this discussion.