Wow! That's a lot to process.
So I've got it. A HashTable has to have a KEY that is a string, but it doesn't matter whether the value is a string or integer. Thanks for the lucid explanation.
Your example is fantastic. I'd never actually considered storing multiple levels within a map. I think I will probably use that idea eventually, but it's going to wait until I finish the basic version of this (random map generation would be something I'd love to put in later too.)
I have one concern. One of the things I've been quite happy with in this project is the possibility of making a map as big as 1000x1000. I once tried storing all of the paths to texture files in a global variable, and it crashed construct after about 40 of them (they were pretty convoluted to be fair c:\users\documents\dropbox\construct projects... etc..) Anyways, I can't find anything on a hard limit for global variables, would you happen to know what it is?
In the meantime this is much simpler than the method I was using, which took me two new files to figure out and a bunch of messy notes on a pad of paper!
and don't worry, I didn't take offense. Just seems like a lot of work helping out everyone, and I'm eager to be able to do the same.