106 742
правки
Изменения
Модификации:Моддер гайд/Основы игры (просмотреть исходный код)
Версия 00:51, 26 октября 2021
, 00:51, 26 октября 2021Замена текста — «{| class» на «{|class»
The game uses three related coordinate systems:
The game uses three related coordinate systems:
{| class="wikitable"
{|class="wikitable"
|-
|-
! coordinate system
! coordinate system
Here's how to convert between them:
Here's how to convert between them:
{| class="wikitable"
{|class="wikitable"
|-
|-
!colspan="3"| conversion
!colspan="3"| conversion
Here's how to access the data in some common net types:
Here's how to access the data in some common net types:
{| class="wikitable"
{|class="wikitable"
|-
|-
! net type
! net type
The player can set an in-game zoom level between 75% and 200%, which adjusted the size of all pixels shown on the screen. For example, here's a player with the same window size at different zoom levels:
The player can set an in-game zoom level between 75% and 200%, which adjusted the size of all pixels shown on the screen. For example, here's a player with the same window size at different zoom levels:
{| class="wikitable"
{|class="wikitable"
|-
|-
! min zoom level (75%)
! min zoom level (75%)
The player can scale the UI between 75% and 150%, separately from and alongside the [[#Zoom level|zoom level]]. That adjusts the size of pixels shown on the screen for UI elements only. For example, here's a player with the same window size at different UI scaling levels:
The player can scale the UI between 75% and 150%, separately from and alongside the [[#Zoom level|zoom level]]. That adjusts the size of pixels shown on the screen for UI elements only. For example, here's a player with the same window size at different UI scaling levels:
{| class="wikitable"
{|class="wikitable"
|-
|-
! min UI scale (75%)
! min UI scale (75%)
: A quick reference of common scenarios:
: A quick reference of common scenarios:
: {| class="wikitable"
: {|class="wikitable"
|-
|-
! context
! context
<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:
<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:
{| class="wikitable"
{|class="wikitable"
|-
|-
! field
! field
<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><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:
{| class="wikitable"
{|class="wikitable"
|-
|-
! field
! field
<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><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:
{| class="wikitable"
{|class="wikitable"
|-
|-
! field
! field
<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><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:
{| class="wikitable"
{|class="wikitable"
|-
|-
! field
! field