Stadiums & Fan Base

# Stadiums & Fan Base

The Stadiums & Fan Base feature introduces a weekly economic management system for major teams. Every MAJOR team can own a stadium, have a historical fan base, and receive economic reports based on attendance.

Stadiums are not available for MINOR, COOP, PRO_CLUB, custom, or national teams.

# Requirements to enable stadiums

A league can display and use stadiums only if all of the following conditions are met:

  • the league has major teams;
  • the league has an enabled transfer market;
  • the league has the required premium level;
  • an administrator has enabled the stadium limit.

If stadiums are enabled but administrators have not configured any levels, the stadium still exists but remains at level 0 and provides no upgrades, events, or additional economic benefits. If stadiums are disabled, the fan base is still calculated for major teams participating in competitive tournaments. However, no economic reports, stadium events, or transactions are generated, and users cannot view or manage their stadium.

# Pre-season configuration

Administrators can configure stadium levels and events only before the season begins. Once the season has started:

  • levels cannot be created, modified, or deleted;
  • events cannot be created, modified, or deleted;
  • users can still start stadium upgrades and downgrades for their own team.

This rule prevents balance changes while weekly reports are already being generated.

To simplify configuration, the admin pages for stadium upgrades and events include an initialization button. The button creates only the missing default levels and events defined by the backend, without overwriting values already customized by administrators.

# Stadium levels

The stadium is divided into four sections:

  • Seating;
  • Food;
  • Medical;
  • Store.

Each configured level defines:

  • upgrade cost;
  • downgrade cost;
  • weekly maintenance cost;
  • upgrade duration;
  • downgrade duration;
  • one or more guided positive effects.

Levels must be consecutive. Level 3 cannot exist unless levels 1 and 2 already exist for the same section. Level 0 represents the default stadium state and has no associated configuration. If level 1 does not exist, teams see 0/0 and cannot upgrade that section.

Costs and durations must be progressive. A higher level cannot have a lower upgrade, downgrade, or maintenance cost than the previous one. Durations may be set to 0, making upgrades or downgrades instantaneous. In that case, the cost is still deducted and the intervention is immediately recorded as completed.

# Positive level effects

Each stadium level can provide positive effects that benefit the team.

Examples include:

  • additional seating capacity;
  • attendance bonus;
  • ticket price bonus;
  • food revenue per spectator;
  • store revenue per spectator;
  • reduced medical risk;
  • fan satisfaction bonus;
  • maintenance cost reduction.

# User upgrades and downgrades

During the season, the team owner may upgrade or downgrade any stadium section.

An upgrade immediately deducts its cost from the team's balance, but it is completed only after the number of weeks configured by the administrator. A section can only start a new upgrade if the previous one has already been completed.

A section may also be downgraded by paying the configured downgrade cost. Downgrades also require the number of weeks defined by the administrator before taking effect.

If a team can no longer sustain maintenance costs, the system may automatically schedule a forced downgrade for the section with the highest maintenance cost, avoiding any section that already has a pending intervention.

The stadium page always displays the levels actually configured for the current league rather than the technical maximum supported by the code. For example, if Seating theoretically supports up to level 4 but no seating levels have been configured by the administrator, users will see 0/0.

# Weekly events

Stadium events are configured per league but are not completely free-form.

Administrators choose:

  • event effect;
  • minimum required level;
  • base probability, greater than 0 and no higher than 30%;
  • a simple parameter, such as an estimated cost or percentage;
  • enabled/disabled status.

Two events with the same effect cannot exist within the same league. Additionally, an event can only be configured for a stadium section and level that already exist in the stadium configuration.

Events may be either positive or negative. Their type is determined by the selected effect.

Weekly event selection is not purely random. The system considers:

  • configured probability;
  • stadium condition;
  • seating level;
  • relationship between fan base/attendance and Food, Store, and Medical services;
  • ongoing upgrades;
  • recent events.

# Anti-frustration rules

To prevent teams from being excessively punished by negative events, the system applies the following rules:

  • a maximum of one event per team each week;
  • teams that recently suffered negative events are less likely to receive new negative events;
  • negative events become more likely when the stadium is neglected or poorly balanced.

# Stadium condition

The stadium condition ranges from 0 to 100. It starts at 100 by default and can change through weekly events.

Stadium condition:

  • increases the risk score of negative events when it is low;
  • affects fan satisfaction;
  • does not directly modify capacity, revenue, or costs unless a specific event explicitly applies those effects.

The team's stadium page displays both the stadium condition's contribution to event risk and its fan satisfaction bonus or penalty.

# Fan Base

The fan base is recorded weekly for every major team.

The base calculation considers:

  • wins;
  • draws;
  • losses;
  • winning streaks;
  • losing streaks;
  • stadium satisfaction;
  • recent events affecting supporters.

# Weekly financial report

The weekly financial report calculates:

  • capacity;
  • attendance;
  • ticket revenue;
  • food revenue;
  • store revenue;
  • maintenance costs;
  • event impact;
  • net profit.

General formula:

profit =
ticket revenue
+ food revenue
+ store revenue
- maintenance costs
+ event impact

If stadiums are enabled, the resulting net profit generates a financial transaction for the team. If stadiums are disabled, no stadium-related transactions are created.

The team's stadium page also displays a projected financial summary. It uses the same formula as the weekly report but does not generate reports or transactions. This projection allows users to preview their effective capacity, estimated attendance, current revenue, and maintenance costs before the next weekly report is processed.

# User pages

Users can view:

  • their team's stadium page;
  • current stadium levels;
  • the maximum levels actually configured by administrators;
  • effective capacity and projected financial summary;
  • active effects;
  • available upgrades and downgrades;
  • recent events;
  • latest weekly report;
  • fan base trend.

The league also provides an overview page listing every major team together with its stadium summary. From there, users can access each team's weekly reports and fan base history.

Reports are available for users to consult and cannot be modified by administrators.