Upload 140 files

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh0pppib5eyc.txt

@@ -0,0 +1,162 @@
+/
+/
+/
+Mini-Map Marker
+I. Mini-Map Marker Component Functions
+The Mini-Map Marker Component supports displaying entities on the prefabricated 
+Mini-Map UI Controls through visual indicators such as icons/ranges
+The Mini-Map Marker Component needs to be mounted on entities; it supports players, 
+objects, and creations
+Mini-Map Markers can be enabled/disabled through their default settings, or be 
+controlled through node graphs
+II. Editing Mini-Map Marker Components
+1. Adding Components
+(1) In the Entity or Prefab editing interface, open the Component Editing Tab
+(2) Click "Add Components" below, then select and click "Mini-map Marker" to add it
+(3) Click "Advanced Editing" to expand the Editing Tab
+2. Basic Information of Mini-Map Marker Components
+Configuration Parameters
+Description
+Initially Effective
+The drop-down menu provides a list of mini-map markers
+Use the check box to toggle the marker's active state. Cha
+tab
+*Mini-Map Marker List
+Enumerates all mini-map markers for entity configuration
+3. Add Mini-Map Markers
+Click "Advanced Editing" to edit the Mini-Map Marker
+The added mini-map marker is initially effective by default.
+4. Mini-Map Marker Parameter Descriptions
+(1) Display Settings
+Configuration Parameters
+Description
+Initially Visible to All 
+Players
+When enabled, the marker will be visible on the mini-map of
+Follow Object Visibility
+If enabled, when the entity is hidden, the mini-map marker w
+Display Priority
+When Mini-Map Markers overlap at the same location, the m
+number indicates a higher priority
+(2) Marker Style
+Configuration Parameters
+Description
+Select Type
+It is divided into several types: icon, range, marker, player's 
+have different configuration parameters.
+Show Height Difference
+When enabled, entities with height differences exceeding 10
+(3) Classification of Selection Types
+Configuration Parameters
+Description
+Selec Icon
+Offers a variety of icons to choose from
+Background
+Options: None, Circle
+Background Border Color
+Icon background color supports specific colors as well as
+Logic-driven colors include
+[Hostility] Enemies in red, friends in green, and self i
+[Follow Own Faction] Based on the current faction's 
+[Follow Owner's Faction] Based on the current entity
+Clickable
+When enabled, open the map and click on the marker to
+Text Content
+Click to set the text on the right
+Configuration Parameters
+Description
+Area Style
+Area's border can be displayed as a solid line or a dotted
+Color
+Icon background color supports specific colors as well as
+Logic-driven colors include:
+[Hostility] Enemies in red, friends in green, and self i
+[Follow Own Faction] Based on the current faction's 
+[Follow Owner's Faction] Based on the current entity
+Area Size (m)
+Displays proportionally in the Mini-Map UI Controls accor
+Configuration Parameters
+Description
+Style Preview
+Displays the point style which cannot be modified. Points
+Color
+Icon background color supports specific colors as well as
+Logic-driven colors include:
+[Hostility] Enemies in red, friends in green, and self i
+[Follow Own Faction] Based on the current faction's 
+[Follow Owner's Faction] Based on the current entity
+Configuration Parameters
+Description
+Style Preview
+The preview icon shows the creator's (Craftsperson's) cu
+nodes. Player markers cannot be clicked on the world m
+Background Border Color
+Icon background color supports specific colors and logic-
+Logic-driven colors include:
+[Hostility] Enemies in red, friends in green, and self i
+[Follow Own Faction] Based on the current faction's 
+[Follow Owner's Faction] Based on the current entity
+Icon Preview
+This can only be set for creations. Preview only, not edita
+Background Border Color
+Icon background color supports specific colors and logic-
+Logic-driven colors include:
+[Hostility] Enemies in red, friends in green, and self i
+[Follow Own Faction] Based on the current faction's 
+Clickable
+When enabled, open the map and click on the marker to
+Marker Name
+Name of the marker
+Text Content
+Click to set the text on the right
+III. Managing Mini-Map Markers Through Node 
+Graphs
+Batch modify the Mini-Map Marker states of target entities through the input list of mini-
+map marker IDs.
+Scan Tag
+Light Source
+Concept Introduction
+Functions
+Common Components
+Mini-Map Marker
+Click 
+ to add mini-map markers.
+
+Marker X, where X is an ID, can be used as a node input to adjust the initial 
+activation parameters of the mini-map marker.
+
+Icons
+
+AoE
+
+Marker
+
+Player's Marker
+
+Creation Icon
+
+Modify Mini-Map Marker Activation Status
+
+Modify Player List for Visible Mini-Map Markers
+
+Modify Player Markers on the Mini-Map
+
+Modify Mini-Map Zoom
+
+Modify Player List for Tracking Mini-Map Markers
+
+Query Specified Mini-Map Marker Information
+
+Get Entity's Mini-Map Marker Status
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh0ucw9e76f6.txt

@@ -0,0 +1,108 @@
+/
+/
+/
+Ability Units
+I. Definition of Ability Unit
+1. What is an Ability Unit
+Ability Units are a set of ability data predefined by creators (Craftspeople) during editing, 
+which can be called by multiple other functional modules at runtime, such as node 
+graphs, on-hit detection components, and local projectiles
+Includes the following types:
+Type
+Description
+Hitbox Attack
+Initiates a hitbox attack based on a specified target or 
+attack hitbox collides with an entity's hurtbox, it launch
+that entity
+Direct Attack
+Perform a direct attack on the specified target
+Play Special Effects
+Play a timed effect based on a specified target or loca
+Create Local Projectiles
+Create a local projectile based on a specified target o
+Add Unit Statuses
+Add Unit Statuses to the specified target
+Remove Unit Status
+Remove Unit Status from the specified target
+Destroy Self
+Destroy self
+Recover HP
+Restore a certain amount of HP for the target
+2. How to Use Ability Units
+Ability units are a set of pure data that has no functions on their own. Therefore, other 
+systems are needed to call these ability units to achieve their corresponding effects
+There are several entry points for ability unit call in the current mode. Note that each 
+entry point has different types of ability units available
+Call Type
+Description
+Server Node Graph Direct Call
+Directly initiate an ability unit call from the server node
+and can only use attack-related ability units.
+On-Hit Detection Component 
+Hit Event Call
+On-Hit Detection When hitting an entity or scene, Abil
+call can be triggered once
+Local Projectile Hit Event Call
+When local projectile hits an entity or scene, Ability Un
+be triggered once
+Local Projectile Destruction 
+Event Call
+When local projectile  is destroyed, Ability Unit call ca
+triggered once
+II. Editing Ability Units
+1. Entry Point for Ability Units Editing
+(1) Entry Point for Specialized Settings Tab Editing
+Click "Advanced Editing" to enter the details interface
+(2) Entry Point for Local Projectiles Tab Editing
+Click "Advanced Editing" to enter the details interface
+2. Editing Ability Units
+On the ability unit details editor tab, click the "+" icon to add a new ability unit setting
+You can then switch the ability unit type in the Ability Unit Type option
+3. Ability Unit Effects
+See Ability Unit Effects
+4. Ability Unit Call
+(1) Server Node Graph Node Call
+In the server node graph, you can call three ability units: [Hitbox Attack], [Direct Attack], 
+and [Restore HP]
+[Hitbox Attack] and [Direct Attack] are called using the [Initiate Attack] node
+Call the [Recover HP] behavior by calling the [Recover HP] node
+(2) Called When On-Hit Detection Component Registers a Hit
+The on-hit detection component can be configured with ability units that [Trigger on Hit]
+Click Details to enter the on-hit detection component details settings interface
+Click "Add Ability Units" to add pre-configured ability units
+When on-hit detection is successfully triggered, the configured ability unit will be called 
+immediately
+Compared to handling the same logic using the [When On-Hit Detection Is Triggered] 
+event in the server node graph, configuring in [On-Hit Trigger Settings] allows ability 
+units to trigger more quickly locally, reducing the impact of network latency
+(3) Called When Local Projectile Hits
+In the [On-Hit Detection] component of local projectiles, you can also configure ability 
+units that [Trigger on Hit]. Since local projectiles don't have node graph configurations, 
+most of the logic for local projectiles needs to be written through hit trigger logic
+As shown in the graph below, this is a common ability unit configuration where a local 
+projectile hits, plays VFX, and finally destroys itself
+Configure in order: the three ability units of Direct Attack - Play VFX - Destroy Self
+Then configure in the On-Hit Trigger Settings to make the local projectile deal damage, 
+play special effects, and finally make itself disappear upon impact
+(4) Called When Local Projectile Is Destroyed
+In the [Behavior Settings at End of Life Cycle] on the base attributes tab of the local 
+projectile, you can also reference a set of ability units
+Typically used for behaviors executed when a local projectile is destroyed, such as 
+initiating an attack upon destruction
+Combat Settings
+General Settings
+Concept Introduction
+Functions
+Specialized Settings
+Ability Units
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh29wpicgvh0.txt

@@ -0,0 +1,38 @@
+Before You Read
+I. Disclaimer
+The content in this comprehensive guide is currently in a testing phase and will be 
+supplemented and corrected periodically. If Creators (Craftspeople) notice areas for 
+improvement while reading, please submit feedback through the standard channels
+II. Content Introduction
+This guide consists of the following five sections
+1. Interface Guide
+This section introduces the interface features used when editing Stages, including how 
+to open them and how to use them Interface Guide
+2. Concept Introduction
+Explains the basic concepts Creators (Craftspeople) may encounter while editing their 
+Stages, along with their purposes and configuration methods Concept Introduction
+3. Support Function
+Introduction to various global checking functions used for load calculation and 
+detection Support Function
+4. Appendix
+Supplementary content to the main text, providing more detailed but lower-priority 
+information Appendix
+III. Special Symbol Description
+While reading the main text, you will see some text displayed in special colors or 
+marked with special symbols
+Among them:
+Red italics indicate basic concept terms. Each term has a specific, unique meaning
+Blue italics indicate concepts used in the Editing interface in this article
+Interface Guide
+Before You Read
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh2cr30yeak0.txt

@@ -0,0 +1,54 @@
+/
+/
+/
+Currency
+I. Definition of Currency
+Currency is a general item used in gameplay. It is used to determine the value of virtual 
+items and evaluate whether trades can be completed. Currency can be held by units 
+and will increase or decrease through trading or Node Graph logic
+II. Editing Currency
+Enter the editing interface through the [Currency and Inventory] button
+Enter the Currency tab to edit the currency details
+Currency Name: Name defined by the creator (Craftsperson) for the currency
+Configuration ID: Unique identifier for currency data
+Base Attributes
+Loot: Converted into loots and created in the scene
+Destroy: Currency is destroyed
+Save: Only applies to characters. Currency will be retained after character revival. 
+For units other than characters, this is equivalent to Destroy
+Shared Reward: All players share the same currency loot entity. Once one player 
+picks it up, other players can no longer pick it up
+Individualized Reward: Each player will have their own independent currency loot 
+entity generated locally, and players' pickup actions do not affect each other
+Equipment
+Inventory
+Concept Introduction
+Advanced Concepts
+Resource System
+Currency
+Icon: The display style of currency during gameplay. You can click the icon to 
+select one from prefabricated icons
+
+Destruction Debris: The logic executed when the currency owner is defeated
+
+Loot Drop Mechanics: When currency drops, it will be converted into an entity that 
+drops in the scene
+
+Corresponding Loot Appearance: Configure a loot prefab, which is a prefab with 
+physical properties. When a virtual item is created in the scene, it will be displayed 
+using the related loot model
+
+Display Priority : The higher the number, the higher the item will be displayed in the 
+inventory
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh2pir0hat1s.txt

@@ -0,0 +1,185 @@
+/
+/
+/
+On-Hit Detection
+I. Functions of On-Hit Detection Components
+On-Hit Detection Components can send hit events to the server node graph when the 
+hit area defined within the component encounters other entities or scene terrain 
+(including water surfaces). In most cases, this can be used to handle the function of a 
+projectile's hitbox
+It can also immediately trigger an ability unit (attack only) locally when the hit area 
+contacts other entities
+On-Hit Detection Components support multiple on-Hit detection areas taking effect 
+simultaneously, and their effective ranges will stack.
+A typical use case is using this component as a projectile's On-Hit Detection Box. It 
+determines when a projectile hits a target and processes post-hit events in the Node 
+Graph (such as dealing damage or playing special effects)
+II. Editing On-Hit Detection Components
+1. Add Components
+(1) In the Entity/Prefab Editing interface, open the Component Editing Tab
+(2) Click "Add Common Components" below, then click "On-Hit Detection" to add it
+(3) Click "Advanced Editing" to expand the editing tab
+2. Editing Hit Rules
+The parameters and their functions are as follows:
+Parameter
+Function
+Trigger Type
+Single Trigger: On-Hit Detection triggers only once dur
+event is sent to the Node Graph at most once during i
+Non-Repeating Trigger: For each hit entity, On-Hit Det
+Repeating Trigger: Can trigger multiple times, subject 
+wait for the trigger interval time before triggering again
+Trigger Interval
+Only configurable when trigger type is set to Repeatin
+Detection Delay Time
+When an entity is created, it will delay On-Hit Detectio
+Time].
+Common use is to prevent projectile-type objects from
+Enable Continuous Collision 
+Detection
+When enabled, activates Continuous Collision Detectio
+Continuous Collision Detection: When an entity is mov
+may result in "tunneling" (where the entity passes thro
+to large position differences between frames. Enabling
+speed movement
+CCD has a significant performance cost, so it is only r
+speed movement requiring precise hits)
+Continuous Collision Detection 
+Type
+Above Speed Threshold: CCD is only enabled when th
+optimize performance.
+Continuously Effective: Continuously effective, more pe
+Speed Threshold
+Only effective when CCD type is set to "Above Speed 
+velocity exceeds this value, which helps optimize perfo
+Detection Radius
+Continuous Collision Detection is implemented by gen
+frames to assist with collision detection. The detection
+recommended to keep it consistent with the actual rad
+used for detection instead
+Filter Node Graph
+Refer to Local Filter Node Graph: Used to determine w
+distinctions and usage of the two filters, see Node Gr
+together, the hit is considered valid only if both conditi
+The local filter will execute once every time a hit occu
+An explanation of the correspondence between th
+Output parameter is projectile entity.
+Output parameter is the entity that was hit.
+Output parameter is local character.
+Enable Filters Below
+When enabled, the filtering parameters below will be a
+all entities that can pass through the filter will be hit
+Faction Filter
+None: Does not hit entities of any faction.
+Hostile Faction: Only hits entities hostile to the project
+Allied Faction: Only hits entities friendly to the projectil
+Allied Faction Self Entity Included: Only hits entities fri
+Own Faction: Only hits the faction the projectile belong
+All Factions: Hits all factions, including self.
+All Factions Self Entity Excluded: Hits all factions, exc
+Entity Type Filter
+Multiple selectable options, including Objects, Charact
+Hit Layer Filter
+Multiple options can be selected. When multiple option
+when hitting an object with a hurtbox, two hit events m
+hurtbox.)
+Hurtbox: Only hits entities with hurtboxes.
+Scene: Hits scene colliders, in this case the On Hit De
+Object Self-Collision: On-Hit Detection triggered by co
+hurtbox value in the node graph's On-Hit Detection Tri
+Execute Ability Unit When Hit
+References a group of ability units, see Ability Units
+When on-hit detection is triggered, this group of ability
+3. Editing Hit Areas
+Click [Add Trigger Area] to add a new hit area configuration
+The On-Hit Detection Area is similar to the Collision Trigger . Multiple detection areas 
+can be configured, and when any detection area collides with an entity or scene, it will 
+trigger a on-hit detection event
+Parameter
+Function
+Trigger Area Shape
+Currently supports cuboid, sphere, and capsule detect
+Center
+Offset relative to the entity/prefab center
+Rotation
+Only configurable when a cuboid area is selected, the 
+Zoom Multiplier
+Only configurable when a cuboid area is selected, for 
+Radius
+Radius of the sphere/capsule
+Angle
+Can only be configured when a capsule area is select
+Height
+Can only be configured when a capsule area is select
+III. Using On-Hit Detection Functions in Node 
+Graphs
+Node Type: Event
+Node Functions
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Description
+Output 
+Parameter
+Event Source 
+Entity
+Entity
+Common event parameter, th
+Output 
+Parameter
+Event Source 
+GUID
+GUID
+Common event parameter, G
+Output 
+Parameter
+On-Hit Hurtbox
+Boolean
+Returns whether the entity's h
+Returns [Yes] when hitting an
+scenes or colliding with itself
+Output 
+Parameter
+On-Hit Entity
+Entity
+When hitting an entity's hurtb
+hitting scenes or colliding with
+Output 
+Parameter
+On-Hit Location
+3D Vector
+Returns the on-hit location, re
+Timer
+Extra Collisions
+Concept Introduction
+Functions
+Common Components
+On-Hit Detection
+Get Self Entity
+
+Get Target Entity
+
+Get Current Character
+
+Local filter example:
+
+When On-Hit Detection Is Triggered
+
+When the on-hit detection component collides with an entity or scene, it pushes a 
+[On Projectile Hit] event to the component owner's node graph
+
+Based on the [Trigger Type] configuration in the on-hit detection component, this 
+event may be triggered once or multiple times
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh2teu0bmfbc.txt

@@ -0,0 +1,166 @@
+/
+/
+/
+Deck Selector UI Controls
+The Deck Selector provides a simple interface for editing decision interactions
+Supports editing of decision-making content, including decision time, presentation of 
+decision options, interaction methods for decisions, etc.
+I. Deck Selector Functions
+During stage runtime, the Deck Selector can be invoked through default configurations 
+or the node graph.
+Supports player interaction, and send a Decision Pop-up Completion Event to the node 
+graph upon timeout or after interaction.
+II. Editing Deck Selector
+1. Add Deck Selectors
+2. Interface Configuration - Deck Selector
+This section configures the Deck Selector's overall appearance and usage rules, 
+allowing players to customize its display style
+(1) Visibility
+Configuration Parameters
+Description
+Index
+Parameters used to invoke the 
+Deck Selector node
+Initially Visible
+If unchecked, the UI control 
+will not be visible when 
+activated.
+This parameter can be 
+adjusted through the Node 
+Graph - Modify UI Control 
+Group Status.
+(2) Transform
+Configuration Parameters
+Description
+Location
+Supports manually entering the UI Control's location
+You can also adjust it by dragging the UI Control in the ed
+*Size
+Configuration not supported
+Layer
+The higher the number, the higher the display layer
+3. Interface Configuration - Decision Panel
+(1) Page Settings
+a. Visibility
+b. Deck Selector 
+Configuration Parameters
+Description
+Show Title
+When checked, the current Deck Selector w
+Title Text
+Supports editing the display title
+Interface Layout
+Provides two style options to choose from
+List
+Grid
+c. Show selected quantity
+Configuration Parameters
+Description
+Show Selected Quantity
+Determines whether to show the current number of selecte
+d. Show reset count limit
+Configuration Parameters
+Description
+Show Reset Count Limit
+Determines whether to show the minimum and maximum n
+e. Show Remaining Time(s)
+Configuration Parameters
+Description
+Show Remaining Time (s)
+If checked, the Deck Selector will automatically close when
+If the player completes the interaction before the countdow
+Decision Completion Style and Decision Completion Style 
+Pre-End Warning Time (s)
+When the countdown reaches the configured time, the time
+f. Other Settings
+Configuration Parameters
+Description
+Pause Game in Single-
+Player Mode
+If checked, the game will pause during the selection proce
+Controls can collapse
+If checked, the deck selector can be manually collapsed.
+You can choose to postpone handling, process it later, or w
+Selection can be canceled
+If checked, the Deck Selector can be manually closed. The
+support interactions.
+If closed, it triggers the node graph's Decision Completion 
+(2) Option Configuration
+a. Known Deck Settings
+Configuration Parameters
+Description
+Display Deck Icon
+Whether the displayed card includes an icon. If it does, the
+Display Deck Title
+Whether the displayed card includes a title. If it does, the i
+Display Deck Description
+ Whether the displayed card includes a description. If it do
+b. Unknown Deck Settings
+Configuration 
+Parameters
+Description
+Reveal result after 
+Selection
+After the decision is made, determine whether to play an anim
+Result Page Closing 
+Method
+Closes after the 
+countdown ends
+Additional configuration of countdown du
+Closed Manually 
+Requires manually closing the pop-up to 
+Countdown(s)
+After the decision is complete, the deck selector will automatic
+c. Deck Settings
+Use Edit Details to configure deck display
+Configuration 
+Parameters
+Description
+Deck ID
+Used for displaying the cards when invoking the Deck Selecto
+Increments sequentially starting from 1, cannot be modified
+Deck Types
+Known Deck
+Provides a clearly configurable icon
+Unknown Deck
+Provides only a question mark icon. Recom
+and Closes after the countdown ends
+Deck Icon
+This configuration will only be available when icon configuratio
+Deck Title
+Text Configuration
+Deck Description
+Text Configuration
+Tag Color
+Text Color
+Tag Description
+Text visible only to creators (Craftspeople) for record-keeping p
+III. Managing Deck Selector Through Node Graphs
+Scoreboard UI Controls
+Concept Introduction
+Assets
+UI Controls
+Deck Selector UI Controls
+In the UI Control Group Editor Window, add the UI control template - Deck Selector
+
+The Deck Selector is a default UI controls group
+
+Invoke Deck Selector
+
+Close Deck Selector
+
+When Deck Selector Is Complete
+
+Random Deck Selector Selection List
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh2xoxrop0la.txt

@@ -0,0 +1,166 @@
+/
+Units
+Units are individual entities that integrate data during both the editing process and 
+stage runtime.
+The in-game representation of a unit is called an entity.
+Entities that can run complex logic during stage runtime are called Dynamic Entities, 
+which have more Attributes and Components, and can use Node Graphs.
+Entities that can only be used for model placement and visibility settings are called 
+Static Entities.
+Each entity must be created based on predefined basic data, referred to as Prefabs.
+Dynamic entities and static entities are composed of their corresponding types of 
+prefabs.
+I. Basic Concepts
+All entities originate from corresponding prefab data. You can create explicit entity data 
+directly during the editing phase, or dynamically create entities based on specified 
+prefabs during runtime.
+In the Entity Placement tab, drag the prefab from the assets bar into the scene to 
+create an editable entity
+1. Entity
+The essence of an entity is an individual that integrates data, the in-game 
+representation of a unit, and is the minimal collection that carries functionality
+During game runtime, entities can serve as variable types for recording and passing
+Besides static entities, entities can be edited with additional specialized settings, 
+common components, and node graph functions
+2. Entity GUID
+For every editable entity in the editing scene (even those created from the same 
+prefab), there is a unique GUID
+GUID (Globally Unique Identifier) ensures that the entity can be precisely identified 
+through its GUID
+3. Prefabs
+Prefabs are essentially preset entity data
+All editable entities are created from prefabs
+4. Prefabricated Components and Custom Prefabs
+We provide a series of pre-made dynamic, static and enemy prefabs
+Additionally, players can modify prefabricated components and save them as custom 
+prefabs
+5. Prefab ID
+All prefabs have a globally unique prefab ID, but only dynamic prefabs and enemy 
+prefabs can generate runtime entities through node graph nodes
+II. Unit Types
+There are six types of units. Click the link for more detailed information
+Players
+Characters
+Creations
+Objects
+Local Projectiles
+Stages
+III. Entity Editing and Placement
+1. Naming and Indexing of Editable Entities
+In the entity placement tab, editable entities have globally unique entity names and 
+GUIDs
+2. Runtime Entity Naming and Indexing
+During runtime, runtime entities can be generated from editable entity data
+or by using node graphs with prefabricated components
+3. Entity Editing
+After entering the Entity Placement tab (A),
+in the current save file, the sidebar will display all Custom Prefabs (B) and 
+Prefabricated Components (C)
+You can drag prefabricated/custom prefabs from the "Dynamic," "Static," and "Enemy" 
+tabs into the scene for editing
+However, you cannot switch between static and dynamic types through the entity panel
+When clicking on an editable entity, the following tabs will appear on the right. For static 
+entities, only the basic information panel
+ can be edited. If you try to switch to 
+other panels, you will receive a message that they cannot be edited
+4. Basic Information Panel
+This section displays a set of non-removable base attributes for this entity type. 
+Attributes may vary across different entity types. You can only modify the attributes 
+possessed by this entity type here.
+5. Specialized Setting Panel
+Provides basic combat attributes, aggro configuration, hurtbox settings, combat settings, 
+ability units and other content to add combat-related logic to entities
+6. Common Component Panel
+Common Components  are a primary way to add functions to entities. You can add, 
+remove and edit components to give entities more functions during runtime
+Some entity types come with pre-mounted components in the component panel. These 
+can be freely added, removed, or edited as needed
+7. Node Graph Panel
+Node graphs are custom logic scripts created by creators (Craftspeople). You can use 
+this panel to add, delete, and edit node graphs to enable additional functions for running 
+entities
+IV. Prefab Editing
+Select (A) to enter the prefab library interface
+In the prefab library, you can create custom prefabs to assist with stage building
+After entering the prefab library (A),
+click the Object Icon (B) on the status bar to access the object prefab panel; click the 
+Creations Icon (C) to access the creations prefab panel; click the Loot Icon (D) to 
+access the loot prefab panel
+You can organize your tabs based on personal preferences to manage the prefabs 
+you've created
+You can drag prefabricated components from the Dynamic and Static tabs (E) into the 
+scene for editing
+1. Naming and Indexing
+Prefabs must have globally unique names (F) when being saved
+After saving, the prefab will generate a globally unique prefab ID (G)
+You can change the prefab to dynamic or static via the dropdown menu (H)
+The prefab provides four tabs for adding functions (I), arranged from left to right:
+2. Basic Information Panel
+This section displays a set of non-removable attributes for this prefab type. Attributes 
+may vary across different prefab types. You can only modify the attributes specific to 
+this prefab type here
+3. Specialized Setting Panel
+Add combat-related logic to prefabs by providing basic combat attributes, aggro 
+configuration, hurtbox settings, combat settings, and ability units
+4. Common Component Panel
+Common Components  are a primary way to add functions to entities. You can add, 
+remove and edit components to give prefabs more functionality
+Some prefab types come with pre-mounted components in the component panel. These 
+can be freely added, deleted, and edited
+5. Node Graph Panel
+Node graphs are custom logic scripts created by creators (Craftspeople). You can add, 
+remove, or edit node graphs in this panel to enable additional functions for prefabs
+6. Saving Prefabs
+After modifying the prefabricated component, you can click the Save button at the 
+bottom of the screen to store it as a custom prefab and place it under the specified tab
+If you are modifying a custom prefab you can click Overwrite and Save Prefab to 
+update the original custom prefab, or click Save As Prefab to save it as a new custom 
+prefab
+Both dynamic and static prefabs can be dragged into the scene as editable entities on 
+the entity placement tab, after which runtime entities can be created during runtime
+Specifically, dynamic prefabs and creation prefabs can be created as runtime entities 
+directly through the node graph node [Create Prefab] during runtime
+In most cases, editable objects placed in the scene are called editable entities
+They are created by dragging prefabs into the scene under the entity placement tab
+V. Creating Temporary Entities
+Use the [Create Prefab] node in the node graph to create running entities directly from 
+prefabs during gameplay
+These are called temporary entities. Unlike regular entities, they lack an editor-based 
+GUID but otherwise function the same
+VI. Concept and Placement of Static Entities
+Static entities are entities that cannot be edited with additional attributes, components, 
+or node graph functions. Players cannot access them during runtime and can only use 
+them for decoration and scene layout
+Static entities cannot be created as temporary entities via the [Create Prefab] node. 
+They can only be created by making static prefabs first and then dragging them into the 
+scene under the entity placement tab
+Functions
+Concept Introduction
+Units
+You can drag and drop prefabricated components directly to create entities, edit 
+them and build stages
+
+You can also create custom prefabs in the prefab library first, then drag out your 
+custom prefabs to create entities, and proceed with editing and stage building
+
+Prefabs can be created as editable entities by dragging them into the scene from 
+the Entity Placement tab
+
+Through the node graph node [Create Prefab], you can create dynamic entities or 
+monster entities during runtime
+
+After dragging a prefab into the scene and successfully creating an entity from it, 
+any modifications made to the entity will be completely independent of the prefab 
+that created it
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh333vim2h44.txt

@@ -0,0 +1,137 @@
+/
+/
+Path
+I. Path Functions
+Path is a feature that combines one or more waypoints, which contain only position and 
+rotation information, into a set of path information.
+The waypoint information in the path consists of world coordinates and rotation. Its data 
+content will not be adjusted when referenced.
+Paths can be referenced by any supported functionality, which currently includes the 
+Not-in-Battle - Patrol feature of creations and the stage path movement of the basic 
+motion device component.
+II. Path Management Tool Functions
+Paths are managed uniformly through the Path Management Tool
+Add or delete paths and edit the data within them
+Manage the tabs that organize paths
+III. Editing Paths
+1. Entry Points
+Open the System menu in the top left corner and select Path Management to open the 
+Path Management Tool
+2. Tool Display Interface
+Divided into the path management bar and the path configuration bar
+(1) Path Management Bar
+Create a new path by 
+ creating a path
+Newly created paths are assigned to the *Uncategorized tab by default
+It uses the screen center point as the first waypoint of the path
+Select the *Uncategorized tab's 
+ to add a new tab and name it
+New tabs are empty by default. Assign paths to a tab and right-click *Change Tab to 
+adjust tabs where paths are located in for easier management
+(2) Path Configuration Bar
+Configuration 
+Parameters
+Description
+*Name
+The path name used for identification must be unique and can be
+Index
+Unique identifier for the path, can be used as a node graph input 
+Configuration 
+Parameters
+Description
+*Lock Transform
+When enabled, waypoints on this path can only be added or delet
+be adjusted
+*Display in Scene
+When enabled, all of a path's waypoints and their connection orde
+*Path Center Point 
+Location
+The center point position of the path. This position maintains a co
+waypoints. Therefore, modifying this position will affect the positio
+path
+*Path Center Point 
+Rotation
+The center point rotation of the path. This rotation maintains a con
+waypoints. Therefore, modifying this rotation will affect the rotation
+path
+Configuration 
+Parameters
+Description
+Location
+Parameters can be manually adjusted to adjust waypoint position
+Rotation
+Parameters can be manually adjusted to adjust waypoint rotation
+*Add Waypoint
+Click to create a new waypoint
+*Free Placement
+Clicking clears the interface. Place new waypoints in the scene us
+Use
+ to end placement
+Click the button on the right side of the waypoint
+ to expand auxiliary editing
+Configuration Parameters
+Description
+Tangent pointing to the 
+destination
+Adjust waypoint rotation to point to the next waypoint
+Tangent pointing to the 
+starting point
+Adjust waypoint rotation to point to the previous waypoint
+Select All Waypoints on 
+Path
+Select all path points on this path. Disabled if no path points
+Add Waypoint toward 
+the destination
+Adds a new waypoint after the selected point's number.
+For example, adding a waypoint after waypoint 2 will create 
+Add Waypoint toward 
+the starting point
+Adds a waypoint before the current point's number.
+For example, when adding a preceding waypoint at waypoin
+waypoint 3
+Copy
+Copy the waypoint's coordinates and rotation information
+Paste
+Paste the copied waypoint's coordinates and rotation informa
+Delete this waypoint
+Delete the specified waypoint
+Configuration 
+Parameters
+Description
+*Creation 
+Reference
+Displays the number of references to this path
+Can locate creations that reference this path
+*Object Reference
+Displays the number of references to this path
+Can locate objects that reference this path
+III. Managing Paths Through Node Graphs
+Shield
+Concept Introduction
+Advanced Concepts
+Path
+New Path
+
+Management Tabs
+
+Index and Name
+
+Basic Configuration
+
+Waypoint List
+
+Reference Source
+
+Get Specified Waypoint Info
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh3ecor1x5cm.txt

@@ -0,0 +1,65 @@
+/
+/
+Character
+Unlike player entities ,  character entities refer to the actual units that players control 
+during the game, such as walking, running, climbing, and flying units with physical 
+presence
+1. Character Template
+In Beyond Mode, players and characters are mapped one-to-one, so the template 
+configuration of characters exists as part of the player template, which can be 
+accessed under the character editing tab in the player template:
+Tab Overview:
+: Basic Information Tab, where the Character section contains only 
+sound effect-related information compared to other entities.
+ Specialized Configuration Tab, where the Character section contains 
+only combat-related parameters compared to other entities.
+: Components tab, where you can add components to character 
+entities or view existing components
+: Node graph configuration tab, where you can add node graphs to 
+character entities or view the node graphs that have been added
+II. Overview of Available Components for 
+Character Entities
+Collision Trigger
+Custom Variables
+Global Timer
+Unit Status
+VFX Playing
+Custom Attachment Points
+Collision Trigger Source
+Sound Effect Player
+Inventory
+Loots
+Nameplate
+Text Bubble
+Scan Tag
+Mini-Map Marker
+Additionally, there are equipment slot components that can only be added to characters
+For details, please see Equipment
+III. Runtime Characteristics
+Player
+Creations
+Concept Introduction
+Units
+Character
+During gameplay, characters are dynamically initialized based on template 
+configurations, therefore character entities do not have corresponding GUID
+
+Notably, when a character's HP reaches zero, the node graph on the character 
+entity can receive both the Entity Destroyed event and the Entity 
+Removed/Destroyed event. In contrast, when an object is destroyed, the event will 
+be dispatched to the stage entity.
+
+During the Co-Op Mode gameplay, if a player actively returns to the lobby, the 
+stage will receive the character's removal event
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh3fmi0t99ns.txt

@@ -0,0 +1,154 @@
+/
+/
+Structure
+I. What is a Structure
+A Structure is an advanced data type that lets Creators (Craftspeople) group different 
+kinds of data together into a single piece of Custom data
+For example, in some gameplay scenarios, a Creator (Craftsperson) may design a 
+[Weapon] with multiple Attributes. This Weapon includes three fields: [Name], [ATK], and 
+[Enhanced or Not]
+Creators want Players to store a weapon's data as Custom Variables after obtaining it, 
+so it can be reused later. Meanwhile, Players may acquire multiple different weapons 
+that share the same fields during gameplay
+Therefore, Structure can be used to effectively solve this requirement
+Creators (Craftspeople) first define a Structure called [Weapon Data] with three 
+Attributes: [Name] (String), [ATK] (Floating Point Numbers), and [Enhanced or Not] 
+(Boolean)
+Once defined, [Weapon Data] can then be used like any other data type — for example, 
+as a Custom Variable, and modified within a Node Graph using Nodes such as Modify 
+Structure
+Creators (Craftspeople) can also combine it with data structures such as Dictionary to 
+maintain complete weapon data in Custom Variables
+As shown in the graph below, a Dictionary can be defined to map to [Weapon Data] 
+Structures, functioning as a weapon database (with Integers used as IDs)
+1. Definition of Structure
+Structure is a Custom data structure that can be used in Server Node Graphs
+Each Structure has a unique name that identifies it
+Each Structure can contain multiple data entries of any type, and each entry must have 
+a unique field name. These entries are called Members of the Structure
+Taking the [Weapon Data] Structure as an example, its layout is as follows:
+Field Name
+Type
+Name
+String
+ATK
+Floating Point Numbers
+Enhanced or Not
+Boolean
+Within a Structure, you can use all currently available data types: Basic, List, Dictionary, 
+and Structure:
+Data Types
+List Data Types
+Entity
+Entity List
+GUID
+GUID List
+Integer
+Integer List
+Boolean
+Boolean List
+Floating Point Numbers
+Floating Point Numbers 
+List
+String
+String List
+Faction
+Faction List
+3D Vector
+3D Vector List
+Prefab ID
+Prefab ID List
+Configuration ID
+Configuration ID List
+Custom Structure
+Custom Structure List
+Dictionaries of All Types
+It should be noted that Structures can also contain other Structures and Structure Lists 
+(i.e., support nested Structures)
+2. Key Points of Structure-Related Functions
+The type of a Structure is completely determined by its name. Even if two Structures 
+have identical internal data layouts, they are considered different Structures if their 
+names differ, and cannot be connected in a Node Graph
+Therefore, structures with the same name are not allowed
+Similar to Lists, Structures in Node Graphs are passed by reference. As a result, 
+Structure modification Nodes directly affect Structure data stored in Custom Variables 
+and Node Graph Variables. For details, see Custom Variables
+Similarly, in the When  Custom Variable Changes Event, the fields [Pre-Change Value] 
+and [Post-Change Value] are not provided. Use Get Custom Variable to obtain the 
+updated Value
+II. Creating a Structure
+Find the [Advanced Data Management] option in the menu to open the Structure Editing 
+Tab
+In the Structure Editing Tab, you can view Structures already created in the Stage, add 
+new Structures, and edit the values of Structure Members
+You can add new Structures, as shown in Graph A
+You can add new Members within a Structure, as shown in Graph B
+After creation is complete, you can use the defined Structures in features such as 
+Server Node Graph, Custom Variables, and Node Graph Variables
+III. Using Structures in Generics
+In a Server Node Graph, Structures and Structure Lists are special types of Generic 
+Pins. You must select a specific Structure or Structure List before the corresponding 
+Node can be defined as that Structure or Structure List type
+On Generic Pins that support Structures, you can find [Structure] and [Structure List] 
+options in the Generic dropdown menu. Expanding this menu displays all Structure data 
+types currently defined in the Stage
+IV. Structure-Related Nodes
+1. Operation Nodes
+Assemble Structure
+Assemble a Structure by passing in or directly assigning values to each of its parameters
+To use this Node, first select the defined Structure type via the Generic selection button
+After selecting the corresponding Structure, the Node displays all Member variables 
+defined in that Structure
+Node Type: Operation
+Node Functions
+Split Structure
+Pass in a Structure to obtain the values of each Member within it
+To use this Node, first select the defined Structure type via the Generic selection button
+After selecting the corresponding Structure, the Node displays all Member variables 
+defined in that Structure
+Node Type: Operation
+Node Functions
+2. Execution Nodes
+Modify Structure
+Pass in a Structure and edit the values of selected Members within it
+To use this Node, first select the defined Structure type via the Generic selection button
+After selecting the corresponding Structure, the Node changes to the following layout:
+Use the dropdown menu to choose which Members to edit. Only the checked Members 
+will have their values modified
+As shown in the graph below, only the values of [Name] and [ATK] fields are modified
+Node Type: Execution
+Node Functions
+Dictionary
+Appendix
+Node Graph Advanced Features
+Structure
+Structure Types
+
+Pass by Reference for Structures
+
+Fill in the values for each parameter in the Structure to generate Structure data
+
+This Node can only be used once the corresponding Structure type has been 
+defined
+
+Returns the values of all Members contained in the input Structure data
+
+This Node can only be used once the corresponding Structure type has been 
+defined
+
+Edit the values of selected Members within the Structure data
+
+You can select which values to edit. Values of unselected Members remain 
+unchanged
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh3oxo0ojgxk.txt

@@ -0,0 +1,31 @@
+/
+/
+Basic Information
+The entity's basic information refers to characteristics or data related to the entity 
+model and position.
+During gameplay, basic information can be read or modified, but cannot be added or 
+deleted.
+I. Editing Basic Information
+Basic information is located under the Basic Information tab in the prefab settings.
+II. Overriding Basic Information
+When creating a prefab, you can specify its basic information. When converting the 
+prefab into an entity and placing it in the scene, the prefab's basic information will be 
+automatically applied. However, basic information on an entity can be changed. When 
+changing an entity's basic information, the prefab's basic information will not change.
+III. Differences in Basic Information
+Different types of prefabs will have different basic information available.
+Specialized Settings
+Concept Introduction
+Functions
+Basic Information
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh3pgiraqkiu.txt

@@ -0,0 +1,52 @@
+/
+/
+Stage
+Stages are special entities recommended for handling stage-specific logic.
+I. Creating a Stage Entity
+When a new stage is created, a stage entity is automatically generated in the scene 
+and represented by a unique icon.
+II. Edit Stage Entities
+Switch to the Entity editing tab.
+Editing stage entities is similar to other types of entities, but the configurable basic 
+information and components will be different.
+1. Basic Information
+Basic Information tab, where you can configure all available attributes for the stage 
+entity.
+2. Common Components
+Common Components tab, where you can add common component settings to stage 
+entities.
+Overview of Available Components for Stage Entities:
+Custom Variables
+Global Timer
+3. Node Graph
+Node Graph Settings Tab, where you can add node graphs to stage entities or view 
+existing node graphs.
+III. Stage Characteristics
+Unlike other entity types, stage entities have the following unique characteristics:
+1. Can Receive Special Events
+Some special events can only be received by stage entities, including:
+When object or creation-type entities are removed/destroyed, those entities cannot 
+receive the corresponding events, which will instead be forwarded to the stage entity.
+The subsequent logic will be processed by the stage entity as well.
+2. Non-Physical Entity
+The stage entity is a purely logical entity.
+3. Incomplete Placement Information
+Stage entities only have position information. They lack rotation and scale information.
+4. Life Cycle
+Stage entities are created when the stage initializes and destroyed when the stage is 
+removed.
+Local Projectiles
+Concept Introduction
+Units
+Stage
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh3rgo0c16c8.txt

@@ -0,0 +1,367 @@
+/
+/
+/
+General Settings
+I. Definition of General Settings
+Creation-specific settings are divided into Behavior Modes, Not-in-Battle Behavior, and 
+Battle Areas
+II. Edit General Settings
+1. Behavior Mode
+Supports Behavior Mode selection for Creation Entities. At runtime, Entities will 
+autonomously perform actions such as movement, battle entry and exit based on the 
+configured Behavior Mode
+Creation Behavior Mode Full Enumeration Details: Creation Behavior Mode Archive
+Configuration 
+Parameters
+Description
+Behavior Modes
+Can be selected from the enumerated options in the pre-provided
+Each Behavior Mode provides different optional actions for both in
+situations, causing the Creation to autonomously display different 
+2. Not-in-Battle Behavior
+Configuration 
+Parameters
+Description
+Not-in-Battle 
+Behavior
+Rules for creations while out of battle..
+Each mode has its own Not-in-Battle behavior pool
+3. Battle Area
+Configuration 
+Parameters
+Description
+Battle Area
+An entity's autonomous detection of hostile entities. If detection su
+the detected entity as its target
+All behavior modes include: Range Detection and FOV Detection
+*Preview Battle 
+Area
+Enable to observe Horizontal Range of Battle Area
+*Behavior 
+Description
+Behavior Mode Introduction
+4. Details Editor
+(1) Details Editor - Not-in-battle
+Rules to be followed when a Creation Entity is running but has not yet entered the battle
+For all not-in-battle behaviors, please refer to Not-in-Battle Behavior
+Editable Not-in-Battle behaviors include Wandering  and Patrolling
+a. Wandering
+A behavior supported by all Creations when not engaged in a battle
+During stage runtime, when Creations are not in battle, they will move randomly within 
+their Territory Range
+Configuration 
+Parameters
+Description
+Movement Area
+A range centered on the creation's spawn coordinates
+At runtime, the creation randomly moves to points within this r
+Only spherical shapes are supported
+Area Radius (m)
+The radius of the spherical movement area
+*Preview Movement 
+Area
+When enabled, the configured Wandering Area Range can be
+Movement Interval (s)
+Randomly selected within the configured time interval. After ea
+duration before moving again
+Single Movement 
+Distance (m)
+Randomly selected within the configured distance for each mo
+b. Patrol
+Some Creations support configuring patrol behavior when not in battle
+Configuration Parameters
+Description
+Initial Effective Patrol 
+Template
+The drop-down menu enumerates patrol templates for this 
+Use the checkbox to toggle whether it's active; changes sy
+*Patrol Template List
+Enumerates all patrol templates configured for this creatio
+Open the Details Editing Tab to create a new patrol template or edit the existing ones
+Add Patrol Templates
+For newly added patrol templates, Initially Effective is off by default.
+Configuration Parameters
+Description
+Initially Effective
+If enabled, this patrol template takes effect when the creatio
+Only one patrol template can be active per creation at a tim
+Loop Type
+One-Way
+The creation follows the path to the final w
+Round Trip
+Upon reaching the final waypoint, the crea
+reaches the first waypoint
+Loop
+After reaching the final waypoint, the creat
+Patrol Start Position
+Choose which waypoint the creation uses to begin its patrol
+Nearest point
+The closest waypoint in the selected patro
+Starting point
+The first waypoint in the selected patrol tem
+Patrol Path Configuration
+Editing Patrol Path Template
+Configuration Parameters
+Description
+Patrol Path
+Select the pre-configured paths from the path management 
+*Open Path 
+Management Tool
+Redirects to the Path Management Tool
+Patrol Path Waypoint Configuration
+Configuration Parameters
+Description
+*Waypoint
+Waypoint X: Use X as a node parameter to read the waypoi
+Travel Speed
+Offers Walk and Run as movement speed options
+Arrival Detection Radius 
+(m)
+If the creation is within the configured radius of a waypoint, 
+Stay Duration(s)
+How long the creation remains in place after reaching the w
+Turn After Reaching 
+Waypoint
+If enabled, the creation turns to match the waypoint's rotatio
+Notify Node Graph on 
+Arrival
+If enabled, upon arrival the creation sends a [Creation Reac
+*Show Waypoint 
+Information
+If enabled, you can view the waypoint's position and rotation
+(2) Details Editor - Combat
+Rules for Creation Entity behavior when targeting a Character and preparing 
+for/engaging in a battle
+The basic configuration is consistent across different Behavior Modes, and here we'll 
+explain all the parameters that have appeared so far.
+a. Battle Entry Settings
+At runtime, configure a creation entity's rules for how to detect hostile entities, detection 
+distance, and relationship settings
+Configuration 
+Parameters
+Description
+Detection Range
+When hostile entities are within this range, the creation can ob
+information and target that entity to enter battle
+*Preview Range
+When enabled, you can view the Detection Range of the edite
+Window
+Configuration 
+Parameters
+Description
+FOV Type
+Provides Full FOV and FOV Cone enumerations, and shape 
+change accordingly after selection
+Configuration 
+Parameters
+Description
+FOV Cone - Cone 
+Distance
+Configure the radius distance of the FOV Cone
+Full FOV - FOV 
+Detection Radius
+Configure the sphere radius
+*Preview Range
+When enabled, you can view the FOV Detection Range of the
+Edit Window
+Coordinated 
+Engagement Distance 
+(m)
+When a Creation enters a battle, other Creations within this di
+will also join the battle
+b. Battle Exit Settings
+When the creation entity is running, and has entered battle with hostile entities, 
+configure the creation's automatic out-of-battle rule settings
+Configuration 
+Parameters
+Description
+Out-of-Battle Distance 
+(m)
+When a creation is in battle, if the distance to its target entity 
+distance, the creation will leave battle
+*Preview Out-of-Battle 
+Distance
+When enabled, you can view the configured distance
+Leave Battle on 
+Pathfinding Failure
+When a creation is in battle and there is no valid path to its ta
+leave battle
+Leaving Battle Delay 
+(s)
+When a creation is in battle and there is no valid path to its ta
+after the configured Leaving Battle Delay
+c. Territory Settings
+Configuration 
+Parameters
+Description
+Territory
+Supports configuration of none, sphere, or cylinder, with size p
+The Territory is centered at the created Location of the Creatio
+Location with Creation movement
+The Creation's movement range is restricted within the Territo
+*Preview Territory 
+Range
+When enabled, you can view the configured Territory Range
+Leave Battle When 
+Player Leaves Area
+When enabled, if the target entity leaves this area, the creatio
+Leaving Battle Delay 
+(s)
+After the target entity leaves the territory range, the creation w
+specified delay
+(3) Details Editor - Skills
+Some of the logic parameters of certain creations can be configured by the creator 
+(Craftsperson) to adjust the behavior and logic during runtime. 
+For example, as shown in the figure for the [Abyss Mage], the Powerful Elemental 
+Ward parameter is provided. By modifying this parameter, the creator can adjust the 
+elemental value of the creation's Ward.
+Enumerates some of the Creation's skills, which support a certain degree of adjustment 
+to their cooldown times.
+Configuration 
+Parameters
+Description
+*Skill Name
+Currently provides editing for some melee skills, ranged skills,
+Enable This Skill
+When enabled, if the Creation's Behavior Mode includes this s
+otherwise, this skill will not be used
+Initial CD Range (s)
+A random time within the configured range will be set as the E
+After the creation is created, it will start using this skill only aft
+Time has elapsed
+Default CD Range (s)
+A random time within the configured range will be set as the a
+After the Creation uses this skill, it cannot use it again during 
+Complete enumeration details of Creation Skills: Creation Skills Description
+III. Managing Creation Patrol via Node Graphs
+If, in Patrol Template editing, the Send Node Graph Event on Arrival Event option is 
+checked for a specified waypoint, the Node Graph Event will be received when the 
+conditions are met
+This Node Graph Event can only be received by the creation's node graph
+Configuration 
+Parameters
+Data Type
+Description
+Creation Entity
+Entity
+The creation entity during runtime
+Creation GUID
+GUID
+The GUID of the creation, outputs empty if n
+Current Patrol 
+Template ID
+Integer
+The currently active patrol template ID for th
+Current Global Path 
+ID
+Integer
+The Global Path ID referenced by the creati
+Current Waypoint ID
+Integer
+The current waypoint ID reached by the cre
+Next Waypoint ID
+Integer
+The waypoint ID the creation will move to ne
+Configuration 
+Parameters
+Data Type
+Description
+Creation Entity
+Entity
+The creation entity during runtime
+Patrol Template ID
+Integer
+The configured patrol template ID for the cre
+Configuration 
+Parameters
+Data Type
+Description
+Creation Entity
+Entity
+The creation entity during runtime
+Patrol Template ID
+Integer
+Currently active patrol template ID for the cr
+Global Path ID
+Integer
+Global Path ID referenced by the creation's 
+Target Waypoint ID
+Integer
+The waypoint ID the creation will move to ne
+Output lists for this node are only correct when the hostility configuration is set to 
+[Default Type].
+Configuration 
+Parameters
+Data Type
+Description
+Creation Entity
+Entity
+The creation entity during runtime
+Aggro List
+Entity List
+Which entities the creation currently has hos
+Depending on the creation's current behavior, the target entities may differ. 
+For example, when the creation is attacking an enemy, the target is a specified enemy 
+entity. 
+For example, when the creation is healing an ally, the target is a specified allied entity.
+Configuration 
+Parameters
+Data Type
+Description
+Creation Entity
+Entity
+The creation entity during runtime
+Target Entity
+Entity
+The creation's current AI selects the target e
+Ability Units
+Concept Introduction
+Functions
+Specialized Settings
+General Settings
+The Behavior Modes of Creation Entities can be configured and switched through 
+enumeration selection
+
+After selecting a Behavior Mode, you can choose the Not-in-Battle Behavior.
+
+After selecting a Behavior Mode, you can choose the Battle Area.
+
+Through "Details Editor", you can adjust and configure more parameters for not-in-
+battle and battle behaviors.
+
+Click 
+ to add a patrol template.
+
+Template X, where X is the ID; use it as a node input to switch patrol templates.
+
+Select the pre-configured paths from Path for reference.
+
+Detection Range
+
+FOV Detection
+
+Basic Settings
+
+Skill Settings
+
+1.
+When Creation Reaches Patrol Waypoint
+2.
+ Switch Creation Patrol Template
+3.
+ Get Current Creation's Patrol Template
+4.
+Get Aggro List of Creation in Default Mode
+5.
+Get Creation's Current Target
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh4ppo02m1o8.txt

@@ -0,0 +1,82 @@
+/
+/
+/
+VFX Playing
+1. Functions of VFX Playing Components
+The VFX Playing component contains two parts of functions
+1. Effects played through the node graph must rely on the VFX playing component. 
+Without this component, effects cannot be played through the node graph
+2. Default looping effects can be mounted through components, and these effects will 
+be created along with the entity
+Multiple effects can be active simultaneously on the VFX Playing Component
+II. Editing VFX Playing Components
+1. Adding VFX Playing Components
+(1) Switch to the Components tab of the entity or prefab
+(2) Find or add a VFX playing component
+The VFX Playing component is a default mounted component for all units (i.e., it is 
+mounted by default when an entity is created). Therefore, for newly created entities or 
+prefabs, you can find the Effect Player component directly in the Components tab
+If it doesn't exist, you can add a new VFX playing component through the Add Common 
+Components button
+2. Add VFX Play
+On the "Details" tab of the VFX Playing component, press [Add Special Effects] to add 
+a new effect configuration
+3. Configure VFX Playing
+Parameter Name
+Parameter Description
+VFX Player ID
+The sequence number of the VFX Player
+VFX Player Name
+The name of the VFX Player, which cannot be duplica
+VFX Asset Type
+Choose between Looping Effects and Timed Effects, 
+For effect-related assets, see Special Effects
+Special Effects Asset
+You can select Special Effects Asset. After selecting a 
+Follow Location
+Whether to move along with the component owner
+Follow Rotation
+Whether to rotate with the component owner, only take
+Attachment Point
+The attachment point where the effect plays. You can 
+attachment points configured on the entity
+Zoom Factor
+Zoom multiplier of the effect
+Offset
+The offset of the VFX's playing position relative to the 
+Rotation
+The rotation of the VFX's playing position relative to th
+Local Filter
+Refer to Local Filter Node Graph: Used to determine w
+specific distinctions and usage of the two filters, see N
+perform checks while the entity with the effect is prese
+Here is an explanation of the basic nodes in the local 
+Unit Status
+Custom Attachment Points
+Concept Introduction
+Functions
+Common Components
+VFX Playing
+Get Self Entity
+
+Output parameter: The entity that has the effect g
+
+Get Target Entity
+
+No output parameter.
+
+Get Current Character
+
+Output parameter: The local character.
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh57xz9afh7e.txt

@@ -0,0 +1,29 @@
+/
+/
+Skill Animation
+I. Definition of Skill Animation
+Skill animations are animation assets created for combat actions performed by entities
+II. Characteristics of Character Skill Animations
+Character skill animations require a character entity as their base, and each skill 
+animation playback must have a specific character entity as its carrier.
+Character skill animations depend on the activation of custom skills.
+III. Character Skill Animation References
+When editing skills, you can reference character skill animations to define the animation 
+effects that play after the skill is cast.
+For specific reference methods, please refer to Skills
+Preset Status
+UI Controls
+Concept Introduction
+Assets
+Skill Animation
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh5jko05fzyw.txt

@@ -0,0 +1,119 @@
+/
+/
+/
+Tab
+1. Tab Component Functions
+The Tab component enables players to configure and interact with dynamic objects and 
+creations
+After adding this component to an entity, it supports configuring and applying multiple 
+tabs simultaneously
+Each tab supports using a local filter to determine visibility for each player
+The entity type that triggers the tab function is Character
+II. Editing Tab Components
+1. Add Components
+(1) In the entity/prefab editing interface, open the Editing Components tab (A)
+(2) Click "Add Common Components" below, select and click "Tab" to add (B), (C) 
+successfully
+When "Tab" is selected, the entity being edited will display the tab trigger area with 
+a blue border
+(3) Click "Advanced Editing" to expand the editing tab (D)
+2. Editing Tabs
+(1) Basic Tab Information
+Configuration Parameters
+Description
+Initially Effective Tab
+The dropdown menu provides tab enumeration
+By modifying the checkbox behind, you can change the eff
+modification, the effective status will be synchronized to the
+*Tab List
+Enumerate all tabs of entity configuration.
+Click to
+toggle the visibility status of a tab in the editing window. 
+Effective only during editing
+Click "Advanced Editing" to enter the tab list and trigger area configuration interface
+(2) Tab List
+Click "Add Tabs" to create a new tab
+Option ID  ID X. Can be used for node graph input parameter to adjust whether tab is 
+in effect
+Option Tab Icon Click
+ to switch the icon in front of the tab.
+Initially Effective   If enabled, this option tab takes effect immediately upon entity 
+creation. An effective tab is visible and can be selected for operation
+Sort Level   Controls the display order of option tabs. The higher the number, the 
+further forward it appears
+Local Filter  There are two types of filters: Boolean filters and integer filters. See Node 
+Graphs  for details. 
+Filter Node Graph   You can refer to the filter node diagram of the above selection types 
+to determine whether the tab meets the display conditions.
+The following is an example using a Boolean filter:
+The local filter continuously monitors while the character is within the effective 
+range. If the result changes, it updates the display immediately.
+Explains the basic nodes in the local filter node graph
+The output parameter is the entity where the tab component is mounted
+When the character is within range, this node outputs parameters for the character 
+entity that is effective within the tab range
+Output parameter is the local character
+(3) Trigger Option Area
+Press the "Add Trigger Option Area" button to create a new trigger area
+Configuration Parameters
+Description
+Trigger Area Shape  
+Supports cuboid, sphere, and capsule shapes. Different siz
+parameters will be displayed based on the selected shape
+Center
+Offset relative to the entity/prefab center
+Rotation
+Supports orientation adjustment along different axes based
+position
+Zoom Multiplier
+The trigger area's shape supports defining scaling along di
+III. Manage Tabs Through Node Graph
+Enter the Tab ID to control whether the tab is enabled or not
+When the active tab is selected, it will send an event to the node graph
+The entity node graph configured by the tab component will receive this event
+Configuration Parameters
+Description
+Event Source Entity
+The entity where the tab component is mounted
+Event Source GUID
+The entity with mounted tab components, outputs 0 if none
+Tab ID
+Tab ID
+Selector Entity
+Character entity that triggers tab
+Basic Motion Device
+Concept Introduction
+Functions
+Common Components
+Tab
+Add New Tabs
+
+Editing Tabs
+
+Get self entity
+
+Get target entity
+
+Get Current Character
+
+Example
+
+Add Trigger Areas
+
+Trigger Areas
+
+Activate/Disable Tab
+
+When the tab is selected
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh5n160t2b6w.txt

@@ -0,0 +1,323 @@
+/
+/
+/
+Nameplate
+1. Functions of Nameplate Component
+Nameplate Components support displaying visual information for the specified entities 
+during stage runtime, providing specific information such as entity HP, level, and other 
+details, as well as directional guidance, distance display, and other visual indicators.
+1. Overview
+The nameplate component needs to be mounted to entities. Supports usage of 
+characters, objects, and creations.
+The nameplate component allows multiple nameplates to be active at the same time.
+Nameplates can be enabled or disabled via default configuration, or controlled 
+individually through the node graph; the visibility of the specific nameplates can also be 
+adjusted using the local filter.
+2. Details
+The actual nameplate display includes both the nameplate and the navigation 
+indicator
+Nameplates
+Can be occluded by the environment
+On the same physics layer as the entity
+Navigation Indicator
+Not occluded by the environment
+Above Interface Layout layer
+II. Editing Nameplate Components
+1. Add Components
+(1) In the entity/prefab editing interface, open the Editing Components tab
+(2) Click "Add Components" below, select and click "Nameplate" to add it
+When the nameplate is selected, the entity being edited will display all currently active 
+nameplates of the nameplate component and their stacking behavior.
+(3) Click "Advanced Editing" to expand the editing tab
+2. Editing Nameplate Components
+Configuration Parameters
+Description
+Initially Effective 
+Nameplate
+The dropdown menu provides nameplate enumeration
+By modifying the checkbox behind, you can change the eff
+synchronized to the nameplate editing tab
+*Nameplate List
+Enumerates all nameplates configured for the entity
+III. Editing Nameplates
+1. Adding Nameplates
+The added nameplate is initially effective by default.
+2. Editing Nameplates
+(1) Select the Nameplate submenu
+(2) Basic Settings
+Configuration Parameters
+Description
+Select Attachment Points
+Select the preset attachment point of the entity, or a custom
+Can be selected from the dropdown menu. The nameplate p
+location.
+Visible Radius (m)
+The effective range of the nameplate. The nameplate logic w
+this configured distance.
+Filter Node Graph
+Can reference the local filter node graph to determine wheth
+specific distinctions and usage of the two filters, see Node G
+Selection Type: Boolean
+When the local filter re
+visible to the local clien
+Selection Type: Integer
+Effective Integer Range: 
+Configure an integer list as 
+needed
+When the local filter re
+associated nameplate 
+Explains the basic nodes in the local filter node graph
+Output parameter is the entity with nameplate compone
+Output parameter is the character entity within effective 
+Retrieval succeeds only if the character entity is equal t
+Output parameter is the local character
+Initially Effective
+Whether to enable simultaneously with object creation
+If multiple nameplates are enabled simultaneously, overlapp
+(3) Nameplate Content
+The nameplate offers five independent types of editable content and supports both 
+individual and combined use of these content types, with adjustable position, size, and 
+detailed data for each item.
+You can add content items to the nameplate with "Add Content".
+Use 
+to adjust the visibility of the specified items in the edit mode.
+Use 
+ to copy, paste, delete and perform other operations on the selected items.
+a. Text Box
+Configuration Parameters
+Description
+Offset
+Adjustable offset based on the attachment point selected in 
+Size
+Adjust the size of text box
+Background Color
+Supports setting a transparent or black semi-transparent bac
+Font Size
+Font size configuration
+Text Content
+Display text editing
+Supports adjusting the alignment of the text content
+Supports variable insertion. Selecting a custom variable for
+text box
+If the configured text content exceeds text box range, it will 
+Insert the referenced custom variables in rich text format, us
+{Type:Prefix.VariableName}
+Type:
+1: When referencing a custom variable of the entity itself.
+2: When referencing an attribute of the entity.
+Prefix:
+s: When the billboard is attached to a non-character/player e
+a: When the billboard is attached to a character entity.
+p: When the billboard is attached to a player entity.
+Variable Name:
+When referencing a custom variable, use the name of the cu
+When referencing an entity's attribute, use the following vari
+Current HP: HpCur
+Maximum HP: HpMax
+Current ATK: AtkCur
+Current DEF: DefCur
+Current Level: LvCur
+Player Nickname: PName
+Distance to Player: PDist
+b. Icons
+Configuration 
+Parameters
+Description
+Offset
+Adjustable offset based on the attachment point selected in b
+Size
+Adjust the size of the icon
+Icon Type
+Custom Icon
+Icon must be additionally selected for us
+Use Faction Icon
+Repeated icon selection unnecessary. T
+c. Progress Bar
+Configuration 
+Parameters
+Description
+Offset
+Adjustable offset based on the attachment point selected in bas
+Shape
+Horizontal
+Supports setting width and height
+Vertical
+Supports width and height configuration
+Ring
+Supports diameter configuration
+Size
+Progress bar size adjustment
+Progress Bar Style
+Percentage
+Displays progress as a percentage based 
+Do Not Show
+Hide progress hint text
+Current Value
+Display current value in real-time
+1:1 Scale
+Display actual ratio in real-time
+Color
+Can be selected from preset colors
+Current Progress 
+Value
+Supports selection of custom variables for the mounted entities
+Minimum Value
+Supports selection of custom variables for the mounted entities
+Maximum Value
+Supports selection of custom variables for the mounted entities
+Progress Bar Smooth 
+Transition
+When enabled, the progress value change will be animated ove
+Transition Duration (s)
+When the current progress value changes, the visual transition 
+d. Timer
+Configuration 
+Parameters
+Description
+Offset
+Adjustable offset based on the attachment point selected in bas
+Type
+Stopwatch, Countdown
+Specify Timer
+Enumerates all predefined global timers that match the specifie
+Source Entity
+Default configuration is stage entity; can choose between stage
+e. HP and Shield
+Configuration 
+Parameters
+Description
+Offset
+Adjustable offset based on the attachment point selected in bas
+Size
+Adjust HP bar size
+HP Display Style
+Do Not Show
+Hide HP bar
+Progress Bar
+Progress Bar + 
+Value
+Value is precise to two decimal places
+HP Color
+The progress bar will display with the color configured in the se
+Shield Display
+Do Not Show
+Only show HP bar
+Display 
+Separately
+If the shield is configured to display separa
+Mixed Display
+If configured for mixed display, the progres
+simultaneously, with the shield value displa
+the deduction priority.
+Show Shield Display 
+Maximum Value
+If checked, when the shield value exceeds
+as full.
+Shield Display 
+Maximum Value
+This configuration is only available when S
+The shield display maximum value will be 
+exceeding this limit will continue to display
+The shield bar will show the deduction only
+value.
+3. Editing Navigation Indicators
+(1) Select the Navigation Indicator submenu
+(2) Basic Settings
+Configuration 
+Parameters
+Description
+Offset
+Adjustable offset based on the attachment point selected in bas
+Maximum Visible 
+Radius (m)
+Maximum effective range of indicator
+Minimum Visible 
+Radius (m)
+Minimum effective range of indicator
+Hide Indicators When 
+Nameplate Is 
+Displayed
+When enabled, the indicator will not be displayed when the nam
+nameplate and indicator display.
+(3) Navigation Indicator Content
+The navigation indicator provides two independent types of editable content, which can 
+be used separately or in combination. Each type supports adjustments to position, size, 
+and detailed data.
+Use Add Content
+ to add 
+items to the navigation indicator.
+Use 
+to adjust the visibility of the specified items in the edit mode.
+Use 
+ to copy, paste, delete and perform other operations on the selected items.
+a. Text Box
+Configuration Parameters
+Description
+Size
+Adjust the size of text box
+Background Color
+Supports setting a transparent or black semi-transparent bac
+Font Size
+Font size configuration
+Text Content
+Display text editing
+Supports variable insertion, select custom variables for the
+box
+Supports adjusting text alignment effects
+If the configured text content exceeds the text box range, it w
+b. Icons
+Configuration 
+Parameters
+Description
+Size
+Adjust the size of the icon
+Icon Type
+Custom Icon
+Icon must be additionally selected for us
+Use Faction Icon
+Repeated icon selection unnecessary. T
+IV. Managing Nameplates Through Node Graph
+During entity runtime, its active nameplates can be managed through the node graph
+The Nameplate Config ID List entered through the node will completely override the 
+target entity's active nameplate
+Configuration 
+Parameters
+Data Type
+Description
+Target Entity
+Entity
+Runtime entity
+Nameplate Config ID 
+List
+Config ID List
+Sound Effect Player
+Text Bubble
+Concept Introduction
+Functions
+Common Components
+Nameplate
+Click 
+to add a nameplate.
+
+Nameplate X, where X is the nameplate ID, can be used as a node input to adjust 
+the initial activation parameters of the nameplate.
+
+Get Self Entity
+
+Get Self Entity
+
+Get Current Character
+
+Set Entity Active Nameplate
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh5y5001vqd4.txt

@@ -0,0 +1,74 @@
+/
+/
+/
+Inventory Component
+I. Inventory Component Functions
+The Inventory component directly references the Inventory  template and generates 
+corresponding inventory instances at runtime
+The Inventory component supports selecting only one inventory template at a time
+The Inventory component can be mounted on characters, creations, and dynamic objects
+II. Editing Inventory Components
+1. Add Components
+(1) In the Entity or Prefab editing interface, open the Component Editing Tab
+(2) Click "Add Components" below, then click "Inventory" to add it
+(3) Click "Advanced Editing" to expand the editing tab
+2. Basic Concepts
+By adding this component, you can configure the character's inventory component and 
+define default items in the inventory
+Inventory Template: Reference an inventory template
+Starting Items : The default item configuration in the inventory. When gameplay starts, 
+the character carries these contents by default
+III. Inventory Runtime Instance
+IV. Inventory Data for Node Graph Operations
+1. Inventory Component-Related Execution Nodes
+2. Inventory Component-Related Event Nodes
+3. Inventory Component-Related Query Nodes
+Text Bubble
+Loots
+Concept Introduction
+Functions
+Common Components
+Inventory Component
+Set Inventory Drop Items/Currency Amount
+
+Set Inventory Item Drop Contents
+
+Modify Inventory Item Quantity
+
+Modify Inventory Currency Quantity
+
+Increase Maximum Inventory Capacity
+
+When Item Is Lost From Inventory
+
+When the Quantity of Inventory Item Changes
+
+When Item Is Added to Inventory
+
+When the Quantity of Inventory Currency Changes
+
+When items in the inventory are used
+
+Get Inventory Item Quantity
+
+Get Inventory Capacity
+
+Get All Inventory Basic Items
+
+Get All Inventory Equipment
+
+Get All Inventory Currency
+
+Get Inventory Currency Quantity
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh63ox06afy8.txt

@@ -0,0 +1,61 @@
+/
+/
+/
+Loots
+1. Functions of Loot Components
+The Loot Component allows creators (Craftspeople) to configure a fixed Loot collection 
+template data, which creates Loot based on this data template when the component 
+holder is defeated
+In design, it is recommended for implementing Loot-related concepts
+The Loot component only supports configuring one set of Loot template data
+II. Editing the Loot Components
+1. Add Components
+(1) In the Entity or Prefab editing interface, open the Component Editing Tab
+(2) Click "Add Common Components" below, then click "Loot" to add it.
+(3) Click "Advanced Editing" to expand the editing tab
+2. Basic Concepts
+(1) Basic Settings
+Configuration for Drop Behavior and Drop Methods
+Destruction Debris: Defines how the drop configuration is handled when the 
+component's owner is defeated
+Individual Drops: Each virtual item in the Loot Content is converted into a 
+corresponding Loot item and dropped separately
+Combined Drops: Virtual items in the Loot Content are converted into a single Loot 
+item and dropped
+Loot Drop Mechanics: Divided into Shared Reward and Individualized Reward
+Shared Reward: All players share the same loot. Once a player picks it up, other 
+players cannot pick it up again
+Individualized Reward: Each player's client will generate their own independent 
+copy of the item, and players' looting actions do not affect each other
+Corresponding Loot Appearance: Configure a Loot prefab, which is a physical entity 
+prefab. When a virtual item is created in the scene, it will be displayed using the model 
+of the associated drop prefab. This setting only takes effect when combined drops are 
+selected; if individual drops are chosen, each drop will use the associated drop prefab 
+configured in its own item or currency template
+(2) Loot Content
+Configure virtual Loot data. Click "Add Items" to configure a list of virtual items
+Item List: You can select all defined items, currency templates and quantities
+III. Loot Collection Examples
+IV. Node Graph Operations for Loot Components
+Loot Component Execution Nodes
+Inventory Component
+Shop Component
+Concept Introduction
+Functions
+Common Components
+Loots
+Trigger Loot Drop
+
+Set Loot Drop Content
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh65jrr2yj3i.txt

@@ -0,0 +1,69 @@
+/
+/
+/
+Achievements
+I. Achievement Functions
+Achievements are used to record specific goals or milestones that players accomplish 
+in the game
+Achievement progress can be carried over across multiple playthroughs. When players 
+replay the same stage, they can continuously accumulate achievement progress to 
+unlock different achievements.
+The number of achievements and completion conditions in a stage can be customized 
+by creators (Craftspeople) through the Achievement module
+II. Editing Achievements
+Click [Manage Peripheral System] in the System menu to enter the Peripheral System 
+Settings interface
+Configure achievement settings in the Peripheral System Settings interface
+A stage supports configuring multiple regular  achievements and one ultimate 
+achievement. The ultimate achievement will be automatically unlocked after all normal 
+achievements are completed. The ultimate achievement will only be enabled when at 
+least five normal achievements are set and their names and images are configured
+Achievement Settings: Switch and Validity settings for the achievement system
+Enable Achievements?: Enable or disable the achievement system
+Enable in-room achievement settlement: Whether to allow setting achievement 
+progress when players play this stage through room teams rather than matchmaking
+1. Ultimate Achievement
+Ultimate Achievement: Ultimate Achievement settings, click the edit button on the right 
+to enter the Edit Details interface
+Achievement Name: The display name for the achievement. Can be modified in the 
+Achievement Name field below
+ID: The identifier used to distinguish this achievement when modifying achievement 
+data in a node graph
+Achievement Icon: Allows uploading a local image to serve as the achievement's icon
+2. Regular Achievements
+Regular Achievements: Click the New Achievement button in the bottom right to add a 
+new normal achievement, then click the Edit button to modify its details
+Achievement Name: The display name for the achievement. Can be modified in the 
+Achievement Name field below
+ID: The identifier used to distinguish this achievement when modifying achievement 
+data in a node graph
+Rarity: Creators (Craftspeople) can also customize an achievement's rarity, which is 
+divided into Glorious  Gold , Starsilver, and Bright  Bronze
+Achievement Counter: A configurable value that starts at 0 for each player and 
+gradually increases through Node Graph trigger logic during gameplay. The 
+achievement is considered complete when the counter reaches this configured value
+Achievement Description: The description displayed for this achievement
+III. Node Graph Achievement Data Management
+Rank
+Stage Settlement
+Concept Introduction
+Advanced Concepts
+Peripheral System
+Achievements
+Set Achievement Progress Tally
+
+Change Achievement Progress Tally
+
+Query If Achievement Is Completed
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh6ate95agb6.txt

@@ -0,0 +1,52 @@
+/
+/
+/
+Skill Resources
+I. Definition of Skill Resources
+Skill Resources are resources that need to be consumed when specific skills are cast. 
+For example, "Elemental Energy" in the Classic Mode is a type of skill resource. The 
+Miliastra Sandbox supports creators (Craftspeople) in defining their own types of skill 
+resources and specifying which skill resources their skills require
+II. Editing Skill Resources
+1. Entry Point for Editing
+Enter through the Skill Resource Management button in the system menu bar
+Open the interface to edit globally available skill resource types
+2. Parameters Introduction
+Unconditional Growth: When exceeding the maximum obtainable value, this skill 
+resource amount will grow unconditionally
+Follow Skill (Retaining Value): When attempting to change the skill resource 
+amount, it will only succeed if the player currently has a skill that requires this resource. 
+Otherwise, it will not take effect. When no skills require a certain skill resource, the 
+resource amount will be saved
+Follow Skill (Not Retaining Value): Same rules as above, but when no skills require 
+a certain skill resource, the resource amount will be reset to zero
+III. Modifying Skill Resources in Node Graphs
+Concept Introduction
+Advanced Concepts
+Skills
+Skill Resources
+Skill Resource Name: Name of skill resource
+
+Configuration ID: The unique identifier for the skill resource, which is required when 
+calling it from the Node Graph
+
+Growth Type: The growth type determines the actual growth rules when external 
+logic attempts to increase the quantity of skill resources. Currently, three types are 
+supported
+
+Maximum Obtainable Value: The maximum value of skill resources. The amount of 
+skill resources that a character can obtain cannot exceed this value
+
+Reference Information: Indicates which skills reference this skill resource
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+Copyright © COGNOSPHERE. All Rights Reserved.
+General Guide
+Tutorial

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh6fj30p2cmo.txt

@@ -0,0 +1,70 @@
+/
+/
+/
+Copy and Paste Data
+1. Feature Overview
+This function is used to copy data from the specified content and stores it in an 
+independent clipboard (storing only one copy at maximum), which can then be used to 
+paste and replace data in target content. After data replacement, the ID remains 
+unchanged, not affecting node graph references, only replacing the functional data.
+II. Usage Restrictions
+1. Asset Types
+Only applicable to objects and creations.
+2. Use Units
+Prefab data can only be pasted onto prefabs.
+Entity data can only be pasted onto entities.
+III. Copy and Paste Prefab Data
+1. Entry Points
+2. Functional Logic
+Copy prefab data to the clipboard, which can then be pasted to other prefabs of the 
+same type to replace data of the target and associated entities.
+3. Data Replacement
+4. Operation Process
+IV. Entity Data Copy and Paste
+1. Entry Points
+2. Functional Logic
+Copy entity data to the clipboard and paste it to other entities of the same type to 
+replace their data.
+3. Data Replacement
+All data except name, GUID (identifier), and parent tab.
+4. Operation Process
+Load Optimization
+Concept Introduction
+Functions
+Basic Information
+Copy and Paste Data
+Right-click the menu in the Prefab Library scene
+
+Right-click the menu in the assets bar
+
+Left-click the menu in the details bar
+
+All data except name, prefab ID (identifier), and parent tab.
+
+All data of the affiliated entities.
+
+Select the prefab you want to copy, and click "Copy Prefab Data".
+
+Select the prefab where you want to paste, click "Paste Prefab Data" to complete 
+the replacement.
+
+Right-click the menu in the entity placement/prefab library scene
+
+Left-click the menu in the details bar
+
+Select the entity you want to copy, then click "Copy Entity Data".
+
+Select the entity you want to paste, click to paste the entity data, and the 
+replacement is complete.
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh6rh59iil2i.txt

@@ -0,0 +1,190 @@
+/
+/
+Unit Status
+I. Definition of Unit Status
+Unit Status is a status management module for managing additional functions and 
+attributes of Entities during Stage runtime.
+During Stage runtime, Entities can be applied with Unit Statuses. Each Unit Status must 
+have a defined Applier Entity.
+Entities can dynamically hold multiple Unit Statuses. Each status has a defined Runtime 
+Duration that grants the Entity Additional Effects and Additional Node Graph 
+functionality. Statuses must be predefined at the editing time to be enabled during 
+runtime.
+Each active Unit Status has independent Stack Layers, and some functions can scale 
+in real time with the number of stacks.
+A Unit Status ends when its Runtime Duration expires or when all Stack Layers are 
+depleted.
+1. Additional Effects
+All Additional Effects come from the predefined Effect Pool, such as functional effects 
+like "Mount Looping Effects" or numerical effects like "Motion Speed Change".
+Each Additional Effect has certain runtime limits on both its Effective Target and Effect 
+Intensity —
+Effective Target: Each effect can only apply to one or several among "Characters", 
+"Creations", or "Objects". When a target entity tries to hold a Unit Status, if that status 
+includes an effect that cannot apply to the entity’s type, the entity will fail to acquire the 
+status. For example, the "Mount Screen Effect" is allowed only on "Characters", so any 
+status using this effect can only be applied to character entities.
+Effect Intensity: An entity may receive multiple Additional Effects of the same type at 
+the same time, but the final effect cannot stack without limit — it is restricted to a valid 
+range. For example, with "Motion Speed Change", since the change cannot be less 
+than -40% or greater than 40%, whether an entity has one effect of +50% speed 
+change or five effects of +10% each, the final Motion Speed will never exceed 140%.
+Additionally, some effects cannot coexist within the same Unit Status. For example, a 
+Unit Status can provide only one type of Elemental Effect. If multiple Mutually Exclusive 
+effects are configured, the last effect will take precedence.
+2. Additional Node Graph
+Each Unit Status can be related with a server Node Graph. When an Entity holds this 
+status, the Node Graph is synchronously added to the corresponding Entity, and it is 
+removed when the status ends.
+The related Node Graph can only come from a Status Node Graph, where Composite 
+Nodes can still be used.
+Unlike regular Node Graphs, if multiple Unit Statuses held by an Entity are related with 
+the same Node Graph, it is considered related only once, and the Node Graph will lose 
+relation only when the Entity has lost all related statuses.
+II. Editing Unit Statuses
+After entering the Combat Preset page, select the Unit Status bar, create management 
+Tabs as needed, and create the corresponding Unit Statuses within the Tabs.
+Click the New Status, then click Confirm Create in the pop-up to create a new Unit 
+Status
+1. Naming and Identification
+Each predefined Unit Status Name must be globally unique. A globally unique Config 
+ID is automatically generated for it.
+You can use the Copy button to quickly duplicate this Config ID.
+You can also replace the Icon for each status.
+2. Stacking Rules
+When a status is stacked onto an existing one, detailed stacking rules must be defined.
+Each time stacking occurs, the new status's stack layers count is added to the existing 
+status, but the total will not exceed the Maximum Stack Layers.
+The maximum count of the stacks may vary depending on the situation.
+When stacking may exceed the limit, you can choose whether to enable Overlapping 
+Data Update.
+If updated, the overlapping data will sequentially replace the earliest existing stack data. 
+Otherwise, the overlapping data will be discarded.
+If no change occurs to the stack data of the status, the stacking action is considered 
+invalid, and the application of the status is also invalid.
+3. Timing Rules
+Each active Unit Status may have a defined Life Cycle. When the Life Cycle is 
+exceeded, the status is automatically removed.
+Enabling Infinite Duration prevents the status from being removed when its Life Cycle 
+expires, and any updates to the status will no longer affect its Initial Runtime Duration.
+If the Initial Runtime Duration of a status is finite, when an Entity gains a new status, 
+that status's Life Cycle is set to its Initial Runtime Duration.
+If the Initial Runtime Duration is finite, you can enableStack Shared Duration.
+ When disabled, each stack calculates its Runtime Duration independently. Once a 
+stack exceeds its Runtime Duration, it is automatically removed, reducing the 
+corresponding Stack Layers of the status
+Stack Layers Count.
+ In this case, the Maximum Stack Layers count is 10.
+ When enabled, all stacks are removed together once the status exceeds its duration. 
+However, each time a new stack is applied, the status's Time Remaining may be 
+extended based on specific rules.
+ Each time a new stack is applied, the current Time Remaining of the status may be 
+increased by an Extended Duration.
+ When Maximum Extended Duration Limit is enabled, the extended Time Remaining 
+cannot exceed the Maximum Duration, even if the original Time Remaining was greater.
+ In this case, the Maximum Stack Layers count is 1000.
+4. Related Node Graph
+The Status Node Graph related with an Entity while it holds a status.
+5. Status Coexistence
+When the same Unit Status is repeatedly applied to an Entity, different handling can be 
+configured based on the Applier Entity, and the most recent update time is recorded.
+The same Applier cannot apply two instances of the same‑name Unit Status to a Target 
+Entity; instead, it is added to the already applied status.
+When different Appliers apply the same Unit Status to a Target Entity, you must decide 
+whether these statuses can stack from different Applier sources:
+If stackable, then after the stacking action is successfully completed, you can enable 
+Record Latest Applier.
+If stacking is not allowed, set a Coexistence Limit for this status from different Appliers.
+When the Coexistence Limit is reached, define a Same Name Status Update Strategy 
+to determine how new applications are handled: 
+Cannot Update — the status application fails and the action is terminated.
+Minimum Time Remaining — remove the status with the shortest Time Remaining, then 
+apply the new one.
+Earliest Update Time — removes the status with the earliest last update time, then 
+applies the new status. If the status has not been re-applied, its first application time is 
+used.
+Earliest Application Time — remove the status applied earliest, even if its Time 
+Remaining is not the shortest, then apply the new one.
+6. Yielding and Replacement
+When applying a status, the Yielding Status List may affect the outcome of the 
+application, and the Replacement Status List may affect the statuses held by the target 
+Entity.
+If the target already holds any Unit Status from the Yielding Status List, the application 
+is immediately terminated and fails.
+If the target already holds any Unit Status from the Replacement Status List, all 
+corresponding statuses are removed before the new status is applied.
+III. Unit Status Execution
+1. Apply via Component
+If a preset Unit Status is configured in the target Entity's Unit Status Component, the 
+corresponding status is applied by the Stage Entity when the Entity is created.
+The Stack Layers Count for the status can be configured in the component, and 
+statuses are applied in the top-to-bottom order of the configuration.
+The same status can only be applied once within the component.
+For details, please refer to Unit Statuses
+2. Manage with Server Nodes
+When both the Applier Entity and the Target Entity are present, the system attempts to 
+apply the corresponding Unit Status to the target and returns one of the following results:
+Failed: Unexpected error — failure due to special cases, such as the Applier or Target 
+not being present in the scene
+Failed: Operation paused for another process — the target already holds one or more 
+statuses from the Yielding Status List; the application does not proceed
+Failed: Maximum coexistence limit reached — the target has already reached the 
+coexistence limit for statuses from other Appliers, and replacement is not allowed
+Failed: Unable to add additional stack — when attaching to the target's existing status, 
+all stacks are full and updates are not accepted
+Success: New status applied — a new status is applied to the target
+Success: Slot stacking — an existing status on the target is updated
+When the Remover Entity is present, the system attempts to remove the corresponding 
+status from the Target Entity.
+When the removal target holds one or more coexisting statuses, you can choose:
+All Coexisting Statuses With the Same Name — regardless of whether the Applier is 
+self, all statuses with the same name held by the target are removed
+Status With Fastest Stack Loss — if stacks are timed independently, remove the status 
+whose first stack has the shortest Time Remaining; if stacks are not timed 
+independently, remove the status with the shortest Time Remaining
+(Not available) statuses applied by self — if the target holds a status whose Applier 
+matches self, remove it
+When the target entity gains a new unit status or an existing unit status is updated, this 
+event will be triggered.
+When the Target Entity loses an existing Unit Status, this Event is dispatched.
+If multiple coexisting statuses on the target are removed, the same number of Events is 
+received.
+Removal reasons include:
+ Replaced by other Unit Status — a new status was applied, replacing this status
+ Duration exceeded — the status exceeded its Initial Runtime Duration, or all stacks 
+exceeded their Initial Runtime Duration and ended naturally
+ Dispelled — the status was forcibly terminated by a Skill, an Ability Unit, or a fully 
+reacted Element
+ Status expired — the status removed itself because some of its effects ended
+ Class changed — the Player switched Class, removing statuses attached to the 
+previous Class
+You can search whether the Target Entity present in the scene already holds a given 
+Unit Status
+3. Manage with Ability Units
+Add or remove specified Unit Statuses in the Local Projectile's Ability Unit.
+When the Local Projectile hits the Target, use the Ability Unit to add or remove Unit 
+Statuses on the Target
+For details, see Ability Units
+4. Manage with Skill Node Graphs
+When both the Applier Entity and the Target Entity are present, attempt to apply the 
+corresponding Unit Status to the Target, but the final result cannot be determined.
+Regardless of whether the Remover Entity is present, attempt to remove the 
+corresponding Unit Status from the Target. If the Remover Entity is not present, the 
+removal is treated as source-less.
+Regardless of the Applier, all statuses with the same Config ID are removed.
+Classes
+Preset Points
+Concept Introduction
+Advanced Concepts
+Unit Status
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh8w69rzuc3i.txt

@@ -0,0 +1,110 @@
+/
+/
+/
+Collision Trigger
+I. Functions of Collision Trigger Component
+The collision trigger component provides a detection range for collision detection during 
+stage runtime and serves as a tool for contact determination.
+The collision trigger component supports multiple collision triggers to be active 
+simultaneously.
+1. Collision Detection between Collision Triggers and 
+Collision Trigger Source
+During stage runtime, the "Collision Trigger" continuously monitors other entities 
+carrying "Collision Trigger Source Components."
+When the runtime entity's "Collision Trigger Source" enters or exits the range of another 
+entity with a "Collision Trigger Component," a collision between the two component 
+ranges will send a node graph event to the entity configured with the "Collision Trigger."
+This type of collision does not create physical collision barriers.
+When a "Collision Trigger Source" collides with different "Collision Triggers," the collision 
+detection between them is calculated independently
+Example: When a "Collision Trigger Source" collides with "Collision Trigger 1" and 
+"Collision Trigger 2," node graph events will be sent separately without affecting each 
+other
+2. Collision Trigger Source Components
+Collision Trigger Source
+II. Editing Collision Trigger Components
+1. Add Components
+(1) In the entity/prefab editing interface, open the Editing Components tab
+(2) Click "Add Common Components" below, select and click "Collision Trigger" to add it
+(3) Click "Advanced Editing" to expand the editing tab
+2. Editing Collision Trigger Components
+Configuration Parameters
+Description
+Initially Effective Trigger
+Enumerates the collision triggers that are effective by defa
+runtime
+Supports editing of the trigger's default effective state by u
+arrow to adjust the enumeration checkbox after the trigger.
+state will be synchronized to the corresponding trigger's "A
+*Trigger List
+Enumerates all collision triggers configured for the entities
+3. Editing Collision Triggers
+In the stage editor window, the entity will display the range of the currently selected 
+collision trigger.
+(1) Collision Trigger Group
+(2) Basic Information of Collision Trigger
+Configuration Parameters
+Description
+Initially Effective
+If enabled, the collision trigger takes effect immediately upo
+Effective Target
+Collision trigger source detection only applies to the config
+Provides enums for characters, objects, and creations
+(3) Collision Trigger Range
+Click "Add Trigger Area" to add new trigger areas. The ranges under the same collision 
+trigger will be merged and take effect as a combined range
+Configuration Parameters
+Description
+Trigger Area Shape 
+Supports cuboid, sphere, and capsule shapes. Different siz
+parameters will be displayed based on the selected shape
+Center
+Offset relative to the entity/prefab center
+Rotation
+Supports orientation adjustment along different axes based
+position
+Zoom Multiplier
+The trigger area's shape supports defining scaling along di
+III. Managing Collision Triggers Through Node 
+Graph
+You can manage the collision trigger for runtime entities via the node graph during its 
+runtime
+The "Collision Trigger Source" range of a runtime entity enters the "Collision 
+Trigger" range of another runtime entity.
+Node graph events will be sent to the entity configured with "Collision Trigger"
+The "Collision Trigger Source" range of a runtime entity exits the "Collision Trigger" 
+range of another runtime entity.
+Node graph events will be sent to the entity configured with "Collision Trigger"
+The "Collision Trigger" component function supports dynamic adjustment of the 
+activation parameter through node graphs
+Basic Motion Device
+Custom Variables
+Concept Introduction
+Functions
+Common Components
+Collision Trigger
+Enumerate all predefined collision triggers for this entity
+
+Click 
+to add a collision trigger
+
+"ID: X", where X is the "Trigger ID", serves as a node input that allows you to 
+adjust the collision trigger parameters
+
+When Entering Collision Trigger
+
+When Exiting Collision Trigger
+
+Activate/Disable Collision Trigger
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mh9fj3rudd9q.txt

@@ -0,0 +1,153 @@
+/
+Multiplayer Test Play
+I. Function Overview
+This feature simulates multiplayer scenarios in edited stages to quickly validate stage 
+effects.
+II. Function Entry Point
+System Menu — Multiplayer Test Play
+III. Multiplayer Test Play Room
+After clicking [Multiplayer Test Play] (see above), the initialization runs (required checks 
+and stage upload). When complete, you enter the Multiplayer Test Play Room interface.
+Note: Each Multiplayer Test Play loads the most recently uploaded Saving. If you edit 
+the stage, manually update the stage before playing the latest changes.
+1. Room Functions
+(1) Waiting Area
+Players who join the Test Play Room are placed in the first available Waiting Area seat. 
+Players in the Waiting Area do not join subsequently started playtests. They can switch 
+areas and seats by clicking any open seat in the [Waiting Area] or [Preparation Area].
+Invited Players
+Invited Players can switch seats in the following two ways:
+(2) Preparation Area
+Holds all players who intend to participate in Test Play. Invited Players download the 
+stage here and get ready to play.
+Preparation Area: Loads [Stage Settings] -> [Player Count Settings] (player count, 
+groups).
+Invited Players
+While in the Preparation Area, Invited Players click the [Ready] button (bottom-right) to 
+signal readiness to play the stage
+After clicking Ready, the stage download starts; when complete, the player enters the 
+Ready state.
+Note: When the host starts the game, any player in the Preparation Area who is not in 
+the Ready state is moved to the Waiting Area.
+(3) Player Invitation
+After the host clicks [Invite], the [Invite Players] panel opens on the right with three 
+sections: [Search Invitation], [Today's Invites], and [Friends].
+Search for players by UID. After searching, send an invite with the [Invite] button; once 
+accepted, the player joins the Test Play Room.
+Switch to this tab to view players invited today. Use the Invite button to invite them 
+again.
+View your account's friend list on this tab; click a friend's Invite button to send a Test 
+Play invite.
+Invited Players
+Players have 15 seconds to respond to a Multiplayer Test Play invite; if they do not 
+respond in time, the invite is automatically declined.
+Invitation Limits
+(4) Start Test Play
+The host can start Test Play with the [Start Game] button (bottom-right). After Test Play 
+begins, all seats in the Preparation Area become non-joinable and non-clickable; players 
+who entered Test Play switch to the In-Game status, and the Cosmetic Display phase 
+starts.
+Note: Even if the host is not in the Preparation Area, Multiplayer Test Play can be 
+started as long as the stage meets the required conditions (player count, groups, etc.). 
+The host does not need to participate in the Multiplayer Test Play.
+If invited players are in the Preparation Area but not yet Ready, clicking [Start Game] 
+prompts the host for confirmation. If confirmed, all players not in the Ready state are 
+moved to the Waiting Area.
+2. Test Play Settings
+(1) Update Stage
+Click to upload the most recently edited stage to the Multiplayer Test Play Room. This 
+action moves all players to the Waiting Area, and they must get Ready again.
+(2) Generate Test Play Report
+After enabling, all players participating in Test Play automatically generate a local report 
+at the end of Test Play for viewing the Load Calculation Function . Creators can import 
+these reports to review each player's Dynamic Load for the session.
+Storage path: C:\Users\%USERPROFILE%\AppData\LocalLow\miHoYo\Genshin 
+Impact\BeyondLocal\(Player UID)\Beyond_Performance_Report
+(3) Character Display Settings
+When enabled, players entering a stage go through the Cosmetic Display phase, then 
+proceed to the Loading Interface.
+(4) Enable Settlement
+To speed up testing and reduce steps, disable settlement-related steps via [Enable Test 
+Play Settlement] under [Multiplayer Test Play].
+(5) Test Play Manekin
+Before starting a test play, creators can use [Test Play Manekin] in [Test Play Options] 
+to set which Manekin body type is used.
+(6) Test Play Data Settings
+Before test play starts, the host can configure per-seat data via the [Settings] button at 
+the top-right of each seat.
+Note: These settings are bound to the seat. Any player occupying that seat uses the 
+same settings.
+(7) Test Play Player Management
+During Multiplayer Test Play, the host can remove invited players or move them to the 
+Waiting Area using the button at the top-right.
+The host can remove a player from the Test Play Room. After successful removal, the 
+player returns to their pre-invitation location.
+Removal restriction: If a player is currently in Test Play, they are removed after their 
+Test Play ends.
+The host can move a player to an empty seat in the Waiting Area via [Move to Waiting 
+Area].
+(8) Disbanding the Room
+The host can disband the Multiplayer Test Play Room using [Dismiss]. After disbanding, 
+all players return to their location prior to joining the room.
+(9) Room Collapse
+The host can collapse the interface to the top Menu Bar with the [Collapse] button (top-
+right) and return to the editing interface. Note: The Multiplayer Test Play Room remains 
+active; invited players stay in the room.
+IV. In-Game Controls for Multiplayer Playtest
+The host can perform these actions: Retry Challenge, End Test Play.
+Invited Players can perform this action: End Test Play.
+1. Exit Button
+While in playtest, open the [Test Play Controls] panel via the top-left button or the Esc 
+hotkey.
+2. Test Play Controls
+(1) Retry Challenge
+After clicking [Retry Challenge], all startup steps from the Cosmetic Display phase are 
+re-run; when complete, a new playtest session starts.
+Note 1: If an exception prevents immediate restart, exit Test Play and start the Test Play 
+flow again.
+Note 2: In Multiplayer Test Play, if any player exits the current session early, Retry 
+Challenge cannot be executed.
+Note 3: During Multiplayer Test Play, only the host can use Retry Challenge.
+(2) Abandon Challenge
+Click to end the current Test Play immediately and trigger the corresponding non-
+standard settlement result.
+V. Multiplayer Test Play Settlement
+When Test Play ends, the settlement flow runs and displays results according to the 
+stage's settlement settings.
+Creators (Craftspeople) can configure these settings in [Settlement] under [Stage 
+Settings].
+Test Play
+Miliastra Sandbox
+Interface Guide
+Multiplayer Test Play
+Click [Join Preparation Area] to take a remaining seat in the Preparation Area.
+
+Click an empty seat to switch.
+
+Search Invitation
+
+Today's Invites
+
+Friends
+
+Invitation Limit: You can invite up to 16 players per day for Test Play. [Today's 
+Invites] resets at midnight.
+
+Invited Players: Players currently in a Stage, Domain, or Editing cannot receive Test 
+Play invites.
+
+Remove Player
+
+Move to Waiting Area
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mha42r0cwx74.txt

@@ -0,0 +1,55 @@
+/
+/
+/
+Combat Settings
+I. What are Combat Settings
+Provides more detailed configuration for custom combat gameplay, enabling players to 
+configure attack and hit response settings
+II. Editing Combat Settings
+In the Specialized Settings tab, click Advanced Editing to enter the entity's combat 
+settings
+Configuration Parameters
+Description
+Cannot Be Affected by 
+Elemental Effects
+Configure whether this object can be affected by elementa
+Cannot Be Targeted
+Configures whether any function that targets and locks this
+effect
+Hit Effect
+Configures special effect to play when the object is attacke
+Knockdown Effect
+Configures special effect to play when the object is destroy
+The hit effects and knockdown effects can be further configured on the Edit Details tab
+Effect Configuration 
+Parameters
+Description
+VFX Asset Type
+Only Timed Effects  can be selected
+For effect-related assets, see Special Effects
+Special Effects Assets
+You can select Special Effects Assets. After selecting a Sp
+you can preview it in the scene
+Zoom Factor
+Zoom factor of the effect
+Offset
+Specified Relative Position
+Rotation
+Specifies the rotation information of the special effect
+Hurtbox Settings
+Ability Units
+Concept Introduction
+Functions
+Specialized Settings
+Combat Settings
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhaneb9qnvay.txt

@@ -0,0 +1,77 @@
+/
+/
+Text Chat
+I. Text Chat Features
+The text chat management provides gameplay-oriented chat features, supporting the 
+configuration of multiple exclusive chat channels for different players or factions based 
+on gameplay needs. 
+The same player can send messages in different chat channels simultaneously.
+Supports real-time management of player chat channel permissions through node 
+graphs. 
+II. Text Chat Function Management
+ You can manage the current level's chat channel through [System Menu] > [Manage 
+Text Chat] 
+Controls whether text chat functionality is enabled in the current level 
+III. Text Chat Channel Editing
+Click the [Add Channel] button to add new chat channels 
+The stage comes with a default global channel that applies to all players. While its 
+configuration and name can be modified, it cannot be deleted.
+ Press the icon to rename or delete the channel 
+Parameter
+Description
+Index
+The unique identifier corresponding to the chat ch
+Initially Effective
+Controls the channel's activation status at the beg
+Channel Application Method
+Supports application by player/by faction  
+When the channel is applied by faction, chat cha
+Apply to Player/Team
+Controls the initial coverage of the channel in the
+Display Priority
+Controls the display order of channels in the leve
+Select Icon
+Controls the icon and color of the channel in the 
+ Control quick chat messages for corresponding channels within the level Click   
+  to add quick text, click 
+to delete text. At least 1 default text 
+must be kept 
+The corresponding in-game runtime display is shown in the figure below: 
+IV. Controlling Text Chat Channels with Node 
+Graph 
+Input a list of player-specific channel indices through the node graph to override the 
+active channels for target players 
+The node graph can control all text chat channel switches in the current level. 
+Enabling/disabling will affect all corresponding objects in that channel
+Through node graph input, specific players can be kicked out of or added into 
+player-divided channels 
+Multi-language Text
+Background Music
+Concept Introduction
+Other Concepts
+Text Chat
+Global Settings:       
+
+Add Chat Channel 
+
+Basic Information 
+
+Quick Message
+
+Set Player's Current Channel 
+
+ Set Chat Channel Switch 
+
+Modify Player Channel Permission
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhaqt9rgqv4u.txt

@@ -0,0 +1,83 @@
+/
+/
+/
+Projectile Motion Device
+I. Functions of Projectile Motion Device 
+Component
+The Projectile Motion Device component enables entities to perform complex movements
+Only one projectile motion device can be active on a component at a time
+The position of the projectile motion device may vary at each end, therefore it is 
+recommended for use with projectiles or motion-based effects
+If a disconnection or reconnection occurs, the projectile motion device's position may 
+reset
+II. Add Projectile Motion Devices
+(1) In the entity/prefab editing interface, open the Editing Components tab
+(2) Click "Add Common Components" below, select and click "Projectile Motion Device" 
+to add it
+(3) Click "Advanced Editing" to expand the editing tab
+III. Projectile Motion Device Types
+The Projectile Motion Device currently supports four types
+1. Linear Projectile
+Initial Speed: The velocity direction when the component gets initialized
+Speed: Speed value
+Acceleration: The increase in velocity per second
+Acceleration Duration: The duration for which the acceleration rate takes effect
+Ground Hugging Movement: Whether the movement is attached to the ground
+2. Parabolic Projectile
+Initial Speed: The velocity direction when the component gets initialized
+Speed: Speed value
+Gravitational Acceleration: Vertical downward direction, speed increase value per second
+3. Tracking Projectile
+Tracking Object: The target to track.
+Track Target Attachment Point: Tracks attachment point on the target.
+Initial Speed: The velocity direction when the component gets initialized
+Speed: Speed value
+Acceleration: The increase in velocity per second
+Acceleration Duration: The duration for which the acceleration rate takes effect
+Tracking Angular Velocity: The projectile will turn towards the tracking target at the 
+specified tracking angular velocity from its initial direction. If this value is small, the 
+projectile may not be able to hit the target directly due to the slow turning speed.
+Tracking Final Phase: This can be set to one of three types:
+None: No final stage settings. After reaching the tracking target, the projectile will 
+continue to attempt to track the target, which may cause it to oscillate around the target.
+Cancel Tracking: When the projectile is within a certain range of the tracking target 
+(configured by Stop Tracking Range), it will stop the tracking function and continue in a 
+straight line with the direction it had at that moment. This means the tracking projectile 
+will not hit the target directly. It can be used to create projectiles that players can dodge 
+by moving.
+Stop Tracking Range: Configures the distance from the tracking target at which the 
+tracking will stop.
+Adsorption Tracking: When the projectile is within a certain range of the tracking target 
+(configured by Adsorption Range), it will try to attach to the target over a fixed period 
+(Adsorption Time). After this period, it will move stably with the target. Common tracking 
+projectiles can use this configuration.
+Adsorption Range: The distance from the tracking target at which the projectile will start 
+to attract.
+Adsorption Time: The fixed time it takes for the projectile to attach to the tracking target 
+and then move stably with it.
+4. Radial Fire
+Around Object: The object to orbit around. 
+Track Target Attachment Point: Which attachment point on the circular motion target. 
+Rotate Clockwise: When enabled, the object rotates clockwise; when disabled, it rotates 
+counterclockwise. 
+Circumradius: The radius of the circular motion. 
+Angular Velocity: The angular velocity of the circular motion.
+IV. Node Graph Related
+Create Projectile
+Custom Variables
+Character Disruptor Device
+Concept Introduction
+Functions
+Common Components
+Projectile Motion Device
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhawd6rl5kpy.txt

@@ -0,0 +1,123 @@
+/
+/
+/
+Global Timer
+I. Global Timer Component Functions
+The  global timer component provides timing capabilities. It supports pausing, restarting, 
+and modifying timers, and can synchronize with UI controls to display the timer's time.
+The global timer supports configuring multiple sets of static timer data.
+Global timers run independently on different active entities.
+II. How to Use Global Timers
+There are two ways to use the global timer:
+1. The entity editing component can have a reference timer set, which will be activated 
+when the entity is created. 
+2. A node graph execution node can activate the timer when it is executed..
+III. Global Timer Management Tool
+You can predefine all global timers via the timer management tool.
+Enumerates all predefined global timers in the current stage.
+IV. Editing Global Timers
+Use the button shown above to add a new timer.
+Click 
+ the icon to rename or delete the specified timer.
+This name is the global timer's reference.
+Configuration Parameters
+Description
+Global Timer Type
+Provides two types: countdown and stopwatch.
+Duration (s)
+When the timer type is countdown, a duration needs to be 
+V. Global Timer Reference
+1. Referencing the Global Timer Through UI Controls
+Open Interface Layout Management Tool, Select Timer UI Controls  "Timer" to execute 
+its logic.
+Configuration Parameters
+Description
+Type
+Stopwatch, Countdown
+Specify Timer
+Will enumerate all predefined global timers that match the 
+Source Entity
+Default configuration is stage entity. You can choose betwe
+player entity
+When the source entity is running and the timer is active, the UI control shows the 
+timer's current time.
+2. Reference Global Timer Through Component
+(1) Add Component
+a. In the entity prefab editing interface, open the Edit Component tab.
+b. Click "Add Common Component", then select "Global Timer" to add it.
+c. Press "Advanced Editing" to expand the editing page.
+(2) Reference Timer
+Click "Add Timer" to open a list of global timers, then you can select the desired 
+global timer.
+A global timer referenced by a component will be activated when the entity is 
+created.
+Click "Manage Timer" to open the global timer management tool.
+VI. Reference Global Timer by Node Graph
+Use the node graph to reference a global timer, with the running entity as the 
+carrier.
+Only timers predefined in the global timer management tool are valid as a reference.
+Use the node graph to stop running a global timer early.
+Use the node graph to pause a running global timer.
+When paused, the UI controls linked to the timer will also pause their display.
+You can resume a timer paused by "Pause Global Timer" via the node graph.
+If a UI control references the timer, its display will resume as well.
+You can adjust a running global timer via the node graph.
+Change Value
+  If the timer is counting down, a positive number will increase 
+its remaining time, and a negative number will decrease its remaining time.
+ For stopwatch timers, positive values increase the accumulated time, and negative 
+values decrease it.
+A paused timer can have its time reduced as low as 0s. For countdowns, this will 
+trigger the timer.
+If a paused timer is set to 0s and then you increase its time, it will not be activated.
+If the UI control references the corresponding timer, its display updates along with 
+the changes.
+When the global timer's countdown ends, it will send an event to the node graph.
+Use the node graph to get the current time of a running global timer.
+Current Time
+ If the timer is counting down, returns the remaining time.
+If the timer is a stopwatch, it returns the accumulated time.
+Character Disruptor Device
+Timer
+Concept Introduction
+Functions
+Common Components
+Global Timer
+Global Timer List
+
+Add Timer
+
+Name and ID
+
+Basic Information
+
+The selected source entity needs to be configured with a global timer component.
+
+If the timer configured for the interface controls is not active when the source entity 
+is running, the UI controls will display the default value 00:00.
+
+Start Global Timer
+
+Stop Global Timer
+
+Pause Global Timer
+
+Recover Global Timer
+
+Modify Global Timer
+
+When Global Timer Is Triggered
+
+Get Current Global Timer Time
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhb3ho0k5l2w.txt

@@ -0,0 +1,98 @@
+/
+/
+/
+Node Graph Editing Guide
+I. Entry Point for Node Graph Editing
+Node graph editing must be done in the Miliastra Sandbox. Please locate the Miliastra 
+Sandbox entry point as shown in the graph below
+The main window of the Miliastra Sandbox is shown in the graph below
+II. Creating a New Node Graph
+1. Server Node Graphs
+Double-click the newly created node graph to open the Editing Tab
+You can also right-click a node graph to rename it and perform other common file 
+operations
+2. Client Serve Node Graphs
+The Client Node Graph Resource Explorer is closed by default. To open it, choose 
+Window > Client Node Graph Resource Explorer (top-left)
+The Client Node Graph Resource Explorer works like the Server Node Graph Resource 
+Explorer. In the Asset Management panel on the left, select the node graph type you 
+need, then right-click in the right panel to create a new node graph
+III. Node Graph Actions
+After entering the node graph editing tab (as shown below):
+1. Create Nodes
+The most common way to create a node is to right-click in the editing area to open the 
+node menu
+You can find specific nodes by searching through node categories
+Shown below is the [When Custom Variable Changes] node. You can find this node 
+under [Event Node] >[Custom Variable]
+Click to create a new node in the editing area
+Another common way to create nodes is through quick connections
+To do this, drag a connection from a pin outward and release without connecting to any 
+other node. This will bring up the node creation menu.
+This menu will automatically filter all nodes that match the pin type (i. e., those that can 
+be directly connected)
+2. Node Connections
+Hold and drag outward from a pin to create a connection line
+Connect it to a valid pin on another node to complete the connection
+3. Other Node Graph Operations
+Hover over a pin or connection to highlight the connection and its endpoints. This is 
+especially useful in complex graphs
+Delete: Delete nodes
+Cut: Cut the node, then you can paste with (Ctrl + V)
+Copy: Copy the node, then you can paste with (Ctrl + V)
+Disconnect Node Connection: Remove all connections to this node
+Notes: Add a comment on this node
+Generate Composite Node: See Composite Nodes
+Jump to Next Node: Jump to the next node connected to this pin
+Disconnect Link: Remove the pin's connection
+Collapse Menu: Collapse the shortcut menu
+Enter Comment: Add a comment to the node. Click to add a new comment when 
+clicking on a node
+Search Nodes: Click to open the node search tab
+Node Graph Variables: Click to open the node graph variables tab
+Signal Management: Click to open the Server Signal Explorer
+Editing Area Zoom: Zoom in/out of the edit area. You can also use the mouse wheel to 
+zoom
+Operation Log: View the operations in the current node graph
+Undo: Undo a single step of an operation
+Restore: After undoing an operation, you can redo the undo to restore the previous state
+Save: Save current node graph
+Save As: Save the current node graph as a new node graph file
+Basic Concepts
+Concept Introduction
+Functions
+Node Graphs
+Node Graph Editing Guide
+Server Node Graph (Graph A)
+
+Created Node Graph (Graph B)
+
+In the Node Graph Management interface on the left (A), choose the type you want 
+to create: Entity Node Graph, Status Node Graph, Class Node Graph, or Item Node 
+Graph
+
+In the menu on the right, Select [Create Node Graph]
+
+Create via menu
+
+Quick Creation by Connecting
+
+Connection Details
+
+Right-Click Menu Actions (Nodes)
+
+Right-Click Menu Actions (Pins)
+
+Node Graph Shortcut Menu Actions
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhbgx0rspbqu.txt

@@ -0,0 +1,88 @@
+/
+/
+/
+Item
+I. Definition of Items
+Items are virtual objects that players can obtain, use, or equip during gameplay. In 
+Miliastra Wonderland, items are categorized into multiple types and are managed 
+uniformly through the inventory
+II. Item Classification
+Items are categorized into Equipment, Materials, Consumables, and Very Special Items
+III. Editing Items
+In the item tab shown below, you can edit items
+Click the "New Item" button and click Confirm in the Pop-Up to create a new item 
+template
+Item Name: The name of the item displayed in the interface during gameplay
+Item Icon: The icon displayed in the interface during gameplay
+Configuration ID: The unique identifier of the item template, which can be used in Node 
+Graphs
+1. Basic Settings
+Basic settings primarily define an item's displayed information and how it appears in the 
+inventory
+Rarity: Rarity determines the background color of the item icon, currently available in 
+gray, green, blue, purple, and orange
+Stack Limit: The maximum number of items that can be stored in a single inventory slot 
+within the inventory
+Associated Item Node Graph: When an item enters the character's inventory, the 
+related Node Graph will be attached to the character unit
+Inventory Ownership Tab: Determines which tab the item will be sorted into when it 
+enters the inventory
+Description: The item's description that will be displayed in the interface during 
+gameplay
+Has Currency Value: Select "True" to relate a currency value to a single item, which 
+serves as a value anchor for transactions in the shop module
+Display Currency Value: Enable this to display the currency value of the item in the 
+inventory
+Currency Value: When the item has a currency value, clicking [Add Currency Value] 
+allows you to configure the specific amount
+2. Drop Settings
+Items can drop into the scene from the inventory in multiple ways, including when the 
+owner is defeated or through Node Graph triggers. The drop settings section defines the 
+specific logic executed when a drop event occurs
+Destruction Debris: The process executed when the item owner is defeated
+Loot: When the owner is defeated, items are converted into loot entities and 
+created in the scene
+Destroy: When the owner is defeated, the items are destroyed
+Save: When the owner is defeated, items are saved in the inventory. This setting is 
+only meaningful when the owner is a character. For other types of entities, the logic is 
+the same as Destroy
+Loot Drop Mechanics: Divided into Shared Reward and Individualized Reward
+Shared Reward: All players share the same loot. Once one player picks it up, other 
+players cannot pick it up
+Individualized Reward: Each player will receive their own independent copy of the 
+dropped item, and players' pickup actions do not affect each other
+Corresponding Loot Appearance: Configure a loot prefab, which is a physical entity 
+component. When the virtual item is created in the scene, it will be displayed using the 
+corresponding loot model
+3. Interaction Settings
+Interaction settings define what players can do with an item in their inventory
+Destructible: Whether players can destroy this item in their inventory through interface 
+actions
+Tradable: Whether the item can be sold in the shop
+Usable: Whether players can use an item through interface actions
+Allow Bulk Use: Whether multiple items can be used in a single operation
+Auto Use Upon Pickup: When set to "Yes", the item will be automatically used 
+upon acquisition
+Cooldown (s): After using the item, it will enter cooldown and cannot be used again 
+during this period
+Group Cooldown (s): When this item enters cooldown, all items related with the 
+Linked Cooldown Group will enter cooldown simultaneously, with a duration equal to this 
+value
+Linked Cooldown Group: Configure a list of items that defines all items within the 
+cooldown group
+Equipment
+Concept Introduction
+Advanced Concepts
+Resource System
+Item
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhciimiw86jg.txt

@@ -0,0 +1,98 @@
+/
+/
+Local Projectiles
+1. Definition of Local Projectiles
+Local projectiles are entities that are computed and rendered locally to simulate 
+projectile effects and on-hit effects
+II. Characteristics of Local Projectiles
+Local projectiles need to be predefined during editing before they can be referenced 
+and created by skill node graphs. For skill-related information, please refer to Skills
+During runtime, local projectile entities depend on the projectile motion device to 
+determine their runtime rules, and rely on on-hit detection to determine their collision 
+trigger rules and effects.
+When a local projectile entity runs, it follows the configuration set in its "Life Cycle"
+III. Editing the Local Projectile
+1. Create Local Projectiles
+After entering the combat preset tab, you can select the local projectile tab, manage 
+tabs as needed, and create corresponding local projectiles within the tab
+Click "Confirm Create" to create a new local projectile
+2. Naming and Indexing
+Each predefined local projectile name must be globally unique and a globally unique 
+prefab ID will be automatically generated.
+3. Base Attributes
+The first column is for the Base Attribute
+(1) Basic Settings
+The model configuration used by the local projectile during runtime. Selectable models 
+are sourced from the projectile model library provided by the editor.
+Supports adjusting the scaling along the X, Y, and Z axes. The zooming values are 
+preserved after switching models
+(2) Combat Parameters
+Configuration 
+Parameters
+Description
+Attribute Settings
+Provides 2 enumeration options, Inherited from Creator and In
+parameters below will differ based on the option selected
+Inherited from Creator by default
+Inherited from Creator: HP, ATK, and DEF are identical to the 
+Independent: Configure HP, ATK, and DEF as needed
+Corresponding parameters below will differ based on the optio
+Whether Subsequent 
+Settings Are 
+Influenced by the 
+Creator
+If enabled, certain unit status effects on the creator will be syn
+Only status effects that affect HP, ATK, and DEF will be synch
+(3) Life Cycle Settings
+Configuration 
+Parameters
+Description
+Permanent Duration
+If not enabled, you need to specify the duration time
+Duration
+The maximum time from initialization to destruction of this local 
+influencing factors
+X/Z Axis Destruction 
+Distance
+Except for Ability Units, this is the highest priority condition for d
+during runtime
+Local projectiles will self-destruct when exceeding the maximum
+runtime
+Y-Axis Destruction 
+Distance
+(4) End of Life Cycle Behavior Settings
+When a local projectile's life cycle ends, it will execute the configured ability units in 
+order from top to bottom.
+The ability units referenced here are those defined within the local projectile's ability unit 
+settings.
+4. Common Components
+The second column is for common components
+(1) VFX Playing Component
+For details, please see VFX Playing
+(2) Projectile Motion Device Components
+For details, please see Projectile Motion Device
+(3) On-Hit Detection Components
+For details, please see On-Hit Detection
+5. Ability Units
+The third column is for the ability units
+Local projectiles can reference ability units, which require predefined editing. For details, 
+please see Ability Units
+Ability units can be adjusted through "Advanced Editing"
+In the On-Hit Detection component, predefined ability units can be referenced and 
+executed once hit detection is triggered
+Objects
+Stage
+Concept Introduction
+Units
+Local Projectiles
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhctmgi51lpo.txt

@@ -0,0 +1,57 @@
+/
+/
+Player
+I. The Concept of Player
+Player is a special abstract entity type used to describe the "Character Ownership 
+Concept" in the game, such as:
+In Teyvat, multiple characters can be added to the player's team.
+In Beyond Mode, each player corresponds to only one character.
+II. Player Configuration
+You can reference player-specific configurations through the player template. The entry 
+point for template configuration is shown below:
+Click New Template to create a new player template
+1. Basic Information
+Basic Information Tab: Configure all available player basic information
+Effective Target: Determines which players this template applies to
+Level: Override the initial level of the class
+Spawn Point: List of available spawn points for players, see preset points 
+documentation Preset Points
+Initial Class: The initial class for this player template, see class definitions in the Class 
+document Class
+Revive: The revival rules that apply to the player, see the Revival Rules document Reviv
+e
+Special Knockdown Damage: The percentage of HP deducted when a character is 
+defeated due to special circumstances such as drowning or falling damage
+2. Components
+Components Tab: Add or view components attached to the player entity
+Overview of Available Components for Player Entity
+Custom Variables
+Global Timer
+Unit Status
+3. Node Graph
+Node Graph Configuration Tab: Add or view node graphs attached to the player entity
+III. Runtime Characteristics
+1. Non-Physical Entity
+The player entity is a pure logical entity
+2. No Placement Information
+Player entities are not directly placed in the scene, therefore there is no placement 
+information
+3. Life Cycle
+The player entity is created during stage initialization and removed when the stage is 
+destroyed
+When the user actively exits and returns to the lobby, the player entity will be removed
+Character
+Concept Introduction
+Units
+Player
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhd7nxrfa8im.txt

@@ -0,0 +1,46 @@
+/
+/
+/
+Unit Status
+1. Unit Status Component Functions
+The Unit Status Component is a component used to configure the default Unit Status  
+possessed when an entity is created
+For example: Configuring the default [Increase Movement SPD] unit status on a 
+character entity will increase their Movement SPD upon creation; configuring the default 
+[Mount Special Effects] unit status on a mechanism will make it display certain looping 
+effects upon creation
+Multiple unit status can take effect simultaneously on the unit status component
+II. Editing Unit Status Components
+Step 1: Add Unit Status Component
+1. Switch to the entity or prefab component tab
+2. Find or add a unit status component
+The unit status component is a default mounted component for all units (i.e., it will be 
+mounted by default when the entity is created). Therefore, for newly created entities or 
+prefabs, you can find the unit status component directly in the Components tab
+If it doesn't exist, you can add a unit status component through the Add Common 
+Component button
+Step 2: Add Unit Status
+On the details page of unit status, you can click [Select Status] to add a new unit status 
+configuration
+In the pop-up tab, you can view some preset unit statuses as well as unit status 
+configured by creators (Craftspeople)
+Step 3: Configure Default Unit Status
+After selecting a specific status, you can configure the default unit status and set its 
+initial layer
+Follow Motion Device
+VFX Playing
+Concept Introduction
+Functions
+Common Components
+Unit Status
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhdtk89yhd6q.txt

@@ -0,0 +1,18 @@
+Concept Introduction
+This directory explains the various basic concepts that creators (Craftspeople) might 
+encounter when editing their own stages, as well as introduces their specific uses and 
+configuration methods.
+Interface Guide
+Node Introduction
+Concept Introduction
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhdznsie9up8.txt

@@ -0,0 +1,83 @@
+/
+/
+Environment Configuration
+I. Definition of Environment Configuration
+Environment Configuration includes a series of environment-related parameters that 
+enrich how elements in the Scene are presented
+Environment Configurations must be predefined and applied to each player's client
+II. Editing Environment Configuration
+Switch to the Terrain Editing tab to select Environment Configurations on the left.
+Click [New Environment] and [Confirm Create] to create a new Environment 
+Configuration
+1. Background Settings
+Choose a background preset to determine the Scene's overall style
+Auto switch with time: When enabled, the sun and moon, lighting angles, and intensity 
+in the scene change over time. Define the starting time and in-game time flow rate in 
+Stage Settings, or adjust them via the Node Graph.
+If Auto switch with time is disabled, additional parameters must be configured:
+Set Time Point: Fixes the Scene presentation to a specific time point.
+Background Rotation: Adjusts the background's rotation angle along the Y-axis
+Direct angle, intensity, blur, light color: Adjust parameters of the primary directional 
+light source
+Filter Style: Applies a filter effect to the camera layer
+Sky Background Color: Background color of the skybox
+2. Environmental Elements
+Stars: When enabled, density and intensity can be adjusted
+Galaxy: When enabled, intensity and light color can be adjusted
+Clouds: When enabled, intensity and the toggle for high, medium, and low-level clouds 
+can be adjusted
+3. Light Source List
+The light sources bound to this Environment Configuration are activated together with 
+the Configuration.
+(1) Light Source Configuration Entry Point
+(2) Light Source Configuration
+Light Source Parameter Settings:
+Source File: Indicates which Environment Configurations reference this light source
+Location, Rotation: Controls its Location and Rotation in the Scene.
+Light Source Type: Currently supports Point Light and Spotlight.
+Color: Sets the color shown on illuminated models
+Radius: Illumination radius
+Intensity: Degree of color or brightness change on the illuminated model
+Effective Range: The light source is loaded only when a character enters this range. 
+Used for performance optimization.
+4. Weather
+Multiple Weather configurations can be set within a single Environment Configuration 
+and enabled together with it
+Weather Type: Fog
+Distance Fog Settings: Based on Camera Location, creates a fog effect that occludes 
+distant models and the skybox.
+High Fog Settings: Based on Scene height, creates a fog effect that occludes distant 
+models and the skybox.
+III. Using Environment Configuration
+The initial player list for the environment configuration can be configured
+Also switch via the Node Graph
+IV. Environment Time
+Define the starting time and in-game time flow rate in Stage Settings, or adjust them via 
+the Node Graph.
+The environment time can also be adjusted through nodes:
+The Environment Time is a globally unique running value. Regardless of the 
+Environment Configuration applied by each player, the server continuously advances 
+Environment Time. The visual effects of time changes are visible only when an active 
+Environment Configuration has Auto switch with time enabled
+Background Music
+Prefab Group
+Concept Introduction
+Other Concepts
+Environment Configuration
+Click "Add Light Source" > "Open Light Source Manager" to access the Light 
+Source Management Tool
+
+Click the system menu in the top left corner, then click Manage Light Source] to 
+open the Light Source Management Tool
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhe1030vx380.txt

@@ -0,0 +1,66 @@
+/
+/
+Special Effects
+I. Definition of Special Effects
+Special effects are art assets that can be used to enhance visual effects during 
+gameplay.
+Special effects must be attached to an entity, with each effect having a designated 
+mount entity.
+When a special effect plays, it uses the entity's Attachment Point as its origin and 
+follows that point's position at runtime.
+Referencing a special effect requires a VFX Player component. VFX Playing .
+II. Classification of Special Effects
+Based on the playback duration of special effect assets, timed effects pools and looping 
+effects pools are provided
+1. Timed Effects
+Timed special effects have an effective duration.
+Timed effects will only play once when triggered, and will not repeat.
+2. Looping Effects
+Looping effects have no fixed duration and continue playing until stopped or removed.
+III. Using Special Effects
+1. Component Mounting
+Supports mounting effects via the VFX Playing Component during prefab/entity 
+editing. These effects are created alongside the entity
+For editing details, please refer to VFX Playing  for use.
+2. Usage in Node Graphs
+Supports creating and deleting special effect assets via effect-related nodes in the 
+node graph.
+Different reference special effect asset nodes are provided for different special 
+effect types.
+Effects from the timed effect pool can be referenced by selecting entities with the 
+"VFX Playing Component" and configuring Attachment Points.
+If the Attachment Point is incorrect, the special effect will not play
+If no Attachment Point is specified, it defaults to the GI_RootNode
+Effects from the looping effects pool can be referenced by selecting entities with the 
+"VFX Playing Component" and configuring Attachment Points.
+If the Attachment Point is incorrect, the special effect will not play
+If no Attachment Point is specified, it defaults to the GI_RootNode
+Looping effects created by the "Mount Looping Special Effect" node can be cleared 
+using this node
+Clear the specified special effect assets from the selected runtime entity
+Click the 
+ icon to view all special effect enumerations and select the 
+specified special effect asset
+Preset Status
+Concept Introduction
+Assets
+Special Effects
+Play Timed Effects
+
+Mount Looping Special Effect
+
+Clear Looping Special Effect
+
+Clear Special Effects Based on Special Effect Assets
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhe1ixri46ta.txt

@@ -0,0 +1,58 @@
+/
+/
+/
+Factions
+In order to create competitive gameplay, entities are divided into different groups where 
+players belonging to the same group share the same game objectives. This group is 
+called a faction
+In team-based competitive games, factions can serve as criteria for settlement 
+objectives or score calculation
+I. Global Definition of Factions
+Before selecting a faction in Basic Info, you need to first define the required factions in 
+the faction tab of the stage settings
+Faction Name: The name given to this faction
+Default Faction Unit: New players/objects/creations will be categorized into the 
+corresponding default faction
+Players Included: A list of players representing who initially belong to this faction
+Entities Included: A list of objects and creations that initially belong to this faction
+II. Faction Relations
+Between any two factions, there must exist two types of relationships: Hostile and 
+Friendly, which can be configured through the Faction Relations in the stage settings
+Note that faction relations are one-way. Faction 1 may be hostile towards Faction 2, but 
+Faction 2 isn't necessarily hostile towards Faction 1. There could be situations where 
+Faction 2 is friendly towards Faction 1, in which case only entities from Faction 1 can 
+attack Faction 2, while entities from Faction 2 cannot attack Faction 1
+For example, as shown in the graph: The initial player faction is hostile towards both the 
+initial object faction and initial creation faction, therefore they can directly attack entities 
+(characters, creations or objects) belonging to these two factions
+In other systems, faction-related settings work according to the faction relations defined 
+in the stage configuration. For example, the ability unit in the graph below will correctly 
+target enemies from hostile factions
+III. Default Faction Configuration
+Each faction can be configured with a default faction unit. When an entity of this object 
+type (such as players and objects shown in the image) is created with a default faction 
+(faction value of 0), it will be assigned to the default faction for that entity type
+For example, in the graph above, if no faction is overridden for this Stone Ball prefab 
+when it is created, it will be created with [Initial Object Faction] (because the default 
+faction for objects is Initial Object Faction)
+IV. Using Node Graph to Control Player Factions
+Entity Faction Change Events
+Modify Entity Faction
+Query Entity Faction
+Model
+Unit Tag
+Concept Introduction
+Functions
+Basic Information
+Factions
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhe8yn9bysd6.txt

@@ -0,0 +1,52 @@
+/
+/
+Flow Control Node
+I. General
+1. Multiple Branches
+Node Functions
+Accepts one input parameter as the control expression (supports Integer or String). 
+Branches into multiple paths based on its value
+When the value on an Output Pin equals the control expression, execution continues 
+along that Output Pin. If no pin matches, the [Default] pin is taken
+Node Parameters
+Paramete
+r Type
+Parameter Name
+Type
+Description
+Input 
+Parameter
+Control Expression
+Generic
+Only supports Intege
+2. Double Branch
+Node Functions
+Branches into True or False based on the evaluated condition
+When the Boolean is True, the [True] execution flow runs; when it is False, the [False] 
+execution flow runs
+Node Parameters
+Paramete
+r Type
+Parameter Name
+Type
+Description
+Input 
+Parameter
+Condition
+Boolean
+Event Nodes
+Query Nodes
+Node Introduction
+Server Nodes
+Flow Control Node
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhei6orvcbkm.txt

@@ -0,0 +1,33 @@
+/
+/
+Common Components
+Components are functions that can be added to entities.
+After adding components to an entity, the entity can use the corresponding functions, 
+and you can modify the component's data and logic through the node graph.
+Common components can be freely added and deleted on prefabs or entities.
+Some units will come with their commonly used components by default.
+I. Editing Common Components
+After selecting a prefab or entity, you can view the configured components or add and 
+delete components in the Common Components tab on the right
+II. Component Life Cycle
+Components can only be added to or removed from prefabs and entities during editing, 
+and cannot be dynamically added or removed during gameplay. Some components can 
+be enabled or disabled through node graphs
+When an entity exists in the scene, its component functions will remain active until the 
+entity is destroyed or removed
+Specialized Settings
+Node Graphs
+Concept Introduction
+Functions
+Common Components
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhen7r0djxkg.txt

@@ -0,0 +1,31 @@
+/
+/
+/
+Pop-Up UI Controls
+I. Pop-Up Functions
+An interface that appears while running a stage due to logic triggers. It is used to 
+provide information, hints, options, or interactions for players. 
+II. Editing Pop-Up Window
+Title  
+Text shown in the title area (see the graph)
+Text Content   
+Text in this area (see the graph) is the same as the content in the text box, supporting 
+the insertion of custom variables for players and stages
+During stage runtime, the displayed text updates in real time as custom variables change
+Text Box UI Controls
+Progress Bar UI Controls
+Concept Introduction
+Assets
+UI Controls
+Pop-Up UI Controls
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhesro0hyn5k.txt

@@ -0,0 +1,40 @@
+/
+/
+/
+Scoreboard UI Controls
+I. Scoreboard Functions
+Displays the player's custom variables during stage runtime and ranks them accordingly
+II. Editing the Scoreboard
+Configuration Parameters
+Description
+Sort
+Provide ascending and 
+descending order for values
+Type
+The selection of self, faction, 
+or type will affect the 
+configuration content of the 
+remaining parameters
+III. Types of Scoreboard
+Type
+Scoreboard Style
+Style Settings
+Self
+Faction
+Timer UI Controls
+Deck Selector UI Controls
+Concept Introduction
+Assets
+UI Controls
+Scoreboard UI Controls
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhewyi0fjfvs.txt

@@ -0,0 +1,180 @@
+/
+/
+UI Control Groups Management
+UI Control Groups Management provides unified management of Interface Layouts and 
+UI Control Groups.
+I. Entry Point
+Click the System menu in the upper left corner and select [Manage UI Control Groups] 
+to open the management interface
+It is divided into the Menu Bar, Library Window, Details Window, Preview Window, 
+Editing Button Area, and Parameter Configuration Window
+II. UI Layout Management Tool
+1. Interface Layout
+By default, it includes the "Default Layout" interface, which contains the essential UI 
+Control Groups for Stage execution
+The Interface Layout Library cannot be empty; it must contain at least one Interface 
+Layout
+When switching between Interface Layouts, you can view the changes simultaneously in 
+the Layout Preview Window
+Right-click to copy, paste, or rename
+2. Interface Layout Details
+The currently selected Interface Layout lists its contents, enumerated based on UI 
+Control Groups.
+You can add UI Control Groups to the current Interface Layout through [Add UI 
+Control]
+(1) Inherent Content
+This category includes UI Control Groups that are essential for processes and functions.
+When managed through the Node Graph, only the display state can be modified; 
+removal is not supported.
+Position and size cannot be adjusted. Takes effect by default and cannot be changed.
+Configuration 
+Parameters
+Description
+Index
+Unique identifier for the current UI Control Group/UI Control
+Initially Visible
+Whether this UI Control Group is visible when the Stage runs and this
+Interface Layout takes effect
+(2) Custom
+Custom or prefabricated UI Controls added through [Add UI Control] belong to this 
+category
+When managed through the Node Graph, only display states can be modified; removal 
+is not supported
+Position and size can be adjusted. Takes effect by default and cannot be changed.
+Configuration 
+Parameters
+Description
+Index
+Unique identifier for the current UI Control Group/UI Control
+Initially Visible
+Controls whether this UI Control Group is visible when the Interface L
+takes effect
+Text Box 
+Settings
+Configure the color, font size, and content of the text box
+3. Interface Layout Preview Window
+Preview the basic visual effects of the Interface Layout being edited
+You can adjust devices for comparison
+4. Parameter Configuration Window
+The default application configuration for the current Interface Layout, which serves as 
+the default Interface after a Player runs the Stage
+[Open Player Editor] will transit to the Class  configuration interface, where you can 
+configure its default Interface Layout
+III. UI Control Groups Management Tool
+1. UI Control Group Custom Templates
+UI Control Groups saved as Custom Templates are enumerated here
+Right-click to perform operations on the selected custom template
+Rename the custom template for UI Control Group
+Delete Selected Template
+Delete the template. If there are references, all references (Interface Layouts and UI 
+Control Group Details) will be deleted together.
+UI Control Group Details Window After saving the UI Control Group being edited as a 
+custom template, it will appear in the UI Control Group Library
+When a custom template in the UI Control Group Library is selected
+2. UI Control Group Details
+Display enumeration of UI Control Groups being edited
+Only UI Control Groups within this window can be edited
+Template references in this interface support modifying and saving by overwriting the 
+template
+Use [Add UI Control Template] to create a UI Control Group based on the prefabricated 
+UI control assets
+(1) UI Control Group
+(2) UI Control Group Preview Window.
+3. Editing Button Area
+The interaction below the preview window only affects the UI Control Group being edited
+(1) UI Control Group — Multiple UI Controls
+Configuration 
+Parameters
+Description
+Create 
+Combination
+Packages the selected UI Controls into a combination
+Delete multiple selected UI Control Groups
+Configuration 
+Parameters
+Description
+Disband 
+Combination
+Split the group into individual UI Control Groups and delete the combi
+Delete this UI Control Group
+Save Changes
+If the group content is modified, you will be prompted to save and ove
+Save as 
+Template
+Save the current data as a new UI Control Group template
+(2) UI Control Group — Single UI Control
+Configuration 
+Parameters
+Description
+Delete this UI Control Group
+Save Changes
+If the UI Control Group on this Interface changes, you will be prompte
+(overwrite)
+Save as 
+Template
+Save the current data as a new UI Control Group template
+4. Parameter Configuration Window
+(1) UI Control Group — Multiple UI Controls
+Configuration 
+Parameters
+Description
+Initially Visible
+Default display state when the UI Control Group template is activated
+Location
+Location on the Interface Layout
+Size
+Not editable. Represents the maximum bounds of the UI Control Grou
+Layer
+Represents the display layer of the UI Control Group
+(2) UI Control Group — Single UI Control
+Configuration 
+Parameters
+Description
+Initially Visible
+Default display state when the UI Control Group template is activated
+Location
+Location on the Interface Layout
+Size
+Not editable. Represents the maximum bounds of the UI Control Grou
+Layer
+Represents the display layer of the UI Control Group
+Main Camera
+Concept Introduction
+Advanced Concepts
+UI Control Groups Management
+Rename
+
+Delete Template
+
+If there is no reference to a custom template in the UI Control Group Details, 
+clicking a target in the library will create a reference in UI Control Group Details 
+and select it by default for editing. After editing, you can overwrite the template 
+content or save it as a new template.
+
+If a reference to this template already exists in UI Control Group Details, a single 
+click selects the corresponding reference in "UI Control Group Details" for 
+overwriting and modifying the template content.
+
+Select multiple UI Controls/UI Control Groups using the mouse or by holding Shift.
+
+Right-click [Create Combination], or click [Create Combination] in the Editing Button 
+Area to generate a UI control group composite and create an Index.
+
+An individual UI Control can also be directly [Saved] to generate a UI Control 
+Group and generate an index.
+
+Preview the basic effects of the UI Control Group being edited.
+
+You can adjust devices for comparison
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhexhcr1qjh2.txt

@@ -0,0 +1,42 @@
+/
+Combat Preset
+I. Edit Module Switch
+Use the left sidebar to switch Edit Modules, listed from top to bottom as:
+II. Create and Save
+Use the New button in the Assets Bar to create content for the currently selected Edit 
+Module.
+Changes made in the Character and Class Editing module are saved automatically. 
+Changes to Unit Statuses, Skills, Local Projectiles, and Items must be saved manually. 
+A yellow exclamation mark in the Assets Bar (as shown in the image) indicates unsaved 
+content. Use the Save button at the bottom (as shown) to save or save as new content.
+III. Switch Gender
+Use the gender toggle at the bottom to switch the model's gender in the Miliastra 
+Sandbox.
+IV. Reset Camera
+In the Combat Preset module, right-click an empty area of the scene to open the Reset 
+Camera option. Selecting it returns the Camera to its initial state
+Prefab Library
+Stage Settings
+Interface Guide
+Combat Preset
+Player and Class Editor: Player Character Classes
+
+Unit Status Editor: Unit Status
+
+Skill Editor: Skill
+
+Local Projectile Editor: Local Projectile
+
+Item Editor: Items
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mheybl0mdcqo.txt

@@ -0,0 +1,20 @@
+/
+Advanced Concepts
+When certain data must be pre-defined at the global level of a stage in order to be 
+accessed and utilized by multiple units or modules, it is referred to as an "advanced 
+concept."
+Assets
+Other Concepts
+Concept Introduction
+Advanced Concepts
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhf45sisuup8.txt

@@ -0,0 +1,117 @@
+/
+/
+/
+Rank
+I. Rank Functions
+The Rank Function allows creators (Craftspeople) to define player rank points within a 
+stage. During stage settlement, players will receive different rank points based on 
+different settlement status. The points for each state can be customized by the creator 
+(Craftsperson).
+When other players browse the stage information in the main hall, they can see 
+recorded ranking information, as shown in the graph below:
+At the end of the match, players' rank points will be calculated accordingly
+II. Editing Score Groups
+Click [Manage Peripheral System] in the System menu to enter the Peripheral System 
+Settings interface
+In the Peripheral System Settings interface, go to the Rank tab to configure Rankings-
+related settings
+Rank points are modified through preset score group templates, with each player in the 
+match using one score group template. Click the "New Scoring Group" button in the 
+bottom right to create a new score group template
+Enable competitive ranking?: Choose to enable either the Leaderboard or Rank Function
+Enable in-room score calculation: Whether to allow rank points adjustments when 
+players play this stage through room teams instead of matchmaking
+Craftsperson's Message: Allows creators (Craftspeople) to write detailed Rank Points 
+Scoring Rules that will be displayed in the stage information interface outside of matches
+Score Group Settings: Specific point value settings for each score group template
+Score Group Name: Can be customized, used by creators (Craftspeople) to 
+distinguish between different score groups
+ID: The identifier for this score group, used to identify when modifying score group 
+data within a node graph
+Victory Score: Rank points earned when a player settles with the victory state
+Defeat Score: Rank points earned when a player settles with the defeat state
+Undecided Score: Rank points awarded when a player completes a stage in the 
+undefined state
+Escape Score: Rank points earned when a player settles with the escape state
+Players Included: Which players this score group applies to
+III. Rank Score Template Configuration 
+Suggestions
+It is recommended to configure the scores according to the expected duration of the 
+gameplay and the actual playing experience, referring to the following score table.
+Expected Gameplay 
+Duration (minutes)
+Victory
+Defeat
+0-2
+20
+-5
+2-4
+40
+-10
+4-6
+60
+-15
+6-8
+80
+-20
+8-10
+100
+-25
+10-15
+120
+-30
+15-20
+140
+-35
+20-30
+160
+-40
+30-40
+180
+-45
+40-999
+200
+-50
+IV. Special Situations for Rank Score Handling
+1. Fleeing Penalties in Special Circumstances
+Players may flee for various reasons, such as a large number of teammates fleeing or 
+AFK, disconnection due to network issues, or the match becoming unplayable due to a 
+significant power imbalance in the later stages. Creators (Craftspeople) can handle 
+fleeing penalties based on the actual situation of the stage.
+2. Win Streak
+When players achieve consecutive wins, they can be given additional score rewards 
+based on a certain percentage of their victory points.
+3. Consecutive Escapes
+When players escape consecutively, additional penalties can be applied.
+4. Rank Protection
+It is recommended to implement a rank protection mechanism. For example, if a player 
+reaches the Silver rank and losing points would cause them to drop to the Bronze rank, 
+they should be protected from dropping. 
+If any of the above special handling measures are implemented, it is suggested that 
+creators (Craftspeople) explain them in the rank-related announcements.
+V. Node Graph Management of Score Group Data
+Leaderboard
+Achievements
+Concept Introduction
+Advanced Concepts
+Peripheral System
+Rank
+Switch the scoring group that affects playher's competitive rank
+
+Set Player Rank Score Change
+
+Get Player Rank Score Change
+
+Get Player Rank Info
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhfc0lr1tcke.txt

@@ -0,0 +1,172 @@
+/
+/
+/
+Scan Tag
+I. What is the Scan Function
+The scan function allows players to select an entity during gameplay by using the 
+camera.
+The scanned target can be configured to display special effects, such as unique icons 
+or special effects.
+In skill usage logic, scanned targets can also be retrieved via nodes from the relevant 
+node graph, allowing selection of specific skill targets.
+Whether an entity can be scanned and its status display after being scanned can be 
+defined through scan tags and implemented through scan components to assign logic 
+to prefabs and entities.
+II. Editing Scan Tags
+A scan tag defines the filtering logic and display settings for a scannable object. It must 
+be defined globally in advance. Access the scan tag definition interface via "Scan Tag 
+Management" in the system menu
+After entering the Scan Tag Definition interface, the editing interface will be divided into 
+three main sections:
+1. Scan Tag List
+2. Scan Tag Effect Preview
+3. Scan Tag Logic Configuration
+1. Scan Tag List
+All defined scan tags can be found in this interface, making it convenient for creators 
+(Craftspeople) to filter and search globally
+Click the "Create New Scan Tag Template" button to add a new scan tag
+2. Scan Tag Logic Configuration
+The configuration section determines the rules by which prefabs and entities with this 
+tag will be scanned during gameplay, and their behaviors when scanned. It is divided 
+into two tabs: "Status Performance" and "Effective Conditions"
+(1) Basic Definition
+Scan Tag Name: The name of the scan tag, used for identification only
+Configuration ID: Data type serves as the configuration ID, which is the unique identifier 
+of this scan tag, used to index this scan tag within the node graph
+(2) Status Performance
+Icon Settings: When a prefab or entity with this scan tag is selected by the scan logic, a 
+hint icon will appear. This section configures the related display properties of that icon
+Select Icon: Configure an icon resource group corresponding to different selection 
+states. This field can be left empty, in which case no icon will be displayed. Up to two 
+icons can appear on-screen simultaneously
+Attachment Point: The icon is displayed at the attachment point of the 
+corresponding entity's name
+Offset: The offset position of the icon
+Selection State: For a scannable entity, there are three selection states. The icon 
+display differs for each state
+Active State: The state when currently selected by the scan function. Only one 
+entity can be in the active state at any given moment
+Available State: The state when active state conditions are met but not yet 
+activated, usually due to the existence of other higher-priority targets that are already 
+active
+Disabled State: The state when effective conditions are not yet met
+The corresponding runtime behavior is illustrated in the graph below:
+Special Effects Settings
+Activated Status Effects: Effect configuration that will be applied when an entity carrying 
+the scan tag component is in the active state
+VFX Assets: Creators (Craftspeople) can select a suitable special effect asset here 
+to apply as the effect
+Attachment Point: The effect is applied at the corresponding unit's attachment point 
+and automatically follows its position and rotation
+Zoom Factor: The actual scale at which the effect asset is played
+Offset: Additional offset based on the above attachment point position
+Rotation: Additional rotation applied relative to the attachment point above
+Available Status Effects: Effect setting that will be applied when an entity carrying the 
+scan component is in the available state
+The configurable parameters are consistent with the activated status effects
+Disable Status Effects: Effect configuration that will be applied when an entity carrying 
+the scan component is in a disabled state
+The configurable parameters are consistent with the activated status effects
+(3) Effective Conditions
+The effective conditions describe the conditions which must be met to put a scannable 
+entity into the available state
+Local Filter: Boolean filter and integer filter can be selected
+Filter Node Graph::Can be associated with a local filter node graph of the selected 
+type. If the return value of the local filter does not meet the conditions, the entity will not 
+participate in the state calculation and will be considered as a non-scannable object.
+Obstacle Detection: Obstacle detection is used to verify line-of-sight between the local-
+controlled character and scanned entities. It determines whether there are obstructions 
+between the character and the scanned object. When enabled, if the ray detection fails, 
+the entity will be disabled.
+Obstacle Detection Point: The name of the unit attachment point on the scanned object. 
+This serves as the target point for ray detection
+Ignore Water Surface: When enabled, if a water surface collider is detected between 
+the player and entity, it will be ignored and treated as if there is no obstruction
+Distance Detection: Used to define the available range of a scannable entity. This 
+determines the distance within which the scannable object and local character are 
+available
+Distance Detection Point: Distance detection evaluation is based on the position of the 
+configured unit attachment point
+Detection Range: If the scanned entity is not within the configured range, it will be 
+disabled. The range can be previewed directly in the scene
+Line of Sight Detection: Line of sight detection is used to determine whether there are 
+any obstacles between the local camera and the scanned object. When enabled, if the 
+ray detection fails, the entity will be disabled.
+Line of Sight Detection Point: The unit attachment point on the scanned object used as 
+the target for ray detection
+Ignore Water Surface: When enabled, if a water surface is detected between the local 
+camera and entity, it will be ignored and treated as if there is no obstruction
+Ignore Obstacles: When enabled, line of sight detection ignores all obstacles
+FOV Range Settings: Requires that the scanned entity must be within an elliptical area 
+at the center of the screen, otherwise the entity will be disabled
+FOV Detection Point: Detection is based on the unit attachment point position as 
+set on the entity
+Ellipse Horizontal Axis Ratio: The ratio of the ellipse's left and right borders relative 
+to the screen width
+Ellipse Vertical Axis Ratio: The ratio of the ellipse's top and bottom borders to the 
+screen height
+Click "Preview FOV" below to visually preview the effective range, as shown in the 
+following graph:
+III. Editing Scan Tag Components
+1. Adding Components
+(1) In the Entity or Prefab editing interface, open the Component Editing Tab
+(2) Click "Add Components" below, then select and click "Scan Tag" to add it
+2. Scan Tag Component Settings
+The scan tag component can be configured with multiple alternative scan tag templates, 
+but only one scan tag can take effect during gameplay. This can be dynamically 
+switched using node graphs
+Initially Effective: Default active scan tag
+Scan Tag List: All scan tags contained in this component
+Click Advanced Editing to enter the editing interface
+In this interface, click the Add button to add a new scan tag and set its scan tag 
+template reference
+Scan Tag ID: Used as an identifier when switching node graphs dynamically
+Initially Effective: Determines whether the scan tag is active initially. Only one scan tag 
+can be active at a time
+Reference Scan Tag: Select and reference pre-defined global scan tags
+IV. Scan Tag Filtering Logic
+The previous section on Scan Tag Logic Configuration introduced under what conditions 
+a single scan object would be considered available. When multiple available scan 
+objects are present simultaneously, only one scan object will be set to the active state. 
+The filtering rules are defined by the class attribute "Scan Tag Recognition Rules"
+For more class information, please check Classes
+Scan Tag Recognition Rules: Rules for filtering active units from all available Scanned 
+Objects
+Distance From Center of FOV: Scan tags closest to the center of the view are 
+prioritized for activation
+Actual Position Distance: Gives priority to activating scan tags nearest to the player 
+character
+V. Scan Tag Node Graph Nodes
+Server Nodes
+Client Node
+Shop Component
+Mini-Map Marker
+Concept Introduction
+Functions
+Common Components
+Scan Tag
+Set Scan Tag Rules
+
+Set Scan Component's Active Scan Tag ID
+
+Get Current Active Scan Tag Config ID
+
+Get All Valid Entities That Are Scannable by Scan Component
+
+Get Entity Currently Scanned by Scan Component
+
+Get Entity's Current Active Scan Tags
+
+Get Entity's Scan Status
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhfmxw9fn6n6.txt

@@ -0,0 +1,614 @@
+/
+/
+Operation Nodes
+I. General
+1. Enumeration Match
+Node Functions
+After confirming the Enumeration type, determines whether the two input values are 
+equal
+Node Parameters
+Paramete
+r Type
+Parameter Name
+Type
+Description
+Input 
+Parameter
+Enumeration 1
+Generic
+Input 
+Parameter
+Enumeration 2
+Generic
+Output 
+Parameter
+Result
+Boolean
+Output True if equal,
+2. Equal
+Node Functions
+Determines whether two inputs are equal
+Some Parameter Types have special comparison rules:
+Floating Point Numbers: Floating Point Numbers are compared using approximate 
+equality. When the difference between two Floating Point Numbers is less than an 
+extremely small value, the two numbers are considered equal. For example: 2.0000001 
+and 2.0 are considered equal
+3D Vector: The x, y, and z components of a 3D Vector are compared using Floating 
+Point approximate equality
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Generic
+Input Parameter
+Generic
+Output Parameter
+Result
+Boolean
+3. Data Type Conversion
+Node Functions
+Converts input parameter types to another type for output. For specific rules, see Basic 
+Concepts  - [Conversion Rules Between Basic Data Types]
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Input
+Generic
+Output Parameter
+Conversion Result
+Generic
+II. Math
+1. Split 3D Vector
+Node Functions
+Outputs the x, y, and z components of a 3D Vector as three Floating Point Numbers
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+3D Vector
+3D Vector
+Output Parameter
+X-Component
+Floating Point Numb
+Output Parameter
+Y-Component
+Floating Point Numb
+Output Parameter
+Z-Component
+Floating Point Numb
+2. Orientation to Rotation
+Node Functions
+Converts a Direction Vector to Euler Angles
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Orientation
+3D Vector
+Output Parameter
+Rotate
+3D Vector
+3. Multiplication
+Node Functions
+Performs multiplication, supporting Floating Point and Integer multiplication
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Generic
+Input Parameter
+Generic
+Output Parameter
+Result
+Generic
+4. Division
+Node Functions
+Performs division, supporting Floating Point division and Integer division. Integer division 
+returns the quotient result
+The divisor should not be 0, otherwise it may return an illegal value
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Generic
+Input Parameter
+Generic
+Output Parameter
+Result
+Generic
+5. Arccosine Function
+Node Functions
+Calculates the arccosine of the input and returns the value in radians
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Input
+Floating Point Numb
+Output Parameter
+Radian
+Floating Point Numb
+6. Arctangent Function
+Node Functions
+Calculates the arctangent of the input and returns the value in radians
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Input
+Floating Point Numb
+Output Parameter
+Radian
+Floating Point Numb
+7. Arcsine Function
+Node Functions
+Calculates the arcsine of the input and returns the value in radians
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Input
+Floating Point Numb
+Output Parameter
+Radian
+Floating Point Numb
+8. Direction Vector to Rotation
+Node Functions
+Converts the Forward Vector and Upward Vector to Euler Angles
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Forward Vector
+3D Vector
+Input Parameter
+Upward Vector
+3D Vector
+Output Parameter
+Rotate
+3D Vector
+9. Radians to Degrees
+Node Functions
+Converts radians to degrees
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Radian
+Floating Point Numb
+Output Parameter
+Angle
+Floating Point Numb
+10. Get Random Number
+Node Functions
+Returns a random number in [Lower Limit, Upper Limit] (inclusive)
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Lower Limit
+Generic
+Input Parameter
+Upper Limit
+Generic
+Output Parameter
+Random Number
+Generic
+11. Addition
+Node Functions
+Adds two Floating Point Numbers or Integers
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Generic
+Input Parameter
+Generic
+Output Parameter
+Result
+Generic
+12. Subtraction
+Node Functions
+Subtracts two Floating Point Numbers or Integers
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Generic
+Input Parameter
+Generic
+Output Parameter
+Result
+Generic
+13. Degrees to Radians
+Node Functions
+Converts degrees to radians
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Angle
+Floating Point Numb
+Output Parameter
+Radian
+Floating Point Numb
+14. Absolute Value Operation
+Node Functions
+Returns the absolute value of the input
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Input
+Generic
+Output Parameter
+Result
+Generic
+15. Logical NOT Operation
+Node Functions
+Performs a logical NOT operation on the input Boolean value and returns the result
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Condition
+Boolean
+Output Parameter
+Result
+Boolean
+16. Logical OR Operation
+Node Functions
+Performs a logical OR operation on the two input Boolean values and returns the result
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Condition 1
+Boolean
+Input Parameter
+Condition 2
+Boolean
+Output Parameter
+Result
+Boolean
+17. Logical XOR Operation
+Node Functions
+Performs a logical XOR operation on the two input Boolean values and returns the result
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Condition 1
+Boolean
+Input Parameter
+Condition 2
+Boolean
+Output Parameter
+Result
+Boolean
+18. Logical AND Operation
+Node Functions
+Performs a logical AND operation on the two input Boolean values and returns the result
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Condition 1
+Boolean
+Input Parameter
+Condition 2
+Boolean
+Output Parameter
+Result
+Boolean
+19. 3D Vector Normalization
+Node Functions
+Normalizes the length of a 3D Vector and outputs the result
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+3D Vector
+3D Vector
+Output Parameter
+Result
+3D Vector
+20. 3D Vector Addition
+Node Functions
+Calculates the sum of two 3D Vectors
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+3D Vector 1
+3D Vector
+Input Parameter
+3D Vector 2
+3D Vector
+Output Parameter
+Calculation Result
+3D Vector
+21. 3D Vector Angle
+Node Functions
+Calculates the angle between two 3D Vectors and outputs the value in degrees
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+3D Vector 1
+3D Vector
+Input Parameter
+3D Vector 2
+3D Vector
+Output Parameter
+Angle
+Floating Point Numb
+22. 3D Vector Subtraction
+Node Functions
+Calculates the difference of two 3D Vectors
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+3D Vector 1
+3D Vector
+Input Parameter
+3D Vector 2
+3D Vector
+Output Parameter
+Calculation Result
+3D Vector
+23. 3D Vector Modulo Operation
+Node Functions
+Calculates the magnitude of the input 3D Vector
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+3D Vector
+3D Vector
+Output Parameter
+Result
+Floating Point Numb
+24. 3D Vector Dot Product
+Node Functions
+Calculates the dot product of two input 3D Vectors
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+3D Vector 1
+3D Vector
+Input Parameter
+3D Vector 2
+3D Vector
+Output Parameter
+Calculation Result
+Floating Point Numb
+25. 3D Vector Zoom
+Node Functions
+Scales the input 3D Vector (scalar multiplication) and outputs the result
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Zoom Multiplier
+Floating Point Numb
+Input Parameter
+3D Vector
+3D Vector
+Output Parameter
+Result
+3D Vector
+26. 3D Vector Cross Product
+Node Functions
+Calculates the cross product of two 3D Vectors
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+3D Vector 1
+3D Vector
+Input Parameter
+3D Vector 2
+3D Vector
+Output Parameter
+Calculation Result
+3D Vector
+27. 3D Vector Rotation
+Node Functions
+Rotates the input 3D Vector by the Euler Angles specified by the rotation and returns 
+the result
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Rotated 3D Vector
+3D Vector
+Input Parameter
+Rotate
+3D Vector
+Output Parameter
+Result
+3D Vector
+28. Greater Than
+Node Functions
+Returns whether the left value is greater than the right value
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Generic
+Input Parameter
+Generic
+Output Parameter
+Result
+Boolean
+29. Greater Than or Equal To
+Node Functions
+Returns whether the left value is greater than or equal to the right value
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Generic
+Input Parameter
+Generic
+Output Parameter
+Result
+Boolean
+30. Less Than
+Node Functions
+Returns whether the left value is less than the right value
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Generic
+Input Parameter
+Generic
+Output Parameter
+Result
+Boolean
+31. Less Than or Equal To
+Node Functions
+Returns whether the left value is less than or equal to the right value
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Generic
+Input Parameter
+Generic
+Output Parameter
+Result
+Boolean
+32. Cosine Function
+Node Functions
+Calculates the cosine of the input in radians
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Radian
+Floating Point Numb
+Output Parameter
+Result
+Floating Point Numb
+33. Tangent Function
+Node Functions
+Calculates the tangent of the input in radians
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Radian
+Floating Point Numb
+Output Parameter
+Result
+Floating Point Numb
+34. Sine Function
+Node Functions
+Calculates the sine of the input in radians
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+Radian
+Floating Point Numb
+Output Parameter
+Result
+Floating Point Numb
+35. Create 3D Vector
+Node Functions
+Creates a 3D Vector from x, y, and z components
+Node Parameters
+Parameter Type
+Parameter Name
+Type
+Input Parameter
+X-Component
+Floating Point Numb
+Input Parameter
+Y-Component
+Floating Point Numb
+Input Parameter
+Z-Component
+Floating Point Numb
+Output Parameter
+3D Vector
+3D Vector
+III. Lists
+1. Assembly List
+Node Functions
+Assembles multiple Input Parameters of the same type (up to 100) into a single List
+Node Parameters
+Paramete
+r Type
+Parameter Name
+Type
+Description
+Input 
+Parameter
+0~99
+Generic
+Assembles up to 100
+list
+Output 
+Parameter
+List
+Generic List
+The assembled list
+Query Nodes
+Execution Nodes
+Node Introduction
+Client Nodes
+Operation Nodes
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhfua005zpeg.txt

@@ -0,0 +1,96 @@
+/
+/
+Main Camera
+Camera is the tool that renders the Player's perspective in the game. It defines what 
+the Player sees on screen.
+In Beyond Mode, it supports creators (Craftspeople) to define camera rules through the 
+creation of camera templates. Each Template represents a distinct Camera State.
+I. Definition of Camera Templates
+Camera Templates available to Players during gameplay must be edited in Manage 
+Main Camera. The entry point is shown below:
+At runtime, each Player always has one active Camera Template.
+Active Templates can differ between Players. For example, in Co-Op Mode, Player A 
+might use "Template 1" while Player B uses "Template 2" at the same time.
+You can switch a specific Player Entity's active Camera Template at runtime through the 
+Node Graph, but Template parameters themselves cannot be modified dynamically.
+II. Editing Camera Templates
+Opening the main Camera editor displays the following Interface, divided into three 
+sections:
+III. Camera Template Parameter Configuration
+1. Template Name
+Template Name: The name of this Camera Template. It indicates the Template's role in 
+gameplay and is also used as a reference when Node Graphs operate on a Player's 
+main Camera Template
+2. Location Information
+Relative location between Camera and Character. These are editing parameters, 
+collapsed by default. They display detailed values of the Camera-Character relationship 
+in the current preview Interface, serving as a reference during editing
+3. Basic Camera Configuration
+Movement Mode: The current version only supports camera following character entities. 
+Future updates will expand support to include other Entity Units such as vehicles, etc.
+Mode: A key parameter that defines the Camera Template type. The mode determines 
+the core Camera rules, and the adjustable parameters vary depending on the mode
+Default Effective Target: The Camera Template is stored as a Player parameter. It can 
+be modified at runtime for the corresponding Player. During initialization, however, it 
+must be assigned through the Player's Class. This field specifies which Classes the 
+Template initially applies to
+4. Camera Detailed Settings
+Available adjustable parameters differ depending on the selected mode
+(1) Classic Camera
+The Classic Camera matches the Classic Mode. Parameters are grayed out. It supports 
+preview only and cannot be edited, so it is not described further
+(2) 3D Back Camera
+The 3D Back Camera is an over-the-shoulder view. The Camera is positioned behind 
+and to the right of the Character, as shown below:
+The detailed settings are shown in the graph below:
+d
+Camera FOV Detection: Field of view (FOV), represented by the viewing cone. 
+Changing the FOV adjusts the range of the white cone shown in the graph
+Viewpoint Offset: An additional Location offset applied in the World Coordinate System 
+after the Camera points to the target. The red box in the graph shows the viewpoint
+Viewpoint Follows Rotation: Whether the Camera rotates along with Character rotation
+Default Line of Sight: Initial distance between the Camera and the viewpoint
+Line of Sight Range: The adjustable range of Line of Sight that can be modified through 
+player input
+Horizontal Angle Range: The left-right rotation range, in degrees, that Players can 
+adjust by moving the Camera horizontally
+Pitch Angle Range: The up-down rotation range, in degrees, that Players can adjust by 
+moving the Camera vertically.
+(3) 2.5D Camera
+The camera for traditional 2.5D games, as shown in the following reference:
+The detailed settings are shown in the graph below:
+Ignore Camera Collision: When set to "No", the Camera may be pushed by collisions 
+with Entities in the Scene, causing stutter or sudden shifts. When set to "Yes", the 
+Camera ignores collisions, but its position may move inside models, leading to poor 
+results. This setting should be customized by creators (Craftspeople) based on the 
+actual gameplay scene
+Other attributes: Already explained earlier and not repeated here
+(4) First-Person Camera
+The Camera is positioned at the Character's eye level, simulating a first-person 
+perspective view of the scene, as shown below:
+The detailed settings are shown in the graph below:
+(5) Third Person Camera
+Similar to the Classic Mode, but with editable detailed settings available to the user:
+The detailed settings are shown in the graph below:
+IV. Camera Templates Switching
+You can use Node Graphs to dynamically switch Camera Templates at runtime. The 
+Target Units are a list of Player Entities.
+UI Control Groups Management
+Peripheral System
+Concept Introduction
+Advanced Concepts
+Main Camera
+1. Preview and configure parameters of the current Camera Template.
+2. Preview of camera position and character position relationship in the scene
+3. Preview of actual in-game screen during gameplay
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.

data/act_hoyoverse_com_ys_ugc_tutorial_detail_mhfvn30ctm9c.txt

@@ -0,0 +1,71 @@
+/
+/
+Preset Points
+I. What is a Preset Point?
+A Preset Point is a data record of location and orientation within a Scene.
+Preset Points can be referenced by features that require points data, such as Spawn 
+Points, Revive Points, and Node Graph retrieval points.
+II. Editing Preset Points
+1. Entry Point for Editing
+2. Overall Editing Interface
+(1) Preset Point Library
+All Preset Points are listed in this window.
+Manage the visibility of the corresponding Preset Point in the Layout Scene
+(2) Preset Point Visibility in the Edit Window
+Persistent Display Toggle On Even if the Preset Point management tool is 
+disabled, all Preset Points remain visible in the Edit Window
+Persistent Display Toggle Off  If the Preset Point management tool is disabled, all 
+Preset Points become invisible
+(3) Create Preset Point
+By clicking "Create Preset Point", a new Preset Point is generated at the center of 
+the current Edit Window, with naming editing mode enabled automatically.
+(4) Preset Point Parameters
+Preset Point Name  The name of the Preset Point, which can be modified
+Preset Point Index Used as an input parameter for Nodes and serves as the 
+unique identifier of the Preset Point
+Configuration Parameters
+Description
+Lock Transform
+When checked, the Preset Point's position and rotation can
+Display in Scene
+When unchecked, only the coordinate axes remain visible, 
+Point model will be hidden
+Location 
+The Location data of the Preset Point
+Rotation
+The orientation data of the Preset Point
+Unit Tags
+Add units tags to preset points. See Unit Tag  for more de
+* Reference Relationship
+III. Referencing Preset Points
+1. Spawn Point
+In "Stage Settings" — Spawn Point configuration, you can Select Point to reference a 
+Preset Point as the Spawn Point
+2. Revive Points
+In "Stage Settings" — Revive Point configuration, you can Select Point to reference a 
+Preset Point as the Revive Point
+3. Node Graph
+Through the Preset Point Index, you can search for its location and rotation data
+Click 
+to expand all Preset Point enumerations for selection as input 
+parameters
+Unit Status
+Shield
+Concept Introduction
+Advanced Concepts
+Preset Points
+Query Preset Point Position Rotation
+
+Get Preset Point List by Unit Tag
+
+Home
+News
+About Us
+Careers
+Business Affairs
+Privacy Policy
+Terms of Service
+Help Center
+General Guide
+Tutorial
+Copyright © COGNOSPHERE. All Rights Reserved.