An unofficial Hacknetjam focused on the vanilla game.


This jam is a personal initiative by FBIK. to champion a distinct design philosophy for Hacknet Extensions:

Powerful, innovative experiences can also be forged strictly within Vanilla Hacknet’s constraints

We operate on the belief that true creativity emerges from limitations, and thrives in a space of exploration rather than crunch.


To encourage Hacknet Extension developers to explore creation from a fresh perspective:

Unleash the potential of Hacknet Extensions.



A generous month-long period designed for thoughtful experimentation and iteration. The emphasis is on sustainable creation, free from time pressure.


The creative prompt revealed at the start of the cycle remains an open invitation. We welcome and encourage creations inspired by it at any time, even after the core event concludes.


Actions are restricted for use!

• You may use the following only as StartingActions, and their condition must be
  OnConnect target="playerComp"
  : AddAsset, AppendToFile, DeleteFile, CopyAsset
  
• You may use the following freely: ShowNode, RunFunction, StartScreenBleedEffect, CancelScreenBleedEffect, SaveGame, HideNode, HideAllNodes, GivePlayerUserAccount

You may NOT use any mods or tools that alter how Hacknet runs

Exceptions:

• fengxu-30338/HacknetChineseSupport[github.com] (essentially a Pathfinder mod to use custom fonts) but you can not open the MultiColorFontParse.
  
• fengxu-30338/HacknetFontReplace[github.com] New Version of HacknetChineseSupport, but you can not open the MultiColorFontParse.
  
• Any tools installed locally for development assistance that are not required for players to use. (e.g., AutumnRivers/HacknetThemeEditor[github.com])

The core 1-month creative cycle is currently planned for February 2026.

The creative challenge itself has no deadline.

• You shoud strictly follow The Challenge.
  
• All entries must comply with the Hacknet Community Code of Conduct[www.hacknet-os.com]. Use only assets you have the right to use, and be respectful to others.
  
• You are encouraged to form teams and collaborate on submissions.
  
• To keep the spirit of the jam fresh, any extension submitted before the jam prompt is revealed is not eligible for the jam timeline highlights.
  
• To ensure a fair and consistent review process for all participants, please do not update your Workshop submission after the 1-month event concludes. If you wish to continue developing your extension, we encourage you to create a new Workshop item for the updated version.
  
• Please show your email on the workshop description. It will be used to the Judgement of Community's Choice Highlights.

To be included in the jam timeline highlights, extensions must be uploaded to the Steam Workshop within the 1-month window and tagged with
You are welcome to iterate on your submission throughout the month. It is meant to encourage exploration, polish, and a healthy pace. Focus on a complete, solid idea rather than an overly ambitious scope.


The creative prompt remains open for interpretation indefinitely.
Simply use the tag on Steam Workshop whenever you finish! We may feature late submissions in future community highlights.


After the core event, we will celebrate the work in two ways:

• Community's Choice Highlights: A curated list of extensions that received the most positive feedback and plays from fellow participants.
  
• Host's Selection Highlights: A separate list of extensions that, in the host's view, most compellingly explore or demonstrate the jam's core design philosophy.

The purpose is to showcase diverse approaches and spark discussion.


Participants are encouraged to rate and provide constructive feedback on each other's work. See https://jam.hacknet.wiki/#judgement for more details.

Don't forget to show your email on the workshop description. It will be used to the Judgement of Community's Choice Highlights.


QQ Group: 940056115[qm.qq.com]

Also you can leave comments on this post.


See https://jam.hacknet.wiki