docs(fort-attack): document Interceptor's Base event RE status

Add fort-attack-event.md capturing everything known about the fort
attack event system (packet wire formats, register plumbing, DB schema
gap, quest IDs) and what needs reverse-engineering before implementation
is possible. The feature/enum-event branch covered only scheduling and
is not mergeable; its findings are preserved here for future reference.

Update unimplemented.md to point to the new doc and correctly describe
the branch scope.
This commit is contained in:
Houmgaor
2026-03-22 20:11:22 +01:00
parent f03476e6e0
commit 63312dac1b
2 changed files with 203 additions and 2 deletions

View File

@@ -57,7 +57,7 @@ Grouped by handler file / game subsystem. Handlers with an open branch are marke
| Handler | Notes |
|---------|-------|
| `handleMsgMhfGetRestrictionEvent` | Fetch event-based gameplay restrictions — **[`feature/enum-event`]** (4 commits) |
| `handleMsgMhfGetRestrictionEvent` | Fetch event-based gameplay restrictions — see `docs/fort-attack-event.md` |
### Guild (`handlers_guild.go`)
@@ -189,7 +189,7 @@ that needs no reply). Others are genuine feature gaps.
| Branch | Commits ahead | Handlers targeted |
|--------|:---:|-------------------|
| `feature/enum-event` | 4 | `GetRestrictionEvent` |
| `feature/enum-event` | 4 | `EnumerateEvent` scheduling only — not mergeable, see `docs/fort-attack-event.md` |
| `feature/conquest` | 4 | Conquest quest handlers |
| `feature/tower` | 4 | Tower handlers |