Thats pretty typical for studios after a launch. They release the game and scale back on staff till they have another game to cook up. Theres usually not much to do after a game release for a lot of the staff till they have a game in the pipeline again.
Video game developer here. It has been happening since the games industry started. Frequently, early games were made by contractors that were let go at the end of a project.
Many studios have done this for decades. Many developers actually like this as contract work pays differently than salary work and gives different freedoms.
altima_neo@lemmy.zip 1 year ago
Thats pretty typical for studios after a launch. They release the game and scale back on staff till they have another game to cook up. Theres usually not much to do after a game release for a lot of the staff till they have a game in the pipeline again.
Conyak@lemmy.tf 1 year ago
Typical doesn’t mean it’s not fucked up.
qwertyqwertyqwerty@lemmy.world 1 year ago
So leadership doesn’t prep for a new project towards the end of the current one? sounds like terrible project management is to blame.
Shadow@lemmy.ca 1 year ago
They don’t generally have the funding to have multiple games in the pipeline, so that each resource is busy at all times.
It’s a shitty deal for the staff and they should contract more or something instead.
sadbehr@lemmy.nz 1 year ago
Imo it’s only recently that it’s become ‘typical’ for this to happen.
hightrix@lemmy.world 1 year ago
Video game developer here. It has been happening since the games industry started. Frequently, early games were made by contractors that were let go at the end of a project.
Many studios have done this for decades. Many developers actually like this as contract work pays differently than salary work and gives different freedoms.
pulaskiwasright@lemmy.ml 1 year ago
It’s been typical for qa and similar staff for a very long time.