• Helpcenter

    Contains various help topics for Elaztek Studios.
    Switch to Classic View
    Show all categories

    Tutorials and Guides

    Need help or guidance on how to do something? Try checking here first!

    Blamite Game Engine

    View available guides for the Blamite Game Engine.

    Website and Forums

    View available guides for using our website and forums.

    Miscellaneous

    View available guides for some of our other services.


    Resources

    A collection of resources providing help and information on a variety of topics.

    Guidelines

    View various rules, guidelines, and other policies. You know, boring (but important) legal stuff.

    Troubleshooting

    Running into an issue with one of our services? Be sure to check here before submitting a bug report.

    History

    Various resources detailing or cataloguing Chaotic United's history and/or legacy web content.

    Blamite Game Engine

    A collection of resources containing information about the Blamite Game Engine.

    Website and Forums

    A collection of resources containing information about our website and forums.


    Can't find what you're looking for?

    Try asking in our support forum

    Found an issue somewhere?

    Report it on our bug tracker

    Recent Articles

    Forum Ranks

    In Website and Forums,

    What are Ranks?
    The Elaztek Studios website has a series of ranks you can unlock through participating in various ways in our community. Some great ways to rank up include:
    Creating new content, including forum topics, forum posts, comments, files, blog posts, and so on Receiving positive reactions on content  
    Be wary, though - receiving negative ratings or having content deleted or hidden may cause you to lose points.
     
    What do these ranks do?
    Currently, they're just for bragging rights. However, in the future we'd like to offer more tangible rewards (both on the website and within our various games) as a reward for participating.
     
    What ranks are available?
    The full list of ranks, their badges, and the amount of points required to reach each one is detailed in the table just below.
    Rank Changes as of 6/4/2023
    On June 4th, 2023, we significantly overhauled our ranking system, as well as made changes to display ranks more prominently. Previously, the only ranks available were Newbie, Member, and Advanced Member. These ranks were renamed to Recruit, Private, and Corporal respectively, in order to match the new military-inspired rank system. They were also given updated badges from the default badge used before - however, they are otherwise unchanged and have identical unlock requirements.
     
     
    Emblem Title Points Points from Previous Recruit
    (formerly Newbie) 0 + 0 Private
    (formerly Member) 10 + 10 Corporal
    (formerly Advanced Member) 30 + 20 Sergeant 60 + 30 Master Sergeant 100 + 40 Warrant Officer 150 + 50 First Lieutenant 250 + 100 Captain 400 + 150 Lt. Colonel 600 + 200 Colonel 800 + 200 Brigadier 1000 + 200 Major 1250 + 250 General 1500 + 250 Lt. Commander 1750 + 250 Commander 2000 + 250 Vice Admiral 2300 + 300 Admiral 2700 + 400 Field Marshall 3500 + 800 Hero 4500 + 1000 Legend 6000 + 1500 Mythic 7777 + 1777  
    Last Updated: 6/3/2023 at 11:29 AM CST
     
    This page outlines a series of guidelines that apply to any and all team members working on one or more of our games, or game-related projects. It does NOT, however, apply to those working on the following projects, and team members working on these projects are subject to their own, separate guidelines:
    DonationStore  
    INTERNAL CONTENT AND NON-DISCLOSURE AGREEMENT
    We don't want our internal content being discussed or leaked. Most of our game content is generally considered confidential. However, we don't think it's fair to permanently prohibit discussion or showcase of this content forever, either. Some folks often really get excited to see what our games look like during the development process, and like seeing the game transition into what they ultimately get their hands on. In a lot of cases, we'll make much of this public to begin with - however, in rare cases that we don't, the following guidelines cover how that content is to be handled - along with general information for how content is handled overall:
     
    All content not visible on the public end of the website should be treated as if it were under Non-Disclosure Agreement (NDA). Posting images, descriptions, videos, or any other content revealing the content under implied or true NDA will result in termination from the team, and in some cases, could result in legal action being taken All modifications of official source code, game assets, textures, sound effects, and any other content used within Elaztek's website, games, software, or any other product/service should be documented and approved by each project's respective leader Any and all source code within private Elaztek repositories, on either our own Gitlab, Github, or any other service or site where our source code is stored, is under a non-disclosure agreement. Releasing any part of this source code in the form of text, screenshots, videos, audio, or any other means will be seen as a violation of the NDA and will result in your immediate termination from the team and potential legal action Certain aspects of projects may be freely discussed and considered to no longer be under an NDA, under the following circumstances: Screenshots, videos, audio, and other content that does NOT include game assets or source code, may be revealed and game details may be freely discussed by FORMER TEAM MEMBERS if one of the following criteria are met: The project has been unannounced to the public for more than 5 years from the time of the project's inception The project has had no future communications, blog posts, or other information for more than 5 years from the last communication about the project The project has been formally announced as cancelled, and is marked as "Cancelled" in the Project History page within the About Us section (this does NOT apply to projects marked as on "Indefinite Hold") The project has been formally sunset and is no longer receiving future updates The content is already included in a publicly-accessible alpha, beta, or other pre-release build Express, written permission has been obtained to discuss the content in question from the company owner or project lead Screenshots, videos, audio, and other content that does NOT include game assets or source code, may be revealed and game details may be freely discussed by CURRENT TEAM MEMBERS if one of the following criteria are met: The project has had no internal development for more than 3 years, and there are no active plans to continue development The project has been formally announced as cancelled, and is marked as "Cancelled" in the Project History page within the About Us section (this does NOT apply to projects marked as on "Indefinite Hold") The project has been formally sunset and is no longer receiving future updates The content is specifically part of alpha, beta, or other pre-release content and all content shown is either: Already included in its final form within the final game Is not intended to be reused in future updates or DLC The content is already included in a publicly-accessible alpha, beta, or other pre-release build Express, written permission has been obtained to discuss the content in question from the company owner or project lead Game content, including source code, assets, and other content may be freely released and discussed ONLY if the following criteria are met: The project is formally cancelled The project's source code and assets are not being reused in other projects (ex, the Blamite Game Engine's source code would not be able to be released to the public, however game scripts that are only applicable to a specific project would likely be allowed to be released) There are no significant security risks that would be opened up as a result of content being released to the public There are no personal details or other sensitive information included within the content Express, written permission from the company owner is given  
    PUBLIC RELATIONS
    We want to encourage open and free discussion between both members of the community, as well as between the community and our team. In order to help maintain this communication and avoid things breaking down into angry shouting matches, we've got a few guidelines on how community communications are to be handled:
     
    All interactions with the community should be handled with care and a basic level of maturity should be demonstrated. Acting in an immature manner could result in you being terminated from the team In the case of a large amount of community backlash or outrage, the following actions should be taken: Contact an administrator or the company Owner immediately Do what you can to keep discussion calm, though we recognize that in some cases this may not be effective or possible Do your best to maintain communication, though we understand that in the case of large events, this may not be feasible If discussion reaches a point where it becomes hostile and overly heated, and users refuse to disengage and/or behave more respectfully, temporary muting of hostile users is considered appropriate Avoid flaming, insulting, attacking, or harassing users during such an event. If you feel that you yourself are too stressed to deal with the situation, it is best to take a step back and disengage at that time All other community guidelines should be followed at all times  
    BEHAVIOR INSIDE & OUTSIDE OF ELAZTEK STUDIOS
    For the most part, we only really care about users behavior inside Elaztek Studios. Unless you're going out of your way to be a horrible person - we don't care one way or the other what you post in your free time. We believe that our team members should have the right to post what they choose on social media, and not have to worry about censoring themselves in order to "represent the business better" or anything like that. However, we do have a few guidelines on how you should behave inside Elaztek Studios, and things that we consider severe enough to take action on if it happens outside of Elaztek Studios, all of which are outlined below:
     
    The following behaviors inside OR outside of Elaztek Studios are considered a violation and may result in termination: Performing or encouraging any illegal activities Cyberbullying, harassement, flaming, or otherwise attacking one or more people Doxing or otherwise leaking personal information of one or more people Threatening violence against one or more people in a manner that is clearly not intended as a joke or sarcasm Repeated instances of clear and obvious racist or sexist behavior that is clearly not intended as a joke or sarcasm The following are examples of content that would NOT be considered a violation: Strong controversial political opinions, regardless of political leaning Controversial posts or "hot takes" Controversial posts that are accused of inciting violence, but that we deem are not doing so Posting negative opinions on any of Elaztek Studios' projects, provided that no content or personal details are being leaked  
    MONETIZATION
    Most games developed under Elaztek Studios will have some form of monetization - after all, the bills don't pay themselves. That being said, we do strive to ensure that monetization within our games is as far from predatory and exploitative as possible. We don't like FOMO (Fear Of Missing Out) tactics, we don't like forcing players to spend money as the only way to get that cool helmet, and we especially don't like retroactively taking stuff people paid for out and making it impossible to use or obtain in the future. As such, the following guidelines describe how monetization may be implemented into any game developed by Elaztek Studios:
     
    Game design and monetization should, generally, not seek to exploit the consumer or player (certain exceptions can be made in special circumstances, see below). Examples of what we consider to be exploitative monetization include, but are not limited to: Gameplay altering microtransactions in a non-free game or product, where certain aspects of gameplay are locked behind a paywall Pay-to-Win mechanics in a non-free game or product, where a player is encouraged or pressured into paying for additional benefits in order to gain a competitive advantage Lootboxes or other related RNG-driven reward systems, when combined with the ability to purchase lootboxes either directly or indirectly Any other similar tactics that are used as part of generating revenue and are not part of the genuine creative vision of Elaztek Studios Microtransactions are generally permitted (provided they do not violate any other guidelines in this section), however there are several additional guidelines that apply to all types of microtransactions, cosmetic or otherwise: Individual microtransactions (single items, not a group of items) should not exceed $10 USD in any circumstance, and "bundles" of multiple items should not exceed $20 USD All microtransactions should have some mechanism for obtaining without requiring that the player spends real-world money. This can be achieved by having specific unlock criteria on a per-item basis, or by having microtransactions be purchasable using an in-game currency An in-game virtual currency system is permitted, however it must also meet the following guidelines:  In-game currency packs can be sold at any amount, including discount bundles All items which can be obtained with a virtual currency must also be able to purchased directly, without requiring the use of the virtual currency In the case of a technical reason why items could not be easily purchased directly, then an option to purchase an exact amount of in-game currency in order to obtain the item should be made available Players must not be forced, under any circumstance, to purchase an excess of virtual currency in order to obtain an item Microtransactions that are described as "exploitative" (see point 1) may be permitted ONLY under the following circumstances, as long as they meet all other criteria described in this section: The game or product that they are implemented in is a free-to-play title, with no other financially feasible means of generating revenue The specific implementation is approved in writing by the company owner Expansions, DLC (Downloadable Content), and other forms of paid addon content (referred to henceforth as simply 'DLC') is permitted, as long as the following criteria are met: The DLC is not retroactively prepared prior to launch and composed of already completed content previously intended to be part of the base game Assets that are used purely for DLC content must not be included in the base title, and should be included as part of the DLC package instead. In other words, players disk space should not be consumed with content that they have not purchased This rule can be waived by the company owner in special circumstances where technical limitations may require this, however this should be a last-resort, and this should be remedied in a future title or through an update This rule does not apply to cases where base assets that are present within the base game are reused within DLC, and only applies to newly introduced assets that are only used within the specific DLC in question DLC content should not at any point be removed from the game, and should remain purchasable and playable indefinitely If keeping a DLC item purchasable were to ever become infeasible for any reason, the DLC should be fully included in the base game or otherwise made available free of charge to all players The Battle Pass monetization model or other similar microtransaction models are permitted as long as the following criteria are met: Previous seasons must remain purchasable and must be able to be completed at any point in the future, even after the release of newer seasons. This applies to both paid and free items within a season Paid seasonal content (often referred to as a "Premium" Battle Pass) should have a mechanism of unlock that does not require the use of real-world money All other guidelines within this section are met, as applicable Existing projects which were compliant with these guidelines at the time of release, but became non-compliant through a future revision of the guidelines, are not obligated to adhere to the new guidelines UNLESS one of the following criteria are met: The game is a "live-service" title and/or is intended to receive future updates for more than 1 year after the point where these guidelines were revised The company owner makes an explicit order for a project to be updated to become compliant Projects will have 6 months from the time of the guidelines being revised to become compliant, however time extensions may be given as necessary Projects may have one or more of the above guidelines waived only with written and express permission from the company owner  
    TITLE UPDATES/LIVE SERVICE TITLES
    In some cases, we'll release updates and patches for our games after their initial launch. Sometimes, these are nothing more than some bugfixes. Other times, however, updates may be used to introduce new content. These are commonly known as "live service" titles. However, in order to avoid some of the pitfalls and negative associations that come with live service games, we have some guidelines in place for how these updates are to be handled.
     
    Updates generally should not remove or permanently lock content from the base game. This may be permitted in rare circumstances, with approval from studio administration Updates may not be used as a means to complete base game features. If a title is likely to not have sufficient content by its release date, then the title should be delayed - as while delays are not ideal and can lead to disappointment, releasing a half-baked experience is often significantly worse Features that are finalized or nearly finalized prior to release cannot be retroactively removed and locked behind a future game update  
    TEAM SIDE PROJECTS
    In some instances, team members are permitted to initiate development of side projects under the Elaztek Studios name. Generally, these take the form as side projects that either a single or a small group of people. Note that these side projects are projects that are worked on during "company time", and take the place of a small period of time that would have otherwise been allocated to other official projects. They do NOT refer to projects that team members develop outside of work hours. If these projects are seen as having a good potential for success, they may be granted further attention and resources from Elaztek Studios. No matter the case, all of these side projects are subject to the following guidelines:
     
    All side projects (including the content created for them, such as source code, game assets, etc) are recognized as being property of Elaztek Studios, and not under the ownership of the team members who create them, unless otherwise stated by the company owner Elaztek Studios reserves the right to continue development of previously cancelled side projects at any point in the future All side projects must be stored within the Elaztek Gitlab or another Elaztek-operated service Team members working on side projects, unless otherwise specified, are not entitled to any permanent/ongoing royalties from the side project should be completed and released All side projects are to be released under the Elaztek Studios name, and treated as a standard Elaztek Studios project  
    TERMINATION
    It sucks, but sometimes we have to let people go from our team. While we generally try to avoid this as much as possible, there are certain scenarios where we have no choice. Note that the following section applies ONLY to volunteer team members, and may not necessarily apply to paid employees. The common conditions for this, as well as the protections for team members are described below:
     
    Elaztek Studios reserves the right to remove any team member, for any reason. The most common reasons include, but are not limited to: Failure to abide by the guidelines outlined in this document Being inactive (ie, not communicating with team members and/or not making any contributions to projects) for an extended period of time, without prior notice Any other reason deemed severe enough to warrant a removal from the team Conspiring to get another team member terminated without valid reason may result in your termination from the team Upon termination, you will lose the following: Immediate removal of website rank and Discord role Immediate removal of access to internal systems (Jenkins, private Gitlab repositories, Stratagem, Team Hub, Ivory Tower, Sentry) Immediate removal of access to internal communication channels (Nextcloud, Mattermost, staff-only Discord channels, staff-only subforums) If you commute on-location, you will have 14 days to collect any personal belongings. This may be extended at a manager's discretion. After this time, your keycard will no longer be valid and you will no longer be able to enter the building. If you have forgotten or lost any personal belongings, please contact a manager or other member of the team Elaztek is not required to disclose the reasoning for any termination (but we usually will, and usually you will know in the first place) You may not be terminated for race, religion, personal beliefs, gender, sexual orientation, or other discriminatory reason Except in extreme cases (such as clear threats of violence or otherwise), team members may not be terminated for any content made on personal social media profiles Some things that we DO consider significant enough for termination: Continued, repeated harassment of one or more individuals Threats of violence in a manner that is clearly not intended to be a joke of some sort Repeated instances of clear and obvious racist or sexist behavior Some things that we DO NOT consider significant enough for termination: Strong controversial political opinions, regardless of political leaning Controversial posts or "hot takes" Controversial posts that are accused of inciting violence, but that we deem are not doing so Posting negative opinions on any of Elaztek Studios' projects, provided that no content is being leaked  
    RESERVATION OF RIGHTS
    Elaztek Studios reserves the right to modify, add to, remove from, or otherwise alter these terms, with sufficient notice. If you disagree with any changes made to these terms, you may contact a manager for questions or concerns. If you ultimately do not agree to the terms, you may no longer be permitted to continue working on Elaztek Studios projects.
     
    QUESTIONS
    If you have any questions on any of the above guidelines and/or feel that you need additional clarification, feel free to reach out to a manager or the Owner.
    Last Updated: 6/1/2023 at 6:57 AM CST
     
    Considering applying to a volunteer or paid position here at Elaztek Studios? Awesome! We're always looking for new folks to join the team! Before you do, however, we encourage you to have a look over this page to get a sense of what we expect from our team members.
     
    But first, a quick overview of the differences between our volunteer and paid team positions.
     
    Volunteer Positions
    These positions are where most of our work happens currently, since none of our projects are at any point of generating profit, and since we're really just a group of people working on stuff we find fun and exciting.
     
    These positions generally have quite lax requirements on time and work invested, with no fixed quotas that must be met in either case. We typically just ask that you do something when you can, and let us know if you won't be able to for an extended period.
     
    Paid Positions
    Currently, we don't really have many (if any) of these - as currently, we don't really have any real funding coming in, from products or otherwise. In the future, however, we'd like for this to become the primary way we bring folks aboard.
     
    These positions generally do come with slightly stricter expectations of time and work invested - but of course, you'll be getting paid in return for your contributions. At this early stage, most positions will be contract-based positions, and will likely not be the type of thing that you could live on alone (and as such, we won't ask for full-time hours either).
     
    For all of our paid positions, the typical pay for the position will always be listed within the Job Portal. We won't ever hide that information from you, because after all, that's likely one of the most important things you'd want to know, right?
     
    General Team Member Expectations
    This is stuff we expect from all of our team members - volunteer or otherwise.
     
    Communication
    One of the most important parts of being part of our team, besides contributing to our projects, is maintaining communication with the rest of our team. Most often, this will take place on our Discord server. In rare circumstances, however, you may be asked to communicate via Mattermost or Nextcloud, as these allow for on-premises chat communication, and are preferable when discussing particularly confidential topics.
     
    Primarily, however, we simply ask and expect that you maintain semi-regular communication with the team - and would prefer if you didn't drop off the face of the earth for weeks at a time. Don't worry though, you won't be forced to get into constant weekly meetings - after all, some things are better off as an email (or an instant message).
     
    Time Off
    For all of our positions, we do not have any fixed limit on the number of days that can be taken off. All time off is currently unpaid (for now), but you can have as much of it as you want (within reason). If there's an emergency within your family, if you've got a vacation planned, if you're busy with school or other obligations, or if you just need some time to step back for a little bit - we're happy to accomodate. Currently, no special action is required besides just informing a manager or administrator beforehand - just so that we know that you'll be gone for a bit, and we aren't sat wondering why you haven't been responding to messages.
     
    Volunteer-Specific Expectations
    These are the expectations we have for our volunteer team members.
     
    Time Investments
    For all of our volunteer positions, we do not have any fixed amounts of time that are required to be invested in any project. Your invested hours do not have to be tracked (though if you'd like to for personal reasons, go nuts), and you're free to generally do as much or as little as you like. We do ask that you make some amount of regular contributions, even if small. We primarily don't want to have you be gone and not have any progress made for months on end.
     
    If you need to be absent for a long period of time, however, you'll just need to let us know beforehand - you won't be told no, and we'll still keep your seat warm for you. If you do end up stopping any and all progress for an extended period of time without notice, you could risk losing your position - though we'll usually try to reach out several times beforehand.
     
     
    Employee-Specific Expectations
    This is what we expect from our employees, contractors, or other financially compensated team members.
     
    Time Investments
    For paid positions, we do have varying amounts of required time investments. You'll also be expected to clock in and clock out using an online page. Since most paid positions are intended to be side-gigs and not the type of things you fully pay your bills on (believe us, we'd love to be able to - but we just aren't there yet), hourly requirements are generally quite small (often well under 10 hours a week), though this may vary by position. For the standard compensation and hourly requirements, you'll want to check the job details on the Job Portal.
     
    Many of our games are built from the ground up with mods and user-generated content in mind. The Blamite Game Engine itself is even designed around it. In addition to the engine having mod support built-in, we also offer a one-stop shop for mods and user content - accessible both within the website, as well as being able to manage, install, remove, and customize mods directly in each of our games.
     
    Before creating and submitting any content to our Download Center, ensure you read over the following guidelines:
    General Guidelines
    Content must not contain malware, viruses, telemetry, spyware, etc. - Content containing anything that may harm or give the user content they may not want, such as viruses, malware, spyware, ransomware, adware, telemetry, tracking, etc. will not be allowed and your access to the download center will be permanently revoked. Cheats and hacks will not be permitted - Content that contains cheats, hacks, aimbots, etc. will not be allowed and your file will be rejected. Content should be thoroughly tested - Bugs happen, we know that. No software is free of error. If your content is found to have damaging effects to gamesaves or cause other irreversible effects, your content will be displayed with a warning informing users of this fact until you are able to fix it. No racism/hate speech - Content that contains racism, in that  the content supports racist activities, will be rejected. If your content is centered around racism as political/social commentary, and is against racism in this portrayal, then your content will not be rejected (atleast not for this reason). Essentially, if your content supports racism, it will be rejected. No harassment/bullying - Content that is created as harassment towards Elaztek, its team, members of its community, or anyone else will be rejected. As with racism/hate speech, if your content makes commentary on this issue, it is permitted. It's when your content supports these actions that it becomes a problem. Rules on NSFW Content - Content which contains mild adult themes are perfectly fine and (usually) won't be subject to any restrictions. If your content contains any strong adult themes, your content will require additional age verification from users to be downloaded. Content that contains illegal materials (ie, pedophilia) will not be permitted. Your content must not contain stolen, ripped, or pirated assets - If your content contains assets that are not your own, is not public domain, and/or you do not have rights to use, it will be rejected. We reserve the right to include your ideas, characters, concepts, and software created for our future or current projects - Elaztek Studios was born out of community passion for a larger franchise, and in staying true to being community-focused and driven, we like to incorporate community ideas here and there into our games, whether they be in the form of technical improvements, storylines, characters, and so on. Should your content or ideas ever directly influence or find their way into any official projects, you will not go uncredited. We will do our best to reach out to you and give you a chance to have your full name provided for proper credit. If we are unable to contact you, your display name on the website will be used instead.  
    Adult/NSFW Content
    Adult content featuring nudity and other such things are generally considered acceptable, though are subject to a couple other minor guidelines:
     
    Content which contains mild adult themes (and NO nudity) will be available as normal content. Content which contains nudity or strong adult themes will only be available to users who are 18 years of age or older, but is subject to no other restrictions and is permitted. Content which contains adult themes which are considered illegal (ie, non-consensual sexual behavior, sexual content depicting minors, etc) will not be permitted under any circumstance, and will likely result in a permanent account suspension.  
    Custom Tools and Applications
    Tools which enable online cheating are not allowed - Any tools which enable cheating or hacking in an online setting will not be allowed. Cheats which made available purely for offline or custom games are allowed, as cheating in these areas doesn't cause harm to other players. Tools which involve hacking and malware will not be permitted under any circumstance however. The application source must be provided either to Elaztek Studios, or the tool must be made open-source - We cannot under any circumstance allow malicious software onto our download center. The only way to guarantee this, unfortunately, is that we must have access to the source code of your tool. This includes any future updates to the tool. Only the Owner and Administrators will have access to this code if you choose to keep it closed-source, and we will never use your code for any purpose other than reviewing to ensure that the software is safe to use unless you grant us explicit, written permission. You may alternatively have your project open source on the Elaztek Gitlab, Github, or any other similar website instead.  
    If you are a mod author and are unsure if your content is permitted, just ask! You can message any of our staff on the website or Discord, or create a support ticket. More often than not, it'll be safe to upload - but if you feel your content is teetering on the edge - it's better safe than sorry.
    Excluding cases where uploaded content violates our submission guidelines or is otherwise deemed unacceptable within the Download Center, user-submitted content cannot and will not be removed later. In order to ensure that any mods which depend on other content remains playable, and to ensure that users can continue enjoying user-created content, we require that any submitted files are permanently available. This includes previous versions of files as well as the entirety of the file itself.
     
    You may be wondering - why? Shouldn't the mod author be able to dictate what to do with their own content?
     
    There have been cases where mods for other games on other platforms have been taken down by the author for various reasons - and as such, users must either seek out old downloads that other community members had lying around, or simply be unable to use their favorite mod anymore. Among other things, Elaztek Studios believes in preservation of content of all sorts. We believe that users should never be locked out of things they enjoy, or forced into a different user experience for no good reason. And while we do generally wish to place as much control as possible into the hands of the user, this is a special case where allowing mod authors to remove their own content is far more damaging than restricting this ability.
     
    You don't have to continuously support or update your mods as an author - that's not what we're saying. You're entirely free to add a note to your file stating that you are no longer updating the content. However - we believe that people should still be able to use that old, unsupported version of the content - after all, there's nothing stopping them from just using an older build of the game, so there's not much to stop them.
     
    The tl;dr - once your content is submitted, there's no take-backs. Once it's shared, its shared - and unless we end up removing it ourselves due to violating one of our guidelines, it can't be taken back offline later.

    Archived Pages Index

    In History,

    A list of any archived webpages from the website.
    Here, you can find a list of any old pages which have been replaced, removed, or are otherwise no longer being updated.
     
    It is entirely possible that these links will break over time. If any of the links below fail to work for any reason, you are encouraged to submit a bug report. Chances are, the page still exists somewhere - we just moved it during some mass organization effort.
     
    Please keep in mind that these pages are NOT being updated. Many of them WILL contain outdated or inaccurate information. They were removed/replaced for a reason.
     
    Homepages
    Initial Temporary Homepage (v0): https://elaztek.com/legacy/index-v0.html/ Homepage v1: https://elaztek.com/legacy/index-v2.html/ Homepage v2: https://elaztek.com/legacy/home_2019/ Homepage v3: https://elaztek.com/legacy/index.html/  
    Error Pages
    404: https://elaztek.com/legacy/404_legacy/ 404 (Alternate, never finished): https://elaztek.com/error_pages/404/ Soon™: https://elaztek.com/error_pages/soon/  
    Policies and Documents
    Community Guidelines: https://elaztek.com/legacy/community-guidelines/ Raven Runner Privacy Policy: https://elaztek.com/legacy/rr_privacy/ Raven Runner Terms of Service: https://elaztek.com/legacy/rr_tos/ File Submission Guidelines: https://elaztek.com/legacy/submission-rules/ Rank Information: https://elaztek.com/legacy/rankinfo/  
    Informational Pages
    About Elaztek Studios: https://elaztek.com/legacy/about-us/ Early About Section About Elaztek: https://elaztek.com/legacy/about/about_elaztek/ Careers: https://elaztek.com/legacy/about/careers/ Game History: https://elaztek.com/legacy/about/game_history/ Publications: https://elaztek.com/legacy/about/publications/ Style Guide: https://elaztek.com/legacy/about/style_guide/ About Section v2 (Retired in 2023) About: https://elaztek.com/legacy/about_v2/index/ Our Vision: https://elaztek.com/legacy/about_v2/vision/ Projects: https://elaztek.com/legacy/about_v2/projects/ Legacy Projects: https://elaztek.com/legacy/about_v2/projects_legacy/ History: https://elaztek.com/legacy/about_v2/history/ Company Pages Projects: https://elaztek.com/legacy/elaztek/projects/ Redeem Code: https://elaztek.com/legacy/elaztek/redeem/ Trademarks: https://elaztek.com/legacy/elaztek/trademarks/  
    Games and Projects
    Project: Infinity Nameplates: https://elaztek.com/legacy/infinity/nameplates/ Elaztek Launcher Data Collection & Logging: https://elaztek.com/legacy/products/launcher/launcher_telemetry/ Blamite Game Engine Material Website Homepage: https://elaztek.com/projects/blamite/blamite_legacy/index.html/ Homepage (weird business license page thing): https://elaztek.com/projects/blamite/blamite_legacy/index-business-unused.html/ Team Application: https://elaztek.com/projects/blamite/blamite_legacy/team-join/ Version History: https://elaztek.com/projects/blamite/blamite_legacy/versions/ About/Overview: https://elaztek.com/projects/blamite/blamite_legacy/about/overview/ 2021 Website Recent Commits: https://elaztek.com/projects/blamite/commits_v1/ Homepage (v1): https://elaztek.com/projects/blamite/index_v1/  
    Databases
    Helpcenter Under Maintenance Page: https://elaztek.com/legacy/helpcenter_ve/ Old Wrapper (now empty, made using Visual Editor): https://elaztek.com/legacy/helpcenter_new_ve/ Old Wrapper (now empty, has sidebar): https://elaztek.com/legacy/helpcenter/ Product DB Product Page Test: https://elaztek.com/legacy/products/generic/ Product List Test: https://elaztek.com/legacy/products/generic_list/ Product DB: https://elaztek.com/legacy/products/pdb/  
    Forms
    Blamite Team Application: https://elaztek.com/legacy/team-join-blamite/ Application Portal: https://elaztek.com/legacy/team-join-hub/ Project: Infinity Team Application: https://elaztek.com/legacy/team-join/  
    Miscellaneous Pages
    Official Downloads: https://elaztek.com/legacy/official_downloads/ Chaotic United Landing Page: https://elaztek.com/legacy/cu_landing/ Game History: https://elaztek.com/legacy/game_history/  
    Test Pages
    404 Random Phrase JS Test: https://elaztek.com/legacy/test/404_jstest.html/ Answers DB (broken): https://elaztek.com/legacy/test/answers/ Articles (default with Pages/IP.Content): https://elaztek.com/legacy/test/articles.html/ IP.Chat Unavailable Page: https://elaztek.com/legacy/test/ipc-err/ IP.Chat Test Page: https://elaztek.com/legacy/test/ipc-test/ Music Test: https://elaztek.com/legacy/test/musictest/ Release Notes: https://elaztek.com/legacy/test/release-notes/ UI Demo: https://elaztek.com/legacy/test/ui_demo/  
    Data Files
    Launcher (NTClient) Changelog (ntclient_versions.json): https://elaztek.com/external/launcher_helpers/ntclient_versions.json Latest News Post Data (update.html): https://elaztek.com/external/launcher_helpers/update.html Foundation Mod Manager Source Info (fmm_src_info.json): https://elaztek.com/external/platform_data/fmm_src_info.json Mod List (mods.json): https://elaztek.com/external/platform_data/mods.json  
    Forum Archives: https://elaztek.com/forums/forum/63-archive/
    This page is incomplete and not yet being enforced. As such, the policies outlined below are not yet in effect.
     
    In the interest of ensuring that users that enjoy our games can keep doing so tomorrow, next year, and decades from now, the following policy has been put in place and is effective for the duration of the lifetime of Elaztek Studios.
     
    Last modified: 1/20/2021
     
    The TL;DR (for your everyday joe):
     
    Any official downloads should always be available. Users should always be able to choose what version of our games they play. They should always be able to tinker with them, create content for them, and modify them to their heart's content.
     
    If we decide that we want to move forward and leave a previous project behind, we must honor that project's legacy and history. Any downloads made for it must remain available, users must be able to keep submitting new content, and if the game requires online servers to function, those servers should be placed into the hands of the community to keep them going in our place.
     
    In the event that we are no longer able to do business (and we can't just revert to being a hobbyist group), everything we've ever made should be released to the public. If we cannot continue operation, we must take all steps possible to ensure that our work and legacy don't die with us - to ensure that the community can, if desired, carry the torch forward.
     
    Preserving the past is a key part of what we do, it's been a key part of the operation of Chaotic United for many years, and too many other studios neglect to maintain their legacy projects - eventually resulting in them fading away to time. We aren't about that.
     
    If you're just a member of the community scrolling by - hey there. Make sure you hold us accountable if we ever steer too far from these guidelines.
     
    If you're part of the company, the full detailed policy can be found below.
     
    The Nitty-Gritty (required reading for team members and applicants):
     
    Dedicated Multiplayer Servers
    Whenever possible, any games which contain a multiplayer component should include (either with the game content or as a free download on the website) user-operated dedicated server software. This software should be able to be used by any user to host a 24/7 private server. Whenever possible, any games which contain a multiplayer component should include a Server Browser, which allows the user to browse through these self-hosted servers. User-hosted servers shall not be blacklisted or removed from the server list, excluding only cases where the server host is in direct violation with any of our policies or any licenses that are part of the game (ie, the game's EULA). The user should be able to, at any time, download outdated server versions for use with outdated game clients.  
    Post-Launch Updates and Patches
    Post launch updates should be offered through the game client and/or launcher, as well as a separate download on the website if possible. The user should be able to, at any time, choose to remove these patches or install an outdated game version. Outdated game versions should be blocked from public matchmaking, but should be allowed to connect to community-hosted servers of the equivalent version. Updates should, whenever possible, be minimal in filesize and be able to be applied as a patch on top of the previous game version.  
    User Generated Content
    User submitted content must remain available, even if their account becomes suspended. Only user content which itself violates policy can be removed. Removed content should remain accessible to company and site administrators for potential future review and restoration if desired. In the event of user content removal, the user must be allowed to submit an appeal and have the appeal heard and considered.  
    End-of-Life/End-of-Support
    All game or engine downloads must remain available for download. This includes the Blamite Editing Kit, patch/version history, server software, and any other software needed to play and create content for the game. All existing game or engine licenses should be honored indefinitely, or all downloads must become free to all registered users on the Elaztek Studios website. Any user content submitted that depends on a specific game or engine version must remain available for download, and new content must be able to be submitted. In the event of a version of Blamite reaching end-of-life: All engine documentation must remain available. At minimum, a download archive of the documentation must be available. Alternatively, a download can be omitted if Elaztek-hosted documentation remains online. In the event that Elaztek-hosted documentation becomes broken, unusable, or goes offline, a complete offline download must be made available.  
    Online-Only Services
    Games which cannot operate without a connection to an online server should be avoided whenever possible. The following guidelines exist in the event that a creative vision requires the presence of an online-only component. No game content should be retroactively locked after its release. In the event that a game's content demands become too great, all possible efforts should be first made to remedy these technical burdens without removing content. In the event that content must be removed, it should be removed in such a way that allows for the user to re-download it separately in order to continue playing the content. Major content expansions should not be removed from any download or purchase mechanism. The following procedures should be followed towards the end of the game's life-cycle: Online servers should remain online as long as possible. If the need to terminate online servers becomes required, the server software must be released to the public. Additionally, a final update/patch must be released to allow the game to easily connect to 3rd-party servers. All game content must remain purchasable and/or downloadable. Content creation tools should be released to the community. In games developed with Blamite, the full Blamite Editing Kit should be released, with no restrictions on functionality and no crucial tools omitted.  
    Contingency Plan

    The following is a fallback plan to try and execute as effectively as is feasible in the event that Elaztek Studios were to ever be unable to continue business operation. Unlike other parts of the policy, it does not need to be followed to the letter - because there is the likelihood that, should the company reach this stage, it may simply be impossible to meet the requirements. However, if possible, as much of the following should be completed as possible. An incomplete execution of the following plan is better than having all of our hard work turn to dust and fade away.
     
    Should the company fall on hard times and be unable to continue business operations, efforts should first be made into downscaling into a volunteer operation, similar to how it started. This means that the CEO(s) or upper management at the time take it upon themselves to continue hosting services out-of-pocket, funding them through means such as an alternative job elsewhere. Every effort to preserve the company should be taken and pursued, except in cases which would compromise the company's integrity or core values. The ultimate determination on how to proceed in such a circumstance falls on the company Founder, or the highest ranking CEO at the time in the event the Founder is no longer overseeing the company. Feedback should be considered from all existing employees. In the event that the company is determined to be unable to continue operating in any capacity, business or otherwise, and the company is decided to be permanently shutting down: All possible efforts must be made to ensure that all intellectual property, software source code, software binaries (including outdated versions), documentation, and game content are released to the public under the most permissive licenses possible. All possible efforts must be made to ensure that any and all FREE community-created content is released to the public. In the case of PAID content, the decision on how this content is to be released should fall to the content author. In the event that the author cannot be contacted, their paid content should be treated as free content under the assumption that the author has stopped maintaining their content. A webpage providing access to all of the above should remain online for 1 year at minimum, with at least 90 days notice before permanent shutdown. Every effort should be made to instruct users on where to locate the content after that date. If a community operation arises with the goal of continuing to offer Elaztek software downloads and/or support, every effort should be made to ensure that they follow the guidelines specified within this document, and that they are in possession in all released materials before permanent shutdown. All existing forum and website content should be preserved using a read-only website for as long as possible. In the event that hosting existing web content can no longer be performed, existing topics, users, and polls must be preserved through one of the following two methods: A Specific Community Preservation Group In the event that you wish to exchange the data with a single, trusted, and respected member of the Elaztek community for the purposes of preserving forum content, the content may remain unaltered, including hidden and staff-only content, except as desired. All public content must remain unaltered and intact. The General Public In the event that data cannot be handed off to a specific group, the following content and SQL tables should be released to the public: Forum Topics Forum Posts Forums and Forum Categories Polls Downloads Categories Downloads Files Downloads Reviews and Comments Website Themes Pages Databases Pages Records Any other tables or data that is part of a public-facing webpage or content Before releasing the data to the public, care should be taken to ensure the following are REMOVED: IP addresses Email Addresses Payment and Billing Information (if applicable) Street Addresses (if applicable) Other personal information (if applicable) Hidden and Staff-only Content  
    Failure to abide by this policy may result in termination from the company. Each and every policy listed does not have any limitation. Every policy listed should be considered as effective from the date of introduction for the duration of the company's lifespan.

    Webs.com Site Archives

    In History,

    Here, you can find links to very early Webs.com sites that we used to operate.
    Elaztek Studios' roots can be traced all the way back to 2013, when the founder of the company first created a "company" named Haloman Development - abbreviated as HMD. Galactiminer and Project: Infinity can both be traced back to those origins, though very little real development wouldn't come until many years later.
     
    Unlike Elaztek or Chaotic United's modern websites, which are more or less custom built - that is, run on a proper webserver with full control over site content and applications - these older websites were created using Webs (webs.com), which is an easy-to-use site builder service. They offer very limited control over what you can do, but are intended to make it so that those without the knowledge or experience to operate their own webserver were able to create a basic website.
     
    Those websites got very little development and were officially retired once Elaztek Studios was launched. The websites have since only been maintained enough to ensure they continue to exist (in other words, periodically logging into the Webs account to ensure they weren't automatically removed).
     
    However, on November 11, 2020, Webs announced that they would be shutting their doors and migrating all content over to Vistaprint - the parent company of Webs. However, only Premium Webs customers would have their content migrated over. Those who didn't have premium websites were told that their site would no longer be viewable or editable:
     
     
    In order to preserve the old websites (as awful as they are, seeing as they were made by a 13 year old), the websites were mirrored using WinHTTrack and will be hosted on our own webserver going forward. You can find all 6 Webs sites that were previously operated by haloman30 below, though not all of them were related to Elaztek. Additionally, a 7th site that was part of CU's history but wasn't hosted by haloman30 was also archived - and is also linked below.
     
    Please keep in mind that, again, the quality of the websites are terrible. They were made by a 13 year old and, as such, contain some pretty dumb stuff and weird claims - and have been unaltered from those early iterations. Additionally, keep in mind that these websites are read-only. Several of them used to contain account and forum functionality, but these are dependent on Webs' backend systems - which are not available for these archives. As such, logging in, registering, or any other user content will simply do nothing. Think Wayback Machine.
     
    Enjoy - if you can.
     
    Elaztek Studios
     
    Haloman Development
    Archive URL: http://haloman30.com/archives/webs.com/halomandev.webs.com/index.html Original Webs.com URL: https://halomandev.webs.com/   
    Galactiminer
    Archive URL: http://haloman30.com/archives/webs.com/galactiminer.webs.com/index.html Original Webs.com URL: https://galactiminer.webs.com/   
    Project: Infinity
    Archive URL: http://haloman30.com/archives/webs.com/infinityproject.webs.com/index.html Original Webs.com URL: https://infinityproject.webs.com/   
    Chaotic United
     
    Chaotic United
    Archive URL: http://haloman30.com/archives/webs.com/chaoticunitedserver.webs.com/index.html Original Webs.com URL: https://chaoticunitedserver.webs.com/   
    United Alycraft
    Archive URL: http://haloman30.com/archives/webs.com/unitedalycraft.webs.com/index.html Original Webs.com URL: https://unitedalycraft.webs.com/   
    Hurricane Gaming (HurricaneCraft) (not owned by haloman30)
    Archive URL: http://haloman30.com/archives/webs.com/hurricanegaming.webs.com/index.html Original Webs.com URL: https://hurricanegaming.webs.com/   
    Other
     
    HaloFanZone
    Archive URL: http://haloman30.com/archives/webs.com/halofanzone.webs.com/index.html Original Webs.com URL: https://halofanzone.webs.com/ 

    Rank Information

    In Elaztek Studios,

    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.
    This article is not yet finished and may contain inaccurate information.
     
    These are the guidelines that all members of the Elaztek Team is expected to agree to and abide by. If you are applying for any of our positions, you will be required to follow these guidelines. If you find a team member not obeying these guidelines, please submit a report or open a support ticket and we will take action if necessary. 
     
    INTERNAL CONTENT AND NON-DISCLOSURE AGREEMENT
    1. All content not visible on the public end of the website should be treated as if it were under Non-Disclosure Agreement (NDA). Posting images, descriptions, videos, or any other content revealing the content under implied or true NDA will result in termination from the team, and in some cases, could result in legal action being taken.
    2. All modifications of official source code, game assets, textures, sound effects, and any other content used within Elaztek's website, games, software, or any other product/service should be documented and approved by each project's respective leader.
    3. Any and all source code within private Elaztek repositories, on either our own Gitlab, Github, or any other service or site where our source code is stored, is under a non-disclosure agreement. Releasing any part of this source code in the form of text, screenshots, videos, audio, or any other means will be seen as a violation of the NDA and will result in your immediate termination from the team and potential legal action.
     
    PUBLIC RELATIONS
    1. All interactions with the community should be handled with care and a basic level of maturity should be demonstrated. Acting in an immature manner could result in you being terminated from the team, and in some cases, could result in legal action.
    2. Should a controversial discussion gain major attention by the community, you should contact an administrator or CEO immediately. Do what you can to keep things calm, maintain two-way communication. Do your best to keep community anger at a minimum and make sure to be respectful.
    3. Getting an attitude with, flaming, insulting, harassing, punishing, attacking, or otherwise using defamatory or angry language during such an event will result in your immediate termination from the team.
     
    GENERAL BEHAVIOR INSIDE AND OUTSIDE ELAZTEK
    1. Performing any illegal activities, either within or outside Elaztek, will result in your immediate termination from the team without notice.
    2. Encouraging any illegal activities, either within or outside Elaztek, will result in your immediate termination from the team without notice.
    3. Cyberbullying, harassment, flaming, or otherwise attacking another person and/or team member will result in immediate termination from the team without notice.
    4. DOX'ing or otherwise leaking personal information of another person, inside or outside Elaztek, will result in immediate termination from the team without notice.
     
    MONETIZATION
    1. Game design and monetization should not seek to exploit the consumer or player, in any way. This includes but is not limited to: Gameplay altering microtransactions in a non-free game or product, Pay-to-Win mechanics in a non-free game or product, Random-number-generators/lootboxes in a non-free game or product, and any other similar tactics that are used as part of generating revenue and are not part of the genuine creative vision of Elaztek Studios.
    2. Paid employee wages should not be increased as a result of exploitative business practices, including but not limited to: Microtransactions in a non-free game or product, Pay-to-Win mechanics in a non-free game or product, and any other similar tactics that are used as part of generating revenue and are not part of the genuine creative vision of Elaztek Studios.
    3. With the exception of company financial instability, or the need to terminate employees due to lack of revenue (layoff), decisions may not be made with the sole intention of generating profit or exploiting the consumer.
    4. Lootboxes, P2W, and gameplay altering microtransactions are permitted in very specific instances of free-to-play games with no other means of revenue. Including these elements in games that are not free (games that must be purchased in order to play) will not be permitted with the exception of company financial instability or as otherwise described above. Elaztek reserves the right to disallow the inclusion of these practices in any free-to-play project.
    5. Cosmetic-only microtransactions may be allowed in some cases. This will vary depending on the scale and scope of the project. Elaztek reserves the right to disallow or deny the inclusion of cosmetic-only microtransactions in any free-to-play or paid game.
     
    INDEPENDENT TEAM PROJECTS
    1. Any projects created by Elaztek team members as independent projects (ie, Project: Vista) will be owned by Elaztek Studios.
    2. Elaztek reserves the right to continue a successful project created by an Elaztek team member independently, in the form of DLC, sequels, expansions, updates, etc.
    3. Elaztek reserves the right to terminate any team project if it is deemed offensive, malicious, or otherwise undesirable to be placed under the Elaztek name.
    4. If you choose to cancel an independent project, Elaztek reserves the right to continue and complete the project should we see it valuable.
     
    TERMINATION
    1. Elaztek reserves the right to terminate anyone from the Elaztek team, for any reason we see fit.
    2. To protect our team and users from unjust action, we require that there must be some degree of probable cause for a termination before action is taken.
    3. Attempting to get another team member terminated without valid reason will result in your termination from the team.
    4. Upon termination, you will lose your website rank and access, your Discord role, and your access to Elaztek repositories.
    5. If you commute, you will have 3 days (72 hours) to collect any personal belongings. This may be extended at a manager's discretion. After this time, your keycard will no longer be valid and you will no longer be able to enter the building. If you have forgotten or lost any personal belongings, please contact a manager or other member of the team.
    6. Elaztek is not required to disclose the reasoning for any termination (but we usually will, and usually you will know in the first place).
    7. You may not be terminated for race, religion, personal beliefs, gender, sexual orientation, or other discriminatory reason.
     
    RESERVATION OF RIGHTS
    Elaztek Studios reserves the right to modify, add to, remove from, or otherwise alter these terms without notice. If you disagree with any changes made to these terms, you may contact a manager for questions or concerns. If you ultimately do not agree to the terms, you will not be allowed to be on the team and must resign.