To reproduce: make this macro in a local tiles build, then in a local console build.
\{6}corpse\{13}a\{13}
Kill something that drops a corpse, stand on a different tile from the corpse, then use the macro.
The intended behavior of the macro is to press ctrl-F, type foo into the search prompt, press enter, press a to select the nearest foo, then press enter again to attempt to autotravel to foo. The result of pressing these keys manually is that your character attempts to autotravel to foo.
In the console build: The result of using this macro is that your character attempts to autotravel to foo.
In the tiles build: The result of using this macro is that your cursor will be placed on the foo that you searched for, but your character will not attempt to autotravel. It seems as though the final \{13} is discarded. Substituting . or ; for the final \{13} in the macro does not change the outcome.
This macro works successfully on CSZO webtiles running the same build (g4453506), so it seems to be an issue with local tiles only.
The macro also works successfully when running local tiles 0.11.0 and 0.11.2 release builds. It seems that something has been changed in trunk local tiles with regard to how macros are handled that has caused it to become nonfunctional.
I first discovered this inconsistency while playing with Lua scripting in local tiles build 0.12-a0-1757-gcbcea53. If, for example, you attempt to do a search for "whatever" using magic(string.char(6) .. "whatever" .. "\ra\r") from parabolic.rc you will run into the same problem.
OS: Windows 7
no change.png [^] (643,354 bytes) 2013-02-18 16:15 
