Closed GoogleCodeExporter closed 9 years ago
Won't be including java interface in BWAPI, but will do the remaining two.
Some additional suggestions of my own:
Move BWAPI.dll location to bwapi-data in the Starcraft folder.
When starting BWAPI, create a copy of the BWAPI.dll in temp and load the temp
one. Do the same for the AI module.
Create a general loader project which will work for both ChaosLauncher and
MPQDraft. The loader project will also not be updated for every revision.
Instead the loader project will retrieve the revision from the BWAPI DLL. The
loader project will also contain a GUI config. There will only be one loader
project, and not separate ones for RELEASE and DEBUG.
Find a way to pass the Broodwar interface to an AI module before the entry
point is called.
Original comment by AHeinerm
on 16 Apr 2012 at 3:09
need a more precise, clear, and simple tutorial on debugging pls, it took me
some good amount of time to try all the possibilities spread around the
documentation and the wiki.
Original comment by thiagovd...@gmail.com
on 18 Jun 2012 at 8:05
I think these types of tutorials are necessary. I can work on them right after
releasing BWAPI4.
Original comment by AHeinerm
on 24 Mar 2013 at 2:57
The BWAPI project is slowly undergoing the migration to GitHub. All issues have
been migrated to the GitHub issue tracker located here:
https://github.com/bwapi/bwapi/issues
In order to receive updates on your issue, please head over to the GitHub issue
tracker and subscribe to your issue.
Original comment by AHeinerm
on 15 Apr 2014 at 7:46
Original issue reported on code.google.com by
AHeinerm
on 8 Mar 2012 at 12:05