Upvote for the Field Museum . It is one of the few I continuously go to anymore . The Shedd isn ' t even on that list . <| sep |> Just for reference , IIRC the highest you can place with a new account in league is gold 1 . <| sep |> rail attachment for ergonomic reasons <| sep |> Guys , please no spoilers ! I ' m spacing out my viewing to one a night . <| sep |> And they would be promptly fired . <| sep |> HE HANDLES CONTENT . I HANDLE SALT . <| sep |> Yes fully understood . You ' re actually helping to make my case for me . Yes I get it that those attributes are mapped into what an ASCII terminal can deliver . The problem is the ASCII aesthetic bitspace is exhausted . It has no room for growth . Now as per the example , your NH designer wants to add 5 more attributes all worthy and wanted . now what ? It is NOT the fault of NH that it is growing that is normal and expected and wanted , everybody likes that . Everybody likes that the source code has the attention of worthy devs after 10 years . It is NOT the fault of the ASCII aesthetics that have very limited capacity . These 2 things cannot remain married forever if the goal is that NH continue to grow . You said The server has two choices displaying the information to the user , or not displaying the information to the user . Nope . The server has a choice to send or not to send . But once sent , it has no say as to what the client does or does not do . This is part of what I ' ve been urging to rElronnd that you guys intentionally change some of the paradigm and get completely married to a serious client server setup . Doing this does NOT mean you must forsake all existing paradigms . But it will put you onto a healthy footing for growth beyond 80 x 24 x 1 ASCII . Changing the x 1 to xN seems like the most sane way forward . All the code that currently works with a single layer will still work with multiple layers right ? Take ALL of the code , inside the NH source , that is devoted to client presentation and remove it into a separate client app . Let the server be a server . Let the client be a client . Divorce yourself from all the varied kinds of historic interfaces and normalize client access over a single publicly defined interface i . e . VT 100 Z . Why do you care if binary data is sent in it ' s own VT 100 Z layer ? Why is the client obligated to show that data to the user ?