Something about the Blitzball players all being characters you could find in the world, some of whom would otherwise be unremarkable NPCs really burrowed into my brain with FFX. Something about the fact that you’d have relationships with characters in two different contexts where they would often play a wildly different role in each really made the world feel a little bit more alive than normal.
I like it but found the fear of using items you might later need too be exacerbated to an uncomfortable degree by the magic system. I suspect I’d enjoy it more today than when it came out.
It looks like Kotick will be leaving after the transition so that’s a great start. My dream is that this all somehow leads to the full Overwatch PvE campaign coming back onto the table again (given that their attempts to provide long-term replay ability without doing the work seem to be floundering now, there’s a chance right?)
Unreal is good if you want to work on big expensive projects at big companies. Godot is good if you want to work on your own projects today and potentially but not definitly work on small to middle-sized projects at small to middle-sized at small to middle-sized companies in the future. Unity is fine if you want to work on small to middle-sized projects at small to middle-sized companies now and potentially in the future.
Which sucks. There ought to be a clear and unambiguous path to chose for someone moving into game development today but since Unity keeps making weird choices that are hostile to developers whilst not continuing to improve at a good pace, it’s hard to say for sure which engine will fill in the not-Unreal Engine part of the market unless you have a crystal ball.
Realistically the best thing is to have as strong a foundation in programming generally as you can so that switching engines is minimally disruptive (as there will always be a need to do so eventually. There’s very little chance one single engine will continue to be the standard over the 40+ years of a career.)
I’m not so sure about that. Godot is fantastic for making the sorts of projects they are describing. But if the relatively minor difference between Unity and Unreal’s workflow are a turn off for them, then the consciously different workflow in Godot is probably going to be a significant barrier. Personally, whilst I love Godot because it’s FOSS and lightweight and a great platform for building smaller scale games: a big part of the appeal for me is that I find the Unreal and Unity ways of doing things stupid, confusing and clumsy and the Godot way clever, clear and elegant. I know lots of people feel the exact opposite.
I think the game “development” industry is run by people who don’t understand the difference between a game designer and a game developer. As such there’s lots of people who only know as much about game design as the average developer does being tasked to do game design work and vice versa.
The reality is that it’s a lot of fuss for a game development company to switch engines but for an experienced individual developer it’s not a huge deal to switch engines. If you learn game development and design today using Unity then 100% of the game design knowledge is exactly transferable and 80-99% of the game development knowledge (depending on exactly what you’re doing) will transfer to Unreal or Godot or whatever else you might need to use later.
It’s like a musician switching from one audio production suite to another. The musical theory stays the same and while the exact details of how to make each bit of software do stuff is different, the actual stuff you’re making it do is broadly the same.
In the comment you replied to they meant video game development companies by “developers” not the individual employees at those companies who do the actual work of developing games. Typically the actions of video game development companies are driven by the MBAs who have most of the big picture decision making power rather than the individual employees who develop the games.
Everyone in this thread is failing to understand that “developers” in this context can mean both “people who develop videogames” and “businesses that develop videogames.” As the people who develop videogames are not always the ones who make decisions like this at businesses that develop videogames those two different things that everyone is using the same word for often have opposing positions on the matter.
In my eyes it’s no different than a publisher selling a book that is in the public domain. You’re not paying them for their copyright, you’re paying them for everything else that goes into putting a physical copy of that text into your hands.