Skip to content

5.Usage

One ArtEase Fields

For the convenience of modifying rule content dynamically, some configurable items are previously stored on ArtEase

  1. data_key. Rule name. Rules will be turned on only when the scheme name matches the category. Rules are by default off.
  2. desc. Rule description. Doesn’t affect the function of rules.
  3. condition. Some conditions. Needs to implement these logics in the rule by itself.
  4. dir. Folders that need to be checked. Checks all by default. Better ends with “/”.
  5. except_dir. Skipped folders, ending with “/”, i.e.! image-20220512140858172. If you want to skip check on this folder, enter /Game/ThirdPersonCPP/. If there are multiple folders that you want to skip, split them with “&”, i.e. /Game/folder1/&/Game/folder2/.
  6. exception. Skipped files. The full file name is required, i.e. /Game/ThirdPersonCPP/NewMaterial. Separate multiple resources with “&”.

Two Local Debugging

After modifying the configuration files, you could possibly mis-upload or affect others by debugging in the project rule base. Here is the local debugging scheme.

Adds a new scheme

image-20220512141019458

Avoids interfering with public rules.

Modifies configuration files

image-20220512141106481

Quick local modifying of configurations without interfering with plugin files, as shown above.

Three Interfaces

The website and email address mentioned in the configuration files will be used in the notification interface.

image-20220512141205070

Click Show Rule to go to the target website.

Click POPO Help to go to the chat window with the responsible staff.

Four Saving Check Results

All check rules will be saved in the local folder “Saved”.

During following-up uploads, you can read the corresponding json files, for example SVN Commit, which can hook pre-commit.

If there is a FailedLog, it is considered check failed and cannot be uploaded,

Also file reference and dependency are saved for reference-missing checks.

image-20220512141301411