[XMAS Release][v232] Swordie source

Every few years, someone comes by and bless the MapleStory forum with an A+ release and this is one of them.
One of the most stable highest version of GMS source, and with the current things on private server, this might be the last one ever :(
Thank you for your work Sjonnie.
 
Has anyone figured out how to add some of the later game fights like black mage, verus hilla? Supposedly they're fun fights and part of the GMS v232 release.

Also - not sure how many people this applies to but wanted to share some good news for those with intel ultra processors, I found how a way to remove 60%+ of the lag and stuttering from this release (still some, but a noticeable improvement)
1. Set to P cores only on process lasso, but keep all P cores checked than running on a single core
2. Set performance to the external GPU and disable the iGPU in bios
3. Run in windowed mode (1920 x 1080) and upscale to borderless fullscreen using magpie
4. Disable debug logs and comment out the null packets firing in IDEA. Not sure why but this version has a LOT of logs hitting the IDEA console
5. Change damage numbers from cascading to strictly mini
6. Vsync off and cap FPS at 60 or 144
 
Has anyone figured out how to add some of the later game fights like black mage, verus hilla? Supposedly they're fun fights and part of the GMS v232 release.

Also - not sure how many people this applies to but wanted to share some good news for those with intel ultra processors, I found how a way to remove 60%+ of the lag and stuttering from this release (still some, but a noticeable improvement)
1. Set to P cores only on process lasso, but keep all P cores checked than running on a single core
2. Set performance to the external GPU and disable the iGPU in bios
3. Run in windowed mode (1920 x 1080) and upscale to borderless fullscreen using magpie
4. Disable debug logs and comment out the null packets firing in IDEA. Not sure why but this version has a LOT of logs hitting the IDEA console
5. Change damage numbers from cascading to strictly mini
6. Vsync off and cap FPS at 60 or 144
yep I have vhilla (although I customized it a bit). just reference other sources. I dont have black mage yet, not sure what source has it working
 
Awesome! Any chance you could upload your file or clarify what you mean by "reference other sources"? If this is a reasonably straightforward implementation, would love to try it out for myself.
 
Awesome! Any chance you could upload your file or clarify what you mean by "reference other sources"? If this is a reasonably straightforward implementation, would love to try it out for myself.
I run a public server so i dont feel fully comfortable sharing my files. Basically use other sources here on ragezone to get the data you need to implement other bosses. Ive done just that and have vhilla and darknell, working toward gloom next but he is a pain
 
I am getting this error too, did you manage to solve it? only thing I havent tried is zipping up the local copy of the client and passing it to my friend.

Edit: tried zipping up my whole local copy (which is definitely working) and getting my friend to download it, still failing with kernelbase.dll error, at this point I am convinced something on an OS level that DOES NOT like this iteration of the game, I had a v83 server (based off cosmicp0nk) which my friend was able to join no issues, sadly if anyone has a fix or workaround that'd be great!

Edit2: ran a hash checksum, both client folders match bit for bit so it definitely is a user environment issue, tried literally everything bar a full os wipe, interestingly, running procmon, the game no longer launches, without procmon, it launches, hits a white screen, and crashes with the kernelbase.dll error, attached both logs if anyone can figure it out.
Did you ever manage to find a fix, or pinpoint further? Struggling with the same issue and running out of troubleshooting options. Two of the few options remaining would be trying an older windows build, or dll injection to try and see if that solves the issue.
 
Hi there! insane release. Can I check for damage cap, it seems to be capped at 150b. is there a way to undo the damage cap?
 
after following everything, after lunching the server i am stuck here:
2026-09-05 22:25:21.006 [INFO] [Bera-3] - Channel Bera-3 listening on port 8587
2026-09-05 22:25:21.006 [INFO] [Thread-1] net.swordie.ms.connection.api.ApiAcceptor - API listening on port 8483
2026-09-05 22:25:21.006 [INFO] [Bera-1] - Channel Bera-1 listening on port 8585
2026-09-05 22:25:21.006 [INFO] [Bera-4] - Channel Bera-4 listening on port 8588
2026-09-05 22:25:21.006 [INFO] [Thread-2] net.swordie.ms.connection.netty.LoginAcceptor - Login listening on port 8484
2026-09-05 22:25:21.006 [INFO] [Bera-2] - Channel Bera-2 listening on port 8586
2026-09-05 22:27:08.511 [DEBUG] [nioEventLoopGroup-8-1] io.netty.buffer.AbstractByteBuf - -Dio.netty.buffer.checkAccessible: true
2026-09-05 22:27:08.512 [DEBUG] [nioEventLoopGroup-8-1] io.netty.buffer.AbstractByteBuf - -Dio.netty.buffer.checkBounds: true
2026-09-05 22:27:08.513 [DEBUG] [nioEventLoopGroup-8-1] io.netty.util.ResourceLeakDetectorFactory - Loaded default ResourceLeakDetector: io.netty.util.ResourceLeakDetector@7f786b50
2026-09-05 22:27:33.724 [DEBUG] [nioEventLoopGroup-8-1] net.swordie.ms.connection.api.ApiHandler - [API In] | null, 100/0x64 | 06 00 69 73 6B 6F 6E 6F 09 00 49 61 6D 61 6D 72 31 32 40
2026-09-05 22:27:33.740 [DEBUG] [nioEventLoopGroup-8-1] net.swordie.ms.connection.api.ApiEncoder - [API Out] | FORCED_STAT_SET, 100/0x64 | 00 32 00 36 5D 43 6A 70 57 66 57 32 50 65 4F 67 59 7A 6D 6E 59 79 31 35 63 6B 48 6A 5D 3F 57 5C 5D 74 48 77 30 5D 34 4B 4C 61 65 4C 77 35 68 5F 7A 46 30 76 35 00
2026-09-05 22:39:37.798 [DEBUG] [nioEventLoopGroup-8-1] net.swordie.ms.connection.api.ApiHandler - [API In] | null, 100/0x64 | 05 00 61 64 6D 69 6E 05 00 61 64 6D 69 6E
2026-09-05 22:39:37.805 [DEBUG] [nioEventLoopGroup-8-1] net.swordie.ms.connection.api.ApiEncoder - [API Out] | FORCED_STAT_SET, 100/0x64 | 00 32 00 6C 75 65 4E 38 33 3F 33 5B 7A 71 51 72 46 30 43 43 75 58 45 51 58 64 52 6B 5A 4F 51 33 59 3E 75 46 57 7A 3C 40 4B 54 77 48 51 7B 36 59 53 6C 78 79 6C 04
 
Did you ever manage to find a fix, or pinpoint further? Struggling with the same issue and running out of troubleshooting options. Two of the few options remaining would be trying an older windows build, or dll injection to try and see if that solves the issue.
Did you find a resolution to this issue? I tried this on my PC and laptop which are both Windows 10.

The Dism/Scannow didn't work, ran it multiple tims on both comps.
Reverted downward to different 22h2 revision, even did a roll back of the full computer to see.
Did a full reinstall of all programs, redownloaded files fresh and still nothing.
Even tried figuring out how to replace the Kernalbase.dll file and swapping it with a close version, no resolve.
Read every public forum and response availible based on maplestory issue related to this and other games and no resoluation.
Don't have issue if I run a v83 server or the 17x server Sworide, run those without issue and even the current Maplestory version offically or mapleworlds.
Added exception to virus protection and windows firewall + disabled real time security feathures nothing w/fresh install of all programs and files re-downloaded.
regsvr32 KERNELBASE.dll - didn't work for me. Was more of a hassle then solution due to failed.
Updated all drivers/programs/graphics/ reviewed nothing with that either.


What I haven't tried is to completly reformat my computer and upgrade to windows 11... IDK if I want to go that far yet.

1. One person stated on reddit to try: "This was fixed (no thanks to nexon support) by uninstalling maple from both steam and the nexon launcher, deleting the empty folders for both, and then using regedit to remove all registry files created by/for maplestory. After that, a restart and then a re-install of maple on the nexon client worked!" This is what I will try next to see whats up.
2. "Create a local user or administrator account" and check if the problem still exists.

I will try these two and update if anything, but if there is a soluation please do respond!
 

Attachments

  • SS of fil - [XMAS Release][v232] Swordie source - RaGEZONE Forums
    SS of file.webp
    29.3 KB · Views: 8
GMS 232.2 from the author-documented Steam depot, Swordie local solo server, Windows 11, i9-13900K, RTX 5080. Login and gameplay work, but moving, using skills and opening UI cause severe stutter. Standing idle is smoother. VSync off did not resolve it. A temporary process affinity selecting one logical processor per physical core (including E-cores) also did not improve perceived stutter; original affinity was restored. Hardware Hyper-Threading was NOT disabled.

A local 30-second CPU profile taken during confirmed stutter reports no lost events. The dominant client thread spent about 21.1 seconds scheduled and had no single off-CPU interval longer than 2.84 ms. Three roughly 200–230 ms active-processing intervals repeat similar executable instruction addresses about 10 seconds apart. These are not measured frame durations; the CPU profile was not simultaneous with PresentMon.

Several frequently sampled locations in the original, Nexon-signed Gr2D_DX9, Canvas and PCOM modules are immediately after LOCK CMPXCHG in recursive-owner synchronization code. This does NOT establish a defective lock or prove its relation to the long executable intervals. No executable/DLL performance patches have been applied.

Is there a known, source-documented performance fix or an official compatible graphics-module revision for 232.2 on this CPU generation? I am looking for a version-specific fix without disabling antivirus, bypassing protections, or using unexplained binary patches. Please distinguish tested fixes from configuration suggestions.
 
Hi everyone, I followed the steps on the first page and the steps below to start Maple with just the launcher. But I encountered the error below on my server. I have no idea what to do.

[DEBUG] [PacketEncoder] | Plain sending CHECK_PASSWORD_RESULT, 0/0x0 | E8 00 01 00 32 F7 FD 9E E4 B4 18 10 41 08 00 00
[DEBUG] Client forcibly closed the game.
[DEBUG] [ChannelHandler] | Channel inactive.
[DEBUG] [PacketEncoder] | Plain sending CHECK_PASSWORD_RESULT, 0/0x0 | E8 00 01 00 32 C1 D7 33 C0 44 9F 01 E5 08 00 00
[DEBUG] Client forcibly closed the game.
[DEBUG] [ChannelHandler] | Channel inactive.
normal login system.
1) remove swordie.dll and replace edited nmco dlls to original one.
2) put my NGClient64.aes to client folder.
3) merge chui's PR to your local branch to handle login packet.
(added more info)
4) remove NexonAnalytics64.dll from client folder. to block port 3000 unknown checks.
5) change SERVER_IP in GameConstants.java to `public static final byte[] SERVER_IP = new byte[]{(byte)175,(byte)207,(byte)3,(byte)211};`
chui's PR :


packet analyzing tool.
1) drag and drop your MapleStory.exe to RunEmu64.exe to load packet editor.
you can easily analyze packet format.



src:

download:
 
Back