NoX Forum

Hmm, what's actually the problem with that npc limit? Why the limit can't be increased with a normal framerate?

The issue is with the monster limit; not the npc limit. Every frame, Nox will send the updated information about every monster you can see to you. However, Nox will only send 2048 bytes of data to a player every frame. What is happening is that if you have too many monsters on the screen, then you run out of available bytes in the packet and some monster just don't get updated. The client will "forget" about anything that hasn't been updated for 8 frames.

My earlier patch fixed this by sending information about half of the monsters every other frame. This way nothing got forgotten; but if a monster is moving, it is now updated less often than it would be otherwise.

I tried another approach to the monster limit (sending extra packets if necessary). This is more invasive, so I would appreciate someone testing it.

ok.
thank you.
i will test it.

Tested. It seems to work perfectly.
If no one finds any bug of this could you please implement it again to the exe I posted before?

Yeah, I'll do that tomorrow.

Attached is a patched GAME.EXE with the solo check removed from PlasmaDraw. It is a client-side patch. I have not tested it with multiple clients.

Works

hey it can use script code of effect list??

for example)
green_bolt, plasma, chaning_lightning

WOW~~ GREAT!!

However, script effect 'PLASMA' is not work.

Latest patches with Host_6 Nox.exe is attached. Nothing is added since last GAME.EXE upload.