[pilger]

Hey guys,

I'm trying to do this:

        new Handle:data = CloneHandle(datapack);

        ResetPack(data);
        SetPackPosition(data, 5);

        LogMessage("#TEST# %N:%f", client, ReadPackFloat(data));

With no success.

While this:

        new Handle:data = CloneHandle(datapack);

        ResetPack(data);
        ReadPackCell(data);
        ReadPackCell(data);
        ReadPackCell(data);
        ReadPackCell(data);
        ReadPackCell(data);

        LogMessage("#TEST# %N:%f", client, ReadPackFloat(data));

Works as intended.

They are part of a callback function that interacts with GameMe plugin.

Any thoughts? Is the function SetPackPosition() broken?

[Impact123]

I'll leave the details to someone else, but SetPackPosition doesn't really work line an array index.

[pilger]

Hmm. How does it work then? Is it explained somewhere?

[Peace-Maker]

You shouldn't be using SetPackPosition. It's setting the position of the internal char* stream to some offset. You'd need to calculate the offset yourself which will likely break easily.

WritePackCell first "pushes" the size of a cell (4 bytes) on the stream then the cell itself (4 bytes again). So you'd need to set the pack position to 5*8=40. It gets trickier with strings in the pack.. You'd be better off with an adt_trie. SetPackPosition should be deprecated as it's of no practical use.

[pilger]

Thanks for the info, Peace-Maker.

Well, using adt_trie would be a pain, since I'm just working with GameME's natives. So I guess I'll stick with reading all the unnecessary cells to get to the position I need.

Hope this helps someone with a similar question on the future.

[xf117]

You still can use SetPackPosition. There is nothing wrong with it if you know the right offset.

[asherkin]

Originally Posted by Peace-Maker SetPackPosition should be deprecated as it's of no practical use.

It has practical use, but you ideally need to be saving the positions as you write.