DM MoonMoon wrote: ↑Mon Jun 05, 2023 9:08 am
I will put my hand up here and state, it was not the best choice to attempt to break up a very bad start to a pvp encounter.
I was hoping that bombard would make both parties retreat, after seeing the battle start with NO RP. There was a shout of "They are here" and after summons came out it descended into all out fight.
This was not acceptable level of RP before a PVP encounter. I attempted to Dispel the summoners to clear summons before they ran in but apologies to those who aren’t the ones rushing in blindly without rp before (it was chaos).
I will state that this was on both sides, and the Bombard is not targeted.
Again, it was to get both parties to fall back, my hope was that the thing can be stopped or even better reapproached with better RP.
My ask though, is that those organising groups attacking an area, and those defending an area, please take responsibility of who you take. If you are finding people who are trigger happy, don’t bring them, as it may fall on the organiser when things go wrong.
Thank you for listening.
(Edit for spell correcting, because I am terrible that word thing humans do)
Summon AI:
Unfortunately, I do think summons have a lot to do with PvP starting prematurely. In my brief time here, I've witnessed combat begin earlier than desired many a time due to one side (or both) failing to control their summons. The AI attacks before the player intends (resulting in accidental breach of the rules of engagement) and the opposing side reacts accordingly. After this, it is nearly impossible to de-escalate the impending domino effect, at least as a player.
I do think that as a DM, though, you've a lot more tools at your disposal for de-escalation of such incidents than us players have. Pausing the game either through a DM tool or some Timestop spell and sending your message to all players involved would de-escalate it immediately, I think!
Observations / Feedback:
Just to offer some hopefully gentle observations and feedback for the future...
(I don't mean these to sound incriminating, rather - they're intended to be an account of what I observed):
- Multiple people on our side (who did not summon anything), myself included, had 100% of their wards stripped by being DM 'rested' in the middle of combat.
- Even mundane weaponmasters (who had no summons out at all) had their wards stripped by DM powers during combat, which was confirmed after rewatching videos of the engagement.
- These appeared to be single-target clicks on specific characters to remove their wards.
- It seemingly only happened to people on the UD side, at least from what we observed, and from what was seen in any recorded footage.
Naturally, when one side of the engagement is having wards stripped mid-combat by a DM, they're going to have a pretty bad taste in their mouth and feel very strongly that the DM wanted one side in particular to come out on top.
I'm not saying this is the case, of course. The optics of it are just not the best, and stripping wards from one side is going to have a high probability of incurring such suspicions and opinions.
Recommendations:
As an alternative idea for breaking up engagements (that you feel started incorrectly), you could consider:
- Using Timestop (or some other DM mechanism to pause the game/combat)
- Appearing in between the two teams as DM.
- Using /shout to tell them to cease combat, disperse, restart the engagement properly, etc.
- Using a combination of the three.
That'd get the message through a lot more clearly and I think people on all sides would disengage if that were to happen.
Notification of Raids:
Admittedly, we pinged the DM channel about this raid later than we intended, though that is primarily my own fault, not anyone else's. We discussed it as a group and I took it upon myself to be the designated person to notify the DMs of the impending raid.
In the heat of organizing everything, I got quite distracted and it slipped my mind.
Thankfully, your shout about a reset served as a good reminder. So, I immediately pinged the DM channel to tell you guys we were mobilizing for a raid. I had intended to warn you all earlier, though.
I do want to note that my notification to the DM channel of the raid:
- Did not ask for the reset to be halted.
- Occured long before any combat began.
- Occurred before any opponents were on the same map as us.
Some final thoughts about the raid category itself, which sort of fell into a gray are that neither matched the description of a hard or a soft raid completely:
- It was not an attack on a settlement.
- It was not in an area with NPCs.
- At this point, it appeared to be more of a soft-raid, save for consisting over >6 players.
- A DM did recently ask us to, in the future, ping the DM channel as we're setting out for such raids. Which we did do this time! Even if it was later than initially intended. Which is really my own fault for trying to manage to much at once and forgetting to do so sooner.
All this said, I'll do my best to ensure that we give you more advance notice in the future!