“SCI Knows What We Want” Is Not Evidence: Why the Boxing Gaming Community Should Demand Better Research
Introduction: A Convenient Answer That Ends the Conversation
Whenever players question the direction of Undisputed, the same response seems to surface:
“Steel City Interactive knows what the community wants.”
Community managers say the developers read the Discord wishlist. Content creators assure frustrated players that feedback has been seen. Supporters argue that the studio has collected ideas for years and therefore understands what boxing fans expect from the game.
But that statement raises a more important question:
What evidence proves that SCI accurately understands the wider boxing gaming community?
Reading Discord messages is not the same as conducting research. Watching content creators is not the same as measuring customer priorities. Receiving suggestions is not the same as determining which features matter most, which audiences are being underserved, or why some players have lost confidence in the product.
The phrase “SCI knows what we want” has become more than reassurance. It is increasingly used to close discussions, dismiss criticism, discourage independent surveys, and tell passionate contributors that their work is unnecessary.
That should concern everyone who wants the next boxing game to be deeper, more authentic, and more accountable to the people buying it.
SCI Had the Community’s Attention During the ESBC Era
Before the game became known as Undisputed, it was promoted as eSports Boxing Club, or ESBC. During that period, the project attracted boxing fans because it appeared to promise something the genre had been missing for years: a serious, detailed and modern boxing experience.
The community was not silent.
Players discussed footwork, punch variety, realistic stamina, defense, clinching, inside fighting, boxer individuality, career depth, judging, referees, corner systems, presentation, historical eras, online competition and extensive creation tools.
Fans were not merely asking for more licensed boxers.
They were describing the fundamental systems required to make a boxing game feel like boxing.
That distinction matters because the central criticism of Undisputed has never been limited to roster size. The deeper concern is whether the game fully represents the tactical, physical, strategic and cultural depth of the sport.
SCI had years to observe these conversations.
If the company understood what players wanted before and during the ESBC period, the question becomes unavoidable:
Why were so many frequently requested systems absent, limited or underdeveloped in the finished experience?
A company may know that customers want something and still decide not to build it. That can happen because of budget constraints, technical difficulties, production deadlines, licensing concerns, management decisions or a change in creative direction.
However, that is different from saying the company did not know.
When supporters repeatedly claim that SCI knows exactly what the community wants, they unintentionally create a second problem. They remove ignorance as an explanation and leave prioritization and decision-making as the central issues.
If SCI knew what boxing fans wanted, then players deserve to know why those priorities were not reflected more clearly in the game.
A Wishlist Channel Is Not Community Research
One of the most common defenses is that SCI developers can see the wishlist section on Discord.
That may be true, but visibility does not equal understanding.
A Discord wishlist can collect ideas, but it cannot automatically determine:
How many players support each request
Which requests matter most to different audience groups
Whether offline players and online players want the same things
Why former players stopped playing
What non-Discord customers think
Which features influence purchasing decisions
Whether simulation-focused fans feel represented
How casual boxing viewers differ from longtime boxing followers
Whether content creators reflect the broader market
Which requests are essential and which are merely desirable
Discord is a communication platform, not a scientific sampling method.
Its most active participants may be highly engaged, but they are not necessarily representative. The discussion can be shaped by regular posters, moderators, competitive online players, prominent personalities and users who are comfortable participating in that environment.
Meanwhile, other groups may be underrepresented or absent:
Offline career players
Older boxing fans
Boxing historians
Former boxers and trainers
Players who left the server
Customers who stopped playing
Console players who do not use Discord
Players who prefer deep simulation systems
People who never bought the game because of missing features
Fans who do not want to argue publicly with creators or moderators
A wishlist channel can tell developers what certain active users are discussing. It cannot, by itself, establish what the entire customer base wants.
That is why “the developers see the wishlist” should never be treated as the final answer.
Seeing Feedback Is Not the Same as Acting on It
There is another problem with the Discord defense.
Even when developers see feedback, the community usually has no way to know how that feedback is handled.
Was the idea documented?
Was it categorized?
Was it sent to the appropriate design team?
Was it rejected?
Was it postponed?
Was it technically tested?
Was it considered too expensive?
Did management decide it did not fit the creative direction?
Was it overshadowed by another priority?
Without a transparent feedback process, “the developers saw it” tells the community almost nothing.
A message can be seen and ignored.
A suggestion can be acknowledged and never evaluated.
A request can be added to an internal list without receiving any serious consideration.
The community does not need every private development document. However, it does need a clearer explanation of how feedback moves from public discussion to internal decision-making.
Otherwise, the wishlist becomes a waiting room where ideas accumulate without accountability.
Why an Independent Third-Party Survey Matters
An independent survey would not solve every development problem, but it would provide something the current conversation lacks: structured evidence.
A properly designed survey could separate the community into meaningful groups and ask each group what it values.
For example, researchers could compare:
Hardcore boxing fans and casual boxing viewers
Simulation players and arcade-oriented players
Offline players and online competitors
Career-mode players and quick-fight players
Historical boxing fans and modern-roster fans
Current players, former players and non-buyers
Console players and PC players
Content creators and ordinary customers
The survey could then measure priorities across major categories.
Gameplay
How important are clinching, inside fighting, ring positioning, realistic stamina, block fatigue, punch variation, referee interaction, footwork identity and tactical AI?
Boxer Identity
Do players want boxers to differ through tendencies, traits, attributes, signature punches, defensive styles, movement patterns, ring IQ and corner relationships?
Career and Universe Systems
How much demand exists for promoters, managers, trainers, amateur careers, rankings, rivalries, injuries, matchmaking, belts, organizations, dynamic records and multiple controllable boxers?
Creation Tools
How important are created boxers, trainers, referees, gyms, belts, arenas, organizations, records, commentary names and downloadable community content?
Presentation
Do players value era-specific broadcasts, ring walks, weigh-ins, corner scenes, belt ceremonies, post-fight interviews, historical filters and authentic commentary?
Roster Priorities
Do players prefer more modern boxers, more legends, multiple versions of the same boxer, deeper gameplay systems, or a balance of all four?
Customer Trust
Why did some players become disappointed? What would restore their confidence? What would make them purchase a sequel, avoid it, or wait for reviews?
These questions cannot be answered reliably by pointing to a Discord channel.
They require data.
Why Would Anyone Oppose More Accurate Information?
The resistance to an independent survey deserves scrutiny.
A third-party survey would not force SCI to implement every winning response. It would simply reveal what different sections of the audience prioritize.
So why dismiss it?
There are several possible explanations.
Some people may believe existing feedback is already sufficient. Others may worry that survey questions could be biased. Some may distrust whoever organizes it. Content creators may fear that the results would challenge their understanding of the audience. Community managers may prefer feedback systems that remain under company control.
There is also a more uncomfortable possibility:
A public survey could reveal that the loudest voices do not represent the majority.
It could show that many players value gameplay depth more than roster additions.
It could reveal stronger demand for offline modes than expected.
It could demonstrate that simulation-focused fans are not a tiny minority.
It could show that customers want historical boxers and modern boxers rather than choosing one group over the other.
It could also reveal that some highly promoted features matter less than missing foundational mechanics.
Transparent data creates accountability. That may be precisely why some people are uncomfortable with it.
Content Creators Are Not Automatically Community Representatives
Content creators can provide valuable feedback. They test games, communicate with developers, create tutorials, build enthusiasm and maintain active communities.
However, visibility does not equal representation.
A creator’s audience may share a particular playstyle, competitive interest or personality. Some creators focus on ranked online competition. Others prioritize entertainment, knockouts, roster reveals or frequent content updates.
Their concerns may be legitimate, but they may not match those of offline players, simulation fans, career-mode players or boxing historians.
Creators may also have relationships with studios that affect how they communicate. Early access, developer interviews, event invitations, exclusive information and continued access can create incentives to remain measured or supportive.
That does not mean every creator is dishonest.
It means the audience should recognize the structural difference between independent criticism and access-dependent commentary.
A content creator saying “SCI knows what we want” should not be treated as evidence unless that creator can show how the conclusion was reached.
What research was conducted?
How many people were surveyed?
Which groups were included?
What questions were asked?
Were former players represented?
Were the results published?
Without answers, the claim remains an opinion.
Community Managers Should Facilitate Dialogue, Not End It
Community managers occupy a difficult position. They communicate with customers while representing the company. They often receive criticism for decisions they did not personally make.
Still, their role should include helping the studio understand the community and helping the community understand the studio.
Repeatedly telling players that developers have seen the wishlist does not accomplish either goal.
A stronger community-management process would explain:
How suggestions are collected
How duplicate requests are organized
Which subjects are being researched
Which ideas are outside the current scope
Which systems are being investigated
Why certain requests were rejected
What kind of feedback is most useful
How the studio distinguishes majority demand from vocal demand
This would not require revealing confidential development plans.
It would simply demonstrate that the feedback process has structure.
When community managers instead rely on broad statements such as “the team knows what players want,” they may unintentionally sound dismissive. The message becomes: stop asking, stop repeating yourself and trust the process.
But trust requires evidence.
Why Contributors Like Poe Should Not Be Treated as a Problem
Poe has spent years developing and documenting ideas for boxing video games. His work extends far beyond requesting individual boxers or minor cosmetic additions.
He has proposed systems involving:
Boxer tendencies
Capabilities and traits
Signature punches
Defensive styles
Inside fighting
Clinching
Referee behavior
Corner intelligence
Trainer chemistry
Career ecosystems
Promoter and manager AI
Amateur progression
Universe modes
Creation tools
Historical presentation
Online rule contracts
CPU-versus-CPU functionality
Era-specific broadcasts
Dynamic records and rivalries
No company is obligated to adopt every idea from one person. No contributor should expect complete agreement.
But dismissing a person with thousands of documented concepts while claiming the company already knows what fans want is contradictory.
If the ideas are unrealistic, explain why.
If they are too expensive, discuss production priorities.
If they conflict with the design vision, clarify that vision.
If some are valuable, acknowledge them.
What should not happen is the use of vague assurances to make detailed criticism disappear.
Passionate contributors are not automatically enemies of a studio. They may be demanding because they care about the sport and believe the genre can be better.
Silencing or marginalizing such people does not strengthen the community. It creates an environment where only comfortable feedback is welcomed.
Repetition Is Often a Symptom of Unresolved Problems
Critics are frequently accused of repeating themselves.
That accusation ignores why repetition happens.
Players repeat concerns about clinching because clinching remains inadequate or absent.
They repeat concerns about inside fighting because the issue remains unresolved.
They repeat concerns about career depth because the mode still does not meet their expectations.
They repeat requests for transparency because clear answers were never provided.
Repetition is not always harassment, negativity or attention-seeking.
Sometimes it is evidence that the company has not addressed the underlying concern.
When people feel heard, they usually do not need to raise the same issue indefinitely. When they receive only generalized responses, they continue asking.
Telling them that the developers have already seen the wishlist does not resolve the issue. It merely confirms that the feedback was visible.
The Difference Between Knowing and Prioritizing
The debate should be reframed.
The central question may not be whether SCI knows what players want.
The more important questions are:
Which players does SCI prioritize?
Which version of boxing does the studio want to represent?
Which features does management consider essential?
Which audiences are viewed as commercially valuable?
Which requests are considered too complex or too costly?
Which systems were sacrificed to meet deadlines?
Does the studio want a simulation, a hybrid game or an accessible competitive product?
How much influence do content creators have compared with ordinary players?
How much weight is given to boxing experts and former boxers?
A company can know that a section of the community wants realism and still decide to pursue broader accessibility.
A company can know that players want deep career systems and still prioritize online modes.
A company can know that fans want more boxer individuality and still rely on shared animation or movement systems.
Those are business and design decisions.
The community should be allowed to discuss them honestly.
“SCI knows what we want” should not be used to disguise the difference between understanding a request and choosing not to prioritize it.
What Transparent Community Research Could Look Like
SCI could take several practical steps without surrendering creative control.
1. Commission an Independent Survey
Use an outside research firm with experience in games, sports or consumer behavior.
2. Publish the Methodology
Explain who was surveyed, how participants were recruited, how many responded and how the data was weighted.
3. Separate Audience Segments
Do not combine competitive online players, career players, boxing historians and casual players into one undifferentiated category.
4. Publish Major Findings
The company would not need to release every internal detail. It could share the strongest preferences and major differences between player groups.
5. Create a Public Feedback Framework
Show which areas are being explored, which are not currently planned and which require additional research.
6. Conduct Exit Research
Survey people who stopped playing, refunded the game or chose not to purchase it.
7. Include Boxing Expertise
Consult boxers, trainers, referees, judges, historians and experienced boxing-game players—not merely personalities with large followings.
8. Repeat the Process
Community preferences can change. Research should occur at multiple stages of development, not only after controversy.
This would not guarantee a perfect game.
It would make claims about community understanding more credible.
Questions SCI and Its Representatives Should Answer
Before anyone says SCI knows what the community wants, they should be prepared to answer the following:
How was the wider community studied outside Discord?
Were former players and dissatisfied customers included?
How were offline and online players compared?
How did SCI distinguish boxing fans from general fighting-game players?
Which requested mechanics were identified as highest priority?
Why were frequently requested boxing systems missing or limited?
How much influence did selected content creators have?
Were survey results ever collected and publicly shared?
How were boxing experts involved in design decisions?
Why is an independent third-party survey considered unnecessary?
What evidence supports the claim that the studio understands the full audience?
Does SCI view Undisputed as a simulation, a hybrid game or something else?
Which audience is the game primarily designed to satisfy?
How does the studio handle detailed feedback from long-term contributors?
What lessons from the first game would materially change the development of a sequel?
These are not hostile questions.
They are questions about research, product design and accountability.
Conclusion: Stop Treating a Claim as a Proven Fact
The boxing gaming community should stop accepting “SCI knows what we want” as a conversation-ending response.
SCI may know what its most active Discord members want.
It may know what selected content creators want.
It may know what competitive players want.
It may know what internal leadership wants the game to become.
But none of that proves that SCI accurately understands the entire boxing gaming audience.
A Discord wishlist is not a representative survey.
A content creator is not automatically a community spokesperson.
A community manager’s reassurance is not market research.
Seeing feedback is not the same as analyzing it.
Acknowledging feedback is not the same as prioritizing it.
The purpose of a third-party survey is not to attack SCI. It is to replace assumptions with evidence.
If SCI truly knows what the community wants, independent research should confirm that understanding.
If the results reveal gaps, then the survey would provide an opportunity to improve.
Either outcome would benefit the company, the developers and the players.
The resistance to better research only creates more suspicion.
The community should not be told to be quiet because the wishlist has been seen. It should be shown how feedback was measured, how decisions were made and which audience the game is truly being built for.
Until that happens, “SCI knows what we want” remains a public-relations statement—not a demonstrated fact.
No comments:
Post a Comment