Hi there,
This is not a complain about the policy of gem dropping on dungeon death, it’s bearable to some degree, especially since we are given the option to revive anyway.
I however found that it’s annoying to lose my gem over connection issue which I have no control over it.
Connection problem is a possible 2-way issue, fixing server stability doesn’t always fix the issue.
Therefore I offer the following idea of changes regarding death behavior:
#Current behavior:
Player die > Gem sprouting > prompt revive option
- player can choose normally between option.
- on connection issue or crash situation that prevent the player from choosing, they will be revived outside the dungeon after relog.
- note that when I relogged back in, there’s a small interval at which I still in the same spot as I was when I die, I even manage to retrieve back 1 or 2 gem before I was forced to tele outside the dungeon.
#Suggested change:
Player die > prompt revive option > Gem sprouts only after one of them is chosen.
- on connection error / crash situation, the player still spawned in his last spot, dead.
- I assume it’s feasible for the in-game system to detect that the player was dead, but hasn’t choose the options yet. thus prompting back the option, and only after this the gem starts sprouting, regardless the option.
I think this kind of fix doesn’t change that much process and I don’t see that it can be abused to the player’s advantage.
But anyone please enlighten me if there is any flaw concerning this idea.
I believe similar idea might have been thrown elsewhere,
Or maybe this idea is currently impossible to be implemented because of some code limitation.
There are in-game workaround to put the gem in storage to prevent losing it.
But I think this is still a problem, and I hope this will be solved too…
Wishing the best for this game and dev team .