COOLer Has found all Native Calls in Game Dl

as stated above I have found a compleat list with what handels(objects) each takes im not shure if there are any new ones then in the common j but i will post a list asap of what i found. :>

do you want a cookie?

no i wanted to show it can be done I said a year ago i would find it and after some work i have found them . here is a link to what i have found Have fun all jassers

Hmm could u put this into a format where three are actual returns?


All i get in 3 programs are one big line of text

Thanks

Rod

I did find DialogSetAsync which means that Blizzard didn't completely kill this native. It originally appear in 1.00 of common.j but disappeared shortly there after.

Im glad this could be help full I also found 90% of the file names of the class/cpp/.h files in the game dl as well and what files it calls in mpq.

Could you please put this in a readable format.

Working on that asap!

Just curious, what did you use to find them? I tried to view Game.dll with MSDEV, but could only see anything using Wordpad, and when I did most of it appeared as unreadable (random-looking characters, in Wordpad anyway) except for some lines which appeared like the native calls.

It's also a funny coincidence that you found and posted this on the same day I found it (Or at least I found it on the same day that you posted.). Anyway, it didn't occur to me that there would be native calls that aren't listed in common.j, and do you think this might help discover where native functions are declared?

I noticed this line, but I guess it can't help us unless we actually have the source file.

..\Game/JassWar3.cpp

A thought I've had about this is if the the calls in Game.dll are declarations, perhaps the implementations are also in Game.dll somewhere. I don't know how WC3 declares it's native functions and I'm havn't learned much with C++ or gotten much practice with it, so I'm more than likely completely off with that guess, but it's just a thought.

From what i have seen in Game dll. wc3 is 99% written in C++ and not C.
the reason you cant read most of the code is beacuse its in binary. word pad converts the file to acsii so only strings can be seen.

I know that it's binary, and I'm not sure what I was thinking. To see the native functions we'd need the source files, unless they appear somewhere else or some one has a way of changing the assembly code to source, and even that might not be helpful since I often don't even have a clue how native functions of C++ work. :(

That's great, but does declaring new natives in a custom common.j work?
and does a custom common.j actually load correctly?

I don't think so, but if you put the native names in a blizzard.j file in war3dir\scripts as a function the editor will be able to save the map, custom common.j files don't work cause World edit already has all the native functions registered inside that exe it seems, (this comes from the thing that makes cracked old editor versions give compiler messages like crazy)

This is the same file COOLer already posted, just with linebreaks after each function name :P