Peter Mardahl wrote: > > I far prefer the xpms to the png images. I think they look > a lot better. I think forcing the use of pngs by default > would do more harm at this point than good. Its a mix. The current png images are based on the 32x32 xpm's that david sundqvist did a while back. For those that were actually done for 32x32, they look better, for those not, they look worse. In reality, for many images, it probably would have made more sense to just transer the 24x24 without expansion - for things like items, this would work fine. For things like background, that obviously was not an option. > More productive, I think, would be more of a move of image from > server to client side. I know this is difficult, but it would > allow someone to, say, create his own client which uses ASCII > characters for everything, or uses his own custom 128x128 uberimages. > > We could send the archetype name+ an int to ask for an image? How much > additional bandwidth/CPU would this require? Could we send the > archetype name once and assign an int for second requests of that image > during a single session? This would require a large bitmap > (NumImages bits) for each client. This can already be done - if you choose the image caching option, the server says 'image 50 is orc.111' for example. So a client could certainly have a complete set of images it uses of whatever size and format it finds convenient. The problem with that is that as new images are added to the server, the client has to be updated or the client still needs to be able to deal with whatever image format and size the server has. Or for a text only client, it would obviously have to have some idea what the different names mean (if you go nethack like, most of the monsters could just be represented by the first letter, but things like money and gems would require some more intelligent handling.