I know a lot of players are split on modern halo gameplay (spartan abilities that provide enhanced movement such as sprint) and classic halo (no enhanced movements and abilities). I have two possibly impossible ideas to try to solve this.
- What if Halo 6 had multiplayer maps that were scalable in size? Imagine the developer creating a map with classic style gameplay in mind. Then instead of having to create a whole new map they can ‘stretch it out/scale it up’ to make it work for modern style Halo. The maps need to be bigger for sprint.
OR OPTION
- What if Halo took the Call of Duty formula of having three different teams make Halo? That would give each team three years to make a game. And that would give fans a new game each year. It would break down like this. Year one 343 releases a sequel to the current Halo storyline and offers multiplayer that is modern style Halo. Year two team two releases a Halo Wars sequel. Year three team three releases a new family of Halo games that tell stories from early on in Halo’s history and offers classic style multiplayer (Halo 3). Then the following year the cycle starts over. 343 team one releases a modern halo sequel. And so on.
I dont know if either either of these is feasible. Just putting some ideas out.
> 2533274805980490;1:
> I know a lot of players are split on modern halo gameplay (spartan abilities that provide enhanced movement such as sprint) and classic halo (no enhanced movements and abilities). I have two possibly impossible ideas to try to solve this.
>
> 1. What if Halo 6 had multiplayer maps that were scalable in size? Imagine the developer creating a map with classic style gameplay in mind. Then instead of having to create a whole new map they can ‘stretch it out/scale it up’ to make it work for modern style Halo. The maps need to be bigger for sprint.
>
> OR OPTION
>
> 2. What if Halo took the Call of Duty formula of having three different teams make Halo? That would give each team three years to make a game. And that would give fans a new game each year. It would break down like this. Year one 343 releases a sequel to the current Halo storyline and offers multiplayer that is modern style Halo. Year two team two releases a Halo Wars sequel. Year three team three releases a new family of Halo games that tell stories from early on in Halo’s history and offers classic style multiplayer (Halo 3). Then the following year the cycle starts over. 343 team one releases a modern halo sequel. And so on.
>
> I dont know if either either of these is feasible. Just putting some ideas out.
- It’s a nice idea, but changing a map’s flow requires more nuance than simple scaling. However, a scaling option would be useful.
- That would mean the sections of the population would linger with their preferred game, meaning that each game would take a hit to their matchmaking. H5 fans would stick to 343 games, Halo Wars fans would stick or cycle between the Classic and Modern games, and the Classic fans will stick to the multiplayer of the classic based games. Population issues would likely come of that.
I think having a permanent playlist like the Classic Throwback Playlist from the get-go in the next installment will please a lot of people. Especially if they decide to continue with the Halo 5 mechanics. Otherwise, vice versa to please modern fans. I agree with your general idea, Halo 6 should be a means to bring the two generations together.
I would hate for Halo to become a year to year franchise.
I do see your point though.
Feel free to use any of the existing wish list threads in General Discussion to talk about future Halo games and features. This forum is for discussing Halo 5 