Invalid bodytype: 240

[myseqfan]

The old version I've been using still works fine (just updated new offsets an still works 4/30) with 1.10 Client and 1.7 Server.

However, when I use the new ones (1.9/1.11), I get the same error every time. With new server running and new client running:

I hit go.
"Invalid bodytype: 240"
>ok
"An unhandled exception....." & a big red X

continuing doesn't help...

Any ideas?

Thx

[Lyroschen]

This might sound silly, but do you have the maps folder in the client folder?

[donk]

i have the same problem but invalid bodytype 192

using new server and clienty( guess ill go back to old one

[cavemanbob]

Does it always do this in a particular zone? As it gives the red X exception I would guess that the data stream is getting out of sync, but I wouldn't rule out that there's zones with other body types...

[myseqfan]

Lyroschen,
Thank you very much for the tip!! rofl

Problem: Invalid Body Type
Possible Solution: Make sure maps are in the directory you're running in, especially since the unzip directory seems to change.

Unfortunately, I still crash with the invalid body type every time I zone.

Thank you very much,
Myseqfan

PS: Thanks a ton for myseq -- you rule, cavemanbob.

[GD_EQ]

I get this error about 90% of the time when I zone...



See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.OverflowException: Value was either too large or too small for an Int32.
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at myseq.Form1.checkMobs()
at myseq.Form1.timer1_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.Callback(IntPtr hWnd, Int32 msg, IntPtr idEvent, IntPtr dwTime)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.3300.0
Win32 Version: 1.0.3705.288
CodeBase: file:///c:/windows/microsoft.net/framework/v1.0.3705/mscorlib.dll
----------------------------------------
System
Assembly Version: 1.0.3300.0
Win32 Version: 1.0.3705.288
CodeBase: file:///c:/windows/assembly/gac/system/1.0.3300.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.3300.0
Win32 Version: 1.0.3705.288
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.3300.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
myseq
Assembly Version: 1.0.1221.41009
Win32 Version: 1.0.1221.41009
CodeBase: file:///C:/WINDOWS/DESKTOP/PROGRAM/CLIENT/CLIENT.EXE
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.3300.0
Win32 Version: 1.0.3705.288
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.3300.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System.Runtime.Serialization.Formatters.Soap
Assembly Version: 1.0.3300.0
Win32 Version: 1.0.3705.288
CodeBase: file:///c:/windows/assembly/gac/system.runtime.serialization.formatters.soap/1.0.3300.0__b03f5f7f11d50a3a/system.runtime.serialization.formatters.soap.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.3300.0
Win32 Version: 1.0.3705.288
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.3300.0__b77a5c561934e089/system.xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.

[The Duck]

A friend of mine just recently started having this problem, and I've been looking into it myself.

A couple of questions for you that have been having this same problem.

1) What OS are you running, my friend is running 98 on his client box, and ME on his EQ machine.

2) Do you get multipel dialog boxes with the same error?

3) Please let us know if it gets fixed some other way =)

A few things I've noticed, I can run just fine and haven't had any problems. My friend is using 1.9b of the server software as well on his ME box. I can connect to HIS box, and I get the same error. He can connect to my box without errors. Obviously, this narrows the problem down to the server sending invalid info in particular, isolated cases.

Please let me know the OS your SERVER is running on if this is still happening to you.

Thanks


*quack*

[Calmari]

I am getting this same error, maps are in seq/maps. I am running 2 98SE machines that are completely updated. Any other ideas as to what may cause this?

[MQSEQ2]

What version of the Client are you using?

The current versions are Server 1.11 and Client 1.15.14.

[Calmari]

Doh!

I snagged the files from the stickied post in the General forum about installing the proggy....and they were several versions out of date. Works great now, thanks for pointing me at the obvious!!

[MQSEQ2]

I knew you was on an older version seen we resolved that awhile back, but I didn't want to sound like a broken record over and over hehe.