Glorious Alpha Two Testers!
Alpha Two Phase II testing is currently taking place five days each week. More information about testing schedule can be found here
If you have Alpha Two, you can download the game launcher here, and we encourage you to join us on our Official Discord Server for the most up to date testing news.
Alpha Two Phase II testing is currently taking place five days each week. More information about testing schedule can be found here
If you have Alpha Two, you can download the game launcher here, and we encourage you to join us on our Official Discord Server for the most up to date testing news.
Player Mount Kills and Corruption

Currently, a player can flag up for PvP in a town or the open world and attack someone or kill their mount without any repercussions. Killing someone’s mount takes 10 min to revive for the affected player and the player taking the action doesn’t receive corruption or any other penalty. On Resna there was a guy standing in Lionhold and attacking new players repeatedly and killing their mounts but not actually killing them so he received no penalty or repercussion to stop his action.
I’m fine being ganked as there are repercussions the player doing it suffers but this is just griefing for no reason with no penalty. Additionally, the time it takes to heal up post attack for most classes is a long time without rations and extra detrimental to newer players.
I’m fine being ganked as there are repercussions the player doing it suffers but this is just griefing for no reason with no penalty. Additionally, the time it takes to heal up post attack for most classes is a long time without rations and extra detrimental to newer players.
0
Comments
The regen issues are found in another thread and don't seem to have anything to do with the topic of mount kills.
Honestly I didn't even know they could be killed in the current build, given how many are just left at the side of the road. Maybe I should start killing them just to make room to travel past
I didn’t know if this was a bug or an oversight allowing it to happen. Happy to put it in the bug section.