OIM20
Well-Known Member
Proposal: Have an automated sweep that disbands Fellowships with open enrollment/automatic join whose archmages have become inactive.
While this action would occur naturally once the AM's inactive city is deleted, before that happens, there could be months (years?) that pass where players
Pros:
1) Time to write new code.
The message could read something like:
While this action would occur naturally once the AM's inactive city is deleted, before that happens, there could be months (years?) that pass where players
- join the game,
- are directed by the game to the inactive FS,
- join the inactive FS,
- become jaded and think the game is dead because their FS is inactive,
- and ultimately quit the game, thus losing Inno both players and money.
- This would only affect Fellowships with automatic join selected. (The button says "Join" instead of "Apply". You don't see this when you're in an FS, only when you're looking at an overview page and you're not in one. So I don't have a screen of that to show you.)
- This would only affect Fellowships whose AMs have been added to the city-nuke list but whose listing is more than 7 days from being processed by the code.
- A message should be generated automatically by the system when the FS is added to the 'to be disbanded' queue to be sent to any member of the FS not on the city-nuke list, which should allow 1 week for players to find new homes. (If someone isn't logging in during an entire 7-day period, they likely aren't looking for a very active FS, and not being part of a defunct FS isn't going to affect them either.)
Example: The Grove
Archmage Ular Thornoak has not had a change in their score since 19 July 2021.
Because their FS has been allowed to be recommended to new players, when King Alford joined the game on 19 Sep 2021,
there was nothing stopping them from joining "The Grove". However, Flame of Elysium was their first FS, and its AM, R Sharpe, has had no change in score since 11 July 2021.
Because King Alford has had the misfortune of joining two defunct Fellowships, they likely have the impression that this is simply how Elvenar is. While we know this game is not a bunch of dead cities, newer players do not know that when they find themselves part of a defunct FS, especially when it is one that was recommended to them by the game itself.
Archmage Ular Thornoak has not had a change in their score since 19 July 2021.
Because their FS has been allowed to be recommended to new players, when King Alford joined the game on 19 Sep 2021,
there was nothing stopping them from joining "The Grove". However, Flame of Elysium was their first FS, and its AM, R Sharpe, has had no change in score since 11 July 2021.
Because King Alford has had the misfortune of joining two defunct Fellowships, they likely have the impression that this is simply how Elvenar is. While we know this game is not a bunch of dead cities, newer players do not know that when they find themselves part of a defunct FS, especially when it is one that was recommended to them by the game itself.
Pros:
- Player Retention: to prevent players new to the game from becoming immediately jaded and quitting after joining an FS whose AM has left the game but left their FS with open enrollment. These players don't know how to tell if an FS is active or not, and the game makes no differentiation when it suggests Fellowships to new players for them to join. (Also would be nice if that were fixed. See the possible implementation message below.)
- Increased Activity: by keeping players from joining defunct Fellowships and steering them towards active ones (by default as the others will not exist), all players in the active FS are more likely to spend increased time in the game building their cities since they will be able to trade more for the goods they need to be able to do so.
- Creating a process for disbanding inactive Fellowships establishes a protocol which will allow developers to clean up the database files. And the less unused data being stored on a server, the less chance the server develops lag because of broad queries being forced to go through that old data. This could possibly result in fewer "stream error" incidents.
1) Time to write new code.
- The city-nuke list code could possibly be tweaked to generate a similar FS-nuke list.
The message could read something like:
Dear {player.name},
We hope you have been enjoying building and growing your city in Elvenar. We see that you're in chapter {player.chapter} - congratulations!
We want to help you grow your city even better, and to do that, we are letting you know that the Fellowship you're in, {player.FS}, is scheduled to be disbanded on {player.FS.disband-schedule} due to the inactivity of its founding member. Fellowships are intended to help you by providing trading partners and enabling you to participate in weekly activities (the Tournament and the Spire), as well as the Fellowship Adventure which helps many players obtain artefacts for the evolving event buildings that they missed during the event. You aren't currently getting that opportunity, and we're taking this step to change that.
But despair not! Please log in to your city to be provided a list of potential new Fellowships for you to join. We also recommend that you look in our forum for your world, {player.world}, here: [link to subforum for player's world - e.g. Arendyll] to browse listings for Fellowships currently looking for new members.
We look forward to seeing your city grow in Elvenar, {player.name}!
Sincerely,
Your Elvenar Development Team at InnoGames
- Obviously there would need to be a period at the onset of such a feature that would warn members of the affected FS that it was about to be disbanded. But as time moves on, the period between sending such a message and disbanding the FS should, I think, be 7 days. That gives them time no matter where they fall in the Spire/Tourney cycle to find a new group to join before the next cycle begins.
Something like that. If I've been unclear somewhere in there, please tell me. My English isn't always the best (hence why I try to read carefully, but even I mess up sometimes).A new feature to keep players from joining inactive or defunct Fellowships is being enacted. This feature utilizes the code already in place to find inactive players. If the inactive player is an AM of an FS which allows players to "Join" rather than "Apply", once they have been added to the list for possible deletion, several things will happen.
1) The FS will be changed to "Apply".
2) The FS will be removed from the recommended FS rotation so that new players are guided towards active Fellowships.
3) The AM will be sent an external e-mail to let them know their FS will be disbanded (time frame to be included in message).
4) Messages will be sent via external e-mail to notify any members of the FS who are still active that it is going to be disbanded due to the AM no longer playing the game.
If none of the above applies to your AM, then this feature will not affect you directly. If you are in a leadership position for an FS, this may result in your FS receiving more applications than you are accustomed to.