<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Hypemasters - Medium]]></title>
        <description><![CDATA[Hypemasters (est. 2019) is an international game development studio with offices in Europe and the UAE. We are on a mission to build the top mid-core PvP gaming company in the world, one that disrupts and defines gaming genres. - Medium]]></description>
        <link>https://medium.com/hypemasters?source=rss----d3321f4456ee---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Hypemasters - Medium</title>
            <link>https://medium.com/hypemasters?source=rss----d3321f4456ee---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 14:09:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/hypemasters" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Game UI redesign. Is it worth it?]]></title>
            <link>https://medium.com/hypemasters/game-ui-redesign-is-it-worth-it-69e6cbb0a6f7?source=rss----d3321f4456ee---4</link>
            <guid isPermaLink="false">https://medium.com/p/69e6cbb0a6f7</guid>
            <dc:creator><![CDATA[Boris Kiselev]]></dc:creator>
            <pubDate>Tue, 12 Mar 2024 09:49:57 GMT</pubDate>
            <atom:updated>2024-03-12T09:49:57.135Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xPX83jD6sudv91nMSd_Z8w.jpeg" /></figure><p>Redesigning the UI in a game that has already been released is a tricky topic. When, how, and most importantly, why you’d better (not) tackle it? In this article, I will discuss how this issue was addressed in our game and share my thoughts and advice.</p><h4>Who am I, and what project is this?</h4><p>My name is <a href="https://www.linkedin.com/in/boris-kiselev/">Boris Kiselev</a>, and for the past 12 years, I have been working as a UI/UX designer in various mobile gaming studios. I will be discussing <a href="https://www.hypemasters.com/games">World War Armies</a>, a cross-platform RTS game set in a military environment, developed using the Unity engine.</p><p>At the time of writing this article, the game had been operational for about a year and a half. The UI that was released was initially conceived as “rough” and developed in a rather chaotic manner. I think many small gaming studios are familiar with this situation. Until your project generates sufficient revenue, prioritizing speed and flexibility in the development process often seems more important than investing in meticulous, pre-designed architecture. Right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*yP_MvQrcXTVRmGRV8SpBSg.jpeg" /></figure><p>Over time, our UI system became cumbersome, slow, and unclear. The interface itself, though quite functional, became hopelessly outdated. The team started to question the quality of our UI. It fell below the industry standards, and we believed our game deserved better.</p><p>This is when the idea of a redesign was born.</p><p>Looking ahead, the entire redesign process, from the initial go-ahead to the first release, took us about 10 months. Of these, the first six months were mainly spent on finding the new UI look and transferring each interface to Figma. This was accomplished by a designer during intervals between more urgent tasks. That’s why this stage took us so long. The active work phase lasted for 3–4 months, during which developers and testers were involved.</p><h4>Goals and expectations.</h4><p>Besides visual changes, we set ourselves several other tasks:</p><ul><li>Combine the UI redesign with a rebranding of the project and the entire studio.</li><li>Move away from the World War II aesthetic and introduce a more energetic and sporty feel.</li><li>Convert all the mockups to Figma instead of Photoshop.</li><li>Prepare a mobile-first interface to accommodate the upcoming PC release.</li><li>Organize the file system related to the interface inside the project.</li></ul><p>It was immediately apparent that until the redesigned UI launch, we would need to somehow maintain the existing old UI. This meant that all new product features introduced during this ‘transition’ period would have to be implemented in both the old and new designs. It’s like driving an old car that constantly breaks down, while simultaneously building a second, fresher, and more fashionable one. Doesn’t sound very reliable, does it?</p><p>Vividly aware of the number of unknown factors and things that could go wrong, we tried to protect ourselves from a possible fiasco in advance. A mandatory condition was set: in the unlikely event (as we thought) that the new design turned out to be noticeably worse than the old one, we wanted to be able to pull the conditional plug and roll everything back painlessly. Then, we could pretend that nothing had happened.</p><p>What were our expectations? Ambiguous. Within the studio, there was no understanding of how exactly the redesign would affect our game. Colleagues from other studios shared that it worked out for them and actually had a positive and measurable impact. But this is not a guaranteed outcome. Also, we couldn’t rule out the possibility that the changes would lead to a significant drop in metrics. It may sound risky (taking on a big feature with this amount of risks and unpredictable results), but it’s a fairly common situation for visual tweaks. Subjectively, as developers, we might believe that the innovations are beneficial to the project. However, they either have imperceptible effects on metrics, or it’s not clear how to measure their impact. We agreed to be ready to accept the risks and just dived into it headfirst.</p><p>In the next sections, I will talk about the technical aspects of the process, the problems we encountered along the way, and reveal the final results of the whole adventure.</p><h4>The Plan.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dstFB5txwHWiDGCX" /></figure><p>In broad strokes, our plan for the redesign feature included six steps:</p><ol><li>Find a suitable new visual style for the UI. First, we would create several key benchmark screens to serve as references for all others.</li><li>Redraw mockups for all screens and windows in the new design — in Figma. We had about 90 screens and windows in the game at that time. The mockups were entirely created in Photoshop and stored on Google Drive.</li><li>Once we have redrawn all the screens, we gradually transferred them into the game engine, laying them out, but not connecting them to code yet.</li><li>Once a critical mass of reworked screens is reached and the system of UI elements and components inside Unity is formed, we begin by reconnecting the screens in the engine. Simultaneously, we designed the missing mockups.</li><li>Roll out the new interface through QA, screen by screen, fix any bugs found, and then release.</li><li>Document and analyze the outcome.</li></ol><p>The entire plan seemed quite clear and feasible. With a list of screens awaiting redesign, we could easily monitor and forecast each stage. In theory.</p><p>Initially, there was no deadline, but it appeared much later as the release dates for the PC version approached.</p><h4>Step 1. Searching for a new visual style for the UI.</h4><p>Given that our game is set in World War II, the typical approach involves employing a skeuomorphic interface. In this design style, buttons, panels, and widgets mimic authentic materials and textures, with a subdued palette dominated by grey, brown, and green</p><p>Here are some examples of skeuomorphic interfaces from similar games with a comparable setting:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*_-Zj2qNt0VyPCbMSF8Stpw.jpeg" /><figcaption>KARDS</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*awJea9lAnnyKK7agr2D3kQ.jpeg" /><figcaption>World Conqueror 3</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/1*9f_uRfyR3unFEFkHJ2HPMA.jpeg" /><figcaption>Warpath: Ace Shooter</figcaption></figure><p>In the redesign, our goal was to step away from this concept and aim for a lighter, simpler, and more energetic visual, evoking associations with sports competitions instead of war. Additionally, we aimed to develop a set of memorable visual elements that would make our game stand out from its competitors.</p><p>After several weeks of brainstorming, the art department identified images that received a positive reaction within the studio, and they became the foundation for the redesign:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iDeW4ehw2fsFvng-YOZarg.jpeg" /><figcaption>Old UI vs Concepts vs New UI (click to see in full size).</figcaption></figure><h4>Step 2. Designing mockups. Figma instead of Photoshop.</h4><p>I’ll start with a brief explanation for those unfamiliar with why Photoshop is mentioned here at all. What does it have to do with interface development?! Well… No sane web designer would assemble interfaces in this software, that’s for sure. But in game studios, it’s common practice. Why? Games generally have a higher amount of “artistic” UI elements per square pixel. Some game interfaces are truly beautiful pieces of art, featuring complex effects, styles, masks, textured fills, and a multitude of layers with various blending modes. Players are accustomed to exceptionally high artistic standards in this area. Standard web designer toolkits often fall short, and Photoshop comes to the rescue. However, in recent years, Figma has been slowly but surely pushing the old-timer aside, even in game studios. This is primarily because, unlike Photoshop, Figma allows the creation and maintenance of a system of interface components and offers a dynamic layout</p><p>To give you an idea of the depths of suffering of a UI/UX designer working in Photoshop, here’s a simple example. You can create a library of components (for example, buttons), but any changes to a specific instance, whether resizing the element or adjusting the text, require breaking its link to the library component. A trivial task of changing all buttons’ text size from 30pt to 32pt, suddenly turns into a titanic quest.</p><p>I can’t help but mention the icing on the cake — the size of PSD files:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/0*hV_yfGW8Zp_3Xxow.jpg" /></figure><p>Note that we had to store them in the cloud, which needed to be regularly updated. It’s painful.</p><h4>Step 3. Layouting screens in Unity.</h4><p>So, after a couple of months of meticulous work in Figma, as if by magic, we have layouts for all screens with the new visuals and an amazing system of components:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dZSQ1nQOmGBg2Ud_.jpg" /></figure><p>Just beautiful!</p><p>Now the most interesting part begins — transferring the layouts into Unity Engine.</p><p>Before the work started, we divided all screens into three logical groups. The first group included those screens that players see constantly: the main menu, the collection, the battle management screen, etc. These are an integral part of the players’ basic game cycle. We weren’t ready to release the feature until the redesign of these parts was finished. This group also included screens related to the game’s monetization, like Battle Pass.</p><p>The second group consisted of screens and windows that players see rarely or only under special conditions. For example, the account linking window, player profile, or event rules. It was decided that no one would die if the visuals of these screens were updated gradually, from release to release.</p><p>The third group of screens essentially consisted only of the battleHUD, the gameplay part of the interface:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*GZ_qEvJ4UIQ8HeOu.jpg" /><figcaption>In-battle HUD</figcaption></figure><p>We decided <em>not to touch it at all</em>, at least in the first iteration of the redesign.</p><p>Why? First of all, it is a fairly isolated space with its own rules and design. For example, it’s the only place where we use round buttons, which are more convenient for quick, blind use.</p><p>Secondly, players are very sensitive to any changes in the gameplay interface. Colleagues from other studios who have already gone through the redesign process told me that players react extremely negatively (up to mass “boycotts”) to any changes in the gameplay interface. Even though the new version may (according to analytics) work better than the previous one. We decided to assess how the redesign of the game’s meta part goes. If it met our goals, then we would move on to the battle HUD.</p><p>Whether to release all screens at once in the redesigned format or to do it gradually is still a question for me. Clearly, it would be better to release everything at once (and without bugs), but this is idealistic thinking. At the beginning of redesigning the game, I had adhered to the concept of “release everything at once”, but towards the end, I changed my mind. Now, I believe that such an approach is erroneous. In reality, maintaining two different working versions of the interface simultaneously is quite a challenge. The sooner we get rid of the duplication, the easier and more predictable the project’s life will become.</p><p>As far as I know, none of those who released interface redesigns piece by piece encountered noticeable negativity from players on this matter or metrics drops. Overall, I think that the decision whether to release the redesign in chunks or not depends on many factors: the studio’s internal resources, set deadlines, differences in the visual style of the old and new UI versions (how noticeable the difference is), etc.</p><h4>Resource issue. Interfaces and outsourcing.</h4><p>Our Hypemasters team is relatively small. We only have one UI/UX designer. Given the need to redesign the UI while maintaining the existing screen system and managing a constant stream of new features, we recognized early on that it was essential to delegate as much work as possible. We made two attempts, one involving interns and the other hiring an experienced specialist from an outsourcing company. Unfortunately, both attempts failed, and it was a valuable lesson learned.</p><p>The interns consumed a significant amount of time and required almost constant supervision. In the end, they were unable to deliver the desired quality level. While we didn’t have high expectations for this option, we still gave it a chance.</p><p>Collaboration with the outsourcing company turned into a different kind of disappointment. Despite the skill and experience of the hired specialist, we did not receive a single completed screen. This happened for several reasons. From my perspective, the main issue was the fundamentally unattainable level of integration of the outsourcing specialist into the project. The interface of any game is a unique thing, full of its own features, quirks, crutches, and workarounds. Essentially, there are only two options for the outsourcing specialist: they can meticulously delve into every aspect, ask numerous questions, maintain constant communication with the developers, and invest a significant amount of time and mental effort, increasing their chances of receiving an offer to join the team permanently. Alternatively, they can ignore these intricacies and proceed with their usual methods, avoiding “redundant” questions. This approach may be energy-efficient, but unfortunately, in our case, it resulted in “final” screens that were not suitable for further work. Reconnecting them to the engine required significant effort due to the drastically different internal structure of the prefabs compared to the originals.</p><p>As a result, a couple of months later, we found ourselves in a situation where the deadlines had already been missed, but no screens were ready for integration. This was a critical moment where we could have opted to abandon the entire redesign idea relatively painlessly. But, we were already unstoppable! Therefore, we had to roll up our sleeves, endure some crunch time, and accomplish everything with the hands we had available on the team.</p><h4>Step 4. Screens integration.</h4><p>As I mentioned earlier, we implemented the redesign with a feature flag, which allowed us to quickly and easily turn the whole feature off. For this purpose, the project stored two (actually three — included in the PC release) versions of screen prefabs and visual configs. One version was for the old interface and the other for the new one. They were structured so that (in theory) removing all elements of the old interface would break as few links as possible in the new one. All UI sprites were also duplicated: the old textures were used only in the old interface, and the new ones were used only in the new interface. Of course, some overlapped.</p><p>Since changes to the visual appearance of a screen often entail modifications to the internal structure of the prefab (the number of “layers”, their grouping and position, animations, and naming), after the layout was implemented, all code snippets needed to be reconnected to the new components. The fewer logical changes in the new screen after the redesign, the better. Ideally, the screen add would run smoothly and without errors immediately after the layout was completed. Unfortunately, this happens rarely.</p><p>I am not a coder. Without knowing even the basics of C#, all I could do was copy the structure from the old prefabs, paste it into the new ones, and pray that nothing broke in the process. Like a diligent student attempting to cheat on an assignment without understanding it, I often couldn’t grasp why a specific element would magically stop working in the new design, even though it worked perfectly in the old one. This led to numerous issues and required a lot of subsequent corrective work from the developers.</p><p>The phased approach we eventually settled on, which aimed to more or less guarantee the absence of bugs in the final screens, looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kx92FpMgfAUHiDp8u7M4vA.jpeg" /></figure><ol><li>The markup designer assembles the screen and connects code snippets to the best of their abilities. Usually, after assembling, the screen does not function properly, preventing it from being tested in the game.</li><li>The developer refines the screen code, ensuring its functionality.</li><li>The screen is then returned to the markup designer for visual cleanup and testing to ensure it functions properly within the game. This includes testing across different variations and on various devices in the simulator. Most visual bugs are identified and addressed at this stage.</li><li>After this initial check, the screen is passed to the QA department, where it is tested more thoroughly. Here, both the markup designer and the programmer collaborate to address and fix any bugs identified during QA testing.</li><li>When the flow of bugs dries up, we consider the work on the screen to be completed and move it to the folder with “ready” prefabs.</li></ol><h4>Step 5. Feature release.</h4><p>Even with such a pipeline, a significant number of bugs that made their way into the release build. These bugs impacted basic metrics like ARPDAU during the AB testing that started after the initial, cautious feature release. This negative impact was mitigated by the gradual rollout of the feature, ensuring that only a small number of players saw the rawest version. Thanks to them, we were able to find and fix most of the problems.</p><p>For example, we encountered a bug where players who purchased a battle pass were unable to collect quest rewards. For such players, we had to disable the feature until the bug was fixed. In essence, users with the new UI experienced a “downgrade” to the previous interface state after making a purchase.</p><p>And believe me, this was far from the only problem we encountered.</p><p>After several releases with fixes and bug fixes, the results of the version with the new UI finally stabilized, allowing us to discuss and analyze the obtained data.</p><h4>Step 5. Evaluation of the results. What about metrics?</h4><p>Frankly speaking, I didn’t expect any significant and unequivocally positive changes after introducing the new UI. After all, the feature did not impact gameplay or introduce any new functionality. The main changes were related to the project’s internals and the visual component.</p><p>Colleagues from game studios who had gone through the same process shared that UI redesign improved projects’ metrics “on average,” but with many nuances.In most cases, some projects saw slight improvements, while others experienced declines. In certain cases, the impact was notably negative. Moreover, the effect varied across different countries, with the same redesigned screen showing higher results in Germany and lower in South Korea.</p><p>In our case, the main measurable positive effect of the UI redesign was on retention. For new users, the rate of returning to the game on the 1st day was noticeably higher:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9QtwIjy8opTQw5YqTpsyEQ.jpeg" /></figure><p>The difference for the second day was +10.4%, for the third +7.2%, and for the seventh +3.2% in favor of the new UI. For old players, a smaller difference in retention was recorded, around only 1% in favor of the redesign.</p><p>ARPU for new users did not change. Conversion to paying users among old players remained unchanged. However, among new players, it slightly increased. On average, it was about +0.5% in favor of the redesigned UI.</p><p>ARPDAU for old players initially decreased in the redesign, but gradually corrected. Most likely, this was due to bugs in the initial releases.</p><p>If we analyze the feature solely from a financial point of view, the redesign may not seem to make much sense. Comparing the numbers before and after, we see that the redesign will recoup its development cost in about two years. Yes, Warren Buffett would have laughed heartily at such “investments”. However, I would like to remind you that in addition to (initially low) financial expectations, it was necessary, as we needed to adjust the game’s image, the company’s image and brand, and resolve some technical issues. I find it difficult to convert these aspects into a monetary equivalent.</p><p>That’s all regarding the objective data I can share with you. Additionally, there was an array of subjective feedback.</p><h4>Players’ feedback.</h4><p>It is well-known that users don’t like relearning. After a certain amount of repetitions, even the most inconvenient but familiar interface becomes… well, acceptable. And when it’s changed, it often causes dissatisfaction and frustration among users.</p><p>The interface changes in our case were almost exclusively visual, so I hoped that we would be able to avoid major negativity. In vain! I would describe the feedback we received as “mixed” at best. Our players pointed out a lot of issues, mostly related to the numerous bugs in the release.</p><p>All in all, UI bugs outside of the gameplay HUD didn’t bother players much, but any interface-related problems during battles were critical and significantly affected the application’s ratings in stores.</p><p>It is also worth mentioning that feedback is only the tip of the iceberg, representing the opinion of an active minority. The vast majority of players will not bother to engage in debates with developers; they will silently vote with their time and money. Therefore, in my opinion, changes in metrics always provide a more objective picture, while live feedback from players allows us to understand and catch the most noticeable bugs and problems.</p><p>Here are some examples of the feedback we received:</p><p><em>“I really like it, a lot smother than the old one”</em></p><p><em>“It’s good! Feels like a new game.”</em></p><p><em>“Old was better.”</em></p><p><em>“It’s good, but it’s more laggy than the past version.”</em></p><p><em>“Beat and tidy, good improvement.”</em></p><p><em>“I like the clean new look. It’s a nice refresh from the dull generic animation it used to be.”</em></p><p><em>“Looks very clean and polished.”</em></p><p><em>“It’s good, but I prefer the older version.”</em></p><h4>Conclusions:</h4><p>To those who are also considering redesigning their game’s interface, I can advise the following:</p><ul><li>If your game was launched less than a year ago or hasn’t been released yet, don’t bother with redesigning the UI. If you’re not satisfied with the current performance of the game, tuning the UI visuals is unlikely to improve it. Focus on other, more critical (and probably missing) game aspects and mechanics. It’s important to note that this advice doesn’t apply to UX! Improving the interface’s usability whenever possible is always worth it!</li><li>The measurable financial outcome of the redesign, in our case, was primarily reflected in the increase in retention. While this may not have a significant direct impact on revenue for our game, for games with more ad-driven monetization, it could increase revenues.</li><li>Don’t redesign the interface if you’re already feeling a lack of resources, both in terms of time and manpower. Adding another layer of chaos on top of the constant bustle is a surefire way to lower the overall quality across all fronts.</li><li>Allocate a sufficient amount of time to the stages that fall “between” the responsibilities of different departments. As practice shows, these are the most problematic. Establish clear guidelines for quality control at each stage. Who controls the quality at each stage? Who accepts and transfers screens from one stage to another? Who fixes emerging issues, and when? Who can revise a screen and send it back to the previous stage, and under what conditions? Who’s responsible in case of problems?</li><li>Consider releasing the redesign in stages, screen by screen. Don’t wait until the very last moment in an attempt to release everything at once.</li><li>Be mentally prepared for setbacks and problems in the first days after the feature release. The Interface acts like glue, it binds the entire game together. There are many connections, and there’s a good chance that something may go wrong. Well, or option “B”: allocate a lot of time for testing.</li><li>Don’t hire outsourcing for sensitive and complicated tasks. If necessary, hire someone in-house. This way, you’ll save time, money, and nerves and gain more control over the results.</li></ul><p>For those of you who want to evaluate the results of our work and the decisions we made, look for World War Armies on <a href="https://play.google.com/store/apps/details?id=com.Hypemasters.rts&amp;hl=en&amp;gl=US">Google Play</a>, <a href="https://apps.apple.com/sg/app/world-war-armies-modern-rts/id1506931934">Apple App Store</a>, and <a href="https://store.steampowered.com/app/2438160/World_War_Armies/">Steam</a>.</p><p>If you have any questions or want to keep in touch, contact me on <a href="https://www.linkedin.com/in/boris-kiselev/">LinkedIn</a>.</p><p>That’s all from me, thanks for your attention!</p><p>Yours, Boris Kiselev.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69e6cbb0a6f7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hypemasters/game-ui-redesign-is-it-worth-it-69e6cbb0a6f7">Game UI redesign. Is it worth it?</a> was originally published in <a href="https://medium.com/hypemasters">Hypemasters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Safe ways to use defines]]></title>
            <link>https://medium.com/hypemasters/safe-ways-to-use-defines-4cb53c43a882?source=rss----d3321f4456ee---4</link>
            <guid isPermaLink="false">https://medium.com/p/4cb53c43a882</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[error-handling]]></category>
            <category><![CDATA[compilation]]></category>
            <category><![CDATA[c-sharp-programming]]></category>
            <category><![CDATA[game-development]]></category>
            <dc:creator><![CDATA[Andrey Vishnitskiy]]></dc:creator>
            <pubDate>Mon, 17 Apr 2023 05:48:08 GMT</pubDate>
            <atom:updated>2023-04-17T05:48:08.036Z</atom:updated>
            <content:encoded><![CDATA[<p>This article is written to help any developer faced with errors related to defines in the code. Namely, for those of you who’ve performed some renaming via IDE, and suddenly, have a compilation time error (CTE) on the release build. After reading this article, you will use methods that are less error-prone when using defines, enabling you to face fewer cases of CTEs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*1s5-M7zBo-R965Y6ZcDMKw.png" /><figcaption>At Hypemasters, our engineer corps is working tirelessly to make the best RTS games ever</figcaption></figure><h3>Simple use define</h3><p>Let’s take a look at a simple case of using</p><pre>using UnityEngine;<br>using UnityEditor;<br>//...<br>private void Start()<br>{<br>    DoSmthEditor();<br>}<br><br>private void DoSmthEditor()<br>{<br>#if UNITY_EDITOR<br>    AssetDatabase.SaveAssets();<br>#endif<br>}</pre><h4>Issues</h4><p>The above example demonstrates how we cannot compile that code in any build. This code will only work in Editor.</p><p>This method uses the AssetDatabase class, which was declared in UnityEditor. Of course, to use it, we have to declare using UnityEditor at the top of the file.</p><p>Here, our main problem is a using, what your IDE usually imports into a file. This may work well in regular cases, but not if you are using defines. In this particular case, we imported UnityEditor into a file, which does not exist in builds. That’s the reason why we cannot compile this example to any build, mobile, console, pc, etc.</p><h4>Option to solve</h4><p>Now that we understand the issues, it’s time to resolve them.</p><pre>using UnityEngine;<br>#if UNITY_EDITOR<br>using UnityEditor;<br>#endif<br>//...<br>private void Start()<br>{<br>    DoSmthEditor();<br>}<br><br>private void DoSmthEditor()<br>{<br>#if UNITY_EDITOR<br>    AssetDatabase.SaveAssets();<br>#endif<br>}</pre><p>It compiles, but here, you have one more define using. If you will implement any additional using, then it will still automatically be placed out of the define, and will lead to CTE once more.</p><pre>using UnityEngine;<br>#if UNITY_EDITOR<br>using UnityEditor;<br>#endif<br>using Reimporter.AvailableOnlyInEditor;<br><br>//...<br>private void DoSmthEditor()<br>{<br>#if UNITY_EDITOR<br>    AssetDatabase.SaveAssets();<br>    Reimporter.ReimportAllFolders();<br>#endif<br>}</pre><p>Clearly, this potential solution is not so safe. How can we improve it?</p><h3>Case with full namespace</h3><pre>using UnityEngine;<br>//...<br><br>private void Start()<br>{<br>    DoSmthEditor();<br>}<br><br>private void DoSmthEditor()<br>{<br>#if UNITY_EDITOR<br>    UnityEditor.AssetDatabase.SaveAssets();<br>#endif<br>}</pre><p>In this example, we use the fully qualified class name.</p><p>Do not leave the using namespace on top of the file in the way it was suggested by your IDE. Just use the full name of the classes inside your defines to avoid having the CTE in that case.</p><h4>Issues</h4><p>This approach has almost no issues except for the following:</p><p>1) In cases with over 10–20 lines, it can be hard to maintain that rule</p><p>2) It still won’t rename it safely. This is because if the current context has disabled defines, then the code under disabled defines is not active. It won’t invoke an IDE; it’s just a text like a comment. Once that code is activated by enabling a define, you will find yourself with a CTE.</p><h3>Conditional</h3><p>Can this last case be resolved as well? Yes.</p><pre>using UnityEngine;<br>//...<br>private void Start()<br>{<br>    DoSmthEditor();<br>}<br><br>[Conditional(&quot;UNITY_EDITOR&quot;)]<br>private void DoSmthEditor()<br>{<br>    UnityEditor.AssetDatabase.SaveAssets();<br>}</pre><p>When using a [Conditional()] attribute, you will have always code available in IDE, even when your defines are not active.</p><p>That way, it is easier for your to analyze code, display warnings, make suggestions, and perform the refactoring. This is true in the case of renaming as well.</p><h4>Issues</h4><p>This approach can be very helpful and preferable in most cases, but it has limitations as well:</p><p>- The method must return void</p><p>- It doesn’t support ‘or’ operations like ‘UNITY_EDITOR || UNITY_IOS’</p><h3>Bonus — logger tip</h3><p>I think most projects have some level of logging, and we should enable and disable this function on release and development builds.</p><p>We can easily do this as follows:</p><pre>public void LogTrace(string message)<br>{<br>#if LOGLEVEL_TRACE<br>    Log(LogLevel.Trace, message)<br>#endif<br>}</pre><p>It works, but it also presents an issue. The LogTrace method still compiles and executes with strings created from invocation. And strings to make a log that is still creating for each not-enabled log generate garbage in a heap. i.e. any string concatenations or formatting would still take place.</p><p>Just use a [Conditional] attribute to improve the performance of your project as follows:</p><pre>[Conditional(&quot;LOGLEVEL_TRACE&quot;)]<br>public void LogTrace(string message)<br>{<br>    Log(LogLevel.Trace, message)<br>}</pre><h3>Project limitation</h3><p>A final approach would be to limit your code by defines in .asmdef. In the case of mismatched defines, you would simply cut the whole assembly. This method works well for tests, plugins, and packages and presents no disadvantages, but your architecture may require you to split it by different assemblies.</p><p>For additional information, check out <a href="https://docs.unity3d.com/Manual/class-AssemblyDefinitionImporter.html#define-constraints">Unity’s documentation</a>.</p><h3>Conclusion</h3><p>It may seem like a tiny theme, but when you use defines, you will be faced with more and more CTE. Some will occur because of renaming or refactoring, while others will result from inaccurate or insufficient experience with defines. Without implementing best practices and additional code checks, you will find yourself experiencing more and more broken develop compilations.</p><p>All these approaches have their own pros and cons. Some will be better for some cases, while others are more optimal in others.</p><p>It’s up to you to try and decrease your defines count. You can do this using various interface implementations through dependency injection. This is safe, and transparent, and enables you to achieve a lower repeatable code count (using define).</p><p>For example,</p><pre>public class LoggerProvider : ILoggerProvider<br>{<br>    public ILogger GetLogger(string category)<br>    {<br>    #if LOGS_ENABLES<br>        return new Logger(category);<br>    #endif<br>        return new NullLogger();<br>    }<br>}</pre><p>Or, you can only use one define and have a transparent logic in its dedicated class:</p><pre>void InstallBindings()<br>{<br>#if LOGS_ENABLED<br>    Container.BindAllInterfacesTo&lt;LoggerProvider&gt;().AsSingle();<br>#else<br>    Container.BindAllInterfacesTo&lt;NullLoggerProvider&gt;().AsSingle();<br>#endif<br>}<br><br>public class NullLoggerProvider : ILoggerProvider<br>{<br>    public ILogger GetLogger(string category)<br>    {<br>        return new NullLogger();<br>    }<br>}<br><br>public class LoggerProvider : ILoggerProvider<br>{<br>    public ILogger GetLogger(string category)<br>    {<br>        return new Logger(category);<br>    }<br>}</pre><p><em>Chat to us if you are passionate about creating games and want to experience one of the most dynamic cultures in gaming today </em><a href="/service/mailto:join@hypemasters.com"><em>join@hypemasters.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4cb53c43a882" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hypemasters/safe-ways-to-use-defines-4cb53c43a882">Safe ways to use defines</a> was originally published in <a href="https://medium.com/hypemasters">Hypemasters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to save 2 sec+ loading time of your game]]></title>
            <link>https://medium.com/hypemasters/how-to-save-2-sec-loading-time-of-your-game-f53611bbea0a?source=rss----d3321f4456ee---4</link>
            <guid isPermaLink="false">https://medium.com/p/f53611bbea0a</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[unity]]></category>
            <category><![CDATA[loading-time]]></category>
            <category><![CDATA[performance]]></category>
            <dc:creator><![CDATA[Andrey Vishnitskiy]]></dc:creator>
            <pubDate>Fri, 24 Feb 2023 10:32:38 GMT</pubDate>
            <atom:updated>2023-02-24T10:32:38.653Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Article was written by </em><a href="https://medium.com/u/a49467583718"><em>Andrey Vishnitskiy</em></a></p><p>After reading this article, you will be able to decrease the loading time of your unity app on 2+ sec, or more. Why is this important? The less time users spend loading games, the more time they spend playing them. This is because it will be easier and faster to open for them to open the game, reducing much unecessary frustration. Would you think twice about opening a game if it will loads in second instead of in minutes? I’d think not!</p><h3>Splash screen solution</h3><p>The easiest way to achieve this goal is to remove the Unity splash screen and bring them into your scene.</p><p>Most projects have Unity splash screens, like in screenshot below. These are easy to enable and setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mTvWQ9sMX2E4bEwg" /></figure><p>The screenshot shows that the duration is set to 2 seconds, which is the default value. Nothing is happening on the CPU or on other threads during this period of time, except for the Render Thread that is rendering the splash screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IpTll-BKb_h34Mni" /></figure><p>Unity engine developers are aware of this behavior, and we hope to see improvements soon. Until then, the 2021 and older versions continue to display this behavior. In the meanwhile, it’s better to simply disable Unity’s built-in splash screen and add the logo to a lightweight loading scene. With such an approach, the process of initialization and loading could be started 2 seconds earlier, reducing the player’s wait time.</p><h4>Notice</h4><p>If you use Zenject or have a heavy synchronous operation on start affecting your loading time, be aware of a stuck main thread that includes no screen updates. Zenject’s installation phase is synchronous and, depending on the project’s size, could take seconds to complete — seconds during which animation might be visible, and users could be playing. My advice — use a static image screen to avoid breaking up the user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YbFDFEOMVn_9fPeU" /></figure><h3>Application.backgroundLoadingPriority</h3><p>When integrating assets on the main frame, we noticed that CPU time is underutilized. As a result, it requires more frames for the integration process to complete, which leads to longer loading times. The amount of time that can be spent on this operation is defined by the Application.backgroundLoadingPriority property.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*h8QJYZfB-a6IXdWw" /></figure><p>If you install higher Application.backgroundLoadingPriority during the loading screens, this will increase the amount of time per frame that can be spent on the main thread when integrating loaded assets. The default value is ThreadPriority.BelowNormal, which corresponds to 4 ms. <a href="https://docs.unity3d.com/ScriptReference/Application-backgroundLoadingPriority.html">Check out Unity’s documentation</a>.</p><h3>AsyncUploadTimeSlice and asyncUploadBufferSize</h3><p>Async Upload Time Slice is the amount of time the CPU spends uploading texture or mesh data to the GPU, in milliseconds per frame. A larger value means the data will be ready on the GPU sooner, but the CPU will spend more time on upload operations during those frames.</p><p>Try to experiment with values of QualitySettings.asyncUploadTimeSlice and QualitySettings. properties of Async Upload Pipeline. These values can be set in code, as well as in the Quality section of theProjectSettings.</p><p>Check out the following links for more details: <a href="https://blog.unity.com/technology/optimizing-loading-performance-understanding-the-async-upload-pipeline">Optimizing loading performance: Understanding the Async Upload Pipeline</a> <a href="https://docs.unity3d.com/ScriptReference/QualitySettings-asyncUploadTimeSlice.html">QualitySettings.asyncUploadTimeSlice</a></p><h3>Scriptable object instead of json</h3><p>Having configurations in json is convenience. It’s a human readable format, that enables you to to see diffs from your VCS. But json built-in configurations has one con — it needs to be deserialized each time. Deserializing is a not a cheap operation. We need to read the whole file, do some computing, and allocate memory. As a result, we have two copies of this configuration stored in memory: json format and deserialized in memory. I suggest to use Scriptable Objects instead of built-in json with configurations. Scriptable Objects already have ready-to-use memory that’s native for Unity</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cicCgUnZ4a9HmlPV" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6copguGaMtCESKge" /></figure><p>ScriptableObjects over json, leading to loading time, memory, and CPU utilisation benefits.</p><h3>Don’t unload previously used resources</h3><p>Yes, I’m talking about classic ObjectPool pattern. Usually, it is used for bullet, NPC, or other frequency repeatable objects. To decrease loading time, you can put all your resources from previous scenes in the object pool. Do not unload scenes, do not destroy prefabs, and do not unload addressabled handles. Destroying and instantiating processes is not cheap. This is especially true for large objects such as scenes or huge prefabs. Instead of destroying objects — just disable them. Enabling objects/scenes are cheaper to load too. They will stay in memory, and you will hold two scenes of your game; current and previous. Doing so increases memory consumption but decreases loading time.</p><p>To further improve the user experience, you can analyze the tier of the phone. Will this phone hold two scene without crashing? If yes — it will enable faster loading. If not — it will suffer from longer loading times but won’t crash.</p><h4>If you use addressables</h4><p>Addressables analyze the usage of loaded assets by reference count. If one or more references are left, they won’t be unloaded. Otherwise, if you hold asset instances but not addressable reference, you will have white objects without resources on hand.</p><h3>Check blocking calls during loading</h3><p>If your game supports fully offline mode, check your http request or other requests from the server. They shouldn’t block your loading. Otherwise, users could be deadlocked with slow internet. Or, in our case, increased loading time, which will varies more based on internet provider, than it does based on phone type. If you use async/await from C#, just check all flows from start to finish as they load and pay attention to the ‘await’ keyword. There should be no server requests pending.</p><h3>Load resources on demand</h3><p>Loading resources is one of most expensive operations in the loading process. Does your game need data from all levels configurated? Do players really need them from their starting level? Or can they be loaded later when the user opens that window?</p><p>All versions of this scenario lead to a trade-off:</p><ul><li>Preloading all resources during the loading screen — more memory is used, and a longer loading time is required, but there is no delay accessing loaded resources</li><li>Loading on demand — less memory is used, and there’s a faster loading time on the loading screen, but there may be delay, if access to unloaded resources during gameplay is required.</li></ul><h3>Parallel computing and loading</h3><p>It’s simple and mighty. Current mobile devices have a multicore CPU, and Unity, by default, executes all code in the main thread. Unity starts to execute some loading process on other threads. However, it has still a lot of free power that can be used, such as parallel loading resources, http requests, serialize/deserialize data/json, and heavy computing.</p><h3>Check thread pool</h3><p>From the other side, if you use ‘Task’ from C#, you can have too many tasks in queue on the thread pool. As a result, your Task.Delay(TimeSpan.FromSeconds(1)) may complete after 2 seconds, instead of 1. My advice — use a more lightweight async library. It could be <a href="https://github.com/Real-Serious-Games/C-Sharp-Promise">Promises </a>, <a href="https://learn.microsoft.com/en-us/dotnet/api/system.threading.tasks.valuetask-1?view=net-6.0">ValueTask</a>, <a href="https://github.com/Cysharp/UniTask">UniTask</a>, or <a href="https://github.com/neuecc/UniRx">UniRx</a>, though I prefer to use <a href="https://github.com/Cysharp/UniTask">UniTask</a>. They run by default in main threads, which helps you safely use Unity methods in async operations. Also, it allows you to benefit from the full power of classic ‘Task’s with thread pool.</p><p>It is also important know that you can change SynchronisationContext from Unity to ThreadPool, but it will not be immediately operational. Most of small operations are better off being performed on the same SynchronisationContext, without moving to ThreadPool.</p><h3>Bundles compression</h3><p>Unity bundles have three compression options:</p><ul><li>Uncompressed (large size of bundle, faster access)</li><li>LZ4 (medium size of bundle, do not require decompression to use)</li><li>LZMA (smallest size of bundle, require decompression to use, slowest to load)</li></ul><p>I prefer to use LZ4, where we need speed, and LZMA, which is critical by bundle size, for instance, 10 2048x2048 atlases.</p><p>Check your bundles in the addressables settings and other places where bundles are builds.</p><p><a href="https://docs.unity3d.com/530/Documentation/Manual/AssetBundleCompression.html">Bundle compression details</a> <a href="https://forum.unity.com/threads/choosing-the-right-asset-bundle-compression.389650/#post-2584401">Unity forum discussion</a></p><h3>Zenject</h3><p>Here is some advice for Zenject’s users</p><h4>Reflection baking</h4><p>If you still didn’t enable it — do it now. It slightly increases build time because of the baking process. It also boosts your loading time. In our case, The difference with and without Zenject reflection binding is over 3 times as long.</p><p><a href="https://github.com/modesttree/Zenject#reflection-baking">Zenject reflection-baking</a></p><h4>Install phase</h4><p>Zenject allocates memory during the InstallBindings phase. When the already allocated memory runs out — Unity allocates the next batch of memory from RAM. Mid-end devices like the Samsung A51 take ~300ms per next allocation memory from device RAM. For our project, it happened twice during the InstallBindings phase.</p><p>Allocate big amounts of memory at start, saving about 0.5 seconds of loading time on mid-end devices.</p><h3>Conclusion</h3><p>If you check off all the above tips from your to-do list, you can significantly improve your game’s loading time, as well as its startup loading and the loading of scenes. Users will be happy to open your app faster and keep opening your app over and over again.</p><p><em>We hope you found this article helpful and will use it in your projects! If you are interested in joining us, </em><a href="https://www.hypemasters.com/careers"><em>check out our open positions</em></a><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f53611bbea0a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hypemasters/how-to-save-2-sec-loading-time-of-your-game-f53611bbea0a">How to save 2 sec+ loading time of your game</a> was originally published in <a href="https://medium.com/hypemasters">Hypemasters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maps for the World War Armies RTS — a development story]]></title>
            <link>https://medium.com/hypemasters/maps-for-the-world-war-armies-rts-a-development-story-d6a124718a5?source=rss----d3321f4456ee---4</link>
            <guid isPermaLink="false">https://medium.com/p/d6a124718a5</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[games]]></category>
            <category><![CDATA[strategy-games]]></category>
            <dc:creator><![CDATA[Boris Kalmykov]]></dc:creator>
            <pubDate>Wed, 21 Dec 2022 09:00:34 GMT</pubDate>
            <atom:updated>2022-12-27T06:38:56.778Z</atom:updated>
            <content:encoded><![CDATA[<h3>Maps for the World War Armies RTS — a development story</h3><p><em>Article written by </em><a href="https://medium.com/@cptplague"><em>Sergey Kaplin </em></a><em>&amp; edited by </em><a href="https://medium.com/u/7dcd645e76f?source=post_page-----dc7fbaa5b05c--------------------------------"><em>Boris Kalmykov</em></a></p><p>Recently, we’ve introduced a new map, the Lost Stronghold. Our players loved it, and this reaction inspired us to shed light on how we develop maps!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MvIeJ9hnfs46odeA_WB7zA.png" /><figcaption>The Lost Stronghold concept art</figcaption></figure><p><strong>Players always crave new maps, and our mission is to exceed their expectations</strong>.</p><p>Maps keep the gameplay fresh and let players explore new environments. However, new maps evoke the emotions above, and meeting players’ expectations are critical. For instance, if the game’s audience comprises hardcore players and fans of complex manoeuvres, it would be a big mistake to assume that a straightforward map will be well-received.</p><p>Still, there is an exception to every rule. On mobile phones, even with the largest screen size, it would not be easy to control complex multi-level maps with multiple areas branched away from the main zone and resource points. Also, it’s vital to remember that any community has different kinds of players — we want to recognize their interests and expectations! Each player should have the opportunity to enjoy the game.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*A8RylmT8v7QbaTo45QXj2A.png" /><figcaption>The Lost Stronghold level design or a ‘cake’ as we call it</figcaption></figure><p><strong>What do players want?</strong></p><p>There are two ways to make the right choice for a new map, and both of them involve close interaction with the game community:</p><ol><li>Internal data. We look into the game statistics to understand which map players play most often and ask our community to share their thoughts on why the majority of players play on this exact map.</li><li>We ask the community which map and settings they want to see in the next release.</li></ol><p>Only after completing these steps we go ahead with the development of a new map. When creating a map, the developers keep these factors in mind to balance complex gameplay and follow the platform’s specific conditions. To combine these two needs and to maintain a degree of predictability, the developers usually draw inspiration from existing locations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v4VY_6QvgC6VcxpNs5NxDg.png" /><figcaption>The main landmark of the Lost Stronghold map — the Castle</figcaption></figure><p>How we created the Lost Stronghold map:</p><p><strong>Warming up</strong></p><p>It’s no secret that our team is a big fan of Company of Heroes (CoH). It would be odd if we didn’t investigate the experience of other game fans and look into the hundreds of maps created by CoH players for multiplayer battles. The level designer had explored every map there before articulating the vision of our new one.</p><p><strong>Gameplay</strong></p><p>Our studio has many fans of dynamic &amp; fast-paced battles, so upgrading the Coastline (our first, smallest and most popular map) and developing a new map based on it was the next logical step. We used the Coastline as a reference because of its simple tactical design and accessibility to both new and experienced players.</p><p><strong>Visual design</strong></p><p>In the future, we plan on creating more thematic maps so that each of them has a story to tell. The Lost Stronghold is our first shot! Visual components of the map refer to the battlefields of the Eastern Front. The season had to be winter, and, as for the place of action, we decided on a ruined town, referring to the defence of the Brest Fortress and Pavlov’s house.</p><p>We hope that you have enjoyed this article! Join our <a href="https://discord.com/invite/G9EUtwC">Discord </a>and take part in creating the best F2P RTS!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6a124718a5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hypemasters/maps-for-the-world-war-armies-rts-a-development-story-d6a124718a5">Maps for the World War Armies RTS — a development story</a> was originally published in <a href="https://medium.com/hypemasters">Hypemasters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hypemasters insiders: Dmitry Shaposhev, Game Designer]]></title>
            <link>https://medium.com/hypemasters/hypemasters-insiders-dmitry-shaposhev-game-designer-17e170f23dbc?source=rss----d3321f4456ee---4</link>
            <guid isPermaLink="false">https://medium.com/p/17e170f23dbc</guid>
            <category><![CDATA[game-designer]]></category>
            <category><![CDATA[game-industry]]></category>
            <dc:creator><![CDATA[Digna Futika]]></dc:creator>
            <pubDate>Tue, 23 Aug 2022 13:56:54 GMT</pubDate>
            <atom:updated>2022-08-23T14:48:44.188Z</atom:updated>
            <content:encoded><![CDATA[<p>Last month we released World War Armies (WWA) globally. Why did Hypemasters create an RTS game for mobile, and how did we do it? To answer these questions, Hypemasters Insiders spoke to our Game Lead, Dmitry Shaposhev (Dima). Let’s get straight into the interview!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Y3Sub0iVSaLg_U2dGCG_w.jpeg" /></figure><p><strong>Q: Can you briefly share how the process of designing the WWA game worked?<br></strong>A: “What if we make a true RTS game for mobile?” was the initial conversation between Hypemasters founders Sergii and Boris. This question turned into a prototype proving that it can work. My first assignment was to write a concept for a mobile RTS as a complete game. Apparently, I got into the same wavelength with Boris and Sergii, so I was invited to lead the game! :)</p><p>The first concept was inspired by Company of Heroes (CoH) and Clash Royale. As the concepts’ details emerged from the two games, we began to craft the original idea of our game. After about a month, the 1-page idea turned into a full-fledged 56-page design document describing all possible game mechanics (spoiler: about half of the mechanics were never implemented or were thrown out after the prototyping stage. Hello, game dev reality).</p><p>As our team was growing from 1 to 20 over the next six months, we were making features based on the original design document. Then, the magic of game development began — new prototypes of mechanics allowed us to generate new ideas and look at the game from a new perspective. As a result, we finally realised that it was impossible to transfer CoH to mobile phones with minimal changes. We had to find our own way. A long journey of searching for my vision and experimenting with fundamental mechanics began.</p><p>Since we immediately understood we were making an innovative game, we decided to release an MVP version in open beta status on Google Play. It happened eight months after the design document was first drafted. We have been testing all the changes on the players since then — watching how the game performs and gathering feedback. The development process for the game was based on these three pillars: constant alignment with the project vision, data analysis, and player feedback. Our game was globally launched after 1.5 years of bold experiments. Finally, we were ready to show the world what we had accomplished.</p><p><strong>Q: What is it like to work with the team?<br></strong>A: For me, the most important thing is to see and feel the desire of all team members to make a cool product. Sometimes, working in game development is stressful, especially if results are not visible (for example, project metrics aren’t not growing). In these moments, the desire to push forwards and test new hypotheses is the best proof that we are all on the right track. Going to a bar helps as well! That’s where comradery flourishes.</p><p><strong>Q: What were the challenges of designing WWA?<br></strong>A: The main challenge was the lack of references. We had to go through real R&amp;D — a lot of trials and a lot of errors. For example, our tanks fire physical projectiles that can ricochet off the target and destroy another enemy unit on the other side of the map. Maybe that’s what happens in real life, but for a game… These things have to get simplified to avoid WTF moments for our players.</p><p><strong>Q: What is the most valuable feedback that you’ve ever received?<br></strong>A: We have formed a great community of players and they always share their <a href="https://imgur.com/a/H68mnXy">memes</a> and useful <a href="https://imgur.com/a/mSQDLnj">feedback</a>.</p><p><strong>Q: What is the biggest lesson that you have learned?<br></strong>A: The biggest lesson for me is to prioritise bold experiments. In the early stages of a project, it’s essential to make radical changes rather than trying to polish what’s already there. This can drastically change the vision, but it certainly increases your chances of creating a hit.</p><p><strong>Q: How has Hypemasters changed over the years?<br></strong>A: Compared to when I had my first interview, the difference is dramatic. Whenever I tell someone that I work for a startup called Hypemasters and we are almost 40 people, I hear the same reaction “this doesn’t sound like a startup.” However, we still have the spirit of a startup in the “body” of a well-established company and that’s what I love.</p><p><strong>Q: So, what’s next for you?<br></strong>A: Since the beginning of this year, we have decided to start thinking about new games. Initially, this didn’t set me on fire because my whole focus was (and still is) on WWA — I believe that we can continue creating awesome updates for the game for years to come. However, recently I’ve come up with a cool idea and that got me going! Now, I am always looking forward to these discussions and I can’t wait to see what’s next!</p><p><em>Want to see what’s next for you and for the industry? To be challenged and create legendary games? Send your CV now to </em><a href="/service/mailto:join@hypemasters.com"><em>join@hypemasters.com</em></a><em>, and you can become one of our masters!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17e170f23dbc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hypemasters/hypemasters-insiders-dmitry-shaposhev-game-designer-17e170f23dbc">Hypemasters insiders: Dmitry Shaposhev, Game Designer</a> was originally published in <a href="https://medium.com/hypemasters">Hypemasters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mobile RTS interface: the story of how Hypemasters rediscovered the genre]]></title>
            <link>https://medium.com/hypemasters/mobile-rts-interface-the-story-of-how-hypemasters-rediscovered-the-genre-dc7fbaa5b05c?source=rss----d3321f4456ee---4</link>
            <guid isPermaLink="false">https://medium.com/p/dc7fbaa5b05c</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[games]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Boris Kalmykov]]></dc:creator>
            <pubDate>Fri, 12 Aug 2022 13:28:11 GMT</pubDate>
            <atom:updated>2022-08-12T14:32:16.398Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Article written by </em><a href="https://medium.com/u/461b4a51d5c"><em>Boris Kiselev</em></a><em> &amp; edited by </em><a href="https://medium.com/u/7dcd645e76f"><em>Boris Kalmykov</em></a></p><p>For two years, we at <a href="https://www.hypemasters.com/"><strong>Hypemasters</strong></a> have been working on ‘<a href="https://apps.apple.com/us/app/world-war-armies-ww2-pvp-rts/id1506931934"><strong>World War Armies</strong></a>’ — a mobile strategy title. Creating the interface has been one of our main challenges. We needed to find a compromise between classic PC strategy controls and convenience on mobile. Boris Kiselev, UX director at Hypemasters, shares how the studio managed to achieve a balance between the two.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*jCAuQIohWBBdniAu" /><figcaption>Boris Kiselev, UX Director at Hypemasters</figcaption></figure><p>In this article, I will share our experience of creating an interface for a mobile real-time strategy game(RTS). This is a rather unusual combination of genre and platform: there are very few similar examples in the mobile game market. I will talk about the difficulties we encountered in the production process, the mistakes we made and what we learned through this process.</p><h3>Strategy game? What is that?</h3><p>Let’s come to a mutual understanding, to begin with.</p><p>For PC players, RTS means games like <strong>Starcraft, Company of Heroes, Age of Empires, Blitzkrieg, Warhammer 40,000 Dawn of War </strong>etc.</p><p>On mobile devices, a strategy game can be … well, almost anything. Let’s take a look at top <strong>Google Play</strong> games in the <strong>Strategy</strong> category:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4jdxDHUpYWj-WhdV" /></figure><p>The genre boundaries here are blurred. Generally, in mobile Strategy games, the gameplay is focused on developing the base, as well as selecting and upgrading units. In battle (if it exists as a separate activity at all), units usually act independently after being generated, without any player involvement. As a rule, players don’t have direct control over troops.</p><p>For the past two years, we at Hypemasters have been working on bringing the ‘true RTS’ genre to mobile. By ‘true RTS’, we mean a game that has:</p><ul><li>Real-time combat against real opponents</li><li>A big battle map</li><li>A relatively large number of units simultaneously participating in battle</li><li>Direct control of units with free movement</li><li>A tactical element</li></ul><h3><strong>Mission (Im)possible</strong></h3><p>We can all agree, that “reviving the genre” sounds strong.</p><p>But there are a couple of caveats here.</p><p>RTS is one of the most hardcore genres. It implies a huge information load on the player and requires a large number of actions. You have to control several groups of units operating simultaneously in different parts of the map, while not forgetting about building new troops, developing your own economy and monitoring enemy movements.</p><p>To illustrate my point, the average APM (actions per minute) for professional Starcraft players is about 350, and for amateurs, it is about 70. Imagine if you had to perform the same amount of actions, not by clicking the mouse, but by tapping on the screen.</p><p>This is where the main difficulty in transferring RTS controls from PC to smartphones follows. Strategy games as a genre make the most of PC capabilities that mobile devices do not have.</p><p>It’s easy to get discouraged when you compare the functionality of the mouse + keyboard combo to what phones have to offer. See this for yourself:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*sVWEVYEsn24O7zlDqwl5Fw.jpeg" /></figure><p>This list calls into question the very possibility of transferring controls from a PC RTS to a mobile format without losing depth and flexibility.</p><p>Therefore, after some weeping, we were mentally ready to give up a part of the PC heritage in order to squeeze RTS into the mobile format.</p><p>At the same time, it was fundamentally important for us to preserve the spirit of the classic RTS and to find the fine balance between “simplified, but still RTS” and “not at all like a PC strategy”.</p><p>They say that you can find anything on Google Play, and PC-like strategies for phones are no exception. The market, although small, still exists. During our development, we kept an eye on Art of War 3 and Acies: Battle Runes. In both cases, the developers took the path of copying as much of the gameplay as possible from the classic PC strategies. In our opinion, this approach is not optimal, because it does not take into account the peculiarities of mobile platforms.</p><p>We think that in order for RTS to work on mobile, you will need to:</p><ul><li>Reduce the session duration from several hours to 15 minutes max</li><li>Reduce the number of elements that need to be monitored at the same time</li><li>Limit the maximum possible number of units participating in the battle at the same time to 15 on each side</li></ul><p>Now, I will talk about a few of the problems we encountered and how they resulted in our final product being quite different to what we originally had planned.</p><h3>Unit controls</h3><p>In the early days of our game development, we established that units would be controlled directly. Selecting a single unit was supposed to be done by simply tapping on the model. Group selection could be done by using frames or a separate button (spoiler: as a result, almost all players only use single unit selection). We also wanted to keep the screen clean to show more of the game and less of the interface.</p><p>We learned almost immediately that on a phone screen the unit models were too small to tap on them with a finger. Camera zoom-in was not an option in our case:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ok507YVOQx0JMs9T" /></figure><p>Moreover, during the development process, new layers of information were added about the units. We wanted to display this information in battle, in addition to the standard HP.</p><p>In the beginning, the unit UI looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DLm7hYnHQhQLkqEM" /></figure><p>Later, we added portraits for each unit, combined with HP bars (the portrait was filled in by red colour as the unit received damage):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c0639rCe6ZSmMEH6" /></figure><p>The amount of information about the units that we wanted to show in battle increased with each version. As result, for the release, the nameplate included:</p><ul><li>A unit callsign. This is how players can distinguish one tank from another (more on that below)</li><li>A serial number. The first unit of the same type is called NAME-1, the second NAME-2, and so on. In theory, the number should help distinguish units of the same type from one another on the bottom panel.</li><li>A class icon. Knowing exactly what kind of unit is in front of you is not enough, you also need to know how to use this unit. Who is this type good against and not so good against? But what if your enemy has this unit in battle but you have no idea how to play against it? The icon will help.</li><li>Remaining little things: HP, unit level (outside of battle, units can be upgraded, and the one that has a higher level will be stronger in 1v1 combat), reload progress and a veterancy badge.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Tda8to2smzkF5Mdn" /></figure><p>In addition to being displayed on nameplates, all information about the unit is duplicated on its portrait in the bottom panel. This helps players to monitor the state of the units without having to see them on their screen.</p><p>This is what it looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nt28mQBZFc13u_dq" /></figure><p>As a result, players receive comprehensive information about the state of their army and have no difficulty controlling single units. However, there is still work to be done when it comes to group selections. At the moment, few players use them.</p><h3>Identifying units</h3><p>Our chosen setting implies the use of real-life technology models. This is very limiting in terms of visual design. When you have the ability to create units from scratch, you can reflect their functionality through appearance. A pumped-up warrior with a huge shield signal that he is slow and tenacious, and a thin elf with a large bow is seen as painfully striking, but frail physically, etc.</p><p>In our case, such an approach is impossible: any deviations from historically correct models result in military experts feeling excruciating mental pain. The more significant the discrepancies, the more negative reactions they cause. We still get comments from players saying that the shape of the barrel of a particular tank model does not match the real prototype, or that the calibre of the machine gun belt on the infantryman does not match his weapon. Historical accuracy brings about hard limits.</p><p>Fortunately, for the most part, our players are not military experts and, to put it mildly, are poorly versed in the technology of World War II. During playtests, it got ridiculous: one player took the M18 Hellcat (artillery) into battle instead of the M6 ​​Heavy (heavy tank) saying, “Well, 18 must obviously be cooler than 6!”</p><p>Naturally, he lost the very first battle because of his choice of units.</p><p>At the same time, an identification mistake (say, sending infantry to attack an anti-personnel unit) for the player will result in the probable loss of the unit, and for us — the probable loss of the player.</p><p>At first, we tried to make it easier for players to navigate who is who, using different unit portraits in battle. It worked well with infantry, but vehicles of the same type (tanks, for example) still looked alike. Among our team, we called this the “boxes on wheels” problem.</p><p>We then added short callsigns that the player could refer to, in addition to the unit model.</p><p>Finally, after some time, class icons were added to the callsigns. Now, instead of memorising each unit separately, it was enough to figure out the class system once. As a result, we greatly simplified our players’ learning.</p><p>Here is what it looked like before:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vFziQpFTelP8bi81" /></figure><p>And after:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3kJODPVum5TWMBcA" /></figure><h3>The base and unit generation</h3><p>Another good example of how initial ideas change during development is our story about the base. Initially, we agreed that the base building construction on it was an integral part of the ‘true’ RTS experience (this is what our competitors did too). We tried to transfer this mechanic to the mobile format with minimal changes. Therefore, in the early versions of our game, players had to construct specialised buildings, each with its own function: barracks to recruit soldiers, a factory for tanks, storage for resources, and etc. To interact with a building, players had to tap on it. After that a circular menu with action options opened:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f-9w74t8iWIrasUw" /></figure><p>This solution proved to be unviable. Recruiting units is a very frequent action that requires players to constantly move the camera from the battlefield to the base and back, which can be very annoying and distracting.</p><p>In our next iteration, we added a panel with three switchable modes: troops management, unit recruitment and construction. We saw this implemented in <a href="https://play.google.com/store/search?q=Acies%3A%20battle%20runes&amp;c=apps">Acies: battle runes</a>. Constructing a building still required moving the camera to the base, since most buildings could only be built within a small radius of the main building, but now it was possible to hire units at any time:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Fz-mOP586ugvDNzR" /></figure><p>It got better, but operating the base still felt too labour-intensive and distracting. As a result, we took the path of simplification again. Instead of having the opportunity to use different buildings to generate any unit type in any battle, players now had to collect a deck of 8 units before the start of each battle. There were the only units that could be recruited in battle. We simplified the base to become one building. Upgrading the base opens up access to more expensive and advanced units from the deck and at the same speeds up resource growth.</p><h3>Instead of a conclusion</h3><p>We have been following an ambitious goal: to walk the fine line between casual and hardcore, making RTS accessible to mobile players, while preserving the feeling of classic PC strategy games. During the development process, we always had to be flexible. Each game element has gone through many iterations. Some things worked out well from the beginning, and others — did not so well. We still have a lot of work to do: we are only at the beginning of the journey.</p><p>Non-standard mobile projects like ours are always a complex challenge for the whole team. There is nowhere to look for ready-made solutions because they simply do not exist. You have to move through a path of trial, error and experimentation. However, it is these conditions that make it possible to catch the very feeling of being a pioneer and to discover something that no mobile developer has done before. I wish you to experience this feeling often in your work.</p><p>For those of you who want to evaluate the results of our work and the decisions we made, look for World War Armies on <a href="https://play.google.com/store/apps/details?id=com.Hypemasters.rts&amp;hl=en_US">GooglePlay</a> and <a href="https://apps.apple.com/us/app/world-war-armies-ww2-pvp-rts/id1506931934">Apple App Store</a>.</p><p>If you have any questions or want to keep in touch, look for me on <a href="https://www.linkedin.com/in/boris-kiselev/">LinkedIn</a>.</p><p>That’s all from me, thanks for your attention!</p><p>Yours, <a href="https://medium.com/u/461b4a51d5c">Boris Kiselev</a>!</p><p><em>Originally published here: </em><a href="https://app2top.ru/interfaces/interfejs-dlya-mobil-noj-rts-istoriya-o-tom-kak-hypemasters-zanovo-otkry-vala-zhanr-200335.html"><em>https://app2top.ru/interfaces/interfejs-dlya-mobil-noj-rts-istoriya-o-tom-kak-hypemasters-zanovo-otkry-vala-zhanr-200335.html</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc7fbaa5b05c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hypemasters/mobile-rts-interface-the-story-of-how-hypemasters-rediscovered-the-genre-dc7fbaa5b05c">Mobile RTS interface: the story of how Hypemasters rediscovered the genre</a> was originally published in <a href="https://medium.com/hypemasters">Hypemasters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hypemasters insiders — Anton Shilin, Server Developer]]></title>
            <link>https://medium.com/hypemasters/hypemasters-insiders-anton-shilin-server-developer-464b17fd574c?source=rss----d3321f4456ee---4</link>
            <guid isPermaLink="false">https://medium.com/p/464b17fd574c</guid>
            <category><![CDATA[gaming-culture]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[gaming-industry]]></category>
            <dc:creator><![CDATA[Digna Futika]]></dc:creator>
            <pubDate>Thu, 07 Jul 2022 06:41:39 GMT</pubDate>
            <atom:updated>2022-07-28T09:27:19.861Z</atom:updated>
            <content:encoded><![CDATA[<h3>Hypemasters insiders: <strong>Anton Shilin, Server Developer</strong></h3><p>When it comes to professional development, choosing the right company to work for is an important factor. The size of the company matters: working in a small team is different to navigating a large organisation.</p><p>This week, Hypemasters insiders is about <strong>Anton Shilin</strong>, our server developer, who has seen Hypemasters grow from 6 employees to 30+ employees. Anton shares his experience of working at Hypemasters over time, with the company growing and the world situation changing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AtnJA_vdi7uKVAM3d4MxsQ.jpeg" /></figure><p><strong>Q:How has Hypemasters changed since 2019?<br></strong>A: Hypemasters has changed a lot. When I joined, the six of us were huddled in a back room, working on a small idle game. At that time, we were just beginning to understand that we wanted to create ambitious and unique games such as World War Armies.</p><p>Now we have a distributed team of over 30 diverse professionals who work remotely and flexibly . I am definitely satisfied with how the company has evolved and continues to evolve, while maintaining the same values we laid down at the start.</p><p>As the studio grows, so does the number of interactions. I now spend more time talking to the team,, planning, estimating the time to complete new tasks, and monitoring metrics. I have less time than before to write code and complete my own tasks.</p><p><strong>Q:Most valuable feedback for your work?<br></strong>A: This was one of my favourite product reviews: someone left a comment on our social media page saying, “God, a strategy game on a mobile phone :(”. And then 15 minutes later they wrote, ‘Well, it’s worth playing actually”.</p><p>With regards to my work, collecting feedback is not easy, because my work is not usually apparent. It affects the server side of the project, which players usually do not feel in any way. No one pays attention to the continuous communication between the game application and the server. Although behind the scenes, there are multiplayer components, protection from cheaters, the safety of the user’s game progress, and much more.</p><p>However, I realised that non-verbal feedback is actually the real feedback: the comfort of the team and the reliability of the services that I build and maintain. That’s one of the reasons why I like my job so much.</p><p>For example, my area of responsibility includes maintaining the performance of automatic builds of the application. Starting a new working day, I get access to build the latest changes for the game. For the convenience of testing or viewing new art, everyone has the opportunity to launch a build of the game version with the necessary changes, which will automatically become available to anyone in the company.</p><p>Another example: automatic creation of a complete environment for a separate development branch. This is a handy tool for situations where work on a new feature or game balance needs to be isolated so as not to interfere with the work of the rest of the team. It may not sound very clear, but this thing saves a lot of time in the process of working on the game :)</p><p><strong>Q:What is it like to work with a small team?<br></strong>A: Comfortable. Really comfortable. There is no bureaucracy that puts sticks in the wheels, everything is open and independent, we are all equal.</p><p>It’s cool to see when someone is carried away by a task they like, and how new commits appear in the repository at 1 am. I occasionally do this myself. However, a couple of times this was happening in anticipation of releases :D</p><p><strong>Q:With all the instability in the world, how do you feel about your job?<br></strong>A: When the pandemic began, we almost immediately went remote. It took some time to get used to the new mode of work. It was hard to establish the line between work and life in such a period when it was scary to leave the house. But in the end I liked it. With time, I definitely saw more advantages than disadvantages for myself, so I decided not to return to the (by that time already new and equipped) office.</p><p>When the war started, I didn’t panic much. I tried to weigh and calculate my decisions. Therefore, although I was ready to move to Turkey, having tickets in my hands and a Corgi packed for the flight, I decided to stay and relocate after some time. At work, we tried to keep a cool head. There is no point in transferring any panic into your work.</p><p><strong>Q: How do you see Hypemasters in the next 3 years?<br></strong>A: If things go well for us, then I see an international studio doing 2–3 unique projects with more teams. I am impressed by the example of Valve with the ability to easily switch between projects, do what you like best and what you see in the future.</p><p>Of course, it would be great to periodically meet the whole team at one place (not only in Google Meets), so that we do not forget that we remain one big friendly company.</p><p><strong>Q: What’s next for you?<br></strong>A: I want World War Armies to become a hit! This will bring new challenges, difficulties and interesting tasks. No developer likes to stagnate and sit with monotonous tasks overlaid, performing them year after year.</p><p>After that, I would like to start a new project on a new tech stack, to try myself in new technologies.</p><p><em>Chat to us if you are passionate about creating games and want to experience one of the most dynamic cultures in gaming today </em><a href="/service/mailto:join@hypemasters.com"><em>join@hypemasters.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=464b17fd574c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hypemasters/hypemasters-insiders-anton-shilin-server-developer-464b17fd574c">Hypemasters insiders — Anton Shilin, Server Developer</a> was originally published in <a href="https://medium.com/hypemasters">Hypemasters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hypemasters insiders: Kate Safronova, 2D artist]]></title>
            <link>https://medium.com/hypemasters/hypemasters-insiders-kate-safronova-2d-artist-24ec79ccf62d?source=rss----d3321f4456ee---4</link>
            <guid isPermaLink="false">https://medium.com/p/24ec79ccf62d</guid>
            <category><![CDATA[gaming-articles]]></category>
            <category><![CDATA[company-culture]]></category>
            <dc:creator><![CDATA[Digna Futika]]></dc:creator>
            <pubDate>Wed, 08 Jun 2022 16:23:04 GMT</pubDate>
            <atom:updated>2022-06-08T16:35:08.090Z</atom:updated>
            <content:encoded><![CDATA[<p>Ever wondered what it’s really like to work somewhere? We will be sharing a series of interviews with Hypemasters employees to give you a feel of what it’s like to be part of our team. We asked our employees to be as honest as possible with their responses and tried to go beyond the standard “what’s your favourite part of…” type of questions. What did they say? Let’s find out.</p><p>This week, we spoke to <strong>Kate Safronova</strong>, our 2D artist. Kate talked about her journey at Hypemasters over the last 3 years and shared advice for women who are looking to join the gaming industry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*btnfQxkzJ6T6jIY8WrqQwQ.jpeg" /></figure><p><strong>Q: How have Hypemasters changed since 2019?<br></strong>A: Everything has actually transformed with time — games, offices and, most importantly, people! And it’s not about the team members leaving and new team members being hired: it’s about changes within us. I think that the key feature of the company’s culture is the general openness to new ideas. We discuss them in an open manner and embrace the ones that we feel are right. This makes me happy — I know that when I bring something new to the table, it won’t get disregarded, regardless of my rank.</p><p><strong>Q: With all the instability in the world, how do you feel about your job?<br></strong>A: Regardless of COVID or world conflicts, Hypemasters has continued to grow! Back in 2019, I’ve started working in Russia, but now relocated to another country as many of us did. I’ve spent all my life living in one city and it was hard for me to take such a step. It helped me a lot that we were doing this collectively, with great support. One could go crazy with all things happening, but I now see it all as a great adventure!</p><p><strong>Q: What’s the most valuable feedback have you ever received?<br></strong>A: For me, any feedback is valuable, even if it is a poop emoji in slack. The most valuable feedback usually arrives when you mess up somewhere. Sometimes I lose direction in my work and a constructive kick helps me look at fresh ideas. This kind of feedback can be painful, but it makes me stronger. The main thing for me is not to think that I cannot cope with it. You never know what you can do till you try.</p><p><strong>Q: What is it like to work with the team?<br></strong>A: We spend a huge part of our lives at work, so the team can rightfully be considered a second family. And as in any family, creating a positive atmosphere within the team is everyone’s job. In my team everyone is friendly and respectful — we never get to argue! This helps me with my self-confidence. I can offer my ideas and get heard.</p><p>Also, teamwork means passive learning from my colleagues — I learn about things that are not related to my main craft and slowly turn into a multi-specialist. You never know what skill might come in handy, even if it’s the ability to tell ambiguous jokes.</p><p><strong>Q: What is it like to work as a female employee?<br></strong>A: Our current project is aimed at a male audience, so it is not surprising that the development team is mostly male — they are simply interested in the subject of the project.</p><p>But I don’t think that gender somehow affects my work. On the contrary, it helps me to look at the project from the outside and give feedback on how the non-target user sees the game.</p><p>Right now I’m the only girl in the art team, but not the only one in the company. In addition, many women in our company are in charge and know how to manage processes, so many of them have grown into leads by now.</p><p>It’s important to know that not every gaming company has discrimination. Do not set yourself up negatively in advance. Otherwise, it can undermine your self-confidence. How you present yourself plays a big role.</p><p><strong>Q: What’s next for you?<br></strong>A: I joined the company immediately after university as a junior 2D-artist. Every year I have been discovering myself in a new light — as an artist, as an organizer, as a team member and a cultural cell of Hypemasters. My dream is to become an art director of one of our future games. I really want to work with a completely crazy visual style, full of fun and Easter eggs for our players!</p><p><em>Are you interested in joining our team? Visit our </em><a href="https://www.hypemasters.com/careers"><em>careers page</em></a><em> or simply contact us: join@hypemasters.com</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24ec79ccf62d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hypemasters/hypemasters-insiders-kate-safronova-2d-artist-24ec79ccf62d">Hypemasters insiders: Kate Safronova, 2D artist</a> was originally published in <a href="https://medium.com/hypemasters">Hypemasters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leadership at Hypemasters]]></title>
            <link>https://medium.com/hypemasters/leadership-at-hypemasters-6f3e27160a33?source=rss----d3321f4456ee---4</link>
            <guid isPermaLink="false">https://medium.com/p/6f3e27160a33</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[game-development]]></category>
            <dc:creator><![CDATA[Boris Kalmykov]]></dc:creator>
            <pubDate>Thu, 19 May 2022 14:26:31 GMT</pubDate>
            <atom:updated>2022-05-19T14:23:55.164Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article, I tackle the topic of leadership and what it means for our studio.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KXfp0EciHwh-u3u6HNC2hw.png" /><figcaption>A sketch of a Soviet general from <a href="https://play.google.com/store/apps/details?id=com.Hypemasters.rts&amp;hl=en_US">World War Commander</a>, by <a href="https://medium.com/u/8a5c22e7c4cf">Igor Podmogilnikov</a></figcaption></figure><p><em>Disclaimer: I am aware that the topic is vast and has a lot of nuances. This is by no means an attempt to present the universal truth about leadership. Also, this is not an academic article, but rather an article about our practice at Hypemasters.</em></p><p>The topic of leadership is always on my mind. I am a leader myself and I lead other leaders in the company. By sharing my thoughts, I am hoping to bring more transparency into what I expect from our current and future leaders.</p><ul><li><strong>Be a role model</strong> — any leader is always looked up to. “Why have they promoted her/his? What do I need to show to do the same?”. Acting is more powerful than talking. Act the way you want others to act, and show them the way with your behaviour. Want everyone to be friendly with each other? Be friendly yourself!</li><li><strong>Keep company’s priorities in focus</strong> — leadership entails a lot of decision-making. It’s the leaders’ duty to understand the company’s priorities, keep them in focus, convey them to others and guard them.</li><li><strong>Know your people</strong> — a leader must know her/his people’s aspirations, needs and desires. This helps tremendously when thinking about career growth &amp; new initiatives. A good leader will be the first one to put her/his people in line for an interesting project.</li><li><strong>Stay synched</strong> — keeping up to date with how people feel, and what they are working on and offering help is paramount to leaders’ success. Weekly catch-ups — a tool that every leader at Hypemasters uses. It has proven indispensable for keeping a great atmosphere, focus and transparency.</li><li><strong>Be curious</strong> — ask more questions to find any hints towards your secret agenda — helping each member of your team grow.</li><li><strong>Listen </strong>— really listen to what one has to say. Active listening always results in more questions, which leads to a greater depth in any conversation. Do not assume that you know what they mean. Ask more!</li><li><strong>Be transparent</strong> — we operate under strict “full transparency” rules. Unless something is explicitly under an NDA, we are obliged to share any info that answers questions or helps another person.</li><li><strong>Serve </strong>— a leader is the one who serves her/his people, making sure that they have all resources that they need to achieve their goals.</li><li><strong>Help with goals</strong> — help others set and achieve goals. I have seen cases where stellar employees get burned out due to the lack of clear goals. It’s important to help people set themselves goals and sync on progress. Celebrate achieved goals and deconstruct any goals that weren’t achieved.</li><li><strong>Help in taking ownership</strong> — instead of giving out tasks and setting goals, let the person do everything her- or himself. Freedom to choose what we do is foundational for our culture.</li><li><strong>Acknowledge strengths</strong> — each leader should know her/his team’s strengths even more so than weaknesses. Helping team members know and foster their strengths is key to leaders’ success.</li><li><strong>Highlight achievements</strong> — highlighting when people excel is the best way to motivate team members and promote further growth. Praise also increases team awareness of what others are doing and what they are good at.</li><li><strong>Think about team composition</strong> — making sure that the right people are doing the right things, playing to everyone’s strength.</li><li><strong>Hire people who are better than you </strong>— a good leader is smart. A great leader is surrounded by smarter people than her/him. Leaders at Hypemasters strive to hire people who make us stronger and are not afraid to hire people who are better.</li><li><strong>Be decisive</strong> — leaders are the ones calling the shots for both hiring and firing. Being decisive around people matters is of paramount importance in keeping teams healthy and growing.</li><li><strong>Prioritise leadership </strong>— leadership is never secondary to other tasks. In fact, I always say that leaders should do nothing else but whatever is needed to be effective leaders.</li></ul><p>Being a leader is tough. There are no pre-made solutions. It always requires active participation and thinking. Only through experience does one realize what works for her/him and what doesn’t.</p><p>At Hypemasters, we place great importance on hiring the best leaders and, even more so, growing leadership from within. Though we are still in the early stages as a company, I know that our continued investment in leadership is the not-so-secret recipe for our current and future successes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f3e27160a33" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hypemasters/leadership-at-hypemasters-6f3e27160a33">Leadership at Hypemasters</a> was originally published in <a href="https://medium.com/hypemasters">Hypemasters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crisis management at Hypemasters]]></title>
            <link>https://medium.com/hypemasters/crisis-management-at-hypemasters-eb80518c1f74?source=rss----d3321f4456ee---4</link>
            <guid isPermaLink="false">https://medium.com/p/eb80518c1f74</guid>
            <category><![CDATA[crisis-management]]></category>
            <category><![CDATA[gamedev]]></category>
            <dc:creator><![CDATA[Boris Kalmykov]]></dc:creator>
            <pubDate>Wed, 30 Mar 2022 08:30:45 GMT</pubDate>
            <atom:updated>2022-03-30T08:25:21.732Z</atom:updated>
            <content:encoded><![CDATA[<p>Our studio has been founded in 2019 and our team is spread across Europe and Asia. Since the foundation, we’ve had COVID (2020) and the conflict between Russia and Ukraine (2022) to live through. Every crisis had its challenges, but, also, similarities. As a result, we have worked out our principles, do’s and dont’s, for crisis management behavior that I am willing to share.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e5EZg8ZwAu0buLuNebW42A.png" /><figcaption>Our team levels up after every crisis!</figcaption></figure><h3>Do:</h3><ul><li><strong>Recognise the crisis asap</strong>. No point in hiding or waiting. As soon as it’s obvious, get everyone in a room and say that “this is it — we are experiencing an extraordinary situation”. It helps people realise that leadership is not blind to difficulties that everyone is about to experience.</li><li><strong>Speak calmly</strong>. The simple act of remaining calm and using a deep voice can relax people and reduce anxiety.</li><li><strong>Be kind</strong>. Crises are extraordinary events. It’s important to recognise that people need warmth and kindness during these events in order to persist.</li><li><strong>Stay open</strong>. This may be the most valuable thing a leader can do. Getting on a 1x1 call and listening to a person allows them to open up, address their fears and get on that cool-calm-collected train like nothing else.</li><li><strong>Focus on consequences</strong>. Crises produce a lot of noise. Get your tunnel vision goggles on and concentrate only on what matters to you and your colleagues. Filtering through the noise helps to preserve the energy so needed for good decisions during tough times. Listening to all the noise is draining and won’t help anyone.</li><li><strong>Share facts</strong>. Ask the team to be mindful of what they are sharing with others. We don’t want to waste our energy on discussing unverified sources. Fact check before sharing.</li><li><strong>Focus groups</strong>. Crises cannot be resolved or overcome by one leader. Creating focus groups helps to spread the burden and get more opinions on the decision-making table.</li><li><strong>Stay united</strong>. Get the team working together and agree on decisions. Avoid making decisions without farming for dissent. Unilateral decisions can lead to public arguments and can worsen the chaos.</li><li><strong>Keep everyone updated</strong>. Even if there are no decisions, it’s important to give updates. It gives reassurance that the company actually cares about what’s happening.</li><li><strong>Business as usual</strong>. As much as possible and as quickly as possible. Work is a safe haven, a place where we can be creative and meaningful. Work helps to preserve sanity.</li></ul><h3>Do not:</h3><ul><li><strong>Constantly chat about the issue</strong>. It never helps or solves any problems.</li><li><strong>Rush into decisions.</strong> During crises, everything changes fast. Acting too quickly might lead to counterproductive outcomes.</li><li><strong>Talk politics</strong>. Political debates are counterproductive to doing business or solving problems. Avoid judging and discussing the political side of crises. It can only lead to negative effects and internal divisions (people are bound to have different opinions). Concentrate on people and help them.</li></ul><p>Lastly, I want to thank our masters of Hype — during these tough times, every person has shown amazing character, teamwork, and resilience. As a result, we have continued to achieve our goals and I am grateful for that.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb80518c1f74" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hypemasters/crisis-management-at-hypemasters-eb80518c1f74">Crisis management at Hypemasters</a> was originally published in <a href="https://medium.com/hypemasters">Hypemasters</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>