[aRoach]

Well, it's simple...:

Quote:

Originally Posted by ****** I need to upload a new version anyway, there are a few minor "issues" (not bugs) with the current one that have been fixed. One of these fixes would address this problem slightly by making it possible to omit the "extract" macro from sscanf, but that's no use if you want both. I might be able to change the sscanf code to: pawn Код: #define hex:%0;unformat(_:EXTRZ:EXTRX:%1); %0;unformat(_:EXTRZ:EXTRX:%1); That SHOULD actually fix the problem entirely, would you mind replacing "#define hex:" in your "sscanf2.inc" file with that line and see if the errors go? The only problem with this is that if people declare a variable as "hex:" when using "extract", they might then expect it to be printed as "hex" when they use this library without an explicit tag, even though in both cases the "hex:" tag is a fake hint, rather than a true tag (sort of). Maybe I should use "from_hex:" and "from_playerid:" instead to make it clear that they STARTED as hex, but now aren't (although they sort of are given storage methods). Anyway, this isn't really the right topic for this - sorry Slice.

Or, you can delete:

pawn Код:

else if ( iTag == tagof( hex: ) || iTag == tagof( Hex: ) )
{
    // Code..
}

Nothing happens... Because 0-Admin doesn't use that snippet of code...