translators
8,445
edits
Changes
Jump to navigation
Jump to search
Line 3:
Line 3: − + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 20:
Line 46: − + − + Line 31:
Line 57: − + Line 55:
Line 81: − |} − − ===Net fields=== − A 'net type' is any of several classes which Stardew Valley uses to sync data between players, and a 'net field' is any field or property of those types. They're named for the <code>Net</code> prefix in their type names. Net types can represent simple values like <tt>NetBool</tt>, or complex values like <tt>NetFieldDictionary</tt>. The game will regularly collect all the net fields reachable from <tt>Game1.netWorldState</tt> and sync them with other players. That means that many mod changes will be synchronised automatically in multiplayer. − − Although net fields can be implicitly converted to an equivalent value type (like <code>bool x = new NetBool(true)</code>), their conversion rules are counterintuitive and error-prone (e.g. <code>item?.category == null && item?.category != null</code> can both be true at once). To avoid bugs, never implicitly cast net fields; access the underlying value directly instead. The build config NuGet package should detect most implicit conversions and show an appropriate build warning. − − Here's how to access the data in some common net types: − {| class="wikitable" − |- − ! net type − ! description − |- − | <tt>NetBool</tt><br /><tt>NetColor</tt><br /><tt>NetFloat</tt><br /><tt>NetInt</tt><br /><tt>NetPoint</tt><br /><tt>NetString</tt> − | A simple synchronised value. Access the value using <tt>field.Value</tt>. − |- − | <tt>NetCollection<T></tt><br /><tt>NetList<T></tt><br /><tt>NetObjectList<T></tt> − | A list of <tt>T</tt> values. This implements the standard interfaces like [https://docs.microsoft.com/en-us/dotnet/api/system.collections.generic.ienumerable-1 <tt>IEnumerable<T></tt>] and [https://docs.microsoft.com/en-us/dotnet/api/system.collections.generic.ilist-1 <tt>IList<T></tt>], so you can iterate it directly like <code>foreach (T value in field)</code>. − |- − | <tt>NetLongDictionary<TValue, TNetValue></tt><br /><tt>NetPointDictionary<TValue, TNetValue></tt><br /><tt>NetVector2Dictionary<TValue, TNetValue></tt> − | Maps <tt>Long</tt>, <tt>Point</tt>, or <tt>Vector2</tt> keys to instances of <tt>TValue</tt> (the underlying value type) and <tt>TNetValue</tt> (the synchronised net type). You can iterate key/value pairs like <code>foreach (KeyValuePair<Long, TValue> pair in field.Pairs)</code> (replacing <tt>Long</tt> with <tt>Point</tt> or <tt>Vector2</tt> if needed). Line 91:
Line 96: − + Line 106:
Line 111: − + Line 120:
Line 125: − + − + − + − + Line 134:
Line 139: − + − + + + + + − : In UI mode, you should usually replace <tt>Game1.viewport</tt> with <tt>Game1.uiViewport</tt>. '''Don't''' do this if you'll adjust the positions for UI scaling separately, since double-conversion will give you incorrect results. You can convert between UI and non-UI coordinates using <tt>Utility.ModifyCoordinatesForUIScale</tt> and <tt>Utility.ModifyCoordinatesFromUIScale</tt>.+ + + − : You can test whether your mod accounts for this correctly by setting the zoom to maximum and the UI scale to minimum (i.e. have them at opposite values) or vice versa; in particular check any logic which handles pixel positions, like menus clicking.+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − + Line 154:
Line 201: − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + Line 189:
Line 236: − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + Line 242:
Line 289: − + − + − + Line 255:
Line 302: − + − + − + − + − + − + − + − + − + + + + +
remove {{upcoming|1.6}}
This page explains some of the Stardew Valley fundamentals that are useful for modders. See also [[Modding:Common tasks]].
This page explains some of the Stardew Valley fundamentals that are useful for modders. See also [[Modding:Common tasks]].
==Concepts==
==General concepts==
===Time format===
The in-game time of day is tracked using a version of [[wikipedia:24-hour clock|24-hour format]] informally called "26-hour time", measured in 10-minute intervals. This is the format used by <samp>Game1.timeOfDay</samp> in a [[Modding:Modder Guide/Get Started|C# mod]] or <samp><nowiki>{{Time}}</nowiki></samp> in a [[Modding:Content Patcher|Content Patcher pack]].
Sample times:
{| class="wikitable"
|-
! time value
! display text
|-
| 600
| 6:00 am
|-
| 1250
| 12:50 am
|-
| 1300
| 1:00 pm
|-
| 2600
| 2:00 am (before sleeping)
|}
The internal time will continue incrementing forever until you sleep (e.g. 6am the next day would be 3000 in that case).
===Tiles===
===Tiles===
The world is laid out as a grid of ''tiles''. Each tile has an (x, y) coordinate which represents its position on the map, where (0, 0) is the top-left tile. The ''x'' value increases towards the right, and ''y'' increases downwards. For example:
The world is laid out as a grid of ''tiles''. Each tile has an (x, y) coordinate which represents its position on the map, where (0, 0) is the top-left tile. The ''x'' value increases towards the right, and ''y'' increases downwards. For example:
[[File:Modding - creating an XNB mod - tile coordinates.png]]
[[File:Modding - creating an XNB mod - tile coordinates.png]]
You can use the {{Nexus mod|679|Debug Mode}} mod to see tile coordinates in-game.
===Positions===
===Positions===
| tile position
| tile position
| top-left corner of the map
| top-left corner of the map
| measured in [[#Tiles|tiles]]; used when placing things on the map (e.g. <tt>location.Objects</tt> uses tile positions).
| measured in [[#Tiles|tiles]]; used when placing things on the map (''e.g.,'' <samp>location.Objects</samp> uses tile positions).
|-
|-
| absolute position
| absolute position
| top-left corner of the map
| top-left corner of the map
| measured in pixels; used when more granular measurements are needed (e.g. NPC movement).
| measured in pixels; used when more granular measurements are needed (''e.g.,'' NPC movement).
|-
|-
| screen position
| screen position
|}
|}
Here's how to convert between them:
Here's how to convert between them (there are also helpful methods in Utility for some of these):
{| class="wikitable"
{| class="wikitable"
| tile || → || screen
| tile || → || screen
| <code>(x * Game1.tileSize) - Game1.viewport.X, (y * Game1.tileSize) - Game1.viewport.Y</code>
| <code>(x * Game1.tileSize) - Game1.viewport.X, (y * Game1.tileSize) - Game1.viewport.Y</code>
|}
|}
; Effect on SMAPI mods
; Effect on SMAPI mods
: In game code, this is represented by the <tt>Game1.options.zoomLevel</tt> field. Coordinates are generally adjusted for zoom level automatically, so you rarely need to account for this; but you can convert an unadjusted coordinate using <code>position * (1f / Game1.options.zoomLevel)</code> if needed.
: In game code, this is represented by the <samp>Game1.options.zoomLevel</samp> field. Coordinates are generally adjusted for zoom level automatically, so you rarely need to account for this; but you can convert an unadjusted coordinate using <code>position * (1f / Game1.options.zoomLevel)</code> if needed.
===UI scaling===
===UI scaling===
; Effect on SMAPI mods
; Effect on SMAPI mods
: The game has two distinct scaling modes depending on the context: ''UI mode'' and ''non-UI mode''. You can check <tt>Game1.uiMode</tt> to know which mode is active. You should be careful not to mix UI and non-UI coordinates to avoid tricky calculations; for example, do all your work in one coordinate system and then convert them once.
: The game has two distinct scaling modes depending on the context: ''UI mode'' and ''non-UI mode''. You can check <samp>Game1.uiMode</samp> to know which mode is active. You should be careful not to mix UI and non-UI coordinates to avoid tricky calculations; for example, do all your work in one coordinate system and then convert them once.
: A quick reference of common scenarios:
: A quick reference of common scenarios:
| UI mode
| UI mode
|-
|-
| [[Modding:Modder Guide/APIs/Events#Display.RenderingActiveMenu|<tt>RenderingActiveMenu</tt>]]<br />[[Modding:Modder Guide/APIs/Events#Display.RenderedActiveMenu|<tt>RenderedActiveMenu</tt>]]
| [[Modding:Modder Guide/APIs/Events#Display.RenderingActiveMenu|<samp>RenderingActiveMenu</samp>]]<br />[[Modding:Modder Guide/APIs/Events#Display.RenderedActiveMenu|<samp>RenderedActiveMenu</samp>]]
| UI mode
| UI mode
|-
|-
| [[Modding:Modder Guide/APIs/Events#Display.Rendering|<tt>Rendering</tt>]]<br />[[Modding:Modder Guide/APIs/Events#Display.Rendering|<tt>Rendered</tt>]]
| [[Modding:Modder Guide/APIs/Events#Display.Rendering|<samp>Rendering</samp>]]<br />[[Modding:Modder Guide/APIs/Events#Display.Rendering|<samp>Rendered</samp>]]
| depends on the context; check <tt>Game1.uiMode</tt>
| depends on the context; check <samp>Game1.uiMode</samp>
|-
|-
| <tt>draw</tt> method for world objects
| <samp>draw</samp> method for world objects
| non-UI mode
| non-UI mode
|-
|-
: If you need to draw UI when the game isn't in UI mode, you can explicitly set UI scaling mode:
: If you need to draw UI when the game isn't in UI mode, you can explicitly set UI scaling mode:
: <source lang="c#">Game1.game1.InUIMode(() =>
: <syntaxhighlight lang="c#">Game1.game1.InUIMode(() =>
{
{
// your UI draw code here
// your UI draw code here
});
});
</source>
</syntaxhighlight>
: In UI mode, you should usually replace <samp>Game1.viewport</samp> with <samp>Game1.uiViewport</samp>. '''Don't''' do this if you'll adjust the positions for UI scaling separately, since double-conversion will give you incorrect results. You can convert between UI and non-UI coordinates using <samp>Utility.ModifyCoordinatesForUIScale</samp> and <samp>Utility.ModifyCoordinatesFromUIScale</samp>.
: You can test whether your mod accounts for this correctly by setting the zoom to maximum and the UI scale to minimum (''i.e.,'' have them at opposite values) or vice versa; in particular check any logic which handles pixel positions, like menus clicking.
==Multiplayer concepts for C# mods==
===Net fields===
A 'net type' is any of several classes which Stardew Valley uses to sync data between players, and a 'net field' is any field or property of those types. They're named for the <code>Net</code> prefix in their type names. Net types can represent simple values like <samp>NetBool</samp>, or complex values like <samp>NetFieldDictionary</samp>. The game will regularly collect all the net fields reachable from <samp>Game1.netWorldState</samp> and sync them with other players. That means that many mod changes will be synchronised automatically in multiplayer.
Although net fields can be implicitly converted to an equivalent value type (like <code>bool x = new NetBool(true)</code>), their conversion rules are counterintuitive and error-prone (''e.g.,'' <code>item?.category == null && item?.category != null</code> can both be true at once). To avoid bugs, never implicitly cast net fields; access the underlying value directly instead. The build config NuGet package should detect most implicit conversions and show an appropriate build warning.
Here's how to access the data in some common net types:
{| class="wikitable"
|-
! net type
! description
|-
| <samp>NetBool</samp><br /><samp>NetColor</samp><br /><samp>NetFloat</samp><br /><samp>NetInt</samp><br /><samp>NetPoint</samp><br /><samp>NetString</samp>
| A simple synchronised value. Access the value using <samp>field.Value</samp>.
|-
| <samp>NetCollection<T></samp><br /><samp>NetList<T></samp><br /><samp>NetObjectList<T></samp>
| A list of <samp>T</samp> values. This implements the standard interfaces like [https://docs.microsoft.com/en-us/dotnet/api/system.collections.generic.ienumerable-1 <samp>IEnumerable<T></samp>] and [https://docs.microsoft.com/en-us/dotnet/api/system.collections.generic.ilist-1 <samp>IList<T></samp>], so you can iterate it directly like <code>foreach (T value in field)</code>.
|-
| <samp>NetLongDictionary<TValue, TNetValue></samp><br /><samp>NetPointDictionary<TValue, TNetValue></samp><br /><samp>NetVector2Dictionary<TValue, TNetValue></samp>
| Maps <samp>Long</samp>, <samp>Point</samp>, or <samp>Vector2</samp> keys to instances of <samp>TValue</samp> (the underlying value type) and <samp>TNetValue</samp> (the synchronised net type). You can iterate key/value pairs like <code>foreach (KeyValuePair<Long, TValue> pair in field.Pairs)</code> (replacing <samp>Long</samp> with <samp>Point</samp> or <samp>Vector2</samp> if needed).
|}
===Farmhand shadow world===
In [[multiplayer]], secondary players (''farmhands'') don't see most of the in-game locations. Instead their game creates a single-player copy of the world before they join, and then only fetches the [[farm|farm area]] and their current location (called ''active locations'') from the host player. The unsynchronized locations often don't match what players within those locations see.
This has some significant implications for C# mods:
* The <samp>Game1.locations</samp> list shows both active and shadow locations. While mods can access the shadow locations, these don't reflect the real data on the server and any changes to them won't be synced to the host.
* There may be duplicate copies of NPCs, horses, etc in the shadow world. Only those in active locations are 'real'.
* Game methods (like <samp>Game1.getCharacterByName</samp>) may not correctly distinguish between the 'real' and 'shadow' copies.
* When a farmhand warps to a location, the game fetches the real location from the host player before the warp completes. For a short while, the farmhand may have a null <samp>currentLocation</samp> field while they're between locations.
You can check whether a location is active using its <samp>IsActiveLocation</samp> method:
<syntaxhighlight lang="c#">
foreach (GameLocation location in Game1.locations)
{
if (!location.IsActiveLocation())
continue; // shadow location
...
}
</syntaxhighlight>
==Main classes==
==Main classes==
===Game1===
===Game1===
<tt>Game1</tt> is the game's core logic. Most of the game state is tracked through this class. Here are some of the most useful fields:
<samp>Game1</samp> is the game's core logic. Most of the game state is tracked through this class. Here are some of the most useful fields:
{| class="wikitable"
{| class="wikitable"
! purpose
! purpose
|-
|-
| <tt>Game1.player</tt>
| <samp>Game1.player</samp>
| <tt>Farmer</tt>
| <samp>Farmer</samp>
| The current player.
| The current player.
|-
|-
| <tt>Game1.currentLocation</tt>
| <samp>Game1.currentLocation</samp>
| <tt>[[#GameLocation|GameLocation]]</tt>
| <samp>[[#GameLocation|GameLocation]]</samp>
| The game location containing the current player. '''For a non-main player, may be <tt>null</tt> when transitioning between locations.'''
| The game location containing the current player. '''For a non-main player, may be <samp>null</samp> when transitioning between locations.'''
|-
|-
| <tt>Game1.locations</tt>
| <samp>Game1.locations</samp>
| <tt>IList<[[#GameLocation|GameLocation]]></tt>
| <samp>IList<[[#GameLocation|GameLocation]]></samp>
| All locations in the game. '''For a non-main player, use [[Modding:Modder Guide/APIs/Multiplayer#Get_active_locations|SMAPI's <tt>GetActiveLocations</tt> method]] instead.'''
| All locations in the game. '''For a non-main player, use [[Modding:Modder Guide/APIs/Multiplayer#Get_active_locations|SMAPI's <samp>GetActiveLocations</samp> method]] instead.'''
|-
|-
| <tt>Game1.timeOfDay</tt><br /><tt>Game1.dayOfMonth</tt><br /><tt>Game1.currentSeason</tt><br /><tt>Game1.year</tt>
| <samp>Game1.timeOfDay</samp><br /><samp>Game1.dayOfMonth</samp><br /><samp>Game1.currentSeason</samp><br /><samp>Game1.year</samp>
| <tt>int</tt><br /><tt>int</tt><br /><tt>string</tt><br /><tt>int</tt>
| <samp>int</samp><br /><samp>int</samp><br /><samp>string</samp><br /><samp>int</samp>
| The current time, day, season, and year. See also [[Modding:Modder Guide/APIs/Utilities#Dates|SMAPI's date utility]].
| The current time, day, season, and year. See also [[Modding:Modder Guide/APIs/Utilities#Dates|SMAPI's date utility]].
|-
|-
| <tt>Game1.itemsToShip</tt>
| <samp>Game1.itemsToShip</samp>
| <tt>IList<Item></tt>
| <samp>IList<Item></samp>
| Do not use (this is part of the save logic). See <tt>Game1.getFarm().getShippingBin(Farmer)</tt> instead.
| Do not use (this is part of the save logic). See <samp>Game1.getFarm().getShippingBin(Farmer)</samp> instead.
|-
|-
| <tt>Game1.activeClickableMenu</tt>
| <samp>Game1.activeClickableMenu</samp>
| <tt>IClickableMenu</tt>
| <samp>IClickableMenu</samp>
| The modal menu being displayed. Creating an <tt>IClickableMenu</tt> subclass and assigning an instance to this field will display it.
| The modal menu being displayed. Creating an <samp>IClickableMenu</samp> subclass and assigning an instance to this field will display it.
|}
|}
===<span id="GameLocation"></span>GameLocation et al===
===<span id="GameLocation"></span>GameLocation et al===
<ul>
<ul>
<li><tt>GameLocation</tt> represents an in-game location players can visit. Each location has a map (the tile layout), objects, trees, characters, etc. Here are some of the most useful fields for any location:
<li><samp>GameLocation</samp> represents an in-game location players can visit. Each location has a map (the tile layout), objects, trees, characters, etc. Here are some of the most useful fields for any location:
{| class="wikitable"
{| class="wikitable"
! purpose
! purpose
|-
|-
| <tt>Name</tt>
| <samp>Name</samp>
| <tt>string</tt>
| <samp>string</samp>
| The unique name for this location. (This isn't unique for constructed building interiors like cabins; see <tt>uniqueName</tt> instead.)
| The unique name for this location. (This isn't unique for constructed building interiors like cabins; see <samp>uniqueName</samp> instead.)
|-
|-
| <tt>IsFarm</tt>
| <samp>IsFarm</samp>
| <tt>bool</tt>
| <samp>bool</samp>
| Whether this is a farm, where crops can be planted.
| Whether this is a farm, where crops can be planted.
|-
|-
| <tt>IsGreenhouse</tt>
| <samp>IsGreenhouse</samp>
| <tt>bool</tt>
| <samp>bool</samp>
| Whether this is a greenhouse, where crops can be planted and grown all year.
| Whether this is a greenhouse, where crops can be planted and grown all year.
|-
|-
| <tt>IsOutdoors</tt>
| <samp>IsOutdoors</samp>
| <tt>bool</tt>
| <samp>bool</samp>
| Whether the location is outdoors (as opposed to a greenhouse, building, etc).
| Whether the location is outdoors (as opposed to a greenhouse, building, etc).
|-
|-
| <tt>characters</tt>
| <samp>characters</samp>
| [[#Net fields|<tt>NetCollection</tt>]] of <tt>NPC</tt>
| [[#Net fields|<samp>NetCollection</samp>]] of <samp>NPC</samp>
| The villagers, pets, horses, and monsters in the location.
| The villagers, pets, horses, and monsters in the location.
|-
|-
| <tt>critters</tt> (private)
| <samp>critters</samp>
| <tt>List</tt> of <tt>Critter</tt>
| <samp>List</samp> of <samp>Critter</samp>
| The temporary birds, squirrels, or other critters in the location.
| The temporary birds, squirrels, or other critters in the location.
|-
|-
| <tt>debris</tt>
| <samp>debris</samp>
| [[#Net fields|<tt>NetCollection</tt>]] of <tt>Debris</tt>
| [[#Net fields|<samp>NetCollection</samp>]] of <samp>Debris</samp>
| The floating items in the location.
| The floating items in the location.
|-
|-
| <tt>farmers</tt>
| <samp>farmers</samp>
| <tt>FarmerCollection</tt>
| <samp>FarmerCollection</samp>
| The players in the location.
| The players in the location.
|-
|-
| <tt>Objects</tt>
| <samp>Objects</samp>
| <tt>OverlaidDictionary</tt>
| <samp>OverlaidDictionary</samp>
| The placed fences, crafting machines, and other objects in the current location. (<tt>OverlaidDictionary</tt> is basically a [[#Net fields|<tt>NetVector2Dictionary</tt>]] with logic added to show certain quest items over pre-existing objects.)
| The placed fences, crafting machines, and other objects in the current location. (<samp>OverlaidDictionary</samp> is basically a [[#Net fields|<samp>NetVector2Dictionary</samp>]] with logic added to show certain quest items over pre-existing objects.)
|-
|-
| <tt>terrainFeatures</tt>
| <samp>terrainFeatures</samp>
| [[#Net fields|<tt>NetVector2Dictionary</tt>]] of <tt>TerrainFeature</tt>
| [[#Net fields|<samp>NetVector2Dictionary</samp>]] of <samp>TerrainFeature</samp>
| The trees, fruit trees, tall grass, tilled dirt (including crops), and flooring in the location. For each pair, the key is their tile position and the value is the terrain feature instance.
| The trees, fruit trees, tall grass, tilled dirt (including crops), and flooring in the location. For each pair, the key is their tile position and the value is the terrain feature instance.
|-
|-
| <tt>waterTiles</tt>
| <samp>waterTiles</samp>
| <tt>bool[,]</tt>
| <samp>bool[,]</samp>
| A multi-dimensional array which indicates whether each tile on the map is a lake/river tile. For example, <code>if (location.waterTiles[10, 20])</code> checks the tile at [[#Tiles|position]] (10, 20).
| A multi-dimensional array which indicates whether each tile on the map is a lake/river tile. For example, <code>if (location.waterTiles[10, 20])</code> checks the tile at [[#Tiles|position]] (10, 20).
|}</li>
|}</li>
<li><tt>BuildableGameLocation</tt> is a subclass of <tt>GameLocation</tt> for locations where players can construct buildings. In the vanilla game, only the farm is a buildable location. Here are the most useful fields:
<li><samp>BuildableGameLocation</samp> is a subclass of <samp>GameLocation</samp> for locations where players can construct buildings. In the vanilla game, only the farm is a buildable location. Here are the most useful fields:
{| class="wikitable"
{| class="wikitable"
! purpose
! purpose
|-
|-
| <tt>buildings</tt>
| <samp>buildings</samp>
| [[#Net fields|<tt>NetCollection</tt>]] of <tt>Building</tt>
| [[#Net fields|<samp>NetCollection</samp>]] of <samp>Building</samp>
| The buildings in the location.
| The buildings in the location.
|}</li>
|}</li>
<li><tt>Farm</tt> is a subclass of both <tt>GameLocation</tt> and <tt>BuildableGameLocation</tt> for locations where the player can have animals and grow crops. In the vanilla, there's only one farm location (accessed using <code>Game1.getFarm()</code>). Here are its most useful properties:
<li><samp>Farm</samp> is a subclass of both <samp>GameLocation</samp> and <samp>BuildableGameLocation</samp> for locations where the player can have animals and grow crops. In the vanilla, there's only one farm location (accessed using <code>Game1.getFarm()</code>). Here are its most useful properties:
{| class="wikitable"
{| class="wikitable"
! purpose
! purpose
|-
|-
| <tt>animals</tt>
| <samp>animals</samp>
| [[#Net fields|<tt>NetLongDictionary</tt>]] of <tt>FarmAnimal</tt>
| [[#Net fields|<samp>NetLongDictionary</samp>]] of <samp>FarmAnimal</samp>
| The farm animals currently in the location.
| The farm animals currently in the location.
|-
|-
| <tt>resourceClumps</tt>
| <samp>resourceClumps</samp>
| [[#Net fields|<tt>NetCollection</tt>]] of <tt>ResourceClump</tt>
| [[#Net fields|<samp>NetCollection</samp>]] of <samp>ResourceClump</samp>
| The giant crops, large stumps, boulders, and meteorites in the location.
| The giant crops, large stumps, boulders, and meteorites in the location.
|-
|-
| <tt>piecesOfHay</tt>
| <samp>piecesOfHay</samp>
| [[#Net fields|<tt>NetInt</tt>]]
| [[#Net fields|<samp>NetInt</samp>]]
| The amount of hay stored in silos.
| The amount of hay stored in silos.
|-
|-
| <tt>shippingBin</tt>
| <samp>shippingBin</samp>
| [[#Net fields|<tt>NetCollection</tt>]] of <tt>Item</tt>
| [[#Net fields|<samp>NetCollection</samp>]] of <samp>Item</samp>
| The items in the shipping bin.
| The items in the shipping bin.
|}</li>
|}</li>
<li>There are a number of subclasses for specific location (like <tt>AdventureGuild</tt>) which have fields useful for specific cases.</li>
<li>There are a number of subclasses for specific location (like <samp>AdventureGuild</samp>) which have fields useful for specific cases.</li>
</ul>
</ul>
[[es:Modding:Guía del Modder/Fundamentos del juego]]
[[ru:Модификации:Моддер гайд/Основы игры]]
[[zh:模组:制作指南/游戏基本架构]]