Bitl Development Studio

here are their names and ids:

bitl1- 1390096248551378984
bitl0 - 1390601655174565928
bitll0 - 1390091530714353815

this seems to only be a problem in Novetus, but i'm posting here as well

bitll0's profile

bitl1's profile

bitl0's profile

Hi all, I wanted to inform everyone that there's accounts trying to impersonate me on Discord.

if you get a friend request from "bitl0", "bitll0", or "bitl1", block them immediately.

the only real accounts are bitl and bitldevstudios.

potu album art

the album will have two parts. the first 4 tracks will focus on the origin of the border world, ziocronica, and its history up to that point. the rest of the album will focus on the resistance's fight for survival.

a world between three (mentioned on my dev account) has been renamed to persecution of the unwilling, the title of the planned second album that would come after a world between three. i did this so the final album feels more complete as a whole.

Bit of an update related to the ZIOCRONICA project:

- Projects can be considered non canon. You can see if a project is non canon if it has Z0 as the prefix.

Updated ids:

Z0-C1 - FIREFIGHT RELOADED CODEX
Z0-C2 - Novetus Tales of the Spheres Item

Z1-A1 - a world between three

Bit of an update for this:

C projects may now be considered non-canon, but people are allowed to make up their headcanon if C projects are canon to the ZIOCRONICA project or not.

Was used for an old novetus version as was added in as an easter egg

The Writing and recording of our next album is underway.
We’re looking forward to the new The Resistance record.

-Bitl

So, this means the following:

FIREFIGHT RELOADED's upcoming CODEX will have the designation Z1-C1, as this is the first released story in terms of canon.

The Novetus item, "Tales of the Spheres", will be Z2-C2.

a world between three will be Z3-A1.

There are multiple definitions for these project identifiers.

A - Album
S - Serial, written story.
G - Game, reserved for the unannounced project
C - Connections/cameo, used to specify the connection between the ZIOCRONICA project and a project separate from it that are connected in some form.

Then, the second part is the project identifier and the number relative to how many of the related projects there are. For example, the 10th album release would be known as A10.

To identify each release, there will be an ID system for each release in the format below:

Z#-[A-Z]#

Z means ZIOCRONICA, and specifies the project number and its order in the canon. For example, a world between three would be known as Z3.

Hi all!

Rather recently, I decided to make the ZIOCRONICA project a thing, which will be a series of various multimedia projects leading up to the release of a unannounced project. The first project in this is being developed as the "a world between three" album project.

Nevermind this, quiver fortress will be developed alongside survivor 2, both projects as of now are in active development.

Mods will still be maintained (such as FIREFIGHT RELOADED, which has an update in development that was paused due to Quiver development), however I plan on focusing on a new IP sometime in the near future.

I have stated in some Discord servers that I was also interested in making a Nerf FPS, but that won't be done as I plan for Quiver Fortress and SURVIVOR II to be my final 2 new source engine mods for the foreseeable future.

I'm more confident in my programming abilities now than I was in the past, and so I feel like I'll be able to finally finish something that should have been done to begin with.

It will be on the new Source SDK 64 bit version (specifically the BDS BASE fork I've used for Quiver Fortress) and I plan on recreating virtually every part of the original arcade game from scratch.

The original SURVIVOR mod released in a virtually unfinished state and had ambitions that I wasn't able to fulfill due to my focus on FIREFIGHT RELOADED and other projects. However, I plan on finishing SURVIVOR, for real this time.

NEW PROJECTS

A while back on ModDB I stated that I'm interested in making a sequel to one of my projects that I've archived. That sequel will be SURVIVOR II, a remake of a remake of Half-Life 2 Survivor Ver 2.0. I have a reason for doing this.

I should also state that this wasn't caused by any external events. This was my original decision that was done without any external influence.

The project has caused so much unneeded stress over the last few months that I felt it would be healthier to shelve it and come back to it later. I'm not done with modding, however.

Hi all, i have some news I'd like to share regarding Quiver fortress and a planned project. 🧵

QUIVER FORTRESS UPDATE

Due to development problems and issues, Quiver Fortress will be shelved for the foreseeable future. Not cancelled, but shelved at least until I'm ready to go to the project again.

Update: there will be no teaser this Halloween, read this thread for more updates:

bsky.app/profile/bitl...

long development and delays. I've been dealing with a job and school, so I have limited free time I can put towards my projects.

Quiver Fortress is expected to release around 2026 at the latest.

a merging between TF2 and QTF/TFC as originally envisioned.This means I want to consider ideas from TF2's various development ideas, which includes ideas from Valve's Team Fortress all the way to TF2, and post release ideas.

I hope I can unveil SOMETHING soon at some point. I apologize for the-

Small update thread:

Unfortunately, there won't be a Quiver Fortress teaser this Halloween as previously stated as I realized I need more time to get the mod to a more finalized state. The vision for the mod changed halfway through development to be more of a tribute to TF as a whole rather than-

Quiver Fortress will have a proper teaser trailer coming out this Halloween! (Or later)

ModDB page coming sometime afterwards.

hey all, some disappointing news, i don't feel like I can get quiver fortress ready for a reveal on 8-8-25, so that has been postponed until further notice.