summaryrefslogtreecommitdiff
path: root/src/SMAPI/Events/IModEvents.cs
diff options
context:
space:
mode:
Diffstat (limited to 'src/SMAPI/Events/IModEvents.cs')
-rw-r--r--src/SMAPI/Events/IModEvents.cs12
1 files changed, 12 insertions, 0 deletions
diff --git a/src/SMAPI/Events/IModEvents.cs b/src/SMAPI/Events/IModEvents.cs
index cf2f8cb8..bd7ab880 100644
--- a/src/SMAPI/Events/IModEvents.cs
+++ b/src/SMAPI/Events/IModEvents.cs
@@ -3,13 +3,25 @@ namespace StardewModdingAPI.Events
/// <summary>Manages access to events raised by SMAPI.</summary>
public interface IModEvents
{
+ /// <summary>Events related to UI and drawing to the screen.</summary>
+ IDisplayEvents Display { get; }
+
/// <summary>Events linked to the game's update loop. The update loop runs roughly ≈60 times/second to run game logic like state changes, action handling, etc. These can be useful, but you should consider more semantic events like <see cref="Input"/> if possible.</summary>
IGameLoopEvents GameLoop { get; }
/// <summary>Events raised when the player provides input using a controller, keyboard, or mouse.</summary>
IInputEvents Input { get; }
+ /// <summary>Events raised for multiplayer messages and connections.</summary>
+ IMultiplayerEvents Multiplayer { get; }
+
+ /// <summary>Events raised when the player data changes.</summary>
+ IPlayerEvents Player { get; }
+
/// <summary>Events raised when something changes in the world.</summary>
IWorldEvents World { get; }
+
+ /// <summary>Events serving specialised edge cases that shouldn't be used by most mods.</summary>
+ ISpecialisedEvents Specialised { get; }
}
}