NOVASMC

Once Human Mobile

Open-world survival shooter · PC / Mobile (iOS / Android)

Read this game through the selected section of its nine-part knowledge record.

CATALOG CONTENTS
178
CLASSIFICATION GROUPS
29
TRANSITIONS
0
RULES & PROCESS CONTENTS
29
PLAYER EXPERIENCE ELEMENTS
54

시스템 점검 기록

RECORDS
140
VISIBLE
140
PAGE
3 / 3

101–140OF 140 MATCHING RECORDS

RECORDRELATIONSTATE / SCOPEATTRIBUTES
0101Diagnosis & Direction 101Wish Machine; Starchrom; Wish Stones; legacy prize pools——
3 FIELDS
ENTRY TYPE
Recommendation
CONS BOTTLENECK RISK
Do not delete historical pool names or reinterpret old costs as current.
RECOMMENDATION IMPROVEMENT DIRECTION
Current-state deprecation map — Expose a dated `legacy → current` map so old 500/5,000-Starchrom draw information cannot be mistaken for baseline rules.
0102Diagnosis & Direction 102Lightforge Loot Crate; Combo Crate; Wish Wheel; Stardust Secret Crate——
3 FIELDS
ENTRY TYPE
Recommendation
CONS BOTTLENECK RISK
Keep 20-draw and 30-draw guarantee classes separate; do not average or merge them.
RECOMMENDATION IMPROVEMENT DIRECTION
Unified guarantee disclosure — Use one field grammar for threshold, early-hit behavior, reset, carryover, pool removal, and duplicate handling.
0103Diagnosis & Direction 103Frostshade and all living Lightforge tables——
3 FIELDS
ENTRY TYPE
Recommendation
CONS BOTTLENECK RISK
No silent numerical correction; source occurrence remains auditable.
RECOMMENDATION IMPROVEMENT DIRECTION
Probability-table label QA — Correct presentation-layer ordinal/color-label inconsistencies while retaining the original disclosed values and a revision log.
0104Diagnosis & Direction 104Summer Wave; Eldritch Diadem; Letter From Ocean; all active Combo Crates——
3 FIELDS
ENTRY TYPE
Recommendation
CONS BOTTLENECK RISK
Do not infer end dates from customary four-week cadence unless the notice states it.
RECOMMENDATION IMPROVEMENT DIRECTION
Lifecycle registry — Publish explicit start, end, timezone, region, and replacement status for every occurrence.
0105Diagnosis & Direction 105Crystgin; Lightforge Ingot; Lightforge Gem; Lightforge Relic; Surprise Points; Draw Tickets——
2 FIELDS
ENTRY TYPE
Recommendation
RECOMMENDATION IMPROVEMENT DIRECTION
Currency and token dictionary — Place official names, icons/IDs, input/output role, and conversion/guarantee scope in one cross-system glossary.
0106Diagnosis & Direction 106Official effective dates and legacy labels remain visible.——
2 FIELDS
ENTRY TYPE
Expected Outcome
RECOMMENDATION IMPROVEMENT DIRECTION
Current-state deprecation map
0107Diagnosis & Direction 107All counter states, early-hit resets and carryover rules are published.——
2 FIELDS
ENTRY TYPE
Expected Outcome
RECOMMENDATION IMPROVEMENT DIRECTION
Unified guarantee disclosure
0108Diagnosis & Direction 108Revision history preserves source-specific wording and values.——
2 FIELDS
ENTRY TYPE
Expected Outcome
RECOMMENDATION IMPROVEMENT DIRECTION
Probability-table label QA
0109Diagnosis & Direction 109Start/end/timezone/region data are available.——
2 FIELDS
ENTRY TYPE
Expected Outcome
RECOMMENDATION IMPROVEMENT DIRECTION
Lifecycle registry
0110Diagnosis & Direction 110Official UI name or item ID is available for each token.——
2 FIELDS
ENTRY TYPE
Expected Outcome
RECOMMENDATION IMPROVEMENT DIRECTION
Currency and token dictionary
0111Diagnosis & Direction 111The shop exposes several explicit anchors: an external recharge bonus, a fixed-price membership, a permanent low-price selection pack, paid pass editions, and discount-framed limited packs. Users encounter cash price, premium-currency price, percentage discount, and bonus-currency frames across different surfaces rather than one canonical comparison view.——
3 FIELDS
ENTRY TYPE
시스템 점검 기록
PROS STRUCTURAL STRENGTH
broad anchor portfolio.
CONS BOTTLENECK RISK
cross-surface value comparison requires manual reconstruction because regional prices and full tier tables are not public.
0112Diagnosis & Direction 112The baseline combines active, Summer Wave, July 29 arrivals and four-week Combo Crates with a recurring Thursday–Sunday bazaar, while anniversary rebate and several July packs have already ended. Scarcity is generated through season deadlines, limited return windows, rotating inventory, account limits and occurrence-specific discounts.——
3 FIELDS
ENTRY TYPE
시스템 점검 기록
PROS STRUCTURAL STRENGTH
multiple cadence types.
CONS BOTTLENECK RISK
missing exact end dates for several offers can convert legitimate scarcity into ambiguous urgency.
0113Diagnosis & Direction 113A plausible ladder exists from the permanent selection pack to passes/subscription, limited cosmetic packs, Lightforge input packs and multi-tier recharge products. The surfaces differ by commitment, cadence and reward class, but no public unified ladder shows all regional cash prices, Crystgin equivalents and account limits.——
3 FIELDS
ENTRY TYPE
시스템 점검 기록
PROS STRUCTURAL STRENGTH
entry, recurring and high-intent products are all present.
CONS BOTTLENECK RISK
ladder coherence and unit-value progression cannot be audited from public data alone.
0114Diagnosis & Direction 114Shop systems connect cash recharge to Crystgin, event rebates to T-Crystgin, duplicate recovery to Lightforge Relic, and progression currencies to Tech and Starwish exchanges. The 2026 blueprint transition removes the legacy Starchrom shop classification. Different currencies and exchange shops create targeted sinks while preserving the official cash-power separation, but alias, lifecycle and inventory control is distributed across many surfaces.——
3 FIELDS
ENTRY TYPE
시스템 점검 기록
PROS STRUCTURAL STRENGTH
specialized sinks and non-cash progression paths.
CONS BOTTLENECK RISK
orphan currencies, stale shop labels and expired offer balances if versioning is not unified.
0115Diagnosis & Direction 115All limited packs, Combo companion shops, Wish Bazaar and pass returns——
3 FIELDS
ENTRY TYPE
Recommendation
CONS BOTTLENECK RISK
Do not infer end dates from usual cadence when the official notice does not state one.
RECOMMENDATION IMPROVEMENT DIRECTION
Commerce occurrence registry — Maintain one occurrence record with exact name, start/end/timezone, region, shop path, direct-purchase status and replacement/return relation.
0116Diagnosis & Direction 116Top-up Center; Meta Pass; Selection Gift Pack; Battle Pass editions; Lightforge packs——
2 FIELDS
ENTRY TYPE
Recommendation
CONS BOTTLENECK RISK
Keep regional and platform variants separate; do not convert dynamic prices into a single global value.
0117Diagnosis & Direction 117Meta Pass; Starshine Coffer; Stardust Secret Crate——
3 FIELDS
ENTRY TYPE
Recommendation
CONS BOTTLENECK RISK
Do not describe the former Starshine Coffer benefit as current.
RECOMMENDATION IMPROVEMENT DIRECTION
Subscription benefit versioning — Expose effective dates and replacement history for daily, weekly and monthly entitlements.
0118Diagnosis & Direction 118Crystgin; T-Crystgin; Starwish Token; Silver Key; Lightforge Ingot; Lightforge Relic——
3 FIELDS
ENTRY TYPE
Recommendation
CONS BOTTLENECK RISK
Do not merge Crystgin with Lightforge Gem or resolve Silver Key localization without official item-level evidence.
RECOMMENDATION IMPROVEMENT DIRECTION
Currency and alias operating reference — Bind official English/Korean names, item IDs, source/sink role, expiration and applicable shop occurrence.
0119Diagnosis & Direction 119Wish Machine; Blueprint Shop; Starchrom——
2 FIELDS
ENTRY TYPE
Recommendation
CONS BOTTLENECK RISK
Preserve historical claims for lineage but block them from current implementation.
0120Diagnosis & Direction 120Permanent selection pack; passes; subscription; limited packs; recharge tiers——
3 FIELDS
ENTRY TYPE
Recommendation
CONS BOTTLENECK RISK
No recommendation badge or unit-value claim without complete regional prices and components.
RECOMMENDATION IMPROVEMENT DIRECTION
Value-ladder audit surface — Compare commitment, recurring cadence, direct value components and eligibility without introducing an inferred ranking.
0121Diagnosis & Direction 121Official end/timezone/region fields are maintained per occurrence.——
2 FIELDS
ENTRY TYPE
Expected Outcome
RECOMMENDATION IMPROVEMENT DIRECTION
Commerce occurrence registry
0122Diagnosis & Direction 122Regional price, tax, platform and account-limit data are available.——
1 FIELDS
ENTRY TYPE
Expected Outcome
0123Diagnosis & Direction 123Replacement dates and unclaimed-reward transition rules remain visible.——
2 FIELDS
ENTRY TYPE
Expected Outcome
RECOMMENDATION IMPROVEMENT DIRECTION
Subscription benefit versioning
0124Diagnosis & Direction 124Official localized labels, item IDs and expiration rules are confirmed.——
2 FIELDS
ENTRY TYPE
Expected Outcome
RECOMMENDATION IMPROVEMENT DIRECTION
Currency and alias operating reference
0125Diagnosis & Direction 125Downstream documents apply the 2026 effective dates.——
2 FIELDS
ENTRY TYPE
Expected Outcome
RECOMMENDATION IMPROVEMENT DIRECTION
Legacy boundary map
0126Diagnosis & Direction 126Complete regional prices and components are available.——
2 FIELDS
ENTRY TYPE
Expected Outcome
RECOMMENDATION IMPROVEMENT DIRECTION
Value-ladder audit surface
0127Diagnosis & Direction 127기준일 활성 포트폴리오는 시즌·패스·일/주간 기회·계정 트리거형 복귀 구조를 결합한다. Gravity Abyss가 장기 시즌 프레임을, Battle Pass 이 지속 진행을, Challenge Gifts와 복귀 이벤트가 제한된 행동 트리거를 제공한다. 클라이언트 수준 반복 체감은 별도 관찰하지 않았다.——
2 FIELDS
ENTRY TYPE
시스템 점검 기록
CONS BOTTLENECK RISK
기회: 복수 주기 레이어. 리스크: 서버·계정 표면마다 리셋과 자격 해석이 분산된다.
0128Diagnosis & Direction 128협동 구조가 서버, Custom Server, 전 서버 기여, 콜라보 모듈 수준에 존재한다. Aerial Hunt, Challenge Gifts, Wish Tree, Palworld 소셜 활동은 집단 참여 또는 공동 진행도를 사용한다. 다만 기여도 가중치와 전체 보상 배분은 일관되게 공개되지 않았다.——
2 FIELDS
ENTRY TYPE
시스템 점검 기록
CONS BOTTLENECK RISK
기회: 폭넓은 사회적 활성화. 리스크: 기여 귀속과 서버별 접근성이 불명확하다.
0129Diagnosis & Direction 129——
2 FIELDS
ENTRY TYPE
시스템 점검 기록
CONS BOTTLENECK RISK
기회: 영구 전투력을 재정의하지 않는 강한 시간 피크. 리스크: 종료일 중첩과 유예 기간 공시 부족.
0130Diagnosis & Direction 130동일 기준일 창에 Active, Ended, Conditional, Scheduled가 공존해 높은 업데이트 처리량과 엄격한 라이프사이클 거버넌스 필요성을 동시에 보여준다. Version 3.0.2는 현행 이벤트를 공급했고, 주년 이벤트는 직전에 종료됐으며, Version 3.0.3은 기준일 이후로 이미 공지됐다. 시나리오별 가용성과 계정 트리거형 이벤트가 비달력 라이프사이클을 추가한다.——
2 FIELDS
ENTRY TYPE
시스템 점검 기록
CONS BOTTLENECK RISK
기회: 지속적인 복귀 이유. 리스크: 이벤트·시나리오·상점·가챠 소유권 사이의 상태 오분류와 handoff 오류.
0131Diagnosis & Direction 131Gravity Abyss; Battle Pass Challenge Gifts; Summer Wave; Block Adventure——
3 FIELDS
ENTRY TYPE
Recommendation
CONS BOTTLENECK RISK
기준일 이후 공지를 현행 구현으로 승격하지 않는다. 계정 트리거형과 달력 트리거형 이벤트를 병합하지 않는다.
RECOMMENDATION IMPROVEMENT DIRECTION
통합 이벤트 라이프사이클 원장 — 각 이벤트 실행을 출처와 연결된 1행으로 유지하고 Open, Live, Closing, 수령 유예, Post-event 상태와 시간대·서버 적용 범위를 함께 기록한다.
0132Diagnosis & Direction 132Battle Pass Stardust Secret Crate Summer Wave; Starwish Shop——
1 FIELDS
ENTRY TYPE
Recommendation
0133Diagnosis & Direction 133Battle Pass Challenge Gifts; Returnee 2.0; Monthly Challenge——
3 FIELDS
ENTRY TYPE
Recommendation
CONS BOTTLENECK RISK
누락된 리셋 시각을 추론하거나 한 이벤트 규칙을 다른 이벤트에 적용하지 않는다.
RECOMMENDATION IMPROVEMENT DIRECTION
주기·리셋 공시 문법 통일 — 일일, 주간, 30일, 계정 트리거, 버전 전환 리셋을 공통 문법으로 제시한다.
0134Diagnosis & Direction 134Aerial Hunt; Wish Tree; Challenge Gifts; Palworld 소셜 모듈——
3 FIELDS
ENTRY TYPE
Recommendation
CONS BOTTLENECK RISK
기여 공식, 랭크 cutoff, 미공개 보상 수량을 생성하지 않는다.
RECOMMENDATION IMPROVEMENT DIRECTION
기여·보상 감사 추적 — 이벤트 실행 단위에서 Actor Action, 기여 단위, 즉시 System Response, 보상 수령을 연결한다.
0135Diagnosis & Direction 135Dawn Stars / Dawnbreak Stars; Stardust Resonant Filter; Permanent Scenario Servers——
3 FIELDS
ENTRY TYPE
Recommendation
CONS BOTTLENECK RISK
날짜가 특정된 근거 없이 과거 alias를 현행 구현 주장으로 바꾸지 않는다.
RECOMMENDATION IMPROVEMENT DIRECTION
과거 alias 거버넌스 — 현행명, 과거명, 소유 system을 출처 문구를 조용히 정규화하지 않고 함께 저장한다.
0136Diagnosis & Direction 136공식 시각, 시간대, 서버 적용 범위를 실행별로 유지해야 한다.——
2 FIELDS
ENTRY TYPE
Expected Outcome
RECOMMENDATION IMPROVEMENT DIRECTION
통합 이벤트 라이프사이클 원장
0137Diagnosis & Direction 137모든 연결 객체가 소유 system과 Source Locator를 보존해야 한다.——
2 FIELDS
ENTRY TYPE
Expected Outcome
RECOMMENDATION IMPROVEMENT DIRECTION
교차 시스템 소유권 라벨
0138Diagnosis & Direction 138누락 주기를 유사 사례로 채우지 않아야 한다.——
2 FIELDS
ENTRY TYPE
Expected Outcome
RECOMMENDATION IMPROVEMENT DIRECTION
주기·리셋 공시 문법 통일
0139Diagnosis & Direction 139출처가 직접 밝힌 Action/Response와 수령 조건이 필요하다.——
2 FIELDS
ENTRY TYPE
Expected Outcome
RECOMMENDATION IMPROVEMENT DIRECTION
기여·보상 감사 추적
0140Diagnosis & Direction 140날짜 범위 alias와 출처별 문구를 함께 저장해야 한다.——
2 FIELDS
ENTRY TYPE
Expected Outcome
RECOMMENDATION IMPROVEMENT DIRECTION
과거 alias 거버넌스