Acerola (Garrett Gunnell) — public-source background and brand-risk dossier

Prepared: 2026-06-26
Subject: Acerola / @acerola_t / Garrett Gunnell
Review type: Public-source creator, commercial, and reputational due diligence
Overall assessment: Medium overall risk, with one universal High prelaunch correction and campaign-specific High brand-fit exposure
Confidence: High on the creator's public work history, sponsor history, current public career presentation, and direct statements; medium on contractual/IP obligations and rights-clearance status because those require private documentation.

Executive assessment

Acerola is a technically credible graphics-programming educator with a public body of code, long-form explanatory videos, and an unusually clear first-person account of how he entered the field. His official GitHub profile identifies him as Garrett Gunnell and links back to the Acerola channel; the channel and 10xN roster identify the same @acerola_t brand (official GitHub profile, accessed 2026-06-26; 10xN roster, accessed 2026-06-26). The 10xN roster displayed approximately 311K YouTube subscribers on the review date; treat that as a dynamic snapshot, not a guaranteed current count (10xN roster, accessed 2026-06-26).

No substantiated public reporting of fraud, hate conduct, sexual misconduct, criminal conduct, or a regulator/platform enforcement action was located in the sources reviewed through 2026-06-26. This was not a formal court/criminal-record search; it is a bounded negative finding, not proof that no such material exists.

The launch-relevant concerns are mostly public-content, compliance, operational, and rights issues rather than a hidden personal scandal:

1. High launch gate — AcerolaFX currently gives categorical FFXIV policy guidance that conflicts with Square Enix's official position. The project wiki says ReShade is “not against ToS and is not bannable,” and the installation page tells users not to worry about ReShade's multiplayer-ban warning (AcerolaFX wiki, installation page, accessed 2026-06-26). Square Enix's 2022 policy says third-party tools are strictly prohibited, can result in suspension or repeat-offense bans, and that public promotion is an investigation priority (Square Enix, “Regarding Third-party Tools,” 2022-05-09). The policy does not name ReShade, and practical enforcement may be uncommon, but “not against ToS/not bannable” is not supportable as categorical current advice. Correct it before 10xN publicly launches or promotes AcerolaFX.
2. High campaign-specific brand-safety exposure for mainstream sponsors — the sponsored AI video contains extreme rhetoric. Beyond categorical “theft” claims, Acerola makes a self-directed suicide joke while discussing music/stock-image rights and ends by saying contributors to generative-AI technology should face trial for “crimes against humanity” (AI video at 12:47 and 32:57, 2025-11-30). The statements appear polemical/hyperbolic, not a literal threat or evidence of private medical status; they are still unsuitable for many advertisers and appeared in a Brilliant-sponsored video. This is not a universal launch blocker; require informed brand-fit and full-video tone review for each campaign.
3. Music and third-party-media clearance is a recurring delivery risk. Many descriptions credit commercial game soundtrack recordings, sometimes dozens in one video, but do not state the license or Content ID status. Acerola said on camera that he did not own the music then playing and did not pay for displayed stock photos; that statement does not rule out a free license, permission, or fair-use defense, but it increases the need for documentation (AI video at 12:47, 2025-11-30). A 2024 description also says an outro song was copyright-claimed and had to be trimmed (OpenUSD video, 2024-08-26). This is not a finding of infringement or a channel-wide launch blocker. Rate the general evidence gap Medium and elevate it to High only for a specific deliverable that cannot be cleared.
4. Acerola publicly described past sponsor deadlines as damaging quality. In his 2025 recap he said a February video was made under a contractual release obligation, called the result his own “slop,” and explained that views support rent and sponsor metrics (2025 recap at 03:12, 2025-12-24). He also said the usual cadence was one sponsor obligation per month and that missed uploads meant he had explicitly cancelled with a sponsor. His corrective plan was to reject strict sponsorship deadlines and seek sponsors only after videos were finished (same video at 16:02). This is a medium delivery/capacity risk with strong self-awareness and a sensible mitigation already proposed by the creator.
5. His public status is now independent creator/former studio employee, but historical IP obligations still need documentation. His official Bluesky bio says “Graphics Programming Youtuber / Formerly Intel, Sony Studio Bend” (official Bluesky profile, accessed 2026-06-26). Before 10xN markets technical work, obtain written confirmation of current employment/representation, any surviving confidentiality or invention-assignment obligations, and ownership of code/assets created for sponsored videos.
6. A viral Palworld post shows hot-take/correction risk. In January 2024 Acerola linked Palworld's success to normalization of “generative ai slop games” and called it an asset flip; the post drew roughly 2.75 million views according to the public post metadata (X post, 2024-01-21). Pocketpair later denied using generative AI and said its artists produced thousands of sketches (GamesRadar, 2024-07-10). His wording strongly suggested an association but did not literally state “Palworld used AI,” and this review found no indexed correction. Treat it as an unsupported implication/hot take, not an adjudicated false statement.
7. There are additional historical judgment/dispute items worth discussing directly: a 2023 comment downplaying the GShade security incident and a 2025 Silksong backlash that Acerola characterizes as harassment. Neither establishes serious misconduct by Acerola, but both show how technical commentary can become a sponsor-facing dispute.

Recommendation: pause public launch until the ReShade/FFXIV guidance is corrected. Then proceed conditionally, applying music/IP clearance and full-video brand-fit review to each campaign, plus conflict confirmation, a completed-video sponsorship model, and category/tone guardrails. Nothing found requires a categorical “do not sign.”

Identity and official public footprint

How he got started and career history

The following timeline is primarily Acerola's own account, not an independently verified employment record. It is internally coherent and is supported by the dated public portfolio, but HR documents and references should be obtained for contracting purposes.

• 2017 — first computer-science course. Acerola said he enrolled at Oregon State University–Cascades and took his first computer-science class in fall 2017, learning fundamentals through p5.js (career explainer at 05:37–06:17, 2023-11-30).
• 2019 — graphics focus emerges. He said Unity and Catlike Coding tutorials in spring 2019, followed by the visual presentation of Death Stranding, pushed him toward real-time graphics programming (career explainer at 07:55, 2023-11-30).
• 2020–2021 — intensive self-study and portfolio building. He described prioritizing graphics study and project work while remaining in school; in June 2021 he applied that work to custom Minecraft shaders (career explainer at 10:10 and 12:03, 2023-11-30).
• August 2021 — YouTube starts as a learning resource and portfolio. He said the lack of accessible graphics videos motivated him to make tutorials for people coming after him, beginning with “I Made Minecraft Shaders,” 2021-08-03; his retrospective places the first upload in August 2021 (career explainer at 12:41–13:16, 2023-11-30).
• 2021–2022 — Intel internship. He said he interviewed in November 2021 for an Intel graphics internship working on a GPU profiler and began in February 2022 (career explainer at 13:16, 2023-11-30).
• June 2022 — degree and games-industry offer. He said he graduated with a bachelor's degree, received a full-time Intel offer, and instead accepted an associate graphics-programming position at a local Sony game studio. He attributed the offer to his portfolio and videos (career explainer at 13:30, 2023-11-30).
• 2023 onward — creator/educator plus public software work. The 2023 explainer presents him as a working graphics programmer; his current GitHub and Patreon present creator work, shaders, and graphics education as ongoing businesses (GitHub profile, Patreon, accessed 2026-06-26). By 2026 his official Bluesky bio described both Intel and Sony Studio Bend as former roles and his current role as graphics-programming YouTuber (accessed 2026-06-26).

Audience, content positioning, and credibility

Core positioning

The channel's durable niche is visually demonstrable graphics programming: shaders, rendering, procedural generation, post-processing, game-engine internals, and technical analysis of game visuals. Representative work includes Minecraft shaders, 2021-08-03, Counter-Strike 2 smoke, 2023-05-30, “What Is A Graphics Programmer?”, 2023-11-30, moving to Godot, 2024-12-30, and Silksong graphics, 2025-10-30.

His credibility is stronger than commentary-only creators because viewers can inspect public implementations. AcerolaFX is a modular post-processing pipeline; Acerola-Compute is a Godot compute-shader wrapper; and the public Post-Processing repository accompanies educational work (all accessed 2026-06-26). Graphics practitioner Eric Haines also discussed Acerola's work positively, describing the color video as technically solid and the career video as informative, while noting the use of artwork under a fair-use rationale (Real-Time Rendering, “Seven Things for August 22, 2024,” 2024-08-22).

The 2025 Dirt Jam produced 65 public entries and invited participants to learn terrain, graphics, and shader programming using any development environment, with a preference expressed for FOSS/Godot (event ran 2025-07-01 to 2025-08-02; accessed 2026-06-26). This is a positive community/education signal.

Voice and audience-fit considerations

Acerola's voice mixes technical explanation with profanity, dark hyperbole, insults directed at companies/industry actors, and combative sarcasm. That is visible in his own 2025 generative-AI video, 2025 gaming-industry video, and 2025 recap. This is not hidden conduct; it is part of the product. It can be effective with a technically literate gaming audience but is a mismatch for child-directed, conservative, or highly controlled corporate messaging unless the sponsored segment and adjacent editorial are approved.

Business interests, sponsor history, and conflicts

Owned and community-linked interests

• Patreon memberships and posts (Patreon, accessed 2026-06-26).
• Fourthwall merchandise (acerola.gg, accessed 2026-06-26).
• Open-source and source-available graphics repositories (GitHub profile, accessed 2026-06-26).
• Twitch/Discord community and creator-run game jams (Linktree; Dirt Jam, accessed 2026-06-26).

No public corporate entity was identified in the reviewed creator-controlled pages. Confirm the contracting entity, tax documentation, insurance, subcontractors/editors, ownership of the Acerola marks, and whether any talent manager or other agency currently has exclusive rights before launch.

Public sponsorship examples

This is a representative, not necessarily exhaustive, history derived from video descriptions and integrations:

Spot checks show conspicuous description disclosures and spoken sponsor handoffs; no concrete hidden-sponsorship incident was found. The public page does not reliably establish whether the YouTube paid-promotion setting was selected for every placement. Standardize both platform disclosure and clear, proximate verbal/on-screen disclosure under YouTube's paid-promotion guidance and the FTC's influencer disclosure guidance (both accessed 2026-06-26).

Conflict map

• Engines/tools: Acerola has publicly advocated moving to Godot and criticized aspects of Unity while also accepting a GameMaker sponsorship (Godot video, 2024-12-30; GameMaker sponsorship, 2025-08-31). An engine sponsor needs a full historical-claims review and narrowly drafted exclusivity.
• AI/cloud/data centers: His 2025 video is strongly anti-generative-AI in present industry practice and names companies and controversies (AI video, 2025-11-30). AI vendors and adjacent cloud/chip companies may be incompatible or require explicit disclosure and editorial independence.
• Game publishers/live services: He advocates preservation and Stop Killing Games and has criticized layoffs, publisher economics, and live-service incentives (industry video, 2025-07-29). A publisher sponsorship should be checked against past and scheduled editorial.
• Privacy/security: Prior Surfshark and Incogni placements create possible category exclusivity and claims-substantiation obligations (Surfshark, 2023-10-30; Incogni, 2023-09-30).

Controversies, criticism, and responses

1. AcerolaFX: GShade security response and current ReShade policy guidance — fact plus inference

Verified background: Acerola announced AcerolaFX in 2022 as a shader pipeline for GShade/Final Fantasy XIV (original announcement, 2022-08-19). In February 2023, GShade's developer acknowledged intentionally adding code that could restart a user's computer when a third-party application invoked GShade functions; contemporary reporting described the code as malware and reported community bans/removal of endorsements (PCGamesN, 2023-02-07).

Acerola's direct response: On 2023-02-06, replying in his launch thread, Acerola said his shaders should work with standard ReShade, called the GShade controversy “a little overblown,” said the restart behavior had been removed, and vouched that users did not need to worry about malicious intent based on his conversations with the developer (Acerola Reddit comment, 2023-02-06).

Security assessment/inference: This is a historical medium-confidence judgment concern, not evidence that Acerola wrote malicious code. The public facts available at the time involved deliberately deployed restart behavior; personal trust in the developer was not an adequate security control. On the other hand, Acerola explicitly told users the shaders could work with ReShade, the behavior was in GShade rather than AcerolaFX, and no evidence reviewed indicates malicious code in AcerolaFX. The project moved its install guidance from GShade to ReShade during the February 2023 incident, which was a favorable response; the present AcerolaFX repository is public and MIT-licensed (accessed 2026-06-26).

Current compliance problem: The AcerolaFX FAQ currently says the FFXIV community team has explicitly stated that ReShade is “not against ToS and is not bannable.” The installation page instructs users to download ReShade with full add-on support and says not to worry about its multiplayer-ban warning, while adding that streamers may want to tread carefully (both accessed 2026-06-26). Square Enix's official 2022 statement says all third-party tools are strictly prohibited, violations can lead to suspension or repeat-offense permanent bans, and public statements promoting such tools are an investigation priority (Square Enix policy, 2022-05-09). Square Enix does not name ReShade on that page and says it cannot assess every tool; that nuance does not support a categorical “not against ToS/not bannable” assurance.

Prelaunch response: treat the current wording as a High correction gate. Replace it with accurate risk-based guidance that quotes/links the current publisher policy, makes no ban guarantee, and tells users to make their own informed choice. Also ask what he learned from GShade, require independent security review before recommending third-party installers/plugins, and prohibit reassurance based solely on personal familiarity with a vendor.

2. Silksong technical criticism and claimed harassment — fact, allegation, and timing correction

Fact: Acerola's Silksong graphics video, published 2025-10-30, praised the game while criticizing visible color banding and discussing dithering as a solution. In his 2025 recap at 13:10, he said the video received his worst like/dislike ratio and alleged relentless hate, daily comments, and a harassment campaign from an unnamed creator and that person's fans. Those harassment claims are his account; the present review did not independently establish the alleged organizer, scope, or causation. He did not name the person in the reviewed video, which reduced escalation risk.

Important chronology: Team Cherry had already added a dithering option to reduce color banding in a September 2025 patch, before Acerola's October 30 upload (official patch 1.0.28650, published 2025-09-21 PT). A later November 2025 patch added more dithering levels and made low the default (official patch 1.0.29242, published 2025-11-06 PT). Therefore Acerola's later statement that Team Cherry fixed the issue “after seeing my video” is not independently proven. The later expansion followed his video, but the original fix predates it; the public patch notes do not attribute causality.

Assessment: Low-to-medium reputational risk. His core technical observation was real enough for the developer to address in official patches, but fandom disputes can pull sponsors into hostile replies, and causal credit should not be asserted without confirmation. Require an escalation protocol, no naming of alleged harassers without evidence/legal review, and corrections when chronology materially changes a claim.

3. Generative-AI advocacy — fact and compatibility risk

In “Generative AI” is not what you think it is, published 2025-11-30 and sponsored by Brilliant, Acerola argues that current training practices constitute theft, describes the technology as unethical in the wrong hands, and makes broad environmental and social-harm claims. The description includes a reading list by title and author, but many entries are not direct links, making fast claim-level verification harder (video description, 2025-11-30).

Two lines materially raise the brand-safety level beyond ordinary issue advocacy. At approximately 12:47 he acknowledges not owning the music then playing and not paying for stock photos displayed, then makes a self-directed suicide joke as a sarcastic rebuttal to a piracy comparison. At approximately 32:57 he says anyone who contributed to generative-AI technology should be tried for “crimes against humanity” (timestamped video, 2025-11-30; closing statement). These are direct creator statements. They appear hyperbolic and polemical, not a literal threat or evidence about his private health; they are nevertheless severe sponsor-adjacency language. In the 2025 recap at 14:00, he also describes “absolute pure hatred” for generative AI and jokes about bullying hostile commenters.

Assessment: High brand-safety risk for mainstream, family, education, workplace, and AI-adjacent sponsors; Medium overall creator risk. The position is consistent with artist-rights advocacy and the video attempts a substantive technical explanation, but a sponsor appeared in this exact video. The legal and empirical issues remain contested, so categorical assertions about named companies should receive source, legal, and defamation review when adjacent to a sponsor. Require a timestamped tone/adjacency review of the entire deliverable, not just sponsor copy. Do not pair him unexpectedly with AI-generation vendors; preserve editorial independence in writing.

4. Palworld “AI slop” post — fact, contested implication, and correction risk

On 2024-01-21, Acerola posted that Palworld's success was “the first step in the normalization of generative ai slop games” and called the game an asset flip. Public post metadata showed approximately 2.75 million views and 23,000 likes when reviewed (X post, accessed 2026-06-26). The language strongly associated the game with the generative-AI concern, although it did not literally claim “Palworld used AI.”

In July 2024, Pocketpair's CEO denied that the game used generative AI and said its artists drew thousands of sketches; GamesRadar characterized the launch-era accusations as largely unsupported (GamesRadar, 2024-07-10). This review did not locate an indexed correction or clarification from Acerola.

Assessment: Medium hot-take/relationship risk, not an adjudicated defamation finding. Context matters: Pocketpair's prior AI experimentation contributed to public suspicion, and Acerola's exact wording can be read as a prediction about normalization rather than a literal claim about the game's production. The episode still shows that a viral implication can outrun the evidence and affect relationships with developers. Require a correction/clarification standard for material factual implications and a source review before naming a company in sponsor-adjacent criticism.

5. Gaming-industry and preservation advocacy — fact and compatibility risk

The unsponsored “Collapse Of The Gaming Industry” video, published 2025-07-29, urges viewers to support Stop Killing Games and sharply criticizes executive incentives, venture capital, layoffs, live-service design, and publisher conduct. The rhetoric is intentionally caustic. This creates predictable conflict with some publishers/platforms, but it is disclosed, issue-based advocacy rather than a hidden controversy.

Assessment: Medium category-conflict risk; low integrity risk. Screen every publisher, platform, engine, and live-service opportunity against his existing positions. Do not demand a false endorsement or editorial retraction as a condition of unrelated work.

Technical, intellectual-property, and disclosure review

Code and project licensing

Several flagship repositories visibly carry MIT licenses, including AcerolaFX, Acerola-Compute, and Post-Processing (accessed 2026-06-26). Selected public demonstration repositories, including CS2-Smoke-Grenades, Godot-Terrain, and Disney-PBR, did not surface a repository license in the GitHub interface during review (accessed 2026-06-26).

Absence of a displayed license is not evidence of copying or infringement; under GitHub's own guidance, default copyright normally applies when a repository has no license, so third parties do not automatically have permission to reproduce, distribute, or create derivatives (GitHub licensing guidance, accessed 2026-06-26). This matters because Dirt Jam explicitly told participants they could use his Godot-Terrain code as a base (Dirt Jam rules, 2025). Confirm and add the intended license before 10xN promotes reuse or distributes derivative assets.

Music, game footage, art, and other third-party media

Descriptions regularly credit recognizable commercial game soundtrack tracks without disclosing a license. The 2025 AI video alone lists music from Persona, Pokémon, Skullgirls, The Hundred Line, Danganronpa, and other commercial games; the 2025 recap and 2026 “Indie” video also contain long soundtrack lists. Videos also necessarily use game footage, screenshots, and occasionally gallery/art examples for commentary; an industry reviewer noted fair-use gallery-image use in the color video (Real-Time Rendering, 2024-08-22).

There is also direct creator evidence of friction. In the sponsored AI video Acerola says he does not own the music then being used and does not pay for the displayed stock photos (AI video at 12:47, 2025-11-30). “Do not own” and “do not pay” do not by themselves prove lack of permission—free licenses, platform licenses, permission, and fair use may apply—but the statement is poor sponsor-facing rights hygiene. Separately, the description of his OpenUSD video, 2024-08-26 says an outro song was copyright-claimed and had to be trimmed. That is a confirmed past delivery alteration, not merely a hypothetical risk.

Finding: Rights status is unclear, not adjudicated. Credit is not itself permission, and fair use is fact-specific. YouTube distinguishes Content ID claims from copyright removal requests/strikes (YouTube copyright-claim guidance; YouTube copyright overview, accessed 2026-06-26). Before any sponsored cut, require:

• a final cue sheet and asset list;
• license, permission, public-domain, or defensible commentary/fair-use basis for each third-party asset;
• screenshots of current claims, blocks, and strikes for the channel and proposed upload;
• replacement music available before delivery;
• a contract allocation for clearance, edits, claims, lost monetization, and takedowns.

Community/UGC terms

Dirt Jam was a constructive educational event, but its public rules said there “aren't really any rules” and that submitting granted permission for the work to be shown on stream or in a video (Dirt Jam rules, 2025). That lightweight grant may be enough for an informal community showcase but is thin for a branded or paid campaign: it does not clearly address warranties, music/art rights, commercial advertising use, moderation, age eligibility, privacy, releases, takedowns, or prizes.

Mitigation: Any 10xN-backed challenge should use agency-reviewed official rules, eligibility and moderation criteria, a defined media license, rights warranties, a takedown process, and platform-specific terms.

Research and claim substantiation

Acerola often links code and educational resources, which improves reproducibility. However, the AI video's source section names articles/authors without direct links while making categorical assertions about named companies (AI video description, 2025-11-30). For sponsor-adjacent technical or legal claims, require a claim sheet that maps each non-obvious assertion to a primary or high-quality source and records review sign-off.

Delivery and conduct themes

• Strength — candor and self-correction: The 2025 recap openly connects contractual deadlines to a video he considered below standard and proposes booking sponsors after completion (2025 recap at 03:12 and 16:02). This is valuable disclosure and a practical operating model.
• Risk — schedule predictability: Post-completion booking improves quality but makes fixed launch calendars harder. The agency should sell windows or completed inventory, not promise an unproduced monthly deliverable.
• Strength — substantive technical work: Public code and project walkthroughs make competence inspectable (GitHub profile, accessed 2026-06-26).
• Risk — conflict style: Sarcasm, profanity, corporate insults, and jokes about hostile commenters recur in public videos (2025 recap at 13:10–14:20). Do not assume the creator will fit sanitized brand voice without negotiated guardrails.
• Risk — audience pile-ons: Acerola says Silksong criticism triggered continuing hate and a creator-led campaign, although that allegation was not independently verified (2025 recap at 13:10). Sponsored controversy content needs moderation, escalation, and no-brigading language.

Risk matrix and claim ledger

Prelaunch questions for Acerola

Ask these in writing and retain the answers in the deal file:

1. Your public bio now describes Intel and Sony Studio Bend as former roles. Are you currently employed or subject to surviving confidentiality, invention-assignment, publicity, or outside-work restrictions? Provide the relevant carve-outs or approvals.
2. Which person or entity owns the Acerola channel, trademarks/handles, footage, code, merch business, and sponsor receivables? Who signs and invoices, and does any manager or other agency hold exclusive representation rights?
3. Provide the current YouTube copyright dashboard, including active Content ID claims, blocks, takedowns, strikes, and any repeat disputes. Which music licenses cover the soundtrack recordings in existing and proposed videos?
4. For the proposed deliverable, provide a cue sheet, game-footage/art list, code/dependency list, licenses, and any employer-created or third-party assets.
5. Will you follow the 2026 policy stated publicly: sponsor outreach only after a video is substantially or fully complete? What delivery window and review rounds can you actually support?
6. Which sponsor categories are incompatible with your public positions or prior exclusivities—AI, engines, game publishers, live services, privacy/VPN, education, or hardware?
7. What happened with the February 2025 sponsor-driven video and any sponsor cancellations mentioned in the annual recap? Were makegoods, refunds, or disputes involved?
8. Will you correct the AcerolaFX claim that ReShade is not against FFXIV's terms and not bannable? What source supported that wording, and what security/compliance standard will you apply before recommending third-party software again?
9. Did Brilliant review or approve the full AI video's self-directed suicide joke and “crimes against humanity” line? What tone limits will you accept for future sponsor-adjacent content?
10. Do you still stand behind the Palworld “generative ai slop games”/asset-flip post after Pocketpair's denial? Will you publish a clarification if the intended meaning was narrower?
11. What evidence supports the assertion that Team Cherry acted after seeing your Silksong video? Will you correct or qualify that claim if attribution cannot be documented?
12. Who moderates YouTube, Discord, Twitch, and community events? What are the rules for harassment, brigading, ban appeals, threats, and sponsor escalation?
13. Are there prior posts, deleted accounts, disputes, claims, employment conflicts, or sponsor problems that could reasonably surface during launch but were not found in this public review?
14. Can you provide two professional references, ideally one prior sponsor and one technical collaborator/editor, plus a list of all subcontractors touching campaign assets?

Contract and launch safeguards

• Rights warranty and asset schedule: creator warrants authority to use music, footage, art, code, fonts, sponsor marks, and subcontractor work; attach a final bill of materials.
• Pre-announcement correction: update AcerolaFX's FFXIV/ReShade FAQ and install warning to accurately reflect and link Square Enix's current blanket third-party-tool policy; retain a dated screenshot of the correction.
• Completed-inventory model: contract only after the core video is substantially complete, with a bounded sponsor-integration window. If a future commission is necessary, use a range and kill fee rather than a hard monthly promise.
• Copyright contingency: pre-approved replacement music/assets, rapid edit rights, claim/strike notice within 24 hours, makegood rules, and payment treatment for blocked/demonetized content.
• Employment/IP representation: continuing duty to disclose employer restrictions; no confidential or employer-owned code/assets; written employer approval where applicable.
• Conflict schedule: list prior active exclusivities and prohibited/incompatible categories; creator retains editorial independence, while the agency can reject false factual claims about the sponsor.
• Disclosure standard: clear spoken and on-screen sponsorship disclosure, #ad near the beginning of the description, and YouTube's paid-promotion designation.
• Claims review: primary/high-quality sourcing for named-company, security, legal, performance, privacy, environmental, and health claims; documented corrections process.
• Whole-video brand-safety review: screen the complete upload and adjacent posts, not only the sponsor read, for suicide/self-harm references, threats or violent hyperbole, profanity, targeted company allegations, and category conflicts. The purpose is sponsor-informed consent, not compelled editorial agreement.
• Conduct/crisis clause: no harassment, doxxing, threats, discriminatory conduct, or calls to brigade; evidence review before naming alleged wrongdoers; coordinated response and comment moderation during launch.
• Community-event addendum: formal rules, eligibility, rights grants, moderation, privacy, release, prize, and takedown language for any 10xN-backed jam or contest.
• Morals clause with due process: narrowly define serious misconduct and material brand harm, require notice and fact review, and distinguish substantiated conduct from mere disagreement or an online pile-on.

Source and evidence limitations

• This review used public creator-controlled profiles, videos/descriptions/transcripts, public repositories, event pages, official game patch notes, platform/regulator guidance, and limited third-party reporting through 2026-06-26.
• Dynamic counts, prices, inventory, posts, and public channel status can change after the access date.
• The employment history is substantially self-reported. The official bio supports his current public presentation as an independent creator/former Intel and Sony Studio Bend worker, but contracts, surviving obligations, clearances, private sponsor performance, insurance, tax entity, and platform dashboards cannot be proven from public pages.
• Reddit and creator statements were used as direct evidence of what Acerola said, not as independent proof of disputed events. The unnamed Silksong harassment claim remains uncorroborated in this dossier.
• Absence of located reporting is not proof of absence. A final launch decision should include creator disclosures, references, rights documents, and a fresh check immediately before announcement.

Bottom line

Pause announcement for one correction, then proceed with conditions. Acerola's technical authority, inspectable portfolio, and audience fit are credible, and the present review found no substantiated severe personal-conduct scandal. The universal launch gate is correcting AcerolaFX's categorical and presently unsafe ReShade/FFXIV rules assurance. After that, each campaign still needs asset clearance and informed whole-video brand-fit review because one sponsored upload included a self-directed suicide joke, “crimes against humanity” rhetoric, and music/stock-rights admissions. The next-tier risks are prior copyright-claim friction, surviving former-employer IP obligations, rigid sponsor deadlines, the viral Palworld implication, and predictable conflicts created by an anti-generative-AI/pro-preservation editorial identity. Use completed-video sponsorships with strong rights, claims, disclosure, moderation, and crisis controls.