SamandClaude Fable 5
c887170b37
- The social window: friends, ignore and `/who`, in the reference's own two-level arrangement with its inner tabs and per-row right-click menus. The lists ride the real wire — guid-keyed with no names, resolved through the name cache, and capped at 50 friends / 25 ignores because those are the client's own caps — and the ignore list does its actual job: an ignored speaker's chat is dropped silently, a whisper additionally tells the sender, and a duel challenge is auto-declined. Guild ships as a disabled tab, which is what a guildless character sees. - The escape menu: ESC's last rung finally opens something. The game menu lands at the reference's own size and ladder, and leaving works — logout and quit with the server owning the clock (instant at an inn, refused in combat, or the 20-second countdown), narrated by the real camp/quit dialogs. While the menu holds the center nothing else opens, and the bag bar greys out under it. - Items on the action bar act like items. An equipped trinket was a dead button; the reference's use law is two stages — not equippable means use, equippable and already worn means use in place — over its exact search order (equipment first, then the bags, then the backpack, then the keyring; never the bank). What can go on the bar is now the reference's own two filters, byte-read: an item with an on-use spell or one you can equip, and no passive spells — and dropping a passive there speaks the real client's own line, "You can't put a passive ability in the action bar." - A quest-starter item opens its quest instead of "The item was not found." The question goes to the item's own guid, never through item-use — which the server refuses for every one of the 215 quest-starter items — and refusing the quest says what the client says, then closes the window. - For the toolbox: a pixel pick that reports everything under the cursor all the way back, a lens that says which render phase a draw landed in, and switches that separate "discarded" from "lost depth" from "never drawn" — built while cornering a flickering tent, whose fix ships in the next snapshot. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
79 lines
3.6 KiB
Rust
79 lines
3.6 KiB
Rust
//! The **session-exit API** (decision 0674) — the four globals the game menu's Logout and Exit
|
|
//! Game buttons call, and the two dialogs' answers to them.
|
|
//!
|
|
//! The shape is [`super::duel`]'s: nothing to read, only the outbound half. Each call queues a
|
|
//! [`SessionRequest`] the app drains ([`super::UiScript::take_session_requests`]) and turns into a
|
|
//! packet or a process exit, so the engine keeps no reach into ECS/net (decision 0068 §3).
|
|
//!
|
|
//! What each one means, and where the reference puts it:
|
|
//!
|
|
//! - `Logout()` — ask to leave the world (`CMSG_LOGOUT_REQUEST`; the client's own
|
|
//! `ClientServices::SendLogout`, wow-re `system/net/ledger.tsv` 0x5ab000). The **server** decides
|
|
//! whether that is instant or a 20-second countdown, and says so in `SMSG_LOGOUT_RESPONSE`; the
|
|
//! client's whole job is to narrate the answer, which is the CAMP dialog.
|
|
//! - `Quit()` — the same request, plus a standing intent to end the *process* rather than return to
|
|
//! character select when the logout completes. That is why Exit Game shows the same countdown
|
|
//! under a different name (QUIT_TIMER "%d %s until exit").
|
|
//! - `CancelLogout()` — call off either one (`CMSG_LOGOUT_CANCEL`); the server acks with
|
|
//! `SMSG_LOGOUT_CANCEL_ACK`, which is what fires `LOGOUT_CANCEL` and takes the dialog down.
|
|
//! - `ForceQuit()` — the QUIT dialog's "Exit now": end the process immediately, without waiting out
|
|
//! the server's clock. (Its logout sibling `ForceLogout()` is deliberately absent: the reference's
|
|
//! own CAMP dialog has the force button commented out — "uncomment once forced logouts are
|
|
//! completely implemented (they currently have a failure case)" — so 1.12 ships no way to call it
|
|
//! from the UI, and neither do we.)
|
|
|
|
use mlua::Lua;
|
|
|
|
use super::Model;
|
|
|
|
/// Outbound session-exit intents queued by the Era API calls, drained by the app
|
|
/// ([`super::UiScript::take_session_requests`]). Plain data — [`super::DuelRequest`]'s twin.
|
|
#[derive(Clone, Copy, Debug, PartialEq, Eq)]
|
|
pub enum SessionRequest {
|
|
/// `Logout()` — leave the world back to character select.
|
|
Logout,
|
|
/// `Quit()` — leave the world and end the process once it completes.
|
|
Quit,
|
|
/// `CancelLogout()` — call off a pending logout or quit.
|
|
CancelLogout,
|
|
/// `ForceQuit()` — end the process now, no server round trip.
|
|
ForceQuit,
|
|
}
|
|
|
|
impl super::UiScript {
|
|
/// Drain the session-exit intents queued since the last call.
|
|
pub fn take_session_requests(&mut self) -> Vec<SessionRequest> {
|
|
std::mem::take(&mut self.model_mut().session_requests)
|
|
}
|
|
|
|
/// Queue an intent from the app side — the `/logout` and `/camp` slash commands, which benilla
|
|
/// parses in Rust rather than through `SlashCmdList` (the [`super::UiScript::queue_duel_request`]
|
|
/// posture), so they enter the same queue and get the same dialog.
|
|
pub fn queue_session_request(&mut self, request: SessionRequest) {
|
|
self.model_mut().session_requests.push(request);
|
|
}
|
|
}
|
|
|
|
/// Register the four session-exit globals.
|
|
pub(super) fn install(lua: &Lua) -> mlua::Result<()> {
|
|
let g = lua.globals();
|
|
|
|
for (name, request) in [
|
|
("Logout", SessionRequest::Logout),
|
|
("Quit", SessionRequest::Quit),
|
|
("CancelLogout", SessionRequest::CancelLogout),
|
|
("ForceQuit", SessionRequest::ForceQuit),
|
|
] {
|
|
g.set(
|
|
name,
|
|
lua.create_function(move |lua, ()| {
|
|
let mut model = lua.app_data_mut::<Model>().expect("model app_data");
|
|
model.session_requests.push(request);
|
|
Ok(())
|
|
})?,
|
|
)?;
|
|
}
|
|
|
|
Ok(())
|
|
}
|