Some help with my v158 sniffed packets

[CRoP]

Hi, is there anyone who can help me with this?

I have a problem with the new warp_to_map 0x160 for v158.2. I have tried to put static numbers so that they match the packet but it still dcs me with error 38. In the client error provided is also pointing to warp_to_map. But I am not sure if there is any other factor that might DC me, could anyone help with the new structure/other possible DC causes? Thanks very much :)

The packet that I am comparing to has 1787 bytes in it (repeated twice with same total bytes)
And my packet sends 1787 bytes as well.

[MentaL]

[Tyler1q1q]

One thing I noticed recently was that the client would send the crash log as Error 38ing on WARP_TO_MAP, but it was a completely different opcode altogether causing the crash. Attempt to hardcode the WARP_TO_MAP with a GMS packet just to make sure there are no mis-alignments in the structure that would cause an error 38.

[CRoP]

Wondering if anyone else can help me with that?