-
Notifications
You must be signed in to change notification settings - Fork 1
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
Some questions about the asmodean tools #1
Comments
Good question, and I'm happy to answer with what information I have. I of course encountered the same issues. The > this is the only place I found that uses asmodean's code - This is probably pretty accurate. Any GitHub page I found that referenced Asmodean's code only included the source files that were packaged with the binaries and instead relied on the binaries to do the actual work. It took quite a bit of searching to find most of the missing header/c/cpp file combos but here's where I found the code that I ended up using. A lot of results I found were similar but didn't seem to function the exact same way so I tried to get closer matches. Now I'll be honest, I'm pretty average at web searching, but in this case I fared pretty well, although it took a lot of keyword guessing and time.
As for
I've included the solution I used as I worked my way through the code. Do note that some functionality was changed/removed/ignored/forced/or outright improved in order to meet my goals quicker: ExkifintWork.zip (VS2017) If you have any more questions about the code (no matter how nitpicky), then feel free to throw them my way in this issue thread. If you have questions about other Asmodean extractors then I may be able to help out with that too, I'm definitely not happy at the lack of open source, especially when so many of Asmodean's programs would benefit from community improvement. (For example, I fixed an issue with the |
Thanks SO much for helping out! I'm really not much of a pro in programming (my major is in physics...), but I'm sure I will put the resource to good use,. I'm still learning the tricks for now(eg. I've just learned a bit about the use of "#pragma pack(1)" preprocessor), but I think I will try to do my part as much as I can. Thanks again for explaining the functions, the sources to look for, and the offer to help. It means a lot to me. PS: It turns out that the "Asmodean Util B" is from a chinese programming forum "CSDN", and it seems that visiting it from within China doesn't come up with a lot of adds. (May be a side effect of the great firewall of China...) |
Sorry for necroing, but i've been wondering how you have your code MIT licensed, when asmodean didn't license his code? I'm facing an issue myself, since I want to include some of his code in my GPLv2 licensed project. |
@monyarm to be honest, I didn't think too much about it back then. I've seen a ton of projects on GitHub including asmodean tools/source code, so I wouldn't worry too much over it. Maybe leave a text file in the folder containing their code that explains its separate from the rest of the project/license (or however it would be best to word that). But I'm not an expert with licensing, so I'm not sure what the safest "correct" choice would be (if there even is a correct way to include unlicensed code). If you want to be really cautious, then you could reference anything you want from my CatSystem2 C# library or Sprite Viewer tool or Python3 library which have replacements for asmodean code (though it's not in C/C++ and they're both a bit of a mess). Also note the C# library doesn't account for older There's also GARbro which has replacements for the |
I'm sorry to post a issue concerning others' code here, but it seems that this is the only place I found that uses asmodean's code.
The problem is: I cannot find any header files the source code references, and I couldn't guess how certain functions work without them, especially functions in the "as::" namespace.
The question is: How did you work around it? I would really need some help in understanding the code...
Thanks SO much for looking at this off-topic issue anyway.
The text was updated successfully, but these errors were encountered: