- Joined
- Dec 19, 2016
- Messages
- 2,280
- Reaction score
- 1,314
Well never mind then.
So I've spent the last 45 minutes debating whether I should say something here or just report it under auto-hit, but I really don't like doing those surprise reports so I thought I'd at least try to pursue this here first, but I also don't really feel like arguing. =/
@Valen Pelora your post pretty much has you go back in time to not launch the Force blast from the prior round and now use that energy to dodge and escape. The probelm is that both Orbit and Gaba's posts revolve around Aurora's Force blast already having been launched, you can't retroactively rewrite an attack that's already been responded to by other people because it's no longer convenient for your character to do it. There wasn't any indication in the previous post that she was questioning whether to do the attack (in fact saying she didn't even hesitate and there was only one true choice) or really even pay further attention to Varyn.
"With Zul's gaze still remaining forward, he only had to flick his eyes to see Aurora send a concussive blast of the force directed at his chest. With some distance still between the two, Zul simply dashed right to avoid the blast as it instead hit the wall behind him." - @Orbit
"However, the Light of the Force was still with her and the moment Zul shifted his focus to avoid the Force blast from Aurora, Arda pressed through her pain releasing the energy from the tips of her fingers into the Sith woman." - @GABA
To give a comparison, this would be like me slashing at someone's leg with a saber and rather than defend themself, that person stabs me in the face. They write in their post how the saber goes through their leg and they take it to secure a hit of their own. I can't then go back and say "just kidding, I didn't actually swipe at your leg because it's no longer convenient" (true story, this is how @Sreeya killed me, so I'm all too well aware of it).
But anyway.... I don't know how else to say this but there isn't really any part of the post that works.
I certainly don’t think a mistake in the timeline warrants an auto-report. I’ve read through this but won’t have time to write out my response until tomorrow.
The TLDR version is it wasn’t my intent to recot the attack. The Force she uses is what she began gathering after the blast at Orbit, rather than the blast reapplied.
I’ll elaborate on what my understanding on the timeline of actions is tomorrow morning when I can actually write it out.
Well, that's part of why I didn't end up going with the report lol
But anyway, I know you don't have time to elaborate, but just based on that TL;DR, I'm gonna say there's not time to 1) drop a blaster 2) launch a Force blast 3) gather the Force again and 4) dodge all in the time that it takes a blaster bolt to travel 10m. I likely won't be able to really have a lengthy OOC discussion about this tomorrow, and I'll let you give a more lengthy breakdown if you'd like, but there really isn't any time to gather the Force "after the blast at Orbit" since the blaster shot would be hitting during the blast on Orbit
Well, I actually don’t think we disagree that much. The only thing would be total time, which I think it actually time for the blaster to reach Varyn and then be deflected back.
Agreed that’s not very long though. I don’t mind editing out the use of the “pooled” Force and having it be a more tiring maneuver. I can edit once I get home tonight, like around 6:00PM EST.
But taking out the fact that the Force is pooling doesn't resolve the real issue, which is the fact that the blaster shot would be hitting her while she's launching her other attack. It's still treating it like the world is standing still for her to 1) drop the blaster 2) launch an attack 3) transition to using the Force a different way 4) dodge. Just because you take out her "pooling" the Force you're not really changing the 2-3 seconds worth of stuff you're doing in a fraction of a second
But taking out the fact that the Force is pooling doesn't resolve the real issue, which is the fact that the blaster shot would be hitting her while she's launching her other attack. It's still treating it like the world is standing still for her to 1) drop the blaster 2) launch an attack 3) transition to using the Force a different way 4) dodge. Just because you take out her "pooling" the Force you're not really changing the 2-3 seconds worth of stuff you're doing in a fraction of a second
Admin Ruling: Aurora gets hit in the chest. Luckily she is wearing armor and only has a hold-out blaster listed in her profile (which I'm going off of since your intro, Valen, just says "blaster" for weapons other than her saber). This would do light damage. As such, Aurora suffers a first-degree burn. Somewhat painful, yes, but not debilitating.
This is pretty good example of what we were talking about in the recent PVP announcement. Namely, relying on split-second timing of multiple different actions for your actions isn't likely to work unless your character is some level 4 badass. Aurora launched an attack and committed to another big attack in a way that left her open to a counter of her first attack. It'd be quite extraordinary for her to be able to attack and defend herself in that manner in the very short time available, and it rather blends into higher-level capabilities than she's at.
@Valen Pelora @Phoenix @Orbit @Sreeya @GABA @Faster Than Light