This is what it does (but with a few more details):
- Count strings that are read in StarCraft (excluding never trigger strings and disabled triggers.)
- Load strings.
- If melee, remove non-p12 resources/critters and non-p12 unitsprites.
- ONLY write sections SC reads (depending on Melee or UMS modes.)
- Recycle strings.
- Write string sections with new indeces.
- Ignore Never trigger blocks.
- Create new MPQ and load all files in the map (with inputted compression for WAVs.)
- Compact MPQ.

WTF. I replied and couldn't see my reply, so I replied again and then both appeared.

Probably because you needed to clear your cache or wait a moment if the forum database is going slow or something.

I use F5.

My refresh cache button is CTRL+F5 (and I got Firefox). Does just F5 work? Also, it couldn't been just slow-time for the database.

F5 reloads the page, Ctrl+F5 reloads everything. I think it had to do with the pages.

Make sure you create the MPQ with a smaller table size.

I already have. If you compress a map that ONLY has the CHK, you can't see it at all in WinMPQ.

Perhaps I should completely remake SECompress(being incomplete and all).

Only thing is the UMS portion would take some time to code properly.

No, help me make tiny map tinier.

Did you resize the STR section? You don't need the table to be 1024 strings large.

I'm just trying to help so don't take anything I say negatively.

Yes, I did resize the table. Do you want detailed things that I do?
I could just crack open an OSMap-compressed map and look at the differences. Maybe when I get bored I'll do that... Compression is just not my friend.

Yes please.

If I get remotivated I'll add more and make the compressed data cleaner... that'd probably help it compress further too.
lol, are you going to try to optimize OSM2's compression or something? What sort of deeds do you plan to do? : P ... Apparently I'm not very trusting, even though I mean this as somewhat of a joke... I hope you realize that if I was really worried I'd probably not put any detail or I'd put a lot less.
Str section is just a more-than-normal retarded tbl file... Not a hard format. I have no idea why editors have so many issues with str section... Because of issues editors have I thought TinyMap'd have the most trouble with str, when infact the opposite was true (other than sections that are static data, of course.)

Post has been edited 8 time(s), last time on Aug 3 2008, 6:50 am by FaRTy1billion.

Some of these methods may be theoretical so test them pleeease!

Checklist:
Remove TRIG for melee? - Already does.
Remove MBRF for melee? - Already does.

Remove UPGS for Brood War scenario? - Already does.
Remove UPGx for Vanilla scenario? - Already does.

Remove UPGR for Brood War scenario? - Already does.
Remove PUPx for Vanilla scenario? - Already does.

Remove PTEC for Brood War scenario? - Already does.
Remove PTEx for Vanilla scenario? - Already does.

Remove TECS for Brood War scenario? - Already does.
Remove TECx for Vanilla scenario? - Already does.

Remove UNIS for Brood War scenario? - Already does.
Remove UNIx for Vanilla scenario? - Already does.

Null UNIS/UNIx for melee? - Already removes.
Null TECS/TECx for melee? - Already removes.
Null PTEC/PTEx for melee? - Already removes.
Null UPGR/PUPx for melee? - Already removes.
Null UPGS/UPGx for melee? - Already removes.

Delete unowned triggers? - I could do that...
Null unused sections of triggers? - Part of me being lazy. I thought of that. CHK already compresses really well, don't know how necessary it would be.
Null players who cannot own triggers from trigger ownership? - Oh? Why not just remove?
Delete improper conditions/actions? - TrigPlug will explode. Unless strings of 0s compress better than anything else, this would be mostly useless.

Remove hyper triggers if more than 4? Lol OSMAP doesn't even do this. - I don't even use that method of hts. ><

Null SIDE for Melee? - Does to some degree.

Remove TYPE for vanilla? - I don't even write type.


Melee only has like 12 sections after TinyMap does its thing.

MPQ compresses nulls better than anything I think.

Don't forget to remove MBRF or TRIG if there's nothing in them for UMS.

It doesn't compress it better than nothing!

Eh. I was too lazy. I could write a list of things to add if I feel like it...
I'd like to avoid rewriting the CHK compression function. There is nothing I hate more than rewriting a long function (And I've already done it for TinyMap.. maybe even twice. My original string recycling took like 5 minutes.)

As I said/implied in my first post, there is a lot more I could do to make this much better. I just got lazy...

Wait, do you mean rewrite as opposed to edit?

I'm just trying to help ;p

I mean if I have to change the way I handle compressing the CHK, it will really bother me. If it is something that I can just throw in the middle of the function it is better... but then it looks messy and isn't optimized well. I guess if I work with sections on the individual scale that'd be ok... TRIG is annoying to deal with because it is too much crammed around... MBRF is better because it doesn't have NEVER or conditions at all (other than that one..)