Question 1

What should be prepared before onboarding?

Accepted Answer

Prepare an account, a valid invite code, an API key, and a ready project environment for your target engine. The safest order is registration first, API key generation second, then follow prerequisites and integration docs step by step so environment issues do not get mixed with product issues.

Question 2

Should I start from docs or community?

Accepted Answer

Start with docs for standard onboarding, then use community for project specific issues. Docs are better for deterministic steps and rules. Community is better when you need help with edge cases, design constraints, or delivery decisions in a real project.

Question 3

Why is an invite code required to register?

Accepted Answer

The invite gate is intentional at the current stage to control rollout pace and make sure early users receive clearer onboarding support. This is expected behavior rather than a bug. The invite mechanism helps control access while the team keeps refining the product and delivery workflow. If you do not have a code yet, first ask an existing user or open the community to check the current access path.

Question 4

What happens after invite validation succeeds?

Accepted Answer

Next, request the email verification code, finish registration, and then open your dashboard to review the API key and next steps. Invite validation does not finish account creation on its own. You still need the email code and the remaining account fields. If the invite passes but you cannot continue, first check whether the email code arrived, whether it expired, or whether the browser environment blocked the request.

Question 5

Which design sources and engines are supported today?

Accepted Answer

Released today: Lanhu → Unity. Lanhu → Cocos, Figma → Unity, and Figma → Cocos is currently in Beta. Not every path has the same maturity. Use the roadmap and changelog as the source of truth for released, beta, and planned states instead of treating every visible platform as equally supported.

Question 6

What does Beta actually mean here?

Accepted Answer

Beta means the pipeline is available, but stability, coverage, or production readiness is still being hardened. Lanhu → Cocos, Figma → Unity, and Figma → Cocos is the current Beta path. The safer rollout pattern is to validate it in a contained real project before moving it into a broader production workflow.

Question 7

How should I choose a subscription plan?

Accepted Answer

Start from project frequency, device needs, and whether your workflow is already in recurring delivery. If you are only validating feasibility, begin with the free quota. If the workflow is already part of continuous delivery, use pricing to match team scale and device usage.

Question 8

When does access update after payment?

Accepted Answer

Entitlements should usually refresh immediately after a successful order. If payment succeeded but the plan did not update, first verify order state and then contact support so the team can inspect the sync path.

Question 9

What should I check first when output differs from the design?

Accepted Answer

Start with design source conventions, target engine constraints, and the maturity of the current pipeline. Many mismatches are caused by combined factors such as layer structure, design conventions, supported component boundaries, or engine side rendering differences rather than a single isolated defect.

Question 10

What information should I include when reporting an issue?

Accepted Answer

Include the design source, target engine, symptom, reproduction steps, and expected outcome at minimum. Screenshots, constraint details, and whether the issue reproduces consistently help the team decide faster whether the problem is usage related, a current capability boundary, or a real bug that needs to be scheduled.

Common Questions and Resolution Paths

Integration and Setup

Registration and Invite Codes

Capability Status and Delivery Scope

Billing and Entitlements

Common Troubleshooting

Still blocked?

After FAQ answers the objection, what is usually next?

Confirm the current support state

Review setup prerequisites

Review the Unity workflow next