phd-thesis/AppendixB.html at main · haakmal/phd-thesis · GitHub

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
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
<!DOCTYPE html>
<html lang="" xml:lang="">
<head>

  <meta charset="utf-8" />
  <meta http-equiv="X-UA-Compatible" content="IE=edge" />
  <title>B Appendix | Design by Play</title>
  <meta name="description" content="B Appendix | Design by Play" />
  <meta name="generator" content="bookdown 0.33 and GitBook 2.6.7" />

  <meta property="og:title" content="B Appendix | Design by Play" />
  <meta property="og:type" content="book" />


  <meta name="twitter:card" content="summary" />
  <meta name="twitter:title" content="B Appendix | Design by Play" />


<meta name="author" content="Haider Ali Akmal" />


  <meta name="viewport" content="width=device-width, initial-scale=1" />
  <meta name="apple-mobile-web-app-capable" content="yes" />
  <meta name="apple-mobile-web-app-status-bar-style" content="black" />


<link rel="prev" href="AppendixA.html"/>
<link rel="next" href="AppendixC.html"/>
<script src="libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/fuse.js@6.4.6/dist/fuse.min.js"></script>
<link href="libs/gitbook-2.6.7/css/style.css" rel="stylesheet" />
<link href="libs/gitbook-2.6.7/css/plugin-table.css" rel="stylesheet" />
<link href="libs/gitbook-2.6.7/css/plugin-bookdown.css" rel="stylesheet" />
<link href="libs/gitbook-2.6.7/css/plugin-highlight.css" rel="stylesheet" />
<link href="libs/gitbook-2.6.7/css/plugin-search.css" rel="stylesheet" />
<link href="libs/gitbook-2.6.7/css/plugin-fontsettings.css" rel="stylesheet" />
<link href="libs/gitbook-2.6.7/css/plugin-clipboard.css" rel="stylesheet" />


<link href="libs/anchor-sections-1.1.0/anchor-sections.css" rel="stylesheet" />
<link href="libs/anchor-sections-1.1.0/anchor-sections-hash.css" rel="stylesheet" />
<script src="libs/anchor-sections-1.1.0/anchor-sections.js"></script>


<style type="text/css">
pre > code.sourceCode { white-space: pre; position: relative; }
pre > code.sourceCode > span { display: inline-block; line-height: 1.25; }
pre > code.sourceCode > span:empty { height: 1.2em; }
.sourceCode { overflow: visible; }
code.sourceCode > span { color: inherit; text-decoration: inherit; }
pre.sourceCode { margin: 0; }
@media screen {
div.sourceCode { overflow: auto; }
}
@media print {
pre > code.sourceCode { white-space: pre-wrap; }
pre > code.sourceCode > span { text-indent: -5em; padding-left: 5em; }
}
pre.numberSource code
  { counter-reset: source-line 0; }
pre.numberSource code > span
  { position: relative; left: -4em; counter-increment: source-line; }
pre.numberSource code > span > a:first-child::before
  { content: counter(source-line);
    position: relative; left: -1em; text-align: right; vertical-align: baseline;
    border: none; display: inline-block;
    -webkit-touch-callout: none; -webkit-user-select: none;
    -khtml-user-select: none; -moz-user-select: none;
    -ms-user-select: none; user-select: none;
    padding: 0 4px; width: 4em;
    color: #aaaaaa;
  }
pre.numberSource { margin-left: 3em; border-left: 1px solid #aaaaaa;  padding-left: 4px; }
div.sourceCode
  {   }
@media screen {
pre > code.sourceCode > span > a:first-child::before { text-decoration: underline; }
}
code span.al { color: #ff0000; font-weight: bold; } /* Alert */
code span.an { color: #60a0b0; font-weight: bold; font-style: italic; } /* Annotation */
code span.at { color: #7d9029; } /* Attribute */
code span.bn { color: #40a070; } /* BaseN */
code span.bu { color: #008000; } /* BuiltIn */
code span.cf { color: #007020; font-weight: bold; } /* ControlFlow */
code span.ch { color: #4070a0; } /* Char */
code span.cn { color: #880000; } /* Constant */
code span.co { color: #60a0b0; font-style: italic; } /* Comment */
code span.cv { color: #60a0b0; font-weight: bold; font-style: italic; } /* CommentVar */
code span.do { color: #ba2121; font-style: italic; } /* Documentation */
code span.dt { color: #902000; } /* DataType */
code span.dv { color: #40a070; } /* DecVal */
code span.er { color: #ff0000; font-weight: bold; } /* Error */
code span.ex { } /* Extension */
code span.fl { color: #40a070; } /* Float */
code span.fu { color: #06287e; } /* Function */
code span.im { color: #008000; font-weight: bold; } /* Import */
code span.in { color: #60a0b0; font-weight: bold; font-style: italic; } /* Information */
code span.kw { color: #007020; font-weight: bold; } /* Keyword */
code span.op { color: #666666; } /* Operator */
code span.ot { color: #007020; } /* Other */
code span.pp { color: #bc7a00; } /* Preprocessor */
code span.sc { color: #4070a0; } /* SpecialChar */
code span.ss { color: #bb6688; } /* SpecialString */
code span.st { color: #4070a0; } /* String */
code span.va { color: #19177c; } /* Variable */
code span.vs { color: #4070a0; } /* VerbatimString */
code span.wa { color: #60a0b0; font-weight: bold; font-style: italic; } /* Warning */
</style>

<style type="text/css">
/* Used with Pandoc 2.11+ new --citeproc when CSL is used */
div.csl-bib-body { }
div.csl-entry {
  clear: both;
}
.hanging div.csl-entry {
  margin-left:2em;
  text-indent:-2em;
}
div.csl-left-margin {
  min-width:2em;
  float:left;
}
div.csl-right-inline {
  margin-left:2em;
  padding-left:1em;
}
div.csl-indent {
  margin-left: 2em;
}
</style>

<link rel="stylesheet" href="style.css" type="text/css" />
</head>

<body>


  <div class="book without-animation with-summary font-size-2 font-family-1" data-basepath=".">

    <div class="book-summary">
      <nav role="navigation">

<ul class="summary">
<li><a href="./">Design by Play</a></li>

<li class="divider"></li>
<li class="chapter" data-level="" data-path="index.html"><a href="index.html"><i class="fa fa-check"></i>Note from Author</a></li>
<li class="part"><span><b>Preface</b></span></li>
<li class="chapter" data-level="" data-path="declaration.html"><a href="declaration.html"><i class="fa fa-check"></i>Declaration</a></li>
<li class="chapter" data-level="" data-path="acknowledgements.html"><a href="acknowledgements.html"><i class="fa fa-check"></i>Acknowledgements</a></li>
<li class="chapter" data-level="" data-path="abstract.html"><a href="abstract.html"><i class="fa fa-check"></i>Abstract</a></li>
<li class="chapter" data-level="" data-path="dedication.html"><a href="dedication.html"><i class="fa fa-check"></i>Dedication</a></li>
<li class="chapter" data-level="" data-path="quote.html"><a href="quote.html"><i class="fa fa-check"></i>Quote</a></li>
<li class="part"><span><b>I Introduction</b></span></li>
<li class="chapter" data-level="1" data-path="Chapter1.html"><a href="Chapter1.html"><i class="fa fa-check"></i><b>1</b> An Unorthodox Introduction</a>
<ul>
<li class="chapter" data-level="1.1" data-path="Chapter1.html"><a href="Chapter1.html#a-starting-point"><i class="fa fa-check"></i><b>1.1</b> A starting point</a>
<ul>
<li class="chapter" data-level="1.1.1" data-path="Chapter1.html"><a href="Chapter1.html#fish-out-of-water"><i class="fa fa-check"></i><b>1.1.1</b> Fish out of water</a></li>
<li class="chapter" data-level="1.1.2" data-path="Chapter1.html"><a href="Chapter1.html#surrounded-by-technology"><i class="fa fa-check"></i><b>1.1.2</b> Surrounded by technology</a></li>
</ul></li>
<li class="chapter" data-level="1.2" data-path="Chapter1.html"><a href="Chapter1.html#of-pasts-and-presents"><i class="fa fa-check"></i><b>1.2</b> Of Pasts and Presents</a>
<ul>
<li class="chapter" data-level="1.2.1" data-path="Chapter1.html"><a href="Chapter1.html#growing-up-around-play"><i class="fa fa-check"></i><b>1.2.1</b> Growing up around play</a></li>
<li class="chapter" data-level="1.2.2" data-path="Chapter1.html"><a href="Chapter1.html#art-design-and-philosophy"><i class="fa fa-check"></i><b>1.2.2</b> Art, Design, and Philosophy</a></li>
</ul></li>
<li class="chapter" data-level="1.3" data-path="Chapter1.html"><a href="Chapter1.html#in-closing"><i class="fa fa-check"></i><b>1.3</b> In closing</a></li>
</ul></li>
<li class="part"><span><b>II Foundations</b></span></li>
<li class="chapter" data-level="2" data-path="Chapter2.html"><a href="Chapter2.html"><i class="fa fa-check"></i><b>2</b> Scaffolding</a>
<ul>
<li class="chapter" data-level="2.1" data-path="Chapter2.html"><a href="Chapter2.html#introduction"><i class="fa fa-check"></i><b>2.1</b> Introduction</a></li>
<li class="chapter" data-level="2.2" data-path="Chapter2.html"><a href="Chapter2.html#steppingstones-into-post-modern-humanities"><i class="fa fa-check"></i><b>2.2</b> Steppingstones into post-modern humanities</a>
<ul>
<li class="chapter" data-level="2.2.1" data-path="Chapter2.html"><a href="Chapter2.html#transdisciplinary-design-research"><i class="fa fa-check"></i><b>2.2.1</b> Transdisciplinary Design Research</a></li>
<li class="chapter" data-level="2.2.2" data-path="Chapter2.html"><a href="Chapter2.html#crafting-trandisciplinary-assemblages"><i class="fa fa-check"></i><b>2.2.2</b> Crafting Trandisciplinary Assemblages</a></li>
<li class="chapter" data-level="2.2.3" data-path="Chapter2.html"><a href="Chapter2.html#transcending-method-through-design"><i class="fa fa-check"></i><b>2.2.3</b> Transcending method through Design</a></li>
</ul></li>
<li class="chapter" data-level="2.3" data-path="Chapter2.html"><a href="Chapter2.html#how-to-use-this-thesis"><i class="fa fa-check"></i><b>2.3</b> How to use this Thesis</a></li>
</ul></li>
<li class="chapter" data-level="3" data-path="Chapter3.html"><a href="Chapter3.html"><i class="fa fa-check"></i><b>3</b> Seeing Things of the Internet</a>
<ul>
<li class="chapter" data-level="3.1" data-path="Chapter3.html"><a href="Chapter3.html#a-case-for-and-against-an-internet-of-things"><i class="fa fa-check"></i><b>3.1</b> A case for (and against) an Internet of Things</a>
<ul>
<li class="chapter" data-level="3.1.1" data-path="Chapter3.html"><a href="Chapter3.html#defining-iot"><i class="fa fa-check"></i><b>3.1.1</b> Defining IoT</a></li>
<li class="chapter" data-level="3.1.2" data-path="Chapter3.html"><a href="Chapter3.html#interacting-with-iot"><i class="fa fa-check"></i><b>3.1.2</b> Interacting with IoT</a></li>
<li class="chapter" data-level="3.1.3" data-path="Chapter3.html"><a href="Chapter3.html#the-disillusionment-of-living-in-iot"><i class="fa fa-check"></i><b>3.1.3</b> The disillusionment of living in IoT</a></li>
</ul></li>
<li class="chapter" data-level="3.2" data-path="Chapter3.html"><a href="Chapter3.html#approaching-an-alternative-perspective-for-design-in-iot"><i class="fa fa-check"></i><b>3.2</b> Approaching an alternative perspective for Design in IoT</a>
<ul>
<li class="chapter" data-level="3.2.1" data-path="Chapter3.html"><a href="Chapter3.html#changing-perspectives"><i class="fa fa-check"></i><b>3.2.1</b> Changing perspectives</a></li>
<li class="chapter" data-level="3.2.2" data-path="Chapter3.html"><a href="Chapter3.html#metaphorically-speaking"><i class="fa fa-check"></i><b>3.2.2</b> Metaphorically speaking</a></li>
</ul></li>
<li class="chapter" data-level="3.3" data-path="Chapter3.html"><a href="Chapter3.html#conclusion"><i class="fa fa-check"></i><b>3.3</b> Conclusion</a></li>
</ul></li>
<li class="chapter" data-level="4" data-path="Chapter4.html"><a href="Chapter4.html"><i class="fa fa-check"></i><b>4</b> Being Things of the Internet</a>
<ul>
<li class="chapter" data-level="4.1" data-path="Chapter4.html"><a href="Chapter4.html#introduction-1"><i class="fa fa-check"></i><b>4.1</b> Introduction</a>
<ul>
<li class="chapter" data-level="4.1.1" data-path="Chapter4.html"><a href="Chapter4.html#a-philosophical-interlude"><i class="fa fa-check"></i><b>4.1.1</b> A Philosophical Interlude</a></li>
</ul></li>
<li class="chapter" data-level="4.2" data-path="Chapter4.html"><a href="Chapter4.html#understanding-things-on-and-not-on-the-internet"><i class="fa fa-check"></i><b>4.2</b> Understanding <em>Things</em> on (and not on) the Internet</a>
<ul>
<li class="chapter" data-level="4.2.1" data-path="Chapter4.html"><a href="Chapter4.html#phenomenologically-speaking"><i class="fa fa-check"></i><b>4.2.1</b> Phenomenologically speaking</a></li>
<li class="chapter" data-level="4.2.2" data-path="Chapter4.html"><a href="Chapter4.html#towards-an-object-oriented-ontology"><i class="fa fa-check"></i><b>4.2.2</b> Towards an Object-Oriented Ontology</a></li>
</ul></li>
<li class="chapter" data-level="4.3" data-path="Chapter4.html"><a href="Chapter4.html#object-oriented-ontology"><i class="fa fa-check"></i><b>4.3</b> Object-Oriented Ontology</a></li>
<li class="chapter" data-level="4.4" data-path="Chapter4.html"><a href="Chapter4.html#concluding-on-a-post-anthropocentric-perspective-for-design"><i class="fa fa-check"></i><b>4.4</b> Concluding on a post-anthropocentric perspective for Design</a></li>
</ul></li>
<li class="part"><span><b>Methodologies</b></span></li>
<li class="chapter" data-level="5" data-path="Chapter5.html"><a href="Chapter5.html"><i class="fa fa-check"></i><b>5</b> Design Research</a>
<ul>
<li class="chapter" data-level="5.1" data-path="Chapter5.html"><a href="Chapter5.html#introduction-2"><i class="fa fa-check"></i><b>5.1</b> Introduction</a></li>
<li class="chapter" data-level="5.2" data-path="Chapter5.html"><a href="Chapter5.html#doing-design-research"><i class="fa fa-check"></i><b>5.2</b> Doing Design Research</a>
<ul>
<li class="chapter" data-level="5.2.1" data-path="Chapter5.html"><a href="Chapter5.html#defining-design"><i class="fa fa-check"></i><b>5.2.1</b> Defining Design</a></li>
<li class="chapter" data-level="5.2.2" data-path="Chapter5.html"><a href="Chapter5.html#defining-research"><i class="fa fa-check"></i><b>5.2.2</b> Defining Research</a></li>
<li class="chapter" data-level="5.2.3" data-path="Chapter5.html"><a href="Chapter5.html#the-object-of-design"><i class="fa fa-check"></i><b>5.2.3</b> The Object of Design</a></li>
</ul></li>
<li class="chapter" data-level="5.3" data-path="Chapter5.html"><a href="Chapter5.html#research-through-design"><i class="fa fa-check"></i><b>5.3</b> Research through Design</a>
<ul>
<li class="chapter" data-level="5.3.1" data-path="Chapter5.html"><a href="Chapter5.html#approaching-research-through-design"><i class="fa fa-check"></i><b>5.3.1</b> Approaching Research through Design</a></li>
<li class="chapter" data-level="5.3.2" data-path="Chapter5.html"><a href="Chapter5.html#practice-based-research"><i class="fa fa-check"></i><b>5.3.2</b> Practice-based Research</a></li>
<li class="chapter" data-level="5.3.3" data-path="Chapter5.html"><a href="Chapter5.html#ideology-or-methodology"><i class="fa fa-check"></i><b>5.3.3</b> Ideology or Methodology?</a></li>
</ul></li>
<li class="chapter" data-level="5.4" data-path="Chapter5.html"><a href="Chapter5.html#conclusions"><i class="fa fa-check"></i><b>5.4</b> Conclusions</a></li>
</ul></li>
<li class="chapter" data-level="6" data-path="Chapter6.html"><a href="Chapter6.html"><i class="fa fa-check"></i><b>6</b> Playfully Designing for Things</a>
<ul>
<li class="chapter" data-level="6.1" data-path="Chapter6.html"><a href="Chapter6.html#introduction-3"><i class="fa fa-check"></i><b>6.1</b> Introduction</a></li>
<li class="chapter" data-level="6.2" data-path="Chapter6.html"><a href="Chapter6.html#defining-play"><i class="fa fa-check"></i><b>6.2</b> Defining Play</a>
<ul>
<li class="chapter" data-level="6.2.1" data-path="Chapter6.html"><a href="Chapter6.html#what-is-play"><i class="fa fa-check"></i><b>6.2.1</b> What is Play?</a></li>
<li class="chapter" data-level="6.2.2" data-path="Chapter6.html"><a href="Chapter6.html#playgrounds-for-play"><i class="fa fa-check"></i><b>6.2.2</b> Playgrounds for Play</a></li>
</ul></li>
<li class="chapter" data-level="6.3" data-path="Chapter6.html"><a href="Chapter6.html#design-and-playfulness"><i class="fa fa-check"></i><b>6.3</b> Design and Playfulness</a>
<ul>
<li class="chapter" data-level="6.3.1" data-path="Chapter6.html"><a href="Chapter6.html#returning-to-playfulness"><i class="fa fa-check"></i><b>6.3.1</b> Returning to Playfulness</a></li>
<li class="chapter" data-level="6.3.2" data-path="Chapter6.html"><a href="Chapter6.html#ludic-design"><i class="fa fa-check"></i><b>6.3.2</b> Ludic Design</a></li>
</ul></li>
<li class="chapter" data-level="6.4" data-path="Chapter6.html"><a href="Chapter6.html#designing-curious-philosophical-artefacts"><i class="fa fa-check"></i><b>6.4</b> Designing Curious Philosophical Artefacts</a>
<ul>
<li class="chapter" data-level="6.4.1" data-path="Chapter6.html"><a href="Chapter6.html#speculating-over-definitions"><i class="fa fa-check"></i><b>6.4.1</b> Speculating over definitions</a></li>
</ul></li>
<li class="chapter" data-level="6.5" data-path="Chapter6.html"><a href="Chapter6.html#carpentry"><i class="fa fa-check"></i><b>6.5</b> Carpentry</a>
<ul>
<li class="chapter" data-level="6.5.1" data-path="Chapter6.html"><a href="Chapter6.html#getting-your-hands-dirty-with-philosophy"><i class="fa fa-check"></i><b>6.5.1</b> Getting your hands dirty with philosophy</a></li>
</ul></li>
<li class="chapter" data-level="6.6" data-path="Chapter6.html"><a href="Chapter6.html#a-combined-methodological-framework"><i class="fa fa-check"></i><b>6.6</b> A combined methodological framework</a></li>
<li class="chapter" data-level="6.7" data-path="Chapter6.html"><a href="Chapter6.html#conclusions-1"><i class="fa fa-check"></i><b>6.7</b> Conclusions</a></li>
</ul></li>
<li class="part"><span><b>III Doing Carpentry</b></span></li>
<li class="chapter" data-level="7" data-path="Chapter7.html"><a href="Chapter7.html"><i class="fa fa-check"></i><b>7</b> A Model for a Philosophical View of IoT</a>
<ul>
<li class="chapter" data-level="7.1" data-path="Chapter7.html"><a href="Chapter7.html#introduction-4"><i class="fa fa-check"></i><b>7.1</b> Introduction</a></li>
<li class="chapter" data-level="7.2" data-path="Chapter7.html"><a href="Chapter7.html#iot-as-a-spatial-phenomenon"><i class="fa fa-check"></i><b>7.2</b> IoT as a spatial phenomenon</a>
<ul>
<li class="chapter" data-level="7.2.1" data-path="Chapter7.html"><a href="Chapter7.html#the-division-of-space"><i class="fa fa-check"></i><b>7.2.1</b> The division of space</a></li>
<li class="chapter" data-level="7.2.2" data-path="Chapter7.html"><a href="Chapter7.html#reconfiguring-insides-and-outsides-as-heterotopia"><i class="fa fa-check"></i><b>7.2.2</b> Reconfiguring Insides and Outsides as Heterotopia</a></li>
</ul></li>
<li class="chapter" data-level="7.3" data-path="Chapter7.html"><a href="Chapter7.html#crafting-a-model-for-a-philosophical-view-of-iot"><i class="fa fa-check"></i><b>7.3</b> Crafting a Model for a Philosophical View of IoT</a></li>
<li class="chapter" data-level="7.4" data-path="Chapter7.html"><a href="Chapter7.html#discussion-and-conclusion"><i class="fa fa-check"></i><b>7.4</b> Discussion and Conclusion</a></li>
</ul></li>
<li class="chapter" data-level="8" data-path="Chapter8.html"><a href="Chapter8.html"><i class="fa fa-check"></i><b>8</b> Playing with the IoT</a>
<ul>
<li class="chapter" data-level="8.1" data-path="Chapter8.html"><a href="Chapter8.html#introduction-5"><i class="fa fa-check"></i><b>8.1</b> Introduction</a></li>
<li class="chapter" data-level="8.2" data-path="Chapter8.html"><a href="Chapter8.html#creating-a-foundation-for-approaching-game-design"><i class="fa fa-check"></i><b>8.2</b> Creating a foundation for approaching Game Design</a>
<ul>
<li class="chapter" data-level="8.2.1" data-path="Chapter8.html"><a href="Chapter8.html#play-and-rhetoric"><i class="fa fa-check"></i><b>8.2.1</b> Play and Rhetoric</a></li>
</ul></li>
<li class="chapter" data-level="8.3" data-path="Chapter8.html"><a href="Chapter8.html#carpentering-the-internet-of-things-board-game"><i class="fa fa-check"></i><b>8.3</b> Carpentering the Internet of Things Board Game</a>
<ul>
<li class="chapter" data-level="8.3.1" data-path="Chapter8.html"><a href="Chapter8.html#exploration-phase"><i class="fa fa-check"></i><b>8.3.1</b> Exploration Phase</a></li>
<li class="chapter" data-level="8.3.2" data-path="Chapter8.html"><a href="Chapter8.html#reflection-phase"><i class="fa fa-check"></i><b>8.3.2</b> Reflection Phase</a></li>
<li class="chapter" data-level="8.3.3" data-path="Chapter8.html"><a href="Chapter8.html#redux"><i class="fa fa-check"></i><b>8.3.3</b> Redux</a></li>
</ul></li>
<li class="chapter" data-level="8.4" data-path="Chapter8.html"><a href="Chapter8.html#discussion-1"><i class="fa fa-check"></i><b>8.4</b> Discussion</a></li>
<li class="chapter" data-level="8.5" data-path="Chapter8.html"><a href="Chapter8.html#wrapping-up"><i class="fa fa-check"></i><b>8.5</b> Wrapping Up</a></li>
</ul></li>
<li class="chapter" data-level="9" data-path="Chapter9.html"><a href="Chapter9.html"><i class="fa fa-check"></i><b>9</b> Predicting futures in the IoT</a>
<ul>
<li class="chapter" data-level="9.1" data-path="Chapter9.html"><a href="Chapter9.html#introduction-6"><i class="fa fa-check"></i><b>9.1</b> Introduction</a></li>
<li class="chapter" data-level="9.2" data-path="Chapter9.html"><a href="Chapter9.html#philosophical-foundations"><i class="fa fa-check"></i><b>9.2</b> Philosophical Foundations</a>
<ul>
<li class="chapter" data-level="9.2.1" data-path="Chapter9.html"><a href="Chapter9.html#the-perception-of-technology-and-post-phenomenology"><i class="fa fa-check"></i><b>9.2.1</b> The Perception of Technology and Post-Phenomenology</a></li>
<li class="chapter" data-level="9.2.2" data-path="Chapter9.html"><a href="Chapter9.html#human-technology-relations-as-perceptual-illusions"><i class="fa fa-check"></i><b>9.2.2</b> Human-Technology Relations as Perceptual Illusions</a></li>
<li class="chapter" data-level="9.2.3" data-path="Chapter9.html"><a href="Chapter9.html#quantum-causation-for-iot"><i class="fa fa-check"></i><b>9.2.3</b> Quantum Causation for IoT</a></li>
</ul></li>
<li class="chapter" data-level="9.3" data-path="Chapter9.html"><a href="Chapter9.html#carpentering-the-supernatural-iot"><i class="fa fa-check"></i><b>9.3</b> Carpentering the Supernatural IoT</a>
<ul>
<li class="chapter" data-level="9.3.1" data-path="Chapter9.html"><a href="Chapter9.html#designing-the-deck"><i class="fa fa-check"></i><b>9.3.1</b> Designing the Deck</a></li>
<li class="chapter" data-level="9.3.2" data-path="Chapter9.html"><a href="Chapter9.html#scanning-the-stars-with-software"><i class="fa fa-check"></i><b>9.3.2</b> Scanning the Stars with Software</a></li>
<li class="chapter" data-level="9.3.3" data-path="Chapter9.html"><a href="Chapter9.html#a-tarot-of-things"><i class="fa fa-check"></i><b>9.3.3</b> A Tarot of Things</a></li>
<li class="chapter" data-level="9.3.4" data-path="Chapter9.html"><a href="Chapter9.html#madame-bitsys-emporium"><i class="fa fa-check"></i><b>9.3.4</b> Madame Bitsy’s Emporium</a></li>
</ul></li>
<li class="chapter" data-level="9.4" data-path="Chapter9.html"><a href="Chapter9.html#feedback"><i class="fa fa-check"></i><b>9.4</b> Feedback</a></li>
<li class="chapter" data-level="9.5" data-path="Chapter9.html"><a href="Chapter9.html#discussion-and-conclusion-1"><i class="fa fa-check"></i><b>9.5</b> Discussion and Conclusion</a></li>
</ul></li>
<li class="part"><span><b>IV Moving Forwards</b></span></li>
<li class="chapter" data-level="10" data-path="Chapter10.html"><a href="Chapter10.html"><i class="fa fa-check"></i><b>10</b> Discussions and Conclusions</a>
<ul>
<li class="chapter" data-level="10.1" data-path="Chapter10.html"><a href="Chapter10.html#the-living-internet-of-things"><i class="fa fa-check"></i><b>10.1</b> The Living Internet of Things</a>
<ul>
<li class="chapter" data-level="10.1.1" data-path="Chapter10.html"><a href="Chapter10.html#is-this-discussion-about-privacy-and-security-in-iot"><i class="fa fa-check"></i><b>10.1.1</b> Is this discussion about privacy and security in IoT?</a></li>
<li class="chapter" data-level="10.1.2" data-path="Chapter10.html"><a href="Chapter10.html#going-beyond-human-centred-design"><i class="fa fa-check"></i><b>10.1.2</b> Going beyond Human-Centred Design</a></li>
<li class="chapter" data-level="10.1.3" data-path="Chapter10.html"><a href="Chapter10.html#is-this-a-transhumanist-argument"><i class="fa fa-check"></i><b>10.1.3</b> Is this a transhumanist argument?</a></li>
</ul></li>
<li class="chapter" data-level="10.2" data-path="Chapter10.html"><a href="Chapter10.html#the-mantra-of-playfulness"><i class="fa fa-check"></i><b>10.2</b> The Mantra of Playfulness</a>
<ul>
<li class="chapter" data-level="10.2.1" data-path="Chapter10.html"><a href="Chapter10.html#being-a-playful-philosopher-designer"><i class="fa fa-check"></i><b>10.2.1</b> Being a playful philosopher-designer</a></li>
</ul></li>
<li class="chapter" data-level="10.3" data-path="Chapter10.html"><a href="Chapter10.html#in-closing-1"><i class="fa fa-check"></i><b>10.3</b> In closing</a></li>
</ul></li>
<li class="appendix"><span><b>Appendix</b></span></li>
<li class="chapter" data-level="A" data-path="AppendixA.html"><a href="AppendixA.html"><i class="fa fa-check"></i><b>A</b> Appendix</a>
<ul>
<li class="chapter" data-level="A.1" data-path="AppendixA.html"><a href="AppendixA.html#game-design-definitions-and-terminologies"><i class="fa fa-check"></i><b>A.1</b> Game Design Definitions and Terminologies</a></li>
</ul></li>
<li class="chapter" data-level="B" data-path="AppendixB.html"><a href="AppendixB.html"><i class="fa fa-check"></i><b>B</b> Appendix</a>
<ul>
<li class="chapter" data-level="B.1" data-path="AppendixB.html"><a href="AppendixB.html#the-internet-of-things-board-game-explored"><i class="fa fa-check"></i><b>B.1</b> The Internet of Things Board Game Explored</a></li>
<li class="chapter" data-level="B.2" data-path="AppendixB.html"><a href="AppendixB.html#backstory91"><i class="fa fa-check"></i><b>B.2</b> Backstory</a></li>
<li class="chapter" data-level="B.3" data-path="AppendixB.html"><a href="AppendixB.html#game-objective"><i class="fa fa-check"></i><b>B.3</b> Game Objective</a></li>
<li class="chapter" data-level="B.4" data-path="AppendixB.html"><a href="AppendixB.html#setup"><i class="fa fa-check"></i><b>B.4</b> Play Setup</a></li>
<li class="chapter" data-level="B.5" data-path="AppendixB.html"><a href="AppendixB.html#phases-of-play94"><i class="fa fa-check"></i><b>B.5</b> Phases of Play</a></li>
<li class="chapter" data-level="B.6" data-path="AppendixB.html"><a href="AppendixB.html#tiles"><i class="fa fa-check"></i><b>B.6</b> Understanding the Tiles</a></li>
<li class="chapter" data-level="B.7" data-path="AppendixB.html"><a href="AppendixB.html#avatars"><i class="fa fa-check"></i><b>B.7</b> Avatars</a></li>
<li class="chapter" data-level="B.8" data-path="AppendixB.html"><a href="AppendixB.html#rolls"><i class="fa fa-check"></i><b>B.8</b> Rolling Dice</a>
<ul>
<li class="chapter" data-level="B.8.1" data-path="AppendixB.html"><a href="AppendixB.html#attack"><i class="fa fa-check"></i><b>B.8.1</b> Doing an Attack Roll</a></li>
<li class="chapter" data-level="B.8.2" data-path="AppendixB.html"><a href="AppendixB.html#random"><i class="fa fa-check"></i><b>B.8.2</b> Randomisation</a></li>
</ul></li>
<li class="chapter" data-level="B.9" data-path="AppendixB.html"><a href="AppendixB.html#decks"><i class="fa fa-check"></i><b>B.9</b> Understanding and Reading Cards</a>
<ul>
<li class="chapter" data-level="B.9.1" data-path="AppendixB.html"><a href="AppendixB.html#items"><i class="fa fa-check"></i><b>B.9.1</b> Items Deck</a></li>
<li class="chapter" data-level="B.9.2" data-path="AppendixB.html"><a href="AppendixB.html#risks"><i class="fa fa-check"></i><b>B.9.2</b> Risks Deck</a></li>
<li class="chapter" data-level="B.9.3" data-path="AppendixB.html"><a href="AppendixB.html#privacy"><i class="fa fa-check"></i><b>B.9.3</b> Privacy Deck</a></li>
<li class="chapter" data-level="B.9.4" data-path="AppendixB.html"><a href="AppendixB.html#daemons"><i class="fa fa-check"></i><b>B.9.4</b> Daemons Deck</a></li>
</ul></li>
<li class="chapter" data-level="B.10" data-path="AppendixB.html"><a href="AppendixB.html#connections"><i class="fa fa-check"></i><b>B.10</b> Making Connections</a></li>
<li class="chapter" data-level="B.11" data-path="AppendixB.html"><a href="AppendixB.html#risk-check"><i class="fa fa-check"></i><b>B.11</b> Conducting Risk Checks</a></li>
<li class="chapter" data-level="B.12" data-path="AppendixB.html"><a href="AppendixB.html#tokens"><i class="fa fa-check"></i><b>B.12</b> Tokens</a></li>
<li class="chapter" data-level="B.13" data-path="AppendixB.html"><a href="AppendixB.html#resolve"><i class="fa fa-check"></i><b>B.13</b> Resolves and Other Actions</a></li>
<li class="chapter" data-level="B.14" data-path="AppendixB.html"><a href="AppendixB.html#delayed"><i class="fa fa-check"></i><b>B.14</b> Being Delayed</a></li>
<li class="chapter" data-level="B.15" data-path="AppendixB.html"><a href="AppendixB.html#rest"><i class="fa fa-check"></i><b>B.15</b> Resting</a></li>
<li class="chapter" data-level="B.16" data-path="AppendixB.html"><a href="AppendixB.html#databox"><i class="fa fa-check"></i><b>B.16</b> Databoxes</a></li>
<li class="chapter" data-level="B.17" data-path="AppendixB.html"><a href="AppendixB.html#threat-tracker"><i class="fa fa-check"></i><b>B.17</b> Threat Tracker</a></li>
<li class="chapter" data-level="B.18" data-path="AppendixB.html"><a href="AppendixB.html#end"><i class="fa fa-check"></i><b>B.18</b> End of the Game</a></li>
</ul></li>
<li class="chapter" data-level="C" data-path="AppendixC.html"><a href="AppendixC.html"><i class="fa fa-check"></i><b>C</b> Appendix C</a>
<ul>
<li class="chapter" data-level="C.1" data-path="AppendixC.html"><a href="AppendixC.html#the-tarot-of-things-deck"><i class="fa fa-check"></i><b>C.1</b> The Tarot of Things Deck</a></li>
</ul></li>
<li class="chapter" data-level="" data-path="bibliography.html"><a href="bibliography.html"><i class="fa fa-check"></i>Bibliography</a></li>
<li class="divider"></li>
<li><a href="https://github.com/rstudio/bookdown" target="blank">Published with bookdown</a></li>

</ul>

      </nav>
    </div>

    <div class="book-body">
      <div class="body-inner">
        <div class="book-header" role="navigation">
          <h1>
            <i class="fa fa-circle-o-notch fa-spin"></i><a href="./">Design by Play</a>
          </h1>
        </div>

        <div class="page-wrapper" tabindex="-1" role="main">
          <div class="page-inner">

            <section class="normal" id="section-">
<div id="AppendixB" class="section level1 hasAnchor" number="12">
<h1><span class="header-section-number">B</span> Appendix<a href="AppendixB.html#AppendixB" class="anchor-section" aria-label="Anchor link to header"></a></h1>
<div id="the-internet-of-things-board-game-explored" class="section level2 hasAnchor" number="12.1">
<h2><span class="header-section-number">B.1</span> The Internet of Things Board Game Explored<a href="AppendixB.html#the-internet-of-things-board-game-explored" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<p>The Internet of Things Board Game was a lengthy endeavour into understanding the creation of unique procedural rhetoric in play around philosophy, design, and IoT. All aspects of the game would be too difficult to communicate as it went through 14 iterations with some being entire overhauls in design and rhetoric. So as to not derail the focus of this thesis, this information is kept as supplementary content as the true rhetoric of the game can only be understood by play. This special section is therefore devoted to illuminating as much of the game as possible in its latest iteration (14 at the time of writing).</p>
<p>For ease, this section is presented as a game manual with additional footnotes explaining the reasoning behind certain decisions. The detailed background process of reaching this iteration is explored in the journey of <a href="Chapter8.html#Chapter8">Chapter 8</a>.</p>
<p>In addition to the game manual presented here, the game may also be experienced online as a video playthrough. As of writing this manuscript the playthrough is intended to give a brief idea of how the game operates. This online content may be updated in the future with further information regarding the operations of the game. The playthrough may be experienced here:</p>
<ul>
<li><a href="https://youtu.be/V-u2XsMj5mI" class="uri">https://youtu.be/V-u2XsMj5mI</a>.</li>
<li><a href="https://haiderali.co/Internet-of-Things-Board-Game" class="uri">https://haiderali.co/Internet-of-Things-Board-Game</a>.</li>
</ul>
</div>
<div id="backstory91" class="section level2 hasAnchor" number="12.2">
<h2><span class="header-section-number">B.2</span> Backstory<a href="#fn91" class="footnote-ref" id="fnref91"><sup>91</sup></a><a href="AppendixB.html#backstory91" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<p>Imagine a world in a parallel realm not very different to your own, in a time not too far into the future with people not unlike you. Imagine a place shining with technological brilliance driving a society offering peace, tranquillity, efficiency, and ultimately futures full of happiness and hope: Welcome to <em>Sol</em> on the distant world of <em>Atlas Prime</em>. A place where technology and human are two sides of the same coin, where the physical meets the digital and paves the roads you walk on.</p>
<p>Just around the turn of the century, the forerunners of <em>The Algorithm</em> praised it as a way to move forward. One system to control all and ensure daily safety bringing about a <em>technirvana</em>. Soon heard of in magazines, e-zines, and newspapers everyone spoke of it and expected others to join. However, what was meant to be a means of watching over and securing loved ones evolved into an obsession of control as <em>The Council</em> was born!</p>
<p>Initially proposed as a way to streamline matters of government, <em>The Council</em> proposed using <em>The Algorithm</em> to gain access to all affairs of life. From family trees to bank details, to how many bags of tea were left in people’s pantries. Suddenly data was the new currency, and one digital signature was all it took to fetch, analyse, and upload information to a hive-mind network.</p>
<p>Now, people are born into a world where they are digital cookie distribution machines dropping bits and bytes of information about everything they do. The once free cities of <em>Atlas Prime</em> have all been following the image of <em>Sol</em>. Over time <em>The Algorithm</em> evolved to include other versions, secret incremental updates that gradually tightened its grip on everyone and everything. The past, a distant blur of memory that <em>The Council’s</em> data-hungry algorithms have almost entirely wiped out exists in the form of rogue code woven into the digital fabric of the free cities inhabitants. Lost advertisements, Memes, Gifs and messages commented into program code have been circulating in the shadows of <em>Tor</em> networks; those that still are out of reach of <em>The Council’s</em> deep search engines. They whisper a prophecy of the counter system called, the <em>DataBox</em>.</p>
<p>The <em>DataBox</em> is said to give people back power, essentially blocking out <em>Council</em> attempts at foraging data. By giving people control over what data can and cannot be in the reach of others, <em>DataBox</em> is the nemesis <em>The Council</em> have been fearing. As such, they’ve created their countermeasures. Although a series of algorithms meant to hunt out rogue code, its ferocity of action with a seek and devour reputation towards data cookies has given it infamy as the <em>Cookie Monster</em>!</p>
<p>Now with the enemy having unleashed its hounds upon whosoever attempts to stand against them, a ragtag group of vigilantes have taken up the mantle to fight back. <strong><em>Welcome to the Resistance!</em></strong> The last bastion against an invisible enemy! You and your party members will traverse between the tangible and the intangible Internet to take back what is yours. But be warned, <em>The Council</em> is ever watching. Botnet’s and Spyware are but the tip of the iceberg as they intend to stop you, or worse, have you assimilate!</p>
<p>Afraid of potentially losing all their influence and control, <em>The Council</em> have begun work on another upgrade to their <em>Cookie Monster</em> algorithms. An update proposed to eliminate all links to code related to <em>DataBox</em> on any connected network. Deceptively named <em>The Crumble</em> this increment should successfully end any chance for resisting the reach of the <em>Cookie Monster</em>. As part of the <em>Resistance,</em> you can’t allow that and must fend off any daemons thrown at you establishing a secure encrypted network.</p>
<p>Tread lightly, there are Privacy bombs and traps everywhere! Be prepared lest you get spotted in virtual floodlights. The digital landscape is no longer a peaceful one so keep an eye on that <em>Threat Tracker</em>. Will you build your secure networks in time for <em>The Crumble</em>?</p>
</div>
<div id="game-objective" class="section level2 hasAnchor" number="12.3">
<h2><span class="header-section-number">B.3</span> Game Objective<a href="AppendixB.html#game-objective" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<p>The Internet of Things Board Game is a 2–4 player cooperative<a href="#fn92" class="footnote-ref" id="fnref92"><sup>92</sup></a> board game where players work together against amassing digital threats to build a secure network amongst themselves. Create digital links as you traverse physical spaces on the board and secure them by deploying <em>Databoxes</em> equal to <strong>twice</strong> the number of players. Build all the <em>Databoxes</em> and win the game!</p>
</div>
<div id="setup" class="section level2 hasAnchor" number="12.4">
<h2><span class="header-section-number">B.4</span> Play Setup<a href="AppendixB.html#setup" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<p>The board is prepared according to the number of players<a href="#fn93" class="footnote-ref" id="fnref93"><sup>93</sup></a>. First, place the <em>Server</em> tile in the middle. Next, separate <em>Insecure Tiles</em> (see <a href="AppendixB.html#tiles">B.6</a>) and <em>Regular Tiles</em> into separate piles upside down and according to the number of players from Table. <a href="AppendixB.html#tab:tab-formation">B.1</a>, take the top tiles from each pile to make a tile deck. Return the remaining tiles to the box, and shuffle the tile deck placing them in a pile upside down. Now pick tiles from the top of the deck and place them following the numbers in Fig. <a href="AppendixB.html#fig:formation">B.1</a>. Each tile of the board is now a different <strong><em>space</em></strong> that players can navigate. <strong>Once placed tiles cannot be moved</strong>.</p>
<table>
<caption><span id="tab:tab-formation">Table B.1: </span>Number of players and tile formations.</caption>
<thead>
<tr class="header">
<th align="right">Players</th>
<th align="left">Regular Tiles + Insecure Tiles</th>
<th align="left">Infected Tiles (Tokens)</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="right">2</td>
<td align="left">9 + 3, or, 8 + 4</td>
<td align="left">2 (2), 2 (1)</td>
</tr>
<tr class="even">
<td align="right">3</td>
<td align="left">7 + 5, or, 6 + 6</td>
<td align="left">2 (2), 4 (1)</td>
</tr>
<tr class="odd">
<td align="right">4</td>
<td align="left">19 + 7</td>
<td align="left">4 (2), 4 (1)</td>
</tr>
</tbody>
</table>

<div class="figure"><span style="display:block;" id="fig:formation"></span>
<img src="figures/appB-formation.png" alt="Board formation for play, darker shaded formation suggested for 2 player game. Follow numbers to place tiles."  />
<p class="caption">
Figure B.1: Board formation for play, darker shaded formation suggested for 2 player game. Follow numbers to place tiles.
</p>
</div>
<p>Next, ignoring the <em>Server</em> randomly pick tiles (see <a href="AppendixB.html#random">B.8.2</a>) and follow Table <a href="AppendixB.html#tab:tab-formation">B.1</a> to add <em>Vulnerability</em> tokens (see <a href="AppendixB.html#tokens">B.12</a>) to them infecting those spaces. Add double tokens from the table first, then single. Players now select an <em>Avatar</em> (see <a href="AppendixB.html#avatars">B.7</a>) to play with, taking that avatars board and placing the corresponding standee on the <em>Server</em> tile. Any items associated with selected avatars are collected by players, as well as one <em>Primary</em> item each (see <a href="AppendixB.html#primary">B.9.1.1</a>). Players set their avatar to their starting settings and finally, place the <em>Threat Tracker</em> (see <a href="AppendixB.html#threat-tracker">B.17</a>) to the side of the play area agreeing upon a difficulty level for play. Starting with whoever last used an Antivirus on their devices, play may now proceed clockwise.</p>
</div>
<div id="phases-of-play94" class="section level2 hasAnchor" number="12.5">
<h2><span class="header-section-number">B.5</span> Phases of Play<a href="#fn94" class="footnote-ref" id="fnref94"><sup>94</sup></a><a href="AppendixB.html#phases-of-play94" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<p>Each player’s turn comprises of two phases, an <em>Actions Phase</em>, and <em>Risk Phase</em> <a href="#fn95" class="footnote-ref" id="fnref95"><sup>95</sup></a>. During the <strong>Actions Phase</strong> a player gets to do up to 2 actions per turn (unless they are <em>Delayed</em>, see <a href="AppendixB.html#avatars">B.7</a>) allowed out of the following actions:</p>
<ul>
<li><strong>Move:</strong> Players can move in any direction up to their <em>Speed</em> level (see <a href="AppendixB.html#avatars">B.7</a>).</li>
<li><strong>Find:</strong> Roll for <em>Observation</em> (see <a href="AppendixB.html#rolls">B.8</a>) over spaces with an <strong>EYE</strong> icon to draw one item from the <em>Items Deck</em> (see <a href="AppendixB.html#decks">B.9</a>).</li>
<li><strong>Trade:</strong> If sharing a space with a player trade any number of items with them.</li>
<li><strong>Rest:</strong> Recover 1 <em>Sanity</em> <strong>OR</strong> attempt to resolve any <em>Daemon</em> cards in hand (see <a href="AppendixB.html#rest">B.15</a>).</li>
<li><strong>Connect:</strong> Return items in hand or use items in spaces to make a <em>Connection</em> (see <a href="AppendixB.html#connections">B.10</a>).</li>
<li><strong>Discard:</strong> Remove 1 item in hand from play.</li>
<li><strong>Ability:</strong> Use player or card <em>Abilities</em> (see <a href="AppendixB.html#avatars">B.7</a>).</li>
<li><strong>Resolve:</strong> Attempt to clear a space of <em>Issues</em> (see <a href="AppendixB.html#resolve">B.13</a>).</li>
<li><strong>Deploy:</strong> Spend 2 actions to attempt a <em>Privacy</em> card (see <a href="AppendixB.html#privacy">B.9.3</a>), if succeeded deploy a <em>Databox</em> (see <a href="AppendixB.html#databox">B.16</a>).</li>
<li><strong>Skip:</strong> Skip an action.</li>
</ul>
<p>After spending actions the player must enter the <strong>Risk Phase</strong> by rolling for <em>Security</em> (see <a href="AppendixB.html#rolls">B.8</a>). In the game, this is often called <em>Rolling for Risk</em> or conducting a <em>Risk Check</em>. If they succeed play continues to the next player. If they fail the following is done in order:</p>
<ul>
<li>Place a <em>Vulnerability</em> token (see <a href="AppendixB.html#tokens">B.12</a>) in the space occupied and any further connected spaces.</li>
<li>Draw a card from the <em>Risk Deck</em> and follow the card in order top to bottom (see <a href="AppendixB.html#decks">B.9</a>)</li>
<li>Do risk checks on all items in hand using the new dice-count from the drawn card (see <a href="AppendixB.html#decks">B.9</a>).</li>
<li>If the drawn card requires other players to act as well, do so accordingly</li>
<li>The player ends their turn, next player begins with their <em>Action Phase</em>.</li>
</ul>
</div>
<div id="tiles" class="section level2 hasAnchor" number="12.6">
<h2><span class="header-section-number">B.6</span> Understanding the Tiles<a href="AppendixB.html#tiles" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<p>There are 2 kinds of tiles in the game, <em>Regular Tiles</em> and <em>Insecure Tiles</em> (Fig. <a href="AppendixB.html#fig:tiles">B.2</a>). They both function similarly, except for one thing: <em>Insecure Tiles</em> force players to <em>Roll for Security</em> twice during the <em>Risk Phase</em>, meaning they could cause it twice. This only occurs if a player decides to stop their <em>Move</em> action on an <em>Insecure Tile</em>. <em>Insecure Tiles</em> are recognised with their darker borders. Tiles are all named after physical locations such as a living room, kitchen, etc. and act as physical spaces. Spaces also signify connectivity using the notches in the corners (see <a href="AppendixB.html#connections">B.10</a>). See Fig. <a href="AppendixB.html#fig:tiles">B.2</a> to understand the different parts of each tile. Each space, subsequently, has a connection requirement which needs to be fulfilled before it can be secured by turning into a <em>Databox</em>.</p>
<div class="figure"><span style="display:block;" id="fig:tiles"></span>
<img src="figures/appB-tiles.png" alt="*Regular* and *Insecure Tiles* are similar except the latter forces players to do extra actions."  />
<p class="caption">
Figure B.2: <em>Regular</em> and <em>Insecure Tiles</em> are similar except the latter forces players to do extra actions.
</p>
</div>
<p>Some tiles have items players can connect to within them (see <a href="AppendixB.html#connections">B.10</a>). Generally, when a player connects a space they place a <em>Connection Token</em> in the open space next to the present item. <strong>Be careful when making these connections!</strong> If you end up connecting with an <em>Insecure Tile</em> you have to <em>Roll for Risk</em>.</p>
<p>Tiles also show as dots how many connected spaces are needed before deploying a <em>Databox</em> (see <a href="AppendixB.html#databox">B.16</a>). Players may use their <em>Find</em> action to draw cards from the <em>Items Deck</em> (see <a href="AppendixB.html#items">B.9.1</a>) on tiles that have an <strong>EYE</strong> icon (some tiles allow for more than 1 item to be drawn indicated by a number next to the icon).</p>
</div>
<div id="avatars" class="section level2 hasAnchor" number="12.7">
<h2><span class="header-section-number">B.7</span> Avatars<a href="#fn96" class="footnote-ref" id="fnref96"><sup>96</sup></a><a href="AppendixB.html#avatars" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<p>Players may play as different characters or avatars in the game. Each avatar comes with their own standee and board for keeping track of skills. Avatars each have unique abilities which players can use during play as actions. Certain avatars have <em>Passive</em> abilities which are always active, for instance, <em>Spook</em> can always clear all <em>Vulnerability</em> tokens in a space in one action.</p>
<div class="figure"><span style="display:block;" id="fig:avatars"></span>
<img src="figures/appB-avatars.png" alt="Players may choose between 6 in-game *Avatars* each with their own variable skills and abilities tracked using blue and black tokens."  />
<p class="caption">
Figure B.3: Players may choose between 6 in-game <em>Avatars</em> each with their own variable skills and abilities tracked using blue and black tokens.
</p>
</div>
<p>Avatars have skill levels defined by their <em>Speed</em>, <em>Sanity</em>, <em>Security</em>, <em>Observation</em>, and <em>Coding</em> skills on their boards, with their starting skill levels highlighted (Fig. <a href="AppendixB.html#fig:avatars">B.3</a>). <em>Speed</em> is denoted in the top right corner of the avatar board and refers to how many spaces a player may navigate up to in their turn. As the game progresses these skills rise and fall, and players may keep track using provided blue and black tokens. To keep track of reduced speed, add black tokens next to the <em>Speed</em> skill. For all other skills (except <em>Sanity</em>) when a player must permanently reduce their skills such as after the <em>Effect</em> of a <em>Risk</em> card (see <a href="AppendixB.html#risks">B.9.2</a>), black tokens can be placed as reminders. Each number on the tracks (except for <em>Sanity</em> and <em>Speed</em>) represent the number of dice a player can roll for that skill. For instance, in Fig. <a href="AppendixB.html#fig:avatars">B.3</a> <em>Spook</em> has a <em>Coding</em> skill of 4 meaning the player controlling <em>Spook</em> can roll 4 dice when asked to roll for <em>Coding</em>. However, as <em>Spook</em> also has 2 black tokens on his <em>Coding</em> track the player only gets 2 dice to roll.</p>
</div>
<div id="rolls" class="section level2 hasAnchor" number="12.8">
<h2><span class="header-section-number">B.8</span> Rolling Dice<a href="AppendixB.html#rolls" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<p>There is a lot of dice rolling in this game! <a href="#fn97" class="footnote-ref" id="fnref97"><sup>97</sup></a> The general rule while doing most dice rolls is:</p>
<p><span class="math display">\[
d6\left( \text{SkillLevel} \right) \pm Modifiers
\]</span></p>
<p>Modifiers are any cards or events that alter the number of allowed dice during play (see <a href="AppendixB.html#decks">B.9</a>). Skill level is the level of the skill asked to roll for. For instance, <em>Spook</em> has a <em>Coding</em> skill of 3, when asked to roll for <em>Coding</em> the player controlling <em>Spook</em> gets 3 <strong>d6</strong> to roll with, however, if they also have a <em>Health Monitor</em> item they get an additional <strong>d6</strong> (see <a href="AppendixB.html#secondary">B.9.1.2</a>).</p>
<p>Having multiple dice in a roll is important as it increases your chances of <em>passing</em>. A pass is if the player gets a <strong>5</strong> or <strong>6</strong> during the roll on <strong>any 1 die</strong>. Alternatively, players may lower the difficulty of play by including <strong>4</strong> as a pass. Anything besides will be considered a fail and depending on the situation (which often will involve a card or token) the corresponding <em>Effect</em> will come into play (see <a href="AppendixB.html#decks">B.9</a>).</p>
<div id="attack" class="section level3 hasAnchor" number="12.8.1">
<h3><span class="header-section-number">B.8.1</span> Doing an Attack Roll<a href="AppendixB.html#attack" class="anchor-section" aria-label="Anchor link to header"></a></h3>
<p>Sometimes players will have to get aggressive and attack the board. When doing an <em>Attack Roll</em>, players roll for <em>Coding</em> against a <strong>d20</strong> going to the opponent (sometimes cards make players attack each other). Dice are rolled together subtracting the total value of player dice from the opponent. The opponent always wins a draw. To win players must get a value higher than the opponents unless the following rolls occur:</p>
<ul>
<li>A <strong>1</strong> on the <strong>d20</strong>; this is an <em>instant kill</em>; the player wins immediately irrespective of what they rolled.</li>
<li>A <strong>19</strong> or <strong>20</strong>; this is an <em>instant hit</em> from the opponent making the player face consequences if present. If no consequences (such as an <em>Effect</em>, see <a href="AppendixB.html#decks">B.9</a>), the player must back away 1 space losing either 1 <em>Sanity</em> or lowering a skill by 1. This rule is irrespective of getting a higher value from the dice, but if the roll was higher the player may roll again after taking damage.</li>
</ul>
</div>
<div id="random" class="section level3 hasAnchor" number="12.8.2">
<h3><span class="header-section-number">B.8.2</span> Randomisation<a href="AppendixB.html#random" class="anchor-section" aria-label="Anchor link to header"></a></h3>
<p>During play, players will often be asked to randomise an action. This is done by rolling a <strong>d20</strong> and referencing the tile with the corresponding number. Each <em>Regular Tile</em> has a number printed from 1–20. Random actions may never reference an <em>Insecure Tile</em>.</p>
</div>
</div>
<div id="decks" class="section level2 hasAnchor" number="12.9">
<h2><span class="header-section-number">B.9</span> Understanding and Reading Cards<a href="AppendixB.html#decks" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<p>There are 4 decks of cards in the game: <em>Items</em>, <em>Risks</em>, <em>Privacy</em>, and <em>Daemons</em>. Cards in the deck usually have a <em>Function</em> and an <em>Effect</em>, with the latter represented in a darker shade. Each card is read top to bottom and often have numbers or icons in the corners which trigger other <em>Effects</em>.</p>
<div id="items" class="section level3 hasAnchor" number="12.9.1">
<h3><span class="header-section-number">B.9.1</span> Items Deck<a href="AppendixB.html#items" class="anchor-section" aria-label="Anchor link to header"></a></h3>
<p>This deck is comprised of three kinds of items <em>Primary</em>, <em>Secondary</em>, and <em>Tertiary</em> each with their functionality (Fig. <a href="AppendixB.html#fig:item-types">B.4</a>). Players may carry cards in hand up to a hand-limit of <strong>5 cards</strong>. Certain events and cards may change this number during play.</p>
<div id="primary" class="section level4 hasAnchor" number="12.9.1.1">
<h4><span class="header-section-number">B.9.1.1</span> Primary Items<a href="AppendixB.html#primary" class="anchor-section" aria-label="Anchor link to header"></a></h4>
<p>These are smart phones and tablets, and their <em>Function</em> is to make connections in the game. They each have a connect limit (see <a href="AppendixB.html#connections">B.10</a>), and upon completion players get a bonus action for every completed <em>Primary</em> item in hand. For instance, if there are 5 blue <em>Connection</em> tokens on a players smart phone item, for all future turns including the current one they get 3 actions instead of 2. Although, if at any point they lose that <em>Primary Card</em> or have to reduce tokens on it, the bonus is lost.</p>
<p>As an <em>Effect</em> activated upon failing the <em>Risk Phase</em>, players must do a <em>Risk Check</em> on all tokens present on the card. For each failed roll, players move that token to the <em>Effect</em> portion of the card. When no more spaces are left there the card is discarded and the <em>Threat Tracker</em> (see <a href="AppendixB.html#threat-tracker">B.17</a>) advanced by 1.</p>
<div class="figure"><span style="display:block;" id="fig:item-types"></span>
<img src="figures/appB-items_types.png" alt="*Primary*, *Secondary*, and *Tertiary* items and associated icons."  />
<p class="caption">
Figure B.4: <em>Primary</em>, <em>Secondary</em>, and <em>Tertiary</em> items and associated icons.
</p>
</div>
</div>
<div id="secondary" class="section level4 hasAnchor" number="12.9.1.2">
<h4><span class="header-section-number">B.9.1.2</span> Secondary items<a href="AppendixB.html#secondary" class="anchor-section" aria-label="Anchor link to header"></a></h4>
<p>These are different everyday IoT objects that players discard to make connections on the board using their <em>Primary</em> items. The <em>Function</em> of each <em>Secondary</em> item is between activating icons used by other cards (often <em>Risks</em>) and increasing skill levels as modifiers according to the colour of the card; orange for <em>Coding</em>, blue for <em>Observation</em>, and green for <em>Security</em>. Each time a player fails a <em>Risk Check</em> during their <em>Risk Phase</em> (see <a href="AppendixB.html#risk-check">B.11</a>), the <em>Effect</em> of that card is played out.</p>
</div>
<div id="tertiary" class="section level4 hasAnchor" number="12.9.1.3">
<h4><span class="header-section-number">B.9.1.3</span> Tertiary items<a href="AppendixB.html#tertiary" class="anchor-section" aria-label="Anchor link to header"></a></h4>
<p>These are either <em>Accounts</em> or <em>Buffs</em> both acting as benefits if players keep on hand, but come with associated higher risks if they become insecure (by failing a <em>Risk Check</em>). <em>Tertiary</em> items often act as modifiers when calculating dice counts for rolling. Furthermore, these cards usually may also be spent for an immediate bonus function. Players may spend these cards and take advantage of bonuses at any moment in the game. Once spent, the card must be discarded unless specified.</p>
</div>
</div>
<div id="risks" class="section level3 hasAnchor" number="12.9.2">
<h3><span class="header-section-number">B.9.2</span> Risks Deck<a href="AppendixB.html#risks" class="anchor-section" aria-label="Anchor link to header"></a></h3>
<p>This deck is full of all that can go wrong in the game! <a href="#fn98" class="footnote-ref" id="fnref98"><sup>98</sup></a> Each time a player fails the initial roll for <em>Security</em> during the <em>Risk Phase</em>, the top card is drawn from this deck and its <em>Function</em> played out. First, the number in the corner denotes how many steps forward the <em>Threat Tracker</em> moves (see <a href="AppendixB.html#threat-tracker">B.17</a>). Second, players collect dice equal to the totals of each skill represented on the card following the subtractions. The new dice roll is then used for each subsequent <em>Risk Check</em> (see <a href="AppendixB.html#risk-check">B.11</a>) in that phase. Finally, the player(s) takes any associated damage followed by the cards <em>Effect</em> immediately. Besides the regular <em>Risk</em> cards, there are also <em>Data Leaks</em>. These cards affect <strong>ALL</strong> players immediately triggering all <em>Privacy</em> tokens (see <a href="AppendixB.html#resolve">B.13</a>) and advancing the <em>Threat Tracker</em> (see <a href="AppendixB.html#threat-tracker">B.17</a>).</p>
<div class="figure"><span style="display:block;" id="fig:risks"></span>
<img src="figures/appB-risks.png" alt="Cards from the *Risks Deck* all have negative affects on players."  />
<p class="caption">
Figure B.5: Cards from the <em>Risks Deck</em> all have negative affects on players.
</p>
</div>
<div class="figure"><span style="display:block;" id="fig:privacy"></span>
<img src="figures/appB-privacy.png" alt="The *Privacy Deck* presents conditional loops as vignettes for players to deploy *Databoxes*"  />
<p class="caption">
Figure B.6: The <em>Privacy Deck</em> presents conditional loops as vignettes for players to deploy <em>Databoxes</em>
</p>
</div>
</div>
<div id="privacy" class="section level3 hasAnchor" number="12.9.3">
<h3><span class="header-section-number">B.9.3</span> Privacy Deck<a href="AppendixB.html#privacy" class="anchor-section" aria-label="Anchor link to header"></a></h3>
<p>Cards from here are invoked when players attempt a <em>Deploy</em> action for a <em>Databox</em> (see <a href="AppendixB.html#databox">B.16</a>) <a href="#fn99" class="footnote-ref" id="fnref99"><sup>99</sup></a>. Players must successfully navigate the different conditions presented stepwise otherwise face consequences. These cards require players to first roll according to the icon in the corners to see if they may proceed. If at any moment players fail a dice roll, they must execute the cards negative <em>Effect</em> at the very bottom and discard it. However, if they pass the initial roll, they enter the second step often requiring a more difficult skill check. Upon passing that as well, players may execute the positive <em>Effect</em> of the card along with deploying a <em>Databox</em>. For instance, the <em>Chasing Daemons</em> card (Fig. <a href="AppendixB.html#fig:privacy">B.6</a>) has players roll for <em>Coding</em> to be able to move forward to its next step, which further requires an <em>Observation</em> minus 1 check. Upon passing, this card gives the player not only a <em>Databox</em> but also +1 <em>Sanity</em>. If at any moment in this card the dice rolls fail, the negative <em>Effect</em> is played, and the player loses 1 <em>Security</em> skill discarding the card from the game.</p>
</div>
<div id="daemons" class="section level3 hasAnchor" number="12.9.4">
<h3><span class="header-section-number">B.9.4</span> Daemons Deck<a href="AppendixB.html#daemons" class="anchor-section" aria-label="Anchor link to header"></a></h3>
<p>These cards act like software daemons<a href="#fn100" class="footnote-ref" id="fnref100"><sup>100</sup></a> where it gets its name from. They are not drawn by choice and instead issued by other cards as constant <em>Effects</em> upon players; often reducing their skills and abilities (Fig. <a href="AppendixB.html#fig:daemons">B.7</a>). Many cards have an <em>Effect Amount</em> in the corner linked with the card. For instance, if a player receives a <em>Virus Daemon,</em> they must add 1 <em>Vulnerability</em> token on every space they move to. <em>Daemons</em> are stackable and may only be removed by doing a <em>Rest</em> action (see <a href="AppendixB.html#rest">B.15</a>) and attempting the cards <em>Resolve</em> portion.</p>
<div class="figure"><span style="display:block;" id="fig:daemons"></span>
<img src="figures/appB-daemons.png" alt="*Daemon* cards function as continuous negative *Affects* on players."  />
<p class="caption">
Figure B.7: <em>Daemon</em> cards function as continuous negative <em>Affects</em> on players.
</p>
</div>
</div>
</div>
<div id="connections" class="section level2 hasAnchor" number="12.10">
<h2><span class="header-section-number">B.10</span> Making Connections<a href="AppendixB.html#connections" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<p>Items collected throughout the game may be traded for <em>Connector</em> tokens (Fig. <a href="AppendixB.html#fig:connect">B.8</a>). This is an important part of play. To win players need to deploy <em>Databoxes</em> which can only be done in spaces that have reached their connection requirements. There are a few prerequisites To make a connection. First, a player must have a <strong><em>Primary Item</em></strong> on hand (see <a href="AppendixB.html#primary">B.9.1.1</a>). Second, players need to navigate to a space with an empty notch. Finally, connections can only be made by either discarding a <strong><em>Secondary Item</em></strong> (see <a href="AppendixB.html#secondary">B.9.1.2</a>) from their hand or using an item in the space.</p>
<div class="figure"><span style="display:block;" id="fig:connect"></span>
<img src="figures/appB-connect.png" alt="Physical spaces are connected using Connector tokens by discarding in-hand Secondary items or using the items in space"  />
<p class="caption">
Figure B.8: Physical spaces are connected using Connector tokens by discarding in-hand Secondary items or using the items in space
</p>
</div>
<p>Items in spaces are shown on the tiles and can only be connected to the notch they occupy. When players discard an item from hand to make a connection, they add a blue <em>Connection</em> token to their <em>Primary</em> item<a href="#fn101" class="footnote-ref" id="fnref101"><sup>101</sup></a>. Each new <em>Connector</em> makes a new <em>Connection</em> token on their card. These cannot be removed once added thus players must acquire new <em>Primary</em> items to make further connections if they reach their connection limit. As a bonus, using in-hand items to cover notches meant for items in spaces in the same action, gives the player two blue <em>Connection</em> tokens together to place on their <em>Primary</em> item. Finally, all notches on a tile may be used for connecting, even those on the outer rim of play.</p>
<div class="figure"><span style="display:block;" id="fig:risk-check"></span>
<img src="figures/appB-risk_check.png" alt="An example of performing a *Risk Check* on a players cards."  />
<p class="caption">
Figure B.9: An example of performing a <em>Risk Check</em> on a players cards.
</p>
</div>
</div>
<div id="risk-check" class="section level2 hasAnchor" number="12.11">
<h2><span class="header-section-number">B.11</span> Conducting Risk Checks<a href="AppendixB.html#risk-check" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<p>During play (particularly the <em>Risk Phase</em>) players will have to undergo <em>Risk Checks</em>. These are done by rolling <em>Security</em> on <strong>each</strong> item in hand. Failing any of the checks means executing that cards <em>Effect</em> portion (which could further trigger a secondary <em>Risk Check</em>). During the <em>Risk Phase</em>, these checks are more elaborate with the dice count being decided by the drawn card (Fig. <a href="AppendixB.html#fig:risk-check">B.9</a>) <a href="#fn102" class="footnote-ref" id="fnref102"><sup>102</sup></a>. For instance, the <em>Virus Attack</em> card (Fig. <a href="AppendixB.html#fig:risks">B.5</a>) tells the player to do the following in order:</p>
<ul>
<li><p>Move the <em>Threat Tracker</em> ahead 2 spaces.</p></li>
<li><p>Collect the total dice count of the player’s <em>Security</em>, <em>Observation</em>, and <em>Coding</em> skills.</p></li>
<li><p>Subtract that dice count by 6 to a minimum of 1 dice.</p></li>
<li><p>After using that new dice count to roll on all items in hand, reduce player <em>Security</em> skill by 1 as damage.</p></li>
<li><p>Then finally play any <em>Further Effects</em> on the card. In this case, the player takes an <em>Infected Daemon</em> (see <a href="AppendixB.html#daemons">B.9.4</a>) and rolls for <em>Privacy</em> (see <a href="AppendixB.html#resolve">B.13</a>).</p></li>
</ul>
</div>
<div id="tokens" class="section level2 hasAnchor" number="12.12">
<h2><span class="header-section-number">B.12</span> Tokens<a href="AppendixB.html#tokens" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<table>
<caption><span id="tab:tab-token">Table B.2: </span>There are a number of tokens in the game representing different functions and affects.</caption>
<colgroup>
<col width="13%" />
<col width="86%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Token</th>
<th align="left">Function (F) / Effect (E)</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left">Round Connector Tokens</td>
<td align="left">*(F)** Shows connections between physical spaces</td>
</tr>
<tr class="even">
<td align="left">Blue Connection Tokens</td>
<td align="left"><strong>(F)</strong> Denotes connections made during play on cards</td>
</tr>
<tr class="odd">
<td align="left">Orange Vulnerability Tokens</td>
<td align="left"><strong>(F)</strong> Denotes low-level insecurity issues within a space or item; <strong>(E)</strong> Converts into a <em>Threat</em> token if more than 2 in one space</td>
</tr>
<tr class="even">
<td align="left">Black Threat Tokens</td>
<td align="left"><strong>(F)</strong> Denotes high-level insecurity issues within a space; <strong>(E)</strong> Each <em>Threat</em> moves <em>Threat Tracker</em> ahead by 1 (see <a href="AppendixB.html#threat-tracker">B.17</a>)</td>
</tr>
<tr class="odd">
<td align="left">Privacy Tokens</td>
<td align="left"><strong>(F)</strong> Ticking time bomb that churns out <em>Vulnerability</em> tokens after certain events; <strong>(E)</strong> If the number of <em>Privacy</em> tokens exceeds the number of players the game is lost</td>
</tr>
<tr class="even">
<td align="left">Block Tokens</td>
<td align="left"><strong>(F)</strong> Denotes a disconnected space; <strong>(E)</strong> If <em>Block</em> tokens exceed the number of players the game is lost</td>
</tr>
<tr class="odd">
<td align="left">Databox Tokens</td>
<td align="left"><strong>(F)</strong> Marks the space as a <em>Databox</em>; <strong>(E)</strong> Step closer to victory (see <a href="AppendixB.html#databox">B.16</a>)</td>
</tr>
</tbody>
</table>

</div>
<div id="resolve" class="section level2 hasAnchor" number="12.13">
<h2><span class="header-section-number">B.13</span> Resolves and Other Actions<a href="AppendixB.html#resolve" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<p>When players are on a space or card that has an issue needing to be resolved (<em>Vulnerability</em>, <em>Threat</em> or <em>Privacy</em> tokens), they may encounter them as a <em>Resolve</em> action often by rolling for a skill. The interactions of the different tokens are shown in Fig. <a href="AppendixB.html#fig:resolve">B.10</a>.</p>
<div class="figure"><span style="display:block;" id="fig:resolve"></span>
<img src="figures/appB-resolve.png" alt="Different tokens have different interactions."  />
<p class="caption">
Figure B.10: Different tokens have different interactions.
</p>
</div>
<p><strong>Vulnerability:</strong> These tokens are easier to remove and simply take an action to clear 1 from the space occupied, unless a players avatar or other cards allow them to resolve multiple.</p>
<p><strong>Threats:</strong> If a space has 2 <em>Vulnerability</em> tokens, a third token would replace the 2 with a black <em>Threat</em> token. They are persistent, advance the <em>Threat Tracker</em> (see <a href="AppendixB.html#threat-tracker">B.17</a>), and require an <em>Attack Roll</em> to resolve (see <a href="AppendixB.html#attack">B.8.1</a>).</p>
<p><strong>Privacy Tokens:</strong> When instructed to roll for <em>Privacy</em> the player rolls <strong>1d6</strong> for each <em>Privacy</em> token in play; 1–4 is a fail, 5–6 is a pass (follow the difficulty level of the game, see <a href="AppendixB.html#setup">B.4</a>). If the player fails on any of the tokens the following happen in sequence: a <em>Threat</em> token is placed in the space occupied by the player; all adjacent spaces of the failed <em>Privacy</em> token receive <em>Vulnerability</em> tokens; all connected spaces from the <em>Privacy</em> token receive <em>Vulnerability</em> tokens. If during this action (or any other) the <em>Server</em> receives a <em>Vulnerability</em> or <em>Threat</em>, all spaces <strong>connected</strong> to the <em>Server</em> with <em>Connector</em> tokens will also receive <em>Vulnerability</em> tokens. <em>Privacy</em> tokens are removed through an <em>Attack Roll</em> (see <a href="AppendixB.html#attack">B.8.1</a>). If a <em>Privacy</em> token falls on the <em>Server</em>, <strong>players must resolve it within 1 round otherwise the game is lost</strong> (see <a href="AppendixB.html#end">B.18</a>).</p>
<p><strong>Block Tokens:</strong> Some cards, and in dire circumstances certain players, may <em>Block</em> a space. Place the Block token on the tile and remove any <em>Connector</em> tokens from it as well. These cannot be resolved; they are permanently disconnected spaces from the board. They do not accumulate any further tokens and any tokens present within if removed do not affect the <em>Threat Tracker</em>.</p>
</div>
<div id="delayed" class="section level2 hasAnchor" number="12.14">
<h2><span class="header-section-number">B.14</span> Being Delayed<a href="#fn103" class="footnote-ref" id="fnref103"><sup>103</sup></a><a href="AppendixB.html#delayed" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<p>At times players may become <em>Delayed</em> during play. This is not something they would do at will but be forced by cards. <em>Delayed</em> players skip the next <em>Action Phase</em>, but must endure the coming <em>Risk Phase</em> of that turn. To indicate a <em>Delayed</em> player, place their standee on its side in the space they occupy. After completing the <em>Risk Phase</em>, they may continue as before.</p>
</div>
<div id="rest" class="section level2 hasAnchor" number="12.15">
<h2><span class="header-section-number">B.15</span> Resting<a href="AppendixB.html#rest" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<p>As an action, players may <em>Rest</em> and regain 1 or more <em>Sanity</em>. During this players are also allowed to resolve any number of <em>Daemon</em> cards <strong>ONCE</strong> in that action. To do that, they must follow the <em>Resolve Function</em> on a <em>Daemon</em> card (see <a href="AppendixB.html#daemons">B.9.4</a>). Certain events and cards may allow players to do this function multiple times.</p>
</div>
<div id="databox" class="section level2 hasAnchor" number="12.16">
<h2><span class="header-section-number">B.16</span> Databoxes<a href="AppendixB.html#databox" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<p>To win, players must secure spaces with <em>Databoxes</em> equal to twice the number of players. These are special tokens that may only be placed in space after the connection requirements are fulfilled <strong>AND</strong> a player has a successful <em>Deploy</em> action (Fig. <a href="AppendixB.html#fig:databox">B.11</a>). When a player is ready to deploy a <em>Databox</em>, they spend 2 actions to draw the top card from the <em>Privacy Deck</em> following its conditions (see <a href="AppendixB.html#privacy">B.9.3</a>). Upon successfully navigating the card, a golden <em>Databox</em> token is placed in the space marking it as secure. <strong>No further tokens of any kind may come into a Databox.</strong> As a bonus, each Databox deployed will recede the <em>Threat Tracker</em> (see <a href="AppendixB.html#threat-tracker">B.17</a>) by 1 and if players manage to deploy a <em>Databox</em> in an <em>Insecure Tile</em>, they may recede the <em>Tracker</em> by 2!</p>
<div class="figure"><span style="display:block;" id="fig:databox"></span>
<img src="figures/appB-databox.png" alt="*Databoxes* are deployed by successfully completing Privacy cards."  />
<p class="caption">
Figure B.11: <em>Databoxes</em> are deployed by successfully completing Privacy cards.
</p>
</div>
</div>
<div id="threat-tracker" class="section level2 hasAnchor" number="12.17">
<h2><span class="header-section-number">B.17</span> Threat Tracker<a href="AppendixB.html#threat-tracker" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<p>The <em>Threat Tracker</em><a href="#fn104" class="footnote-ref" id="fnref104"><sup>104</sup></a> (Fig. <a href="AppendixB.html#fig:threat">B.12</a>) keeps track of when <em>The Crumble</em> occurs signifying a victory for the game. To stop that happening, players must attempt to finish before it reaches the end. The <em>Tracker</em> moves forward in two ways:</p>
<ol style="list-style-type: decimal">
<li>When a <em>Risk</em> card or other card moves it forward.</li>
<li>When a new <em>Threat</em> token appears in play.</li>
</ol>
<p>Certain card events may recede the <em>Tracker</em> during play. Players may only do so themselves by deploying a <em>Databox</em> (see <a href="AppendixB.html#databox">B.16</a>).</p>
<div class="figure"><span style="display:block;" id="fig:threat"></span>
<img src="figures/appB-threat_tracker.png" alt="The *Threat Tracker* counts down the end of the game and win for The Council"  />
<p class="caption">
Figure B.12: The <em>Threat Tracker</em> counts down the end of the game and win for The Council
</p>
</div>
</div>
<div id="end" class="section level2 hasAnchor" number="12.18">
<h2><span class="header-section-number">B.18</span> End of the Game<a href="AppendixB.html#end" class="anchor-section" aria-label="Anchor link to header"></a></h2>
<p>The game ends with either the players winning or losing to <em>The Council</em> (the board). <strong>Players may only win if they deploy <em>Databoxes</em> equal to twice the number of players.</strong> <em>The Council</em> wins if <strong>ANY</strong> of the following comes true:</p>
<ul>
<li>All players are <em>Delayed</em> together (see <a href="AppendixB.html#delayed">B.14</a>).</li>
<li>The <em>Threat Tracker</em> reaches the end (see <a href="AppendixB.html#threat-tracker">B.17</a>).</li>
<li>There are <em>Privacy</em> or <em>Block</em> tokens equal to more than the number of players (see <a href="AppendixB.html#resolve">B.13</a>).</li>
<li>There is a <em>Privacy</em> token on the <em>Server</em> and it’s not resolved within 1 round of play.</li>
</ul>
</div>
</div>
<div class="footnotes">
<hr />
<ol start="91">
<li id="fn91"><p>The addition of a backstory proved to be the most effective aspect of initiating play. Players felt more connected to rhetoric after situating it better.<a href="AppendixB.html#fnref91" class="footnote-back">↩︎</a></p></li>
<li id="fn92"><p>After play-testing the cooperative model of play worked the best as it was able to communicate the rhetoric most effectively compared to other approaches.<a href="AppendixB.html#fnref92" class="footnote-back">↩︎</a></p></li>
<li id="fn93"><p>This modular approach meant play time could be controlled better and allowed flexibility in levels of difficulty.<a href="AppendixB.html#fnref93" class="footnote-back">↩︎</a></p></li>
<li id="fn94"><p>A phase-based play approach was appropriated from both <em>Dead of Winter</em> and <em>Eldritch Horror</em> as it incorporated a more dynamic means for communicating rhetoric.<a href="AppendixB.html#fnref94" class="footnote-back">↩︎</a></p></li>
<li id="fn95"><p>In the latest iteration, terminologies were changed for ease as players felt ‘vulnerabilities’ was a mouthful during play. The term ‘risk’ was then adopted to denote a general understanding of urgency and peril throughout, whereas ‘vulnerabilities’ became a specific kind of token in-game.<a href="AppendixB.html#fnref95" class="footnote-back">↩︎</a></p></li>
<li id="fn96"><p>Avatar inclusion brought about an entire new dynamic in play. Players explained they embodied the game and understood the rhetoric much better through experiencing the many in-game vignettes as their avatars.<a href="AppendixB.html#fnref96" class="footnote-back">↩︎</a></p></li>
<li id="fn97"><p>Players mentioned this to be tedious yet enjoyable. As a takeaway, future iterations would look into approaching this interaction differently.<a href="AppendixB.html#fnref97" class="footnote-back">↩︎</a></p></li>
<li id="fn98"><p>Intended as a means of countermeasures and facilitating the game as a stand-alone player acting against the group.<a href="AppendixB.html#fnref98" class="footnote-back">↩︎</a></p></li>
<li id="fn99"><p>These cards take inspiration from the way cards are played in both <em>Eldritch Horror</em> and <em>Dead of Winter</em>. They act out a scenario entering players in a dialog with the game executed through dice rolls and vignettes.<a href="AppendixB.html#fnref99" class="footnote-back">↩︎</a></p></li>
<li id="fn100"><p>Programs that run in the background affecting systems in various ways.<a href="AppendixB.html#fnref100" class="footnote-back">↩︎</a></p></li>
<li id="fn101"><p>This mechanism intended to solidify concepts coming from the philosophical model into gameplay, essentially acting as physical representations of occurring digital interactions.<a href="AppendixB.html#fnref101" class="footnote-back">↩︎</a></p></li>
<li id="fn102"><p>This particular mechanism aided in making players realise that their own assumptions of control in IoT interactions might not be as they believe, with the varying dice counts affected by associated IoT risks hinting at the fallacy of IoT interactions.<a href="AppendixB.html#fnref102" class="footnote-back">↩︎</a></p></li>
<li id="fn103"><p>Being <em>Delayed</em> and <em>Resting</em> were among the many mechanisms added from <em>Eldritch Horror</em>, that said, these are still fairly common mechanisms used in modern board games. Though the names could have been changed, it was decided not to as this did little to affect the rhetoric and merely worked as a method to facilitate further play dynamics.<a href="AppendixB.html#fnref103" class="footnote-back">↩︎</a></p></li>
<li id="fn104"><p>This mechanism was appropriated from the <em>Doom Track</em> in <em>Eldritch Horror</em> which signified the end of or near end of game.<a href="AppendixB.html#fnref104" class="footnote-back">↩︎</a></p></li>
</ol>
</div>
            </section>

          </div>
        </div>
      </div>
<a href="AppendixA.html" class="navigation navigation-prev " aria-label="Previous page"><i class="fa fa-angle-left"></i></a>
<a href="AppendixC.html" class="navigation navigation-next " aria-label="Next page"><i class="fa fa-angle-right"></i></a>
    </div>
  </div>
<script src="libs/gitbook-2.6.7/js/app.min.js"></script>
<script src="libs/gitbook-2.6.7/js/clipboard.min.js"></script>
<script src="libs/gitbook-2.6.7/js/plugin-search.js"></script>
<script src="libs/gitbook-2.6.7/js/plugin-sharing.js"></script>
<script src="libs/gitbook-2.6.7/js/plugin-fontsettings.js"></script>
<script src="libs/gitbook-2.6.7/js/plugin-bookdown.js"></script>
<script src="libs/gitbook-2.6.7/js/jquery.highlight.js"></script>
<script src="libs/gitbook-2.6.7/js/plugin-clipboard.js"></script>
<script>
gitbook.require(["gitbook"], function(gitbook) {
gitbook.start({
"sharing": {
"github": false,
"facebook": true,
"twitter": true,
"linkedin": false,
"weibo": false,
"instapaper": false,
"vk": false,
"whatsapp": false,
"all": ["facebook", "twitter", "linkedin", "weibo", "instapaper"]
},
"fontsettings": {
"theme": "white",
"family": "sans",
"size": 2
},
"edit": {
"link": "https://github.com/USERNAME/REPO/edit/BRANCH/900-Appendix.Rmd",
"text": "Edit"
},
"history": {
"link": null,
"text": null
},
"view": {
"link": null,
"text": null
},
"download": null,
"search": {
"engine": "fuse",
"options": null
},
"toc": {
"collapse": "subsection"
}
});
});
</script>

<!-- dynamically load mathjax for compatibility with self-contained -->
<script>
  (function () {
    var script = document.createElement("script");
    script.type = "text/javascript";
    var src = "true";
    if (src === "" || src === "true") src = "https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.9/latest.js?config=TeX-MML-AM_CHTML";
    if (location.protocol !== "file:")
      if (/^https?:/.test(src))
        src = src.replace(/^https?:/, '');
    script.src = src;
    document.getElementsByTagName("head")[0].appendChild(script);
  })();
</script>
</body>

</html>