A new weapon class can be added by implementing the CItem and IWeapon interfaces. A basic weapon implementation is supplied in the GameDLL project which provide the most commonly required weapon functionality:
When implementing a new weapon class, it's recommended to derive from the CWeapon class. The following functions from CWeapon are the most common ones overridden to provide new gameplay functionalities:
CWeapon already implements the common weapon action possibles like attack, reload, zoom and changing the fire mode. A new weapon requiring new actions from the player should override this function.
This function is called when the actor select/deselect the weapon as his current item. Any code which modifies the camera/rendering settings should be placed in this function.
The CItem implementation will make sure that the action does not already carry this weapon. When overriding this function, it is possible to add conditions which rule if the actor is allowed to pickup the weapon.
Should handle adding the weapon to the actor inventory. Please note that after CItem::PickUp has been called, it's no longer possible to refuse the actor from picking up the weapon. The appropriate code to validate the actor from taking the weapon should be placed in the CanPickUp() function.
The final step for your custom weapon, to be useable in the weapon xml file, is to register it in the Game Factory (
Code\Game\GameDll\GameFactory.cpp), the central point to register new Game Objects:
Fire Mode Class
The GameSDK example code already includes many unique fire modes:
In case these fire modes aren't sufficient, it's possible to implement a new fire mode by deriving from the IFireMode interface:
In most of the cases, deriving from the existing CSingle class should simplify this process. If this approach is followed, the following functions are usually the only ones needed to override:
Description of the functionalities already provided by CSingle
Triggers the appropriates effects and sounds, resets state variables.
Performs various tests to be sure ammunition are still available and that the weapon isn't overheating.
Search the in inventory to be sure the actor carries the clips for ammunition required.
Triggers the appropriates effects and sounds, performs hit computations.
Performs various frame dependent computations for different weapon features including auto-aim, zoom, recoil and heat accumulation.
The final step for your custom fire mode, to be useable in the weapon xml file, is to register it in the Weapon System implementation (
The CProjectile class implemented in the GameDLL project provides most of the functionality needed. It is possible to extend this class by deriving from it, for example to implement new functionality for homing missiles or to have a new class of explosives.
When deriving from CProjectile, the following functions should be able to give enough flexibility to expand its gameplay features.
Function used to handle game events, the ideal location to deal with collisions.
Provides a way to adjust or setup any functionality before the projectile is shot by the weapon.
After the projectile was launched, this function is called at every frame until the projectile reaches its destination.
If the weapon has any auto-aiming capabilities, this function will be called with the world position of the target.
If the weapon has any auto-aiming capabilities, this function will be called with entity id of the locked target.
The final step for your custom projectile is to register it in the Weapon System implementation (
Zoom Mode Class
The SDK example already includes the following zoom modes: IronSight and Scope. In case you need a customized zoom mode for your weapon it's possible to implement a new zoom mode by deriving from the IZoomMode interface:
In most of the cases, deriving from the existing CIronSight class should simplify this process. If this approach is followed, the following functions are usually the only ones needed to override:
Description of the functionalities already provided by CIronSight
Triggers when entering zoom mode.
Triggers when leaving zoom mode.
Triggers when switching the actual zoom step.
Updating/Changing any first person view parameters should go here.
The final step for your custom zoom mode is to register it in the Weapon System implementation (
The Weapon XML
Creating the final weapon is completely done in an easy to edit XML file, which should be stored in
A good starting point for creating your own weapon XML implementation is to use the shipped Rifle.xml script. It already includes everything you need to have a usable and realistic weapon. More details about the general structure of a weapon XML implementation can be found via comments inside the Rifle.xml weapon example.