Thanks for that soja, it's exactly the kind of answer I was looking for.
It occurs to me that a lot of the integer values I'll be storing don't need to be 32 bit, most really only need 8 or 4 bits so I should be able to get more than one piece of data in a single Blitz integer and mask off what I don't need when I come to extract what I do need. I can also get away with using 8 bit integers instead of those 2 strings. This should keep RAM per map square down by getting rid of a good bit of redundancy.
Also, as about 65-70% of the map is open sea and requires no supporting data there's a massive saving to be made there, although I can't see a way of doing that with an array of types. Time to look into using a Bank instead I think.
How short are the numbers that PokeShort pokes?
It occurs to me that a lot of the integer values I'll be storing don't need to be 32 bit, most really only need 8 or 4 bits so I should be able to get more than one piece of data in a single Blitz integer and mask off what I don't need when I come to extract what I do need. I can also get away with using 8 bit integers instead of those 2 strings. This should keep RAM per map square down by getting rid of a good bit of redundancy.
Also, as about 65-70% of the map is open sea and requires no supporting data there's a massive saving to be made there, although I can't see a way of doing that with an array of types. Time to look into using a Bank instead I think.
How short are the numbers that PokeShort pokes?