Loans — sending and receiving players

A player loan in ManageFC moves a player to another club for a spell without a permanent transfer. The engine models it: a loan row ties the two clubs and the player to a season, with an optional fee, a salary-share percentage and an optional buy option. What it does not have, in the current build, is a way in — no screen creates a loan and no screen recalls one. Treat the feature as dormant; this article describes the model it will expose when it opens.

What the model holds

• The player and the two clubs — the owner who lends him and the club he joins — tied to the active season.
• A loan fee, paid by the receiving club to the owner. It defaults to zero and settles in one payment when the loan is created.
• A salary-share percentage, defaulting to 50%. It is stored, not applied: wages follow the player's club, so the receiving club carries his full weekly wage whatever the row says.
• An optional buy-option fee, recorded on the row. Nothing acts on it automatically — no screen offers the signing and no season-end rule triggers it.

How a loan ends

Two paths exist in the model. The owner can recall it: the player returns at once and the row is marked recalled. Or the season reset completes it — every active loan is closed and the player goes back to the club that lent him out. There is no loan length to set beyond the season itself.

Why the squad flag stays dark

The "on loan" badge and filter on the squad page read a flag the engine only ever writes as false — a loan moves the player's club directly and never sets it. Even with the model in place, a loaned player would appear as a normal member of the receiving squad. That is the code as it stands.

What to do meanwhile

With loans dormant, squad gaps are filled in the transfer market — a permanent signing, with the fee and wage levers the other articles describe. There is no temporary destination for a squad player today, and no loan market to shop in.