In a lot of development circles there are a few methodologies when it comes to developing software. I know that Agile and Waterfall(Iterative approach of planning a whole product ahead of time and doing a step by step process until full delivery) are the two major ones. (I wont get into Scrum Etc) just high level here.
I see more and more games being treated as Platforms or Services than just having a finite end of life and what those ramifications mean for game development as whole.
I see there are pros and cons to both of these methods.
Games as a Service/Platform
Pros
Can Last "Forever or tons of years"
Continuous Content
New Features/Gameplay Mechanics
Constant Add-ons/ Expansions
Cons
Devs might be stuck with a single IP for a longer period of time.
More Bugs and issues at launch to be fixed
Less Content in the beginning
Less Feature rich in the beginning
Games can totally flip game play over time for better or worse.
Games With Finite Dev Cycles
Pros
Usually are complete games
Major Gameplay stays static other than minor tweaks
Devs can move on to the next project faster
Still some life can be added with Add-ons or Expansions
Usually Less Bugs on Launch
Cons
Less Gameplay changing features(sticks to the core)
Sometimes Re-Sold as Remasters in a few years or generations.
Can become stale content wise. You "Finish" the game.
So i was curious are people really into having more games become platforms or services or they like the more traditional model with some added life now where games can be updated at times.
Personally for me I dont really like Games as a Service or Platform, But I do enjoy games like say Monster Hunter who had updates an Add-on and then a final update to the game.
Looking for actual discussion here on peoples thoughts on these different ways of making games and what they prefer and if they are okay with a future where we see more platforms and GaaS and traditionally dev'd games go away.
I see more and more games being treated as Platforms or Services than just having a finite end of life and what those ramifications mean for game development as whole.
I see there are pros and cons to both of these methods.
Games as a Service/Platform
Pros
Can Last "Forever or tons of years"
Continuous Content
New Features/Gameplay Mechanics
Constant Add-ons/ Expansions
Cons
Devs might be stuck with a single IP for a longer period of time.
More Bugs and issues at launch to be fixed
Less Content in the beginning
Less Feature rich in the beginning
Games can totally flip game play over time for better or worse.
Games With Finite Dev Cycles
Pros
Usually are complete games
Major Gameplay stays static other than minor tweaks
Devs can move on to the next project faster
Still some life can be added with Add-ons or Expansions
Usually Less Bugs on Launch
Cons
Less Gameplay changing features(sticks to the core)
Sometimes Re-Sold as Remasters in a few years or generations.
Can become stale content wise. You "Finish" the game.
So i was curious are people really into having more games become platforms or services or they like the more traditional model with some added life now where games can be updated at times.
Personally for me I dont really like Games as a Service or Platform, But I do enjoy games like say Monster Hunter who had updates an Add-on and then a final update to the game.
Looking for actual discussion here on peoples thoughts on these different ways of making games and what they prefer and if they are okay with a future where we see more platforms and GaaS and traditionally dev'd games go away.
Last edited: