npc updating is wrong, could be too many npc bits for the npc id
|
|

What does this mean? it doesnt happen all the time
Code:Error: mobjunk Too many npcs java.lang.RuntimeException: eek at client.Client.method139(Client.java:12406) Error: T2 - 65,81,208 - 11,2661,3308 - 77,7,-3,10,64,18,0,43,-1,-3,0, at client.Client.updateNPCs(Client.java:2434) at client.Client.parsePacket(Client.java:13986) at client.Client.mainGameProcessor(Client.java:4072) at client.Client.processGameLoop(Client.java:3299) at client.RSApplet.run(RSApplet.java:199) at client.Client.run(Client.java:5899) at java.lang.Thread.run(Unknown Source)Code:if(k > npcCount) { Signlink.reporterror(myUsername + " Too many npcs"); throw new RuntimeException("eek"); }
npc updating is wrong, could be too many npc bits for the npc id
Last edited by Spooky; 12-24-2017 at 03:21 PM.





may be something to do with the server sending over 255 npcs to render in the region you're in
disable all npcs and specifically spawn 255-300 around you. you can find out what it may be then

No i never touched npc updating, my friend did it so theres a possibility he forgot/done something wrong. but i dont remb this ever happening before i packed 474 anims/gfxs/npcs
I personally don't know what 'method139' does but it seems that the server is sending more npcs then the 'npcCount' in the client. and thats why its throwing the eek - too many npcs.
I believe 'method139' is what reads how many npcs the server sends to the client.

| « 317 ruse - fullscreen | Ruse - Exporting Models? » |
| Thread Information |
Users Browsing this ThreadThere are currently 1 users browsing this thread. (0 members and 1 guests) |