I know I would pay good money for something tailored specifically towards my specialization, though that is a stretch. My biggest thing is filtering useless data out of the output and showing my relevant data so I actually know what is going on before I'm 30 seconds into getting jumped by 3 people. I suppose that is really more of a system thing than client issue. Mini-windows are pretty cool in concept--haven't tried them in application yet. Can't see myself using too many buttons personally since I tend to stray from using my mouse at all unless I happen to be forging and surfing the net at the same time. I like the only Lusty idea, though admittedly you will earn more money if you have a broader market; however, I look at it in the way that it will probably be tremendously better if it is discriminative in purpose. Similar to Nexus <--though that could obviously use a vast overhaul. I do use Nick's Chat Redirector format to fake mini-windows to send aethers, wounds simple, and assess to separate world windows, which are adjusted for size appropriately. Looking over the functions on the site you've got listed, the DoAfter or a similar function would be an important addition to make, in my limited opinion. I take it, it will be adopting the majority of the functions from MUSH in that manner? Also, when you talk about the GUI do you mean something that is concrete (again, like Nexus) or do you mean that it will have the ability to use GUIs under a certain set of guidelines that you determine? Hope this has been somewhat useful or at least tremendously confusing.

I've been putting my energy lately into a new MUSHclient system, now that Miniwindows make the GUI stuff possible (and interesting). My own client has one or two really nifty features that I kinda wish MUSHclient had, like hierarchical grouping and ATCP support, but they can be added to MUSHclient at a later time, if I decide I really need them.

I was going to make it only for Lusternia, simply because I wanted to hardcode the GUI for speed and ease of installation. I know that making a general client would make more money in the long term, though I was planning to sell it for a few credits and not charge actual cash for anything.

Make Treant not slow as molasses before you start new projects or give me my credits back!

When I switched projects, I said I'd gladly refund anyone who paid for it! Just send Iasmos a message in the game and your contract is over, fully refunded. (Note: if more than a few people want refunds, I'll have to get more credits because I bound most of them for the auctions.)

Bump:

Im new to lusternia and muds by a few months and ive yet to find a cleint that suits me, ive never coded or build anything and have no programs, BUT, i would like to build my own custom client or help someone who can code build or make one better, one sorta like the nexus with direction arrows, programable tradeskill buttons for commands for the tradeskill ,trigger ,alias and macros, stat and experiences bars and instead of the map being drawn in main window one that stays and updates itself in the corner of the screen, and one faster conection and nexus or certain clients for it doesnt red out and loose or go very slow connection when moving around or staying still , i want it to be custom to lusternia and basicall a ui like a a grphics game but still text based, if anyone can put my idea's together and see where im going could you repost and maybe get together and start working on something?

Thanks

Elrick

My ideal client would have the following key features: (in no particular order)

1. Events
2. speed
3. Color coded code completion and code hinting. (Why should I have to remember the correct spelling of the function I made? WHY??)
4. Easy to make gui.
5. "tools" like "highlight text and create a color/alarm/sub trigger in one easy button", (and other commonly made triggers)
6. Code snippets that can be stored, like "cure code", "affliction code" etc, so I can just hit cntrl+b and select one of my premade code snippets that I might use alot.
7. Well designed use of window space.
8. easy means to share code with others and import into my system.

My client code has been sitting on my drive for a couple months with no activity because, as I said, I'm building a MUSHclient combat system instead.

However, you folks may wish to check out Mudlet for your gaming needs. Now is a good time to not only see what it can and will do but also to recommend the features you want most in a client! It's shaping up to be a very good piece of software.