Graphic Designer

We are lookimg for a graphic designer to work on graphics associated with the Flint/Ember Anti cheat.

You will be integral part of bringing out brand identity to life designing a logo, graphics fot the website and working with social media team and promotional graphics

You can find below who/what Flint is and we look forward to bringing in more people to the team

Flint Anti-Cheat

----------------

    What are we building?

Flint is a new anti-cheat engine, fully open source, cross-platform, and designed from the ground up for reusability in gaming communities like DFBHD, by game development hobbyists and game studios of any size. It carries forward a decade of lessons from the legacy of DFBHD's Evosoft ACP (2008-2018) and its commercial spin-off.

Ember is an implementation and proof of concept of Flint, built specifically for the DF:BHD community.

All products as part of this project are open-source. There's no black-box knowledge (i.e. questionable kernel driver logic). You can read every line of code, understand exactly what it does, and build/verify it yourself.

By being open-source, running under the AGPL-3.0 license (dubbed "copy-left"), we invite everyone to join us to help shape the direction. Experts can challenge the logic and algorithms, and contribute additional features, detections, fixes and platform support.

    How does Flint work?

Flint contains a Watchdog (IPC), detection algorithms, fingerprinting (i.e. hardware ID logic), layered signal scoring, and it only watches and reports. It observes system state, memory patterns, loaded modules, input behaviour, and timing anomalies.

But if cheaters can read the source, can't they just bypass it? Sure, they can try. Flint (and Ember by extension) contain build- and runtime randomizations and stack all independent signals, making bypassing all detections at once a sizable task. 100% Is impossible. We're not building a wall, we're imposing a tax.

A false positive that bans or stains the reputation of a legitimate player is the worst possible outcome and a critical issue. Signal scoring is highly conservative by design, and (continuously) tuned for confidence and accuracy.

    What is Ember?

Ember uses Flint as its core engine, and comes with a player-facing anti-cheat client (Agent), a gameserver component (Relay), a player-facing web portal (Lobby), an administrative portal (Forge) and an API/backend.

The API is being used by the Lobby, which means anyone can consume all Lobby-visible data for their own products. Relay can be extended with custom small C#.NET plugins, using Events & Actions exposed by Relay. Plugins are near-limitless: interacting with gameplay statistics, custom rule enforcement and various ways of player interaction (i.e. chat commands).

Ember isn't going to replace or sideline the tools the community has already built. Relay's plugin system exists so server hosters can extend it to fit their needs, and all the data surfaced through the Lobby (API) is designed to give the community more to work with to make their tools better.

Relay additionally offers "Ember-only" and "Match-mode" options. Ember-only restricts the gameserver for users running the Agent. Match-mode bypasses ban-waves, meaning accumulated signals that cross a certain threshold, result in the player immediately getting kicked from the server, rather than waiting for a ban wave.

Ember has no account system. Your identity is your hardware, a fingerprint (hardware IDs) collected at launch. You pick a display name, set a 4-digit PIN, and you're in. You can optionally add an e-mail address for recovery purposes. If you upgrade your PC, through fuzzy matching, a simple migration flow is handled automatically. Slightly more complex upgrades are handled with the PIN and/or e-mail address.

    Erm, but my data?

Nothing leaves your PC unhashed or unprotected. Your e-mail address is optional and (along with your PIN) encrypted in the database.

    What's next?

The project is currently in active design and early implementation phase. Architectural and research docs are complete, and we're just starting the first tests.

As soon as the system is live and operational, and you want to get involved, you don't need to be a security expert or a software engineer. If you have an interest in contributing, there's work here for you. The binaries are being written in C#.NET 10. Python is used for the Ember backend/API, and public facing pages are using TypeScript (React, TBD).