AW Messaging on the way

Life has been keeping ham5ter and I terribly busy, so I thought I would send out an update to let everyone know this! I have been going through the .cos files and assessing just how much we’re going to need to take out and/or modify. From doing this, it has come to my attention how woefully bad my interpreting of CAOS is. (It really isn’t that bad, it’s just far different to my eyes after staring at Python all day.)

Within the next few days I will be setting up a “live” development server, so that I can start testing a registration and login system for everybody. That is the server where I will be pushing updates to before I put them in the code repository, so that I can get some real testing done. This does not mean that there is a whole lot that you would visibly be able to see working, it would just be testing the basics so that we know our foundation is solid before moving forward.

For all you daring souls, this would be a perfect opportunity to help us do some testing. I cannot stress enough that things are not going to be terribly exciting after connecting: until messages are put in, all you will see in your game is the green light.

This is the current path I am thinking about going down:

  • Establish registration and login
  • Establish server-announce, so that the server can send messages to everybody that is logged in
  • Establish status messages, so players can update their statuses
  • Establish other messaging systems to pave the way for sending and receiving creatures.

I have chosen this path order because it would greatly help us test out sending and receiving information, without accidentally sending broken creatures to everybody. The last thing I would want to see right now is everything crash because a creature failed to send correctly.

What are your thoughts? As always, your ideas and suggestions are always welcomed (and encouraged)!

We have a brainstorming thread going over on Creatures Caves!