View on GitHub

Jeremy 'uniflare' Wade

github portfolio

Welcome to my github pages portfolio, here you will find a summary of some of my open source programming projects.

Who am I?

My name is Jeremy Wade (pseudonym uniflare), an enthusiastic coder from the UK that loves creating and fixing things - nothing brings me more happiness than helping someone smile. I started writing html after I got interested in the source code behind my favourite websites, at the time these related to the “Delta Force” series of games back from 2000 (being 11 at the time). PHP naturally followed this interest in website programming and I was hooked. Eventually writing applications in several other languages to solve problems I had or to make mine or someone elses life easier - usually small projects, solo. It was always ‘Just a hobby’, something in my down-time, something to relax with or get stuck into, something I could solve problems with, make a difference to someone - or myself.

Fast forward around 16 years, I get an interest in C++ programming (I always wanted to learn C or C++ but it was a ‘mystical’ language to me back then dealing with compilers etc - php just worked for me). I make the decision to finally learn C++ (the ‘ultimate’ language - my thoughts at the time). Wrote some simple snippets, experimented, just played around… then comes CRYENGINE, I heard people say it is the most difficult engine to master, that the code is hard to understand. Perfect! CRYENGINE - the most visually stunning and ground breaking engine of the Crysis series - time to see what the fuss is about!

I have become more and more of a regular cryengine community member for the better part of a year now and I am thoroughly enjoying my time.


CRYENGINE V - Splash Screen Plugin

Splash Screen Plugin for CRYENGINE 5.3 CMakeC++
GitHub Repository
CRYENGINE Marketplace (Unavailable due forum account bugs, back soon)

Goals

Requirements

Issues

The wide compatiblity requirement did present some issues, the biggest of which involved the default profile that the GameSDK Project uses. To work around the issues, I had to implement my own method of detecting whether the current profile is indeed the default profile.

The most sucessfull & effective method that I found was to store a special attribute in the player profile. Since the splash plugin is supposed to be loaded on the very first run, it should have primary access to the profile management system. eg.

if (!m_pCurrentProfile->GetAttribute("SplashFlag_FirstRun", bSplashFlag, false))
{
	...
}

I decided the risk of having this plugin added during an already released game and a user that set the lowest supported resolution was adequately low. A positive side-effect of this implementation appears to ‘Fix’ the initial default GameSDK Profile management code that deals with the user resolution settings.

tl’dr


CMakeGen

CMakeLists.txt Generator CMakeC++
GitHub Repository

Goals

Requirements


Arma 2/3 - Server Keepalive Batch Tools

Server Keepalive Batch Tools BatchFileC#
GitHub Repository

Goals

Requirements

Issues

The buggest issues were the batch scripting itself, learning the intricacies of windows Batch File (or.. ‘Modern DOS’) was an interesting experience. Definitely not reccommended to use batch for this kind of advanced functionality but it works.

tl’dr


Contribution - CE Tools

Python
GitHub Repository

Purpose of script

To provide an easy alternative for new CE developers to quickly package a development build of their game to pass to users without, for example, the engine, or launcher to run and test the game.

Purpose of contribution


Activity - CRYENGINE Forums

Getting Started with CE guides
Forum Profile