Soccerverse Wiki - Recent changes [en-gb]

Roadmap

Andrew.gore — Thu, 18 Jun 2026 13:36:10 GMT

The schedule

← Older revision		Revision as of 13:36, 18 June 2026
(2 intermediate revisions by the same user not shown)
Line 160:		Line 160:
	\| \|\| \|\| <span style="color: orange;"> Match Engine balancing - tactics</span> <span style="color: green;">(Done)</span> \|\| \|\| \|\| \|\|		\| \|\| \|\| <span style="color: orange;"> Match Engine balancing - tactics</span> <span style="color: green;">(Done)</span> \|\| \|\| \|\| \|\|
	\|-		\|-
	\| \|\| \|\| \|\| style="color: orange;" \| New App live \|\| \|\| \|\|		\| \|\| \|\| \|\| style="color: orange;" \| New App live <span style="color: green;">(Done)</span> \|\| \|\| \|\|
	\|-		\|-
	\| \|\| \|\| \|\| style="color: orange;" \| Mobile first UX revamp \|\| \|\| \|\|		\| \|\| \|\| \|\| style="color: orange;" \| Mobile first UX revamp \|\| \|\| \|\|
	\|-		\|-
	\| \|\| \|\| \|\| style="color: orange;" \| Major app issues fixed \|\| \|\| \|\|		\| \|\| \|\| \|\| style="color: orange;" \| Major app issues fixed <span style="color: green;">(Done)</span> \|\| \|\| \|\|
	\|-		\|-
	\| \|\| \|\| \|\| style="color: orange;" \| ~~Bloomberrg~~ Screen \|\| \|\| \|\|		\| \|\| \|\| \|\| style="color: orange;" \| Bloomberg Screen <span style="color: green;">(Done)</span> \|\| \|\| \|\|
	\|-		\|-
	\| \|\| \|\| \|\| style="color: orange;" \| New user onboarding funnel \|\| \|\| \|\|		\| \|\| \|\| \|\| style="color: orange;" \| New user onboarding funnel \|\| \|\| \|\|
Line 172:		Line 172:
	\| \|\| \|\| \|\| style="color: orange;" \| Ability to add remove friends in chat \|\| \|\| \|\|		\| \|\| \|\| \|\| style="color: orange;" \| Ability to add remove friends in chat \|\| \|\| \|\|
	\|-		\|-
	\| \|\| \|\| \|\| style="color: red;" \| GSP (back end game) ready for open sourcing [ready to press the button] \|\| \|\| \|\|		\| \|\| \|\| \|\| style="color: red;" \| GSP (back end game) ready for open sourcing [ready to press the button] <span style="color: green;">(Done)</span> \|\| \|\| \|\|
	\|-		\|-
	\| \|\| \|\| \|\| style="color: red;" \| Comprehensive APIs & Developer Support: \|\| \|\|		\| \|\| \|\| \|\| style="color: red;" \| Comprehensive APIs & Developer Support: <span style="color: green;">(Done)</span> \|\| \|\|
	\|-		\|-
	\| \|\| \|\| \|\| style="color: red;" \| Support UGC content and Tool building \|\| \|\|		\| \|\| \|\| \|\| \|\| style="color: red;" \| Support UGC content and Tool building <span style="color: green;">(Done)</span> \|\|
	\|-		\|-
	\| \|~~\| \|\| \|\| style="color: red;" \| Player rating changes \|\| \|\|~~		\| \|\| \|\| \|\| \|\| \|\| style="color: purple;" \| Players retiring
	\|-
	~~\| \|\| \|\| \|\| \|\| style="color: red;" \| Open source front end \|\|~~
	\|-
	~~\| \|\| \|\| \|\| \|\| style="color: red;" \| SV team running game nodes \|\|~~
	\|-
	\| \|\| \|\| \|\| \|\| style="color: purple;" \| Players retiring \|\|
	\|-		\|-
	\| \|\| \|\| \|\| \|\| \|\| style="color: red;" \| Tune economy and payouts using game parameter tool		\| \|\| \|\| \|\| \|\| \|\| style="color: red;" \| Tune economy and payouts using game parameter tool
	\|-		\|-
	\| \|\| \|\| \|\| \|\| \|\| style="color: red;" \| Remove transfer market restrictions		\| \|\| \|\| \|\| \|\| \|\| style="color: red;" \| Remove transfer market restrictions
			\|-
			\| \|\| \|\| \|\| \|\| \|\| style="color: red;" \| Player rating changes
	\|}		\|}

Line 206:		Line 202:
	\|-		\|-
	\| \|\| \|\| \|\| \|\| style="color: black;" \| Testing of end of season logic \|\|		\| \|\| \|\| \|\| \|\| style="color: black;" \| Testing of end of season logic \|\|
			\|-
			\| style="color: red;" \| Open source front end \|\| \|\| \|\| \|\| \|\| \|\|
			\|-
			\| style="color: red;" \| SV team running game nodes \|\| \|\| \|\| \|\| \|\| \|\|
	\|-		\|-
	\| style="color: red;" \| Open source the game code (GSP) \|\| \|\| \|\| \|\| \|\| \|\|		\| style="color: red;" \| Open source the game code (GSP) \|\| \|\| \|\| \|\| \|\| \|\|
Line 213:		Line 213:
	\| \|\| style="color: red;" \| Enable club SVC fundraising \|\| \|\| \|\| \|\| \|\|		\| \|\| style="color: red;" \| Enable club SVC fundraising \|\| \|\| \|\| \|\| \|\|
	\|-		\|-
	\| \|\| style="color: red;" \| ~~SV team give up ability to change game parameters \|\| \|\|~~ \|\| \|\| \|\|		\| \|\| \|\| style="color: red;" \| Nirvana \|\| \|\| \|\|
	\|-		\|-
	\| \|\| \|\| style="color: red;" \| ~~Nirvana \|\| \|\|~~ \|\|		\| \|\| \|\| \|\| \|\| style="color: red;" \| SV team give up ability to change game parameters \|\|
	\|}		\|}

	''Note: This gets us to Nirvana by the end of August. However, the ~~last two tasks in here we may want~~ to ~~do later, so~~ Nirvana ~~would also be later. For now we will keep it in August~~.''		''Note: This gets us to Nirvana by the end of August. However, the SV teams ability to change game parameters will be kept for a while after Nirvana.''

Club Fund Raising

Andrew.gore — Thu, 18 Jun 2026 10:34:08 GMT

Andrew.gore deleted page Club Fund Raising content was: "Influence Fundraising is a mechanism in Soccerverse that allows a '''club''' to issue '''new influence''' and sell it to users in exchange for '''SVC''' (Soccerverse Coin). The SVC raised goes directly into the club's balance, strengthening its finances. In return, contributors receive the newly-created influence, which gives them voting power and a claim on future...", and the only contributor was "Andrew.gore" (talk)

Main Page

Andrew.gore — Thu, 18 Jun 2026 10:33:43 GMT

Trading, Economy and Gameplay

← Older revision		Revision as of 10:33, 18 June 2026
Line 23:		Line 23:
	[[Player Morale - Concerns]] - Explains how the Player Morale system in Soccerverse works		[[Player Morale - Concerns]] - Explains how the Player Morale system in Soccerverse works

	[[Club ~~Fund Raising~~]] - An explanation of how the club fund raising feature works, to raise SVC for the club.		[[Club Fundraising]] - An explanation of how the club fund raising feature works, to raise SVC for the club.

	=== [[Backend Game Logic]] ===		=== [[Backend Game Logic]] ===

Club Fundraising

Andrew.gore — Thu, 18 Jun 2026 10:20:00 GMT

Created page with "Influence Fundraising is a mechanism in Soccerverse that allows a '''club''' to issue '''new influence''' and sell it to users in exchange for '''SVC''' (Soccerverse Coin). The SVC raised goes directly into the club's balance, strengthening its finances. In return, contributors receive the newly-created influence, which gives them voting power and a claim on future income payouts. Fundraising is exclusive to '''club influence''' — player influence cannot be diluted...."

New page

Influence Fundraising is a mechanism in Soccerverse that allows a '''club''' to issue '''new influence''' and sell it to users in exchange for '''SVC''' (Soccerverse Coin). The SVC raised goes directly into the club's balance, strengthening its finances. In return, contributors receive the newly-created influence, which gives them voting power and a claim on future income payouts.

Fundraising is exclusive to '''club influence''' — player influence cannot be diluted.

== Why Fundraising Exists ==

Fundraising serves two main purposes:

# '''Rescuing clubs in debt.''' At the end of each season, clubs with a negative balance automatically get a fundraise event started immediately (no vote needed). This creates new influence for SVC, injecting cash into the club so it can recover.
# '''Letting influencers raise SVC.''' Even healthy clubs can benefit from a fundraise — influencers can propose and vote for a fundraise to raise funds for transfers, wages, or other expenses. It is also a safeguard against "lost keys": if a club becomes unmanaged or locked, the end-of-season fundraise proposal ensures it is not permanently lost.

== The Lifecycle of a Fundraise ==

=== 1. Triggering ===

Fundraising can be triggered in one of two ways.

==== A. End-of-Season (Automatic) ====

At the end of each season, '''every club''' automatically gets a fundraise proposal or event:

* If the club is '''not in debt''', a '''proposal''' is created. Influencers vote on whether to accept the fundraise.
* If the club is '''in debt''', the fundraise '''bypasses voting entirely''' — a fundraise event is created immediately and goes straight to the contribution phase.

The amount of new influence to be created is calculated as a percentage (basis points) of the club's current outstanding influence, configured by the <code>seasonend-dilution-bp</code> parameter. The minimum raise is zero.

==== B. User-Proposed (Influencer Initiative) ====

Any influencer can propose a fundraise if they meet two requirements:

* They must own at least a certain '''relative percentage''' of all outstanding club influence (configured by the <code>dilution-min-bps</code> parameter, e.g. 5%).
* Enough time must have passed since the '''last user-proposed fundraise vote''' for that club (configured by <code>min-seconds-between-dilution-votes</code>).

The proposing influencer specifies:

* '''<code>n</code>''': How much new influence to create (between 1 and a maximum, which is a percentage of outstanding influence configured by <code>dilution-max-bps</code>).
* '''<code>mr</code>''' (minimum raise): The minimum amount of SVC that must be raised. If the total contributions fall short of this, the fundraise fails and all SVC is refunded.

=== 2. Proposal Phase (for non-debt clubs) ===

When a user proposes a fundraise, it goes through a '''governance proposal''' lifecycle:

* '''Upcoming phase''': The proposal is created but voting hasn't started yet. During this time, the proposer (or any other eligible influencer) can '''amend''' the proposal by adding more fundraise options (different <code>n</code> and <code>mr</code> combinations). The upcoming phase lasts for <code>dilution-upcoming-seconds</code>.
* '''Voting phase''': After the upcoming phase, the proposal enters voting for <code>dilution-voting-seconds</code>. Influencers vote with their existing influence (1 influence = 1 vote). Once voting ends, the winning option is executed.
* '''The ballot''': Every fundraise proposal has a '''"do nothing"''' option (option 0 for user proposals, option 1 for end-of-season proposals). If the winning option is "do nothing", no fundraise event is created.

For end-of-season proposals, the default option (option 0) is the fundraise itself, meaning it passes unless influencers actively vote it down.

=== 3. The Fundraise Event (Contribution Phase) ===

Once a fundraise proposal passes (or is triggered directly for clubs in debt), a '''fundraise event''' is created and becomes active. It has:

* A '''number of new influence''' to be created.
* A '''minimum raise''' amount (0 for end-of-season fundraises; set by the proposer for user-proposed ones).
* An '''end time''', calculated as <code>current_time + dilution-seconds</code>.

During this phase, '''any user''' can contribute SVC to the event. They send a move with:

<syntaxhighlight lang="json">
{
"dc": {
"a": <amount>,
"e": <event_id>
}
}
</syntaxhighlight>

Key points about contributing:

* Contributions are '''not bids''' — you don't specify a price per influence. The price is determined '''after''' the event ends, based on total SVC raised divided by the amount of influence.
* Users can '''top up''' their contribution at any time while the event is active. Multiple contributions from the same user are combined into one entry.
* The contributed SVC is '''reserved''' (locked) from the user's balance immediately.

=== 4. Settlement (After the End Time) ===

When the block time reaches or passes the event's <code>end_time</code>, the event is finalised:

# '''Effective price''' is calculated: <code>total_contributions / number_of_shares</code>, rounded '''down''' to whole SVC units.
# '''Success check''': The event succeeds if:
#* At least one user contributed, '''and'''
#* <code>shares_sold × price ≥ minimum_raise</code>
#: If the event '''fails''', all SVC is refunded and no influence is created.
# '''Influence distribution''' (if successful): Contributors are processed in order of '''largest contribution first''', then '''earliest contribution''' as a tie-breaker. Each contributor buys as many whole influence as their contribution allows at the effective price:
#* <code>shares_bought = min(remaining_shares, contribution / price)</code>
#* <code>SVC_spent = shares_bought × price</code>
#* <code>refund = contribution - SVC_spent</code>
#: The refund is '''not taken from the user's balance''' — only the actually spent SVC is deducted.
# '''Club gets the money''': The total SVC raised (all contributions minus all refunds) is transferred to the club's balance as a '''"cash injection"''' (visible on the club's balance sheet).
# '''Contributors get influence''': New influence is minted and credited to contributors' balances. This is '''new influence''' — it increases the total supply above the base supply of 1,000,000.

== Key Parameters ==

{| class="wikitable"
! Parameter !! Description
|-
| <code>dilutions-enabled</code> || Master switch (0 = off, 1 = on)
|-
| <code>dilution-min-bps</code> || Minimum influence holding (in basis points) required to propose a fundraise
|-
| <code>dilution-max-bps</code> || Maximum new influence as basis points of outstanding supply
|-
| <code>dilution-upcoming-seconds</code> || Duration of the "upcoming" (amendable) phase
|-
| <code>dilution-voting-seconds</code> || Duration of the voting phase
|-
| <code>dilution-seconds</code> || Duration of the contribution window
|-
| <code>min-seconds-between-dilution-votes</code> || Cooldown between user-proposed fundraise votes per club
|-
| <code>seasonend-dilution-bp</code> || New influence to create at season end, as basis points of outstanding
|}

== Edge Cases and Important Behaviours ==

* '''No contributors''': If nobody contributes to a fundraise event, it fails. No influence is created and no money changes hands.
* '''Zero price''': If the total contributions are less than the amount of influence, the effective price rounds down to 0. In this case, the single largest (and earliest) contributor gets '''all the influence for free''' (but still gets their SVC refunded — effectively free influence).
* '''Minimum raise not met''': Even if many users contribute, if the total SVC that would actually be spent (after rounding) falls below the minimum raise, the event fails. All SVC is refunded.
* '''Individual rounding''': Because influence is bought in whole units at a rounded-down price, it is possible that less influence is sold than was available. E.g. with 1 influence available and a price of 3 SVC/influence, three contributors each putting in 1 SVC would each be able to buy 0 influence (1 / 3 = 0), so the raise would fail despite total bids exceeding the minimum.
* '''Beyond base supply''': Fundraising can push the total outstanding influence above the base supply of 1,000,000. This is intentional — fundraising is how supply grows.
* '''Voting power for proposals''': The quorum for proposing fundraises is always based on '''base supply''' (1,000,000) if fewer influence than that is minted. This prevents a small influencer from proposing a fundraise when very little influence is in circulation.
* '''End-of-season proposals start immediately''': Unlike user-proposed ones, they have no "upcoming" phase and go straight to voting (<code>start_time = now + 1 second</code>). They also cannot be amended.
* '''Balance sheet entries''': For the club, the fundraise creates a <code>cash_injection</code> entry. For the user, it creates a fundraise entry under their balance sheet, and a fundraise entry in the influence transaction history.

== User-Facing Move Summary ==

{| class="wikitable"
! Action !! Move JSON
|-
| Propose fundraise || <code>{"p": {"s": {"club": <id>}, "dilute": {"n": <num>, "mr": <min_raise>}}}</code>
|-
| Contribute to event || <code>{"dc": {"a": <amount>, "e": <event_id>}}</code>
|-
| Vote on proposal || <code>{"v": {"p": <proposal_id>, "o": <option_id>}}</code>
|}

== Summary ==

Influence fundraising is a governance-based mechanism for clubs to raise capital by issuing new influence. It operates in two modes: '''automatic end-of-season''' (to prevent clubs from being stuck in debt) and '''user-proposed''' (for active influencer-driven fundraising). The process is: propose → vote → contribute → settle. At settlement, an effective price per influence is determined by dividing total contributions by the number of influence; contributors receive influence in proportion to their contribution (largest first); any unspent SVC is refunded; and the club receives the proceeds.

[[Category:Game Mechanics]]

Main Page

Andrew.gore — Wed, 17 Jun 2026 16:20:30 GMT

Trading, Economy and Gameplay

← Older revision		Revision as of 16:20, 17 June 2026
(One intermediate revision by the same user not shown)
Line 17:		Line 17:
	* Future Evolution - Plans for game development		* Future Evolution - Plans for game development

	[[~~Influence_Issues~~]] - Issues that effect your SVC payouts in Club and Player influence		[[Influence Issues]] - Issues that effect your SVC payouts in Club and Player influence

	[[Influence Valuation]] - A 'How To' of valuing both Club and Player influence		[[Influence Valuation]] - A 'How To' of valuing both Club and Player influence

			[[Player Morale - Concerns]] - Explains how the Player Morale system in Soccerverse works

			[[Club Fund Raising]] - An explanation of how the club fund raising feature works, to raise SVC for the club.

	=== [[Backend Game Logic]] ===		=== [[Backend Game Logic]] ===

Player Morale - Concerns

Andrew.gore — Fri, 12 Jun 2026 15:46:09 GMT

Show changes

Player Morale - Concerns

Andrew.gore — Fri, 12 Jun 2026 14:30:16 GMT

Created page with "== Summary == This page explains the '''Player Morale''' system in Soccerverse, including the three morale states (happy, concerned, unhappy) and how the daily '''Morale Checker''' works. It details when and how agents can set a player to ‘unhappy’ as leverage against the manager (e.g. to maximise SVC payouts), and the conditions that trigger ‘concerned’ status. == Morale States == A player can have morale in one of three states: * '''Happy''' * '''Concerned'''..."

New page

== Summary ==
This page explains the '''Player Morale''' system in Soccerverse, including the three morale states (happy, concerned, unhappy) and how the daily '''Morale Checker''' works. It details when and how agents can set a player to ‘unhappy’ as leverage against the manager (e.g. to maximise SVC payouts), and the conditions that trigger ‘concerned’ status.

== Morale States ==
A player can have morale in one of three states:
* '''Happy'''
* '''Concerned'''
* '''Unhappy'''

'''Note''': Free bench and retired players will '''never''' have a concern.

== Morale Checker ==
The game runs a '''morale checker at 3am UTC every day'''.

An agent can only set a player’s morale to '''‘unhappy’''' if the player has a valid '''‘concern’'''. This gives the agent leverage against the manager (low wage, lack of games, or playing in a bad league) to try and maximise SVC payouts.

The game (not the agent) is the only one that can set morale to '''‘concerned’''', and it does so under specific conditions.

=== How the Checker Works ===
The morale checker will keep the player on '''‘happy’''' unless one of the following concerns exists:

* The player could be on a '''better contract / wage'''
* The player could be in a '''better league''': player rating is more than 15 above the league’s average
* The player is '''not playing enough league minutes''':
** If one of the best 11 players in the squad (at least 55% minutes)
** If the 12th to 18th best player in the squad (at least 35% minutes)
** If not in the top 18 best players (at least 10% of minutes)

If failing any of these checks then morale will be set to '''‘concerned’''' unless already set to be '''‘unhappy’''' by the agent, in which case it stays as ‘unhappy’.

=== Resolution of Concerns ===
If a player's concerns later clear (e.g. the manager raises the wage or starts playing him), the daily morale checker forces morale back to '''happy''' — this '''overrides''' an agent's "unhappy".

An agent's leverage evaporates once the underlying concern is resolved.

<div style="background:#f8f9fa; border:1px solid #aaa; padding:10px; margin:10px 0;">
''Note: The morale checker runs daily at 3am UTC.''
</div>

== Better League Note ==
* The '''"league average"''' used to compare a player against is the average of the club strength as they were in '''season 1'''. It doesn’t track the current season’s actual league strength.
* The values used can be found in column I here: '''average_league_rating'''

== Minutes Played Notes ==
* '''Injuries''' — If a player has ever been injured during a season, it will only consider games that he could have played for the club.
* '''Transfers''' — If a player has been transferred in during a season, it will only consider games that he could have played for the club.

<div style="background:#f8f9fa; border:1px solid #aaa; padding:10px; margin:10px 0;">
''Note: These adjustments ensure fair evaluation of playing time.''
</div>

== Key ==
{| class="wikitable"
! Style !! Meaning
|-
| '''Bold''' || Most important checks / states
|-
| ''Italic'' || Additional detail / notes
|}