table of Contents
Trigger conditions and specific detection logic
Specific implementation and troubleshooting
Overview of interface common components
Guide category settings:
Force guidance, do not trigger specific events, never skip
Non-mandatory, click other areas to skip to the next step
Non-mandatory, click other areas to close the current guidance
Trigger conditions and specific detection logic
1. After going online, the server will receive the guidance status as a basis for judging whether the guidance is complete
2. Add event monitoring to return or open the main interface for detection
3. Actively call after clearing specific copies or missions
Specific implementation and troubleshooting
1. The interface has not been opened after the boot is triggered.
Join _WaitingUIGuild, and continue to perform related guidance after the specified interface is opened
2. Which guides need to be kept when going online and offline, and which ones need to be discarded
. SaveStep is added to the configuration table , which depends on configuration control
. 3. Boot skip and stuck handling.
Pause for 3s to skip, and 10 times to get stuck, which can be configured specifically
Overview of interface common components
AniMask: Gradient effect
ClickMask: Block events and get click
chat: Dialogue panel
Arrow 1 ..2..3: Arrow finger