Glorious Alpha Two Testers!
Alpha Two testing is currently taking place five days each week. More information about Phase II and Phase III 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 testing is currently taking place five days each week. More information about Phase II and Phase III 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.
"Contesting" as a new option for flagging
Spif
Member, Alpha Two
TLDR: This is a new flagging status that would only activate for stuff in the world that is designed to be contested. Less corruption if killing someone who does not fight back, assuming he's engaged in killing something like a named mob/boss/etc. Less hiding-behind-green. No change if the player fights back
Reading some threads about named mobs and bosses makes me think about a new flagging option that is less punishing.
For example if you're camping a named mob, hardly anyone will fight you for the kill. The risk associated with going red means you're not going to kill someone. It's just a PvE DPS race with little player friction.
So enter the option to flag players as "Contesting". Attacking certain mobs or use certain objects in the world (thinking about chests and maybe ashes here, not gatherables) will flag you as contesting (yellow? pink? brown?). Same timer as purple.
Why the level difference cap? To limit griefing. -10 level players are little challenge, and it follows the xp/loot cap limit. 2 players that are 10+ levels apart shouldn't really be competing for the same resource, since the higher level player cannot get drops.
So, the idea here is that if a player kills another player over a "contested resource" like a named mob that drops a valuable recipe they go almost corrupt and have to work that off before they can do it again.
This also works in dungeons for groups fighting over bosses. You can now attack (going purple and risking retaliation) and be able to manage your risk of going red. IE, if you kill a player and the enemy group is still not fighting back, don't do it again. Note, I would not expect the Contesting flag to be set for trash dungeon mobs. Only bosses make things spicy.
Working off corruption is time consuming, and more so as you go up in level. I think eventually it's designed for ~30 min of PvE grinding to clear corruption of one even level kill.
I believe Intrepid has talked about making "purple" less all-encompassing for events. IE attacking caravan 2189 will flag you "purple-2189", and thus you are only purple to other players flagged "purple-2189". The contested system could use that tech too. Both players would have to attack the boss to get the "Contested-Wormwig" before they could attack each other under those rules, to make sneak attacks less of a surprise.
Reading some threads about named mobs and bosses makes me think about a new flagging option that is less punishing.
For example if you're camping a named mob, hardly anyone will fight you for the kill. The risk associated with going red means you're not going to kill someone. It's just a PvE DPS race with little player friction.
So enter the option to flag players as "Contesting". Attacking certain mobs or use certain objects in the world (thinking about chests and maybe ashes here, not gatherables) will flag you as contesting (yellow? pink? brown?). Same timer as purple.
- Attacking a player who is Contesting will flag you purple
- Attacking a non-red player while you are contesting will promote your flagging to purple
- Killing a similar level player who is Contesting will get you 95% of the corruption to turn you red
- Killing a player 10 or more levels lower than you who is contesting will still turn you red. Note that this player will still show as green to you if the level difference is that high
- Dying while Contesting will have the same death penalty as purple
Why the level difference cap? To limit griefing. -10 level players are little challenge, and it follows the xp/loot cap limit. 2 players that are 10+ levels apart shouldn't really be competing for the same resource, since the higher level player cannot get drops.
So, the idea here is that if a player kills another player over a "contested resource" like a named mob that drops a valuable recipe they go almost corrupt and have to work that off before they can do it again.
This also works in dungeons for groups fighting over bosses. You can now attack (going purple and risking retaliation) and be able to manage your risk of going red. IE, if you kill a player and the enemy group is still not fighting back, don't do it again. Note, I would not expect the Contesting flag to be set for trash dungeon mobs. Only bosses make things spicy.
Working off corruption is time consuming, and more so as you go up in level. I think eventually it's designed for ~30 min of PvE grinding to clear corruption of one even level kill.
I believe Intrepid has talked about making "purple" less all-encompassing for events. IE attacking caravan 2189 will flag you "purple-2189", and thus you are only purple to other players flagged "purple-2189". The contested system could use that tech too. Both players would have to attack the boss to get the "Contested-Wormwig" before they could attack each other under those rules, to make sneak attacks less of a surprise.
0