#System debugger

[redacted-coiner]

Mutual, Idol, and Family Systyle

Judge, Charge, Lawyer

Shepherd, Debugger, Buffer

DNI is listed within my pinned post. Please go read it before interacting with any part of my content. Ask to tag!

[the-silent-fellowship]

Debugger

[PT: Debugger]

“Debuggers are protectors that make sure the system does not slip back into old patterns of abuse (or rather, being abused). They work with headmates such as instructed-persecutors, double agents, and fawn response holders. Debuggers may have or gain some control over their system in order to overwrite another headmate's triggered response or the effects of a scriptwriter.” - Pluralpeida(link)

[ID: none yet]

[Tagging] @radiomogai, @pluralitywords, and @pluralterms

[ozzyfromthecafeteria]

something that is so so frustrating about dealing with and healing from trauma is the way we’ve slid back to performing the same habits and responses every time a situation or emotion that is entirely unfamiliar to us arises. wraps the brain up with a soft blanket shh shh you don’t have to fawn anymore it’s fine it’s so fine it would blow your mind how fine everything is.

[anheliotrope]

Rambling About C# Being Alright

I think C# is an alright language. This is one of the highest distinctions I can give to a language.

Warning: This post is verbose and rambly and probably only good at telling you why someone might like C# and not much else.

~~~

There's something I hate about every other language. Worst, there's things I hate about other languages that I know will never get better. Even worse, some of those things ALSO feel like unforced errors.

With C# there's a few things I dislike or that are missing. C#'s feature set does not obviously excel at anything, but it avoids making any huge misstep in things I care about. Nothing in C# makes me feel like the language designer has personally harmed me.

C# is a very tolerable language.

C# is multi-paradigm.

C# is the Full Middle Malcomist language.

C# will try to not hurt you.

A good way to describe C# is "what if Java sucked less". This, of course, already sounds unappealing to many, but that's alright. I'm not trying to gas it up too much here.

C# has sins, but let's try to put them into some context here and perhaps the reason why I'm posting will become more obvious:

C# didn't try to avoid generics and then implement them in a way that is very limiting (cough Go).

C# doesn't hamstring your ability to have statement lambdas because the language designer dislikes them and also because the language designer decided to have semantic whitespace making statement lambdas harder to deal with (cough Python).

C# doesn't require you to explicitly wrap value types into reference types so you can put value types into collections (cough Java).

C# doesn't ruin your ability to interact with memory efficiently because it forbids you from creating custom value types, ergo everything goes to the heap (cough cough Java, Minecraft).

C# doesn't have insane implicit type coercions that have become the subject of language design comedy (cough JavaScript).

C# doesn't keep privacy accessors as a suggestion and has the developers pinkie swear about it instead of actually enforcing it (cough cough Python).

Plainly put, a lot of the time I find C# to be alright by process of elimination. I'm not trying to shit on your favorite language. Everyone has different things they find tolerable. I have the Buddha nature so I wish for all things to find their tolerable language.

I do also think that C# is notable for being a mainstream language (aka not Haskell) that has a smaller amount of egregious mistakes, quirks and Faustian bargains.

The Typerrrrr

C# is statically typed, but the typing is largely effortless to navigate unlike something like Rust, and the GC gives a greater degree of safety than something like C++.

Of course, the typing being easy to work it also makes it less safe than Rust. But this is an appropriate trade-off for certain kinds of applications, especially considering that C# is memory safe by virtue of running on a VM. Don't come at me, I'm a Rust respecter!!

You know how some people talk about Python being amazing for prototyping? That's how I feel about C#. No matter how much time I would dedicate to Python, C# would still be a more productive language for me. The type system would genuinely make me faster for the vast majority of cases. Of course Python has gradual typing now, so any comparison gets more difficult when you consider that. But what I'm trying to say is that I never understood the idea that doing away entirely with static typing is good for fast iteration.

Also yes, C# can be used as a repl. Leave me alone with your repls. Also, while the debugger is active you can also evaluate arbitrary code within the current scope.

I think that going full dynamic typing is a mistake in almost every situation. The fact that C# doesn't do that already puts it above other languages for me. This stance on typing is controversial, but it's my opinion that is really shouldn't be. And the wind has constantly been blowing towards adding gradual typing to dynamic languages.

The modest typing capabilities C# coupled with OOP and inheritance lets you create pretty awful OOP slop. But that's whatever. At work we use inheritance in very few places where it results in neat code reuse, and then it's just mostly interfaces getting implemented.

C#'s typing and generic system is powerful enough to offer you a plethora of super-ergonomic collection transformation methods via the LINQ library. There's a lot of functional-style programming you can do with that. You know, map, filter, reduce, that stuff?

Even if you make a completely new collection type, if it implements IEnumerable<T> it will benefit from LINQ automatically. Every language these days has something like this, but it's so ridiculously easy to use in C#. Coupled with how C# lets you (1) easily define immutable data types, (2) explicitly control access to struct or class members, (3) do pattern matching, you can end up with code that flows really well.

A Friendly Kitchen Sink

Some people have described C#'s feature set as bloated. It is getting some syntactic diversity which makes it a bit harder to read someone else's code. But it doesn't make C# harder to learn, since it takes roughly the same amount of effort to get to a point where you can be effective in it.

Most of the more specific features can be effortlessly ignored. The ones that can't be effortlessly ignored tend to bring something genuinely useful to the language -- such as tuples and destructuring. Tuples have their own syntax, the syntax is pretty intuitive, but the first time you run into it, you will have to do a bit of learning.

C# has an immense amount of small features meant to make the language more ergonomic. They're too numerous to mention and they just keep getting added.

I'd like to draw attention to some features not because they're the most important but rather because it feels like they communicate the "personality" of C#. Not sure what level of detail was appropriate, so feel free to skim.

Stricter Null Handling. If you think not having to explicitly deal with null is the billion dollar mistake, then C# tries to fix a bit of the problem by allowing you to enable a strict context where you have to explicitly tell it that something can be null, otherwise it will assume that the possibility of a reference type being null is an error. It's a bit more complicated than that, but it definitely helps with safety around nullability.

Default Interface Implementation. A problem in C# which drives usage of inheritance is that with just interfaces there is no way to reuse code outside of passing function pointers. A lot of people don't get this and think that inheritance is just used because other people are stupid or something. If you have a couple of methods that would be implemented exactly the same for classes 1 through 99, but somewhat differently for classes 100 through 110, then without inheritance you're fucked. A much better way would be Rust's trait system, but for that to work you need really powerful generics, so it's too different of a path for C# to trod it. Instead what C# did was make it so that you can write an implementation for methods declared in an interface, as long as that implementation only uses members defined in the interface (this makes sense, why would it have access to anything else?). So now you can have a default implementation for the 1 through 99 case and save some of your sanity. Of course, it's not a panacea, if the implementation of the method requires access to the internal state of the 1 through 99 case, default interface implementation won't save you. But it can still make it easier via some techniques I won't get into. The important part is that default interface implementation allows code reuse and reduces reasons to use inheritance.

Performance Optimization. C# has a plethora of features regarding that. Most of which will never be encountered by the average programmer. Examples: (1) stackalloc - forcibly allocate reference types to the stack if you know they won't outlive the current scope. (2) Specialized APIs for avoiding memory allocations in happy paths. (3) Lazy initialization APIs. (4) APIs for dealing with memory more directly that allow high performance when interoping with C/C++ while still keeping a degree of safety.

Fine Control Over Async Runtime. C# lets you write your own... async builder and scheduler? It's a bit esoteric and hard to describe. But basically all the functionality of async/await that does magic under the hood? You can override that magic to do some very specific things that you'll rarely need. Unity3D takes advantage of this in order to allow async/await to work on WASM even though it is a single-threaded environment. It implements a cooperative scheduler so the program doesn't immediately freeze the moment you do await in a single-threaded environment. Most people don't know this capability exists and it doesn't affect them.

Tremendous Amount Of Synchronization Primitives and API. This ones does actually make multithreaded code harder to deal with, but basically C# erred a lot in favor of having many different ways to do multithreading because they wanted to suit different usecases. Most people just deal with idiomatic async/await code, but a very small minority of C# coders deal with locks, atomics, semaphores, mutex, monitors, interlocked, spin waiting etc. They knew they couldn't make this shit safe, so they tried to at least let you have ready-made options for your specific use case, even if it causes some balkanization.

Shortly Begging For Tagged Unions

What I miss from C# is more powerful generic bounds/constraints and tagged unions (or sum types or discriminated unions or type unions or any of the other 5 names this concept has).

The generic constraints you can use in C# are anemic and combined with the lack of tagged unions this is rather painful at times.

I remember seeing Microsoft devs saying they don't see enough of a usecase for tagged unions. I've at times wanted to strangle certain people. These two facts are related to one another.

My stance is that if you think your language doesn't need or benefit from tagged unions, either your language is very weird, or, more likely you're out of your goddamn mind. You are making me do really stupid things every time I need to represent a structure that can EITHER have a value of type A or a value of type B.

But I think C# will eventually get tagged unions. There's a proposal for it here. I would be overjoyed if it got implemented. It seems like it's been getting traction.

Also there was an entire section on unchecked exceptions that I removed because it wasn't interesting enough. Yes, C# could probably have checked exceptions and it didn't and it's a mistake. But ultimately it doesn't seem to have caused any make-or-break in a comparison with Java, which has them. They'd all be better off with returning an Error<T>. Short story is that the consequences of unchecked exceptions have been highly tolerable in practice.

Ecosystem State & FOSSness

C# is better than ever and the tooling ecosystem is better than ever. This is true of almost every language, but I think C# receives a rather high amount of improvements per version. Additionally the FOSS story is at its peak.

Roslyn, the bedrock of the toolchain, the compiler and analysis provider, is under MIT license. The fact that it does analysis as well is important, because this means you can use the wealth of Roslyn analyzers to do linting.

If your FOSS tooling lets you compile but you don't get any checking as you type, then your development experience is wildly substandard.

A lot of stupid crap with cross-platform compilation that used to be confusing or difficult is now rather easy to deal with. It's basically as easy as (1) use NET Core, (2) tell dotnet to build for Linux. These steps take no extra effort and the first step is the default way to write C# these days.

Dotnet is part of the SDK and contains functionality to create NET Core projects and to use other tools to build said projects. Dotnet is published under MIT, because the whole SDK and runtime are published under MIT.

Yes, the debugger situation is still bad -- there's no FOSS option for it, but this is more because nobody cares enough to go and solve it. Jetbrains proved anyone can do it if they have enough development time, since they wrote a debugger from scratch for their proprietary C# IDE Rider.

Where C# falls flat on its face is the "userspace" ecosystem. Plainly put, because C# is a Microsoft product, people with FOSS inclinations have steered clear of it to such a degree that the packages you have available are not even 10% of what packages a Python user has available, for example. People with FOSS inclinations are generally the people who write packages for your language!!

I guess if you really really hate leftpad, you might think this is a small bonus though.

Where-in I talk about Cross-Platform

The biggest thing the ecosystem has been lacking for me is a package, preferably FOSS, for developing cross-platform applications. Even if it's just cross-platform desktop applications.

Like yes, you can build C# to many platforms, no sweat. The same way you can build Rust to many platforms, some sweat. But if you can't show a good GUI on Linux, then it's not practically-speaking cross-platform for that purpose.

Microsoft has repeatedly done GUI stuff that, predictably, only works on Windows. And yes, Linux desktop is like 4%, but that 4% contains >50% of the people who create packages for your language's ecosystem, almost the exact point I made earlier. If a developer runs Linux and they can't have their app run on Linux, they are not going to touch your language with a ten foot pole for that purpose. I think this largely explains why C#'s ecosystem feels stunted.

The thing is, I'm not actually sure how bad or good the situation is, since most people just don't even try using C# for this usecase. There's a general... ecosystem malaise where few care to use the language for this, chiefly because of the tone that Microsoft set a decade ago. It's sad.

HOWEVER.

Avalonia, A New Hope?

Today we have Avalonia. Avalonia is an open-source framework that lets you build cross-platform applications in C#. It's MIT licensed. It will work on Windows, macOS, Linux, iOS, Android and also somehow in the browser. It seems to this by actually drawing pixels via SkiaSharp (or optionally Direct2D on Windows).

They make money by offering migration services from WPF app to Avalonia. Plus general support.

I can't say how good Avalonia is yet. I've researched a bit and it's not obviously bad, which is distinct from being good. But if it's actually good, this would be a holy grail for the ecosystem:

You could use a statically typed language that is productive for this type of software development to create cross-platform applications that have higher performance than the Electron slop. That's valuable!

This possibility warrants a much higher level of enthusiasm than I've seen, especially within the ecosystem itself. This is an ecosystem that was, for a while, entirely landlocked, only able to make Windows desktop applications.

I cannot overstate how important it is for a language's ecosystem to have a package like this and have it be good. Rust is still missing a good option. Gnome is unpleasant to use and buggy. Falling back to using Electron while writing Rust just seems like a bad joke. A lot of the Rust crates that are neither Electron nor Gnome tend to be really really undercooked.

And now I've actually talked myself into checking out Avalonia... I mean after writing all of that I feel like a charlatan for not having investigated it already.

[techav]

On Accepting Victories Where They Come

At the end of my last post on getting NetBSD running on my 68030 homebrew computer, I had a (mostly) working root shell prompt in single-user mode.

Well here we are a week or so later and I have ... a (mostly) working root shell prompt in single-user mode.

It turns out bringing up a modern operating system is hard.

The first problem was the default collection of init scripts. There are a ton of scripts in /etc/rc.d that are run at startup to finish bringing up the system after the kernel is loaded but before users can log in. These scripts do things like check filesystem integrity, mount disks, initialize networking, etc. Most of the scripts are not relevant to my specific hardware, but I wasn't even getting far enough along for that to matter. I was getting stuck early on in two steps in particular: filesystem checks and initializing /dev/random.

The latter issue there's not really anything I can do about. I can copy a pre-populated entropy file from an existing system, but I don't have the hardware support for random number generation. Frankly I don't need it either, if I'm not doing anything with cryptography like using TLS certificates. So remove that script.

I can check and repair the filesystem much faster on my host machine, so remove that script for now also.

And remove all of those networking-related scripts since I don't have the hardware for networking either.

…

It turns out init scripts have declared dependencies on other scripts. So removing one, especially an early important one like checking filesystem, means editing others to continue without it. It's dependency hell.

So for the sake of just getting things running, I removed everything and wrote my own. There were just a few things I really needed, like mounting the root filesystem as writeable and initializing TTYs.

It took a few tries to get it right, but my init script did eventually run without stalling. This was it, time for it to initialize the terminals and print the login prompt …

init: can't add utmpx record for 'tty01': Bad file descriptor

… That's not a login prompt. That's not a login prompt at all. What does that even mean? What on earth is utmpx?

The error message itself is printed by init. UTMPX keeps record of logged-in users, and it does so using a file, /var/run/utmpx. But is the bad file descriptor error relating to that file or to /dev/tty01?

I was stuck here for a while. I tried everything I could think of to make sure my tty devices were created properly and with the right major/minor numbers and permissions. I finally realized that I didn't get the error if the utmpx file didn't exist. So something was wrong with writing the file, possibly due to never being able to properly shut down and close out the file & filesystem any time it got created. But it's easy enough to just make sure it's deleted by the init script before getting to that point.

It's at this point where I went down a rabbit hole of trying to create a RAM disk for root just to eliminate the possibility of lingering problems with the ATA driver or similar. This proved to be a dead end because the system would only boot single-user from a RAM disk, and I also got stuck in dependency hell trying to get it to compile a RAM disk image that included the actual login binary.

After some more experimentation, I learned that if I had no extra terminals defined in /dev/ttys, then it would at least show the login prompt on the root console, but would never actually log in. Kernel debugger & SIGINFO would show that login was stuck waiting for something. If I did have multiple terminals defined, I would never see a login prompt and it would show that getty, which spawns the terminals, was sleeping, waiting for something.

And that's where I'm stuck. I have no idea what these programs are waiting on, and don't really have any way to check. I suspect it's possible they need those hardware interrupts I don't have, but since I can see activity on the UART chip select lines, I don't think that's the case.

So for now, facing a looming deadline and burnout setting in after a solid month of working on this, I've decided to accept the victory I have and admit defeat where I must. I have a computer that I built myself which can load and run a modern operating system up to the point of a root shell prompt. That is a remarkable accomplishment and I will absolutely accept that victory. There is already so much the machine is capable of just getting to that point. And going from knowing nothing about porting an OS to a new machine to having a running shell in under a month is a victory all on its own.

But, I was not able to get it fully running in multi-user mode on all of my terminals. I will happily accept that defeat in light of the major victory of getting as far as I have.

So, with VCFSW coming up very soon, I've decided to turn my attention back to my multi-user BASIC system. I have a few refinements and new features in mind that I would love to have ready by the show.

[darkfluffydragon]

Cookie Run AU Ideas #6: System Error

Cookie Run Kingdom.

An adorable gacha game filled with hundreds of cookie characters to collect, and a complex story. Not that the inhabitants know of it, they're quite unaware of their digital nature.

The five Virtues, the souljams. Core systems of the software keep it running and functional, each with its own [AWARE_PROGRAM] to oversee the duty.

Silent Salt: The Debugger, in charge of fixing errors in code and erasing any that is deemed unnecessary.

Eternal Sugar: The Task Manager, opening and closing programs that are needed for the developers or to help them work easier.

Burning Spice: The Firewall, keeping away viruses and hackers as well as occasionally messing with combining forces with

Silent Salt. Mystic Flour: The Control System, relegating tasks to the other four when required and keeping everyone in check.

Shadow Milk: The Record Keeper, in charge of keeping an archive of every edition of the code, every past, present, and future change to the entirety of the game as well as the plans the developers have in store. He is also in charge of assisting developers add code to help, if necessary.

So when the [AWARE_PROGRAM]s begin to malfunction, and begin to corrupt, the developers witches decide to do what they must. They take away the Core SystemsSouljams from the [AWARE_PROGRAM]Beasts, and seal them away in the Silver Tree, creating a guardian to keep them locked away.

The Souljams are edited to function systematically, without the need of anyone leading it, and given to those unaware of its true purpose yet still worthy of holding the power.

And then The Record Keeper wakes up, confused. Why had he been locked up? Why had they all been locked away? Had they not just been doing what they had been told to do?...who is this [ASSET] who now holds his Core System?

Pure Vanilla Cookie is very confused on the floating cookie that appeared one day and now refuses to leave him alone. Meanwhile, Elder Faerie feels something is off about the Silver Tree, but isn't quite too sure what.

or:

Pure Vanilla teaches AI Shadow Milk how to be a cookie, while AI Shadow Milk ponders if he should explain the reality of their existence to Pure Vanilla.

[ariidis]

Some other computer/cybercore group system terms for you !

System - BIOS, Motherboard, NOC (Network Operations Center), Webring, Harddive

Headmate/Alter - Debugger, Webmaster, Installation Wizard, Malware, Virus, Computer Worm, Netizen, Websurfer

~ @charmy-gr33n

YOOO THESE ARE SO COOL!!

webmaster for a host is such a cool idea

and OMG INSTALLATION WIZARD ‼️‼️‼️

[m0n0z-brainbuddiez-f0r-y0u]

replying to the thing from our last ask um mayb levelODDBALL

here ya g0! i h0pe y0u n he liek thiz. i went f0r a l0ser werew0lf b0y :3 wh0se a pr0tective s0ftie (kinda)

name(s): erebus, onyx, malachai, dominic, ash, zero

nickname(s): ere, mal, chai, dom, nic, little loser, freak, freaky wolf, loser freak

pronouns: he/him, ey/em, it/its, bite/bites, hx/hxm, ix/ixs

gender(s): gender apathetic, transneumasc boything, myodryogyne | monacharic, internet-addictloser, losermasc, StPDloser

sexuality: omnisexual, biromantic | loser attraction

age: 29-46 age slider, age apathetic

species: werewolf

role(s): apathy holder, aegir, debugger, cassmate

sign off: 💣

transids: transtraumabond, transGerman, transunhealover, transSHscars, transAvPD, transPPD, transpervert, transraspyvoice, transintersex, transcigsmoker, transthreat, transhikkiomori, translowempathy, transwitnessprotection, transDBMC, naltraumatized, perma2000s, cigarettescentian, alcoholscentian

cisids: nonhuman, werewolf, tan skin, mixed race, Mexican, Moroccan, white, brown hair, long hair, moles, brown eyes, fangs, scarred, piercings, hairy, autistic, StPD, NPD, ASPD, DPDR, chronic depression, weak leg muscles, cane user, athiest, weeb, otaku, hentai addict, eccentric, suspicious, quiet, curious

paras: anthrozoophilia, sadist, necrophile, autozoophilia, autogratiophilia, odontophilia, spectrophilia, fictoMAP, kodacon

likes: smell of cigarettes/smoke in general, napping, taking control of high stress situations, being in leader roles, manga, anime, hentai

dislikes: seeing others being taken advantage of, nonconsensual acts, smell of gasoline, being in danger, most emotional people, messy/disorderly rooms, most random people the system doesnt know

typing quirk: "I Type Like This." | "The Quick Fox Jumps Over The Lazy Dog." | "What is it? Oh, Yeah, I Guess This Is My Typing Quirk, Nothin' Special."

personality traits: suspicious of others, curious, loyal, protective, eccentric

front triggers: 2000s anime, grunge/alt rock bands, online arguments, intense situations that are emotional, protecting vunerable headmates, percieved relapses of self harm/falling back into abuse (if applicable)

faceclaim:

[free-willowmates]

the broken script entity pack part 2

decided to put these in one post for my convenience, take whatever you like :D

under the cut: xXram2dieXx, corruption, circuit, the broken end

r2 pack

names: ronald, reginald, apollo

pronouns: rhe/rhem, fuck/fucks, voi/voids, two/twos

system: altpackgenic, debugger, chainbreaker

age: infinite

orientations: shadowlesboy

genders: ketugender

other: wishqueer, influenced by minecraft

likes: being in the dark, kid icarus uprising (game), doctor nowhere

mannerisms: speaks in third person, has an eerie smile

xXram2dieXx pack

names: hex, jax/jack/jaxson

pronouns: hex/hexs, x/xs, hx/hxm, xny pronouns

system: altpackgenic, debugger,

age: agehazy middle

orientations: fin, min, shadowturian

genders: mcbuilt, emeraldgender, orbgender

other: wishqueer, influenced by minecraft, mcboggedstelic

likes: minecraft minigame servers, vivily (youtuber), building roller coasters in minecraft, roller coaster tycoon 1 and 2

mannerisms: easily discouraged but generally friendly

corruption pack

names: webber, scrap, anomaly, 1, cobblestone

pronouns: soul/souls, knife/knifes, web/webs

system: altpackgenic, melponic, double agent

age: minechrono

orientations: shadowenbian

genders: sleepminecraftic, cybergender

other: wishqueer, influenced by minecraft, minedomus, enigma, spider kin

likes: (respectful) videos about true crime and tragedies, 2000s horror movies, indie horror games, mouthwashing (game), minecraft ost and minecraft ost remixes

mannerisms: pleasant conversationalist despite being a very negative person who has trouble thinking positive

circuit pack

names: astral, circe, chase, chax

pronouns: ce/cir, bug/bugs, they/them, 🐈‍⬛/🐈‍⬛s

system: altpackgenic, imprisoner, warden

age: 135

orientations: glin

genders: mcbuilt, cybergender, chaosgender

other: wishqueer, minedomus, influenced by minecraft, automaton, arg kin

likes: minecraft pigs, masks, cosplay makeup

mannerisms: stares at people

faceclaim ideas (above): source 1

the broken end pack

names: hart, heartbeat, the end, the broken one

pronouns: the end/the end's, end/ends, end/ender

system: altpackgenic, melponic, trechtor

age: ageless + minechrono

orientations: mvin in everything

genders: cybergender, rogogender

other: wishqueer, courierqueer, influenced by minecraft, automaton, artificial construct, missingno fictionkin, dissoevil

likes: doctor nowhere, analog horror, watching films, minecraft minigame

mannerisms: intelligent and cunning, rather mean but can be talked out of being cruel

faceclaim ideas (above): source 1

and the other posts i did:

[akyrahaiato]

Little video of my ✨NOW FUNCTIONAL✨ inventory and shop system!

Context/apologies for a few things: - I ask you all to ignore: the rotating shadow, the completely missing UI, the general fact my hub looks ugly as hell right now, the fact all buttons buy swords and the fact the item I'm buying is the same sword as the protagonist (i dont have any item assets yet so I just used his sprite for testing😭) and the absolutely random filler dialogue, that was also for testing purposes

- No, there is no label showing the money amount. Yes, it's being contabilized anyway, its on my debugger, I just havent added the label yet.

- The music was an accident, I was listening to this while recording, it caught the audio and idk it just felt kinda vibey with the video and I only noticed it was there when I had already exported it so I kept it. link to the song is this one if anyone wants to know

[tanyakennedy1899]

Garage Heathen "About Dystopian Debugger." Sept 10th, 2024

tl;dr Dystopian Debugger is, for now, cancelled, because it was too difficult to make technically and gameplaywise. However, the demo for Last look along Woodward Boulevard will soon be accessible.

Dystopian Debugger after yesterday's teaser there has been some confusion in regards to a game that I have been working on before, called Dystopian Debugger.

The game was well into its development, I have arranged a Steam Page and a Public Playtest. The main systems were functional, there was a story in place as well as the main 3d assets. A lot of work and love has been poured in this project.

In Winter 2023, I've made the decision to halt the development. There were several reasons behind it.

First of all, this was a very challenging project in two major aspects - tech and gameplay. To me, making a functioning programming language and a "compiler", even with help of libraries like ANTLR was difficult task which took a lot of time and resources. I did manage to create it, but it took a lot more time than, for example, the systems in Who's Lila.

Secondly, the gameplay. The main challenge and goal of Dystopian Debugger was to turn programming into a game - not just ant programming, but debugging other people's code. Additionally, there was supposed to be several different programming languages, based on concepts like Japanese Haiku, music, probability theory, etc. What I have been too late to realise, is that these more creative languages would completely outshine the tedious c-like language.

This is where the main inner conflict took shape. I've spent an enormous amount of time making this c-like language (and had a lot of fun in the process). When you spend so much resources on a game aspect, it naturally evolves to be the central part of the experience. The most interesting, more creative languages would then become secondary. But they still needed to be implemented.

Finally, from the feedback, I've noticed that people were (naturally) much more interested in "side-content" - the story and secondary languages. Many have described the main language as "work before going to the interesting part", [of] the story.

At the time, this felt wrong. In my projects, I attempt to make the majority of [the] game engaging to play, only adding intentionally tedious bits where I feel the experience demands it. Here, half of the game felt tedious - to me as well. At the time, I was lost in this project. I wasn't sure where this should go.

There was still an enormous amount of work to be done and, before locking in, I wanted to be sure this was not going to be a boring game. It's bad enough to take a long, long time creating a game, but it'd be a catastrophe to end up with something subpar afterwards. So, I took a month-long break. Then, upon return, I've realized that I couldn't handle this project right now.

Meanwhile, all this time, the idea for another game, which is now called Last look along Woodward Boulevard has been forming. I knew it would be easier to make. Like DD, it's larger in scope than what I've been making before, but here the scope is at least visible, if that makes sense. Therefore, since February, I am focusing on this project, as it is not as technically challenging and I can be sure to give you something playable sometime this Winter.

Does this mean the end for Dystopian Debugger? No, absolutely not. I'm sure I can make these mechanics work in the future, albeit in reduced scope and different configuration.

tl;dr Dystopian Debugger is, for now, cancelled, because it was too difficult to make technically and gameplaywise. However, the demo for Last look along Woodward Boulevard will soon be accessible.

Thank you for your patience, situations like these are why I prefer not to take your money though Patreon/Boosty/etc, haha.

Take care! Garage Heathen

[riflehound]

bah pack for my bf @korosenkai i love u i hope u like it LOL

names: n/a (already has name)

pronouns: it/its, tooth/teeth, blood/bloods, bug/bugs, crawl/crawls, bite/bites, scare/scares, void/voids, creep/creeps or creep/creepy, xt/xts, click/clack, string/strings, eye/eyes

age: ageless, immortal, ancient

role: caretaker, protector, gatekeeper, internal self helper, archivist, overseer, guardian, lorekeeper, scout, buffer, advocate, debugger, architect

genders: genderless, agender, gendervoid, neutrois, gendernull, genderno

orientation: asexual demiromantic, aroace, asexual grayromantic, asexual quoiromantic

species: giant tooth-like millipede??

personality overview: jokingly mean, but overall helpful. likes to joke and prank people. cares about respect, wants to be respected and feels respect is earned. protective, prevents harm. can assert self and boundaries when others in system cant. mean when its funny, caring when it matters.

notable traits: YAPPER. likes to talk. prankster, mean in a silly way, not genuinely harmful but the type of person to jump out from behind a door and scare u... looks scary, is helpful.

general aesthetic: cryptid millipede. unnerving aesthetics

add ons: appearance description and music taste!

appearance: giant black millipede with red highlights and a smile with teeth on face. each foot ends in teeth and a clacking noise is made when walking. glowing red eyes along body, that move to other spots upon blinking. white strings come out of the body at random. large enough to wrap around entire buildings.

music taste: EDM, techno, hard bass jumpstyle

[hectorgon5]

Tim Drake created a fake account to infiltrate a hacker ring.

Username: @NullSyntax404. Bio: “Just noise in the system.”

He starts posting vague phrases to bait the hackers. Stuff like:

“Truth is just corrupt code.” “Identity is the first virus.”

But instead of baiting criminals… He gains followers. Thousands.

They think he’s a prophet. People start quoting him like he’s a digital Socrates.

Someone makes a lo-fi beat under his quote

“Reality.exe has crashed.”

It hits a million views.

By week two, they’ve written a manifesto. By week three, there’s a theme song and t-shirts.

Dick finds out and goes, “Tim. Did you start a cult?”

Tim, sipping coffee at 3AM: “I was trying to catch a guy named ‘CryptoFreak69.’”

Now the cult calls him The Debugger. They have rituals. There’s a zine.

He tries to delete the account. It gets reposted ten more times.

Even Damian joins the server just to troll the believers.

Tim sighs. “I’m literally in the Batcave. I can’t lead your revolution.”

They respond: “You’ve already begun it.”

[andmaybegayer]

What flavor of engineering do you typically engineer in?

These days I'm professionally a software debugger, so very little engineering. My training is electrical engineering with a focus on embedded systems and computer engineering. Nowadays when I do use those skills that's mostly to program microcontrollers and design control algorithms for things, plus the odd bit of digital signal processing.

[infwctednyacifier]

can i have a feminine alter who deals with bad friends/manipulation? lowest age preference is 17! thank you so much!

🗝⋆｡ ☣ ₊˚🛍️ ˚. SINGLE, ORIGINAL = BAD FRIEND HANDLER – A SECURUS

cooked :3

Name – Seraphina ,, Nanaka ,, Selene

Age – immortal / 24

Gender – cisgirl ,, faegender ,, fairygender ,, magicia ,, ecoxenic ,, fantasygender ,, pinklolitapearlic ,, softpinkfrillic ,, lolitacoric ,, strawberrybunnyplushic ,, cakefrilled ,, pinkgender ,, bimbogender ,, weirdcoric ,, angelweirdic ,, weirdcorestalgic

Pronouns – she / her ,, fairy / fairy's ,, faerie / faerie's ,, wing / wing's ,, sparkle / sparkle's ,, glimmer / glimmer's ,, swirl / swirl's ,, twirl / twirl's ,, magic / magic's ,, spell / spell's ,, wand / wand's ,, fantasy / fantasy's ,, pink / pink's ,, pearl / pearl's ,, soft / soft's ,, fluffy / fluffy's ,, frill / frill's ,, strawberry / strawberry's ,, berry / berry's ,, bunny / bunny's ,, bun / bun's ,, twitch / twitch's ,, plush / plush's ,, plushie / plushie's ,, cake / cake's ,, frosting / frosting's ,, icing / icing's ,, topping / topping's ,, bimbo / bimbo's ,, girly / girly's ,, weird / weird's ,, eye / eye's ,, void / void's ,, null / null's ,, angel / angel's ,, hymn / hymn's ,, holy / holy's ,, divine / divine's ,, nostalgia / nostalgia's ,, memory / memory's ,, remember / remember's

Orientation – heterosexual

Role – apathy manager ,, apathy holder ,, conductor ,, crafter ,, controller ,, counterweight ,, councilman ,, consul ,, confronter ,, communicator ,, coltenoir ,, diplomat ,, diffuser ,, debugger

Emojis – 🗝 ,, 🍃 ,, 🛍️ ,, 💄 ,, ☣ ,, 👁️‍🗨️

Likes – her boyfriend ,, helping people ,, Pixiecore & Barbie / Bimbocore & Weirdcore ,, shopping ,, Sanrio

Extra – she has fairy ' s own weirdcore / pixie Barbie dream house in faerie ' s part of headspace . Wing leans towards being antisocial and prefers to be by sparkleself / with glimmer ' s boyfriend . Swirl loves to decorate the system ' s accounts and twirl ' s headmates accounts / blogs / etc with symbols , icons , etc . Magic will overcomplicate the system ' s Simply Plural information just to be able to add more stuff to it .

Aesthetics – Pixiecore ,, Barbiecore ,, Weirdcore

Faceclaims –

[mars-ipan]

Im just gonna run to your inbox and yap about komahina whenever I feel upset ok? Ok.

MY OWN FREAK ASS KOMAHINA SEX AU:

Corporate au. Now hear me out:

This is a Digital Circus-esque fucking corporation and they have all kinds of strange unethical cutting edge technology

Komaeda:

- head of testing department.

- Basically, he hires all the testers and debuggers to work on the new tech shit they invent.

- He used to be one, but it malfunctioned on him and fucked up his nervous system pretty bad, so now he works on hiring

- ALSO builds his own weird ass machines in his spare time. His luck still exists, but it's non-Ultimate and far more subtle, more like Makoto's,? Kinda??

Hinata:

- Starving intern.

- Barely scraping through the bills.

- He's not technically a betatester-- he's more like a glorified receptionist for Komaeda

- But after hours, Komaeda pays him extra to stay late and test the... "newest products"

If the priest au is for all of your dubiously ethical kinks, this one is for mine... hell yeah... power dynamics 🤤 uniforms.. boot worship.. overstim... VR and hypnotization... orders and commands... ownership... electric shocks .. bondage

Anyway. Coughs. . Might draw them later. Suitmaeda hell yeah

ohhhohoho WOOF. i would like to see suitmaeda pleaseeeee