BLEACH: Soul Resonance

3D Anime Action RPG / Next-Gen Action RPG — storefront and locale dependent · iOS; iPadOS; Android; Windows availability shown on Google Play surface

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

CATALOG CONTENTS: 338
CLASSIFICATION GROUPS: 28
TRANSITIONS: 25
RULES & PROCESS CONTENTS: 1
PLAYER EXPERIENCE ELEMENTS: —

시스템 점검 기록

RECORDS: 92
VISIBLE: 92
PAGE: 2 / 2

51–92OF 92 MATCHING RECORDS

RECORD	RELATION	STATE / SCOPE	ATTRIBUTES
0051Character LevelingImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION canonical 성장 곡선과 상한 공개 공식 가이드에 누적 EXP/비용표·레벨 상한·해금 조건·버전별 변경사항을 공개한다. 추론 곡선이나 평균값으로 대체하지 말고 지역·버전 범위를 보존한다.
0052StampsImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	1 FIELDS ENTRY TYPE Improvement / Expected Outcome
0053AscensionImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION 투자 회복 안전장치 추가 또는 문서화 초기화·환불·분해 반환·이전/계승·하락 보호 정책을 명확히 한다. 공식 규칙이 공개되기 전 안전장치 존재를 암시하지 말고 중단·되돌림 한계를 정의한다.
0054Character LevelingImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	1 FIELDS ENTRY TYPE Improvement / Expected Outcome
0055Weapon StampsImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	3 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION 공식 현지화와 버전별 Catalog 표준화 게임 고유 한국어/영문명과 버전별 아이템 Catalog·Alias/Rename 이력을 공개한다. Rentless Barrage 또는 Patrol 명칭 변형 같은 출처 문자열을 조용히 정규화하지 않는다. EXPECTED OUTCOME 명칭 충돌과 낡은 빌드 조언을 줄일 수 있다. /과 고객용 보고서가 하나의 게임 고유 명명 권위를 재사용할 수 있다. 공식 한국어/영문 Catalog와 Rename 이력이 유지된다.
0056Spiritual Jade (Jade)explicit diagnosis only; no new diagnosis created	—	—	2 FIELDS ENTRY TYPE 시스템 점검 기록 CONS BOTTLENECK RISK 명명된 Faucet과 Sink는 다층으로 존재하지만 재화별 전체 발행량·소비량·보유상한·reset 표가 없다. Story·Event·Code·IAP가 여러 지갑으로 공급되고 Gacha·Growth·Entry·Shop·Crafting이 소비하나 quantitative closure가 불완전하다. 경제 과열·병목을 외부 공개 자료만으로 판정할 수 없다는 리스크 / named-source map 구축 기회
0057Spiritual Jade (Jade)explicit diagnosis only; no new diagnosis created	—	—	2 FIELDS ENTRY TYPE 시스템 점검 기록 CONS BOTTLENECK RISK Paid/Free premium currency와 지역 조건 IAP denomination은 확인되지만 conversion·paid-only eligibility·platform parity가 불투명하다. 동일한 premium value가 free progression과 platform purchase로 공급되며 일부 premium packs의 paid eligibility가 별도다. 가격 비교·지각가치 판단의 불확실성 / 지갑 분리 disclosure 개선 기회
0058Ticket Stubsexplicit diagnosis only; no new diagnosis created	—	—	2 FIELDS ENTRY TYPE 시스템 점검 기록 CONS BOTTLENECK RISK pull result와 max-Ascension duplicate에 salvage token을 부여하는 fallback economy가 존재한다. 획득 결과가 Ticket Stub 계열로 재전환되어 완전 무가치 결과를 완충하지만 exchange inventory와 공식 버전표가 불완전하다. 중복 가치 회수 기회 / 비공식 표 의존과 generic ticket naming risk
0059Treasure Redeemexplicit diagnosis only; no new diagnosis created	—	—	2 FIELDS ENTRY TYPE 시스템 점검 기록 CONS BOTTLENECK RISK IAP·monthly ticket·gift code·event supply가 병존하지만 code lifecycle·currency glossary·지역 가격 scope가 source별로 엇갈린다. LiveOps Faucet이 빈번하게 경제에 개입하는 반면 유효성·만료·명명·지역 적용의 단일 disclosure surface가 확인되지 않았다. 단기 참여 자극 / 운영 신뢰·고객지원 비용 리스크
0060Spiritual Jade (Jade)Improvement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION 통화·자원 canonical glossary current·paid/free·historical·regional alias를 한 표에서 분리하고 동일성·비동일성을 명시한다. historical denomination을 current wallet으로 자동 병합하지 않는다.
0061Spiritual Jade (Jade)Improvement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	1 FIELDS ENTRY TYPE Improvement / Expected Outcome
0062Ticket StubsImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION 중복 전환 표의 in-client 정본화 pull result와 max-Ascension 상태별 conversion table 및 exchange use를 공식 UI/Help에 고정한다. 확률·천장과 exchange value를 혼합 표기로 오해시키지 않는다.
0063Treasure RedeemImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION Gift Code lifecycle governance 발행 주체, 적용 지역, 시작·종료 시각, status, reward string, mailbox delivery를 하나의 official archive로 관리한다. expired/unknown code를 Active로 자동 승격하지 않는다.
0064Premium Spiritual JadeImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION 지역·플랫폼 price/transfer disclosure storefront별 denomination·가격·paid-only use·refund·account transfer를 명시한다. 한 지역 iOS 가격을 글로벌 또는 Android 가격으로 일반화하지 않는다.
0065Limited Character Gachaexplicit diagnosis only; no new diagnosis created	—	—	3 FIELDS ENTRY TYPE 시스템 점검 기록 PROS STRUCTURAL STRENGTH predictable target pursuit. Risk: overlapping limited pools can compress decision time. CONS BOTTLENECK RISK Targeted limited pools create a clear expectation–attempt–guarantee cycle. Featured character/Stamp instances combine limited windows with 10/40/80 thresholds, reducing endless failure while sustaining repeated attempts. Opportunity: predictable target pursuit. Risk: overlapping limited pools can compress decision time.
0066Permanent Character Gachaexplicit diagnosis only; no new diagnosis created	—	—	3 FIELDS ENTRY TYPE 시스템 점검 기록 PROS STRUCTURAL STRENGTH official table CONS BOTTLENECK RISK High-level guarantee communication is strong, but detailed probability authority is incomplete. Official store copy exposes the 80-draw message, while full rate cells were recovered only from a fan-made guide and not an official legal notice. Risk: disputes over version, region, and displayed rate basis. Opportunity: official table/version registry can close the gap.
0067Limited Character Gachaexplicit diagnosis only; no new diagnosis created	—	—	2 FIELDS ENTRY TYPE 시스템 점검 기록 CONS BOTTLENECK RISK Character pity, featured-target rules, shared carryover, Starter Rewards, and duplicate conversion form a multi-layer safety net. Failure caps protect acquisition; carryover preserves attempts; stubs and Boundary Ascension retain value after non-target or duplicate outcomes. Risk: Limited Stamp post-first cycle and early-termination wording are not fully source-aligned.
0068Limited Stamp Gachaexplicit diagnosis only; no new diagnosis created	—	—	3 FIELDS ENTRY TYPE 시스템 점검 기록 PROS STRUCTURAL STRENGTH every pull can be represented as immediate acquisition plus persistent account value. Risk: exchange naming CONS BOTTLENECK RISK The gacha is connected to a four-ticket input structure and two post-pull accumulation resources. Jade and stubs convert into tickets, while duplicate outcomes feed Boundary Ascension or Advanced Ticket Stubs. Opportunity: every pull can be represented as immediate acquisition plus persistent account value. Risk: exchange naming/localization may obscure value.
0069Permanent Character GachaImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION Official probability disclosure registry Expose an official, versioned, region-scoped probability table from every pool’s main screen and preserve historical versions. Do not reframe low rates with unsupported cumulative claims; show base and guarantee-included bases separately.
0070Limited Stamp GachaImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION Visible pity-state contract Display current count, destination pool, carryover scope, and exact reset trigger before and after every pull. No hidden counter reset; any reset must require a source-stated trigger and post-action receipt.
0071Limited Stamp GachaImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION Stamp guarantee-cycle clarification Publish whether 40 pulls applies to every target cycle or only the first SSR, with a versioned example. Preserve source variants until official rules resolve them; do not average 40 and 80.
0072Permanent Character GachaImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION Canonical naming and localization matrix Use one preferred object name per language and expose aliases/old names in support documentation. Do not merge generic “상시/한정/스탬프 배너” labels into one object when multiple pools exist.
0073Permanent Character GachaImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION Duplicate-value preview Show the exact conversion result before confirmation and in the pull receipt, including max-ascension exceptions. No undisclosed conversion quantity; preserve the original item, output resource, and condition in logs.
0074Total Ruin Limited-Time GachaImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION Exact event-end contract Replace “end of Special Edition” with an exact timestamp, timezone, region, and maintenance dependency. Do not infer an end date by duration arithmetic; later schedule changes must retain superseded notices.
0075App Store In-App Purchasesexplicit diagnosis only; no new diagnosis created	—	—	3 FIELDS ENTRY TYPE 시스템 점검 기록 PROS STRUCTURAL STRENGTH preserve a clear entry-to-premium ladder. Risk: users cannot independently audit value per unit or cross-region parity. CONS BOTTLENECK RISK A visible multi-tier price architecture exists, but product-component and unit-value comparability is incomplete. Official storefronts expose named products and prices while most contents, quantities, discount bases, and tax treatment are absent. Opportunity: preserve a clear entry-to-premium ladder. Risk: users cannot independently audit value per unit or cross-region parity.
0076Beginner Value Packsexplicit diagnosis only; no new diagnosis created	—	—	3 FIELDS ENTRY TYPE 시스템 점검 기록 PROS STRUCTURAL STRENGTH event-aligned conversion. Risk: ambiguous scarcity can create trust and CS burden. CONS BOTTLENECK RISK Scarcity signaling is present through Limited, Check-in, and Target product naming, but operational scarcity rules are under-disclosed. The catalog signals urgency or targeting without disclosing exact sale period, cap, reset, or restock rule. Opportunity: event-aligned conversion. Risk: ambiguous scarcity can create trust and CS burden.
0077App Store In-App Purchasesexplicit diagnosis only; no new diagnosis created	—	—	3 FIELDS ENTRY TYPE 시스템 점검 기록 PROS STRUCTURAL STRENGTH segment-specific conversion. Risk: inconsistent names CONS BOTTLENECK RISK The shop surface spans entry, mid-tier, pass, and premium denominations, but the ladder is fragmented by region and provider. Myanmar, US, and Pakistan storefronts expose different product mixes; beginner and monthly offers provide low-friction entry paths. Opportunity: segment-specific conversion. Risk: inconsistent names/catalogs weaken global value communication.
0078Recharge Centerexplicit diagnosis only; no new diagnosis created	—	—	1 FIELDS ENTRY TYPE 시스템 점검 기록
0079App Store In-App PurchasesImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION Publish a region-versioned shop disclosure matrix For every region/platform, expose product name, provider, effective date, contents, price, tax handling, sale period, cap, and reset. Do not represent post-baseline or another-region values as globally current.
0080Premium Spiritual Jade ×6,480Improvement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION Standardize product-value cards Show exact component quantities, paid/free currency restrictions, eligible banner/content, and unit-value comparison. Avoid unverifiable “best value” or discount claims without a disclosed calculation base.
0081Monthly Card / Monthly Card MembershipImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION Complete pass terms Disclose term, daily grant, claim method, stacking, auto-renewal, billing, cancellation, refund, and missed-day handling. Do not infer subscription behavior from the word Monthly alone.
0082Premium Spiritual Jade ×6,480Improvement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION Separate currency identity and route labels Display paid/free distinction, regional localization, allowed purchases, and ticket conversion rules in one traceable glossary. Do not merge similarly named currencies without direct implementation evidence.
0083Beginner Value PacksImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	1 FIELDS ENTRY TYPE Improvement / Expected Outcome
0084New SSR Bambietta Arrivesexplicit diagnosis only; no new diagnosis created	—	—	3 FIELDS ENTRY TYPE 시스템 점검 기록 PROS STRUCTURAL STRENGTH regular return rhythm. Risk: opaque reset CONS BOTTLENECK RISK The baseline portfolio contains multiple low-friction daily or repeat triggers, but reset and missed-day rules are incomplete. Daily login, double-drop attempts, daily challenge stages, and quest-to-ticket mechanics create repeated return points. Opportunity: regular return rhythm. Risk: opaque reset/claim rules can convert habit into avoidable loss.
0085World Boss Challengeexplicit diagnosis only; no new diagnosis created	—	—	3 FIELDS ENTRY TYPE 시스템 점검 기록 PROS STRUCTURAL STRENGTH collective identity and competition. Risk: current contribution fairness and reward distribution remain unverified. CONS BOTTLENECK RISK A server-wide and leaderboard pattern is verified historically, but a baseline-current social contribution contract is not. World Boss Challenge and server-wide extermination milestones convert individual play into shared or ranked outcomes. Opportunity: collective identity and competition. Risk: current contribution fairness and reward distribution remain unverified.
0086New SSR Bambietta Arrivesexplicit diagnosis only; no new diagnosis created	—	—	3 FIELDS ENTRY TYPE 시스템 점검 기록 PROS STRUCTURAL STRENGTH coherent update peak. Risk: schedule changes and missing exact end CONS BOTTLENECK RISK Limited event windows and a current limited SSR pool are tightly aligned around the Bambietta/TYBW update. A time-bounded themed event, daily-login rewards, and a limited character pool concentrate attention and resource use. Opportunity: coherent update peak. Risk: schedule changes and missing exact end/claim times can increase trust cost.
0087Snowball Assaultexplicit diagnosis only; no new diagnosis created	—	—	3 FIELDS ENTRY TYPE 시스템 점검 기록 PROS STRUCTURAL STRENGTH reduced content gaps. Risk: naming hierarchy, end timestamps, grace periods, and post-event conversion remain fragmented. CONS BOTTLENECK RISK The service operates a staggered multi-wave calendar across Aug-7, Aug-12, Aug-14, and Aug-21, but public closing/post-event governance is thin. Active, conditional, and scheduled event instances overlap to sustain continuity after the previous July portfolio. Opportunity: reduced content gaps. Risk: naming hierarchy, end timestamps, grace periods, and post-event conversion remain fragmented.
0088Total DevastationImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION Publish an event clock contract Expose start, end, time zone, reward-claim deadline, exchange grace, and unspent-asset handling in one text surface. Do not infer end timestamps from duration; preserve region/server differences.
0089Total DevastationImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION Unify parent–subevent naming Show the parent event, subevent role, unlock state, and cross-system link with stable names. Do not collapse independent entry points or replace official names with generic classes.
0090Hueco Mundo ShowdownImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION Make score and contribution rules directly auditable Publish score inputs, difficulty modifiers, rank cutoffs, reward tiers, and contribution attribution. Keep performance rules separate from paid power and preserve fairness review.
0091Snowball AssaultImprovement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION Consolidate the live calendar Provide a single calendar that distinguishes Active, Scheduled, Closing, and Ended states. Avoid urgency inflation; scheduled content must not appear implemented before its unlock.
0092TYBW: Quincy Invasion!Improvement Direction and Expected Outcome joined by exact Direction; no new recommendation or outcome generated	—	—	2 FIELDS ENTRY TYPE Improvement / Expected Outcome RECOMMENDATION IMPROVEMENT DIRECTION Preserve schedule-change lineage Keep original date, delay reason boundary, revised availability, and compensation cadence in one traceable notice chain. Never overwrite prior dates without supersession lineage or mix compensation with ordinary event rewards.