> 2535464451695009;13800:
> > 2533274808578327;13799:
> > > 2533274825830455;13792:
> > > Let’s not be too hasty without our claims. When you assert that something is “objectively provable”, you truly need to be able to prove it, or you just end up exaggerating and making your position appear more objective than it actually is.
> > > There are three claims contained in “[sprint’s] negative impact on Halo is objectively provable”. The first claim is that there exists specific, provable effects that sprint has on gameplay. The second claim is that there exists some objective measure of “negative impact”, and the third is that it can be proven that these specific effects have that property of “negative impact”.
> > > When it comes to the first claim, some effects generally attributed to sprint are: separation of movement and combat, increase of map sizes, and lowered difficulty of escaping encounters. If anyone wants to point out more, feel free to. At any rate, of these three effects, none are strictly speaking provable, mainly because we don’t have any strict enough definitions to speak about–
> >
> > But hasn’t it been proven on so many fronts (in word arguments, with video and such)? It’s not like the discussion of sprint was born recently, it’s been around since it was shown in Reach. It gets fiercer and fiercer as it stubbornly stays and anti sprinters have gotten so much more knowledgeable information they can bring to the table.
> > I’m just not sure what exactly you are trying to say, it just seems like you’re beating around the bush hard.
>
> tsassi’s not beating around the bush. Basically, they’re just saying that we have to think critically about why we believe our position to be true, and use evidence to support it rather than just stating out our opinion. They’ve done this occasionally for both sides of the sprint debate.
>
> Anyways, I was going to post later about how we have to stop circle-jerking this thread, but I guess I’ll address it now since I’m replying to you and don’t want to bump this thread if no one posts after me. I don’t really think we should just keep on talking about just flat out removing sprint anymore since we’re going to end up making this an echo-chamber, which it’s kinda been leaning towards for quite a while. Since there’s an incredibly low chance of 343 removing sprint, based on what Frankie said about Halo 5 being the “base of the games” going forward, how about we talk about “improving” or changing sprint for non-sprinters, and to separate future Halo games from the competition (mostly Call of Duty and Titanfall)?
>
>
> As much as I want sprint gone, we need to talk about some sort of middle ground, just so 343 doesn’t keep ignoring all the “Remove Sprint” and “Sprint Sucks” requests, rants, and stuff like that for the third game in a row and possibly think negatively about us classic-style fans. I feel like a transitional phase, much like Reach to Halo 5, would be much better, and less jarring, for the old and new community (mostly for the new community) than Halo 6 straight up removing sprint out the gate. I’m still finalizing my “free-time” thoughts on my proposition, however. It’s close, and some of its ideas are floating around on my posts, but I can’t think of a way to fix a big problem I thought about, which involves “universality.”
The truth is though that Sprint and No Sprint playlists will not work well together. I had this argument as the game designer in I01 and I think Halo 5 proves it. You need differently designed maps and settings for this to work, and you have to change too much to give both play styles the respect they deserve. This is why I’ve been saying for months that 343 should do a Reach style spin-off without sprint to gauge the community’s interest in Halo games without Sprint. Hell, even just a core series following MC or Locke and a side series with classic gameplay may make everyone happy.