-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ability target positions #15
Comments
Currently numbers are (incorrectly) parsed as int32 everywhere. The w3g specification explains that click coordinates are saved as 32bit IEEE floating point numbers. Therefore the parser has to be adjusted to read floating point values instead of int. Take a look at the following line: Changing the int32le to floatle should work to get the proper coordinates. |
I set up a branch with the changes required: Check it out and see if it fits your needs. |
Now that you're talking about coords, would it be possible to detect players's starting positions? |
the branch fixes work great 👍 thanks for the explanation on the fix. I am also highly interested in starting locations - I was wondering if that was encoded in the 'random seed' potentially? |
I merged the branch into master. Please open another issue about determining the player start positions. |
great tool, thanks for releasing it 👍
have a question about when looking at the
targetX
andtargetY
values of an ActionBlock with those properties - it seems the values are large numbersx: -980223926, y: 1162084274
is there additional conversion needed to align them to the map coordinates? for example Echo Isles seems to be only ~10,000 units wide in the world editor
thanks!
The text was updated successfully, but these errors were encountered: