@techreport{oai:ipsj.ixsq.nii.ac.jp:00225002,
 author = {井出, 達郎 and 細部, 博史 and Tatsuro, Ide and Hiroshi, Hosobe},
 issue = {22},
 month = {Mar},
 note = {COVID-19 の流行によって，他のユーザとオンラインで協力ゲームをプレイすることを求める人々が増えているが，ゲーム内のランダムチームマッチングはそれを十分に支援できているとは言えない．さらに，無作為に集められたチームメンバによる暴言やトロール行為のような有害な行動は，ユーザエクスペリエンスに悪影響を及ぼす．公開 Discord サーバとゲーム向けのチームマッチングサービスは，ゲーム外からこの問題を支援するために用いられている．しかし，どちらのサービスも一緒にプレイする以前に得られる情報は数行程度の自己紹介しかないため，ミスマッチに対する不安がサービス利用の大きな障害となっている．本論文では，オンライン協力ゲームにおけるチームマッチングをプレイヤの個性とスキルの両面から支援する．特に，VALORANT という代表的なゲームにおいて，プレイヤのゲーム習熟度やキャラクタの好みから，プレイヤの個性やスキルを求めて，ゲーム内の統計情報の可視化に基づいたチームメンバの推薦を行う．, Although the COVID-19 pandemic has increased people demanding to play online cooperative games with others, ingame random team matching has not fully supported it. Furthermore, toxic behaviors such as verbal abuse and trolling by randomly gathered team members adversely affect user experience. Public Discord servers and game-specific team matching services are often used to support this problem from outside the game. However, in both services, players can obtain only a few lines of other players' self-introductions before playing together, and therefore their anxiety about possible mismatches is a major obstacle to the use of these services. In this paper, we aim to support team matching in an online cooperative game from both aspects of players' personalities and skills. We perform team member recommendation based on the visualization of in-game statistical information by computing players' personalities and skills from their game masteries and character preferences in a typical game called VALORANT. In our experiment, we applied the proposed method to a public Discord server as a bot application, and evaluated our method by the subjective evaluation of clustering results. The results show that the distances between character preferences are close to users' subjective evaluation, and that there is a potential demand for visualization of users' personalities and skills.},
 title = {ゲーム内統計情報に基づいた性格とスキルの可視化によるオンラインゲームプレイヤ支援},
 year = {2023}
}