Sorry, but not how it arrives at the average reader at all.
Especially the “(but not limited to)” reads to me like “Look, we got the mission and the weapon, but not to worry, there’s more”. And from my standpoint it looks like something you’d write to avoid backlash in advance, so people don’t say “oh, itemization isn’t in”.
@Hank_jw’s clarification made things a lot clearer.
A better way to communicate this from the outset would have been to write the following:
“This new update features: New Mission; New Weapons.
We are at this point not sure if our itemization changes will be ready to deploy by then. For more news on itemization we are currently working on a dev blog update.”
^ Much clearer and still in proper corporate English. Alternatively they could have left all talk about itemization out completely.
I’m usually with Fatshark on the things they do, but we have to give proper feedback here so misunderstandings between Community Managers and Community happen less frequently. We need clear clarifications or the absense of information when it is not relevant. But including it in a vague sentence will always confuse readers.