Note: This entity can be customized to fit bespoke needs. The fields described in this article may not coincide with the ones in your FORGE instance.
Where do I find the Player entities?
In the menu on the left, select the Player icon:
Note: The Player icon can be in a different place because of the custom entities in your FORGE instance.
Managing the Player entity
When creating and managing a Player entity, the entity-specific fields are:
Name: The player's given name as it appears in official rosters or media.
Surname: The family name used in editorial mentions and shirt printing.
Shirt Number: The jersey number assigned to the player for the current season or competition.
Date of Birth: The player’s birth date, often used to calculate age and eligibility.
Place of Birth: The city and country where the player was born.
Nationality: The player’s official nationality, often tied to international competition eligibility.
Club: The current team or organization the player represents.
Weight: The player’s weight, typically in kilograms, for physical profile purposes.
Height: The player’s height, typically in centimeters, for scouting and display.
Career Start Year: The year the player began their professional sports career.
Roles: Positions or roles the player is known to perform on the field.
Biography: A short editorial summary of the player’s background, achievements, and journey.
Shop Link: URL to purchase merchandise related to the player, such as shirts or memorabilia.
Facebook Profile: The player’s official Facebook page for fan interaction and updates.
Twitter Profile: The player’s official Twitter/X account for news and personal commentary.
Instagram Profile: Link to the player’s official Instagram account for personal and professional content.
Player Headshot: A portrait-style image used in player cards, articles, or broadcast graphics.
Player Nationality Flag: The visual representation of the player’s country, typically shown as a flag icon.
By scrolling down, the other fields display:
Translations
Player entities follow the language-independent workflow. The entity fields and publishing status can be different for each language.
For example, a Player can have different field values for the English UK language and for the French language. Also, the English UK Player can be published while the French one is unpublished.