Unlike the offset that recognizes the data ID of the basic unit, it recognizes the structure offset. Also, since this offset is a shared offset, any implementation that affects the game works very well. Nothing goes into the object ID, so you just need to put the structure offset of the unit as it is in the value.
与识别基本单元的数据 ID 的偏移量不同，它识别结构体偏移量。此外，由于此偏移量是共享偏移量，因此任何影响游戏的实现都运行良好。对象 ID 中没有任何内容，因此您只需将单元的结构偏移量与值中的相同位置放置即可。

There is an offset per player.
每个玩家都有一个偏移量。

Below is a simple trigger format. Enter the structure offset of the unit you want in n as a decimal number.
下面是一个简单的触发器格式。以十进制数形式输入所需单位 n 的结构偏移量。

This is an offset that changes the ID of the player within the game.
这是更改游戏中玩家 ID 的偏移量。

There is an offset per player. Below is the basic base death table, and subsequent ID changes follow the rules below.
每个玩家都有一个偏移量。以下是基本 kill 表，后续的 ID 更改遵循以下规则。

You just need to put the ID of the desired upgrade in the object ID and the level of the upgrade to be recognized in the value.
您只需将所需升级的 ID 放在对象 ID 中，并将要识别的升级级别放在该值中即可。

There is an offset per player.
每个玩家都有一个偏移量。

Unusually, the offset is different for each original upgrade (00 ~ 45) and Brood War upgrade (46 ~ 60). So if you are aware of upgrades with an ID lower than 45 (original) or higher than that (brood war), you need to choose an offset accordingly.
不同寻常的是，每个原始升级 （00 ~ 45） 和 Brood War 升级 （46 ~ 60） 的偏移量都不同。因此，如果您知道 ID 低于 45（原始）或高于 ID（母巢战争）的升级，您需要相应地选择偏移。

Also, in the case of Brood War upgrade recognition, 46 is regarded as 0. Therefore, when using the Brood War upgrade offset, subtract 46 before using it. When using this, the number to put in the object ID when using the Brood War upgrade offset is 0 to 14.
此外，在 Brood War 升级识别的情况下，46 被视为 0。因此，当使用 Brood War 升级偏移时，使用前要减去 46。使用此选项时，使用 Brood War 升级偏移时要放入对象 ID 的数字是 0 到 14。

Replaces a string given to a unit with another string. The string number can be checked in SCMD by default.
将给定给 unit 的字符串替换为另一个字符串。默认情况下，可以在 SCMD 中检查字符串编号。

Basically, the turbo trigger is a trigger that executes the trigger about 12 times per second by repeating Wait(0) infinitely and using the infinitely repeated Wait. However, the downside of the wait turbo trigger is that when the wait trigger is used, the waits are twisted together, so you must put them in a computer that is not in use.
基本上，turbo 触发器是一个触发器，它通过无限重复 Wait（0） 并使用无限重复的 Wait 每秒执行大约 12 次触发器。但是，wait turbo 触发器的缺点是，当使用 wait 触发器时，等待会扭曲在一起，因此您必须将它们放在未使用的计算机中。

This offset decreases by 1 every frame, and when it reaches 0, it returns to 30 as soon as the trigger is activated. In other words, if this offset is set to 0, the trigger is actuated immediately and quickly, so the trigger can be actuated up to about 24 times per second, enabling very fast trigger actuation. Because of this, the wait twist phenomenon is remarkably reduced, so no matter where the trigger is placed on any player, the triggers do not twist each other.
此偏移量每帧减少 1，当达到 0 时，一旦激活触发器，它就会返回 30。换句话说，如果此偏移量设置为 0，则会立即快速启动触发器，因此触发器最多可以每秒启动约 24 次，从而实现非常快速的触发器启动。因此，等待扭曲现象显著减少，因此无论将触发器放置在任何玩家的哪个位置，触发器都不会相互扭曲。

You can set the value of offset to n so that the trigger works every (n+1) frame, and of course you can set it higher than the default value of 30.
您可以将 offset 的值设置为 n，以便触发器每 （n+1） 帧工作一次，当然，您可以将其设置为高于默认值 30。

SetDeaths(10, SetTo, n , 17531); (expansion unit)
SetDeaths（10， SetTo， n ， 17531）;（扩展单元）
SetDeaths(210382, SetTo, n , 0); (extended player)
SetDeaths（210382， SetTo， n ， 0）;（扩展播放器）

Set Deaths("Player 11", "Int:17531", Set To, n);
设置 deaths（“player 11”， “int：17531”， set to， n）;
Screen crashes when over 32
超过 32 岁时屏幕崩溃