Exactly.The whole "bonobo is the toolset, its placeholder text" excuse is almost literally perfect for a malicious actor to offer plausible deniability. Just saying.
It's easier to ignore than be transparent
especially when press just ignore the stuff too
From a PR perspective, they've already managed to sweep this under the rug. This isn't even on the front page, let alone headlines, of the major gaming sites.
You really don't see why releasing an item specifically to commemorate juneteenth called "monkey" and then excusing it with an excuse that should have resulted in other documented instances of this problem happening prior but somehow didn't maybe warrants a bit more thorough investigation and further action?It was a name for an internal tool which was fixed super fast along with the apologies.
Why we're still talking about this?
That has nothing to do with the issue at hand of how a nameplate shared the same name, for Juneteenth nonetheless.
You really don't see why releasing an item specifically to commemorate juneteenth called "monkey" and then excusing it with an excuse that should have resulted in other documented instances of this problem happening prior but somehow didn't maybe warrants a bit more thorough investigation and further action?
Really?
I get it, it was VERY unfortunate but it wasn't a name they deliberately choose to publish.That has nothing to do with the issue at hand of how a nameplate shared the same name, for Juneteenth nonetheless.
I have seen literally zero evidence for this. This is not meant as a snide remark: Can you produce any?It was inherited from a template generated by an internal tool named like that
I get it, it was VERY unfortunate but it wasn't a name they deliberately choose to publish.
It was inherited from a template generated by an internal tool named like that (following Bungie naming convention too) and was fixed superfast even without the need to release a patch for it + they acknowledged this unfortunate event and timing and apologized on all social media.
Why the need to still burn them down now?
I have seen literally zero evidence for this. This is not meant as a snide remark: Can you produce any?
I get it, it was VERY unfortunate but it wasn't a name they deliberately choose to publish.
It was inherited from a template generated by an internal tool named like that (following Bungie naming convention too) and was fixed superfast even without the need to release a patch for it + they acknowledged this unfortunate event and timing and apologized on all social media.
Why the need to still burn them down now?
Halo Infinite insensitive Juneteenth color palette quickly removed in recent update
It is now simply labeled "Freedom."www.windowscentral.com
Halo Infinite insensitive Juneteenth color palette quickly removed in recent update
It is now simply labeled "Freedom."www.windowscentral.com
If you don't care about it you can just not post about it. Trying to dismiss people's concerns around racism is super shitty though, especially with baseless claims about how it happened.It was a name for an internal tool which was fixed super fast along with the apologies.
Why we're still talking about this?
They explicitly did not say this.I get it, it was VERY unfortunate but it wasn't a name they deliberately choose to publish.
It was inherited from a template generated by an internal tool named like that (following Bungie naming convention too) and was fixed superfast even without the need to release a patch for it + they acknowledged this unfortunate event and timing and apologized on all social media.
Why the need to still burn them down now?
Halo Infinite insensitive Juneteenth color palette quickly removed in recent update
It is now simply labeled "Freedom."www.windowscentral.com
I'm sorry, diminishing the hurting feeling on seeing that on THAT day was never my intention. Racism is actually shitty on every level.If you don't care about it you can just not post about it. Trying to dismiss people's concerns around racism is super shitty though, especially with baseless claims about how it happened.
Sounds like this to me?
And you didn't think to check if it had been raised before in a near 700 post thread?I'm sorry, diminishing the hurting feeling on seeing that on THAT day was never my intention. Racism is actually shitty on every level.
I've only tried to clear the most probable perspective around this: an unfortunate accident and not 343 being racist.
I find it very hard to believe that this is the most probable scenario when even 343 themselves did not claim such a thing in their response on Twitter.I'm sorry, diminishing the hurting feeling on seeing that on THAT day was never my intention. Racism is actually shitty on every level.
I've only tried to clear the most probable perspective around this: an unfortunate accident and not 343 being racist.
All this says is that the toolset exists. Not how it relates to the naming. It's like saying "Mike Hunt is an employee here, but we did not intend to name this NPC Mike Hunt". The first part of the sentence has nothing to do with the latter part, it's just a useless statement saying "Yeah this also has the same name". Their choice of words is very deliberate here. It implies one explanation without stating it, which gives them plausible deniability.While the original name refers to an internal toolset, it was not intended to be applied to this content
You mean your posts here don't default to ResetEra Dot Com?obviously every program names their files in the name of the program. that's why all my word files are simply called "word.docx" and my photoshop exports are all called "photoshop.psd".
/s
Inherited as in the word is a prefix and the string was empty?
Hmmm.
Uhh the name of the tool should have no bearing on this unless it's a prefix of some sort. Any evidence of this or is that a "best intention" conjecture?
This proves the Bonobo tool exists. It proposes absolutely no mechanism through which the name of the tool was applied to an asset.
So I will ask again: Can you prove the name was pre-set or inherited from an existing template within the tool?
If you don't care about it you can just not post about it. Trying to dismiss people's concerns around racism is super shitty though, especially with baseless claims about how it happened.
They explicitly did not say this.
All this does is prove that the toolset exists, which was never in question. Besides, a report by Kotaku said the tool was largely used in Halo 5, not Infinite.
All they've said is that the toolset with the same name exists. They didn't say the toolset caused the error. They didn't even say the toolset has anything to do with the naming AT ALL.
And you didn't think to check if it had been raised before in a near 700 post thread?
I find it very hard to believe that this is the most probable scenario when even 343 themselves did not claim such a thing in their response on Twitter.
Read it very carefully. The response says "the tool exists and it is named Bonobo". At no point does it propose any workflow or sequence of events that could lead to the name of the tool being applied to an asset.
They don't mention any default names, existing templates, nothing.
All this says is that the toolset exists. Not how it relates to the naming. It's like saying "Mike Hunt is an employee here, but we did not intend to name this NPC Mike Hunt". The first part of the sentence has nothing to do with the latter part, it's just a useless statement saying "Yeah this also has the same name". Their choice of words is very deliberate here. It implies one explanation without stating it, which gives them plausible deniability.
According to Mint Blitz "saving tags within that program is very finicky" (and that tool is up and running since Bungie era) so , yeah, the "Bonobo" tag used as a default when nothing is put in it (or something's not entered correctly) is a real possibility.obviously every program names their files in the name of the program. that's why all my word files are simply called "word.docx" and my photoshop exports are all called "photoshop.psd".
/s
Saying "saving is finnicky" means literally nothing specific and, again, if Bonobo is the default name for items created in the program why not come out and just fucking say that? (And provide visual proof while they're at it, it really isn't that hard)According to Mint Blitz "saving tags within that program is very finicky" (and that tool is up and running since Bungie era) so , yeah, the "Bonobo" tag used as a default when nothing is put in it (or something's not entered correctly) is a real possibility.
Saying "saving is finnicky" means literally nothing specific and, again, if Bonobo is the default name for items created in the program why not come out and just fucking say that? (And provide visual proof while they're at it, it really isn't that hard)
Them dancing around the issue like this makes it much more suspicious if anything. It sounds like they're covering for someone.
If it's actually the second case, I really hope this already happened.If this was truly and accident it really shouldn't be hard to show how it happened. Otherwise, someone should have been fired.
According to Mint Blitz "saving tags within that program is very finicky" (and that tool is up and running since Bungie era) so , yeah, the "Bonobo" tag used as a default when nothing is put in it (or something's not entered correctly) is a real possibility.
I'm not trying to diminish the seriousness of what's happened at all + 343i could have been even more clear with their response, but it's very probable this was an actual accident and that's all.
I'm not trying to diminish the seriousness of what's happened at all + 343i could have been even more clear with their response, but it's very probable this was an actual accident and that's all.
Exactly. No suffix on the default name? Yeah, right.What kind of garbage program would just default to the program name when you forget to enter in a tag? Like imagine if you were on a Java IDE and forgot to name a class so it just named all the classes to Java rather than giving you an error message to enter a fucking name.
It was inherited from a template generated by an internal tool
There's no "smoking gun" proof, but that's the most probable scenario considering how that thing works.
There's no "smoking gun" proof, but that's the most probable scenario considering how that thing works.
It is highly improbable in the absence of evidence to the contrary.There's no "smoking gun" proof, but that's the most probable scenario considering how that thing works.
It was a name for an internal tool which was fixed super fast along with the apologies.
Why we're still talking about this?
If people are confirming that the tool exists, with that name, with screenshots, then at least one of these people could provide proof that it inserts the name of the tool by default into everything. No one's done that.There's no "smoking gun" proof, but that's the most probable scenario considering how that thing works.
Especially considering the ease of producing said evidence.It is highly improbable in the absence of evidence to the contrary.