60 lines
2.7 KiB
Go
60 lines
2.7 KiB
Go
package routers
|
|
|
|
import (
|
|
"context"
|
|
"sync"
|
|
)
|
|
|
|
var _ = sync.Mutex{}
|
|
var _ = context.Background
|
|
|
|
//
|
|
// EonBug / hacker phone app — the interactive half of the BBS.
|
|
// The data half lives in GameRouter.Profiles.cs (SyncHackerJobInfo 64189208: handle, post
|
|
// list, rank, daily counters). This file is what happens when the player actually types in the
|
|
// app, and the whole reason it exists is one symptom: open 千年虫 (EonBug), type a name, and the
|
|
// UI freezes in the dialog with no way out.
|
|
// Root cause (matches the reference branch's own logs): the client keeps asking
|
|
// AskChangeHackerName(63975191) and never gets an answer, so its local "this account has no handle
|
|
// yet" state never clears and the dialog re-arms every couple of seconds. Our tree used to have no
|
|
// handler registered for it at all, which is the same failure with extra steps — the request
|
|
// landed, nothing answered it, and the client stayed stuck.
|
|
//
|
|
func GameRouter_HackerApp_AskChangeHackerName(ctx context.Context, conn any, msg any) any {
|
|
// Router implementation for GameRouter_HackerApp_AskChangeHackerName
|
|
var zero any; return zero
|
|
}
|
|
|
|
//
|
|
// Re-push the BBS backbone with whatever handle is stored. Without this the change only exists
|
|
// server-side: nothing tells the client, so HackerSpiritInfo[cardId] stays empty and the
|
|
// app reopens as a new user — back to the same dialog.
|
|
//
|
|
func GameRouter_HackerApp_RepublishHackerHandleAsync(ctx context.Context, rpcCtx *RpcContext) any {
|
|
// Router implementation for GameRouter_HackerApp_RepublishHackerHandleAsync
|
|
var zero any; return zero
|
|
}
|
|
|
|
// The EonBug handle to publish: the one the player picked, else the default.
|
|
func GameRouter_HackerApp_HackerHandle4229938(ctx context.Context, session *GameSession) string {
|
|
// Router implementation for GameRouter_HackerApp_HackerHandle4229938
|
|
return ""
|
|
}
|
|
|
|
//
|
|
// The two remaining EonBug forum actions: read a new post (63150736) and accept a job from one
|
|
// (63036377). Both return void per DefaultReturnCatalog4229938, so an empty OK is the
|
|
// whole contract.
|
|
// ⛑ The point of routing them is not content — the forum's post list already rides
|
|
// SyncHackerJobInfo (64189208) from GameRouter.Profiles.cs. Both are INVOKEs, so with no
|
|
// handler the client awaits a reply that never comes: tapping a post or 接差事 leaves the UI
|
|
// armed forever, the same failure mode AskChangeHackerName used to have.
|
|
// Nothing is persisted: the client commits the read/accept locally, and there is no server-side
|
|
// job simulation to advance.
|
|
//
|
|
func GameRouter_HackerApp_EonBugForumAction(ctx context.Context, conn any, msg any) any {
|
|
// Router implementation for GameRouter_HackerApp_EonBugForumAction
|
|
var zero any; return zero
|
|
}
|
|
|