Index on Ozbem

Emacs Vanilla vs Flavors (Spacemacs and Doom Emacs)

info@ozbem.com (ebeem) — Sun, 28 Jun 2026 00:00:00 +0000

Where to Begin?

Emacs is not just a text editor, it is a Lisp machine that happens to edit text. When stepping into the Emacs ecosystem, new users are immediately faced with a choice: build from scratch (Vanilla Emacs) or use a pre-configured starter kit like Doom Emacs or Spacemacs. Each approach has distinct pros and cons, and understanding them can save you months of configuration frustration.

The Batteries-Included Flavors

Starter kits are fantastic for package discovery. They show you exactly what Emacs is capable of right out of the box, coming pre-configured with themes, completion frameworks, and integrations for almost every programming language.

However, this convenience comes at a cost. "Batteries-included" setups reduce your visibility into the underlying mechanics. When something breaks, or when you want to change a core behavior, deep customization becomes harder. You often find yourself fighting the framework's design rather than just configuring Emacs.

Spacemacs

Spacemacs revolutionized the community by popularizing mnemonic, space-bar-driven keybindings and excellent Vim emulation. However, it relies heavily on configuration "layers."

These layers add a massive amount of abstraction on top of the base editor. While this makes it incredibly easy to toggle features on and off, migrating your configuration from Spacemacs to Vanilla Emacs becomes an extremely difficult task. Because of the heavy abstraction, you end up learning the "Spacemacs way" rather than the "Emacs way."

Doom Emacs

Doom Emacs takes a different philosophical approach. It still provides a beautiful, feature-rich out-of-the-box experience, but it significantly reduces the layers between the user's configuration and the core Emacs configuration.

It utilizes clever macros to keep startup times incredibly fast and maintains a structure much closer to standard Emacs Lisp. If you want to peek under the hood and see how a feature is implemented, Doom makes it highly visible and accessible.

Vanilla Emacs

Vanilla Emacs is exactly what you get when you download the software from the GNU website. It is a completely blank slate.

The primary advantage here is total ownership. You understand every single line in your configuration file because you put it there. You learn standard Emacs Lisp, making it straightforward to read official documentation and leverage community packages. The major downside is the steep learning curve. You are fully responsible for setting up your own package manager, user interface, completion frameworks, and language servers.

The Keybinding

Your choice of flavor is often heavily tied to your preferred typing style and hardware setup.

Evil Mode (Vim Bindings)

If you are a user coming from vi or Vim, Evil mode (which powers both Spacemacs and Doom by default) is practically magic. It flawlessly brings the language of Vim text objects into Emacs. However, modal editing can sometimes feel like a second-class citizen in niche Emacs packages, requiring extra translation packages (like evil-collection) to make third-party tools play nicely.

Vanilla Bindings (Emacs Bindings)

Standard Emacs keybindings (using Ctrl and Meta). They are deeply integrated into the entire Emacs ecosystem. Everything just works, seamlessly and consistently without any translation layers.

The common complaint is that they require uncomfortable hand stretching. However, if you use a high-quality split ergonomic keyboard, you can easily map modifiers to your thumb clusters. With good hardware, the chances are high that you will not need anything but the standard vanilla keybindings.

Meow (Middle Ground)

If you want the ergonomic benefits of modal editing without straying too far from the standard ecosystem, the meow package is a fantastic alternative. Packages like meow try to sit right in the middle. It allows modal editing but does not fight the default Emacs environment the way Evil sometimes does, keeping your experience much closer to vanilla Emacs.

My Recommendation

For newcomers to Emacs, I highly recommend starting with Doom Emacs. It offers a polished, out-of-the-box experience that lets you get real work done immediately while showing you what Emacs is truly capable of. Later on, as you pick up Emacs Lisp and learn more about the popular packages, you will want to configure things exactly your way, you'll be well-prepared to drop the starter kit and craft your own Vanilla Emacs configuration from scratch.

If you're already a vim user or just want to explore modal editing, evil-mode provides a fantastic experience. If you want the benefits of modal editing but aren't tied to traditional vim bindings, meow is an excellent alternative. I do believe everyone should learn vim keybindings eventually as they are invaluable when you find yourself on a machine without Emacs. However, as a modal editing package, I prefer meow over evil-mode because it's lightweight and integrates much more naturally with the native Emacs ecosystem. If you type on a solid ergonomic split keyboard, I strongly suggest sticking to standard vanilla Emacs keybindings.

My personal progression went from Spacemacs to Doom Emacs, and finally to vanilla. If I go back in time I would skip Spacemacs, it didn't teach me much about how things work under the hood. My editing journey followed a similar path: evil-mode to meow to vanilla. I am incredibly glad I spent time with evil-mode, as it left me highly proficient and comfortable with vim keybindings.

Useful Resources

Bootloader

info@ozbem.com (ebeem) — Tue, 23 Jun 2026 00:00:00 +0000

Introduction

Once the firmware finishes initializing the hardware, it hands the baton to the bootloader. The bootloader is a small program whose sole purpose is to load the Linux kernel and the initial RAM disk (initramfs) into memory and execute them.

GRUB (GRand Unified Bootloader) is the undisputed king of Linux bootloaders, though systemd-boot is a highly popular, lightweight alternative for modern UEFI systems.

Customizing the Bootloader

The bootloader is highly customizable. By editing its configuration files, you can alter fundamental behaviors of your system's startup.

Default Operating System: If you dual-boot Linux and Windows, you can set which OS boots by default. You can even configure GRUB to remember the last OS you booted and default to that one next time.

Timeout: You can change how long the boot menu waits for your input before selecting the default option. You can set it to 10 seconds, 1 second, or even hide the menu entirely for a faster boot.

Kernel Parameters: You can pass specific instructions to the Linux kernel before it starts. This is incredibly useful for troubleshooting. For example, you can add parameters to disable a problematic graphics driver, force a specific screen resolution, or boot into a text-only recovery mode.

Themes and Visuals

Your bootloader does not have to be a boring black-and-white text menu. GRUB heavily supports visual customization.

At the most basic level, you can easily add a custom background image to the GRUB menu. Going further, the Linux community has created thousands of full GRUB themes. These themes can completely overhaul the interface, adding custom typography, colorful progress bars, and high-resolution icons for each operating system you have installed.

To apply a theme, you typically download a theme folder, place it in the designated themes directory, and update your GRUB configuration file.

Edit your main GRUB configuration file (usually located at /etc/default/grub) to point to your new theme:

Example of setting a theme in /etc/default/grub

GRUB_THEME="/boot/grub/themes/my-custom-theme/theme.txt"

After saving the configuration, you must regenerate the actual boot menu for the visual changes to take effect:

sudo grub-mkconfig -o /boot/grub/grub.cfg

Whether you are prioritizing a minimalist, lightning-fast boot or a beautifully themed menu that welcomes you to your computer, the Linux bootloader gives you the tools to make the startup process your own.

Firmware (BIOS and UEFI)

info@ozbem.com (ebeem) — Sat, 20 Jun 2026 00:00:00 +0000

Introduction

The firmware is the absolute bedrock of your system. Before Linux or any operating system can even think about running, the motherboard's firmware must wake up the hardware. It performs the Power-On Self Test (POST), initializes the CPU and RAM, and locates the drive containing your operating system.

Historically, computers used the Basic Input/Output System (BIOS). Today, almost all modern computers use the Unified Extensible Firmware Interface (UEFI), which is essentially a mini-operating system itself. It supports larger hard drives, faster boot times, and graphical interfaces with mouse support.

Upgrading Firmware

Yes, firmware can and often should be upgraded. Motherboard and laptop manufacturers regularly release updates for your BIOS or UEFI.

These upgrades are released to:

Patch critical security vulnerabilities.
Fix bugs related to power management or sleep states.
Add support for newly released hardware, such as a newer generation CPU that fits into the same motherboard socket.

This process is commonly known as flashing the BIOS

Warning: Flashing your firmware carries a small amount of risk. If the power goes out during the update, it can "brick" the motherboard, rendering the computer unusable without specialized recovery tools. Always ensure your system has a stable power supply or a fully charged battery before updating.

Customizing Firmware

Standard UEFI interfaces offer built-in customization, such as changing the boot order, adjusting fan curves, or enabling hardware virtualization. However, for true customization, the Linux community often looks toward open-source firmware replacements.

Projects like Coreboot and Libreboot aim to replace the proprietary, closed-source firmware shipped by manufacturers. These open-source alternatives offer massive benefits:

They strip out hidden, proprietary code.
They allow for incredibly fast boot times because they only initialize exactly what is needed.
They give users total, transparent control over their hardware from the very first second of power-on.

Note that installing open-source firmware requires specific hardware compatibility and technical expertise, as it often involves physically clipping a flashing tool onto the motherboard's firmware chip.

Introduction to Guix

info@ozbem.com (ebeem) — Fri, 19 Jun 2026 00:00:00 +0000

TODO Installation

Channels

Channels in Guix are a way to customize and extend the Guix package collection. They allow users to pull packages and updates from multiple repositories. They are declared as a list of channel records in the file channels.scm. These channels are git repositories that store definitions that instruct Guix how to build and install packages. Since these are git repositories, then similar to any git cloned project, it needs to be pulled to kept up to date. Guix can help you update/pull all your configured channels with the command guix pull.

Note: pulling Guix might take a long time depending on how outdated your system is. Expect up to an hour on your first installation.

Adding a channel

Create or edit your ~/.config/guix/channels.scm file to include your desired channels. Here's an example:

(cons* (channel
 (name 'my-channel)
 (url "https://example.com/my-channel.git"))
 %default-channels)

Note: we create a channel record with the name my-channel and the git url, then we use cons to append it to the %default-channels which includes the default Guix channel. It's possible to remove the default Guix channel by returning a new list without appending the default channels.

Save the file and pull Guix channels:

guix pull

Removing a channel

edit your ~/.config/guix/channels.scm file to exclude the target channel.
Save the file and pull Guix channels:

guix pull

Useful Resources

NonGuix Channel

Nonguix is a Guix channel that packages some software which cannot be included in the official distribution for ethical or policy-related reasons. Guix official repository offers only Gnu Compatible Free Software.

It will be great if we can use only free software, but sometimes it's necessary to add some nonfree software to get our machine functioning properly. For example, Guix's default kernel is called Linux Libre, it's a custom Linux kernel that doesn't ship with some nonfree drivers embedded into the Linux kernel. These drivers are necessary to get some wifi and bluetooth cards to work.

Rule of thumb: If everything works properly in your case, no missing drivers, all hardware is working as expected, then you probably don't want to add or use the nonguix channel.

Adding the NonGuix channel

Create or edit your ~/.config/guix/channels.scm file to include the NonGuix channel

(cons* (channel
 (name 'nonguix)
 (url "https://gitlab.com/nonguix/nonguix")
 ;; Enable signature verification:
 (introduction
 (make-channel-introduction
 "897c1a470da759236cc11798f4e0a5f7d4d59fbc"
 (openpgp-fingerprint
 "2A39 3FFF 68F4 EF7A 3D29 12AF 6F51 20A0 22FB B2D5"))))
 %default-channels)

Pull Guix channels

guix pull

Note: in case you notice the message below after pulling NonGuix

hint: Consider setting the necessary environment variables by running:

 GUIX_PROFILE="/home/ebeem/.config/guix/current"
 . "$GUIX_PROFILE/etc/profile"

Alternately, see `guix package --search-paths -p "/home/ebeem/.config/guix/current"'.


hint: After setting `PATH', run `hash guix' to make sure your shell refers to `/home/ebeem/.config/guix/current/bin/guix'.

Then execute the below to ensure the updated profile path is active

 GUIX_PROFILE="/home/ebeem/.config/guix/current"
 . "$GUIX_PROFILE/etc/profile"
 hash guix'

Note: with this step, you only make the nonguix packages available to your system. You are still not using the Full Linux kernel or any other nonfree software. Continue to the other sections to learn more.

Useful Resources

System Configuration

System configuration in Guix is declarative, meaning you define the desired state of your system in a configuration file, and Guix ensures your system matches that state. Upon installing Guix, you provided system configuration parameters that Guix installer used to create a system configuration file for you in the path /etc/config.scm.

You can take a peak at this file and see all the parameters that have been configured like: locale, timezone, keyboard-layout, host-name, users, packages, services, bootloader, swap-devices, file-systems.

These configurations are system level, this means that they impact all the users on your system. For example, we can add emacs to the declared packages list, this will install emacs globally on your system and make it available to all users. It's important to understand here that unlike other Linux distributions and operating systems. Guix suggests adding packages to user configurations (called home configuration) rather than system configuration. However, some packages must be installed globally, like the Linux kernel, vi to have a text editor and your display manager like GDM. Knowing when to add a package to system or user level might take sometime, but the rule of thumb here, if you can add it to user level, then do so.

Creating System Configuration

It's better to start with the generated Guix configuration located in the path /etc/config.scm. My preference is to have this system configuration added to my dotfiles so I can easily manage and track changes using git.

Copy the generated Guix configuration file to your Guix configuration directory

cp /etc/config.scm ~/.config/guix/system.scm

Applying System Configuration

Upon modifying the system configuration, you will have to tell Guix to apply your changes by providing it with the path of your system configuration.

sudo guix system reconfigure ~/.config/guix/system.scm

Note: Remember that the Guix system configuration contains data that only superusers can access or modify. For example, only superusers can partition disks, manage users, manage system level packages, manage system level services. That's the reason why a sudo is required when you would like to reconfigure your system.

Using Nonfree Linux Kernel

To be able to use the nonfree Linux kernel, you must add the NonGuix channel and pull it so the nonfree software become available to your system.

Edit your ~/.config/guix/system.scm as below

Add needed imports in your system configuration

Just below the line where the gnu module is imported (use-modules (gnu)) Add the below lines

;; Import nonfree linux module.
(use-modules (nongnu packages linux)
 (nongnu system linux-initrd))

Modify the parameters of your operating system record

Now you will have to add the new nonfree Linux kernel as the kernel of your system. You can do so be adding the below lines just below the line where the operating system is defined (operting-system and before the line where locale is defined.

 (kernel linux)
 (initrd microcode-initrd)
 (firmware (list linux-firmware))

Apply the system configuration

Now that you modified the used kernel, you must apply the configuration for it to take affect.

sudo guix system reconfigure ~/.config/guix/system.scm

Note: This might take a long time if this is the first time you reconfigure the system. That's because when you pull the channels, you updated the list of package definitions available with their versions. This means that the latest version of Emacs available becomes Emacs 30, while you're still running Emacs 28. Pulling will NOT upgrade packages, it will just make the new versions available. On the other hand, system reconfigure will update packages if the pulled channels indicate that an update is available.

Note: Avoid running any guix configuration commands under the root user. Using sudo will ensure that your user configured channels are used, if you would like to reconfigure your system as root then you will have to also maintain another list of channels and keep them up to date which is not convenient. Rule of thumb: you probably never want to run any of the Guix commands as a root user, you should use sudo when superuser privileges are required.

Useful Resources

Home Configuration

Now that you have a good idea how to modify and apply system level configuration, let's dive into modify your user level configuration (referred to as home configuration). Guix Home configuration allows you to set packages and services per user. Packages are software to be installed, while services can be actual sheperd services, configuration manager.

Creating Home Configuration

Create or edit your ~/.config/guix/home.scm file to include your desired configuration. Here's an example:

(use-modules (gnu home)
 (gnu home services)
 (gnu home services shells)
 (gnu services)
 (gnu packages admin)
 (guix gexp))

(home-environment
 (packages (list htop))
 (services
 (list
 (service home-bash-service-type
 (home-bash-configuration
 (guix-defaults? #t)
 (bash-profile (list (plain-file "bash-profile" "\
export HISTFILE=$XDG_CACHE_HOME/.bash_history"))))))))

Note: we define packages and services for our home configuration. our list of packages in this example is htop only. The services is only home-bash-configuration which create the file bash-profile.

Note: notice that we import some modules that expose the package htop (gnu packages admin) and the home-bash-service-type (gnu home services shells). Read more about how to find out the modules in Installing Packages. Guix also has a utility that will search for package from a string only (not recommended but works).

(packages (map specification->package '(
 "btop"
 "alacritty"
 "gimp"))

Save the file and apply your home configuration:

guix home reconfigure ~/.config/guix/home.scm

Applying the home configuration above will install htop to your home configuration (user level) and create modify the .bash-profile to define the environment variable HISTFILE to the path defined.

Useful Resources

Installing Packages

At this point, it should be clear that you can declare your packages either in system.scm to become system level packages that can be accessed by all users on the system, or in home.scm to become user level packages that can be only access by the user who applies the home.scm to their home. We also agreed that it's recommended to install packages on user level if possible to avoid any version conflicts, give more flexibility to users regarding when to upgrade, and have a minimal system configuration that doesn't require frequent updates as opposed to user configuration that might be updated very regularly.

Finding Packages

Similar to any other Linux distribution, Guix comes with its own utility to search and install packages. performing a simple Guix search [PACKAGE_NAME] will list available packages that contain the query in their package name or description. Below is an example to try to search for firefox.

guix search firefox

output:

name: firefox
version: 128.0
outputs:
+ out: everything
systems: x86_64-linux
dependencies: alsa-lib@1.2.4 autoconf@2.13 bzip2@1.0.8 cairo@1.18.0 clang@18.1.8 cups@2.4.2 dbus-glib@0.112 eudev@3.2.14 ffmpeg@6.1.1 freetype@2.13.0 gdk-pixbuf@2.42.10 glib@2.78.0
+ gtk+@2.24.33 gtk+@3.24.41 hunspell@1.7.0 icu4c@73.1 jemalloc@5.3.0 libcanberra@0.30 libevent@2.1.12 libffi@3.4.4 libgnome@2.32.1 libjpeg-turbo@2.1.4 libnotify@0.8.3 libva@2.19.0
+ libvpx@1.12.0 libxcomposite@0.4.5 libxft@2.3.4 libxinerama@1.1.4 libxscrnsaver@1.2.4 libxt@1.2.1 llvm@13.0.1 m4@1.4.19 mesa@24.0.4 mit-krb5@1.20 nasm@2.15.05 node@18.19.0 nspr@4.32
+ pango@1.50.14 perl@5.36.0 pipewire@1.0.3 pixman@0.42.2 pkg-config@0.29.2 pulseaudio@16.1 python@3.10.7 rust-cbindgen@0.26.0 rust@1.77.0 speech-dispatcher@0.11.5 sqlite@3.39.3
+ startup-notification@0.12 unzip@6.0 wasm32-wasi-clang-toolchain@15.0.7 which@2.21 yasm@1.3.0 zip@3.0 zlib@1.2.13
location: nongnu/packages/mozilla.scm:544:2
homepage: https://mozilla.org/firefox/
license: MPL 2.0
synopsis: Trademarkless version of Firefox
description: Full-featured browser client built from Firefox source tree, without the official icon and the name "firefox".
relevance: 37

name: icecat
version: 115.13.0-guix1
outputs:
+ out: everything
systems: x86_64-linux
dependencies: alsa-lib@1.2.4 bzip2@1.0.8 cairo@1.18.0 clang@15.0.7 cups@2.4.2 dbus-glib@0.112 eudev@3.2.14 ffmpeg@5.1.4 font-dejavu@2.37 freetype@2.13.0 gdk-pixbuf@2.42.10 glib@2.78.0
+ gtk+@3.24.41 hunspell@1.7.0 icu4c@73.1 libcanberra@0.30 libevent@2.1.12 libffi@3.4.4 libgnome@2.32.1 libjpeg-turbo@2.1.4 libnotify@0.8.3 libpng-apng@1.6.39 libvpx@1.12.0
+ libxcomposite@0.4.5 libxft@2.3.4 libxinerama@1.1.4 libxscrnsaver@1.2.4 libxt@1.2.1 llvm@15.0.7 m4@1.4.19 mesa@24.0.4 mit-krb5@1.20 nasm@2.15.05 node@18.19.0 nspr@4.35 pango@1.50.14
+ pciutils@3.8.0 perl@5.36.0 pixman@0.42.2 pkg-config@0.29.2 pulseaudio@16.1 python-wrapper@3.10.7 rust-cbindgen@0.26.0 rust@1.75.0 shared-mime-info@2.3 sqlite@3.39.3 unzip@6.0 which@2.21
+ yasm@1.3.0 zip@3.0 zlib@1.2.13
location: gnu/packages/gnuzilla.scm:2001:4
homepage: https://www.gnu.org/software/gnuzilla/
license: MPL 2.0
synopsis: Entirely free browser derived from Mozilla Firefox
description: IceCat is the GNU version of the Firefox browser. It is entirely free software, which does not recommend non-free plugins and addons. It also features built-in
+ privacy-protecting features. This package also includes the `geckodriver' command, which can be useful for automated web testing.
relevance: 5

Let's try to analyze the output, you will most likely see so many packages. The exciting part here is that if you don't configure the Nonguix channel, you will not see firefox listed as it has some trademark on its arts. However, we will see ictcat which is described as the GNU version of firefox. We can also see the location of the package which we can use to import the package module into our configuration.

We can also minimize the output to get only the information we are interested in Note: there is an easier way to perform this task using recsel but it's not installed by default.

guix search firefox | grep -E "^(name|version|location)" | sed '/location:/a \\n'

output:

name: firefox
version: 128.0
location: nongnu/packages/mozilla.scm:544:2

name: icecat
version: 115.13.0-guix1
location: gnu/packages/gnuzilla.scm:2001:4

Now we can quickly identify the name of the package, available version, and the location of the package definition and even the line in which it's defined in the module.

Installing a package

To install firefox, we will declare it in our home configuration since a browser is typically a user level program (doesn't have to be available to all users, they can install it if they desire).

Identify your target package name and location

In our case, target is firefox, location is nongnu/packages/mozilla.scm

Declare the module in your home configuration (system configuration if you want system level) by adding a new import to use-modules. This import should match the location with slashes replaced by spaces and without the extension .scm

nongnu/packages/mozilla.scm > =nongnu packages mozilla

(use-modules (gnu home)
 (gnu home services)
 (gnu home services shells)
 (gnu services)
 (gnu packages admin)
 (guix gexp)

			 ;; ensure that the paranthesis are closed and your definition is inside
 (nongnu packages mozilla))

Add the package name to the list of packages

(packages (list htop firefox))

Save the file and apply your home configuration:

guix home reconfigure ~/.config/guix/home.scm

Note: Bare in mind that installing packages from the Guix utility is as simple as guix install htop, but this is not very declarative, and even though there are ways to extract installed packages, in my opinion, it's best to declare them in your configuration and then apply them. However, one might want to try packages first with guix install [PACKAGE_NAME] and then see if they would like to keep it. Without this package name specified in your system or home configuration file, next system or home reconfigure will uninstall these packages.

Note: sometimes you will need to logout from your account/shell and login again for environment variables to be updated, before you assume that the package wasn't installed, try to reboot or logout.

Useful Resources

Root Genesis Now Available on Itch.io

info@ozbem.com (ebeem) — Sun, 29 Mar 2026 00:00:00 +0000

If you’re a fan of gritty cyberpunk aesthetics, hacking simulators, or incremental idle games that actually keep you engaged, I’ve got a brand-new release you need to check out today.

What’s it all about?
#

You play as an underground hacker trying to systematically dismantle a shadowy elite’s control network. While it’s an idle game at its core, it brings a really satisfying, interactive terminal vibe to the genre. The game blends sci-fi, mild horror, and deep conspiracy elements brilliantly. As you infect the control grid and build your digital empire, you actually uncover the dark secrets hidden by elite bloodlines.

If you want to live out your ultimate keyboard-warrior, cyberpunk fantasy and expose some virtual elites, head over to the game page and give it a try.

You can check more details here

MORE SCREENSHOTS
#

Play it right now!
#

Check it out on your web browser, no need for download

Root.Genesis by Ozbem

What is Root Genesis?

info@ozbem.com (ebeem) — Sun, 29 Mar 2026 00:00:00 +0000

The elites think their network is untouchable. Prove them wrong.

ROOT.GENESIS is a cyberpunk idle game where you hack a shadowy elite’s control network and expose the conspiracies they hide.

BUILD YOUR EMPIRE
#

Type commands and deploy hacking tools to pwn nodes. Every key you press chips away at the elite’s firewall.

COMPLETE CONTRACTS
#

Deploy tools to complete contracts on the dark web and earn nodes in exchange. Each tool offers a unique contract minigame or upgrade to your workflow.

UNCOVER THE CONSPIRACY
#

Discover the secrets hidden by the elite bloodline families. Infect their control grid and expose what lies beneath the surface.

MORE SCREENSHOTS
#

Disclaimer: Videos displayed in the game are AI-generated. All information presented is a work of fiction and may or may not reflect reality.

Wishlist the game on STEAM to stay updated!

You can also check out our itch.io page which has a web demo available

Root.Genesis by Ozbem

Spooky Night Is Out Now!

info@ozbem.com (ebeem) — Sun, 02 Nov 2025 00:00:00 +0000

It’s finally here, the night you’ve all been waiting for! We’re thrilled to announce that Spooky Night is officially released and ready for you to play.

After months of development, testing, feedback, and community support, the gates to our haunted village are open. Whether you’ve been with us since the early alpha or are just discovering the game now, we can’t wait for you to experience the chaos, mystery, and laughter that make Spooky Night what it is.

What Is Spooky Night?
#

Spooky Night is an online social deduction game of teamwork, bluffing, and betrayal.
Villagers must uncover the Hunters (formerly known as werewolves) hiding among them, while the Hunters try to eliminate the innocent one by one.

Talk, deceive, vote, and survive. Every night brings new twists, and no two games are ever the same.

Play Now on Steam and Itch.io
#

You can jump into the full release today on both platforms:

Spooky Night by Ozbem

Both versions offer cross-platform multiplayer, so you can play with your friends no matter where they’re haunting from.

What’s Included in the Release
#

20+ Unique Roles with distinct abilities and strategies
Multiplayer lobbies (Casual & Private) for up to 16 players
Match rewards system with free skins and gold
Character customization with hundreds of unlockable cosmetics
Support for 11 languages, making the experience accessible worldwide
No pay-to-win mechanics, everyone plays on equal ground

Fair and Transparent Model
#

Spooky Night follows a completely free-to-play model.
Everyone gets full access to all features, with optional VIP tiers for players who want to support development and earn extra cosmetics.
No subscriptions, no hidden fees, and no microtransactions.

Join the Community
#

Our players are the heart of this project, and your feedback has shaped every part of the game.
Join the conversation, share your experiences, and help us make Spooky Night even better:

Thank You
#

From the entire development team: thank you. Your enthusiasm, ideas, and patience have brought Spooky Night to life. This release is just the beginning, we have many updates, features, and surprises planned for the future.

So gather your friends, light your lanterns, and step into the shadows.

The night has begun… and no one is safe.

ebeem

The Road Ahead for Spooky Night

info@ozbem.com (ebeem) — Wed, 26 Mar 2025 00:00:00 +0000

Greetings, mortals!

Spooky Night Vision
#

Spooky Night has always been about bringing players together for a fun, strategic, and engaging experience. From the very beginning, we set out to create a game that belongs to the community no pay-to-win mechanics, no predatory monetization, just a game built with and for its players.

Our vision is simple: to continuously evolve Spooky Night based on player feedback, community contributions, and fair design principles. This roadmap outlines our plans and how you can be a part of shaping the game’s future.

The Roadmap
#

Phase 1 (Q1 - Q2 2025)
#

Early Access & Core Gameplay (Q1 - Q2 2025)

Steam Next Fest & Public Playtesting – We invite players to test the game, provide feedback, and help us fine-tune the balance and mechanics.
Community Server Expansion – Our Discord server will be the central hub for discussions, suggestions, and community engagement.
Role & Balance Tweaks – Based on player feedback, we’ll refine roles, abilities, and game mechanics to ensure a fair and exciting experience.
Content Creators & Events – We plan to collaborate with content creators and host events to spread the word about Spooky Night.
Game Localization – The game will be localized into 11 languages, with the goal of making Spooky Night accessible to a global audience.
Match Rewards System – Post-match rewards system will allow players to earn cosmetic items by simply playing the game. This will be part of our free-to-play progression model.
Character Customization & Skins – Players will be able to personalize their characters with various skins and outfits. More options will be added over time.
20+ Unique Roles – Early access will launch with over 20 roles, each offering different strategic opportunities. These roles will continue to evolve as we test and refine the meta.
Multiplayer Lobbies (Casual & Private) – Both casual matchmaking and private lobbies will be supported. We’re working on improving stability, UI, and features to make hosting and joining games as smooth as possible.

Phase 2 (Q3 - Q4 2025)
#

Expanding the Game (Q3 - Q4 2025)

New Roles & Abilities – Inspired by community suggestions, we’ll introduce fresh roles to add depth and variety to the gameplay.
Custom Lobbies & Mods – Players will gain the ability to create and customize their own game modes and rules.
More Skins & Cosmetics (All Free, No Paywall!) – Unlockable purely through gameplay, with no real-money transactions.
Localization & Accessibility – Expanding Spooky Night to a global audience with additional language support and accessibility features.

Phase 3 (Beyond 2025)
#

The Future of Spooky Night (Beyond 2025)

New Game Modes – Exploring fresh ways to play beyond the core experience.
Community-Driven Events & Tournaments – Competitive and casual events to keep the game engaging.
Open Contribution Model – We aim to allow community members to contribute directly to the game’s development, including code, art, and features.
And More… – The game’s future will be shaped by player feedback and innovation.

We are committed to keeping Spooky Night a game that is fair, fun, and community-driven. There will be no microtransactions, no pay-to-win mechanics only skill, strategy, and social deduction.

This game is shaped by you, the players. Your ideas, your feedback, and your creativity are what will define Spooky Night’s future.

Join the Community
#

Let’s build something great together!

The Spooky Night Development Team

What is Spooky Night?

info@ozbem.com (ebeem) — Mon, 24 Feb 2025 00:00:00 +0000

Greetings, mortals!

Welcome to the eerie world of Spooky Night, an online social deduction game where teamwork and betrayal intertwine. Your mission: unmask the werewolves lurking among you before they decimate the village. Here’s a quick guide to help you navigate the shadows and survive the night.

Trailer & Gameplay
#

▶ Watch the Official Trailer:

You can checkout out our presskit

How to Play
#

Day Phase: Engage in discussions with fellow players to identify the werewolves. Vote to eliminate the most suspicious individual.

End of Day: The player receiving the majority of votes is eliminated, revealing their true role.

Night Phase: Under the cover of darkness, werewolves choose their victims, while villagers and other roles secretly employ their unique abilities to protect, investigate, or take decisive actions.

Win Conditions:
- Villagers: Prevail by eliminating all werewolves.
- Werewolves: Conquer when they equal or outnumber the remaining villagers.

MORE SCREENSHOTS
#

Why You’ll Love Spooky Night
#

Each session offers a fresh and unpredictable experience. With a diverse array of roles and limitless strategic possibilities, no two games are alike. Forge alliances, sow seeds of doubt, and immerse yourself in the thrill of deception.

Best of all, Spooky Night is entirely free to play! Earn rewards after every match and unlock a plethora of character customizations. Opting to purchase the game accelerates your access to skins and expands your inventory.

Note: As the game is in its early stages, the player base is limited. For the best experience, gather a group of at least 8 friends to join a lobby (minimum 4 players required). Casual matchmaking necessitates 10 players.

Stay vigilant, trust sparingly, and may you survive the Spooky Night.

ebeem

Wishlist the game on STEAM to stay updated!

You can also check out our itch.io page

Spooky Night by Ozbem

Spooky Night Joins Steam Next Fest

info@ozbem.com (ebeem) — Fri, 21 Feb 2025 00:00:00 +0000

Greetings, mortals!

Prepare yourselves for an otherworldly adventure as Spooky Night descends upon the Steam Next Fest from February 24 to March 3, 2025. This week-long celebration offers you a chance to delve into the eerie realms we’ve conjured, all from the (relative) safety of your own abode.

Mark your calendars, summon your courage, and prepare to face the unknown. The witching hour approaches, and Spooky Night awaits your presence.

Stay spooky, my friends.

ebeem

Wishlist the game on STEAM to stay updated!

You can also check out our itch.io page

Spooky Night by Ozbem

Spooky Night Press Kit

info@ozbem.com (ebeem) — Sun, 26 Jan 2025 00:00:00 +0000

🎃 Spooky Night - Press Kit 🎃
#

Welcome to the official press kit for Spooky Night, the ultimate game of deception and doom! Here, you’ll find all the assets, descriptions, and details you need for articles, videos, and promotions.

Game Overview
#

Title: Spooky Night
Developer: Ozbem
Publisher: Ozbem
Release Date: Demo released, full game Q2, 2025
Platforms: PC (Windows, Linux, OSX), IOS, Android
Price: Free to play
Genre: Social Deduction
Players: 4-16 players per match
Website: ozbem.com
Steam Page: https://store.steampowered.com/app/3443650

Short Description
#

Spooky Night is an online social deduction game of teamwork and betrayal! Uncover the werewolves among you before they wipe out the village. During the day, chat, deceive, and vote to eliminate a suspect. At night, use your role’s abilities to gather insights or strike. Can you survive?

Long Description
#

Spooky Night is an online multiplayer social deduction game where deception, teamwork, and strategy determine your survival. Set in a haunted village, players are assigned secret roles: either as innocent villagers or as devious werewolves lurking in the shadows. Your mission? Unmask the threats before they eliminate you.

The Day Phase
#

Each round begins with a tense day phase, where players communicate, strategize, and attempt to uncover the truth. Who can you trust? Who is lying? Engage in discussions, defend yourself from accusations, and cast your vote to decide who will face Fate’s judgment. The Grim Reaper watches over the village, ready to strike down the chosen suspect with a bolt of purple lightning. But did the villagers make the right call? Or did they just eliminate an innocent soul?

The Night Phase
#

As the night falls, the village plunges into eerie silence. This is when players use their role’s abilities: gathering intelligence, forming secret alliances, or launching deadly attacks. Werewolves prowl in the darkness, choosing their next victim. Meanwhile, protective roles like the Knight can shield players, and investigative roles like the Seer can unveil hidden identities. The right move can change the fate of the village, but one wrong choice could mean your doom.

Infinite Strategies
#

Beyond villagers and werewolves, Spooky Night introduces a vast array of unique roles with special abilities that keep every match unpredictable. Will you be a Sentry, tracking footsteps to catch a killer? A Mayor, wielding extra voting power? Or a Trickster, throwing chaos into every decision? With multiple roles and randomized setups, no two games are ever the same.

Key Features
#

Social Deduction Chaos – Play mind games with friends (or enemies) in this high-stakes survival match.
Unique Role Abilities – Each role has game-changing powers that add depth to every match.
Cartoonish Spooky Aesthetic – A Halloween-themed 2D world filled with eerie yet funny characters.
Vote & Execute – Villagers vote during the day, and Fate (the Grim Reaper) strikes with thunder at night.
Replayability – Each match is different, with a large variety of roles & random interactions.

Trailer & Gameplay
#

▶ Watch the Official Trailer:

Logos & Branding
#

Download Official Assets:

Game Logo (PNG)
Social Media Banners
High-Resolution Key Art

Download

Screenshots & GIFs
#

High-quality in-game screenshots:

Short Clips:

Game Quick Guide
#

Day Phase: Engage in discussions with fellow players to identify the werewolves. Vote to eliminate the most suspicious individual.

End of Day: The player receiving the majority of votes is eliminated, revealing their true role.

Night Phase: Under the cover of darkness, werewolves choose their victims, while villagers and other roles secretly employ their unique abilities to protect, investigate, or take decisive actions.

Win Conditions:
- Villagers: Prevail by eliminating all werewolves.
- Werewolves: Conquer when they equal or outnumber the remaining villagers.

Contact & Social Media
#

For press inquiries, interviews, or review copies, please contact:

Email: info@ozbem.com
Website: https://www.ozbem.com
Steam Page: https://store.steampowered.com/app/3443650/Spooky_Night/
Twitter/X: https://x.com/OzbemSoftware
Discord: https://discord.gg/HH8RFT68DZ

Thank you for your interest in Spooky Night!

The Spooky Night Development Team

Spooky Night Now Available on Itch.io

info@ozbem.com (ebeem) — Tue, 14 Jan 2025 00:00:00 +0000

Greetings, mortals!

I bring you thrilling news from the shadowy realms: Spooky Night has emerged from the depths and is now haunting Itch.io! This online social deduction game of teamwork and betrayal is ready for you to experience.

Play Spooky Night!
#

In this eerie adventure, you’ll step into a haunted village where trust is scarce, and danger lurks in every shadow. Your objectives are clear:

Identify the Werewolves: During the day, engage in discussions, deceive, and vote to eliminate those you suspect of lycanthropy.
Survive the Night: As darkness falls, werewolves strike, and villagers must use their unique abilities to protect, gather clues, or take action.

Each round offers a fresh, unpredictable experience with a variety of unique roles and endless player strategies. No two games are ever the same. Build trust or shatter it as you navigate this treacherous landscape.

Why Itch.io?
#

Free to Play: Dive into the game without spending a dime. Earn rewards after every match and unlock a wide range of character customizations.
Early Access: Be among the first to experience Spooky Night and witness its evolution.
Community Engagement: Join our growing community, share your experiences, and provide feedback to help shape the game’s future.

The game is currently in its early stages, and the number of players is limited. Gather your friends to join a lobby; the game requires at least 4 players but is most enjoyable with 8 or more. Casual game matchmaking requires 10 players.

Join Us Today
#

Ready to face the unknown? Download Spooky Night now on Itch.io and step into the shadows.

Stay spooky, my friends.

ebeem

Spooky Night by Ozbem

River Protocol & Architecture

info@ozbem.com (ebeem) — Thu, 18 Apr 2024 00:00:00 +0000

I’m currently studying River in the hope of crafting a guile scheme based window manager, River uses a unique non-monolithic approach, unlike the "all-in-one" approach seen in many compositors, it splits the responsibilities of rendering and window management.

I am using this post as a living document to log my notes and findings as I study the river-window-management-v1 protocol. One done, it should be a great foundation for those who want to understand my window manager or write their own based on River.

interfaces

river_window_manager_v1

Window management state influences the communication between the compositor and individual windows (e.g. xdg_toplevels). Window management state includes window dimensions, fullscreen state, keyboard focus, keyboard bindings, and more.Only one window management client may be active at a time. The compositor should use the unavailable event if necessary to enforce this.

Requests

(2) stop

description: client wants to stop/close

task: Nothing, wait for finished event to proceed with killing the process

(4) destroy()

description: should be called after the finished event has been received.

task: clear anything that's still references and terminate

(6) manage_finish()

description: client has made all changes to window management state after receiving the manage_start event

task: Nothing, don't send any requests to change window management state unless you receive another manage_start

(7) manage_dirty()

description: indicates that a manage_sequence events is needed to reflect some new state changes

task: Nothing, you will receive a manage_start soon to make the changes as before

(9) render_finish()

description: client has made all changes to rendering state after receiving the render_start event

task: Nothing, don't send any requests to change render state unless you receive another manage_start or manage_render

(15) get_shell_surface(surface: wl_surface) -> id: river_shell_surface_v1

description: client wants to create a new shell surface and assign river_shell_surface_v1 role to provided surface, it can be used to draw status bars, menus, tab bar, etc.

task: Nothing

(16) exit_session()

description: client wants to terminal the wayland session, this will close all clients and the compositor

task: Nothing

Events

(1) unavailable()

description: indicates that window management is unavailable, most likely due to another window management client already running

task: The client should clear everything in this case and terminate

(3) finished()

description: indicates that the server will send no longer events

task: The client should clear everything in this case and send destroy request

(5) manage_start()

description: indicates that the server has sent events indicating new state changes

task: The client should send all requesting modfying the window management state then make a manage_finish request

(8) render_start()

description: indicates that the server has sent events indicating window positions and dimensions changes in the interface river_window_v1

task: The client should send all requesting modfying the rendering state then make a render_finish request

(10) session_locked()

description: indicates that the session has been locked

task: The client should most likely may restrict the available keybindings or call a lock screen application

(11) session_unlocked()

description: indicates that the session has been unlocked

task: The client should most likely may reinitiate the available keybindings

(12) window() -> id: river_window_v1

description: indicates that a new has been created.

task: store the id/proxy and mapping for further use

(13) output() -> id: river_output_v1

description: indicates that a output has been created (monitor plugged)

task: store the id/proxy and mapping for further use

(14) seat() -> id: river_seat_v1

description: indicates that a seat/input has been created (keyboard/mouse/touchscreen plugged)

task: store the id/proxy and mapping for further use

river_window_v1

Logical window. For example, a window may correspond to an xdg_toplevel or Xwayland window. A newly created window will not be displayed until the window manager makes a propose_dimensions or fullscreen request as part of a render_sequence

Requests

(1) close()

description: client want the window to be closed, window may ignore this request

task: wait for closed

(3) destroy()

description: client cleaned window object and it can be safely destroyed

task: nothing

(4) get_node() -> id: river_node_v1

description: client wants to know the node that corresponds to the window, this can only be called once per node, so it should be cached after first call.

task: store it as metadata of the window record/object

(7) propose_dimensions(width: int, height: int)

description: client proposes dimensions for the window.

task: only send in manage_sequence as it modifies the window management state, wait for dimensions event for confirmation about the update

(8) hide()

description: client wants to hide a window (newly created windows are shown by default).

task: only send in render_sequence as it modifies the rendering state.

(9) show()

description: client wants to show a window, care about windows that are placed on top of it as they will not make the target window visible.

task: only send in render_sequence as it modifies the rendering state.

(15) use_csd()

description: client wants to use client side decoration (default).

task: only send in manage_sequence as it modifies the window management state.

(16) use_ssd()

description: tell the client to use server side decoration

task: only send in manage_sequence as it modifies the window management state.

(17) set_borders(edges: uint, width: int, r: uint, g: uint, b: uint,

a:uint)

description: decorates the window with borders drawn by the compositor

task: only send in render_sequence as it modifies the rendering state.

(18) set_tiled(edges: uint)

description: inform the window that it is part of a tiled layout

task: only send in manage_sequence as it modifies the window management state.

(19) get_decoration_above(surface: wl_surface) -> id: river_decoration_v1

description: inform the window that it is part of a tiled layout

task: only send in manage_sequence as it modifies the window management state.

Events

(2) closed()

description: indicates that the window has been closed

task: clean window and send destroy

(5) dimensions_hint(min_width: int, min_height: int, max_width: int,

max_height: int)

description: indicates the window's preferred min/max dimensions (excluding borders and decorations). The window manager is free to propose other dimensions for layouts that require it like tiling.

task: store the preferred dimensions in window object/record for further use. This event will be followed by manage_start and state changes should be made there.

(6) dimensions(width: int, height: int)

description: indicates the window's dimensions (excluding borders and decorations). This event is sent as part of the render_sequence due to propose_dimensions or fullscreen request

task: store the dimensions in window object/record for further use. This event will be followed by render_start and state changes should be made there.

(10) app_id(app_id: string?)

description: indicates the window's application id was changed

task: store the app_id in window object/record for further use. This will be followed by a manage_sequence in case state changes need to be made.

(11) title(title: string?)

description: indicates the window's title was changed

task: store the title in window object/record for further use. This will be followed by a manage_sequence in case state changes need to be made.

(12) parent(parent: river_window_v1?)

description: indicates the window's parent was changed

task: store the parent in window object/record for further use. This will be followed by a manage_sequence in case state changes need to be made.

(13) decoration_hint(hint: uint)

description: indicates the window's parent was changed

task: store the hint in window object/record for further use. This will be followed by a manage_sequence in case state changes need to be made.

(14) decoration_hint(hint: uint)

description: indicates the window's parent was changed

task: store the hint in window object/record for further use. This will be followed by a manage_sequence in case state changes need to be made.

Wayland Protocol & Architecture

info@ozbem.com (ebeem) — Thu, 18 Apr 2024 00:00:00 +0000

Introduction

Wayland is a modern, secure display server protocol for Linux and Unix-like operating systems. It is a replacement for the older X11 system and it manages how applications render graphics and windows to your screen.

In a Wayland desktop, you have two components:

Wayland Client (The Application): This is the individual program (like your web browser or text editor). It draws its own interface and sends the finished pixels to the compositor to be displayed.
Wayland Compositor (The Server/Manager): This is the manager, it handles all hardware input (mouse, keyboard) and forwards it to the proper client (application like your focused browser), and combines all the individual windows rendered by the clients into the final image you see on your screen.

Wayland Package

Installing the wayland package (preinstalled on most modern distros) provides the official freedesktop.org implementation of the protocol. This includes:

wayland.xml: A high-level XML interface defining the core Wayland specifications (requests and events). All Wayland protocols (core and extensions) use this format.

wayland-scanner: A tool that generates C headers and glue code from XML protocol files. Many scanners exist in other languages like rust

libwayland-client & libwayland-server: C libraries that implement the wire protocol for both components and offer common utilities for handling Wayland data structures.

Wayland Protocol

The wayland protocol is actually easy to understand and very elegant. I will explain the interfaces first and then I will go over the wiring protocol and it will start to click.

Interfaces (XML files)

We discussed earlier that there is an xml file which is wayland.xml (we call it core). There are so many other xml files as well which we call extensions to wayland, like xdg-shell which is defines the functionality needed to create windows that can be dragged, resized, etc, in a wayland desktop. You can browse these xml files locally, they will be usually in /usr/share/wayland-protocols/.

I find it sometimes very helpful to peak at Wayland Protocols Explorer, it's very elegant and it shows all popular Wayland protocols. I know there are so many protocols, but nobody is expecting you to know them all. You should just be able to read the documentation and know how to use it.

You might notice that there are labels to these protocols, and they are listed under a certain subdirectories in the wayland-prtocols directory locally.

Core: this is the core wayland protocols
Stable: [TODO]
Staging: [TODO]
Unstable: [TODO]

The XML file format defines interfaces, each interface has many requests, and events. Let's explain this with an example form the core wayland.xml.

There are many interfaces, one of them is wl_surface, below is the code truncated.

 <?xml version="1.0" encoding="UTF-8"?>
 <protocol name="wayland">
 <interface name="wl_display" version="1">
 	...
 </interface>

 ....

 <interface name="wl_surface" version="7">
 	<description summary="an onscreen surface">
 	 A surface is a rectangular area that may be displayed on zero
 	 or more outputs, and shown any number of times at the compositor's
 	 ....
 	</description>
 <enum name="error">
 <description summary="wl_surface error values">
 These errors can be emitted in response to wl_surface requests.
 </description>
 <entry name="invalid_scale" value="0" summary="buffer scale value is invalid"/>
 	 ....
 </enum>
 </interface>
 </protocol>

I am leaving StumpWM and X11

info@ozbem.com (ebeem) — Fri, 12 Apr 2024 00:00:00 +0000

Lisp-Based Tools

If you have spent any significant time in the world of Lisp-based tools, you know that once you invest in tweaking them, you simply can't quit. I have spent years living in Emacs and StumpWM, addicted to the idea that my environment shouldn't just be "configurable," but truly extensible.

In StumpWM and EXWM, the line between "user" and "developer" is paper-thin. If you want a new feature, you don’t submit a feature request; you open a REPL and redefine a function on the fly. However, with X11 nearing its end-of-life and the beauty of modern Hyprland setups I am seeing, I feel it's time to begin my transition to Wayland.

Emacs as a Window Manager

I experimented with EXWM (the Emacs X Window Manager), and initially, I was shocked, I couldn't believe such a feat was even possible. But then again, it’s Emacs; everything is possible. However, the experience highlighted a critical flaw: if Emacs froze or crashed, my entire session vanished.

I've come to realize that I don't want to assign Emacs heavy-duty system tasks like window management. I prefer using Emacs as the interface between myself and other specialized utilities. Much like how dired can act as a frontend for ls, I believe a window manager should be assisted by a dedicated compositor written in a systems language like C, Rust, or Zig. Entrusting the entire desktop session to a single-threaded Lisp interpreter is, in my view, a bottleneck for stability.

Creating a Lisp-Based Scripting Environment

I believe a window manager should apply the "Emacs Principle" because everyone's workflow is unique. I have seen people using Emacs setups so personalized that I couldn't even tell it was Emacs.

In my case, I have a specific workflow requirement: extending workspaces across multiple monitors. Assuming I have 2 monitors ot#1 and ot#2. I want each to have its dedicated workspaces, let's say each will have 3 workspaces. Whenever the workspace of ot#1 changes to workspace number 2, the workspace of ot#2 should also change to workspace number 2 (syncing).

 | ws#1 | ws#2 |
 |-----------------------------------------------------|
 | ws#1-1 & ws#1-2 & ws#1-3 | ws#2-1 & ws#2-2 & ws#2-3 |

I tried implementing this in Sway and Hyprland using their standard configuration languages, but I hit a wall. I could bind a key to switch multiple workspaces simultaneously, which worked temporarily, until a window stole focus or an unexpected workspace change occurred. This inevitably caused the monitors to get out of sync.

To solve this properly, I can't just rely on simple keybindings; I need a persistent event listener. I need the environment to watch for workspace changes and programmatically sync the other monitors accordingly. This requires a level of logic that static config files simply cannot handle.

The Way Forward

I need a compositor that is stable but provides a "hook" for high-level logic preferably with a lisp-based language like guile. My next step is to experiment with a both Sway and Hyprland to see how far I can push the implementation of custom window management logic without sacrificing the stability of the underlying Wayland compositor.

Privacy Policy

info@ozbem.com (ebeem) — Fri, 12 Jan 2024 00:00:00 +0000

Privacy Policy
#

Effective Date: 12/01/2024

1. Information We Collect
#

We collect the following information to manage your account and enhance gameplay:

Personal Information: Name, email address, and IP address.
Device Information: Operating system and hardware details.
In-Game Activity: Player interactions (e.g., chat messages) may be tracked to monitor and control chat abuse.

2. Purpose of Data Collection
#

Your data is collected to:

Create and manage user accounts.
Improve the gameplay experience.
Perform analytics and technical troubleshooting.
Serve advertisements through third-party networks.
Integrate social media features.

3. User Accounts
#

Players can create accounts with their email and username. This information is used to personalize and manage your account.

4. Data Storage and Security
#

Your data is securely stored on our private servers, with the following measures:

Passwords are encrypted for added security.
Access to user data is strictly controlled and monitored.

5. Third-Party Services
#

We utilize third-party services for:

Advertising: Displaying relevant ads based on device information.
Social Media Integration: Enabling content sharing and connections.

These services operate under their own privacy policies.

6. Your Rights
#

You have the right to:

Access and modify your account information.
Request deletion of your account and associated data (accessible from the in-game settings interface).

To exercise these rights, contact us at info@ozbem.com.

7. Children’s Privacy
#

Spooky Night is not intended for children under 13. We do not knowingly collect data from children. If such data is found, it will be promptly deleted.

8. Changes to This Policy
#

We may update this Privacy Policy. Any changes will be posted here with an updated effective date.

9. Contact Us
#

If you have any questions or concerns, please reach out to us:

Email: info@ozbem.com

Index on Ozbem

Emacs Vanilla vs Flavors (Spacemacs and Doom Emacs)

Where to Begin?

The Batteries-Included Flavors

Spacemacs

Doom Emacs

Vanilla Emacs

The Keybinding

Evil Mode (Vim Bindings)

Vanilla Bindings (Emacs Bindings)

Meow (Middle Ground)

My Recommendation

Bootloader

Introduction

Customizing the Bootloader

Themes and Visuals

Firmware (BIOS and UEFI)

Introduction

Upgrading Firmware

Customizing Firmware

Introduction to Guix

TODO Installation

Channels

Adding a channel

Removing a channel

Useful Resources

NonGuix Channel

Adding the NonGuix channel

Useful Resources

System Configuration

Creating System Configuration

Applying System Configuration

Using Nonfree Linux Kernel

Useful Resources

Home Configuration

Creating Home Configuration

Useful Resources

Installing Packages

Finding Packages

Installing a package

Useful Resources

Root Genesis Now Available on Itch.io

What’s it all about? #

MORE SCREENSHOTS #

Play it right now! #

What is Root Genesis?

BUILD YOUR EMPIRE #

COMPLETE CONTRACTS #

UNCOVER THE CONSPIRACY #

MORE SCREENSHOTS #

Spooky Night Is Out Now!

What Is Spooky Night? #

Play Now on Steam and Itch.io #

What’s Included in the Release #

Fair and Transparent Model #

Join the Community #

Thank You #

The Road Ahead for Spooky Night

Spooky Night Vision #

The Roadmap #

Phase 1 (Q1 - Q2 2025) #

Phase 2 (Q3 - Q4 2025) #

Phase 3 (Beyond 2025) #

Join the Community #

What is Spooky Night?

Trailer & Gameplay #

How to Play #

MORE SCREENSHOTS #

Why You’ll Love Spooky Night #

Spooky Night Joins Steam Next Fest

Spooky Night Press Kit

🎃 Spooky Night - Press Kit 🎃 #

Game Overview #

Short Description #

Long Description #

The Day Phase #

The Night Phase #

Infinite Strategies #

Key Features #

Trailer & Gameplay #

What’s it all about?
#

MORE SCREENSHOTS
#

Play it right now!
#

BUILD YOUR EMPIRE
#

COMPLETE CONTRACTS
#

UNCOVER THE CONSPIRACY
#

MORE SCREENSHOTS
#

What Is Spooky Night?
#

Play Now on Steam and Itch.io
#

What’s Included in the Release
#

Fair and Transparent Model
#

Join the Community
#

Thank You
#

Spooky Night Vision
#

The Roadmap
#

Phase 1 (Q1 - Q2 2025)
#

Phase 2 (Q3 - Q4 2025)
#

Phase 3 (Beyond 2025)
#

Join the Community
#

Trailer & Gameplay
#

How to Play
#

MORE SCREENSHOTS
#

Why You’ll Love Spooky Night
#

🎃 Spooky Night - Press Kit 🎃
#

Game Overview
#

Short Description
#

Long Description
#

The Day Phase
#

The Night Phase
#

Infinite Strategies
#

Key Features
#

Trailer & Gameplay
#

Logos & Branding
#

Screenshots & GIFs
#

Game Quick Guide
#

Contact & Social Media
#

Play Spooky Night!
#

Why Itch.io?
#

Join Us Today
#

Privacy Policy
#

1. Information We Collect
#

2. Purpose of Data Collection
#

3. User Accounts
#

4. Data Storage and Security
#

5. Third-Party Services
#

6. Your Rights
#

7. Children’s Privacy
#