Registration of Quests and Events #4584

Open
opened 2023-05-24 00:26:16 +00:00 by niceride · 2 comments

Requesting an in-game kiosk (at Haven town hall?) where you can register your in-game Quest and/or Event, bound to a specific upcoming UTC time, and able to be seen in-game as a list of events and also with an in-game command to list such events.

Basic idea is to make it easier to properly register your event without the uncertainty and difficulty of having to decide whether to '/announce', or how to find out if there is an upcoming event to participate in.

Personally I'd like to host tours to Lucky Pastures and I'm sure the players that are hosting Miocene Tribe events would like some better workflow for making it known.

I would like there also to be a registry of attendance if you are hosting an event to record which players attended the whole duration, joined late, or left early, as a matter of historical records-keeping this would be entered by the responsible player(s). Previous such events could be listed with date and UTC time also the number of such participating players and the name of the hosting player(s).

We can re-use some in-game item for its metadata properties so that responsibility can be shared.

Requesting an in-game kiosk (at Haven town hall?) where you can register your in-game Quest and/or Event, bound to a specific upcoming UTC time, and able to be seen in-game as a list of events and also with an in-game command to list such events. Basic idea is to make it easier to properly register your event without the uncertainty and difficulty of having to decide whether to '/announce', or how to find out if there is an upcoming event to participate in. Personally I'd like to host tours to Lucky Pastures and I'm sure the players that are hosting Miocene Tribe events would like some better workflow for making it known. I would like there also to be a registry of attendance if you are hosting an event to record which players attended the whole duration, joined late, or left early, as a matter of historical records-keeping this would be entered by the responsible player(s). Previous such events could be listed with date and UTC time also the number of such participating players and the name of the hosting player(s). We can re-use some in-game item for its metadata properties so that responsibility can be shared.
flux added the
1. kind/enhancement
3. source/ingame
labels 2023-05-24 00:34:39 +00:00
Member

This seems to aim mostly at events (things that take place at a specific time, once or several times), while I'd say quests players can do whenever they feel up to. Quests need some way of promotion as well.

As Amanda already does some announcements, perhaps she can handle announcing other events as well? Or Buttercup? If he gets a pay rise?

A personal log which events the player took part in may also be intresting. But that's for the far future I'm afraid.

This seems to aim mostly at events (things that take place at a specific time, once or several times), while I'd say quests players can do whenever they feel up to. Quests need some way of promotion as well. As Amanda already does some announcements, perhaps she can handle announcing other events as well? Or Buttercup? If he gets a pay rise? A personal log which events the player took part in may also be intresting. But that's for the far future I'm afraid.

Until a final solution gets concieved for this request, I can propose that most of these requirements could be covered by using the billboards already implemented, possibly combined with /mail for the RSVP part.

Until a final solution gets concieved for this request, I can propose that most of these requirements could be covered by using the billboards already implemented, possibly combined with /mail for the RSVP part.
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/bugtracker#4584
No description provided.