Great answer.
I meant quantum physics.

To add more about the quant, as I'm usually quite descriptive, a quant, in it's shortest form, is one unscaled texture pixel. A quant can be any unit of measurement you want. The measurement comparision depends on the type of game/project you're working on. If you're doing a shooter game, 1 quant = 1 inch would be a decent scaling. If you're doing an ant simulator where you try to build ant colonies, 1 quant might be 1 millimeter or so. If you're doing a project that involves travel between the planets, then one quant might equal 10 miles or even 100 miles. It all depends on what kind of project you're working on.

While building your levels, decide on a scaling and stick with it. If you started off with 1 quant being 1 inch then changed it to 1 quant being 1 centimeter, and built a model based on this, your model will end up being 2 1/2 times bigger than expected. Set a scale and stick with it (unless you want your game to take place in giant land or mini land where everything is gigantic or miniature compared to you). If you want something at an exact height, you can take out Windows calculator and type in some numbers to figure it out. If you use, for example, the 32 quants = 5 feet scaling, and if you wanted a human model being 5 feet 10.5 inches tall (70.5 inches), you'd need to make your model 37.6 quants tall. If you wanted an odd-shaped roof for a house measuring 256 by 1024 quants and 48 quants high, using the same scale, your roof would be 40 by 160 feet and 7.5 feet high.

In WED, at the closest zoom possible, each of the smaller squares represents 16 quants (provided you've left it at the default). The larger squares represent 128 quants. If you were to zoom out more, the original large squares become the small squares and another larger set of 1024 quants is divided. If you zoom out to the maximum, the large squares from the middle setting become the small squares (1024 quants) and the larger squares will then represent 8192 quants. A medium-sized level would be about 12000 by 12000 quants (from the top view; if your scaling was 16 quants = 1 foot, then your map would span 750 feet). You can make your levels as big or as small as you want. Blocks can only go out to 125,000 quants from the origin, but models, map entities, sprites, terrains, etc., can go out much further than that, up to 999,999.999 quants from the origin as far as I've heard.

While working with games, knowledge of mathematics (basic arithmatic mainly, but algebra, geometry, triginometry, and other fields of math are recommended) is helpful. Calculators come in handy for helping you out with the complicated stuff. When working with quants and real-life scaling, mathematics for conversions is key to proper scaling of your world.

I guess I didn't say any of that earlier

I just thought I'd point it out. I like giving details and the more I know about something, the more details I tend to give. It might be helpful, who knows.

If the Quant is a none set unit why does it come up so much when a size is needed.

IE
I keep falling through my floors. Some one ask How manny quants wide is it?

Course I assume they take 1 square to equale 1 quant.

[Quote]
1 quant == 1 pixel at 16 bit texture image
[/Quote]

Also, on WED's default settings, there are 16 Quants to a single square in WED.

Regards,
Ayrus

[Quote]
1 quant == 1 pixel at 16 bit texture image
[/Quote]

1 quant is also 1 pixel for a 32-bit image, an 8-bit image, etc. The number of bits does not change the size of the pixel or the quant .

The bit depth just tells how many bits to use to describe a single pixel's transparency. Usually, it's arranged like this:

8-bit: palettized - you choose your own palette but the same palette must be used throughout the entire level but a different palette can be used in a different level provided all objects use it.

16-bit: uses D3D - not recommended for fine or smooth textures and it usually won't come out as expected. Best with rough-looking textures.

24-bit: uses D3D - true color without alpha channel. Best with smooth-looking textures that 16-bit won't display correctly.

32-bit: uses D3D - true color with alpha channel. Use only if you need varying degrees of transparency from the alpha channel.

For the true color types, the first 8 bits are for red, the next 8 bits are for green, the third set of 8 bits is for blue and the final set of 8 bits is for alpha (transparency; the final group only if using TGA files with alpha).

The bit depth has no impact on the size of the quant and pixel, it only gives more options for color and/or transparency.