1. Initiative being called for no discernible reason as far as the players are concerned. (breaks immersion, spoils events for the players themselves, causes confusion, etc..)
2. Players being told they are surprised during round 1 for no reason they understand (or in fact no mechanical reason) because the person initiating combat (for example), in other words causing the surprise, has not yet acted or had a turn. (players questioning what's happening, confusion, having to tell them they can't do anything until the triggering creature has had a turn, assigning surprise for no actual reason since nothing has happened, etc..)
Players being told they can't do anything until the person causing surprise has acted.
4. Narrative issues because the person initiating combat might be required to perform certain actions for story purposes, which gets you into simply giving the NPC / PC the first position in the initiative. (story line events can be disrupted, PC plans disrupted,
The party is moving on a trail in the woods, they enter the kill zone of a goblin ambush without noticing the goblins since they are hidden (either passive or active perception failed to beat stealth). The goblin leader then fires an arrow at one of the PC's to initiate the attack (or yells out in goblin, or whatever prompts combat. Could be many things, such as triggering a trap. But let's say for the sake of the example it's an attack.)
I would resolve the attack first, then determine who hadn't noticed the goblins before the triggering event (the attack) to apply surprise as appropriate, and finally I would have everyone roll initiative and start at the top of the initiative order.
So what happens if we go by the RAW only? First, if the triggering event is a goblin triggering a trap / making an attack that would meet your hostile intent requirement so you would roll initiative before that happens.
That means that if the goblin triggering the trap / making an attack is low on the initiative order. The party is presumably surprised for no reason they understand since nothing has happened.
The trap / attack that was the "hostile intent" and the "triggering event" doesn't actually follow the narrative.
For me, telling people "ok roll initiative" is less fun and interesting as narrating the event, "an arrow flies out of the bushes at you", and then asking for initiative from the party.
[MENTION=6788736]Flamestrike[/MENTION], in response to your statement at the end of post #55, perhaps it's because DMs on both sides of this argument are uncomfortable telegraphing to their players that battle is about to start. You could say, "The ogre has decided to attack you. Roll initiative." But that would be reading the ogre's mind for your players, giving them information their characters shouldn't have.
The Ogre screams in rage, hefts its club and starts charging at the Fighter! Roll initiative.
Its not a question of 'mindreading' - its a question of narrating the action!
If the Ogre goes first (initiative), it closes the gap before any PC can react. If the PCs go first, they might be able to drop the Ogre before it can close the gap, or maybe even charge it themselves, meeting it halfway or even possibly forcing the ogre to make a different choice on its turn in response.
Here's an example of what I mean:
DM: The ogre swings his club at your head. What do you do?
Player: I stab him with my sword.
DM: Okay, make a Dexterity check. If you beat the ogre's Dexterity check, you can try to hit him first. If he beats your check, he gets to try to hit you first.
So, you're asking them to roll initiative, except you're not calling it that? Initiative rolls are dexterity checks.
The problem is, if you only do it one-on-one, that there is no turn taking outside of combat so other players can describe concurrent actions and you then have the problem of deciding timings.
Wizard: While they are squaring up, I cast Hold Monster on the ogre.
Rogue: And I sneak round the back of the ogre and stab him.
Do you ask for dexterity rolls for the wizard vs the ogre, and for the wizard vs the fighter to see whether the spell takes effect before or after the ogre strikes and before or after the fighter strikes, and for the rogue separately against the ogre, the wizard and the fighter to decide when he strikes and if he gets sneak attack ...
Initiative simplifies all that. Each creature makes one dexterity roll and you sort them in order. It does work. Really it does.
Ah. I think we agree.Yes, that was my point. Initiative is a Dexterity check and there are stakes involved just like any other ability check. DMs that don't telegraph that combat is starting are not setting the stakes of the initiative roll.
Ah. I think we agree.
Although in your examples, you seem to be waiting for the player to declare his first round action (I stab the ogre) before he knows the outcome of the dexterity check (= initiative roll). This is fun and "realistic" but it gets messy if there are other players involved who might be taking actions and/or reactions. This is what worries me, I think. It could get chaotic rather quickly.
In 5e, initiative order controls the order that creatures choose their actions, as well as the order they are resolved. I like it, because it gives each player a moment in the spotlight as they address the situation as it stands at that very moment.
I dimly remember that 2e worked differently, though. Everyone declared their actions at the start of the round, then initiative was rolled for that round and the results were applied, effectively simultaneously. Wizards, in particular, had to adopt different tactics to avoid wasting spells on monsters that they knew were already dead. It became a different game.
</nostalgia>

(Dungeons & Dragons)
Rulebook featuring "high magic" options, including a host of new spells.