Skip to content
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.

Specification of SystemMessageAgent system #32

Closed
KeyboardInterrupt opened this issue May 9, 2018 · 3 comments
Closed

Specification of SystemMessageAgent system #32

KeyboardInterrupt opened this issue May 9, 2018 · 3 comments
Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested

Comments

@KeyboardInterrupt
Copy link
Member

Scope of this issue is to internally discuss how SMA's could be implemented, what they should be used for and what they should not be used for.

I think we will eventually need another Agent type for System/Albianwarp Messages, like:

  • Errors
  • Update Notifications
  • Dialog Boxes (for user feedback)
    • Yes/No

SMA's are probably only exchanged between the Client and the game, and the Server itself, they are not sent from one Player to another. (Thats what RTDMA's and regular DMA's are for)

@KeyboardInterrupt KeyboardInterrupt created this issue from a note in AlbianWarp (short term BETA roadmap) May 9, 2018
@KeyboardInterrupt KeyboardInterrupt added enhancement New feature or request help wanted Extra attention is needed question Further information is requested labels May 9, 2018
@Amaikokonut
Copy link
Member

Since one-way messages from the client to the engine are generally faster to just mesg-writ in, I think of SMAs as being used mostly by the engine to ask the client/server to do something or to let them know something. Things like:

  • I clicked the button to go offline, so please stop sending/recieving DMAs/creatures/etc and wait until I ask to go online again.
  • I clicked the button to go online, so please resume those things
  • I need to know how long the server has been up
  • I need to know if there are any creatures still pending upload
  • Here is the answer to a question you asked me (for dialogue boxes that would be mesg-writ'd in)
    etc

@Amaikokonut
Copy link
Member

Hmm, this could also be used to let the client know when there are problems warping in or out certain creatures due to them already existing on disk, so the client can move those creatures into a "duplicates" subfolder or something.

@KeyboardInterrupt KeyboardInterrupt moved this from short term BETA roadmap to Backlog in AlbianWarp May 24, 2018
@KeyboardInterrupt KeyboardInterrupt moved this from Backlog to Made Obsolete by ReBabel in AlbianWarp Apr 1, 2020
@KeyboardInterrupt
Copy link
Member Author

This is made obsolete by the Switch to ReBabel

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants