/
Madden Leagues
/
Trade Settings & Value Formula
Madden Leagues

Trade Settings & Value Formula

Voting, privacy, limits, auto-approval, formula tables, picks, and Discord.

Access Trade Settings

Open Administration → Trade Settings with Edit League/Admin permission. Settings are divided into General Settings, Player Values, Draft Pick Values, and Discord Settings.

Change one area at a time and test with a sample evaluation.

Voting and workflow settings

  • Trade Approval Votes Needed: approvals required to pass.
  • Trade Denial Votes Needed: denials required to fail.
  • Max Pending Trades: pending requests allowed per member.
  • Max Trades Per Season: seasonal completed-trade limit.
  • Enforce Seasonal Trade Count: enabled by default; disable it to use a value budget without a count limit. The separate pending-request limit still applies.
  • Seasonal Trade-Value Limit: optional per-team budget. Pending and approved requests reserve the native value of assets that team sends; denied or deleted requests release it. Zero allows only zero-value offers.
  • Trade Reset Timing: Preseason, Regular Season, or Offseason boundary used to reset the seasonal limit.
  • Private Pending Trades: limits visibility to the two teams involved and Vote Trade holders.
  • Lock In Trade Votes: prevents vote changes.
  • Allow Vote On Own Trades: lets involved voters vote if they already have Vote Trade permission.
  • Anonymous Trade Votes: hides vote identity/decision.
  • Require Both Teams to Agree: requires team-member agreement before voting/approval.

Choose thresholds that cannot conflict indefinitely. Explain them in league Rules.

Seasonal value allowance

Leave Seasonal Trade-Value Limit empty to disable it without changing count limits. The offer preview shows each team’s approved usage, pending reservations, requested outgoing value, and remaining allowance. The budget uses current native player-value calculations and canonical draft-pick values, not optional contextual adjustments or cached player display values. Values are frozen when submitted, rounded to six decimal places, and never repriced when settings change. Both teams are checked again before approval; lowering a limit can block an existing request.

Only the current season and configured trade-reset window count. A pending offer from an earlier season or reset window must be resubmitted when a budget is enabled; it cannot complete for free in the new window. The count and value policies are independent, and the maximum supported limit is one trillion points.

Legacy requests prefer recorded automatic-approval or base-valuation totals. Otherwise the upgrade freezes their available stored player/pick values and labels them legacy_current_values; those are not reconstructed original historical prices. Malformed legacy values remain unavailable and must be reviewed before a configured budget can use them. Leagues with no budget retain legacy approvals.

Low-impact automatic approval

Enable only after configuring all intended safeguards:

  • Maximum Value Per Side
  • Maximum Value Difference
  • Maximum Assets Per Side
  • Minimum Round
  • Maximum Round
  • Attribute ceilings
  • Positions Excluded From Auto Approval

Enabling auto-approval requires all five value/asset/round fields and at least one attribute ceiling. Maximum assets must be at least one, and the minimum round cannot exceed the maximum. Missing required limits prevent enabling the feature; they do not mean unlimited approval. Excluded positions are optional.

Each side must contain an asset and satisfy every configured check to be auto-approved. A proposal outside these limits follows normal voting.

Contextual valuation (optional)

Contextual valuation is off by default and never changes a player’s stored base trade value. When enabled, an offer preview and its private trade audit can apply bounded adjustments:

  • Depth: compares the sending and receiving teams’ current number of players at the same normalized position. Each one-player difference changes the offer by 2.5%, up to the commissioner-selected cap.
  • Attributes: QB uses throw power; HB, WR, TE, CB, FS, and SS use speed. Each point above or below 85 changes the offer by 0.5%, subject to the same cap.
  • Contract: remaining term is already part of the base player-value formula and is shown in the audit rather than applied twice. Contract-demand fields are listed as an unsupported factor until their imported money units are documented; NeonSportz does not guess whether an amount is annual or total-contract.

The preview lists skipped inputs and unsupported factors. Contextual adjustments are skipped when a roster record is older than the configured freshness window or active fields are missing; no value is guessed. Contextual auto-approval is a separate opt-in on top of all low-impact rules. It uses depth, position attributes, and the existing base contract-term component—not the unsupported demand multiplier. Its default tolerance is 5%, calculated as abs(side A − side B) / max(side A, side B). A zero-total offer, stale input, or missing active context stays pending for normal review.

The private audit records when it was evaluated and the later approval path. Committee, forced, and decline decisions act on the creation-time valuation; an automatic approval after team agreement records a fresh evaluation at that point.

Player value formula

The displayed formula uses configurable tables for:

  • Years left.
  • Development trait.
  • Position.
  • Overall.
  • Salary and bonus.
  • Current- and next-year penalties.
  • Speed.
  • Age.
  • Abilities.

Select values carefully. Overweighting one variable can dominate every player score.

Position-relative speed

Speed is adjusted to a shared scale before applying your existing coefficients. An elite rating maps to 95, and every point below/above it moves the adjusted rating by the same amount. Exact 90–99 coefficient keys refer to this adjusted rating, not the original speed. This is a calculator policy, not an EA ranking.

Position Elite speed
QB, TE, LB (SAM/WILL/MIKE and legacy LB names) 88
DT 80
Edge/DE (including LE/RE) 87
Safeties (FS/SS/S) 92
HB/RB, WR, CB/DB 95
FB 85
Offensive line 75

For example, QB 88 and DT 80 use the elite band, while WR/CB 88 does not. QB 87 is one point below elite. Unknown positions and K/P retain the original speed scale; missing or malformed speeds contribute no modifier. Other valuation factors and configured coefficients are unchanged. Stored player values update on the next roster import or after saving value settings.

Ability values

  1. Search abilities.
  2. Optionally enable Only show abilities I’ve valued.
  3. Select an ability’s value.
  4. Enter the intended value.
  5. Save.

Review new Madden abilities after roster imports because unconfigured abilities may use default/neutral behavior.

Draft pick values

Configure Round 1 through Round 7 values. Future picks use:

  • Future Draft Pick Multiplier
  • Beyond Future Draft Pick Multiplier

Multipliers must remain between 0.0 and 1.0. A lower value discounts later-year picks more heavily.

The Commissioner Draft-Pick Inventory switch is separate from values. It opts a league into enforcing the commissioner-maintained owned-pick inventory; enable it only after entering complete, authoritative ownership. It does not create or import Madden ownership data.

Reset or clear values

  • Reset to Defaults: replaces configured tables with NeonSportz defaults.
  • Clear All Values: removes configured values.

Both can dramatically change every trade evaluation. Record current settings before confirming.

Trade Discord settings

Configure:

  • Pending Trade Channel.
  • Approved Trade Channel.
  • Denied Trade Channel.
  • Trade Role to mention for pending requests.

Use each Test action. The bot needs access to view and send in every selected channel.

Validate changes

  1. Save the settings.
  2. Reload Trade Settings.
  3. Open Trades → Create.
  4. Build a sample without submitting.
  5. Compare player/pick values and auto-approval result.
  6. Confirm thresholds match written league rules.

Troubleshooting

  • Values did not change: reload and confirm Save succeeded.
  • Unexpected auto-approval: review every maximum, round range, attribute ceiling, and excluded position.
  • Future pick too high/low: review both future multipliers and base round value.
  • Notification missing: test the exact pending/approved/denied channel.
  • Member exceeds limit unexpectedly: review Trade Reset Timing and stored season trade count.
Advertisement