Contributing to Ares

This is relatively unpolished. As the wrapper library and the project matures, simpler ways to create custom code will be created. Don't panic.

At this moment, you will not be able to run the DLLs you compiled - the sources in SVN have been updated to work with a more recent, development-version of Syringe which is not publicly vailable just yet. Don't try runnning them on the old public version.

Contributing to Ares is relatively simple, if you know at least the basics of C++:

What you'll need

A knowledge of C++

Yes, you'll need this.

A C++ compiler/IDE

Right now, Microsoft Visual Studio and Dev-C++/WxDev-C++ (gcc-based) are supported.

A Subversion (SVN) client

TortoiseSVN is recommended.

Getting the code

The code consists of two parts:

yrpp

the wrapper library enabling the use of most ingame functionality through plain C++

Ares itself

the code for Ares itself, the functionality that is actually utilised

At the time of writing, they're both bundled in the same SVN repository:

• Create a folder on your hard drive where you'll be keeping the code, for example, C:\My Documents\Visual Studio Projects\Ares or f:/source/ares, whatever suits you.
• Right click said folder, and select SVN Checkout... from the context menu.
  • Enter svn://www.renegadeprojects.com/yrpp as the Repository address.
  • Leave the other options as they are, and press OK.

The source code in the repository is updated often with changes and bugfixes. Make sure to compile all your code against the latest version of the SVN code.
The SVN Update context menu option will update your local copy.

Code Layout

The files directly in the folder are parts of the wrapper library. The Ares code is in the Ares subfolder. There are also other folders in the hierarchy, ExceptChecker contains the code for the current ExceptChecker DLL , and Examples contains some examples of using the more complex functionality in yrpp.

Assuming you're familiar with C++, you should create a new .cpp file in the Ares folder (copy the source code from fix_temporal/fix_temporal.cpp until a proper skeleton is set up).

Also, take the time to at least gloss over the existing code, including the wrapper library - knowing what is possible already and how is always good.

Writing A Function

All functionality in Ares is implemented as callback functions - when the game hits a certain location in the original code, some Ares function is invoked. To make your function invokable at a certain point, you'll need to assign your function as one of the predefined callbacks or use the Syringe Injection Control File to define that.

Any serious modification will normally require more than one callback, for now multiple callbacks cannot be registered at one location.

Currently, callback functions are usually declared like this:

//hook at 0xDEADBEEF
EXPORT Functionality_FunctionName() {
 // actual code
}

What the actual code does is naturally up to you, but usually you'll need to pull a pointer to one of the game classes from one of the CPU registers. This sort of information is very location-/context-specific, and as such you'll need information from the people familiar with the reverse-engineered ASM view of the code (as it is now, pd, jonwil, VK, DCoder and TSHyper). What the actual game classes do is documented in the wrapper library, look at its header files and the existing code snippets.

An Example

Here's a sample callback. It fixes a comparatively simple bug - that units firing Template:TTL warheads get experience from erasing friendly units.

Bits marked with (ASM knowledge) you are not required to know, the asm hackers can explain that part.

// keep this part in
#ifndef _CRT_SECURE_NO_WARNINGS
#define _CRT_SECURE_NO_WARNINGS
#endif
#ifndef _CRT_NON_CONFORMING_SWPRINTFS
#define _CRT_NON_CONFORMING_SWPRINTFS
#endif
#pragma warning(disable: 4035)	//"no return value" - there is one, just not in our code ;)

// standard C++ headers
#include <stdio.h>

// wrapper headers to be included - list those which contain functionality you'll want to use
#include "../ASMMacros.h"
#include "../YRPP.h"
#include "../ArrayClasses.h"
#include "../Debugger.cpp"
// end of wrapper headers - those four are always necessary

// the actual function 

//hook at 0x71A92A
EXPORT _Temporal_AvoidFriendlies() {
	// (ASM knowledge) the ESI register contains a pointer to an instance of TemporalClass, let's get it
	TemporalClass *m = (TemporalClass *)Debugger::GetReg32(rESI); 

	// House that owns the unit firing this weapon
	HouseClass *hv = m->get_TargetUnit()->get_Owner();

	// House that owns the unit being erased
	HouseClass *ho = m->get_OwningUnit()->get_Owner();

	// if the two houses aren't allied with each other, there's nothing to fix
	if(!ho->IsAlliedWith(hv)) {
		return;
	}

	// (ASM knowledge) force the game to jump over the experience-granting code
	Debugger::SetReturnEIP(0x71A97D);
}

Compiling that code to a DLL and placing it in the game directory will give you this functionality...

... almost, there's one more step to do.

Registering the DLL/function with Syringe

To tell Syringe when to invoke the "_Temporal_AvoidFriendlies" function, you just need to create one extra file:

Let's say you called the DLL with that function temporal.dll. Now you need to create a plain text file called temporal.dll.inj in the same directory as the DLL is, and place the following line into it:

71A92A = _Temporal_AvoidFriendlies

That's all. Now, running YR via Syringe will invoke that functionality and prevent the units from gaining experience this way.

Compiler Specifics

gcc/MinGW (Dev-C++ and wxDev-C++)

If you're using gcc, you'll need to add an extra option to the C++ Compiler Options (Project Options -> Parameters -> C++ Compiler):

-masm=intel

Otherwise the compiler will spit out error messages and compilation will stop.