Revision as of 06:25, 11 May 2012

Software

Client

• Branan's PlasmaClient is very WIP.
  • Currently supports linking though StartUp to Relto.
  • Has basic rendering and physics interactions.

Server

• Zrax has DirtSand, which is functioning at a basic (but very impressive) level at this point.
• Dustin has one, which I haven't tested and can't comment on yet.

PyPRP2

• Theoretically supports MOUL format. Should be verified and expanded on.
  • What about the PhysX binary blob? Ignore because Branan's client won't read it anyway?
    • That depends entirely on whether supporting Cyan's MOUL client is a design goal... which will probably depend on how communicative cyan becomes in the future.
• What else does this need on top of current PyPRP to be a solid tool?
  • GUI access to all, or at last the most often used, features? Seems to be the PyPRP2 path anyway

File Server

• Where will we store age files? How will the server distribute them?

Assets

It should be possible to create enough fan content to not have to include many Cyan assets. The big issue will be the global data. See below.

• The KI is special. It's deeply integrated into the game, so we have to do *something* with it. Re-implementing the old Choru ki has been floated.

Global Data

• CustomAvatars wouldn't be necessary on an all-fan-asset shard (except for any of our own, of course)
• GlobalAnimations has some things referenced in source code, much of it is only in assets (but those anims are useful for common things)
• GlobalAvatars we're probably stuck with, unless we want to re-do all the necessary global anims in addition to creating new avatars
• GlobalClothing the only thing that should be required here is the default items. Everything else could likely be replaced.
• GlobalMarkers is used for marker hunts. We could change the sounds and pictures stored here to customize markers. It's a small thing, though.

Special Ages

Startup

Tweek once designed a new Startup GUI. Perhaps it should be implemented for this?

AvatarCustomization

This is absolutely necessary, but I'm not sure whether we should just use Cyan's or write a new one

Personal

there are references in the actual code to 'Personal', so we have to have *something*. Whether its Relto or a fan creation? who knows.

Documentation

Python Files

• There are lots of x*.py files to implement common features. They should be doc'd with the correct parameters in a way artists can easily understand.
• On the note of x*.py, it may be worth it to replace some of them with versions that do cleaner things (like vault SDL instead of gameserver)

PyPRP2

Community and Sustainability

Donations

• Might be warranted/needed at some point

Information Sharing

• Should be much more open than Cyan. This seems to be our general nature anyway, so shouldn't be hard ;)