["Major" Issue - XS Scripting] Unability to edit blank technologies costs with "xsEffectAmount" and "cModifyTech"

:play_button: GAME INFORMATION

:backhand_index_pointing_down: These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.

  • GAME BUILD #: #188329
  • GAME PLATFORM: Steam
  • OPERATING SYSTEM: Windows 11

:play_button: ISSUE EXPERIENCED

:backhand_index_pointing_down: DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.

While trying to modify the “blank technology 00”, or any other blank techs, cost type / amount / deduct, it keeps the “free” cost, using :

xsEffectAmount(cModifyTech, 1180, cAttrTypeFirstCost, cAttributeFood, -1);
xsEffectAmount(cModifyTech, 1180, cAttrAmountFirstCost, 80, -1);
xsEffectAmount(cModifyTech, 1180, cAttrDeductFlagFirstCost, 1, -1);

The technology cost stays at “free” due to the dataset values of all the costs set to -1. It seems to be similar to when we were unable to modify units graphics slots of they were set by default to -1 in the dataset.

:play_button: FREQUENCY OF ISSUE

:backhand_index_pointing_down: How often does the issue occur? CHOSE ONE; DELETE THE REST!

  • 100% of the time / matches I play (ALWAYS)

:play_button: REPRODUCTION STEPS

:backhand_index_pointing_down: List CLEAR and DETAILED STEPS we can take to reproduce the issue ourselves… Be descriptive!

Here’s the steps to reproduce the issue:

  1. set technology 1180 train location on a building to test it
  2. apply the script in a script call trigger / map xs file
  3. run test and put mouse hover the blank tech to see the cost unchanged, still to “free”.

:play_button: EXPECTED RESULT

:backhand_index_pointing_down: What was SUPPOSED to happen if the bug you encountered were not present?

Blank technologies, and any technology infact, to be editable with the “cModifyTech” xs function without needing to make dataset edit / trigger usage.

:play_button: IMAGE

:backhand_index_pointing_down: ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.

Can’t really screenshot the issue, or at least not in a relevant way, easy enought to reproduce.

:play_button: GAME FILES (SAVE / RECORDING)

:backhand_index_pointing_down: Attach a SAVE GAME (.aoe2spgame) or GAME RECORDING (.aoe2record) of the match where you encountered the issue. Link it below if using an external file service.

  • #N/A

Side Note: The report is tagged “major” only because it’s a major liitation, there is no gameplay arming due to all the official scripting handled differently in campaigns.