ExeStrings (helps getting strings from the executable)
Posted: 21 Jul 2016, 19:19I made a very small program that probably won't be used by many people, but I thought, why not sharing it anyway?
Each time a new Magic Duels expansion hits, there's a high chance we find more functions inside the executable, which we may use for more modding possibilities. However finding the strings inside the executable is a boring task, and any small help is appreciated. So here comes ExeStrings: drag and drop MagicDuels.exe onto it (or give it the MagicDuels.exe path as argument at the command prompt if you prefer) and it will generate a MagicDuels.txt file inside the same directory as the executable. What will you find inside the text file? All the aggregates of 3 or more characters among [0-9, a-z, a-Z, _]. There will be a lot of garbage, but you'll find functions, constants and XML tags more easily.
Note that some strings will be attached together, that's how you find them inside the executable so it's an unavoidable problem: a human eye is needed in order to figure out where it happened.
It requires .NET Framework 4.0.
I'll try to update the Wiki some time after each expansion, but if I'm late, at least you have a way to find the strings more quickly by yourselves.
Each time a new Magic Duels expansion hits, there's a high chance we find more functions inside the executable, which we may use for more modding possibilities. However finding the strings inside the executable is a boring task, and any small help is appreciated. So here comes ExeStrings: drag and drop MagicDuels.exe onto it (or give it the MagicDuels.exe path as argument at the command prompt if you prefer) and it will generate a MagicDuels.txt file inside the same directory as the executable. What will you find inside the text file? All the aggregates of 3 or more characters among [0-9, a-z, a-Z, _]. There will be a lot of garbage, but you'll find functions, constants and XML tags more easily.
Note that some strings will be attached together, that's how you find them inside the executable so it's an unavoidable problem: a human eye is needed in order to figure out where it happened.
It requires .NET Framework 4.0.
I'll try to update the Wiki some time after each expansion, but if I'm late, at least you have a way to find the strings more quickly by yourselves.