All Activity

This stream auto-updates     

  1. Earlier
  2. An additional notice: The migration has currently been postponed, as we were once again running into issues with LFS data not being migrated over correctly. A follow-up announcement will be posted when we have a better idea of when the Gitlab will be properly moved.
  3. * Changed Inline Code toolbar button to use a <code> element instead of a <span> - Removed CKEditor extension: Context Menu (the CKEditor context menu can be access with Ctrl + Right Click if needed) - Removed Killerteddy
  4. Howdy Folks, I just wanted to let everyone know that we will be migrating the Elaztek Gitlab to a new server in the next couple days. Since the Gitlab was released to the public, I’ve been running the Gitlab to allow Errite and Elaztek projects to have a place to store their source code. Over the years we have moved the servers a couple times to either, consolidate servers, or upgrade the servers depending on what server hardware Errite had available. Errite has intentions to move our infrastructure from a single baremetal hypervisor server running in Canada to multiple Cloud VPS servers in favor of moving our more important services to a High Availability Container cluster (Primarily DeviantCord services), and some to standalone cloud servers. The Gitlab will not be using a container setup, but instead its own Cloud VPS server that we will continue to maintain. I highly recommend that if you need to access your source code from July 3rd, to July 5th to make sure you have a local copy to work on while we work on migrating the Gitlab and performing necessary checks to ensure a smooth transition. We will post a message on Discord and the forums once maintenance begins, with updates. ~ Rikez/Michael
  5. * Redesigned Bug Tracker - Rather than relying on the old, needlessly-separated bug and issue trackers, the new bug tracker is lifted largely from the Chaotic United forums, with a single system for all bugs - whether they be for the website, Discord, or Blamite. * Redesigned Suggestions Tracker - Rather than the old system with one single category for all suggestions, this also is lifted from CU where each project/service has its own category. * Replaced old (sometimes broken) links to issue tracker with appropriate links to the new bug tracker - Removed Killerteddy
  6. haloman30

    Galactiminer Screenshots

    Screenshots of Galactiminer can be found here.
  7. Version 0.0.1


    This build was created in 2013, by a literal 13-year-old. This build does not represent modern development standards. This is an ancient build of Galactiminer, a planned project from 2013 under the studio name 'Haloman Development'. This build is a slightly modified version of a C# Voxel Engine named CubeCrafter, which was formerly available on CodePlex prior to its shutdown. The source code has been made public once again on our Gitlab and can be viewed here. The primary modifications were to textures, which were made worse by a 13-year-old haloman30. This project has very little functionality outside of primitive terrain generation and camera movement. No further development of this project is planned (or at least, not on this codebase). Controls: W : Camera forward A : Camera left S : Camera back D : Camera right Numpad - : Camera Up Numpad + : Camera Down
  8. Version 1.0.0


    This is an early build of the Blamite Game Engine. Please be aware that there WILL be bugs, crashes, inconsistencies, and other weird things as this build is extremely early in development. Everything shown is subject to change at any time. This build is untracked, and as such, will not show accurate version information.
  9. haloman30

    1/15/2022 Update

    + Added a new "Resources" section to Blamite homepage * Made blamite doxygen docs public * Rewrote some of the text on the Blamite homepage to be less weird - Removed Killerteddy
  10. Hey, everyone! We've got a short and sweet announcement today. As of today, all of our generated documentation for the Blamite Game Engine is now public to all users. What does this mean? This means slightly different things depending on who you are. If you're part of our team, it means you don't have to remember your login credentials anymore. If you're someone who just wants to play a game, this will likely be meaningless to you. If you're someone who's curious as to what goes on with Blamite under the hood, this ought to be an exciting source of knowledge for you to comb through. What does the documentation contain? The documentation contains information about a great deal of the code within the engine. It includes documentation of all classes, methods, global variables, macros, enums, functions, and more throughout the entire game engine, including the engine core itself, the executables, and all the Editing Kit. The vast majority of code should be fully documented, although you may find areas here and there which aren't. These are likely incomplete features that are undergoing major changes, legacy code that will be removed in the future, or just something that we forgot to document As of right now, the list of projects available are as follows: blam - The game engine core. blamite - A small executable which is used to run the engine. eula - An unused library which will likely be removed in the future. FontExtractor - A C#-based tool used to create font packages. foundry - A small executable used to run the Foundry editor. guerilla - A small executable used to run the Guerilla tag editor. HEKFoundry - The library containing all Foundry-specific functionality. Used by foundry and keystone. HEKGuerilla - The library containing all Guerilla-specific functionality. Used by guerilla and keystone. HEKSapien - The library containing all Sapien-specific functionality. Used by sapien and keystone. HEKTool - The library containing all Tool-specific functionality. Used by tool and keystone. keystone - A library that contains all Qt-based UI functionality. Used within the entire Editing Kit, excluding legacy C# projects. sapien - A small executable used to run the Sapien level editor. Strings - A general-purpose library used across all projects. tool - A small executable used to run Tool. verstamp - A smal C#-based utility, used during the Jenkins build procedure to "stamp" version information into a build. How can I access it? The latest documentation from a fresh Jenkins build will always be accessible at . However, we also archive documentation from all prior builds as well. You can browse these at Please note that you will see 'Restricted' messages on all documentation builds prior to 00347. This is because until now, the documentation was completely restricted to the public. You may of course disregard those warnings now. If you have any questions about Blamite (or of anything you run across in the documentation), feel free to let me know either here on the website, or on our Discord!
  11. haloman30

    12/14/2021 Update

    * Fixed an issue where Guests could post comments on blog entries * Fixed an issue where Guests could edit their own Mood - Removed Killerteddy
  1. Load more activity