As I've mentioned already, I am writing an open-source QuestNet client. Question: Can anyone think of a good name for my client? So far I've got these for plans:
1. Basic style is similar to Quest with 'in' and 'out' buttons added. Also the viewscreen is split horizontally to add a map screen.
2. New script commands are added for the map system (detailed partially below)
3. A Save system is implemented, allowing a user who has admin access to that game to send a player (via my client) to an inaccessible room that will log all variables, etc. needed to save the game.
4. A user database will be added so a user using a registered name must login. All the character's stats/items/variables etc. will be restored upon login.
5. Logging all input/output of the player (or entire server under ADMIN)

Script commands include:
newmap - displays a map in the client
players - displays all players in that map (in client)

Here's a sample idea for the syntax:

!!S1aY3R!Command!Start!!
newmap {
H(1-PK,2-N,3-N,4-PK)
V(2-N,5-PK,6-N)
V(7-N,8-PK,3-N)
}
players {
A(4-PK,3-N)
N(7-N)
}
!!S1aY3R!Command!End!!

This would create a map like this:
MAPSTART
(7RM)
|
(8PK)
|
(1PK)--(2RM)--(3RM)--(4PK)
|
(5PK)
|
(6RM)
MAPEND
Admin Players will be on squares 4-PK and 3-N
A Normal Player will be on square 7-N

There are also Superusers and Powerful Users (S/P)

This will all be printed on the map screen of the client with brief symbols of the character types flashing off/on over the square. PK Squares will be red. (I sorta stole your idea, Ste, but I implemented it for YOUR use if you want it, since you said your game uses PK squares.

Syntax won't be too hard to figure out. I'll include a help file when finished. Since I can't make an actual command (or can you?) I will have to make a custom msg that is intercepted by the client (game checks to see if the client is mine first) instead of being displayed by the player (soooo simple.. use the win32 message loop)

Any ideas you may have will be welcome. Please give me any ideas you have. I have the skeleton of the app and some basic features. I should have a very basic client working in a week or so. It takes time with one person 8)

I won't be around much for the next few weeks. We have Christmas holidays so I won't have access to school computers. I rarely use the internet at home (slooooooooooooow dialup)

First:
How are you going to add commands when you're building a CLIENT??

Second:
You can't have some of those features yet...

.... You mean you're gonna be building a server??

..... Doesn't that mean you'll have to basically build up something that can use ASL? Again, as I said to Ste - if you add your own code and stuff then you'll have to call the language itself something other than ASL (like DASL or CASL). Wouldn't it just be easier to code EVERYTHING in C/C++ and not use ASL at all.

What's the use of building something to understand ASL exactly (which will take a while) when you can just use raw C/C++ and get away from all this parsing rubbish (except for certain things of course)... Plus every new addition Alex comes up with YOU would have to copy while he can just ignore anything you do.

If I were to actually create an online text game or whatever I'd personally build everything myself... No offense Alex, but ASL *WOULD* be a bother for me. It's quick, simple and easy to do a "first-sketch" IMO, giving you the power to give an impression of what the final product will be.

me and TNO are coding a client, not a server. the server (QuestNet) handles all the ASL, the client just sends commands to the server, so we wont be needing to add anything to do with ASL apart from getting the client to handle stuff like... getting it to show colours from the |cr etc. commands, and stuff like that. it wont be difficult at all (although it's being a pain in the ass right now, and wont seem to work). I have no idea whether TNO is continuing the project or not, but i guess you'll have to ask him. He's usually on the S:UK forums. http://www.squiggleuk.com/forums

S1aY3R said:

Syntax won't be too hard to figure out. I'll include a help file when finished. Since I can't make an actual command (or can you?) I will have to make a custom msg that is intercepted by the client (game checks to see if the client is mine first) instead of being displayed by the player (soooo simple.. use the win32 message loop)

No, CW, I'm making a client. The commands WILL work. The server will skip right over them since they are in the form of MSG strings. They are not actual commands like msg <> or anything. The !!S1aY3R!Command!Start!! will signify the beginning. I'll check on startup to see if the user is using my client. If they are, then these commands will be sent with text messages. My "winsock recv" script will check for the Command!Start and will translate everything after that until the Command!End into map code.
Also, I know for a fact that ALL of my features will work.

Then you aren't just building a client - you're building a client AND a game.... You're building the game to send stuff to your client and vice-versa....... Still, alot more easier to create your own system than to try and work around ASL.

Oh yeah - Ste;

To colour text using the rich text format textbox - you need to select the text THEN alter the colour. Same with size etc.

CW, I'M not building the game. I'll give a list of the commands with my client. If people want to implement this into THEIR game, they can. This will enable the map screen for my client. You'll have to check for the client (i think there's a function) and also clientversion before you use the commands in your game though. Most people won't bother, but I know that a few will. I'll have a simple QuestNet client ready in a couple days. It should be almost equivalent of Quest.

how far have you got with it? i can do some testing if you want, just give me a holla on MSN


seeing as Slayer has msn, and ITID can't act grown up enough to handle a link being posted on the forums i've edited it and deleted the link.