What is packet 1015 (String Packet) Subtype 13 and 14?

Hello guys,

I`m creating monster spawns in Hellmouth.
I think I found some way but the monsters are invinsible and you only see their shadows.
Now everytime it wants to load a monster it shows me:
Unknows string subtype 13.
Unknows string subtype 14.

Anyone got an idea of what it could be?

EDIT: Already checked the wiki, nothing..

Thanks,
JobvdH!

its your spawn monster packet (10014)....simply the packet you are using is not for the patch you are working on (its older) and you need to update it and those sub types will be gone.

Ps. for the patch 5300+ the Wiki will not help you.

good luck.

Quote:

Originally Posted by JobvdH Hello guys, I`m creating monster spawns in Hellmouth. I think I found some way but the monsters are invinsible and you only see their shadows. Now everytime it wants to load a monster it shows me: Unknows string subtype 13. Unknows string subtype 14. Anyone got an idea of what it could be? EDIT: Already checked the wiki, nothing.. Thanks, JobvdH!

use the patch the source was written for or update your packets and it will be fine

Okay I'll try it out, thanks.

EDIT: Didn't work the monster are still invinsible...

If the monsters are invisible then its got nothing to do with the string packet lol...thats an issue with the monster spawn packet x.x

Then explain to me why it shows that error....

lol beats me, i dunno what you've done to pro's source, monsters only appear as invisible if you screwed up the entity spawn packet.

If the spawn entity packet is wrong, then the monsters will be invisible, and the client will send those two sting packets (perhaps requesting the name of the monster?)
Just fix your spawn packet for your patch and it will be just fine.

Quote:

Originally Posted by Korvacs lol beats me, i dunno what you've done to pro's source, monsters only appear as invisible if you screwed up the entity spawn packet.

It doesn't work because he's using the wrong patch for the source, therefor the entity spawn packet in the source is no longer correct.

I'm guessing he's using a patch after where the mesh offset changed. because of this everything will show as invisible and the client will instead spam the server with requests for the spawn to be resent to it because it's missing information that it needs to display it.

Alternatively it could just be a bad mesh but that seems far less likely.

Well yeah like i said, hes screwed up the entity spawn packet.

I think the best thing to do in your case is to either,

A. See if you can correct the spawn entity packet based on someone elses packet structure.

B. Not attempt to change to a newer version of the client if you dont understand how to make the necessary changes to the packet structures in order to successfully complete the change of version.

Learn to walk before you run i believe is a fitting description of what you need to do here...

Quote:

Originally Posted by Korvacs Learn to walk before you run i believe is a fitting description of what you need to do here...

I think a lot of people here need to follow that ideology.

Guys, I USE A 5355 CLIENT like pro said >_>,
Stop stop telling me stuff where you don't know those things.
Jeesh

Quote:

Originally Posted by JobvdH Guys, I USE A 5355 CLIENT like pro said >_>, Stop stop telling me stuff where you don't know those things. Jeesh

He never said that, he said to use the correct client, you never specified that you werent using the correct client, so everyone dealt with it appropriately, in this case the problem is the fact that the spawn packet isnt correct for the client you were trying to use, be that because you failed to update to the newer client correctly, or the fact that you werent using the correct client in the first place is completely irrelevant =x

Edited.

Quote:

Originally Posted by |xabi| #request close

well no1 can Request Thread Closing except the Thread Creator himself .. beside that u are Bumping very old Thread just to say that .. if u wanted it to be closed y didnt u Report it instead of useless bumping