I don't know of any like that, and I have to think you're being difficult. You can easily make it so the enemy will not attack a player that is locked in place due to the cutscene. That's literally already what happens out on the field while you're in a cutscene. Your player model is there, cannot move, and cannot be attacked. For that matter, where do you think your player model is whenever you're watching these cutscenes? The ones that are in the middle of battle?Doesn't work. There are cutscenes that are in the middle of battle. If a player could end up skipping the cutscene somehow but not move, what...you let them die?!
Offering broken solutions to fix a broken solution doesn't help. Especially when you offer them as an alternative to an actual solution that achieves exactly what it's meant to do. Make everyone see the cutscenes throughout their length and no second longer/less.
And before you respond with something, why don't you give it about a minute of thought regarding what possible things can be done to prevent from whatever response you've got from being a problem?
Maybe how about you stop putting words in what I write. I have not once defended exploiting. But you seem to be hellbent on pushing this narrative of 'if you don't stand against it, you are for it'. That's not the case here at all. Each time I've talking about exploiting, I have not defended the practice, nor the toxicity that comes along with it. In fact, several times throughout this thread, I have pointed out WHY people are exploiting, and once again, I will say it: it's because those people who have an issue with the unskippable cutscenes simply do not want to watch them for the umpeenth time. Players have a habit of going with the most efficient way of doing things - that's why this exploit exists, and that is why I keep saying that this is happening.
Seriously.
What same posters defending what bad habits and toxicity? Please, educate me. I would love to know what group of people are you identifying as having these so-called bad habits. Please, do share. I'll wait.
Oh my... this is getting heated!
Good thing no one is forced to do the MSQ roulette. It's something you voluntarily enter, with knowledge of what will likely happen, in exchange for the rewards offered for being willing to help. The best part is you can get those same rewards doing other content if you don't want to deal with the inconveniences of the MSQ roulette.Better yet, how about all veterans just boycott MSQ roulette en masse and see how long it takes to sprouts to complain Castrum and Prae are impossible to complete?
Then we'll see if they care that much about skipping cutscenes that they have to screw the same veteran that are gladly filling up the queue for their sake.
Remember, MSQ roulette exists for veterans to fill out the queue for the sprouts, not for the sprouts to give veterans rewards.
WOW That is a lot DC they might need flex tape to fix this!
Exploits aren't the only reason why people would come out of cutscenes before others. Sometimes it's simply the loading times. And then you're punishing people who have done no wrong. That's the problem with most 'solutions' people are suggesting.
But you are forced to run the dungeons themselves the once on each character.
Then maybe the game should stop to try and teach them about it. The game does very little to teach about it as it is considering how useful of a feature it can be. The PF is hardly an "endgame tool", you can use it for any sorts of content you wish.PF is not an option, not only do most newbies at that stage not know about PF or how it works as its an endgame tool,
Don't act like there isn't any precedent of the game breaking immersion to try to warn the player of copious use of cutscenes; it does that right before That Cutscene of 2.55 and at several points beyond and explicitly tells you to set aside extra time for the cutscenes. It can do the same thing here with warning players that you may want to find like-minded other players that will allow you to properly view the numerous cutscenes in the dungeon, and teach them about how the PF and how it allows them to do just that.
Disagree; I've made several groups precisely this way and precisely for the purpose of preserving the newbie/cutscene experience. You don't necessarily need to fill a full party either.but even if they did, they'd never find enough people to do Castrum or Praetorium.
There's a reason, but it isn't a very good justification for what they did. Much like how just because there are RMT/botters would not be a good justification for, say, making it so that every DoL can only gather 100 items a day.Again, if the devs changed it to be this way, there's probably a reason.
Devs are not infallible or immune to making poor decisions.
Last edited by Fynlar; 01-01-2019 at 05:06 PM.
I tried queuing for the roulette as a DPS earlier today (public holiday, early-to-mid afternoon) and the predicted wait time was 15 minutes. That's pretty normal for a dungeon queue on my server.
Requeued as tank, less than five minutes' wait.
Why assume that all newbies are playing DPS roles? (Or that all veterans are queuing as tanks and healers, for that matter. The run I had today didn't have any first-time players.)
I started as a healer. Fell into being a DPS due to the summoner class specifically appealing to me, but I've always kept white mage at a similar level to it.
And even if there's a bias to newcomers picking DPS roles first, there will still be veterans coming through with alts who know they should bring a tank or healer instead... right? That's what I did with my alts.
Except, as I said, it is not an exploit. And it can very well happen by sheer accident too, not only by players intent.
The first of the two in literally the first minute already have a cutscene in the middle of the battle. Even with the overpowered gear, tanks sometimes died there after gathering all the mobs but with the healers watching the cutscene. Albeit I admit that one is rather short.
That's a lot of extra work that can not only be prone to being bugged, but also possibly exploited somehow.
There are many ways they can go about it. But I specifically said there is only one competent way. Competent, aka. a solution that both neutralizes the "problem" that it's supposed to do without creating any more, and that takes minimal amount of work changing minimum amount of things. Because when you're programing you don't want your systems to be bloated and dependent on one another if possible.
Your idea is a "fix" that needs its own fixes. That's already not "competent". It's another half-assed thing to do. It tries to 'solve the problem' by not affecting it at all (the problem is skipping cutscenes, killing the monsters early is the result!). It is simply more of the same pointless stuff.
Did you actually wait?! I had 7min wait time turn into over 50 minutes on more than one occasion. "Wait time" doesn't mean much, it's just a prediction.
Last edited by kikix12; 01-01-2019 at 08:29 PM.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.