Thank you for Linux/Mac support!) Could you please post it in corresponding thread so users could find it there?
Last edited:
colsaves - Updates
- Thread starter henryjfry
- Start date
You should look for 34 (0x34 == 52 dec). Or just use my enc_decode_sav.exe (save archive as smcol_sav_editor.exe) to convert your SAV to SAV.json format. The coods in SAV.json are in dec format [52, 42].
Bladrov
Warlord
Ok, thanks to your suggestion I had a closer look at your readme.txt, so I see now you included a utility to export those save files in a readable format, modify them, then reencode them. So here is an early save file (00) with a Sioux camp at 52,42 in a Broadleaf Forest, then in 03 it's moved to 51,42 onto another Broadleaf Forest square.
Last edited:
Bladrov
Warlord
Once this is all done, it might be handy to have a quick way to generate the map from the latest autosave--like something a user could double-click on and automatically get the latest autosaved map.
Hey, first time I've been back here in a while and I see some interesting developments have been made for decoding SAV files.
I was curious about your tool, does the SAV JSON decoding contain better/different information than colsaves produces?
Would you be interested in integrating the colsaves image output in some way?
Having a GUI with your JSON saved information displayed in nice tables and a panel containing the current SAV map image would be pretty handy.
Additionally there is more detail about the hex textures in the SAV file than is currently being decoded. So it only uses a limited selection of texture templates currently, I was hoping someone more able would be able to figure out how to interpret the remainder.
But I'd be more than happy for you to lift my fork into your tool if you felt like doing that.
I haven't looked at your tool much yet but it looks pretty handy. Nice one 👍
Hi henryjfry!
It's a bit different (not much actually). It outlines more data, maps data for example (in compact text format). I've also mapped some new data (warehouse exp level, artillery/ship 'damaged' flag and a bit more) myself. Though colsaves sometimes represents the data in more clear and compact format, i.e. "Gunsmith working as Fur trapper for 0 rounds on tile NW". My SAV.JSON format is not so laconic. It follows the original SAV data sequence.
The main things about SAV.JSON format are:
1. It is reversible: with enc_decode_sav.py you can decode SAV file to SAV.JSON, modify it (as a text file) and encode back to SAV.
2. Its structure is not bound to python code. It's fully outlined in smcol_sav_struct.json. You can modify this file and receive different SAV.JSON representations without altering the enc_decode_sav.py code. Perfect for studying unexplored SAV regions.
Yes, I think of it. But I suppose simple image generation is not very handy. It's better to have an interactive window. To be able to click on an indian settlement on the map and receive more detailed info about it for example.
Honestly I don't think nice tables for text data are very useful right now. Text data is relatively clear in SAV.JSON. But talking about map panel - yes, it would be great to have.
I'm not sure I quite understand what do you mean by "hex textures" and "texture templates". Are you talking about unexplored (unmapped) sections of SAV file format? If so, there are some. One of my motivations to create SAV encoder/decoder was the make the study of SAV format more handy: you save your game, then convert it to SAV.JSON, perform some action in the game, save again and convert to other SAV.JSON, and then compare these SAV.JSON files to see what has changed. Or edit SAV.JSON file as text, convert back to SAV, load this SAV and see what happened in the game.
I've made some small "SAV exploration" advances myself (mentioned it already). Also the original viceroy project has recently awakened from sleep and mapped the trade routes data. I will add it to smcol_sav_struct.json.
But the most interesting things for me right now are 1) indian villages teaching speciality mapping and 2) prime resources mapping. I've experimented with teaching spec a bit, but with no result. The only conclusion I have right now is it somehow depends on surronding tiles types.
Prime resources are placed according to some pseudo-random pattern (see this thread), but its formula and seed is still unknown.
I'm ready to collaborate. But honestly I don't think it is any reasonable with colsaves project in its current form. We need a new application with interactive GUI, not a simple image generator.
Thanks mate)
It's a bit different (not much actually). It outlines more data, maps data for example (in compact text format). I've also mapped some new data (warehouse exp level, artillery/ship 'damaged' flag and a bit more) myself. Though colsaves sometimes represents the data in more clear and compact format, i.e. "Gunsmith working as Fur trapper for 0 rounds on tile NW". My SAV.JSON format is not so laconic. It follows the original SAV data sequence.
The main things about SAV.JSON format are:
1. It is reversible: with enc_decode_sav.py you can decode SAV file to SAV.JSON, modify it (as a text file) and encode back to SAV.
2. Its structure is not bound to python code. It's fully outlined in smcol_sav_struct.json. You can modify this file and receive different SAV.JSON representations without altering the enc_decode_sav.py code. Perfect for studying unexplored SAV regions.
Yes, I think of it. But I suppose simple image generation is not very handy. It's better to have an interactive window. To be able to click on an indian settlement on the map and receive more detailed info about it for example.
Honestly I don't think nice tables for text data are very useful right now. Text data is relatively clear in SAV.JSON. But talking about map panel - yes, it would be great to have.
I'm not sure I quite understand what do you mean by "hex textures" and "texture templates". Are you talking about unexplored (unmapped) sections of SAV file format? If so, there are some. One of my motivations to create SAV encoder/decoder was the make the study of SAV format more handy: you save your game, then convert it to SAV.JSON, perform some action in the game, save again and convert to other SAV.JSON, and then compare these SAV.JSON files to see what has changed. Or edit SAV.JSON file as text, convert back to SAV, load this SAV and see what happened in the game.
I've made some small "SAV exploration" advances myself (mentioned it already). Also the original viceroy project has recently awakened from sleep and mapped the trade routes data. I will add it to smcol_sav_struct.json.
But the most interesting things for me right now are 1) indian villages teaching speciality mapping and 2) prime resources mapping. I've experimented with teaching spec a bit, but with no result. The only conclusion I have right now is it somehow depends on surronding tiles types.
Prime resources are placed according to some pseudo-random pattern (see this thread), but its formula and seed is still unknown.
I'm ready to collaborate. But honestly I don't think it is any reasonable with colsaves project in its current form. We need a new application with interactive GUI, not a simple image generator.
Thanks mate)
Last edited:
AyCe
Warlord
- Joined
- Mar 3, 2019
- Messages
- 108
I could build that, if you people need help. Any suggestions for specific features and things?
Bladrov
Warlord
A utility with an interactive GUI would be like a dream come true!
Similar threads
