To save some of the somewhat negative responses to @1942786 dev QoL updates, I would suggest we ask for a Bugfix blog, in essence the devs could pick a bug(s) which are on their backlog ie. mortar shell firing outside of barrel, or the deleted node on Berlin attacker squad, used to have 2 nodes on I.StG2 (fw189 only one gunner now)
Then could send a quick news post stating this bug(s) is now fixed and slowly pick what can be fixed next, relatively easily, without massive resource drain.
There are 100’s of bugs in this game, but a lot are not noticable, unless looking for them.
Thinking if we get enough people agreeing with this idea, maybe the devs would agree to do something like this.
to answer this,
i think ground branch developers have similar issues as enlisted and answered as follow
( which, anyone with more than one brain cell would agree: )
you can’t put all resourches of someone that lacks of skill into the matter just like that, because you are just slowing things for everyone.
so they should proceed doing what they know best, and let the others work up with their own peace.
no one likes rushed things. and as we saw, those do occour and creates issues.
so the more time they take, the better is for everyone.
it’s like for real examples, I, a secretary would be forced to be putted in the main production line of my company.
for how much i’m good at adapting in situations when it’s required, not everyone is able to do so. and it’s not a valid solution for your company as you’d still have to spend time and resourches on the individual to actually make him a functional gear in the overhall system. ( such as actually on overlooking the person doing something new and correct it when makes mistakes because might be their first time ) let alone put someone that knoes nothing about it, nor it’s good at it.
to put it bluntly, ( and a concrete example in the gaming industry which it’s more relatable for us gamers )
look at the " remastered trilogy " of gta game given to a mobile ““gaming”” company. ( horrible port, lack of knowledge, etc )
yeah…
i’d like to avoid that for the longest time as possible.
1 Like
I am a Scrum Master / DM and work in Development, it is not to do with skills and most teams, they ensure a certain level of bugs are resolved each cycle, sprint.
It is not about skillsets, it is priority, generally you dont stop people working on something which has been agreed a priority, what I’m trying to say is Product Owner will be pushing devs to focus on new content and monetary changes, senior devs may have an awareness of tech debt and quality, but it may not be agreed to do a bug sweep over adding a new campaign.
Now back on point to Enlisted, everytime there is an update, poor devs get slammed, what about Pacific, fix XYX bugs first, blah blah. So what I am trying to suggest (not demand) is they be aware of their player bases needs and wants, all I am asking for is some visibility of bug fixes, it will satisfy the people who respond like they do, then the devs will get the feedback on their latest proposed change without the negative posting mixed in. Which sometimes is awful and IMHO people need to show respect or go play another game.
A few bug fixes each cycle and comms around them would keep people happy, currently it’s pot luck do we know what is being fixed this week or in the next update, they kind of do this for big stuff, but all the minor things that get reported, it’s just luck if resolved.
You will be able to see what bugs they fixed at the end of the major update.
I don’t think most people will be interested in reading in dev blog about what they fixed. But I agree that it would be good if they reported that they are working on fixing such and such bugs.
1 Like
