• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Stop wasting time looking for files and revisions. Connect your Gmail, DriveDropbox, and Slack accounts and in less than 2 minutes, Dokkio will automatically organize all your file attachments. Learn more and claim your free account.


Getting Started with Coding

This version was saved 4 years, 5 months ago View current version     Page history
Saved by James Koppel
on April 29, 2016 at 10:59:29 pm
This page has an associated video tutorial, Modding with an Iron Fist: Episode 4: Modding the Code ( http://www.youtube.com/watch?v=dFTT0id4Iz0 )
Getting a development environment set up is never a picnic, especially not for a project as advanced as Ironfist. This tutorial aims to remove as much of the pain as possible.
Our code interacts with the code of the original game at the binary level, and we're stuck using Microsoft tools as a result of some of the features we use to do this. 


What You'll Need


  • A checked-out repository (see Setting up the Repository)
  • Microsoft Visual Studio (free versions should do, but make sure they have C++)




We have now started distributing the Visual Studio Project file in the repository. Simply go to your local copy of the repository, and open the ironfist/ironfist/ironfist.vcxproj file in Visual Studio. You should be able to immediately compile the project. The map editor should work similarly, but with ironfist/editor_vs/editor_vs.vcxproj instead.


One issue is that, for some reason, all files will be displayed in one giant unorganized list, even though the actual files are organized in a nice hierarchy. Fixing this is on the to-do list, but we'll do it sooner if you complain.  And, of course, please complain if you have any other problems.




Follow the Google C++ Style guide's recommendation for formatting,  https://google.github.io/styleguide/cppguide.html#Formatting . The exception is that lines may exceed 80 characters.


When transporting code from the decompilation into Ironfist, apply the "Does this look like code I would have written myself?" test. Decompiled code has a lot of features that are hard to read that are seldom seen in human-written code, such as gotos, lots of pointer arithmetic, automatically-generated variable names, etc. It's important to clean this up before merging it into the Ironfist codebase.




Ask to be added as a contributor to the Ironfist repository in Github. When adding a new feature to Ironfist, use this workflow in git:


  1. Create a new branch in git, named <your initials>-<name of feature>. So, for example, if James Koppel wants to write the code for a "first strike" creature ability, he would run the command git checkout -b jk-first-strike
  2. Write all your code and commit it to this branch. Be sure to commit often, preferably each distinct chunk of work, to make following the history easy.
  3. When you're done, use git push to upload your code to Github, go to the Github website, and create a pull request against the master branch
  4. Ask your teammates for a code review, and make more commits to respond to any feedback they may have
  5. Once you have gotten the thumbs up, merge in your changes. Congrats -- your code is in the game! 


Comments (0)

You don't have permission to comment on this page.