1
00:00:05,080 --> 00:00:07,980
The process of releasing updates 
is not a simple one.

2
00:00:07,980 --> 00:00:09,880
It consists of multiple stages.

3
00:00:09,880 --> 00:00:14,260
In the language of developers,
any game update is referred to as a release.

4
00:00:14,260 --> 00:00:17,440
This should not be confused
with the official release of the game.

5
00:00:17,680 --> 00:00:20,540
The process starts 
with the assignment of the tasks,

6
00:00:20,540 --> 00:00:24,560
and ends with the announcement...
“A new update has been released”.

7
00:00:24,560 --> 00:00:27,060
But what happens in between those two points?

8
00:00:27,380 --> 00:00:29,780
A release can include several tasks.

9
00:00:29,780 --> 00:00:35,000
These can be new features, new functionalities,
bug fixes, or a combination of these.

10
00:00:35,000 --> 00:00:38,680
The lead developers advise
on which releases should be implemented,

11
00:00:38,680 --> 00:00:44,100
and the Product Manager will then decide
which of these will be implemented, and in which order.

12
00:00:44,380 --> 00:00:47,520
Before the final version of the release 
reaches the “master”,

13
00:00:47,520 --> 00:00:50,780
which is the main server that runs 
the Closed­ Beta­ Test,

14
00:00:50,780 --> 00:00:55,260
a preupdate version is released
on a separate Release Candidate server.

15
00:00:55,260 --> 00:01:00,080
This is the first step of the process,
and usually takes about 1­ or 2 days.

16
00:01:00,500 --> 00:01:04,080
Our testers then check the “release candidate”
for critical errors,

17
00:01:04,080 --> 00:01:07,600
and to see whether it does what it should
be doing, properly.

18
00:01:07,610 --> 00:01:10,350
In the meantime, 
the community manager prepares a list

19
00:01:10,350 --> 00:01:14,550
with the upcoming changes and patch notes,
to notify the players.

20
00:01:14,550 --> 00:01:18,740
If the test gives positive results,
the changes reach the primary server.

21
00:01:18,740 --> 00:01:21,500
Of course, we must still be prepared 
for hot fixes.

22
00:01:21,500 --> 00:01:26,520
A hot fix is an adjustment
to fix unforeseen problems in critical cases.

23
00:01:26,520 --> 00:01:29,140
Once we’ve made sure 
everything works as intended,

24
00:01:29,140 --> 00:01:31,100
the update release task is closed,

25
00:01:31,100 --> 00:01:33,800
and the development team 
prepares for the next update.

26
00:01:34,080 --> 00:01:37,920
Tanki X applies the concept 
of continuous releases,

27
00:01:37,920 --> 00:01:42,380
which is why the closed beta testers
are experiencing so many restarts.

28
00:01:42,400 --> 00:01:46,780
Each restart is an update,
a release with a number of small changes,

29
00:01:46,780 --> 00:01:48,140
or server maintenance.

30
00:01:48,140 --> 00:01:51,960
Daily releases allow us to quickly assess 
the impact of that change,

31
00:01:51,960 --> 00:01:53,520
and adjust accordingly.

32
00:01:53,960 --> 00:01:57,720
So why don’t we announce 
every single small update we release?

33
00:01:57,940 --> 00:02:02,800
We split releases into three categories:
functional, technical and experimental.

34
00:02:03,080 --> 00:02:06,760
The technical releases
involve changes to the client and servers.

35
00:02:06,770 --> 00:02:11,570
For example, adding new logs into the game
to help us analyze player activity.

36
00:02:11,570 --> 00:02:16,290
Experimental releases are the ones
that won’t necessarily make it into the game.

37
00:02:16,540 --> 00:02:18,920
First they need to be stress tested.

38
00:02:18,920 --> 00:02:22,040
Functional releases 
change the functionality of the game

39
00:02:22,040 --> 00:02:23,880
in a way that players see.

40
00:02:23,900 --> 00:02:27,820
That includes new content, graphics,
and interface updates,

41
00:02:27,820 --> 00:02:31,620
as well as effects and animations,
equipment balance, and others.

42
00:02:31,620 --> 00:02:35,300
This is the only type of release
that is accompanied by patch notes.

43
00:02:38,240 --> 00:02:41,780
It’s only been 20 days 
since the Closed Beta Quest kicked off,

44
00:02:41,780 --> 00:02:46,900
and the milestone of one million,
three hundred and fifty thousand tanks destroyed,

45
00:02:46,900 --> 00:02:48,400
has already been hit.

46
00:02:48,400 --> 00:02:51,400
This means that 3 rewards 
have already been secured,

47
00:02:51,400 --> 00:02:54,040
with the fourth milestone approaching fast.

48
00:02:54,040 --> 00:02:55,600
So, here’s what’s next!

49
00:02:55,959 --> 00:02:59,799
The fifth milestone of the Beta Quest
will be a new feature -­ avatars!

50
00:02:59,800 --> 00:03:02,740
This feature will allow you 
to set an Avatar for yourself.

51
00:03:03,120 --> 00:03:07,500
It will be displayed next to your nickname
on the battle scoreboard, chat and profile.

52
00:03:07,500 --> 00:03:11,220
We will start developing the rewards
as soon as the milestone is reached,

53
00:03:11,220 --> 00:03:13,660
and will add them once they re done.

54
00:03:13,660 --> 00:03:16,069
The sixth milestone is a unique hull modification

55
00:03:16,069 --> 00:03:19,530
— an awesome modification
to one of the most popular hulls in the CBT!

56
00:03:19,530 --> 00:03:23,410
The sight of it will fill your opponents 
with fear and awe!

57
00:03:23,540 --> 00:03:25,280
As the number of testers grows,

58
00:03:25,280 --> 00:03:28,960
each successive milestone 
requires more tanks to be destroyed.

59
00:03:28,960 --> 00:03:31,780
To see the number needed 
to reach the next milestone,

60
00:03:31,780 --> 00:03:35,920
and to check the overall progress,
visit the Closed Beta Quest website.

61
00:03:36,360 --> 00:03:39,620
Remember, Beta Quest participants
will receive their rewards

62
00:03:39,620 --> 00:03:41,580
at the start of the Open Beta Test,

63
00:03:41,580 --> 00:03:45,820
and these rewards will be theirs to keep,
even after the release of the game.

64
00:03:48,260 --> 00:03:52,080
Like this video and stay up to date 
by subscribing to our channels.

65
00:03:52,140 --> 00:03:53,180
See you next time![]