Server Help :: View topic - couple suggestions

Server Help

ASSS Questions - couple suggestions

CypherJF - Thu Aug 19, 2004 7:41 pm
Post subject: couple suggestions

1.) A way to determine if a message is from a macro, so the client can ignore it like Continuum.

2.) A way to determine if a sound byte is attached to the message.

That's it for now, I think..

Dr Brain - Thu Aug 19, 2004 11:11 pm
Post subject:

I agree with those two additions.

Oh, another nice addition would be the addition of a client string to the login sequence. Nothing would be done with it because it could be faked effortlessly, but it would come in handy every now and then in /?info.

D1st0rt - Fri Aug 20, 2004 10:49 am
Post subject:

I'd like the ability to send sound messages

CypherJF - Sat Aug 21, 2004 12:22 am
Post subject:

Another request, is a way to access the new's file; but I'm not to sure how that'd work efficientially; also to stop people from spaming requests to download news they already received...

Grelminar - Sat Aug 21, 2004 4:27 am
Post subject:

I'd like to point out that the document describing the chat protocol is called "simple-chat.txt". I wrote it to be simple, and I want to keep it simple. The spec should be no more than a page long, and someone should be able to write the base of a new client in a day. And it should be easy to use "manually", over just telnet.

So stuff that involves any more state on the client side, or message types other than single lines (like news download) is definitely out. Go visit a web site for that.

I think sounds are also unnecessary for basic chatting, which is all this is intended for.

I like the client version string idea, now that there's more than two clients. I added that to version 1.5 of the spec. I also added a PUBM type for pub chat macros, although I'm not so happy about it. New version. Support for this stuff is in the cvs version of asss, but may not be running on the test server when you read this.

CypherJF - Sat Aug 21, 2004 4:49 am
Post subject:

I am also thinking there should be a way to poll the server to see what chatnet version it's currently running chatnet wise; so the client can adapt accordingly.

What kind of errors would occur if a player used the new chatnet commands on old server builds?

Multiple lines wouldn't be an issue if you base64 it

but fine I wont push that idea..

Sounds could easily be added, and those "simple" chat clients can simply "ignore" the one extra field stating the number of the sound.. ya know?
...

And what don't you like about the public macro command?

Anonymous - Mon Aug 23, 2004 9:22 am
Post subject:

CypherJF wrote:

Sounds could easily be added, and those "simple" chat clients can simply "ignore" the one extra field stating the number of the sound.. ya know?

You would have to add another message type to keep this backwards compatible.

CypherJF wrote:

I am also thinking there should be a way to poll the server to see what chatnet version it's currently running chatnet wise; so the client can adapt accordingly.

If this was done, then you can write your own complex-chat.txt and server module to handle the new message types.

CypherJF wrote:

Another request, is a way to access the new's file

I think one way to go about this is to make a module that prints the news.txt line by line to you as arena messages when you enter a certain arena. You could make the arena spec only and disallow all c2s chat.

CypherJF - Mon Aug 23, 2004 2:35 pm
Post subject:

See ya'll know what. I would modify ASSS if there was an official up to date Windows build; Catid's was built w/ .NET which I refuse to re-install; since well it doesn't run to well on my machine; also, brain's and explody's version is simply way to old. Until then, all I can do it recommend things. So please no more "you can simply add a module...".
--
That'd work; but there would be no way to know when the news file was done loading; to transfer them to the arena they wanted. :/ it's not a big deal; just was an idea.

Quote:

I am also thinking there should be a way to poll the server to see what chatnet version it's currently running chatnet wise; so the client can adapt accordingly.

C2S-> VERSION
S2C-> VERSION:<version string info>

Or even an arena message:
:VERSION <string info>

Although, any mod could simply just do an arena message and the client wouldn't be able to distinguish the two. I guess it's not a big deal; maybe it should be appened into the server ?version command. :/

Anonymous - Mon Aug 23, 2004 3:45 pm
Post subject:

-Smong- wrote:

Another way is to make a module that sends the news.txt line by line as a priv message from a player called '~news', then in ccc you can do ?mkwin priv ~news so it all goes in there. You could use ppdata so they only get sent the news file once per login, or until the news file changes.

CypherJF - Mon Aug 23, 2004 5:13 pm
Post subject:

soundin good

Cyan~Fire - Mon Aug 23, 2004 5:49 pm
Post subject:

Smong wrote:

You would have to add another message type to keep this backwards compatible.

You could add another field like you were talking about earlier.

CypherJF - Mon Aug 23, 2004 6:22 pm
Post subject:

Or simply append a specific character sequence to ends of messages for sound bytes?

Dr Brain - Mon Aug 23, 2004 8:20 pm
Post subject:

It is possible for me in a few weeks to make another windows setup. They aren't exactly hard to make. Just a little knowlege and some moving of files.

If you want it done, come asking in the zone sometime in september. But remember to ask again and again if I don't do it.

Anonymous - Tue Aug 24, 2004 12:07 pm
Post subject:

Cyan~Fire wrote:

You could add another field like you were talking about earlier.

Looking at MSG:PUB:name:msg I can't see how you can add another field in there and keep it backwards compatible. I suppose you could send something like SND:sound right before MSG:PUB:name:msg and have the server cache the sound, then destroy it after forwarding the pub message on.

Cyan~Fire - Tue Aug 24, 2004 5:12 pm
Post subject:

But a well-designed client should really not care whatever other fields there are. I know the one I was making doesn't.

CypherJF - Tue Aug 24, 2004 5:37 pm
Post subject:

There would be no way to determine the amount of arguments; ie:

MSG:PUB:sound:msg that might contain a :
vs
MSG:PUB:sound msg that might contain a :

Being there are only 3 known published clients, this is the time to modify such things.. :-/ but I think grel has it set in his mind he won't implement such a thing, so really don't worry about it...

All one can do is make a complex-chat protocol; and work from there I guess. :/

Cyan~Fire - Tue Aug 24, 2004 10:55 pm
Post subject:

Oh frick I see the problem now. Hmm that's a toughie.

CypherJF - Wed Aug 25, 2004 12:19 am
Post subject:

Indeed...