-
Notifications
You must be signed in to change notification settings - Fork 17
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
Fixed "invalid" hash sizes (map protection?) in Broodwar maps #32
Conversation
Cool, thanks for the PR 👍
|
@Frotty I'm puzzled, why does it show 8 Fs for you? Should be 7 (it even has the prefix 0x0... in my commit) :) Will try to find a small example. |
Oops, I must have mistakenly added one during copy+paste as I didn't check out the branch 😬 |
I have a test map, but it makes the "testDuplicatePaths" test fail. Ok if I skip that map (it's a SC map after all) - or do you want a failing test ;)
|
I don't know which test you are referring to with "testDuplicatePaths". |
Uhm, check the trace above. The test is |
Okay I wasn't on latest master on this machine. 😅 e: and yea, this looks like the usual bugs with non trivial protection. |
Not sure, maybe it is modifiable. I think that would need further analysis. My use case really only needs reading for now. I'll add the map as an exception. |
Nice 👍 |
@Frotty Yeah - I'm part of a project to enable players to play vs custom AIs for Starcraft: |
Sounds cool 😄 |
Not sure about Warcraft, but some Starcraft maps use the upper 4 bit to make loading the mpq impossible. (The upper 4 bit are dropped because of * 16 in the game/hashtable - but JMPQ3 uses the original hashSize value to create the table)