HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
DescentDevelopers
Descent3
C++2024–2025
DescentDevelopers / Descent3

Descent3

Descent 3 by Outrage Entertainment

7Distinct people
8Mentions
0Explicit recommenders
3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Descent 3 by Outrage Entertainment

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month8 dated mentions

Observed mentions: 2024-04-16 03:49:06 UTC to 2025-01-11 19:04:54 UTC.

02462024-04-01 00:00:00 UTC to 2024-05-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 commentsApr 20242024-05-01 00:00:00 UTC to 2024-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-06-01 00:00:00 UTC to 2024-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-07-01 00:00:00 UTC to 2024-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 00:00:00 UTC to 2024-09-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsAug 20242024-09-01 00:00:00 UTC to 2024-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-01 00:00:00 UTC to 2024-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-11-01 00:00:00 UTC to 2024-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2025-02-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 20242024-04-01 00:00:00 UTC2024-05-01 00:00:00 UTC615
May 20242024-05-01 00:00:00 UTC2024-06-01 00:00:00 UTC000
Jun 20242024-06-01 00:00:00 UTC2024-07-01 00:00:00 UTC000
Jul 20242024-07-01 00:00:00 UTC2024-08-01 00:00:00 UTC000
Aug 20242024-08-01 00:00:00 UTC2024-09-01 00:00:00 UTC110
Sep 20242024-09-01 00:00:00 UTC2024-10-01 00:00:00 UTC000
Oct 20242024-10-01 00:00:00 UTC2024-11-01 00:00:00 UTC000
Nov 20242024-11-01 00:00:00 UTC2024-12-01 00:00:00 UTC000
Dec 20242024-12-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
Jan 20252025-01-01 00:00:00 UTC2025-02-01 00:00:00 UTC101

What Hacker News says

8 sources
I'm not aware of it ever happening after a hack/leak - but years-gone-by I did ask people I knew who worked in the games industry specifically why they didn't release their games as open-source and I noticed that I kept on getting the same answer from people who worked at different companies: Activision, MS Game Studios, Westwood, Electronic Arts, etc etc. And we see the results of those concerns even when games do get open-sourced - for example, last week Descent 3's engine was released as open-source, and it was released without those parts (c.f.: https://github.com/DescentDevelopers/Descent3/blob/61bb9a337... ) ------- When a software company licenses a third-party library in source-form, invariably the license agreement includes a stipulation that the licensee take all reasonable precautions to prevent the release of the source-code -
Read the rest
so if it can be shown that CD Projekt Red was negligent in keeping their source secure such that it was leaked by HelloKitty, then they're open to civil liability here. Obviously the onus is on the plaintiffs to prove that CD Projekt Red was negligent here. I'm not accusing CD Projekt Red of being organizationally negligent myself; but I assume that most of their devs had a copy of their entire source-tree on their machines (just like I have all of my org's source on my machines) - and it only takes 1 person to disable their antivirus for something like this to happen. What I am saying is that it's possible that CD Projekt Red was negligent in keeping any licensed source-code reasonably secure, and that HelloKitty was aware of this fact, and used that as leverage in their extortion attempt: i.e. "we know you didn't secure your source-tree - and MIDDLEWARE_PROVIDER won't be happy about that and we estimate you'll owe MIDDLEWARE_PROVIDER about $500k if they find out, so if you pay us $250k we'll keep quiet about this, if not, we'll leak everything". Again, I'm just positing by connecting-the-dots here - I'm not making any assertions.
In HelloKitty ransomware rebrands, releases CD Projekt and Cisco data
I don't know how much Descent 3 shares with the original in terms of AI code, but Descent 3 seems to give NPCs a dynamic list of goals that's initialized based on their class ("stalker", "evader", etc.).[1] Each goal has a priority/weight, and criteria that will cause the goal to be enabled or not. Some of the goal enablers are straightforward, but others look more like state machine "emotion" states - fear, curiousity, etc.[2] Seems complex enough to meet the description on the box for the original Descent. [1] https://github.com/kevinbentley/Descent3/blob/86141b82295e71... [2] https://github.com/kevinbentley/Descent3/blob/86141b82295e71...
In Descent 3 Source Code
Some friends of mine played Descent competitively, and I was amazed to learn about so-called trichording: to maximize your speed, you need to press multiple keys at the same time to travel along all 3 axes at once, e.g. forward/right/up. The best players zip around the map diagonally. I always assumed this was a bug-turned-feature, like skiing in Tribes. When I saw the repo just now, I looked for clues, but didn't spot any related comments around the line of code where this ultimately happens: https://github.com/kevinbentley/Descent3/blob/142052a67d4318...
In Descent 3 Source Code

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.