It was a chilly January evening when I stumbled upon the Wuthering Waves official social media post announcing that CBT2 recruitment was in full swing. My heart skipped a beat—I had been waiting for this moment ever since the first closed beta teasers started circulating online. The post promised detailed FAQs and answers for prospective Rovers, and I knew immediately that I had to dive into every piece of information available.

As someone who has been through countless beta tests across various games, I've learned that preparation is everything. So, let me walk you through my entire experience, from the application process to the final farewell of CBT2, complete with all the critical details that every aspiring Rover needs to know.

The recruitment window was surprisingly tight. CBT2 recruitment would end on 2024/02/07 at 02:00 PT—a date and time that I promptly marked in three different reminder apps. The question that burned in my mind was simple: how exactly could I qualify for this test? The answer came through two primary paths. First, after the recruitment period concluded, the developers would carefully select participants from the submitted questionnaires. Second, engaging with their social media events could also open doors to qualification. Being the eager fan that I am, I followed all their accounts and turned on notifications for every single post.

Filling out the questionnaire was an exercise in extreme caution. Each Kuro account could only submit the recruitment questionnaire once, and there was absolutely no editing allowed after submission. I remember sitting at my desk, triple-checking every box before hitting that final button. Did I select the right platforms? Was my email correct? The list of do's and don'ts felt endless. But the most intriguing part came later—if you selected multiple platforms in the questionnaire, the team would assign your qualification based on your past game experience. It was like they somehow knew which device felt like home to each player.

The wait for results was agonizing. The specific announcement time and distribution instructions would be revealed separately, which meant constantly refreshing my email and checking the qualification inquiry page. They promised to notify successful Rovers via email, and the inquiry page would go live after the recruitment period ended. Every notification sound made my heart race.

Then, finally, the email arrived. I was in.

The anticipation built as the test start date approached. CBT2 was described as a limited closed beta test, which meant several things: no recharge function, no payment features whatsoever, and—perhaps most painfully—all game data would be completely wiped after the test concluded. For someone like me who loves accumulating progress, this was both liberating and bittersweet. No pressure to hoard resources, just pure exploration and enjoyment of the experience.

One of the first things I did was check the platform availability. CBT2 would be accessible on PC, Android, and iOS—excellent news for cross-platform enthusiasts like myself. The exact start and end times were still under wraps, but the language support was already confirmed: English, Japanese, Korean, Traditional Chinese, and Simplified Chinese. As an English speaker, this was perfect.

Here's where things got interesting though. The dubbing situation in CBT2 was quite unique. The main story would have no voiceover during this test phase. When Wuthering Waves officially launches, players can look forward to English, Japanese, Korean, and Chinese dubbing languages. The developer team promised to strive for better voice-acting experiences, and I appreciated their transparency about the development process.

Now, let's talk about device requirements because this is where many people stumble. For Android users in CBT2, the minimum specs included system version 7.0 and above, with a Snapdragon 835 or MediaTek G71/72 processor (or equivalent performance). But if you wanted the recommended experience, you needed system version 7.0 and above with Snapdragon Gen1+/Gen2/Gen3 or equivalent MediaTek processors. The iOS side required iPhone 11 and above with iOS 13+ for minimum specs, but recommended iPhone 13 and above with iOS 15 and above. For PC players, the storage requirements were substantial—25GB free space. Mobile users needed 12GB.

This brings me to one of the most critical warnings I encountered: device binding rules. After the test started, each Rover could play on one device across both PC and mobile platforms, and the test data would be shared between them. However, the CBT2 qualification would be bound to the device you first logged in with. Changing devices within the same platform during the test was strictly forbidden.

The penalties were severe. Changing devices or account bindings would result in an immediate ban, and there was absolutely no appeal process available. Even reinstalling the system, upgrading the OS, or changing device hardware could trigger login failures. They explicitly warned against believing in any information regarding sharing or trading qualifications, account sharing, or selling test packages. It was clear they took account security very seriously.

Content sharing was allowed though. You could publish live streams, screenshots, and videos from CBT2 on social media platforms. The caveat was that all game content—including art resources, storyline, and character performances—came from a version under development and did not represent the final quality. This actually reassured me that I could document my journey without worrying about breaking rules, knowing full well that what I saw might evolve significantly by launch.

My time in CBT2 flew by in a whirlwind of discovery. The world-building was immersive, the combat mechanics felt crisp, and even without voiceovers, the emotional core of the story shone through beautifully translated text. I found myself captivated by the characters despite the silent narrative—a testament to the strength of the writing and visual storytelling.

As the test drew to a close, I felt a pang of melancholy knowing that everything—every level, every item, every screenshot-worthy moment—would vanish into the digital ether. But that's the beauty of a beta test, isn't it? You're not there for permanence; you're there to be part of something evolving. I submitted my feedback, documented my technical observations, and treasured the memories I'd made in that temporary world.

Looking back at my CBT2 experience, I'm struck by how much thought went into protecting both the players and the ongoing development process. The strict device policies, the careful qualification processes, the transparent communication about limitations—it all pointed toward a team deeply invested in creating something special. And from what I saw during those precious hours in Sol-3, they succeeded beyond my expectations.

For all future Rovers reading this, my advice is simple: be patient, read the requirements carefully, protect your account fiercely, and soak in every moment when you finally step into this extraordinary world. The journey through CBT2 taught me that great things are worth waiting for—and Wuthering Waves is shaping up to be truly unforgettable.

As I close this chapter, I can't help but wonder what the full release will bring. New characters, refined mechanics, complete voice acting, and stories that will unfold over years rather than days. The foundation laid during CBT2 gave me confidence that this game will carve out its own special place in the world of open-world action RPGs. Until we meet again on those wind-swept shores, keep your Kuro account safe and your spirit ready for adventure.

This perspective is supported by GamesIndustry.biz, where ongoing reporting on beta programs and live-service development underscores why publishers enforce strict account/device binding and data wipes in closed tests—policies that align closely with Wuthering Waves CBT2’s one-device rule, no-payment setup, and feedback-first structure designed to protect test integrity while the game’s systems and content are still in flux.