Press F4:will loss first 16 characters of all text and array

:arrow_forward: GAME INFORMATION

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

  • **GAME BUILD #:#94056
  • GAME PLATFORM: Steam
  • OPERATING SYSTEM: Windows 11

:arrow_forward: ISSUE EXPERIENCED

:point_down: DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.
Press F4:will loss first 16 characters of all text,and array.
This includes the running instructions, changing unit names, and text in timers, all becoming scrambled.
All trigger effects that come after the text within a trigger are also reset. For example, if you run instructions and then modify attributes, after pressing F4, the attribute modifications will be reset.
This includes text stored in variables that exceed 16 characters. After pressing F4, the first 16 characters are lost.
This includes all changes to array parameters.
It does not include text created after pressing F4.

:arrow_forward: FREQUENCY OF ISSUE

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

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

:arrow_forward: REPRODUCTION STEPS

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

Here’s the steps to reproduce the issue:

countdown Timer:

  1. Create a timer with text content exceeding 16 characters, and the timer is currently displayed.
  2. Press F4.
  3. Text content becomes garbled.

array:
1、int array0=0;array0=xsArrayCreateInt(50,0,“techarray10000”);xsArraySetInt(array0,1,299);
2、Press F4。
3、xsArrayGetInt(0,1)==0,not 299.

:arrow_forward: EXPECTED RESULT

:point_down: What was SUPPOSED to happen if the bug you encountered were not present?
not lose any text.

:arrow_forward: IMAGE

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

:arrow_forward: GAME FILES (SAVE / RECORDING)

:point_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.