The correct limitations are from -1 to 11(all teams) from -1 to 5 (specific team) for creating dummy bot and from 0 to 11(all teams) from 0 to 5 (specific team) for the rest
Dummy bot creation:
Players in slot(for testing):
In-game limitations are from -10000 to 10000 for creating dummy bot and from 0 to 11 for the rest
Blizzard Patch 1.40.0.0.61441
Responded to the latest overwatch as of 24 August 2019.
I would like to give a note of how Blizzard's patch content is reflected in the dva engine from this patch.
๐ฉโ๐ป If blizzard staff are watching this, please remind the overwatch tech team that a some madman is taking out Overwatch Workshop's information by hand and that Blizzard needs to seriously consider whether he should be rescued (By disclosing language translation resources).
Detail of Elements
Maintain Command - describes how we run maintenance scripts that we create to automate updates.
Descriptions - These are the comments specified in the function. The 0th comment is always the comment of the function itself, after which the comments of the parameters of the function are listed in order of the parameters.
The following are the patched contents of Blizzard.
+ Action
Create Dummy Bot
Maintain Command
npm run maintain:action createDummyBot 'Create Dummy Bot' hero team slot position facing
Descriptions
English
Adds a new bot to the specified slot on the specified team so long as the slot is available. This bot will only move, fire or use abilities if executing workshop actions.
The hero that the bot will be. If more than one hero is provided, One will be chosen at random.
The team on which to create the bot, The "All" option only works in free-for-all game modes, will the "Team" Options only work in team-based game modes.
The player slot which will receive the bot (-1 for first available slot). Up to 6 bots may be added to each team, or 12 bots to the free-for-all team, regardless of lobby settings.
npm run maintain:action destroyDummyBot 'Destroy Dummy Bot' team slot
Descriptions
English
Removes the specified dummy bot from the match.
The team to remove the dummy bot from. The "All" option only works in free-for-all game modes, while the "team" options only work in team-based game modes.
npm run maintain:action startThrottleInDirection 'Start Throttle In Direction' player direction magnitude relative behavior reevaluation
Descriptions
English
Sets or adds to the throttle (directional input control) of a player or players such that they begin moving in a particular direction. Any previous throttle in directon is cancelled.
The player or players whose throttle will be set or added to.
The unit direction in which the throttle will be set or added to. This value is normalized internally.
The amount of throttle (or change to throttle). A value of 1 denotes full throttle.
Specifies whether direction is relative to world coordinates or the local coordinates of the player or players.
Specifies whether preexisting throttle is replaced or added to.
Specifies which of this action's inputs will be continuously reevaluated. This action will keep asking for and using new values from reevaluated inputs.
npm run maintain:action createBeamEffect 'Create Beam Effect' visibleTo beamType startPosition endPosition color reevaluation
Descriptions
English
Creates an in-world beam effect entity. This effect entity will persist until destroyed. To obtain a reference to this entity, use the last created entity value. This action will fail if too many entities have been created.
One or more players who will be able to see the effect.
The type of effect to be created.
The effect's start position. If this value is a player, then the effect will move along with the player. Otherwise, the value is interpreted as a position in the world.
The effect's end position. If this value is a player, then the effect will move along with the player. Otherwise, the value is interpreted as a position in the world.
The color of the beam effect to be created. If a particular team is chosen, The effect will either be red or blue, depending on whether the team is hostile to viewer. Does not apply to sound effects. Only the "Good" and "Bad" beam effects can have color applied.
Specifies which of this action's inputs will be continuously reevaluated. The effect will keep asking for and using new values from reevaluated inputs.