[DiscordArchive] Or do I change the AliasNext in Stand to the same one that is in Ready1H?
[DiscordArchive] Or do I change the AliasNext in Stand to the same one that is in Ready1H?
Archived author: Rayad • Posted: 2022-11-02T10:01:10.885000+00:00
Original source
Or do I change the AliasNext in Stand to the same one that is in Ready1H?
Archived author: <o> • Posted: 2022-11-02T10:01:53.014000+00:00
Original source
you read strings "left to right" if that's what you mean. Usually the string table looks something like this in memory
```
\0first string\0second string\0third string\0fourth string\0fifth string
```
and so on
Archived author: <o> • Posted: 2022-11-02T10:01:58.931000+00:00
Original source
\0 being null byte
Archived author: <o> • Posted: 2022-11-02T10:02:24.399000+00:00
Original source
c strings must be read byte by byte, they cannot be precomputed
Archived author: Rymercyble • Posted: 2022-11-02T10:03:08.150000+00:00
Original source
yes so thats what im saying its on end (left in binary) but storing them and reading them here happens left to right so its actually on start and thus i have to skip it
Archived author: Titi • Posted: 2022-11-02T10:04:15.175000+00:00
Original source
Reading is pretty much always left to right
Archived author: stoneharry • Posted: 2022-11-02T10:05:08.764000+00:00
Original source
Bear in mind these are utf8 strings and need to be handled as such
Archived author: <o> • Posted: 2022-11-02T10:05:38.495000+00:00
Original source
depends a little on what exactly you need to change. if you need to tweak the settings of an existing animation you'd need to work on the animation table itself, but if you just want to swap two very similar animations you can do that in the animation lookup table
Archived author: <o> • Posted: 2022-11-02T10:06:49.257000+00:00
Original source
if all you're doing is binary processing, you shouldn't need to do anything special with utf8 strings, though you might need to check the mysql library handles it correctly
Archived author: Titi • Posted: 2022-11-02T10:07:43.389000+00:00
Original source
I definitely had some issues with bad string format originally when writing my exporter to SQL