BNSBoost is a simple loader for starting NCSoft's Blade and Soul. Not endorsed by them in any way, shape, or form; Blade and Soul, etc. are all trademarks of NCSoft.

BNSBoost bypasses NCSoft's file verification, so you can run a patched game straight from the official launcher.

It features options for:

• Enabling game to use all cores
• Disabling texture streaming
• Disabling loading screens
• Disabling XIGNCODE3
• Enabling multi-client support
• Autopatching common XML edits (DPS meter, AFK check, etc.)
• Arbitrary game XML edits
• Custom mods (voice packs, etc.)
• Randomized splash changing
• Forcing the default launcher to open up with BNSBoost

Latest stable build — you probably want this.

Unstable builds — don't file bug reports regarding these builds, but feel free to mention them in Discord.

Just run the BNSBoost.exe you got from the release archive!

We also maintain a wiki on using BNSBoost. Some topics you may be interested in:

• Changing splash screen; randomized splashes for your enjoyment
• Modding your game; voice packs, model changes, etc.
• Arbitrary game file patches; for running things like custom xinput.dll builds

Your antivirus might complain since BNSBoost's launcher hooking can match its malware definitions, in which case you'll have to whitelist BNSBoost before proceeding. If you're jumpy about security, you can always compile it from the source in this repository yourself.

Most antiviruses are alright with it, though.

Absolutely! The use of any 3rd-party tools to run the game is strictly against NCSoft's EULA, and could land you a ban. But if you've already been using a 3rd-party launcher, this isn't really any different.

I figure half the reason people shy away from injection is that it sounds like you're getting a flu shot, and relate that unpleasant experience to what's going on in the launcher. However, injection is a pretty common practice in tools that interface with games nowadays.

So let's be clear: if you're using Discord, Steam, TeamSpeak, etc., you're already injecting into Blade and Soul. These tools inject into the game to provide things like overlays. Though, they avoid mentioning words like "injection" or "hooking" to avoid sounding scary.

Now, many anti-cheats know these platforms inject, and may have whitelists for them. However, if you've enabled client-injecting features, you have already disabled XIGNCODE3. The launcher is not protected by any anti-cheat, so there's no concern regarding the base functionality of BNSBoost ceasing to work if NCSoft decides to switch off XIGNCODE3 to another anti-cheat.

There's a bunch of files included alongside BNSBoost that are necessary for it to function. Below is a brief overview of what each does.

Writes a DLL into a given process' memory. BNSBoost uses these to write agent DLLs into either the launcher or the client.

Injected into NCLauncherR.exe by BNSBoost. Sets up two hooks:

• CreateFileW hook

  Used to bypass file verification by redirecting calls to the unpatched directory, when it exists.

• CreateProcessW hook

  Used to add client flags (-UNATTENDED, -NOTEXTURESTREAMING, -USEALLAVAILABLECORES) when the launcher spawns the client. If bypassing XIGNCODE3, launches inject32.exe or inject64.exe (depending on client bitness) to inject agent_client32.dll or agent_client64.dll into the client.

Injected into Client.exe by the agent_launcher.dll's CreateProcessW hook. Sets up three hooks:

• LoadLibraryW hook

  Detects if the client is trying to load x3.xem or xcorona_x64.xem, and if so redirects the library to our patched ones instead.

• CreateMutexW hook

  Used for multi-client support. The game creates a named mutex "BnSGameClient" to prevent multiple instances from starting; this hook strips the name from it and allows further clients to be started.

• CreateFileW hook

  The client grabs exclusive access to xml[bit].dat / config[bit].dat, which causes clients to exit with "corrupt game file" messages even if the mutex is patched out. This hook is used to ensure that exclusive access cannot be obtained on any file used by the client, downgrading to sharing read access.

Copied into the launcher's directory as wtsapi32.dll, it warns you if you're launching NC Launcher without BNSBoost (as this would destroy any patches you have applied). It can also be configured to launch BNSBoost unconditionally, without first prompting. The showing of this warning can be toggled in BNSBoost's Settings tab.

VirtualPuppet/XignCode3-bypass built for 32-bit and 64-bit targets, respectively.

I should say that I wrote this project for myself, and it works for me — in that sense, the goal of this project is complete. However, since I figure this may be useful for others, I'll be happy to provide a best-effort attempt at helping out with any errors caused by BNSBoost.

You can use the ticket tracker to report issues, and I'll probably get to them fairly quickly.

Good luck!

• @LoadLibraryW, current maintainer
• @Xyene, initial author and managing releases/documentation
• @zeffy, basically a well of BNS internals knowledge

BNSBoost wouldn't have been possible without the help or inspiration from:

• @mrexodia's x64dbg tool
• @Evengard for his now-defunct "bnsnogg" project
• @ronny1982 for his original work on bnsdat reversing, LokiReborn for their initial C# port of it
• Sysinternals for their forum resources and procexp/procmon utilities