haloman30

CEO
  • Content Count

    314
  • Joined

  • Last visited

  • Days Won

    4
  • Time Online

    24855d 3h 14m 7s

 Content Type 

Profiles

Bug Tracker

News & Announcements

Helpcenter

Products

Project: Infinity Issue Tracker

Blamite Game Engine Issue Tracker

Elaztek Launcher Issue Tracker

NTClient Version History

Suggestions Tracker

Forums

Store

Blogs

Downloads

Calendar

Forms

Everything posted by haloman30

  1. * Archived subforum: Eon Game Engine - Removed Killerteddy
  2. + Added custom emoji from CU Forums (and some extra ones) + Added partners page + Added parnters page to navigation menu + Added new Blamite homepage + Added new Blamite homepage to navigation menu * Help > About now has an icon on Midnight 7.1 - Removed old Blamite website - Removed Killerteddy
  3. + Added new theme: Midnight 7.1 * Default theme set to Midnight 7.1 * Restructured navigation menu * Lots of backend file cleanup * Preparations to consolidate Issue Tracker into Bug Tracker - Removed Killerteddy
  4. Hey, folks! Been a while, hasn't it? That seems to be a common thing unfortunately. Anywho, we've got some new stuff to share with you guys. You may have noticed some of the changes yourself - but we're shaking some stuff around. We've organized them into neat little sections for your convenience. Website Let's start with the site changes, shall we? Themes You may have noticed a number of adjustments have been made to our default theme - Midnight 7.1. Most of these aren't major changes, but they should no-doubt help make things look a bit nicer. The navigation menu has some new icons, and what used to be darker blues are now brighter and more vibrant. Most elements also now have nice animations to them rather than being static. Along with that, some weird quirks with the theme have been taken care of at last, as well as some remnants of the original Midnight theme. If you prefer the old theme, it's still available as 'Midnight 7'. Navigation Along with the nice icons we mentioned before, you might also notice that the menu itself has been reorganized a bit. This was done to make it more consistent with the improvements made on Chaotic United's site, which we believe is a significant improvement over the old navigation menu. Forms We've moved the Project: Infinity and Blamite team sign-up pages over to our own Forms system. In fact, you might notice that there's only one form now. We've consolidated our standard Staff, Blamite Game Engine, Galactiminer, and Project: Infinity signup forms into a single, nicely laid-out form. The new format also borrows some of the improvements made to CU's Staff Application format recently as well. The other forms from CU (Reports, Ban Appeals, etc) have also been brought over and tweaked as need be. Along with that, you'll also notice that several subforums now have handy redirect links to their respective forms, to make submitting things nice and easy. Discord It's not just our site that got some facelifting, our Discord server also got some renovating done too. Gitlab Integration Fun fact - we've had Gitlab notifications on Discord for a long time. They've just been exclusively visible to our team up until now. We figure that, since major announcement-worthy progress updates are so few and far between, it makes sense to at least give you guys a glimpse into what's happening with Blamite and our other projects. Basically, any time a commit, issue, wiki page, or anything of that sort is made to one of our linked repositories, a notification is posted in the #gitlab channel. You won't be able to view the source code of course - but you'll still get an idea of what we're doing behind the scenes. NSFW Channel Do I even need to say anything here? Yes, yes I do actually. By default, you won't see the #nsfw channel. We ask that you review the information in #nsfw-info before heading in. It contains some info about how to access the channel, as well as a few rules that apply to the channel. As of the time of writing this, the rules are as follows: Shock content will NOT be allowed - We define shock content as things such as 2 girls 1 cup, gore, and anything else that is generally intended to be disturbing. The general rule is: "is this someone would want to see"? If the answer is no, it probably shouldn't be posted. Do not post any images, videos, or other content of yourself - We don't want to see your body and chances are, you don't really want to have your naked body floating around the internet either. Post it somewhere else if you really want to, but keep it out of here. All images, videos, and other content must be of people 18 or older - This should be pretty self-explanatory. There will be absolutely zero content of minors posted. The rest of the community rules apply - You can't break all the other rules just because one of them doesn't apply in this specific channel. If you're 18 or older and would like to share or view *ahem* mature content , you can do !nsfw in #bot_turing_test. You can hide the channel again at any time by doing !nonsfw. If you know for a fact you never want to see adult content, you're free to hide the #nsfw-info channel and pretend it doesn't exist by doing !nsfw-ignore. You can also restore that channel by doing !nsfw-unignore. Keep in mind that breaking any of the rules above will result in removal from the channel, or in some cases being banned from the Discord server outright. It's a channel for mature content, please be mature when using it. Additional #forums-feed Notifications Previously, only a handful of content sent a notification to Discord. Now, virtually all content appears. The two ones of note are Status Updates and Blog Entries. Neither of these posted on Discord before - and now they do. The Team, and the Eon Game Engine You may have noticed mention of a project of ours called the Eon Game Engine. This project was spearheaded exclusively by a former developer of ours, @JTKreates. However, due to him becoming busier with life and other such things, he had to step down. As such, Eon is being shelved for the foreseeable future. We are retaining the source code in the event it could be useful, but our current plans don't really include any 2D-based games - so don't expect anything about it for a while. Additionally, we'd like to introduce the first of hopefully many new team members for Blamite - @zzVertigo! His previous experience includes mostly networking stuff, including the Halo Online Rewritten project. He's been hard at work getting Blamite's networking foundation added - which has proven fairly easy due to the early stages of the engine. Of course - if you happen to be interested in joining the team, feel free to apply! We are always looking for new team members - so if you think you've got what it takes, don't hesitate! Join the Team Upcoming Changes In the future, we're going to be continuing to refine and restructure the website. The issue trackers are being removed in favor of a unified bug tracker. The Blamite website will, in its entirety, be replaced with a page that is integrated into the Elaztek website itself - rather than acting as a completely isolated website. Its functionality will be replicated as it currently exists, but the design will match the rest of Elaztek. Other old pages too are being sent to the archives that are redundant or otherwise unnecessary. Company Direction Now, all that stuff is cool, but this announcement isn't just about some site and Discord enhancements. You saw the title - you knew something like this was coming. We're currently gearing up to start the long journey of putting Elaztek Studios on the map. Here recently, Michael informed me of an independent studio that had only existed for less than a year - they have a functional (still incomplete, but functional) game engine, a team, and are a LOT further along than we are right now. There's two major reasons that Elaztek is still where it's at currently after over two years: Chaotic United, and my own stubbornness. There isn't much I can do about the former. Chaotic United is, and always will be my baby. It's a passion project and it continues to exist because I genuinely enjoy doing it. The trouble is, the way I've been going about managing the two has been rather troublesome. I would focus entirely on CU, at which point Elaztek basically goes on hold. After a few months, guilt creeps up and I feel bad for basically ignoring it. At which point I shift gears and go all out on Elaztek. A few months later, guilt creeps up and...I think you see where I'm going with this. I focus on one 100%, then shift gears and focus on the other. I've tried and failed to have a proper balance - what usually happens is that I'm focused on a certain task on one that ends up spanning multiple days, then I keep going and eventually just get too wrapped up in it - then I look and it's been a few months since I've touched the other. However, there's still something we can and are doing about it. Part of it is something that I'll have to slowly learn and get better at doing, which is managing my time and being able to distribute it effectively between the two. The other part comes to the relationship between the two. Elaztek Studios and Chaotic United You see, back when Elaztek first launched in a real, public sense, it was under awful circumstances. Elaztek had existed for over a year prior to it's public launch, and it's history dated even further back if you count Haloman Development. But when it went from being essentially just an idea to being an actual website and entity that existed, it was in response to drama and chaos that had befallen Chaotic United. Back in 2017, a lot of us were still fairly immature - some more than others, but overall it was a chaotic situation that could have, and should have been easily avoided. It was the conclusion of those events that led to Elaztek's launch. Several staff at CU disagreed with my final decision, and nearly left outright - so, I compromised. Elaztek Studios would become their new home, and they luckily agreed. The person involved would be banned from the start and would have no place in Elaztek. This would be both a safe haven and a new frontier to pursue. Over time, however, people matured. Time passed, and people came back to CU. Despite this, however, some of our team members were still largely uncomfortable with bridging the gap between CU and Elaztek. A gap that used to be nonexistent, but still remained despite the smoke clearing. Some small baby steps were made (primarily the ability to link your Elaztek and CU forum accounts), but they were overall still kept separate, and that person kept banned. Today marks the end of that period of time - and with it, a new era for Elaztek Studios. CU and Elaztek will continue - separated, but standing side by side. The two will, moving forward, be partnered with one another. With it, we will be introducing a new Partner program. The details of which are still being ironed out, but the goal is to be able to partner with other relevant communities - big or small. Expect a separate announcement on that once we launch it for real. The person in question will be allowed into our doors, with welcome arms. The wall that was built up between CU and Elaztek has been torn down, and the two will no longer be kept away from each other, but instead be sisters. There are no immediate plans to make use of this, but expect to see CU get included in some things we do here from time to time - it'll probably be a while before anything happens, but the door is open. I briefly considered merging the two together once more, however I feel that ultimately, while it would help things in the short term, the two ultimately have too different of goals to sensibly be a single entity. Chaotic United is a gaming community, primarily focused on Minecraft. It briefly dabbled with game development somewhat with Demoria Online, but the project never panned out and was still separate from CU during its development. Elaztek is focused on game and software development. While granted, both do have a lot in common - the relaxed atmosphere with their teams, the same guidelines, similar Discord and Forum structure, among other things - they both are seeking separate objectives. As such, they are going to continue to remain separate entities. Coming back to the partner program however, our plan is to be more open than we have been to outside communities. Previously I've been fairly squeamish about working with other communities - for fear of losing some of my team to "greener pastures" if you will, or fear that the partnership won't yield any results. These fears are based on virtually nothing - and ultimately, we're at the bottom and we need people to help grow our team and community. The Blamite Game Engine will not happen on its own. I can't do it alone. I'm getting better with C++, but I am still ultimately just one man. One man cannot build a game engine on the same scale as Unreal or Unity or Slipspace. I suppose in a sense you could consider this a sort of relaunch of Elaztek, although it's not so much a relaunch as it is turning a new leaf. Much like CU's nearing 1.14 update, I hope that this is the start point of Elaztek actually making progress. A point where we look back on, where we can say "that's the point where it all began". Whether or not that will happen is yet to be seen. Some other changes are coming down the pipeline as well. I'm going to be making some much-needed refinements to Elaztek's website and its general direction. Stay tuned.
  5. Hey, folks! Been a while, hasn't it? That seems to be a common thing unfortunately. Anywho, we've got some new stuff to share with you guys. You may have noticed some of the changes yourself - but we're shaking some stuff around. We've organized them into neat little sections for your convenience. Website Let's start with the site changes, shall we? Themes You may have noticed a number of adjustments have been made to our default theme - Midnight 7.1. Most of these aren't major changes, but they should no-doubt help make things look a bit nicer. The navigation menu has some new icons, and what used to be darker blues are now brighter and more vibrant. Most elements also now have nice animations to them rather than being static. Along with that, some weird quirks with the theme have been taken care of at last, as well as some remnants of the original Midnight theme. If you prefer the old theme, it's still available as 'Midnight 7'. Navigation Along with the nice icons we mentioned before, you might also notice that the menu itself has been reorganized a bit. This was done to make it more consistent with the improvements made on Chaotic United's site, which we believe is a significant improvement over the old navigation menu. Forms We've moved the Project: Infinity and Blamite team sign-up pages over to our own Forms system. In fact, you might notice that there's only one form now. We've consolidated our standard Staff, Blamite Game Engine, Galactiminer, and Project: Infinity signup forms into a single, nicely laid-out form. The new format also borrows some of the improvements made to CU's Staff Application format recently as well. The other forms from CU (Reports, Ban Appeals, etc) have also been brought over and tweaked as need be. Along with that, you'll also notice that several subforums now have handy redirect links to their respective forms, to make submitting things nice and easy. Discord It's not just our site that got some facelifting, our Discord server also got some renovating done too. Gitlab Integration Fun fact - we've had Gitlab notifications on Discord for a long time. They've just been exclusively visible to our team up until now. We figure that, since major announcement-worthy progress updates are so few and far between, it makes sense to at least give you guys a glimpse into what's happening with Blamite and our other projects. Basically, any time a commit, issue, wiki page, or anything of that sort is made to one of our linked repositories, a notification is posted in the #gitlab channel. You won't be able to view the source code of course - but you'll still get an idea of what we're doing behind the scenes. NSFW Channel Do I even need to say anything here? Yes, yes I do actually. By default, you won't see the #nsfw channel. We ask that you review the information in #nsfw-info before heading in. It contains some info about how to access the channel, as well as a few rules that apply to the channel. As of the time of writing this, the rules are as follows: Shock content will NOT be allowed - We define shock content as things such as 2 girls 1 cup, gore, and anything else that is generally intended to be disturbing. The general rule is: "is this someone would want to see"? If the answer is no, it probably shouldn't be posted. Do not post any images, videos, or other content of yourself - We don't want to see your body and chances are, you don't really want to have your naked body floating around the internet either. Post it somewhere else if you really want to, but keep it out of here. All images, videos, and other content must be of people 18 or older - This should be pretty self-explanatory. There will be absolutely zero content of minors posted. The rest of the community rules apply - You can't break all the other rules just because one of them doesn't apply in this specific channel. If you're 18 or older and would like to share or view *ahem* mature content , you can do !nsfw in #bot_turing_test. You can hide the channel again at any time by doing !nonsfw. If you know for a fact you never want to see adult content, you're free to hide the #nsfw-info channel and pretend it doesn't exist by doing !nsfw-ignore. You can also restore that channel by doing !nsfw-unignore. Keep in mind that breaking any of the rules above will result in removal from the channel, or in some cases being banned from the Discord server outright. It's a channel for mature content, please be mature when using it. Additional #forums-feed Notifications Previously, only a handful of content sent a notification to Discord. Now, virtually all content appears. The two ones of note are Status Updates and Blog Entries. Neither of these posted on Discord before - and now they do. The Team, and the Eon Game Engine You may have noticed mention of a project of ours called the Eon Game Engine. This project was spearheaded exclusively by a former developer of ours, @JTKreates. However, due to him becoming busier with life and other such things, he had to step down. As such, Eon is being shelved for the foreseeable future. We are retaining the source code in the event it could be useful, but our current plans don't really include any 2D-based games - so don't expect anything about it for a while. Additionally, we'd like to introduce the first of hopefully many new team members for Blamite - @zzVertigo! His previous experience includes mostly networking stuff, including the Halo Online Rewritten project. He's been hard at work getting Blamite's networking foundation added - which has proven fairly easy due to the early stages of the engine. Of course - if you happen to be interested in joining the team, feel free to apply! We are always looking for new team members - so if you think you've got what it takes, don't hesitate! Join the Team Upcoming Changes In the future, we're going to be continuing to refine and restructure the website. The issue trackers are being removed in favor of a unified bug tracker. The Blamite website will, in its entirety, be replaced with a page that is integrated into the Elaztek website itself - rather than acting as a completely isolated website. Its functionality will be replicated as it currently exists, but the design will match the rest of Elaztek. Other old pages too are being sent to the archives that are redundant or otherwise unnecessary. Company Direction Now, all that stuff is cool, but this announcement isn't just about some site and Discord enhancements. You saw the title - you knew something like this was coming. We're currently gearing up to start the long journey of putting Elaztek Studios on the map. Here recently, Michael informed me of an independent studio that had only existed for less than a year - they have a functional (still incomplete, but functional) game engine, a team, and are a LOT further along than we are right now. There's two major reasons that Elaztek is still where it's at currently after over two years: Chaotic United, and my own stubbornness. There isn't much I can do about the former. Chaotic United is, and always will be my baby. It's a passion project and it continues to exist because I genuinely enjoy doing it. The trouble is, the way I've been going about managing the two has been rather troublesome. I would focus entirely on CU, at which point Elaztek basically goes on hold. After a few months, guilt creeps up and I feel bad for basically ignoring it. At which point I shift gears and go all out on Elaztek. A few months later, guilt creeps up and...I think you see where I'm going with this. I focus on one 100%, then shift gears and focus on the other. I've tried and failed to have a proper balance - what usually happens is that I'm focused on a certain task on one that ends up spanning multiple days, then I keep going and eventually just get too wrapped up in it - then I look and it's been a few months since I've touched the other. However, there's still something we can and are doing about it. Part of it is something that I'll have to slowly learn and get better at doing, which is managing my time and being able to distribute it effectively between the two. The other part comes to the relationship between the two. Elaztek Studios and Chaotic United You see, back when Elaztek first launched in a real, public sense, it was under awful circumstances. Elaztek had existed for over a year prior to it's public launch, and it's history dated even further back if you count Haloman Development. But when it went from being essentially just an idea to being an actual website and entity that existed, it was in response to drama and chaos that had befallen Chaotic United. Back in 2017, a lot of us were still fairly immature - some more than others, but overall it was a chaotic situation that could have, and should have been easily avoided. It was the conclusion of those events that led to Elaztek's launch. Several staff at CU disagreed with my final decision, and nearly left outright - so, I compromised. Elaztek Studios would become their new home, and they luckily agreed. The person involved would be banned from the start and would have no place in Elaztek. This would be both a safe haven and a new frontier to pursue. Over time, however, people matured. Time passed, and people came back to CU. Despite this, however, some of our team members were still largely uncomfortable with bridging the gap between CU and Elaztek. A gap that used to be nonexistent, but still remained despite the smoke clearing. Some small baby steps were made (primarily the ability to link your Elaztek and CU forum accounts), but they were overall still kept separate, and that person kept banned. Today marks the end of that period of time - and with it, a new era for Elaztek Studios. CU and Elaztek will continue - separated, but standing side by side. The two will, moving forward, be partnered with one another. With it, we will be introducing a new Partner program. The details of which are still being ironed out, but the goal is to be able to partner with other relevant communities - big or small. Expect a separate announcement on that once we launch it for real. The person in question will be allowed into our doors, with welcome arms. The wall that was built up between CU and Elaztek has been torn down, and the two will no longer be kept away from each other, but instead be sisters. There are no immediate plans to make use of this, but expect to see CU get included in some things we do here from time to time - it'll probably be a while before anything happens, but the door is open. I briefly considered merging the two together once more, however I feel that ultimately, while it would help things in the short term, the two ultimately have too different of goals to sensibly be a single entity. Chaotic United is a gaming community, primarily focused on Minecraft. It briefly dabbled with game development somewhat with Demoria Online, but the project never panned out and was still separate from CU during its development. Elaztek is focused on game and software development. While granted, both do have a lot in common - the relaxed atmosphere with their teams, the same guidelines, similar Discord and Forum structure, among other things - they both are seeking separate objectives. As such, they are going to continue to remain separate entities. Coming back to the partner program however, our plan is to be more open than we have been to outside communities. Previously I've been fairly squeamish about working with other communities - for fear of losing some of my team to "greener pastures" if you will, or fear that the partnership won't yield any results. These fears are based on virtually nothing - and ultimately, we're at the bottom and we need people to help grow our team and community. The Blamite Game Engine will not happen on its own. I can't do it alone. I'm getting better with C++, but I am still ultimately just one man. One man cannot build a game engine on the same scale as Unreal or Unity or Slipspace. I suppose in a sense you could consider this a sort of relaunch of Elaztek, although it's not so much a relaunch as it is turning a new leaf. Much like CU's nearing 1.14 update, I hope that this is the start point of Elaztek actually making progress. A point where we look back on, where we can say "that's the point where it all began". Whether or not that will happen is yet to be seen. Some other changes are coming down the pipeline as well. I'm going to be making some much-needed refinements to Elaztek's website and its general direction. Stay tuned.
  6. This update includes changes from the past 2-3 weeks. * Footer navigation for all Midnight themes is now linked together * Reorganized navigation menu * Reorganized backend page structure, archived legacy pages - Removed Killerteddy
  7. * Archived forum: ARK: Survival Evolved * Archived forum: Just Cause 2 * Archived forum: Don't Starve Together * Archived forum: Counter Strike: Global Offensive - Removed Killerteddy
  8. Hey, folks. For those who haven't been keeping up with our Discord, there's a fairly important announcement we have to make in regards to the Gitlab. Actually, we made it before - but failed to announce it on Discord in a timely fashion. So, here's the general situation: due to a failure in a backup we made a while back (an error with Gitlab itself unfortunately, not user-error to our knowledge), LFS data was excluded from the backup. It took us a fair bit to realize this fact, but once we did it was already far too late. All LFS data on the original Elaztek Gitlab is gone. There's nothing we can do to recover it. If you have your local files on hand, we advise making a backup and keeping those files held tight as they are likely the only copy with any LFS files. If your repository doesn't use LFS, you should be in the clear. We are migrating to a new Gitlab at https://newgitlab.elaztek.com - creative hostname, I know. All data must be manually migrated - this includes wiki pages, tags, branches, issues, milestones, labels, and everything else. We are leaving the old gitlab online until sometime in July to allow users to move over. After the old Gitlab shuts down, the new Gitlab will likely return to the standard gitlab.elaztek.com subdomain to keep things clean and consistent (assuming doing so wouldn't cause a plethora of problems). The other part of this announcement is in regards to announcements themselves - we've been doing a pretty terrible job at actually announcing things timely. There's been a couple announcements that were late to the party, namely the one where we shut down most of the old gameservers. The Gitlab LFS data one was announced on forums, but never got a proper announcement on Discord until a while later. This obviously is no way to do things and is something we promise to never repeat. For slightly more information the LFS incident, check the original topic Michael posted a while back here.
  9. Hey, folks. For those who haven't been keeping up with our Discord, there's a fairly important announcement we have to make in regards to the Gitlab. Actually, we made it before - but failed to announce it on Discord in a timely fashion. So, here's the general situation: due to a failure in a backup we made a while back (an error with Gitlab itself unfortunately, not user-error to our knowledge), LFS data was excluded from the backup. It took us a fair bit to realize this fact, but once we did it was already far too late. All LFS data on the original Elaztek Gitlab is gone. There's nothing we can do to recover it. If you have your local files on hand, we advise making a backup and keeping those files held tight as they are likely the only copy with any LFS files. If your repository doesn't use LFS, you should be in the clear. We are migrating to a new Gitlab at https://newgitlab.elaztek.com - creative hostname, I know. All data must be manually migrated - this includes wiki pages, tags, branches, issues, milestones, labels, and everything else. We are leaving the old gitlab online until sometime in July to allow users to move over. After the old Gitlab shuts down, the new Gitlab will likely return to the standard gitlab.elaztek.com subdomain to keep things clean and consistent (assuming doing so wouldn't cause a plethora of problems). The other part of this announcement is in regards to announcements themselves - we've been doing a pretty terrible job at actually announcing things timely. There's been a couple announcements that were late to the party, namely the one where we shut down most of the old gameservers. The Gitlab LFS data one was announced on forums, but never got a proper announcement on Discord until a while later. This obviously is no way to do things and is something we promise to never repeat. For slightly more information the LFS incident, check the original topic Michael posted a while back here.
  10. Hey there! Chances are you're reading this because you're interested in playing Project: Infinity when it releases, or maybe you even want to help us make it a reality. Maybe you're curious as to what it is. Whatever boat you fall in, keep reading. Introduction Project: Infinity is a fan-made Halo project, focusing on bringing a unique Halo experience to PC. Unlike other Halo fan projects, we aim to offer a complete experience - featuring both a single player Campaign and full multiplayer. We plan to include everything that players expect to see within a Halo game, and more. Along with this, we plan to create our own engine that mimics the Halo engine - the Blamite Game Engine. We want to build a game that is accessible and familiar from players and modders alike. Our Goals As mentioned before, we plan to build our own engine from the ground up to mimic the Halo engine. In a more general sense, we want to have the following features available upon the game's completion: Campaign Multiplayer Custom Games Forge Theater Mod Support We plan to continue utilizing Blamite after Project: Infinity for all future games we produce, retaining most of these same features. How You Can Help If you want to help us out with bringing Blamite and Project: Infinity to life, you can apply to join our team. We do ask that you provide examples of your skills. In particular, we are looking for people who can help us in the following areas: Blamite Game Engine C++ and C# (some of our toolset utilizes C#, but the core engine is in C++) Experience with DirectX (OpenGL is also good as we plan to add support for it later) If you are a skilled member of the Halo modding community, we'd especially love to have you on board Project: Infinity Concept Artists As we progress, we will also be looking for people in these areas: 3D Artists (UNSC, Covenant, Forerunner, Flood, Civilian, Nature) 2D Artists (UI/HUD, Medals, etc) Sound Designers (Game SFX) Voice Actors While people are free to apply for these positions now, these won't be heavily needed until later. Apply to the Project: Infinity Team Apply to the Blamite Game Engine Team
  11. CEO These are the people who lead the company. They are involved in most, if not everything that happens within Elaztek Studios. Administrator These people administer the servers and/or forums, and ensure everything is running smoothly. Manager These folk manage game servers and make sure that you're able to have a smooth online experience with our games. Advisor Advisors are special members who serve to guide our decisions and give input when needed. While most of our team gives feedback, these guys are generally more notable members of either the community, or are former staff of Elaztek or Chaotic United. Voice Acting Team These people are tasked with delivering stellar voice acting for our characters in our stories. Without them, the stories we create would be devoid of personality. Join the Team Art Team These people create everything you'll see ingame. Literally. Any texture, 3D model, HUD element, and muzzle flash was make by someone in here. They may also contribute to our website from time to time as well. Join the Team Audio Team These people create the ear-pleasing sound effects as well as the beautiful melodies you hear ingame. They're responsible for all things sound. Join the Team Development Team These people are the backbone of our games. They help create the engine, the tools, and everything in between to ensure that we can create games that are enjoyable, as well as ensure that you - the community - can mod and tweak it to your liking. Join the Team Story Team These are the people who write our stories. They plan out and script every aspect of our campaigns, to ensure that we can succeed in both gameplay and story. Join the Team Moderator These people moderate our games, as well as our Forums and Discord, to ensure that the community guidelines aren't being broken left and right. They generally help keep order within the community. Apply Helper These people help out with the operation of the community. They might also assist with the game development process as well. Apply Tester These are people hand-picked from our community to help beta test our games. While we may run Insider flights to parts of the community, our Testers tend to be involved in testing much earlier builds of our games. Veteran These are members who have been in Elaztek or within Chaotic United for a long time. Premium These are members who donate to ensure we can keep the lights on. Thanks guys! Donate Member These are people who have joined our awesome community. Sign Up Closed These are members who have either requested their accounts be closed, or have been banned from the forums for repeat violations of our guidelines.
  12. Hey there! Are you a fan of Halo? Maybe even a modder? Or maybe you're just interested in game development. Recently we just cut out a few of our inactive team members (mainly ones who came over from CU) and we're looking to help replace those roles and then some. In either case, we're looking for new people to join our team! The Blamite Game Engine and Project: Infinity won't make themselves - we need a team to help bring them to life. If you're interested in helping out with Project: Infinity, check out the Project: Infinity signup page. If you're more interested in the engine itself, you can check out the Blamite signup page. Our requirements aren't too strict, we ask only that you have some level of skill in the area you're looking to apply for, and that you have a good attitude. We tend to be fairly casual in our staff-only chats on Discord and Forums, and we tend to be fairly laid back overall. If that sounds like an environment for you then by all means - apply! Project: Infinity Team Signup Page Blamite Game Engine Team Signup Page
  13. Hey there! Are you a fan of Halo? Maybe even a modder? Or maybe you're just interested in game development. Recently we just cut out a few of our inactive team members (mainly ones who came over from CU) and we're looking to help replace those roles and then some. In either case, we're looking for new people to join our team! The Blamite Game Engine and Project: Infinity won't make themselves - we need a team to help bring them to life. If you're interested in helping out with Project: Infinity, check out the Project: Infinity signup page. If you're more interested in the engine itself, you can check out the Blamite signup page. Our requirements aren't too strict, we ask only that you have some level of skill in the area you're looking to apply for, and that you have a good attitude. We tend to be fairly casual in our staff-only chats on Discord and Forums, and we tend to be fairly laid back overall. If that sounds like an environment for you then by all means - apply! Project: Infinity Team Signup Page Blamite Game Engine Team Signup Page
  14. Hey, everyone! We've got a once again well-after-the-fact announcement for you all. As you know, last fall we announced the return of Galactiminer in the form of Galactiminer: Evolved, and showcased it appearing to gain a lot more progress than had ever been seen for Project: Infinity. We'd announced a Kickstarter campaign, and after it failed, we went silent. No word was said regarding any of it since then. Unfortunately, after the failure of the campaign, I'd been stuck in Walmart - a job very ill-fitting for my abilities on a variety of levels. This job sucked my time away, and I eventually had to drop this job. It was destroying my physically and mentally as I was in constant pain, and I'd been unable to do much of anything. The failure of the Kickstarter campaign marked the point where I'd lost most of my drive for Galactiminer. That's why it all went quiet. Development went on a bit longer after the end of the failed campaign, but it eventually halted. Afterward, I'd moved on to work on Blamite again - as I found that working on Project: Infinity and Blamite were the two things I had true drive to do. Galactiminer: Evolved was born out of a desire to avoid working at a job. That's why I started the campaign, and it eventually flopped. That's why after it failed, it all stopped. That's not to say that I don't like the ideas that I'd come up with for the new and improved Galactiminer, but this specific mode of execution wasn't one that lined up with what I would consider the right way to do things. It was a business move - and I'm not one to particularly be fond about the business side of things. Why is this announcement titled 'History Repeats Itself'? Because for those of you not around back in 2013, when Galactiminer and Infinity were owned by Haloman Development, this is almost exactly what happened. Galactiminer was the original project, which was later shelved in favor of Project: Infinity. So, what's next? Project: Infinity will continue to be our primary focus moving forward. Starting first with the engine - Blamite - and then as it starts to progress, the content will start to be developed. We have donations open for anyone who would like to help out financially, and we will be continuing to look for anyone who wants to help work on the project. We're open to anyone joining the team, whether you're wanting to work on the engine or on actual game content. Just keep in mind that it's going to be a while before we can start to build a cohesive game with our engine - as it can't even render 3D yet. We have confirmed that the composer we had sought out for Galactiminer, Verblendet, will be sticking with us for Project: Infinity. He's a bit tied up with other stuff currently as he isn't exclusively working with Elaztek, but we'll definitely be sharing music once we have a completed piece to share with you. What about Galactiminer? We plan to revisit Galactiminer properly in the future, when we have the people and the funding. Galactiminer is a far too ambitious game for us to realistically accomplish right now. That's not to say it's impossible, but for our relatively small and unknown team, it may as well be. Creating a game engine is also ambitious, yes, but it's not hinging on technology that barely exists. It's not dead, but it's going to remain on hold until we can do it right. Until then, we're gonna keep working on Project: Infinity and deliver on the promise we made all those years ago. If you want to join the Project: Infinity team, head here. If you want to join the Blamite Game Engine team, head here. If you want to hop on our Discord, check it out here.
  15. Hey, everyone! We've got a once again well-after-the-fact announcement for you all. As you know, last fall we announced the return of Galactiminer in the form of Galactiminer: Evolved, and showcased it appearing to gain a lot more progress than had ever been seen for Project: Infinity. We'd announced a Kickstarter campaign, and after it failed, we went silent. No word was said regarding any of it since then. Unfortunately, after the failure of the campaign, I'd been stuck in Walmart - a job very ill-fitting for my abilities on a variety of levels. This job sucked my time away, and I eventually had to drop this job. It was destroying my physically and mentally as I was in constant pain, and I'd been unable to do much of anything. The failure of the Kickstarter campaign marked the point where I'd lost most of my drive for Galactiminer. That's why it all went quiet. Development went on a bit longer after the end of the failed campaign, but it eventually halted. Afterward, I'd moved on to work on Blamite again - as I found that working on Project: Infinity and Blamite were the two things I had true drive to do. Galactiminer: Evolved was born out of a desire to avoid working at a job. That's why I started the campaign, and it eventually flopped. That's why after it failed, it all stopped. That's not to say that I don't like the ideas that I'd come up with for the new and improved Galactiminer, but this specific mode of execution wasn't one that lined up with what I would consider the right way to do things. It was a business move - and I'm not one to particularly be fond about the business side of things. Why is this announcement titled 'History Repeats Itself'? Because for those of you not around back in 2013, when Galactiminer and Infinity were owned by Haloman Development, this is almost exactly what happened. Galactiminer was the original project, which was later shelved in favor of Project: Infinity. So, what's next? Project: Infinity will continue to be our primary focus moving forward. Starting first with the engine - Blamite - and then as it starts to progress, the content will start to be developed. We have donations open for anyone who would like to help out financially, and we will be continuing to look for anyone who wants to help work on the project. We're open to anyone joining the team, whether you're wanting to work on the engine or on actual game content. Just keep in mind that it's going to be a while before we can start to build a cohesive game with our engine - as it can't even render 3D yet. We have confirmed that the composer we had sought out for Galactiminer, Verblendet, will be sticking with us for Project: Infinity. He's a bit tied up with other stuff currently as he isn't exclusively working with Elaztek, but we'll definitely be sharing music once we have a completed piece to share with you. What about Galactiminer? We plan to revisit Galactiminer properly in the future, when we have the people and the funding. Galactiminer is a far too ambitious game for us to realistically accomplish right now. That's not to say it's impossible, but for our relatively small and unknown team, it may as well be. Creating a game engine is also ambitious, yes, but it's not hinging on technology that barely exists. It's not dead, but it's going to remain on hold until we can do it right. Until then, we're gonna keep working on Project: Infinity and deliver on the promise we made all those years ago. If you want to join the Project: Infinity team, head here. If you want to join the Blamite Game Engine team, head here. If you want to hop on our Discord, check it out here.
  16. haloman30

    Eon Game Engine

    Meant to be reliable and fast, Eon is made to be easy to use and very simple. Eon has the power to produce very large games and is in no way meant to limit game creativity and size. It's simple which means easy to change and very adaptable. It's geared towards 2d game development and comes with all the features necessary to make awesome 2D games. Eon is made with C++ and SFML (Simple Fast Multimedia Layer) which is a widely used and popular graphics library for C++. This means that there are plenty of tutorials and resources available to learn SFML. Making Eon a good choice for any beginners or experts next project. So check it out, see what's possible when you have Eon in your toolbox!
  17. + Added menu bar for easier navigation and control + Redesigned about box + Added new Settings window to replace the old Settings flyout + Added new splash screen * Moved a ton of startup events into the splash screen loader, instead of the main application window itself * Configuration is no longer used by continuously re-reading the file, but now has several classes (NTConfigOption, NTConfigFile) * Globals is now a static class (rather than declaring 41 different instances of globals) * Changelog now relies on an online json file (tied to this new changelog system!) rather than having version changelogs hard-coded into the program * Changelog versions are now stored in special classes (NTVersion, NTVersionNuPkg, NTRemoteVersion) * Refactoring for changelog UI controls * Scrollbars will now show up for version Changelog and NuGet packages * Most user-end text is now stored in a String table, rather than being placed within each file individually * User profile menu now uses a standard context menu instead of the fake dropdown * Reworked how the latest News & Announcements are retrieved * Changed most functions that utilized the old message box to use the new design * Moved all logging-related functions to the NTLogger class * Moved all telemetry-related functions to the NTTelemetry class - Disabled Play button functionality for old "predev" launcher UI
  18. + Experimental support for user-defined color schemes + Added checkboxes to enable Snapshots, Beta versions, and Alpha versions of Project: Infinity * Replaced the spam of "Repeated" 'Done' messages in console with more detailed information * Improved spacing within Blamite Map Manager - Removed 'Players First.' button from Legal Documents flyout, as the page is hidden from the public (for now, kinda cringe for my liking)
  19. + Officially introduced telemetry system (user can disable in settings) + Added the Blamite Map Manager (BETA) + Added a 'First Run' dialog, which now provides a very clear option to disable telemetry right out of the gate, as well as forces agreement to all the needed legal documents * Launcher message dialog contents now supports scrolling for longer messages - just in case. * Internal fix: much more flexible and reliable way to write config values * Config button in Console flyout now opens the Settings flyout instead of the old config window (you can still use old broken window via commands though, if you REALLY want to) * Fixed all the 'Done' messages in the log to now display the actual information - which was the loading of RSS items from the Elaztek website
  20. + Fully redesigned UI + Added a redeem key page (wip) + Added login page (wip) + Added user dropdown menu, chat, friends, and something else in window title + Added new config option: Telemetry logging level + Implemented new system logging levels: None, Basic, Full. These levels display various levels of system software and hardware information in log files at startup. Default setting is BASIC, because we aren't Microsoft and this isn't Windows 10. More information on what exactly is collected can be found at: http://elaztek.com/products/launcher/launcher_telemetry + Added new config option: Allow maximize/restore + Added new config option: Allow free resizing * Console now has scrollbars, and no longer has text wrapping * Updated MahApps.Metro to 1.5.0 * Assembly renamed from launcher-wpf to NTlauncher * The old config window is officially deprecated. All updates have been placed into the new integrated page.
  21. + Embedded all UI fonts into the application to fix font problems + Developer features can be accessed via a hidden config option + Clicking an announcement on the frontpage will open the topic in the default web browser + Added scrollbars to all tile lists + Added work-in-progress configurator for the Blamite Game Engine + Added new main screen + Project: Infinity downlaod button now displays a message + Added Infinity game options + Added new exit confirmation dialog * Fixed News & Updates title displaying * Fixed some layout issues with tiles on Infinity game tab (developer only) * Fixed layout issues with info panes in specific game tabs * Marked changelog UI as depreceated * Config values are loaded in a more flexible fashion (needs further testing) * .CNR files are now no longer supported * Migrated to JSON for version downloading/handling * Logging system migrated from junky textbox text appending to proper console binding
  22. * Made certain features hidden unless devmode is enabled * Got basic functionality working with .CNR (Cached Network Resource) files
  23. * Added icon to title bar * Disabled all-caps title + Added experimental Appx/UWP inspired msghandler dialog (see Developer flyout)
  24. [HUGE MIGRATION TO WPF] + Added new experimental features in Project: Infinity tab +Added new themes added by MahApps.Metro * Ported core application to WPF, some windows continue to utilize Windows Forms (and WPF may be discontinued in favor of Forms * Configuration is now integrated into the main window * Developer Tab removed at runtime, can be accessed in developer versions from the title bar * Dark theme is now the default selection - Removed a few themes only applicable to MetroFramework - Removed Launcher Output tab, can be accessed in the main window via the title bar - Removed ability to maximize (because WPF is retarded >_
  25. + Added WIP advanced configuration + Added experimental induivudal game tab layout + Added icon to main window