Fixed an issue where Speeder could attempt to target objects or non-targetable entities. The functionality should now be completely restored to the way it was pre-patch.
I have added two new console commands that will allow you to reuse the same waymark files even after restarting the game. Due to player coordinates being different upon every relog, the coordinates in a waymark file can become invalid. The relative distance between each waymark, as well as the angle and everything needed to calculate trajectory, is the same, however, so all you need to do is calculate xyz offsets so the old coordinates can be translated into the new ones. This is done by placing your character exactly upon the first waymark. Then, you can use the new -tw** or -twrepeat** command to begin your waymark rotation. The two asterisks tells Speeder to calculate the offsets from the first waymark in the file. This is why you need to place your character at the first waymark. Here are the full descriptions of the commands:
- -tw** & -twrepeat** — If you include two asterisks for either of these commands, Speeder will take your current game position and subtract the coordinates from your waymark's first index from it. These "offsets" will then be saved by Speeder and applied to every waymark. Because the game coordinates are random every time you restart the program, this allows you to use the same waymark files without ever having to adjust the xyz coordinates. The basic idea is to manually move your character to the position of the first waymark in your waymark file (be sure you are as close as you can get). Then use -tw** or -twrepeat** with that file. After you have done this once, you don't need to do it again. You can even load a different file, and the offsets will still work. Because of this, you might consider creating a "calibration" waymark file containing a single waymark that is easy to get to. Use -tw** with this file, and then you can load your actual waymark file.
I've also added an extremely helpful console command that allows you to test macro commands:
- -cmd [macro/waymark commands] — Speeder will activate "macro/waymark commands" as if you had pressed a macro key with them present. This is a great way to test commands to make sure they are working correctly. You could also use this command to set variables manually. Example:
- -cmd store % testvar,1|eq % testvar,1|dbg % this message should appear in the console
It is now possible to discern whether a mob or player is targeting you. In the case of a mob, this generally means the mob is attacking you, and you can use this command to respond accordingly. I have also added a command that automatically moves you toward the closest mob. Here are the full descriptions for all the new commands:
- "ibt[type],[distance]" — If you are currently targeted by an entity matching "type" that is closer than "distance," the rest of the keys line will process. "Type" can be 1 for mobs or 2 for players. The global variable IBT will be populated with the ID of the entity targeting you. This can then be used with the "te[entity ID]" command to target the entity that is targeting you. Example:
- keys=ibt1,10000|te*(VAR % IBT)|dbg % I am now targeting the mob that is targeting me
- "te[*][entity ID]" — Speeder will target the entity with an ID of "entity ID." Some commands, such as "ibt," return the ID of the entity matching the criteria, which can then be used with this command. If you include an asterisk, such as "te*," the camera will be rotated to face the matching entity. Example:
- keys=ibt1,10000|te*(VAR % IBT)|dbg % I am now targeting the mob that is targeting me
- "mtm % [name],[distance],[angle],[how far]" — Speeder will move you toward the closest mob with name "name" as long as the mob is closer than "distance." It is possible to omit "name," in which case Speeder will search for the closest mob. It is possible to set distance to 0, in which case any mob in memory will be a potential target. "Angle" controls how straight you want to move toward the mob with 0 being a direct line toward the mob. A value of 0.1 would move you slightly left or right of the mob. "How far" controls how far you want your character to run relative to the mob with 0 being on top of the mob. Because you cannot stand exactly on top of the mob, it is a good idea to use a negative value, such as -100, so that your character stops in front of the mob. A positive value will place you behind the mob. Example:
- keys=mtm % ,10000,0,-100|dbg % I am now standing in front of the closest mob within 10000 distance
- Note how I have left "name" blank in this example and how there is a space between the "%" and the ","
These changes require updating Speeder to version 38.
