Modding:Common tasks - Revision history

imported>Margotbean: remove stub template

2026-04-09T10:32:29Z

remove stub template

← Older revision		Revision as of 10:32, 9 April 2026
Line 1:		Line 1:
	← [[Modding:Index\|Index]]		← [[Modding:Index\|Index]]
	~~{{stub\|Missing information<li>Requires more formal, objective language cleanup</li>}}~~

	This page covers how to do common tasks in SMAPI mods. '''Before reading this page, see the [[Modding:Modder Guide/Get Started\|Modder Guide]] and [[Modding:Modder Guide/Game Fundamentals\|Game Fundamentals]].'''		This page covers how to do common tasks in SMAPI mods. '''Before reading this page, see the [[Modding:Modder Guide/Get Started\|Modder Guide]] and [[Modding:Modder Guide/Game Fundamentals\|Game Fundamentals]].'''

imported>Pneuma163: /* Banner message */ overhaul on the HUDMessage section for accuracy

2026-04-09T00:29:56Z

Banner message: overhaul on the HUDMessage section for accuracy

← Older revision		Revision as of 00:29, 9 April 2026
Line 137:		Line 137:

	===Banner message===		===Banner message===
	HUDMessage are ~~those popups~~ in the lower left ~~hand~~ screen. ~~They have several constructors, which~~ are ~~briefly described: (some less relevant~~ constructors ~~are omitted)~~:		HUDMessage are popup notifications that appear in the lower left of the screen. There are three constructors you can use:

	<syntaxhighlight lang="c#">		<syntaxhighlight lang="c#">
	public HUDMessage(string message);		public HUDMessage(string message)
	public HUDMessage(string message, int whatType);		public HUDMessage(string message, int whatType)
	~~public HUDMessage(string type, int number, bool add, Color color, Item messageSubject = null);~~		public HUDMessage(string message, float timeLeft, bool fadeIn = false)
	public HUDMessage(string message~~, string leaveMeNull)~~
	~~public HUDMessage(string message, Color color~~, float timeLeft, bool fadeIn)
	</syntaxhighlight>		</syntaxhighlight>

			'''A brief description of each:'''
	~~The way <samp>~~HUDMessage~~</samp> uses these are explained here~~. ~~For further details, refer to the <samp>~~HUDMessage~~</samp> class implementation; however~~, the below ~~covers the most commonly used features~~.		*'' HUDMessage(string message)'' - A notification with no icon.
			*'' HUDMessage(string message, int whatType)'' - A notification with an icon depending on the type (see types below).
			*'' HUDMessage(string message, float timeLeft, bool fadeIn = false)'' - Displays a message for a set amount of time and optionally will fade in.

	[[File:HUDMessage-Types-InGame.png\|200px\|thumb\|right\|All of the types for HUDMessage as they appear in-game.]]		[[File:HUDMessage-Types-InGame.png\|200px\|thumb\|right\|All of the types for HUDMessage as they appear in-game.]]
Line 160:		Line 159:
	#Health (HUDMessage.health_type)		#Health (HUDMessage.health_type)

			'''Customizing a HUDMessage'''

	~~'''Color:''' The first two types do not provide an option~~ (~~they default to ''Color:OrangeRed''~~)~~, the fourth with the param 'leaveMeNull' displays as the same color as~~ the ~~game text~~.		You can further customize a HUDMessage by setting its public fields to specific values when (or after) you call the constructor.

			* message - The message text to show.
			* type - A key used to prevent multiple HUD messages from stacking, or null to use the item name.
			* timeLeft - The duration in milliseconds until the message should disappear.
			* transparency - The current opacity, from 0 (fully transparent) to 1 (fully opaque).
			* number - The count of the StardewValley.HUDMessage.messageSubject that was received, if applicable
			* whatType - The icon to show, matching a constant like StardewValley.HUDMessage.error_type.
			* achievement - Whether this is an achievement-unlocked message.
			* noIcon - Whether to hide the icon portion of the box.
			* messageSubject - The item that was received, if applicable.

	'''~~For specifics:~~'''		'''Examples'''
	*'' public HUDMessage(string type, int number, bool add, Color color, Item messageSubject = null);'' - This allows for expanded customization of the message. More often used for money.
	*'' public HUDMessage(string message, string leaveMeNull)'' - Also displays no icon.
	~~::Not only displaying no icon, this type of HUDMessage does not have the square on the left side; it will draw a simple rectangle with text within.~~
	*'' public HUDMessage(string message, Color color, float timeLeft, bool fadeIn)'' - Displays a message that fades in for a set amount of time.

			Add a new HUDMessage to show [[File:Error-image-ingame.png]] toaster popup.
	~~Note: For those of you who want a custom HUDMessage:~~
	~~- Almost all of these variables are public, excluding messageSubject, so feel free to customize!~~
	~~To modify them make a HUDMessage variable like so : HUDMessage <name> = new HUDMessage(<message>) ,now you can even animate them with code!~~

	~~For example: add~~ a new HUDMessage to show [[File:Error-image-ingame.png]] toaster popup.
	<syntaxhighlight lang="c#">		<syntaxhighlight lang="c#">
	Game1.addHUDMessage(new HUDMessage("MESSAGE", 3));		Game1.addHUDMessage(new HUDMessage("MESSAGE", HUDMessage.error_type));
	</syntaxhighlight>		</syntaxhighlight>

	~~Another example: add~~ a HUDMessage that shows up like a simple rectangle with no icon, and no square for ~~the~~ icon:		Add a HUDMessage that shows up like a simple rectangle with no icon (and no square for an icon) and a custom duration by setting values to specific fields:
	<syntaxhighlight lang="c#">		<syntaxhighlight lang="c#">
	Game1.addHUDMessage(new HUDMessage("MESSAGE", ~~"")~~); ~~// second parameter is the 'leaveMeNull' parameter~~		Game1.addHUDMessage(new HUDMessage("MESSAGE"){noIcon = true, timeLeft = 4000f});
	</syntaxhighlight>		</syntaxhighlight>

			For further details, refer to the <samp>HUDMessage</samp> class implementation.

	===Active clickable menu===		===Active clickable menu===

imported>Margotbean: add deleted link

2026-04-07T00:52:51Z

add deleted link

← Older revision		Revision as of 00:52, 7 April 2026
Line 6:		Line 6:
	==Basic techniques==		==Basic techniques==
	===Tracking changes to a value===		===Tracking changes to a value===
	Mods often need to know when a value has changed. A common approach to track changes to those values that do not have a SMAPI event is to create a private field to track it instead. This value should be updated using the update tick event.		Mods often need to know when a value has changed. A common approach to track changes to those values that do not have a SMAPI event is to create a private [https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/classes-and-structs/fields field] to track it instead. This value should be updated using the update tick event.

	See [[Modding:Modder Guide/APIs/Events#Change monitoring]] for an example.		See [[Modding:Modder Guide/APIs/Events#Change monitoring]] for an example.

Line 26:		Line 27:
	===Spawn an item on the ground===		===Spawn an item on the ground===

	An item can be spawnedon the ground with the <samp>[[Modding:~~Modder_Guide~~/~~Game_Fundamentals~~#~~GameLocation_et_al~~\|GameLocation]]</samp> class's <samp>dropObject</samp> method:		An item can be spawnedon the ground with the <samp>[[Modding:Modder Guide/Game Fundamentals#GameLocation et al\|GameLocation]]</samp> class's <samp>dropObject</samp> method:

	<syntaxhighlight lang='c#'>		<syntaxhighlight lang='c#'>

imported>Iciiboi: Formalizing text; More pending (too technical for me). Also, could anybody add the 'field' link back in 'Tracking Changes to a Value' as I could not save my edits with it due to being a new user?

2026-04-06T14:09:18Z

Formalizing text; More pending (too technical for me). Also, could anybody add the 'field' link back in 'Tracking Changes to a Value' as I could not save my edits with it due to being a new user?

← Older revision		Revision as of 14:09, 6 April 2026
Line 6:		Line 6:
	==Basic techniques==		==Basic techniques==
	===Tracking changes to a value===		===Tracking changes to a value===
	Mods often need to know when a value changed. ~~If there's no~~ SMAPI event ~~for the value, you can~~ create a private ~~[https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/classes-and-structs/fields~~ field] to track ~~the~~ value~~, and update it~~ using the update tick event.		Mods often need to know when a value has changed. A common approach to track changes to those values that do not have a SMAPI event is to create a private field to track it instead. This value should be updated using the update tick event.

	See [[Modding:Modder Guide/APIs/Events#Change monitoring]] for an example.		See [[Modding:Modder Guide/APIs/Events#Change monitoring]] for an example.

	==Items==		==Items==
	Items are objects which represent things which can be put in an inventory~~. Tools~~, ~~Crops~~, ~~etc~~.		Items are objects which represent things which can be put in an inventory, such as tools, crops, and ores.

	===Create an item (Object)===		===Create an item (Object)===
Line 27:		Line 26:
	===Spawn an item on the ground===		===Spawn an item on the ground===

	~~You~~ can ~~spawn an item on~~ the ground with the <samp>[[Modding:Modder_Guide/Game_Fundamentals#GameLocation_et_al\|GameLocation]]</samp> class's <samp>dropObject</samp> method:		An item can be spawnedon the ground with the <samp>[[Modding:Modder_Guide/Game_Fundamentals#GameLocation_et_al\|GameLocation]]</samp> class's <samp>dropObject</samp> method:

	<syntaxhighlight lang='c#'>		<syntaxhighlight lang='c#'>
Line 54:		Line 53:

	===Remove an item from an inventory===		===Remove an item from an inventory===
			This is dependent on the inventory. In most cases, this method is not called directly as the game provides functions for the player in the <samp>Farmer</samp> class (in the main namespace).

	~~This is dependent on the inventory - rarely will you be calling this directly, as the game has functions for this for the Player, located in Farmer (in the main namespace).~~		In most situations, this can be done by calling <samp>.removeItemFromInventory(Item)</samp>.

	~~To do so, in~~ most situations, ~~just call~~ .removeItemFromInventory(Item)

	==Locations==		==Locations==
Line 77:		Line 75:

	===Position===		===Position===
	A ~~Character~~'s position indicates the ~~Character~~'s coordinates in the current location.		A character's position indicates the character's coordinates in the current location.

	====Position Relative to the Map====		====Position Relative to the Map====
	Each location has an ``xTile`` map where the top-left corner of the map is ''(0, 0)'' and the bottom-right corner of the map is ''(location.Map.DisplayWidth, location.Map.DisplayHeight)'' in pixels.		Each location has an ``xTile`` map where the top-left corner of the map is ''(0, 0)'' and the bottom-right corner of the map is ''(location.Map.DisplayWidth, location.Map.DisplayHeight)'' in pixels.

	There are two ways to get a ~~Character~~'s position in the current location: by absolute position and by tile position.		There are two ways to get a character's position in the current location: by absolute position and by tile position.

	<code>Position.X</code> and <code>Position.Y</code> will give the XY coordinates in pixels.		<code>Position.X</code> and <code>Position.Y</code> will give the XY coordinates in pixels.
Line 117:		Line 115:
	==NPC==		==NPC==
	===Creating Custom NPCs===		===Creating Custom NPCs===
	Adding new ~~NPCs~~ involves editing ~~a number of~~ files:		Adding a new NPC involves editing several files:

	* New file: [[Modding:Dialogue\|Characters\Dialogue\<name>.json]] (See also [[Modding:Event data]])		* New file: [[Modding:Dialogue\|Characters\Dialogue\<name>.json]] (See also [[Modding:Event data]])
Line 129:		Line 127:
	* Add entries to [[Modding:Schedule data#Schedule points\|Data\animationDescriptions]] (if you want custom animations in their schedule)		* Add entries to [[Modding:Schedule data#Schedule points\|Data\animationDescriptions]] (if you want custom animations in their schedule)

	~~All of the above~~ can be ~~done~~ with an AssetRequested event or Content Patcher. If ~~you did all of this correctly~~, the game ~~will~~ spawn the NPC ~~in for you~~. ~~(If you didn't, it swallows the error)~~
			These changes can be implemented with an <samp>AssetRequested</samp> event or Content Patcher. If any required data is missing or incorrect, the game may fail to spawn the NPC without showing an error.

	==User-interface (UI)==		==User-interface (UI)==
Line 137:		Line 136:

	===Banner message===		===Banner message===
	HUDMessage are those popups in the lower left hand screen. They have several constructors, which ~~we will~~ briefly ~~go over here~~ (~~a few non-~~relevant constructors are ~~not included~~):		HUDMessage are those popups in the lower left hand screen. They have several constructors, which are briefly described: (some less relevant constructors are omitted):

	<syntaxhighlight lang="c#">		<syntaxhighlight lang="c#">
Line 148:		Line 147:


	~~So before we go over when you'd use them, I'm going to briefly note how the class~~ HUDMessage uses these. ~~(I encourage people~~ to ~~read~~ the class ~~if they have further questions~~, ~~but I doubt~~ most ~~of us will need to know more than this)~~		The way <samp>HUDMessage</samp> uses these are explained here. For further details, refer to the <samp>HUDMessage</samp> class implementation; however, the below covers the most commonly used features.


	[[File:HUDMessage-Types-InGame.png\|200px\|thumb\|right\|All of the types for HUDMessage as they appear in-game.]]		[[File:HUDMessage-Types-InGame.png\|200px\|thumb\|right\|All of the types for HUDMessage as they appear in-game.]]

	Types available:		'''Types available:'''
	#Achievement (HUDMessage.achievement_type)		#Achievement (HUDMessage.achievement_type)
	#New Quest (HUDMessage.newQuest_type)		#New Quest (HUDMessage.newQuest_type)
Line 161:		Line 160:


	Color: ~~Fairly obvious. It should be noted that while the~~ first two ~~don't give~~ an option (they default to ''Color:OrangeRed''), the fourth with the param 'leaveMeNull' displays as the same color as the game text.		'''Color:''' The first two types do not provide an option (they default to ''Color:OrangeRed''), the fourth with the param 'leaveMeNull' displays as the same color as the game text.


	For specifics:		'''For specifics:'''
	*'' public HUDMessage(string type, int number, bool add, Color color, Item messageSubject = null);'' - This allows for expanded customization of the message. More often used for money.		*'' public HUDMessage(string type, int number, bool add, Color color, Item messageSubject = null);'' - This allows for expanded customization of the message. More often used for money.
	*'' public HUDMessage(string message, string leaveMeNull)'' - Also displays no icon.		*'' public HUDMessage(string message, string leaveMeNull)'' - Also displays no icon.

imported>Margotbean at 19:22, 29 July 2023

2023-07-29T19:22:48Z

← Older revision		Revision as of 19:22, 29 July 2023
Line 119:		Line 119:
	Adding new NPCs involves editing a number of files:		Adding new NPCs involves editing a number of files:

	* New file: [[Modding:Dialogue\|Characters\Dialogue\<name>.json]] (See also [[Modding:~~Event_data~~]])		* New file: [[Modding:Dialogue\|Characters\Dialogue\<name>.json]] (See also [[Modding:Event data]])
	* New file: [[Modding:~~Schedule_data~~\|Characters\schedules\<name>.json]] (Note that the "s" in the "schedules" folder is lowercase!)		* New file: [[Modding:Schedule data\|Characters\schedules\<name>.json]] (Note that the "s" in the "schedules" folder is lowercase!)
	* New file: [[Modding:~~NPC_data~~#Portraits\|Portraits\<name>.png]]		* New file: [[Modding:NPC data#Portraits\|Portraits\<name>.png]]
	* New file: [[Modding:~~NPC_data~~#~~Overworld_sprites~~\|Characters\<name>.png]]		* New file: [[Modding:NPC data#Overworld sprites\|Characters\<name>.png]]
	* Add entries [[Modding:Dialogue#~~Engagement_dialogue~~\|Data\EngagementDialogue]] for NPCs that are marriable		* Add entries [[Modding:Dialogue#Engagement dialogue\|Data\EngagementDialogue]] for NPCs that are marriable
	* Add entry to [[Modding:~~NPC_data~~#~~Basic_info~~\|Data\NPCDispositions]]		* Add entry to [[Modding:NPC data#Basic info\|Data\NPCDispositions]]
	* Add entry to [[Modding:~~Gift_taste_data~~\|Data\NPCGiftTastes]]		* Add entry to [[Modding:Gift taste data\|Data\NPCGiftTastes]]
	* Add entries to [[Modding:Dialogue#~~Rain_dialogue~~\|Characters\Dialogue\rainy]]		* Add entries to [[Modding:Dialogue#Rain dialogue\|Characters\Dialogue\rainy]]
	* Add entries to [[Modding:~~Schedule_data~~#~~Schedule_points~~\|Data\animationDescriptions]] (if you want custom animations in their schedule)		* Add entries to [[Modding:Schedule data#Schedule points\|Data\animationDescriptions]] (if you want custom animations in their schedule)

	All of the above can be done with an AssetRequested event or Content Patcher. If you did all of this correctly, the game will spawn the NPC in for you. (If you didn't, it swallows the error)		All of the above can be done with an AssetRequested event or Content Patcher. If you did all of this correctly, the game will spawn the NPC in for you. (If you didn't, it swallows the error)
Line 154:		Line 154:

	Types available:		Types available:
	*1 - Achievement (HUDMessage.achievement_type)		#Achievement (HUDMessage.achievement_type)
	*2 - New Quest (HUDMessage.newQuest_type)		#New Quest (HUDMessage.newQuest_type)
	*3 - Error (HUDMessage.error_type)		#Error (HUDMessage.error_type)
	*4 - Stamina (HUDMessage.stamina_type)		#Stamina (HUDMessage.stamina_type)
	*5 - Health (HUDMessage.health_type)		#Health (HUDMessage.health_type)


Line 214:		Line 214:

	===DialogueBox===		===DialogueBox===
	[[File:~~DialogueBox_NoChoices_Example~~.jpg\|200px\|thumb\|right\|Example of DialogueBox without choices.]]A '''DialogueBox''' is a text box with a slightly larger, slightly boldfaced text, with "typewriter-like" effect.		[[File:DialogueBox NoChoices Example.jpg\|200px\|thumb\|right\|Example of DialogueBox without choices.]]A '''DialogueBox''' is a text box with a slightly larger, slightly boldfaced text, with "typewriter-like" effect.

	There are several variants, including ones with a dialogue/conversation choices.		There are several variants, including ones with a dialogue/conversation choices.
Line 400:		Line 400:
	You will notice that there is really very little difference in the code used for static mail and dynamic mail. The class that supports dynamic mail has a private dictionary collection for holding on to any mail content waiting to be injected. It could have been made public to allow mail to be added directly into the collection, but that is not good practice. Instead a public Add method was provided so that mail could be sent, so to speak, to the collection. This code is for a specific MOD, not a robust framework, so it isn't overly concerned with error handling. You can improve that based on your needs.		You will notice that there is really very little difference in the code used for static mail and dynamic mail. The class that supports dynamic mail has a private dictionary collection for holding on to any mail content waiting to be injected. It could have been made public to allow mail to be added directly into the collection, but that is not good practice. Instead a public Add method was provided so that mail could be sent, so to speak, to the collection. This code is for a specific MOD, not a robust framework, so it isn't overly concerned with error handling. You can improve that based on your needs.

	Notice the additional code in the Edit method, where any mail in the dynamicMail collection is injected into Stardew Valley's content. There will be no mail in the dynamicMail collection when the MOD is loaded (in this case) the first time. If you add mail after the original load, then the content will have to be reloaded by invalidating the cache. Refer to [[Modding:~~Modder_Guide~~/APIs/Content#Cache invalidation\|Cache invalidation]] for more details.		Notice the additional code in the Edit method, where any mail in the dynamicMail collection is injected into Stardew Valley's content. There will be no mail in the dynamicMail collection when the MOD is loaded (in this case) the first time. If you add mail after the original load, then the content will have to be reloaded by invalidating the cache. Refer to [[Modding:Modder Guide/APIs/Content#Cache invalidation\|Cache invalidation]] for more details.

	===Send a letter (using dynamic content)===		===Send a letter (using dynamic content)===

imported>AlSweigart: /* Creating Custom NPCs */ Added relevant internal links.

2023-07-29T14:56:29Z

Creating Custom NPCs: Added relevant internal links.

← Older revision		Revision as of 14:56, 29 July 2023
Line 119:		Line 119:
	Adding new NPCs involves editing a number of files:		Adding new NPCs involves editing a number of files:

	* New file: Characters\Dialogue\<name>		* New file: [[Modding:Dialogue\|Characters\Dialogue\<name>.json]] (See also [[Modding:Event_data]])
	* New file: Characters\schedules\<name>		* New file: [[Modding:Schedule_data\|Characters\schedules\<name>.json]] (Note that the "s" in the "schedules" folder is lowercase!)
	* New file: Portraits\<name>		* New file: [[Modding:NPC_data#Portraits\|Portraits\<name>.png]]
	* New file: Characters\<name>		* New file: [[Modding:NPC_data#Overworld_sprites\|Characters\<name>.png]]
	* Add entries Data\EngagementDialogue for NPCs that are marriable		* Add entries [[Modding:Dialogue#Engagement_dialogue\|Data\EngagementDialogue]] for NPCs that are marriable
	* Add entry to Data\NPCDispositions		* Add entry to [[Modding:NPC_data#Basic_info\|Data\NPCDispositions]]
	* Add entry to Data\NPCGiftTastes		* Add entry to [[Modding:Gift_taste_data\|Data\NPCGiftTastes]]
	* Add entries to Characters\Dialogue\rainy		* Add entries to [[Modding:Dialogue#Rain_dialogue\|Characters\Dialogue\rainy]]
	* Add entries to Data\animationDescriptions (if you want custom animations in their schedule)		* Add entries to [[Modding:Schedule_data#Schedule_points\|Data\animationDescriptions]] (if you want custom animations in their schedule)

	All of the above can be done with an AssetRequested event or Content Patcher. If you did all of this correctly, the game will spawn the NPC in for you. (If you didn't, it swallows the error)		All of the above can be done with an AssetRequested event or Content Patcher. If you did all of this correctly, the game will spawn the NPC in for you. (If you didn't, it swallows the error)

imported>Zekaat: Fix syntax, closing " missing

2023-06-21T01:32:22Z

Fix syntax, closing " missing

← Older revision		Revision as of 01:32, 21 June 2023
Line 288:		Line 288:
	private void OnAssetRequested(object? sender, AssetRequestedEventArgs e)		private void OnAssetRequested(object? sender, AssetRequestedEventArgs e)
	{		{
	if (e.NameWithoutLocale.IsEquivalentTo("Data/mail))		if (e.NameWithoutLocale.IsEquivalentTo("Data/mail"))
	{		{
	e.Edit(this.EditImpl);		e.Edit(this.EditImpl);

imported>Atravita: /* Send a letter (using dynamic content) */

2022-11-28T03:44:20Z

Send a letter (using dynamic content)

← Older revision		Revision as of 03:44, 28 November 2022
Line 415:		Line 415:
	Game1.mailbox.Add("MyModMailWool"); // Add to mailbox and we don't need to track it		Game1.mailbox.Add("MyModMailWool"); // Add to mailbox and we don't need to track it

	this.Helper.GameContent.InvalidateCache("Data\\mail");		this.Helper.GameContent.InvalidateCache("Data\\mail"); // note that as of SMAPI 3.14.0, this only invalidates the English version of the asset.
	}		}
	</syntaxhighlight>		</syntaxhighlight>

imported>Atravita: /* Send a letter (using dynamic content) */

2022-11-28T03:42:32Z

Send a letter (using dynamic content)

← Older revision		Revision as of 03:42, 28 November 2022
Line 415:		Line 415:
	Game1.mailbox.Add("MyModMailWool"); // Add to mailbox and we don't need to track it		Game1.mailbox.Add("MyModMailWool"); // Add to mailbox and we don't need to track it

	~~modHelper~~.~~Content~~.InvalidateCache("Data\\mail"); ~~// (modHelper was assigned in ModEntry for use throughout the class)~~		this.Helper.GameContent.InvalidateCache("Data\\mail");
	}		}
	</syntaxhighlight>		</syntaxhighlight>

imported>Atravita: /* Send a letter (using dynamic content) */

2022-11-28T03:40:46Z

Send a letter (using dynamic content)

← Older revision		Revision as of 03:40, 28 November 2022
Line 403:		Line 403:

	===Send a letter (using dynamic content)===		===Send a letter (using dynamic content)===

	~~To make uses of this class in your own project, thereby making the dynamic mail available, hook into the OnGameLaunch event, for example.~~

	~~<syntaxhighlight lang="c#">~~
	~~// Make this available to other methods in the class to access~~
	~~private MailData mailData = new MailData();~~

	~~/// <summary>~~
	~~/// Fires after game is launched, right before first update tick. Happens once per game session (unrelated to loading saves).~~
	~~/// All mods are loaded and initialized at this point, so this is a good time to set up mod integrations.~~
	~~/// </summary>~~
	~~private void OnGameLaunched(object sender, GameLaunchedEventArgs e)~~
	{
	~~Helper.Content.AssetEditors.Add(mailData);~~
	}
	~~</syntaxhighlight>~~

	You can hook into other events, such as "Day Starting" or "Day Ending" to generate the letter you want to send. Consider this simple example, that is only for illustration purposes.		You can hook into other events, such as "Day Starting" or "Day Ending" to generate the letter you want to send. Consider this simple example, that is only for illustration purposes.

← Older revision		Revision as of 10:32, 9 April 2026
Line 1:		Line 1:
	← [[Modding:Index\|Index]]		← [[Modding:Index\|Index]]
	~~{{stub\|Missing information<li>Requires more formal, objective language cleanup</li>}}~~

	This page covers how to do common tasks in SMAPI mods. '''Before reading this page, see the [[Modding:Modder Guide/Get Started\|Modder Guide]] and [[Modding:Modder Guide/Game Fundamentals\|Game Fundamentals]].'''		This page covers how to do common tasks in SMAPI mods. '''Before reading this page, see the [[Modding:Modder Guide/Get Started\|Modder Guide]] and [[Modding:Modder Guide/Game Fundamentals\|Game Fundamentals]].'''