Trades Overview
Trade pages, permissions, lifecycle, trade block, counts, and data rules.
What the trade system does
NeonSportz records a proposed trade, calculates configured values, collects agreement and votes, and stores a decision. It does not execute the roster move inside Madden.
Use:
Trade pages
- League Trades: pending, approved, and denied requests.
- Trade Counts: stored trade activity by team/member.
- Trade Block: players owners marked available.
- Create: build a new proposal.
- Individual Trade: assets, values, agreement, votes, and decision controls.
NeonSportz permissions
- Create A Trade: submit proposals.
- Vote On Trade: vote when workflow/settings allow.
- Force A Trade: use commissioner override.
- Edit League/Admin: edit trade settings.
Permissions are separate. An admin does not automatically represent the intent of an involved team; follow league policy.
Typical lifecycle
- A permitted member creates a request.
- Involved teams agree if agreement is required.
- Eligible voters approve or deny.
- Vote thresholds or a force decision determine status.
- Discord receives configured pending/approved/denied messages.
- Commissioners execute approved roster movement in Madden.
- Rosters/free agents are imported so NeonSportz reflects the actual transaction.
Calculated values are advisory
Trade values depend on league-configured weights and imported player/contract data. They are not a promise of competitive balance and do not override league rules.
Trade Block
Owners can toggle eligible players on/off the block. The league-wide view supports filters such as player, team, position, age, speed, overall, development, value, ordering, and result count.
Use /tradeblock for Discord output.
Trade Counts
Counts include trades recorded through NeonSportz. A trade performed only in Madden will not appear as a NeonSportz trade request unless it was also recorded in the workflow.