fix: sync current handlers, repair relic data and restore visible launcher consoles

This commit is contained in:
CAtlas0784 committed 2026-10-16 22:19:52 +07:00
1 parent 163d4433e6
commit 74f3c4411b
46 files changed
+4599 -1402

No files matched your search

+4 -12
View File
@@ -274,12 +274,8 @@ func init() {
})
handle("GetCurChallengePeak", func(s *Session, req *goproto.GetCurChallengePeakCsReq, rsp *goproto.GetCurChallengePeakScRsp) error {
// reverted to the state of the build that reached Pom-Pom:
// empty peak_id (a fabricated peak_id:1 crashed CreateMemberEntityLeader)
// Match upstream's empty current-state response until a Peak is active.
rsp.Retcode = 0
rsp.HasPassed = true
rsp.PeakId = 1
rsp.BossBuffId = 0
return nil
})
@@ -293,13 +289,9 @@ func init() {
EndTime: 1924992000,
})
}
// NOTE: the real 4.6.51 activity schedule (realActivitySchedule, from
// the March7th dump) BLACK-SCREENS the events page: the client renders
// real event panels, then requests each activity's data (GetActivity-
// HotData/GetActiveActivityData/...) which we cannot fill yet - NRE.
// The synthetic list below resolves to nothing and keeps the page open
// (empty but usable). Re-enable the real list only after implementing
// per-activity data handlers.
// Advertise only the supported Endgame schedules. Exposing the full
// ActivityConfig before implementing its activity-data handlers makes
// the Client request unavailable state and can stall the events page.
// Apocalyptic Shadow tab requires an active schedule with panel 21001
for actID := uint32(21001); actID <= 21030; actID++ {