|
KaVir, I don't think you are getting their point. You are asking them to engage in some pretty significant game design regarding a feature that they do not feel would be very interesting or useful. They do not appear interested in investing the thought and analysis necessary to come up with an actual system for doing in text what you have done via ascii. To them, it would be a waste of a significant amount of time for no real benefit to them or their point.
It would be like asking someone with no interest in genetics to explain how they would go about creating a pet system that used Mendelian genetics to pass traits along various generations of bred pets. They don't need to know how to do it to decide whether or not they like YOUR method. The fact that either genetics or Mendelian genetics specifically did not interest them might preclude them from wanting to invest a lot of time figuring out how they would do it just to explain why they did not like your method.
Personally, I think your cloud/sky/map thing looks pretty neat and I can totally see the benefits of it. It does indeed convey a lot of information simply and neatly.
That said, there are many people who do not like that sort of thing, and would prefer the information to be conveyed purely via text. I imagine it would be possible to do so, but perhaps you are right and no text implementation could even approach the utility of your ascii method. As it is not a feature I am currently programming (and personally, I'd probably go the ascii route myself) I am afraid I don't have the inclination to figure out a way to do it purely by text either. I hope you aren't disappointed.
Lastly, I wouldn't assume that just because someone doesn't like big ascii maps that they only want stock muds, stock code, or simple, stock weather. Your responses towards those who did not like your ascii map struck me as very presumptuous and defensive.
|