[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article:gree-mobile-game-ops":3},{"meta":4,"markdown":67,"quiz":68},{"type":5,"articleId":6,"slug":7,"title":8,"titleEn":9,"category":10,"summary":11,"publishedAt":12,"image":13,"vocabulary":14,"quizId":66},"article","tech-gree-mobile-game-ops","gree-mobile-game-ops","GREEのモバイルゲーム運用 — リアルタイム対戦と決済の裏側","GREE's Mobile Game Operations: Real-time Battles and Payment Internals","tech","An overview of how GREE evolved from a 2004 social-network startup to a global mobile-game operator — covering the feature-phone-to-smartphone transition, WebSocket-based real-time battle infrastructure, double-charge prevention in in-app purchase, the legal obligation to disclose gacha probabilities, cheat detection, the retreat from and re-entry into overseas markets, and the recent expansion into blockchain games.\n","2026-04-28T00:00:00Z","https:\u002F\u002Fimages.yamiyomi.com\u002Ftech-gree-mobile-game-ops.png",[15,20,24,28,33,38,42,46,50,54,58,62],{"word":16,"reading":17,"meaning":18,"level":19},"創業","そうぎょう","founding (a company)","N2",{"word":21,"reading":22,"meaning":23,"level":19},"転換","てんかん","transition",{"word":25,"reading":26,"meaning":27,"level":19},"対戦","たいせん","match",{"word":29,"reading":30,"meaning":31,"level":32},"決済","けっさい","payment","N1",{"word":34,"reading":35,"meaning":36,"level":37},"二重","にじゅう","double","N3",{"word":39,"reading":40,"meaning":41,"level":19},"確率","かくりつ","probability",{"word":43,"reading":44,"meaning":45,"level":37},"表示","ひょうじ","display",{"word":47,"reading":48,"meaning":49,"level":19},"義務","ぎむ","obligation",{"word":51,"reading":52,"meaning":53,"level":19},"不正","ふせい","cheating",{"word":55,"reading":56,"meaning":57,"level":32},"撤退","てったい","withdrawal",{"word":59,"reading":60,"meaning":61,"level":19},"挑戦","ちょうせん","challenge",{"word":63,"reading":64,"meaning":65,"level":19},"基盤","きばん","platform","tech-gree-mobile-game-ops-quiz","\n::para\n[株式会社]{かぶしきがいしゃ:corporation:N1}グリー（GREE）は[2004年]{にせんよねん:2004:N5}に[創業]{そうぎょう:founded:N1}され、[当初]{とうしょ:initially:N3}はPC[向け]{むけ:for:N3}のソーシャル・ネットワーキング・サービスとして[出発]{しゅっぱつ:started:N4}しました。その[後]{ご:after:N5}、[携帯]{けいたい:mobile:N1}[電話]{でんわ:phone:N5}[向け]{むけ:for:N3}のゲームプラットフォームへと[軸足]{じくあし:pivot:N1}を[移し]{うつし:shifted:N2}、[現在]{げんざい:now:N3}ではモバイルゲーム[運営]{うんえい:operations:N2}を[中核]{ちゅうかく:core:N1}[事業]{じぎょう:business:N4}とする[企業]{きぎょう:company:N1}です。[本]{ほん:this:N5}[記事]{きじ:article:N3}では、[同社]{どうしゃ:the company:N4}の[技術]{ぎじゅつ:technical:N2}[基盤]{きばん:foundation:N1}と[運用]{うんよう:operational:N4}[体制]{たいせい:structure:N3}を[概観]{がいかん:overview:N1}します。\n\n#en\nGREE Inc. was founded in 2004, initially starting as a PC-oriented social networking service. It later pivoted to a mobile-phone game platform, and is today a company whose core business is operating mobile games. This article gives an overview of the company's technical foundation and operational structure.\n::\n\n::heading\nガラケー[時代]{じだい:era:N4}からスマートフォンへの[転換]{てんかん:transition:N2}\n\n#en\nTransition from the Feature-Phone Era to Smartphones\n::\n\n::para\n[2007年]{にせんななねん:2007:N5}[頃]{ごろ:around:N2}、[同社]{どうしゃ:the company:N4}はいわゆる「ガラケー」[向け]{むけ:for:N3}の[簡易]{かんい:simple:N2}HTMLゲームで[急成長]{きゅうせいちょう:rapid growth:N3}しました。しかし[2010年]{にせんじゅうねん:2010:N5}[以降]{いこう:and after:N3}、スマートフォンの[普及]{ふきゅう:spread:N1}に[伴い]{ともない:accompanying:N1}、[従来]{じゅうらい:legacy:N1}のキャリア[課金]{かきん:billing:N2}[依存]{いぞん:dependent:N2}モデルが[通用]{つうよう:work:N4}しなくなり、[全社]{ぜんしゃ:company-wide:N3}[規模]{きぼ:scale:N1}の[技術]{ぎじゅつ:technical:N2}[転換]{てんかん:transition:N2}を[迫られ]{せまられ:was forced:N1}ました。[既存]{きぞん:existing:N1}のFlash Lite[資産]{しさん:assets:N3}は[捨て]{すて:abandoned:N2}、HTML5・ネイティブアプリへ[全面]{ぜんめん:full-scale:N3}[移行]{いこう:migrate:N2}したのです。\n\n#en\nAround 2007, the company saw rapid growth via simple HTML games for so-called feature phones (\"garake\"). However, from 2010 onward, with the spread of smartphones, the legacy carrier-billing-dependent model stopped working, forcing a company-wide technical transition. Existing Flash Lite assets were abandoned in favor of a full migration to HTML5 and native apps.\n::\n\n::callout\n[要点]{ようてん:key point:N3}：プラットフォームの[転換]{てんかん:transition:N2}[期]{き:period:N3}は、[既存]{きぞん:existing:N1}[資産]{しさん:assets:N3}を[守る]{まもる:protect:N3}か[捨てる]{すてる:abandon:N2}かの[判断]{はんだん:judgment:N3}が[企業]{きぎょう:company:N1}の[命運]{めいうん:fate:N3}を[左右]{さゆう:determine:N5}します。\n\n#en\nKey point: During platform transitions, the judgment of whether to protect or abandon existing assets determines a company's fate.\n::\n\n::heading\nリアルタイム[対戦]{たいせん:battle:N3}[基盤]{きばん:platform:N1}（WebSocket）\n\n#en\nReal-Time Battle Platform (WebSocket)\n::\n\n::para\n[現在]{げんざい:current:N3}の[主力]{しゅりょく:flagship:N4}タイトルでは、プレイヤー[同士]{どうし:among each other:N1}が[同時]{どうじ:simultaneous:N4}に[操作]{そうさ:operation:N1}する[同期]{どうき:synchronous:N3}[対戦]{たいせん:battle:N3}が[標準]{ひょうじゅん:standard:N1}[機能]{きのう:feature:N3}となっています。HTTPポーリングでは[遅延]{ちえん:latency:N2}が[許容]{きょよう:acceptable:N3}[範囲]{はんい:range:N1}に[収まら]{おさまら:fit within:N3}ないため、WebSocketによる[常時]{じょうじ:permanent:N3}[接続]{せつぞく:connection:N2}[基盤]{きばん:platform:N1}が[採用]{さいよう:adopted:N2}されました。サーバー[側]{がわ:side:N3}はGoで[実装]{じっそう:implemented:N2}され、[一台]{いちだい:one server:N4}で[数万]{すうまん:tens of thousands:N3}[件]{けん:items:N3}の[同時]{どうじ:simultaneous:N4}[接続]{せつぞく:connection:N2}を[捌く]{さばく:handle:N1}[設計]{せっけい:design:N2}です。\n\n#en\nIn current flagship titles, synchronous battles where players operate simultaneously are a standard feature. HTTP polling cannot keep latency within an acceptable range, so a permanent-connection platform based on WebSocket was adopted. The server side is implemented in Go, designed so that a single machine handles tens of thousands of concurrent connections.\n::\n\n::para\n[対戦]{たいせん:battle:N3}[中]{ちゅう:during:N5}の[状態]{じょうたい:state:N1}[同期]{どうき:synchronization:N3}は、[権威]{けんい:authoritative:N1}サーバー[方式]{ほうしき:approach:N3}を[採用]{さいよう:adopt:N2}しています。クライアントから[送ら]{おくら:sent:N4}れる[操作]{そうさ:operation:N1}[入力]{にゅうりょく:input:N4}はサーバーで[検証]{けんしょう:validated:N1}され、[結果]{けっか:result:N1}のみが[全]{ぜん:all:N3}プレイヤーへ[配信]{はいしん:distributed:N3}されます。これによりクライアント[改竄]{かいざん:tampering:N1}による[不正]{ふせい:cheating:N4}を[根本的]{こんぽんてき:fundamentally:N2}に[防ぐ]{ふせぐ:prevent:N2}ことができます。\n\n#en\nState synchronization during battles uses an authoritative-server approach. Operation inputs sent from clients are validated on the server, and only the results are distributed to all players. This fundamentally prevents cheating via client-side tampering.\n::\n\n::heading\nアプリ[内]{ない:in-app:N3}[課金]{かきん:purchase:N2}と[二重]{にじゅう:double:N4}[決済]{けっさい:payment:N3}[防止]{ぼうし:prevention:N2}\n\n#en\nIn-App Purchase and Double-Charge Prevention\n::\n\n::para\nApp Store・Google Playを[経由]{けいゆ:via:N3}するアプリ[内]{ない:in-app:N3}[課金]{かきん:purchase:N2}は、[一見]{いっけん:at first glance:N5}[単純]{たんじゅん:simple:N2}に[見える]{みえる:appear:N5}ものの、ネットワーク[切断]{せつだん:disconnection:N3}や[端末]{たんまつ:device:N1}クラッシュなどで「[決済]{けっさい:payment:N3}は[完了]{かんりょう:completed:N2}したがアイテムが[配付]{はいふ:delivered:N3}されない」あるいは「[同じ]{おなじ:same:N4}[購入]{こうにゅう:purchase:N1}が[二度]{にど:twice:N4}[計上]{けいじょう:counted:N4}される」といった[障害]{しょうがい:incidents:N1}が[発生]{はっせい:occur:N4}しがちです。GREEでは[各]{かく:each:N2}[購入]{こうにゅう:purchase:N1}トランザクションに[一意]{いちい:unique:N4}のレシートIDを[紐付け]{ひもづけ:bind:N1}、サーバー[側]{がわ:side:N3}でべき[等]{とう:idempotent:N3}[処理]{しょり:processing:N3}を[徹底]{てってい:thoroughly enforce:N1}しています。\n\n#en\nIn-app purchases via the App Store and Google Play look simple at first glance, but incidents such as \"payment completed but item not delivered\" or \"the same purchase counted twice\" tend to occur due to network disconnections or device crashes. At GREE, each purchase transaction is bound to a unique receipt ID, and idempotent processing is thoroughly enforced on the server side.\n::\n\n::callout\n[注意]{ちゅうい:caution:N4}：[二重]{にじゅう:double:N4}[決済]{けっさい:payment:N3}は[返金]{へんきん:refund:N3}[対応]{たいおう:handling:N1}と[信頼]{しんらい:trust:N3}[失墜]{しっつい:loss:N1}に[直結]{ちょっけつ:directly leads:N1}するため、[障害]{しょうがい:fault:N1}が[起き]{おき:occur:N4}ても[結果]{けっか:result:N1}が[同じ]{おなじ:same:N4}になる「べき[等]{とう:idempotent:N3}[性]{せい:property:N3}」の[設計]{せっけい:design:N2}が[必須]{ひっす:essential:N1}です。\n\n#en\nCaution: Double charges directly lead to refund handling and loss of trust, so designing for idempotency — where the result is the same even if a failure occurs — is essential.\n::\n\n::heading\nガチャ[システム]{しすてむ:system}と[確率]{かくりつ:probability:N1}[表示]{ひょうじ:disclosure:N3}の[法的]{ほうてき:legal:N3}[義務]{ぎむ:obligation:N1}\n\n#en\nThe Gacha System and the Legal Obligation to Disclose Probabilities\n::\n\n::para\n[日本]{にほん:Japan:N5}のモバイルゲーム[業界]{ぎょうかい:industry:N4}では、ガチャと[呼ば]{よば:called:N3}れる[抽選]{ちゅうせん:lottery:N1}[型]{がた:type:N2}の[課金]{かきん:purchase:N2}[要素]{ようそ:element:N1}が[広く]{ひろく:widely:N4}[普及]{ふきゅう:spread:N1}しています。[2016年]{にせんじゅうろくねん:2016:N5}に[業界]{ぎょうかい:industry:N4}[団体]{だんたい:body:N2}JOGAが[自主]{じしゅ:voluntary:N4}[規制]{きせい:regulation:N3}として[確率]{かくりつ:probability:N1}[表示]{ひょうじ:disclosure:N3}を[義務]{ぎむ:obligation:N1}[化]{か:make:N3}し、[2022年]{にせんにじゅうにねん:2022:N5}の[消費者]{しょうひしゃ:consumer:N3}[庁]{ちょう:agency:N2}による[景品]{けいひん:premium:N3}[表示]{ひょうじ:labeling:N3}[法]{ほう:law:N3}[運用]{うんよう:operations:N4}[基準]{きじゅん:standards:N1}の[改訂]{かいてい:revision:N1}で[事実上]{じじつじょう:de facto:N3}[法的]{ほうてき:legal:N3}[義務]{ぎむ:obligation:N1}となりました。\n\n#en\nIn Japan's mobile game industry, a paid-lottery-style element called \"gacha\" is widely common. In 2016, the industry body JOGA made probability disclosure mandatory as voluntary self-regulation, and with the 2022 revision of the Consumer Affairs Agency's Premium Labeling Act operational standards, it became de facto a legal obligation.\n::\n\n::para\nGREEでは[各]{かく:each:N2}ガチャの[排出]{はいしゅつ:drop:N1}[率]{りつ:rate:N1}を[詳細]{しょうさい:detailed:N1}にゲーム[内]{ない:inside:N3}と[公式]{こうしき:official:N3}サイトで[公開]{こうかい:disclose:N4}しています。[内部]{ないぶ:internal:N3}[実装]{じっそう:implementation:N2}としては、[企画]{きかく:planning:N1}[担当]{たんとう:staff:N2}が[編集]{へんしゅう:edit:N2}する[排出]{はいしゅつ:drop:N1}テーブルが[必ず]{かならず:always:N3}[公開]{こうかい:public:N4}[表示]{ひょうじ:display:N3}と[一致]{いっち:match:N1}するよう、[自動]{じどう:automated:N4}[整合性]{せいごうせい:consistency:N1}テストが[毎]{まい:every:N5}デプロイで[実行]{じっこう:run:N3}されます。\n\n#en\nAt GREE, the drop rate of each gacha is disclosed in detail both in-game and on the official website. As internal implementation, automated consistency tests run on every deploy to ensure that the drop tables edited by planning staff always match the public display.\n::\n\n::heading\n[不正]{ふせい:cheating:N4}[対策]{たいさく:countermeasures:N1}とチート[検知]{けんち:detection:N1}\n\n#en\nAnti-Cheat Measures and Cheat Detection\n::\n\n::para\n[改造]{かいぞう:modified:N2}クライアントやメモリ[改竄]{かいざん:tampering:N1}ツールを[使用]{しよう:use:N4}するプレイヤーは[一定]{いってい:certain:N3}[割合]{わりあい:proportion:N3}[存在]{そんざい:exist:N3}します。GREEではサーバー[側]{がわ:side:N3}での[行動]{こうどう:behavior:N4}ログ[解析]{かいせき:analysis:N1}に[加え]{くわえ:in addition to:N3}、[端末]{たんまつ:device:N1}[側]{がわ:side:N3}の[改造]{かいぞう:modified:N2}OS[検出]{けんしゅつ:detection:N1}（[いわゆる]{いわゆる:so-called}root\u002Fjailbreak[判定]{はんてい:detection:N3}）、そして[機械]{きかい:machine:N2}[学習]{がくしゅう:learning:N4}による[行動]{こうどう:behavior:N4}パターン[分類]{ぶんるい:classification:N3}を[組み合わせ]{くみあわせ:combine:N3}て[多層]{たそう:multi-layered:N2}[防御]{ぼうぎょ:defense:N2}を[構築]{こうちく:build:N2}しています。\n\n#en\nA certain proportion of players use modified clients or memory-tampering tools. At GREE, server-side behavior log analysis is combined with device-side modified-OS detection (so-called root\u002Fjailbreak detection) and machine-learning-based behavior pattern classification, building a multi-layered defense.\n::\n\n::para\n[特に]{とくに:especially:N4}リアルタイム[対戦]{たいせん:battle:N3}では、サーバー[権威]{けんい:authority:N1}[方式]{ほうしき:approach:N3}と[併用]{へいよう:concurrent use:N1}し、[物理]{ぶつり:physical:N4}[法則]{ほうそく:laws:N2}や[制限]{せいげん:limit:N3}[時間]{じかん:time:N5}に[反する]{はんする:violate:N3}[操作]{そうさ:operations:N1}は[受理]{じゅり:accepted:N3}しません。[疑わしい]{うたがわしい:suspicious:N3}アカウントは[人手]{ひとで:human:N4}による[確認]{かくにん:review:N3}キューへ[送ら]{おくら:sent:N4}れ、[誤]{ご:false:N3}[検知]{けんち:detection:N1}を[避け]{さけ:avoid:N1}つつ[厳正]{げんせい:strict:N1}な[対応]{たいおう:handling:N1}が[行わ]{おこなわ:carried out:N5}れます。\n\n#en\nEspecially in real-time battles, this is used together with the server-authoritative approach, and operations that violate physical laws or time limits are not accepted. Suspicious accounts are sent to a human review queue, ensuring strict handling while avoiding false detections.\n::\n\n::heading\n[海外]{かいがい:overseas:N4}[展開]{てんかい:expansion:N1}の[撤退]{てったい:retreat:N1}と[再]{さい:re-:N2}[挑戦]{ちょうせん:attempt:N1}\n\n#en\nThe Retreat from Overseas Expansion and Re-attempt\n::\n\n::para\n[同社]{どうしゃ:the company:N4}は[2011年]{にせんじゅういちねん:2011:N5}[前後]{ぜんご:around:N5}にOpenFeint[買収]{ばいしゅう:acquisition:N3}など[積極的]{せっきょくてき:aggressive:N2}な[海外]{かいがい:overseas:N4}[展開]{てんかい:expansion:N1}を[行い]{おこない:undertook:N5}ましたが、[文化]{ぶんか:cultural:N3}の[違い]{ちがい:differences:N3}や[現地]{げんち:local:N3}[競合]{きょうごう:competitors:N2}の[強さ]{つよさ:strength:N4}により、[2014年]{にせんじゅうよねん:2014:N5}[頃]{ごろ:around:N2}までに[多く]{おおく:many:N4}の[海外]{かいがい:overseas:N4}[拠点]{きょてん:bases:N1}を[縮小]{しゅくしょう:downsized:N1}・[撤退]{てったい:withdraw:N1}しました。[近年]{きんねん:in recent years:N4}は[北米]{ほくべい:North America:N3}・[アジア]{あじあ:Asia}[向け]{むけ:for:N3}に[特定]{とくてい:specific:N3}タイトルを[再]{さい:again:N2}リリースする[形]{かたち:form:N3}で[再]{さい:re-:N2}[挑戦]{ちょうせん:attempt:N1}を[進め]{すすめ:proceed:N3}ています。\n\n#en\nThe company undertook aggressive overseas expansion around 2011, including the acquisition of OpenFeint, but due to cultural differences and the strength of local competitors, by around 2014 it had downsized or withdrawn from many overseas bases. In recent years, it has been re-attempting expansion by re-releasing specific titles for North America and Asia.\n::\n\n::heading\nブロックチェーンゲームへの[拡張]{かくちょう:expansion:N1}\n\n#en\nExpansion into Blockchain Games\n::\n\n::para\n[2021年]{にせんにじゅういちねん:2021:N5}[以降]{いこう:and after:N3}、GREEはブロックチェーンゲーム[領域]{りょういき:domain:N2}にも[本格]{ほんかく:full-scale:N3}[参入]{さんにゅう:enter:N3}しています。[従来]{じゅうらい:traditional:N1}のサーバー[管理]{かんり:managed:N2}[型]{がた:type:N2}アイテムとは[異なり]{ことなり:differ:N1}、NFTとして[発行]{はっこう:issued:N4}されたアイテムはユーザーの[ウォレット]{うぉれっと:wallet}に[帰属]{きぞく:belong:N1}し、[二次]{にじ:secondary:N3}[流通]{りゅうつう:market:N3}も[可能]{かのう:possible:N3}です。[同社]{どうしゃ:the company:N4}は[独自]{どくじ:proprietary:N1}のブロックチェーン[基盤]{きばん:platform:N1}や[他]{た:other:N3}[社]{しゃ:company:N4}チェーンとの[相互]{そうご:mutual:N3}[運用]{うんよう:operation:N4}を[模索]{もさく:explore:N1}しつつ、[既存]{きぞん:existing:N1}ゲームとの[統合]{とうごう:integration:N1}を[進め]{すすめ:advancing:N3}ています。\n\n#en\nFrom 2021 onward, GREE has entered the blockchain-game domain in earnest. Unlike traditional server-managed items, items issued as NFTs belong to users' wallets and can be traded on secondary markets. The company is exploring its own blockchain platforms and interoperability with other companies' chains, while advancing integration with existing games.\n::\n\n::callout\n[要点]{ようてん:key point:N3}：ブロックチェーンゲームは[資産]{しさん:assets:N3}の[所有権]{しょゆうけん:ownership:N3}をユーザーに[移す]{うつす:transfer:N2}という[根本的]{こんぽんてき:fundamental:N2}な[変化]{へんか:change:N3}を[伴う]{ともなう:accompanies:N1}ため、[従来]{じゅうらい:traditional:N1}の[運営]{うんえい:operations:N2}[手法]{しゅほう:methods:N3}の[見直し]{みなおし:review:N3}が[必要]{ひつよう:required:N3}です。\n\n#en\nKey point: Because blockchain games involve a fundamental change — transferring ownership of assets to the user — traditional operational methods must be reviewed.\n::\n\n::heading\n[今後]{こんご:going forward:N5}の[展望]{てんぼう:outlook:N1}\n\n#en\nFuture Outlook\n::\n\n::para\n[長期]{ちょうき:long-term:N3}[運営]{うんえい:operating:N2}タイトルの[安定]{あんてい:stable:N3}[運用]{うんよう:operation:N4}と、[新]{しん:new:N4}[技術]{ぎじゅつ:technology:N2}[領域]{りょういき:domain:N2}への[拡張]{かくちょう:expansion:N1}を[両立]{りょうりつ:balance:N3}させることがGREEの[現在]{げんざい:current:N3}の[課題]{かだい:challenge:N2}です。リアルタイム[対戦]{たいせん:battle:N3}・[決済]{けっさい:payment:N3}・[不正]{ふせい:cheating:N4}[対策]{たいさく:countermeasures:N1}という[基本]{きほん:basic:N1}[要素]{ようそ:elements:N1}を[磨き]{みがき:refining:N2}つつ、[海外]{かいがい:overseas:N4}[市場]{しじょう:market:N3}とブロックチェーン[領域]{りょういき:domain:N2}での[新た]{あらた:new:N4}な[挑戦]{ちょうせん:attempts:N1}が[継続]{けいぞく:continue:N1}していくと[見られ]{みられ:seen:N5}ます。\n\n#en\nGREE's current challenge is to balance the stable operation of long-running titles with expansion into new technology domains. While refining the basic elements of real-time battles, payment, and anti-cheat, new attempts in overseas markets and the blockchain domain are expected to continue.\n::\n",{"id":66,"title":69,"topicPath":10,"questions":70},"GREE Mobile Game Operations — Quiz",[71,96,117,138,159,180],{"id":72,"question":73,"options":76,"correctLabel":82,"explanation":93},"q1",{"en":74,"jp":75},"Which statement about disclosure of gacha drop rates in Japan matches the article?","日本のガチャ確率表示について、本記事の説明と一致するものを選んでください。",[77,81,85,89],{"label":78,"jp":79,"en":80},"ア","確率表示は完全に各社の任意であり、法的な規制や業界自主規制は存在しない。","Drop-rate disclosure is entirely voluntary for each company, with no legal or industry self-regulation in place.",{"label":82,"jp":83,"en":84},"イ","2016年にJOGAが自主規制として確率表示を義務化し、2022年の景品表示法運用基準改訂で事実上の法的義務となった。","JOGA's 2016 self-regulation made drop-rate disclosure mandatory, and the 2022 revision of the Premiums and Representations Act guidelines turned it into a de facto legal obligation.",{"label":86,"jp":87,"en":88},"ウ","確率表示は2010年代からすべての国で法的に義務化されている。","Drop-rate disclosure has been legally required in every country since the 2010s.",{"label":90,"jp":91,"en":92},"エ","確率表示は公開すると不正の温床になるため、ゲーム内では禁止されている。","Disclosing drop rates is banned in-game because publishing them would invite cheating.",{"en":94,"jp":95},"The article explains that JOGA's 2016 self-regulation and the Consumer Affairs Agency's 2022 revision of the Premiums and Representations Act guidelines together made drop-rate disclosure a de facto legal obligation.","本記事では、JOGAによる2016年の自主規制と、2022年の消費者庁による景品表示法運用基準改訂が、確率表示を事実上の法的義務にしたと説明しています。",{"id":97,"question":98,"options":101,"correctLabel":86,"explanation":114},"q2",{"en":99,"jp":100},"What primary measure does GREE use to prevent double-charging on in-app purchases?","アプリ内課金の二重決済を防ぐためにGREEが採用している主要な手段は何ですか。",[102,105,108,111],{"label":78,"jp":103,"en":104},"クライアント側でレシートを暗号化して保存する。","Encrypting and storing receipts on the client side.",{"label":82,"jp":106,"en":107},"ネットワーク切断時に自動的に購入をキャンセルする。","Automatically cancelling the purchase if the network drops.",{"label":86,"jp":109,"en":110},"各購入トランザクションに一意のレシートIDを紐付け、サーバー側でべき等処理を徹底する。","Attaching a unique receipt ID to each purchase transaction and enforcing idempotent processing on the server side.",{"label":90,"jp":112,"en":113},"ユーザーに毎回パスワードを入力させ、二重購入を心理的に防ぐ。","Requiring the user to enter a password every time as a psychological deterrent against double purchases.",{"en":115,"jp":116},"The keys to preventing double charges are idempotency (the same input yields the same result even on retries) and identifying each transaction via a unique receipt ID.","障害が発生しても結果が同じになる「べき等性」と、一意のレシートIDによるトランザクション識別が二重決済防止の鍵です。",{"id":118,"question":119,"options":122,"correctLabel":82,"explanation":135},"q3",{"en":120,"jp":121},"What is the main reason WebSocket was adopted as the real-time PvP backbone?","リアルタイム対戦基盤としてWebSocketが採用された主な理由は何ですか。",[123,126,129,132],{"label":78,"jp":124,"en":125},"WebSocketは課金APIとの統合が容易だから。","WebSocket is easy to integrate with the billing API.",{"label":82,"jp":127,"en":128},"HTTPポーリングでは遅延が許容範囲に収まらず、常時接続による低遅延通信が必要だから。","HTTP polling does not keep latency within acceptable limits, so a persistent low-latency connection is required.",{"label":86,"jp":130,"en":131},"WebSocketは自動的にチート対策機能を提供するから。","WebSocket automatically provides anti-cheat features.",{"label":90,"jp":133,"en":134},"WebSocketはガラケー時代から標準的に使われていた技術だから。","WebSocket has been a standard technology since the feature-phone era.",{"en":136,"jp":137},"In synchronous PvP, millisecond-level latency dramatically affects player experience, so polling is insufficient and persistent-connection WebSocket was chosen.","同期対戦ではミリ秒単位の遅延が体験を大きく左右するため、ポーリング方式では不十分で、常時接続のWebSocketが選ばれました。",{"id":139,"question":140,"options":143,"correctLabel":82,"explanation":156},"q4",{"en":141,"jp":142},"What is the main purpose of the \"authoritative server\" model in real-time PvP?","リアルタイム対戦における「権威サーバー方式」の主な目的は何ですか。",[144,147,150,153],{"label":78,"jp":145,"en":146},"サーバーリソースを節約するため。","To save server resources.",{"label":82,"jp":148,"en":149},"クライアント改竄による不正を根本的に防ぐため。","To fundamentally prevent cheating via client tampering.",{"label":86,"jp":151,"en":152},"プレイヤー同士のチャット機能を実現するため。","To enable player-to-player chat.",{"label":90,"jp":154,"en":155},"App Storeの審査を通すために必要だから。","Because it is required to pass App Store review.",{"en":157,"jp":158},"By validating inputs on the server and broadcasting only the resulting state, the model prevents illegitimate state changes caused by client modification.","操作入力をサーバー側で検証し、結果のみを配信することで、クライアント改造による不正な状態変更を防ぎます。",{"id":160,"question":161,"options":164,"correctLabel":90,"explanation":177},"q5",{"en":162,"jp":163},"Which component of GREE's layered anti-cheat defense is NOT mentioned in the article?","GREEのチート検知における多層防御の構成要素として、本記事で挙げられていないものはどれですか。",[165,168,171,174],{"label":78,"jp":166,"en":167},"サーバー側での行動ログ解析。","Server-side behavior log analysis.",{"label":82,"jp":169,"en":170},"端末側のroot\u002Fjailbreak判定。","Device-side root\u002Fjailbreak detection.",{"label":86,"jp":172,"en":173},"機械学習による行動パターン分類。","Behavior-pattern classification via machine learning.",{"label":90,"jp":175,"en":176},"ブロックチェーン上での取引履歴の公開検証。","Public verification of transaction history on a blockchain.",{"en":178,"jp":179},"The article lists three layers: server-side log analysis, device-side detection of modified operating systems, and ML-based pattern classification. Blockchain transaction verification is not mentioned in the anti-cheat context.","本記事では、サーバー側ログ解析、端末側の改造OS検出、機械学習によるパターン分類の三層を挙げています。ブロックチェーン取引検証はチート検知の文脈では言及されていません。",{"id":181,"question":182,"options":185,"correctLabel":82,"explanation":198},"q6",{"en":183,"jp":184},"Which statement about GREE's overseas expansion matches the article?","GREEの海外展開について、本記事の説明と一致するものを選んでください。",[186,189,192,195],{"label":78,"jp":187,"en":188},"GREEは海外展開を一度も行ったことがない。","GREE has never expanded overseas.",{"label":82,"jp":190,"en":191},"2011年前後に積極的に展開し、2014年頃までに多くの拠点を縮小・撤退、近年は特定タイトルで再挑戦している。","GREE expanded aggressively around 2011, downsized or withdrew from many sites by around 2014, and has recently re-entered with select titles.",{"label":86,"jp":193,"en":194},"海外展開は順調で、現在も全世界で同一のサービスを提供している。","Overseas expansion has gone smoothly and GREE continues to offer the same service worldwide.",{"label":90,"jp":196,"en":197},"海外展開は完全に終了し、今後再開する予定はない。","Overseas expansion has fully ended with no plans to resume.",{"en":199,"jp":200},"The article explicitly describes an aggressive push including the OpenFeint acquisition, a subsequent downsizing and withdrawal, and a recent retry with specific titles.","OpenFeint買収などの積極的展開、その後の縮小・撤退、そして近年の再挑戦という経緯が記事に明記されています。"]