I'm a fan of Pokemon and playing the older games, I've found it really soothing to breed competitive level mons. Currently, I'm working on making a living Pokedex starting with generation 1.
I've got five left, excepting Krabby, which I'm getting later.
I haven't played a competitive battle in years, but I always liked the idea of having a set of Pokemon I could create hypothetical teams with like the rental Pokemon in Stadium 1/2.
What about the rest of you? Anything you're doing just got you because you like it?
ask away. I've contributed to the c2c mod, in the dll code and python code
Can I add you on something for when I have specific questions or do you check in on this site often enough to bug you on? Right now I'm mostly just trying to read the files in a mod (a ffh branch called ashes of erberus) and try to understand what's going on. I've never tried to get my head around a program this large before with so many files and trying to track down dependencies from files THAT APPARENTLY ONLY EXIST AT RUNTIME. :shinji-screm:
So I guess right now any advice on how to fit it in my head at once would be appreciated. Like for instance, since it's a BTS mod, it's not using any of the files from the regular Civ4 folder, right? Just the BTS folder?
What I'm trying to do as a first medium-term goal is making a mod that automates fighter recon missions. Ashes of Erberus has a thing where your adepts can auto-cast a spell at the beginning or end of every turn. You activate that by ctrl+clicking the icon. I'm trying to track down where that behavior's described in code as a piece of how I might be able to implement my jet thing. I don't know where to look so I just open files and get lost in them.
Yeah if its a bts mod, check the BTS/Mods folder.
For processing inputs, I believe it will likely be in the Python code, probably something like YourMod/Assets/Python/Screens/something.py. If you use something like Notepad++, you can search all the .py files for key words, like 'ctrl' or 'handleInput' and get a good chance of finding where this piece of code is.