-
Notifications
You must be signed in to change notification settings - Fork 6
Expand file tree
/
Copy pathtest_cases.txt
More file actions
33 lines (27 loc) · 1.15 KB
/
test_cases.txt
File metadata and controls
33 lines (27 loc) · 1.15 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
This will just be a running list of things that should be checked before creating a release
Basics:
Can place a new avatar
Can control an avatar
Can disconnect from an avatar
Can rename an avatar
Can change the default name of an avatar and not break everything
ARDU:
Can rename an ARDU
Can deploy an avatar from an ARDU
Death:
Can die in an avatar without gameover
Player death ends game
Destruction of ACC kicks player out of avatar
Can place an avatar after one has been destroyed, and it keep incrementing up in numbers
GUI:
An ARDU is listed in the selection GUI, if it hasn't spawned an avatar
- If it has the avatar is shown and not the ARDU
- If the ARDU has been destroyed, then the avatar will be in the list
Can't control an avatar from another avatar
Can't rename an ARDU from an ACC
An avatar can be renamed
An avatar can't be named the same as another avatar
An avatar can't be named an empty string
Commands to get stuff:
/c game.player.force.research_all_technologies()
/c game.player.insert{name="avatar", count="25"} ; game.player.insert{name="avatar-control-center", count="5"} ; game.player.insert{name="avatar-remote-deployment-unit", count="5"}