Informe de exploración

Muestra RM 1v1: 6,388,699 games. Lideres por win rate: Romans 54.3%, Tupi 53.2%, Bulgarians 52.7%. Mas jugadas: Mongols 5.7%, Franks 4.9%, Persians 3.6%. Tramo elite: Byzantines 79.1%, Chinese 77.7%, Tupi 76.6%.

AoE2.ai sigue 47,297 jugadores de RM 1v1. Top cinco: #1 Oni.Vinchester 2,891, #2 TAG_MbL_ 2,888, #3 _LY_Yo 2,887, #4 wR.Lucho 2,857, #5 VIT | Hera 2,848. Mejor racha en la muestra del top ladder: 抖音ique (64 wins). Mejor win rate de la muestra con 300+ partidas: VIT | Hera 74.8%. 67 jugadores del top muestreado han jugado en las ultimas 24h.

GAME INFORMATION These details are CRITICAL; DO NOT skip them or your issue may not be reviewed. GAME BUILD #: 101.103.48987.0 ( #180059 ) 24094652, and (1.1.2RC1) on mac GAME PLATFORM: Steam OPERATING SYSTEM: Windows 10 and Mac (same behavior) ISSUE EXPERIENCED DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD. The xs function main gets called when a saved game is loaded, or when the “save chapter” button is pressed. There is already an old unresolved post on save chapter: https://forums.ageofempires.com/t/save-chapter-glitch/ . But there may be multiple separate issues. Save chapter/game load also resets xs variables, but only when the xs code is inside triggers and not as a separate xs file. But main gets called in both cases. FREQUENCY OF ISSUE How often does the issue occur? CHOSE ONE; DELETE THE REST ! 100% of the time / matches I play (ALWAYS) REPRODUCTION STEPS List CLEAR and DETAILED STEPS we can take to reproduce the issue ourselves… Be descriptiv e! Here’s the steps to reproduce the issue: Test the attached scenario. main gets called. Press “save chapter” or save and load the game. main gets called again. There is a counter but it starts again from 1, because the code is inside a trigger and xs variables reset (as discussed in that other thread). Move the xs code from the trigger into a separate xs file, include it and test again. main gets called. Press “save chapter” or save and load the game. main gets called again. The counter now does not reset. This is in the screenshot. EXPECTED RESULT What was SUPPOSED to happen if the bug you encountered were not prese nt? main should only be called once, when the game starts. IMAGE ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the prob lem. bugMain 478×130 24.4 KB GAME FILES (SAVE / RECORDING) 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 ser vice. bu

GAME INFORMATION These details are CRITICAL; DO NOT skip them or your issue may not be reviewed. GAME BUILD #: 101.103.48987.0 ( #180059 )(1.1.2RC1) 24094652 GAME PLATFORM: Steam OPERATING SYSTEM: Mac ISSUE EXPERIENCED DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD. When calling xsCreateUnit(.., pos, ..) with a position vector pos that was defined earlier in the function, the unit spawns somewhere other than pos if there is other, completely unrelated code in between (such as printing a string literal). It seems to be about reading from the wrong memory address, because printing pos afterwards shows correct values. Other arguments to xsCreateUnit also have issues: xsCreateUnit parses bool arguments incorrectly [Mac only] FREQUENCY OF ISSUE How often does the issue occur? CHOSE ONE; DELETE THE REST ! 100% of the time / matches I play (ALWAYS) REPRODUCTION STEPS List CLEAR and DETAILED STEPS we can take to reproduce the issue ourselves… Be descriptiv e! Here’s the steps to reproduce the issue: Download the attached scenario and the associated xs script (rename from .txt to.xs) Play the scenario on Mac and see where the palisade spawns. Uncomment other unrelated code between pos = ... and xsCreateUnit and see other wrong positions. EXPECTED RESULT What was SUPPOSED to happen if the bug you encountered were not prese nt? Unit should spawn in location given by the vector passed as argument. IMAGE ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the prob lem. bugVector 522×324 122 KB GAME FILES (SAVE / RECORDING) 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 ser vice. bugVector.aoe2scenario (1.3 KB) bugVector.txt (1.3 KB)