Discussion in '"Graveyard"' started by Nestharus, Apr 4, 2011.
gy this please
Great stuff, well explained.
Wish I had the time to help, but this tut does the system good justice. ~Approved.
if only save load can be made in GUI
You can make this stuff GUI too, it'd just be insane ;D.
If you read the tut, you understand that a lot of it is just math. If you use the BigInt lib, you can make your own save/load system pretty easily in GUI, but Encoder is as good as it gets, so it's better to make a GUI interface using Encoder =).
if you are a very nice guy, make me 1 system , no just kidding
( i hope you make 1 some time)
An interface is map specific, hence why I haven't done one.
which part do you think is true for you?
larned a lot
Update information on Encoder.create to reflect Encoder 184.108.40.206
Wow man, this is amazing i didn't really know that this kind of stuff's exist. ^_^
You got me interested, surely i will have hard times study this shitload of information.
I mean i understand a lot of things here but i think i read too much info at once.
This is awesome.
Updated to reflect Encoder 3
is there a gui version?
there is not
I do not understanddd
What don't you understand? : )
every thing you write in this thread...
So you don't even get the unit type ids, like 'Hpal'?
Updated to edition 2. This goes over the latest in save/load techniques and explains things better in the compression chapters.
That's quite a good post. Good thing you actually explain the things done by the libraries rather then "Use the library to do X", which is what you usually do.
Separate names with a comma.