Conditional jumps in script actions

[FS-21]

Is the same PR #599:
"Conditional Jumps for changing the current Team script flow"

I closed #599 because exists an unknow crash I had no idea to fix (I fixed it now). With this pretext I moved all the conditional jump actions into its own file.

All this time I used them a lot in my mod C&C Reloaded to control AI scripts workflow so you can read the aimd.ini if you need some tips or try it yourself with the documentation.

From docs:

16027 Conditional Jump, Clear Variables

• Reset all variables related to conditional jumps.

In aimd.ini:

[SOMESCRIPTTYPE]  ; ScriptType
x=16027,0

16013 Conditional Jump, Manage Variables Reset If The Jump Is Successful

• By default the conditional jump variables are cleaned after a successful jump.
• This action enables the ability to retain variables value after the jump.
• This action behavior isn't affected by the action 16012 "Clear Variables".

In aimd.ini:

[SOMESCRIPTTYPE]  ; ScriptType
x=16013,0         ; Integer, 1 = true, 0 = false

16014 Action Abortion After Success Kill

• If the team kills a target and this option is enabled the current action is interrumped and jumps to the next script line.

In aimd.ini:

[SOMESCRIPTTYPE]  ; ScriptType
x=16014,0         ; integer, 0 for disable it, 1 for enable it

16015 Conditional Jump, Manage Kills Counter

• The team kills counter will work if this action enables it.

In aimd.ini:

[SOMESCRIPTTYPE]  ; ScriptType
x=16015,0         ; integer, 0 for disable it, 1 for enable it

16016 Conditional Jump, Reset Counter

• Sets the team's counter to any initial value. It can be used for counting kills.

In aimd.ini:

[SOMESCRIPTTYPE]  ; ScriptType
x=16016,n         ; integer

16017 Conditional Jump, Set Comparator Mode

• Sets the comparator used in conditional jumps.

In aimd.ini:

[SOMESCRIPTTYPE]  ; ScriptType
x=16017,3         ; integer, from 0 to 5, default to 3 (>=)

• The possible comparator values:

Argument	Comparator type
0	<
1	<=
2	=
3	>=
4	>
5	!=

16018 Conditional Jump, Set Comparator Value

• Sets the value used in conditional jumps comparisons.

In aimd.ini:

[SOMESCRIPTTYPE]  ; ScriptType
x=16018,1         ; integer

16019 Conditional Jump, Set Index

• Sets the index of a list used in conditional jumps comparisons. Depends of the conditional jump action.

In aimd.ini:

[SOMESCRIPTTYPE]  ; ScriptType
x=16019,n         ; integer

16020 Conditional Jump, Jump If False

• Check the conditional jump evaluation and jumps to the specified line if the value is false. Like in the script action 6,x the line number is 1-based.

In aimd.ini:

[SOMESCRIPTTYPE]  ; ScriptType
x=16020,n         ; integer, n > 0

16021 Conditional Jump, Jump If True

• Check the conditional jump evaluation and jumps to the specified line if the value is true. Like in the script action 6,x the line number is 1-based.

In aimd.ini:

[SOMESCRIPTTYPE]  ; ScriptType
x=16021,n         ; integer, n > 0

16022 Conditional Jump, Check Kills Count

• Checks the team kills count and saves the result for the conditional jump evaluation.

In aimd.ini:

[SOMESCRIPTTYPE]  ; ScriptType
x=16022,0

16023 Conditional Jump, Check Simple Count

• Increases or decreases the conditional jump counter with the specified value by the Action argument and saves the comparison result for the conditional jump evaluation.
• The count can be reseted using the script action 16016.

In aimd.ini:

[SOMESCRIPTTYPE]  ; ScriptType
x=16023,n         ; Integer

16024 Conditional Jump, Check If Exist Alive Human Players

• Checks if exist human players in the map and saves the result for the conditional jump evaluation.

In aimd.ini:

[SOMESCRIPTTYPE]  ; ScriptType
x=16024,n         ; integer n = 0, 2 <= n >= 0

• The possible argument values:

Operation	Description
0	Any human house (including the team's owner)
1	Enemy human house
2	Friendly house

16025 Conditional Jump, Check Enemy Objects Count

• Count the number of enemy living object instances and saves the result for the conditional jump evaluation.
• The list of objects that will be used by this Action is selected by the Script Action 16019.

In aimd.ini:

[SOMESCRIPTTYPE]  ; ScriptType
x=16025,0

• This action use a 0-based index for the AITargetTypes section and specifies the list of possible VehicleTypes, AircraftTypes, InfantryTypes and BuildingTypes that can be evaluated. The new AITargetTypes section must be declared in rulesmd.ini for making this script work:

In rulesmd.ini:

[AITargetTypes]  ; List of TechnoType lists
0=SOMETECHNOTYPE,SOMEOTHERTECHNOTYPE,SAMPLETECHNOTYPE
1=ANOTHERTECHNOTYPE,YETANOTHERTECHNOTYPE
; ...

16026 Conditional Jump, Check If The Most Hated Enemy Is Human

• Checks if the major team's enemy is human player and saves the result for the conditional jump evaluation.

In aimd.ini:

[SOMESCRIPTTYPE]  ; ScriptType
x=16026,0

[github-actions]

Nightly build for this pull request:

• compiled-dll-d87be28b91ce8d14ce7f69e98c61a1db74f430a5.zip
  These artifacts will expire in 90 days and will not be available for download after that time.

This comment is automatic and is meant to allow guests to get latest nightly builds for this pull request without registering. It is updated on every successful build.

[coderabbitai]

Warning

Rate Limit Exceeded

@FS-21 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 29 minutes and 20 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between eef9bc0 and 3ced4c6.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.