Enter the offset of the specified address. You can think of it as putting an address that will be a kind of starting point here.
输入指定地址的偏移量。您可以将其视为放置一个地址，该地址将作为此处的起点。

Write the value to be moved from the top offset.
写入要从 top offset 移动的值。

Determines the number of bytes that one is responsible for. By default there are 1 to 4.
确定一个负责的字节数。默认情况下，有 1 到 4。
This byte is often seen in offsets, so many beginners are confused. To define it accurately, it can be seen as "the range covered." As a simple example, offset 0x006636B8, which is in charge of a unit's ground weapon, uses 1 byte per unit, that is, one space (0 to 255). On the other hand, the 0x00664080 offset, which is responsible for the advanced flag of the unit, uses 4 bytes per unit, that is, four spaces (0 ~ 4294967295, 2^32-1) at the same time. That's a lot of space for each unit. Since one death table always contains 4 bytes, four 1-byte offsets can be handled at the same time, and one 4-byte offset can be handled.
这个字节经常出现在 offsets 中，所以很多初学者都感到困惑。为了准确定义它，它可以看作是 “覆盖的范围”。举个简单的例子，负责单位地面武器的偏移量 0x006636B8 每个单位使用 1 个字节，即一个空格（0 到 255）。另一方面，负责单元高级标志的 0x00664080 偏移量每个单元使用 4 个字节，即四个空格 （0 ~ 4294967295， 2^32-1） 同时。每个单元都有很多空间。由于一个 death table 始终包含 4 个字节，因此可以同时处理四个 1 字节的偏移量，并且可以处理一个 4 字节的偏移量。

Determines whether to use EPD ( Extended Layer Death ) or not . What else is EPD? For those who do, normally EUDs use the high-level unit's ID, but enabling EPD usage leaves the unit ID at 0 and moves it into the player number. Basically, when using EUD, the following formula is used. (as of 1.16.1)
确定是否使用 EPD （ Extended Layer Death ） 。EPD 还是什么？对于这样做的玩家，通常 EUD 使用高级单位的 ID，但启用 EPD 使用会将单位 ID 保留为 0 并将其移动到玩家编号中。基本上，在使用 EUD 时，使用以下公式。（自 1.16.1 起）

파일:/20150705_71/sindaehyeon_1436038365729k15XV_PNG/EUDTrigB.png
文件：/20150705_71/sindaehyeon_1436038365729k15XV_PNG/EUDTrigB.png
The arrow pointing down adds up the offset at the top and the object id added by the byte to turn it into a player number and unit id.
向下的箭头将顶部的偏移量和字节添加的对象 ID 相加，以将其转换为玩家编号和单位 ID。
파일:/20150705_34/sindaehyeon_14360386068618tbTF_PNG/EUDTrigC.png
파일：/20150705_34/sindaehyeon_14360386068618tbTF_PNG/EUDTrigC.png
The upward arrow changes the player number and unit ID at the bottom to an offset at the top. At this time, the offset is always a multiple of 4 because it comes out as an offset corresponding to the first space (1 byte).
向上箭头将底部的玩家编号和单位 ID 更改为顶部的偏移量。此时，偏移量始终是 4 的倍数，因为它显示为对应于第一个空格（1 字节）的偏移量。

player number. When EPD use is disabled, P is added in front of it like P1, P2, P3, ..., and the range between 1 and 12 appears, and when EPD use is enabled, P disappears. For reference, when creating a death table, if P (Player) is attached, remove P and subtract 1 from the value. P1 corresponds to the value 0 and P12 corresponds to the value 11.
玩家编号。禁用 EPD 使用时，P 会像 P1、P2、P3 等一样添加到其前面，并显示 1 到 12 之间的范围，而当启用 EPD 使用时，P 会消失。作为参考，在创建死亡表时，如果附加了 P （Player），请删除 P 并从值中减去 1。P1 对应于值 0，P12 对应于值 11。

unit ID. Enable the use of EPD and always come out as 0 when outputting.
启用 EPD 的使用，并在输出时始终显示为 0。

Directly shows the location where the corresponding offset is specified. When outputting, the number is shown in red, and the range shown in red varies according to the number of bytes, which confuses people with bytes. However, if you understand that the address and the death table deal with 4 bytes, this too can be easily solved. The following table is a simple example.
直接显示指定了相应偏移量的位置。输出时，数字显示为红色，红色显示的范围根据字节数而变化，这使人们与字节混淆。但是，如果您了解 address 和 death table 处理 4 个字节，这也很容易解决。下表是一个简单的示例。

That is, if the color changes at the third digit, the third space is a multiple of 65536, so multiply the desired value by 65536.
也就是说，如果颜色在第三位数字处发生变化，则第三个空格是 65536 的倍数，因此将所需值乘以 65536。

Calculate the memory offset and write the output player number. Only numbers must be written down, and both negative (-) and positive (+) numbers can be recognized.
计算内存偏移量并写入输出玩家编号。只需写下数字，并且负数 （-） 和正数 （+） 都可以识别。

Calculate the memory offset and write the output unit ID. Only numbers must be written down, and both negative (-) and positive (+) numbers can be recognized.
计算内存偏移量并写入输出单元 ID。只需写下数字，并且负数 （-） 和正数 （+） 都可以识别。

If it is conditional, you can set At Least, At Most, and Exactly based on the value. In the case of the execution part, 'Add', 'Subtract', and 'SetTo' can change the value or set it to a specified value. As mentioned above, one death table handles a total of four spaces, so the conditional case is often used for offsets of 4 bytes or more. That's good for safety. Also, some memory may not be restored even after the game is over.[3] It is recommended to use SetTo whenever possible.
如果它是有条件的，则可以根据该值设置 At Least、At Most 和 Exactly 。对于执行部分，'Add'、'Subtract' 和 'SetTo' 可以更改值或将其设置为指定值。如上所述，一个 death table 总共处理四个空格，因此条件大小写通常用于 4 个字节或更大的偏移量。这对安全有好处。此外，即使在游戏结束后，某些内存也可能无法恢复。[3] 建议尽可能使用 SetTo。

In the case of conditional, enter the value to be the standard, and in the case of execution, the value to be changed or set from the existing value. That is, the part that determines the number of units killed / the number of units killed on the death table. When used as an execution unit, StarCraft Editor does not recognize values higher than 0x7FFFFFFF (decimal number 2147483647), but it can recognize negative numbers. That is, if you put 0xFFFFFFFE inside, it changes to -2.
在条件情况下，输入要作为标准的值，在执行的情况下，输入要从现有值更改或设置的值。即，确定死亡表上被杀死的单位数/杀死的单位数的部分。当用作执行单元时，StarCraft Editor 无法识别大于 0x7FFFFFFF （十进制数 2147483647） 的值，但可以识别负数。也就是说，如果你把 0xFFFFFFFE 放在里面，它会变成 -2。

The correct value is output to the death table. The death table is added to the conditional column in case of conditional part, and to the execution part column in case of execution part. Once inserted, it does not disappear until the reset button is pressed, and even if the content is deleted from the text format, it is still stored inside.
将正确的值输出到 death 表。如果是条件部分，则 death 表将添加到 conditional 列，如果是执行部分，则添加到 execution part 列。插入后，它不会消失，直到按下重置按钮，即使内容从文本格式中删除，它仍然存储在里面。

The created death table is displayed in StarForge or similar text trigger format. When clicked, there are two cells placed in parallel, and a conditional death table is created in the upper column and an executive death table in the lower column. It can be used as a temporary notepad because it can not only be displayed in text format, but can also be directly copied, and writing and deleting is possible.
创建的死亡表以 StarForge 或类似的文本触发器格式显示。单击时，将有两个单元格平行放置，并在上列创建一个条件死亡表，在下列创建一个执行死亡表。它可以用作临时记事本，因为它不仅可以以文本格式显示，还可以直接复制，并且可以写入和删除。

Shows the created death table in a organized death table format. When clicked, there are two cells placed in series, and a conditional death table is created in the left column and an executive death table in the right column.
以有序的死亡表格式显示创建的死亡表。单击后，将有两个单元格按顺序放置，并在左列中创建一个条件死亡表，在右列中创建一个执行死亡表。

Create one trigger file (*.trg) containing all created death tables. The saved file can be used by loading it with a general editor. At this time, no player settings are set, and if you save it without anything, an empty trigger file with neither conditional nor execution part is created.
创建一个包含所有已创建的死亡表的触发器文件 （*.trg）。可以通过使用常规编辑器加载保存的文件来使用保存的文件。此时，没有设置播放器设置，如果保存它时没有任何内容，则会创建一个既没有条件也没有执行部分的空触发器文件。

Delete all created death tables. If you choose the StarForge format, even if you delete the death table 'directly', the death table is stored inside, so if you use the text trigger format, you have to reset the internal death table from time to time.
删除所有已创建的死亡表。如果你选择 StarForge 格式，即使你 “直接 ”删除了死亡表，死亡表也存储在里面，所以如果你使用文本触发器格式，你必须不时重置内部的死亡表。