Weekly Report #52
[h3]Hello Stalkers! [/h3]
Christmas is coming soon! For many of you, it's a time of rest, meeting your family (even virtual), and of course - gifts!
Before we go for a well-deserved rest ourselves, we still have a few things to do. More specifically, it is about introducing a lot of corrections and novelties to Chernobylite to make this Christmas more enjoyable for you.
We will also take this opportunity to show you what the work of a game tester in our company is all about. We hope that it will be not only interesting, but also informative - after all, everyone who wants to take the first step in the gaming industry usually starts this way (but not necessarily).
[h3]Little UI cleanup[/h3]
First, we decided to do a little cleanup with the UI. For this purpose, we removed the weapon statistics in the recycler and fixed them not working in the storage. We also got rid of a bug where the gas mask was still visible in Igor's hand after removing the gas mask (e.g. after being moved to the storage).
This isn’t new yet, but we have already started working on updating the note system. We’re testing many solutions that are not only pleasant to the eyes but also useful. This includes the ability to resize notes and keep background effects while viewing notes. There is a bit of it so we will discuss it for a while but we think it will be worth waiting for the final result.
[h3]Without a detailed map, don't move[/h3]
A little mention of something big. While making some adjustments to the game, we also looked at probably one of the most essential elements of the game - maps. As you can see, the Moscow Eye map will be greatly enriched with additional elements, making it clearer and more convenient to use. It includes adding a few missing buildings, water sources, fences, and a clearer outline of the level boundaries.

Similar changes await for Pripyat Port….

...and Kopachi.

[h3]Views of the power plant at night[/h3]
This point looks like a gaggle to feast your eyes a bit. However, this is actually one of the effects of our in-game fix work.
We fixed a minor problem that was bothering us a bit. Namely, we have reduced the "strength" of the lights on the building, so that they should not shine through the trees.

Additionally, we reduced their brightness a bit, so they blend in better with the background. We also added missing lights on the chimneys.

[h3]Quick overview[/h3]
And how about minor and major improvements and news that you suggested to us? Among them there are:
And perhaps the most important change: added quick save and quick load under F5 / F8 keys.
F5 will now save the game in the quick save slot, while F8 will load the game directly from that slot. The quick save slot is also available in the load game menu.
[h3] Searching for the bugs [/h3]
Every week we provide you with a solid dose of information about what stage Chernobylite is at. Most of the reports are descriptions of bugs that have been caught in the game. Of course, a lot of your credit for that is. However, we cannot forget about our silent heroes as well.
Meet Sebastian Rojek, our game tester. It is he who spends every day catching and reporting every, even the smallest, error in the game. But since we have such a huge help from your side (meaning our players), he also tries to find the ones you’re reporting. All this so that we can provide you with a product free of defects (hopefully).

It is said that the tester's work is repetitive and can be tedious. However, as Sebastian says, he is lucky that he didn’t fall into a routine during this project. To some extent, thanks to you as well. - We are working on Early Access, which slightly increases the dynamics and the way we run the project. Of course, we have a work schedule that we stick to, but at the same time we have to respond to feedback and errors reported by the gaming community - he says. - My day looks completely different a few days after the megapatch was released, when we focus on community feedback, and completely different a few days before, where we are still struggling with defects in completely new aspects of the game.
What is the tester's working day like? The first thing to do is download the latest version of the game with the latest fixes. Sebastian admits that there were days when he could afford to fence the whole project to see if previously reported bugs were fixed, and then he focused on specific mechanics or other aspects of the game that needed improvement.
- Currently, the project is so large that the work must be divided and organized. We devote part of the day to player reports because it is a valuable source of knowledge about the bugs and problems they encounter. Later, depending on the situation, either I make sure that our colleagues from other departments' corrections have had the desired effect, or we check if any of the patches have broken other elements of the game, or we perform functional tests of new or changed game mechanics.

It's time to deal with one of the biggest myths in the industry: a tester's job is not just about playing games and flipping a lot of money! Sebastian admits that such an image often appears in the minds of people outside the industry, and also, unfortunately, in some people already working in gamedev. - My work is largely based on previously prepared test documentation, collected information about the progress of work from individual departments, prepared checklists and a lot of organizational work so that the time later used for testing brings the best possible results - he says.
Speaking of bug reporting, each report should contain both a general description of the problem and the most accurate information about the steps leading to it, where it occurs, attach a screenshot or a video file with a record of the error. - Sometimes these are simple things that require looking at a given place, sometimes they are much more difficult cases, the reproduction of which requires a very specific positioning or reproducing even several dozen steps. It would probably be more difficult, but we have the right tools to make our work easier. Yes, we have cheats - admits Sebastian without any shame.

Do the testers, like the rest of the team, face difficulties in their work? According to Sebastian, in this case it is better to talk about challenges than difficulties. And he adds that in testing work, you are a bit at the center of everything that happens in the project. - Some departments cooperate with each other only to a limited extent. The tester works with everyone. It checks functionality, sound, graphics, optimization, compliance with design, etc. - says Sebastian. - You have to be careful with work and organize it well, because chaos can sneak in very easily. It may sound funny, but you have to "test" different approaches and learn from "mistakes" - he adds.
Reported defect priorities are reflected from two reference points. The first is to influence the project as a product that needs to be completed and released, the second is Early Access and the people who buy and play Chernobylite all the time. - We have to keep both of these things in mind. The defect, which may be small in the scale of the project, can completely spoil the gameplay experience of people downloading the new patch from Steam - emphasizes Sebastian.
Coming back to the issue of cooperation between the tester and the team, it is worth paying attention to one more thing: there is a belief that developers treat testers as a necessary evil. Because they catch bugs that need to be patched, and this only extends the game production process. Sebastian recalls having dealt with such situations over the years. - In my experience of working on games, there have been a lot of people who could throw meat at the tester, and "you just spoil, you would do something useful" isn’t the worst that can be heard - he admits. At the same time, he points out that the defects found by testers are the result of a mistake made, for example, by a programmer or designer, and they are often sensitive to their work being "picked on".

According to Sebastian, the cooperation depends largely on the tester himself. - It can build an atmosphere of cooperation and a common goal or conflict and criticism of someone else's work. You have to be in the back of your head all the time that you talk to people who spend many hours on their contribution to the project, so it's best not to be guided by emotions, and only consider arguments and dry facts - he says.
Of course - as he points out - the tester should have his own opinion and be able to assess many things himself. At the same time, it should also be able to shift the weight of the conversation towards solving the problem and extinguishing a potential conflict, not its flare-up. - You have to be able to conduct a dialogue in which the end result is a better shape of the project. I think people who can't handle it will only get frustrated in this profession or the industry in general, because it works both ways - says Sebastian.
- For me, working at Chernobylite is very fun in this respect, because we are a small team, so these relationships are in many cases direct and intense. We managed to develop a good workflow quite quickly and it has a good impact on the project. A lot of us are enthusiasts and sometimes you have the impression that they approach more interesting reported defects with curiosity than anger - he emphasizes.

fot. PatHecke
Are there any unusual situations in this job, as in any other? Naturally. In fact, it is required that such happen. And it's even better if game tester causes it himself. Sebastian admits that imagination is important in this work. - Sometimes you need a flash of genius and sometimes you have to do really stupid things. I can still remember the look of Arthur Fojcik who asked me why I was shooting dead bodies shortly after I reported a bug where shooting soldiers' bodies in Chernobylite was generating extra loot.
[h3]"It's not a bug, it's a feature"[/h3]
Sebastian brings up one more anecdote that gives shivers down his back: - I used to think that a new event was added to the game that made the level pools full of blood. When I tried to find out what the event was it turned out to be a water display problem. Maybe that was the problem, maybe it was fixed and gone. For me, this will forever remain one of the darkest events in Chernobylite.

We ourselves regret that this "bug" has been fixed. :(
[h3]That's it for today![/h3]
Take care, Stalkers!
Christmas is coming soon! For many of you, it's a time of rest, meeting your family (even virtual), and of course - gifts!
Before we go for a well-deserved rest ourselves, we still have a few things to do. More specifically, it is about introducing a lot of corrections and novelties to Chernobylite to make this Christmas more enjoyable for you.
We will also take this opportunity to show you what the work of a game tester in our company is all about. We hope that it will be not only interesting, but also informative - after all, everyone who wants to take the first step in the gaming industry usually starts this way (but not necessarily).
[h3]Little UI cleanup[/h3]
First, we decided to do a little cleanup with the UI. For this purpose, we removed the weapon statistics in the recycler and fixed them not working in the storage. We also got rid of a bug where the gas mask was still visible in Igor's hand after removing the gas mask (e.g. after being moved to the storage).
This isn’t new yet, but we have already started working on updating the note system. We’re testing many solutions that are not only pleasant to the eyes but also useful. This includes the ability to resize notes and keep background effects while viewing notes. There is a bit of it so we will discuss it for a while but we think it will be worth waiting for the final result.
[h3]Without a detailed map, don't move[/h3]
A little mention of something big. While making some adjustments to the game, we also looked at probably one of the most essential elements of the game - maps. As you can see, the Moscow Eye map will be greatly enriched with additional elements, making it clearer and more convenient to use. It includes adding a few missing buildings, water sources, fences, and a clearer outline of the level boundaries.

Similar changes await for Pripyat Port….

...and Kopachi.

[h3]Views of the power plant at night[/h3]
This point looks like a gaggle to feast your eyes a bit. However, this is actually one of the effects of our in-game fix work.
We fixed a minor problem that was bothering us a bit. Namely, we have reduced the "strength" of the lights on the building, so that they should not shine through the trees.

Additionally, we reduced their brightness a bit, so they blend in better with the background. We also added missing lights on the chimneys.

[h3]Quick overview[/h3]
And how about minor and major improvements and news that you suggested to us? Among them there are:
- removed unnecessary fill after removing sharpen option in advanced video settings
- fixed the pop-up that sometimes went out of frame
- added the ability to select/deselect a marker on the map with LMB
- moved the shader viewmode to F6 key
- added hero breathing status while sprinting
- updated stats for items used by companions
- fixed the button icons on the map widget
And perhaps the most important change: added quick save and quick load under F5 / F8 keys.
F5 will now save the game in the quick save slot, while F8 will load the game directly from that slot. The quick save slot is also available in the load game menu.
[h3] Searching for the bugs [/h3]
Every week we provide you with a solid dose of information about what stage Chernobylite is at. Most of the reports are descriptions of bugs that have been caught in the game. Of course, a lot of your credit for that is. However, we cannot forget about our silent heroes as well.
Meet Sebastian Rojek, our game tester. It is he who spends every day catching and reporting every, even the smallest, error in the game. But since we have such a huge help from your side (meaning our players), he also tries to find the ones you’re reporting. All this so that we can provide you with a product free of defects (hopefully).

It is said that the tester's work is repetitive and can be tedious. However, as Sebastian says, he is lucky that he didn’t fall into a routine during this project. To some extent, thanks to you as well. - We are working on Early Access, which slightly increases the dynamics and the way we run the project. Of course, we have a work schedule that we stick to, but at the same time we have to respond to feedback and errors reported by the gaming community - he says. - My day looks completely different a few days after the megapatch was released, when we focus on community feedback, and completely different a few days before, where we are still struggling with defects in completely new aspects of the game.
What is the tester's working day like? The first thing to do is download the latest version of the game with the latest fixes. Sebastian admits that there were days when he could afford to fence the whole project to see if previously reported bugs were fixed, and then he focused on specific mechanics or other aspects of the game that needed improvement.
- Currently, the project is so large that the work must be divided and organized. We devote part of the day to player reports because it is a valuable source of knowledge about the bugs and problems they encounter. Later, depending on the situation, either I make sure that our colleagues from other departments' corrections have had the desired effect, or we check if any of the patches have broken other elements of the game, or we perform functional tests of new or changed game mechanics.

It's time to deal with one of the biggest myths in the industry: a tester's job is not just about playing games and flipping a lot of money! Sebastian admits that such an image often appears in the minds of people outside the industry, and also, unfortunately, in some people already working in gamedev. - My work is largely based on previously prepared test documentation, collected information about the progress of work from individual departments, prepared checklists and a lot of organizational work so that the time later used for testing brings the best possible results - he says.
Speaking of bug reporting, each report should contain both a general description of the problem and the most accurate information about the steps leading to it, where it occurs, attach a screenshot or a video file with a record of the error. - Sometimes these are simple things that require looking at a given place, sometimes they are much more difficult cases, the reproduction of which requires a very specific positioning or reproducing even several dozen steps. It would probably be more difficult, but we have the right tools to make our work easier. Yes, we have cheats - admits Sebastian without any shame.

Do the testers, like the rest of the team, face difficulties in their work? According to Sebastian, in this case it is better to talk about challenges than difficulties. And he adds that in testing work, you are a bit at the center of everything that happens in the project. - Some departments cooperate with each other only to a limited extent. The tester works with everyone. It checks functionality, sound, graphics, optimization, compliance with design, etc. - says Sebastian. - You have to be careful with work and organize it well, because chaos can sneak in very easily. It may sound funny, but you have to "test" different approaches and learn from "mistakes" - he adds.
Reported defect priorities are reflected from two reference points. The first is to influence the project as a product that needs to be completed and released, the second is Early Access and the people who buy and play Chernobylite all the time. - We have to keep both of these things in mind. The defect, which may be small in the scale of the project, can completely spoil the gameplay experience of people downloading the new patch from Steam - emphasizes Sebastian.
Coming back to the issue of cooperation between the tester and the team, it is worth paying attention to one more thing: there is a belief that developers treat testers as a necessary evil. Because they catch bugs that need to be patched, and this only extends the game production process. Sebastian recalls having dealt with such situations over the years. - In my experience of working on games, there have been a lot of people who could throw meat at the tester, and "you just spoil, you would do something useful" isn’t the worst that can be heard - he admits. At the same time, he points out that the defects found by testers are the result of a mistake made, for example, by a programmer or designer, and they are often sensitive to their work being "picked on".

According to Sebastian, the cooperation depends largely on the tester himself. - It can build an atmosphere of cooperation and a common goal or conflict and criticism of someone else's work. You have to be in the back of your head all the time that you talk to people who spend many hours on their contribution to the project, so it's best not to be guided by emotions, and only consider arguments and dry facts - he says.
Of course - as he points out - the tester should have his own opinion and be able to assess many things himself. At the same time, it should also be able to shift the weight of the conversation towards solving the problem and extinguishing a potential conflict, not its flare-up. - You have to be able to conduct a dialogue in which the end result is a better shape of the project. I think people who can't handle it will only get frustrated in this profession or the industry in general, because it works both ways - says Sebastian.
- For me, working at Chernobylite is very fun in this respect, because we are a small team, so these relationships are in many cases direct and intense. We managed to develop a good workflow quite quickly and it has a good impact on the project. A lot of us are enthusiasts and sometimes you have the impression that they approach more interesting reported defects with curiosity than anger - he emphasizes.

fot. PatHecke
Are there any unusual situations in this job, as in any other? Naturally. In fact, it is required that such happen. And it's even better if game tester causes it himself. Sebastian admits that imagination is important in this work. - Sometimes you need a flash of genius and sometimes you have to do really stupid things. I can still remember the look of Arthur Fojcik who asked me why I was shooting dead bodies shortly after I reported a bug where shooting soldiers' bodies in Chernobylite was generating extra loot.
[h3]"It's not a bug, it's a feature"[/h3]
Sebastian brings up one more anecdote that gives shivers down his back: - I used to think that a new event was added to the game that made the level pools full of blood. When I tried to find out what the event was it turned out to be a water display problem. Maybe that was the problem, maybe it was fixed and gone. For me, this will forever remain one of the darkest events in Chernobylite.

We ourselves regret that this "bug" has been fixed. :(
[h3]That's it for today![/h3]
Take care, Stalkers!