Define protocol for game object interaction and add more possibilities #65

New issue

Open

opened 2017-01-09 19:03:53 +01:00 by nik · 2 comments

nik commented

2017-01-09 19:03:53 +01:00

(Migrated from edugit.org)

Right now, the protocol for game object interaction only allows doing one defined action and then get a message as reply from the game object.

This protocol should be better defined and fleshed out. For example, this would enable dialogs with NPCs by making it possible to add a set of reply buttons to messages, and so on.

Right now, the protocol for game object interaction only allows doing one defined action and then get a message as reply from the game object. This protocol should be better defined and fleshed out. For example, this would enable dialogs with NPCs by making it possible to add a set of reply buttons to messages, and so on.

nik commented

2017-02-28 13:59:53 +01:00

(Migrated from edugit.org)

The idea is the following:

When a game object method is called through the API, initialise an empty dictionary in Flask's global namespace g. This dictionary is filled with data framework methods - e.g., the say() method does not return, but only adds an entry to the dictionary. This dictionary is then later returned to the browser when the API call finishes.

This automatically allows adding data from may_* and others, as described in #84.

The idea is the following: When a game object method is called through the API, initialise an empty dictionary in Flask's global namespace `g`. This dictionary is filled with data framework methods - e.g., the `say()` method does not return, but only adds an entry to the dictionary. This dictionary is then later returned to the browser when the API call finishes. This automatically allows adding data from `may_*` and others, as described in #84.

eike commented

2017-04-20 17:10:12 +02:00

(Migrated from edugit.org)

Milestone changed to %9