diff --git a/404.html b/404.html index e37a30e0..59581525 100644 --- a/404.html +++ b/404.html @@ -8,8 +8,7 @@ - - + @@ -23,7 +22,7 @@
- + \ No newline at end of file diff --git a/assets/app.Cxu4aH84.js b/assets/app.Cxu4aH84.js deleted file mode 100644 index f9711fe5..00000000 --- a/assets/app.Cxu4aH84.js +++ /dev/null @@ -1 +0,0 @@ -import{U as o,ap as p,aq as u,ar as l,as as c,at as f,au as d,av as m,aw as h,ax as A,ay as g,d as v,u as y,y as P,x as w,az as C,aA as R,aB as b,aC as E}from"./chunks/framework.CK8QU5WH.js";import{R as S}from"./chunks/theme.Lm1E6I-W.js";function i(e){if(e.extends){const a=i(e.extends);return{...a,...e,async enhanceApp(t){a.enhanceApp&&await a.enhanceApp(t),e.enhanceApp&&await e.enhanceApp(t)}}}return e}const s=i(S),T=v({name:"VitePressApp",setup(){const{site:e,lang:a,dir:t}=y();return P(()=>{w(()=>{document.documentElement.lang=a.value,document.documentElement.dir=t.value})}),e.value.router.prefetchLinks&&C(),R(),b(),s.setup&&s.setup(),()=>E(s.Layout)}});async function _(){globalThis.__VITEPRESS__=!0;const e=D(),a=x();a.provide(u,e);const t=l(e.route);return a.provide(c,t),a.component("Content",f),a.component("ClientOnly",d),Object.defineProperties(a.config.globalProperties,{$frontmatter:{get(){return t.frontmatter.value}},$params:{get(){return t.page.value.params}}}),s.enhanceApp&&await s.enhanceApp({app:a,router:e,siteData:m}),{app:a,router:e,data:t}}function x(){return h(T)}function D(){let e=o,a;return A(t=>{let n=g(t),r=null;return n&&(e&&(a=n),(e||a===n)&&(n=n.replace(/\.js$/,".lean.js")),r=import(n)),o&&(e=!1),r},s.NotFound)}o&&_().then(({app:e,router:a,data:t})=>{a.go().then(()=>{p(a.route,t.site),e.mount("#app")})});export{_ as createApp}; diff --git a/assets/changelog_index.md.gjqAjJbE.js b/assets/changelog_index.md.gjqAjJbE.js deleted file mode 100644 index 083c56b8..00000000 --- a/assets/changelog_index.md.gjqAjJbE.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as t,c as e,o as a,a5 as s}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Changelog","description":"","frontmatter":{"title":"Changelog","prev":false,"next":false},"headers":[],"relativePath":"changelog/index.md","filePath":"changelog/index.md"}'),n={name:"changelog/index.md"},o=s('

Changelog

This feed starts when I formatted the site to be a Digital Garden. If you'd like to look further into this site's history, check here!

6 files changed, 4 insertions(+), 8 deletions(-)

Pushed on
PageChanges
chat-glue2 +-
commune2 +-
fedi-v22 +-
guide-to-incrementals2 --
my-personal-website2 +-
my-projects2 --

3 files changed, 3 insertions(+), 3 deletions(-)

Pushed on
PageChanges
commune2 +-
incremental-social2 +-
the-small-web2 +-

2 files changed, 3 insertions(+), 1 deletion(-)

Pushed on
PageChanges
life-is-strange2 ++
my-personal-website2 +-

20 files changed, 274 insertions(+), 16 deletions(-)

Pushed on
PageChanges
artificial-intelligence28 ++++++++++++++++
command-palettes25 ++++++++++++++
fedi-v215 +++++----
fediverse2 +-
guide-to-incrementals2 ++
incremental-social2 +-
life-is-strange60 ++++++++++++++++++++++++++++++++++
logseq2 +-
mtx13 ++++++++
my-personal-website2 +-
my-projects2 ++
pre-order-bonuses28 ++++++++++++++++
premium-currency19 +++++++++++
social-media2 +-
the-beginner-s-guide2 +-
the-indieweb/amplification14 ++++++++
the-indieweb/signature-blocks10 ++++++
the-small-web8 +++--
video-game-monetization43 ++++++++++++++++++++++++
weird11 +++++--

4 files changed, 72 insertions(+)

Pushed on
PageChanges
davey-wreden22 ++++++++++++++++++++++
ivy-road15 +++++++++++++++
the-beginner-s-guide22 ++++++++++++++++++++++
wanderstop13 +++++++++++++

1 file changed, 11 insertions(+), 3 deletions(-)

Pushed on
PageChanges
the-small-web14 +++++++++++---

3 files changed, 48 insertions(+), 38 deletions(-)

Pushed on
PageChanges
digital-gardens2 +-
fedi-v23 +-
the-small-web81 +++++++++++++++++++++++++++---------------------

47 files changed, 124 insertions(+), 13 deletions(-)

Pushed on
PageChanges
activitypub2 ++
advent-incremental2 ++
atproto2 ++
babble-buds2 ++
capture-the-citadel2 ++
chat-glue2 ++
chronological2 ++
cinny2 ++
commune2 ++
decentralized2 ++
dice-armor2 ++
digital-gardens2 ++
federated-identity2 ++
fedi-v230 +++++++++++++++++-----
fediverse2 ++
forgejo2 ++
freeform-vs-chronological-dichotomy2 ++
freeform2 ++
game-dev-tree2 ++
garden-rss4 ++-
.../appeal-to-developers2 ++
guide-to-incrementals/appeal-to-players6 +++--
guide-to-incrementals/defining-the-genre6 +++--
guide-to-incrementals2 ++
.../navigating-criticism2 ++
guide-to-incrementals/what-is-content4 ++-
incremental-social2 ++
kronos2 ++
logseq2 ++
matrix2 ++
mbin2 ++
my-personal-website2 ++
my-projects2 ++
nostr2 ++
open-source2 ++
opti-speech2 ++
planar-pioneers2 ++
profectus4 ++-
social-media2 ++
synapse2 ++
the-cozy-web2 ++
the-small-web2 ++
this-knowledge-hub3 +++
v-ecs2 ++
vitepress2 ++
webrings2 ++
weird2 ++

47 files changed, 1226 insertions(+)

Pushed on
PageChanges
activitypub13 ++
advent-incremental21 +++
atproto18 +++
babble-buds22 ++++
capture-the-citadel15 +++
chat-glue12 ++
chronological21 +++
cinny10 ++
commune33 +++++
decentralized28 ++++
dice-armor55 ++++++++
digital-gardens20 +++
federated-identity23 ++++
fedi-v295 ++++++++++++++
fediverse21 +++
forgejo10 ++
freeform-vs-chronological-dichotomy10 ++
freeform17 +++
game-dev-tree17 +++
garden-rss22 ++++
.../appeal-to-developers30 +++++
guide-to-incrementals/appeal-to-players60 +++++++++
guide-to-incrementals/defining-the-genre141 +++++++++++++++++++++
guide-to-incrementals27 ++++
.../navigating-criticism26 ++++
guide-to-incrementals/what-is-content52 ++++++++
incremental-social16 +++
kronos18 +++
logseq10 ++
matrix10 ++
mbin12 ++
my-personal-website10 ++
my-projects27 ++++
nostr13 ++
open-source12 ++
opti-speech37 ++++++
planar-pioneers15 +++
profectus24 ++++
social-media25 ++++
synapse10 ++
the-cozy-web16 +++
the-small-web58 +++++++++
this-knowledge-hub22 ++++
v-ecs25 ++++
vitepress10 ++
webrings25 ++++
weird12 ++

',1),r=[o];function l(d,p,c,i,y,f){return a(),e("div",null,r)}const w=t(n,[["render",l]]);export{m as __pageData,w as default}; diff --git a/assets/changelog_index.md.gjqAjJbE.lean.js b/assets/changelog_index.md.gjqAjJbE.lean.js deleted file mode 100644 index f50e895e..00000000 --- a/assets/changelog_index.md.gjqAjJbE.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as t,c as e,o as a,a5 as s}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Changelog","description":"","frontmatter":{"title":"Changelog","prev":false,"next":false},"headers":[],"relativePath":"changelog/index.md","filePath":"changelog/index.md"}'),n={name:"changelog/index.md"},o=s("",1),r=[o];function l(d,p,c,i,y,f){return a(),e("div",null,r)}const w=t(n,[["render",l]]);export{m as __pageData,w as default}; diff --git a/assets/chunks/@localSearchIndexroot.Dijcf9Pd.js b/assets/chunks/@localSearchIndexroot.Dijcf9Pd.js deleted file mode 100644 index 04a9d1e2..00000000 --- a/assets/chunks/@localSearchIndexroot.Dijcf9Pd.js +++ /dev/null @@ -1 +0,0 @@ -const e='{"documentCount":122,"nextId":122,"documentIds":{"0":"/garden/activitypub/#activitypub","1":"/garden/advent-incremental/#advent-incremental","2":"/garden/artificial-intelligence/#artificial-intelligence","3":"/garden/atproto/#atproto","4":"/garden/babble-buds/#babble-buds","5":"/garden/capture-the-citadel/#capture-the-citadel","6":"/garden/chat-glue/#chat-glue","7":"/garden/chronological/#chronological","8":"/garden/cinny/#cinny","9":"/garden/command-palettes/#command-palettes","10":"/garden/commune/#commune","11":"/garden/davey-wreden/#davey-wreden","12":"/garden/decentralized/#decentralized","13":"/garden/dice-armor/#dice-armor","14":"/garden/digital-gardens/#digital-gardens","15":"/garden/federated-identity/#federated-identity","16":"/garden/fedi-v2/#fedi-v2","17":"/garden/fedi-v2/#inspiration","18":"/garden/fedi-v2/#identity","19":"/garden/fedi-v2/#servers","20":"/garden/fedi-v2/#content","21":"/garden/fedi-v2/#moderation","22":"/garden/fedi-v2/#problems-to-solve","23":"/garden/fediverse/#fediverse","24":"/garden/forgejo/#forgejo","25":"/garden/freeform-vs-chronological-dichotomy/#freeform-vs-chronological-dichotomy","26":"/garden/freeform/#freeform","27":"/garden/game-dev-tree/#game-dev-tree","28":"/garden/garden-rss/#garden-rss","29":"/garden/guide-to-incrementals/appeal-to-developers/#guide-to-incrementals-appeal-to-developers","30":"/garden/guide-to-incrementals/appeal-to-developers/#incrementals-are-easy-to-make","31":"/garden/guide-to-incrementals/appeal-to-developers/#players-are-easy-to-find","32":"/garden/guide-to-incrementals/appeal-to-developers/#monetization","33":"/garden/guide-to-incrementals/appeal-to-players/#guide-to-incrementals-appeal-to-players","34":"/garden/guide-to-incrementals/appeal-to-players/#numbers-going-up","35":"/garden/guide-to-incrementals/appeal-to-players/#effortlessness","36":"/garden/guide-to-incrementals/appeal-to-players/#strategy","37":"/garden/guide-to-incrementals/appeal-to-players/#avoiding-staleness","38":"/garden/guide-to-incrementals/appeal-to-players/#good-game-design","39":"/garden/guide-to-incrementals/appeal-to-players/#artistic-merit","40":"/garden/guide-to-incrementals/defining-the-genre/#guide-to-incrementals-defining-the-genre","41":"/garden/guide-to-incrementals/defining-the-genre/#incrementals-vs-idlers-vs-clickers","42":"/garden/guide-to-incrementals/defining-the-genre/#incrementals-as-ngu","43":"/garden/guide-to-incrementals/defining-the-genre/#roguelites-as-incrementals","44":"/garden/guide-to-incrementals/defining-the-genre/#the-berlin-interpretation","45":"/garden/guide-to-incrementals/defining-the-genre/#the-incremental-games-canon","46":"/garden/guide-to-incrementals/defining-the-genre/#the-paradigm-shift","47":"/garden/guide-to-incrementals/defining-the-genre/#high-value-factors","48":"/garden/guide-to-incrementals/defining-the-genre/#low-value-factors","49":"/garden/guide-to-incrementals/defining-the-genre/#are-roguelites-incrementals","50":"/garden/guide-to-incrementals/defining-the-genre/#sub-genres","51":"/garden/guide-to-incrementals/defining-the-genre/#other-related-genres","52":"/garden/guide-to-incrementals/#guide-to-incrementals","53":"/garden/guide-to-incrementals/#why-am-i-making-this","54":"/garden/guide-to-incrementals/#ludology","55":"/garden/guide-to-incrementals/#making-an-incremental","56":"/garden/guide-to-incrementals/navigating-criticism/#guide-to-incrementals-navigating-criticism","57":"/garden/guide-to-incrementals/navigating-criticism/#reading-feedback","58":"/garden/guide-to-incrementals/navigating-criticism/#seeking-feedback","59":"/garden/guide-to-incrementals/navigating-criticism/#responding-to-feedback","60":"/garden/guide-to-incrementals/what-is-content/#guide-to-incrementals-what-is-content","61":"/garden/guide-to-incrementals/what-is-content/#interaction","62":"/garden/guide-to-incrementals/what-is-content/#repeatable-purchases","63":"/garden/guide-to-incrementals/what-is-content/#following-instructions","64":"/garden/guide-to-incrementals/what-is-content/#tips-for-developers","65":"/garden/incremental-social/#incremental-social","66":"/garden/ivy-road/#ivy-road","67":"/garden/kronos/#kronos","68":"/garden/life-is-strange/#life-is-strange","69":"/garden/life-is-strange/#the-ending","70":"/garden/life-is-strange/#life-is-strange-before-the-storm","71":"/garden/life-is-strange/#the-awesome-adventures-of-captain-spirit","72":"/garden/life-is-strange/#life-is-strange-2","73":"/garden/life-is-strange/#life-is-strange-true-colors","74":"/garden/life-is-strange/#life-is-strange-double-exposure","75":"/garden/logseq/#logseq","76":"/garden/matrix/#matrix","77":"/garden/mbin/#mbin","78":"/garden/mtx/#mtx","79":"/garden/my-personal-website/#my-personal-website","80":"/garden/my-projects/#my-projects","81":"/garden/my-projects/#games","82":"/garden/my-projects/#tools-and-other-non-games","83":"/garden/nostr/#nostr","84":"/garden/open-source/#open-source","85":"/garden/opti-speech/#opti-speech","86":"/garden/opti-speech/#the-original-project","87":"/garden/opti-speech/#my-work","88":"/garden/planar-pioneers/#planar-pioneers","89":"/garden/pre-order-bonuses/#pre-order-bonuses","90":"/garden/premium-currency/#premium-currency","91":"/garden/profectus/#profectus","92":"/garden/social-media/#social-media","93":"/garden/synapse/#synapse","94":"/garden/the-beginner-s-guide/#the-beginner-s-guide","95":"/garden/the-cozy-web/#the-cozy-web","96":"/garden/the-indieweb/signature-blocks/#the-indieweb-signature-blocks","97":"/garden/the-indieweb/amplification/#the-indieweb-amplification","98":"/garden/the-small-web/#the-small-web","99":"/garden/the-small-web/#browsing-the-small-web","100":"/garden/the-small-web/#building-personal-websites","101":"/garden/the-small-web/#the-future","102":"/garden/the-small-web/#why-people-want-the-small-web","103":"/garden/the-small-web/#recommended-videos-about-the-small-web","104":"/garden/this-knowledge-hub/#this-knowledge-hub","105":"/garden/v-ecs/#v-ecs","106":"/garden/video-game-monetization/#video-game-monetization","107":"/garden/video-game-monetization/#aaa-games","108":"/garden/video-game-monetization/#free-to-play-games","109":"/garden/video-game-monetization/#indie-developers","110":"/garden/video-game-monetization/#ethical-game-monetization","111":"/garden/vitepress/#vitepress","112":"/garden/wanderstop/#wanderstop","113":"/garden/webrings/#webrings","114":"/garden/weird/#weird","115":"/now/#now","116":"/now/#life","117":"/now/#indieweb","118":"/now/#commune","119":"/now/#incremental-social","120":"/now/#chromatic-lattice","121":"/now/#kronos"},"fieldIds":{"title":0,"titles":1,"text":2},"fieldLength":{"0":[1,1,14],"1":[2,1,90],"2":[2,1,94],"3":[1,1,32],"4":[2,1,86],"5":[3,1,36],"6":[2,1,28],"7":[1,1,67],"8":[1,1,17],"9":[2,1,96],"10":[1,1,141],"11":[2,1,35],"12":[1,1,81],"13":[2,1,417],"14":[2,1,57],"15":[2,1,66],"16":[2,1,36],"17":[1,2,117],"18":[1,2,161],"19":[1,2,102],"20":[1,2,126],"21":[1,2,121],"22":[3,2,126],"23":[1,1,35],"24":[1,1,14],"25":[4,1,14],"26":[1,1,46],"27":[3,1,36],"28":[2,1,61],"29":[5,1,28],"30":[5,5,138],"31":[5,5,109],"32":[1,5,133],"33":[5,1,121],"34":[3,5,212],"35":[1,5,290],"36":[1,5,113],"37":[2,5,47],"38":[3,5,256],"39":[2,5,230],"40":[6,1,163],"41":[4,6,403],"42":[3,6,236],"43":[4,6,136],"44":[3,9,122],"45":[4,9,127],"46":[3,9,200],"47":[3,9,143],"48":[3,9,134],"49":[4,9,82],"50":[2,6,138],"51":[3,6,40],"52":[3,1,83],"53":[6,3,71],"54":[1,3,13],"55":[3,3,6],"56":[5,1,122],"57":[2,5,168],"58":[2,5,90],"59":[3,5,98],"60":[7,1,139],"61":[1,7,198],"62":[2,7,266],"63":[2,7,398],"64":[3,7,121],"65":[2,1,36],"66":[2,1,19],"67":[1,1,61],"68":[3,1,85],"69":[2,3,96],"70":[6,3,93],"71":[6,3,34],"72":[4,3,33],"73":[5,3,28],"74":[5,3,95],"75":[1,1,15],"76":[1,1,13],"77":[1,1,21],"78":[1,1,18],"79":[3,1,16],"80":[2,1,30],"81":[1,2,49],"82":[6,2,10],"83":[1,1,14],"84":[2,1,42],"85":[2,1,29],"86":[3,2,92],"87":[2,2,60],"88":[2,1,32],"89":[3,1,84],"90":[2,1,68],"91":[1,1,75],"92":[2,1,83],"93":[1,1,16],"94":[4,1,54],"95":[3,1,46],"96":[4,1,15],"97":[3,1,51],"98":[3,1,69],"99":[4,3,30],"100":[3,3,58],"101":[2,6,20],"102":[6,3,75],"103":[6,3,1],"104":[3,1,95],"105":[2,1,134],"106":[3,1,6],"107":[2,3,51],"108":[4,3,10],"109":[2,3,24],"110":[3,3,11],"111":[1,1,14],"112":[1,1,18],"113":[1,1,108],"114":[1,1,106],"115":[2,1,24],"116":[1,2,28],"117":[1,2,38],"118":[1,2,49],"119":[2,2,15],"120":[2,2,18],"121":[1,2,18]},"averageFieldLength":[2.5245901639344264,2.639344262295082,84.09016393442623],"storedFields":{"0":{"title":"ActivityPub","titles":[]},"1":{"title":"Advent Incremental","titles":[]},"2":{"title":"Artificial Intelligence","titles":[]},"3":{"title":"ATProto","titles":[]},"4":{"title":"Babble Buds","titles":[]},"5":{"title":"Capture the Citadel","titles":[]},"6":{"title":"Chat Glue","titles":[]},"7":{"title":"Chronological","titles":[]},"8":{"title":"Cinny","titles":[]},"9":{"title":"Command Palettes","titles":[]},"10":{"title":"Commune","titles":[]},"11":{"title":"Davey Wreden","titles":[]},"12":{"title":"Decentralized","titles":[]},"13":{"title":"Dice Armor","titles":[]},"14":{"title":"Digital Gardens","titles":[]},"15":{"title":"Federated Identity","titles":[]},"16":{"title":"Fedi v2","titles":[]},"17":{"title":"Inspiration","titles":["Fedi v2"]},"18":{"title":"Identity","titles":["Fedi v2"]},"19":{"title":"Servers","titles":["Fedi v2"]},"20":{"title":"Content","titles":["Fedi v2"]},"21":{"title":"Moderation","titles":["Fedi v2"]},"22":{"title":"Problems to solve","titles":["Fedi v2"]},"23":{"title":"Fediverse","titles":[]},"24":{"title":"Forgejo","titles":[]},"25":{"title":"Freeform vs Chronological Dichotomy","titles":[]},"26":{"title":"Freeform","titles":[]},"27":{"title":"Game Dev Tree","titles":[]},"28":{"title":"Garden-RSS","titles":[]},"29":{"title":"Guide to Incrementals/Appeal to Developers","titles":[]},"30":{"title":"Incrementals are Easy to Make","titles":["Guide to Incrementals/Appeal to Developers"]},"31":{"title":"Players are Easy to Find","titles":["Guide to Incrementals/Appeal to Developers"]},"32":{"title":"Monetization","titles":["Guide to Incrementals/Appeal to Developers"]},"33":{"title":"Guide to Incrementals/Appeal to Players","titles":[]},"34":{"title":"Numbers Going Up","titles":["Guide to Incrementals/Appeal to Players"]},"35":{"title":"Effortlessness","titles":["Guide to Incrementals/Appeal to Players"]},"36":{"title":"Strategy","titles":["Guide to Incrementals/Appeal to Players"]},"37":{"title":"Avoiding Staleness","titles":["Guide to Incrementals/Appeal to Players"]},"38":{"title":"Good Game Design","titles":["Guide to Incrementals/Appeal to Players"]},"39":{"title":"Artistic Merit","titles":["Guide to Incrementals/Appeal to Players"]},"40":{"title":"Guide to Incrementals/Defining the Genre","titles":[]},"41":{"title":"Incrementals vs Idlers vs Clickers","titles":["Guide to Incrementals/Defining the Genre"]},"42":{"title":"Incrementals as NGU","titles":["Guide to Incrementals/Defining the Genre"]},"43":{"title":"Roguelites as Incrementals?","titles":["Guide to Incrementals/Defining the Genre"]},"44":{"title":"The Berlin Interpretation","titles":["Guide to Incrementals/Defining the Genre","Roguelites as Incrementals?"]},"45":{"title":"The Incremental Games Canon","titles":["Guide to Incrementals/Defining the Genre","Roguelites as Incrementals?"]},"46":{"title":"The Paradigm Shift","titles":["Guide to Incrementals/Defining the Genre","Roguelites as Incrementals?"]},"47":{"title":"High-Value Factors","titles":["Guide to Incrementals/Defining the Genre","Roguelites as Incrementals?"]},"48":{"title":"Low-Value Factors","titles":["Guide to Incrementals/Defining the Genre","Roguelites as Incrementals?"]},"49":{"title":"Are Roguelites Incrementals?","titles":["Guide to Incrementals/Defining the Genre","Roguelites as Incrementals?"]},"50":{"title":"Sub-Genres","titles":["Guide to Incrementals/Defining the Genre"]},"51":{"title":"Other Related Genres","titles":["Guide to Incrementals/Defining the Genre"]},"52":{"title":"Guide to Incrementals","titles":[]},"53":{"title":"Why am I making this?","titles":["Guide to Incrementals"]},"54":{"title":"Ludology","titles":["Guide to Incrementals"]},"55":{"title":"Making an Incremental","titles":["Guide to Incrementals"]},"56":{"title":"Guide to Incrementals/Navigating Criticism","titles":[]},"57":{"title":"Reading Feedback","titles":["Guide to Incrementals/Navigating Criticism"]},"58":{"title":"Seeking Feedback","titles":["Guide to Incrementals/Navigating Criticism"]},"59":{"title":"Responding to Feedback","titles":["Guide to Incrementals/Navigating Criticism"]},"60":{"title":"Guide to Incrementals/What is Content?","titles":[]},"61":{"title":"Interaction","titles":["Guide to Incrementals/What is Content?"]},"62":{"title":"Repeatable Purchases","titles":["Guide to Incrementals/What is Content?","Interaction"]},"63":{"title":"Following Instructions","titles":["Guide to Incrementals/What is Content?"]},"64":{"title":"Tips for Developers","titles":["Guide to Incrementals/What is Content?"]},"65":{"title":"Incremental Social","titles":[]},"66":{"title":"Ivy Road","titles":[]},"67":{"title":"Kronos","titles":[]},"68":{"title":"Life is Strange","titles":[]},"69":{"title":"The ending","titles":["Life is Strange"]},"70":{"title":"Life is Strange: Before the Storm","titles":["Life is Strange"]},"71":{"title":"The Awesome Adventures of Captain Spirit","titles":["Life is Strange"]},"72":{"title":"Life is Strange 2","titles":["Life is Strange"]},"73":{"title":"Life is Strange: True Colors","titles":["Life is Strange"]},"74":{"title":"Life is Strange: Double Exposure","titles":["Life is Strange"]},"75":{"title":"Logseq","titles":[]},"76":{"title":"Matrix","titles":[]},"77":{"title":"Mbin","titles":[]},"78":{"title":"MTX","titles":[]},"79":{"title":"My Personal Website","titles":[]},"80":{"title":"My Projects","titles":[]},"81":{"title":"Games","titles":["My Projects"]},"82":{"title":"Tools (and other non-games)","titles":["My Projects"]},"83":{"title":"Nostr","titles":[]},"84":{"title":"Open Source","titles":[]},"85":{"title":"Opti-Speech","titles":[]},"86":{"title":"The Original Project","titles":["Opti-Speech"]},"87":{"title":"My Work","titles":["Opti-Speech"]},"88":{"title":"Planar Pioneers","titles":[]},"89":{"title":"Pre-Order Bonuses","titles":[]},"90":{"title":"Premium Currency","titles":[]},"91":{"title":"Profectus","titles":[]},"92":{"title":"Social Media","titles":[]},"93":{"title":"Synapse","titles":[]},"94":{"title":"The Beginner\'s Guide","titles":[]},"95":{"title":"The Cozy Web","titles":[]},"96":{"title":"The IndieWeb/Signature Blocks","titles":[]},"97":{"title":"The IndieWeb/Amplification","titles":[]},"98":{"title":"The Small Web","titles":[]},"99":{"title":"Browsing the small web","titles":["The Small Web"]},"100":{"title":"Building personal websites","titles":["The Small Web"]},"101":{"title":"The future","titles":["The Small Web","Building personal websites"]},"102":{"title":"Why people want the small web","titles":["The Small Web"]},"103":{"title":"Recommended videos about the small web","titles":["The Small Web"]},"104":{"title":"This Knowledge Hub","titles":[]},"105":{"title":"V-ecs","titles":[]},"106":{"title":"Video Game Monetization","titles":[]},"107":{"title":"AAA games","titles":["Video Game Monetization"]},"108":{"title":"Free-to-play games","titles":["Video Game Monetization"]},"109":{"title":"Indie developers","titles":["Video Game Monetization"]},"110":{"title":"Ethical game monetization","titles":["Video Game Monetization"]},"111":{"title":"Vitepress","titles":[]},"112":{"title":"Wanderstop","titles":[]},"113":{"title":"Webrings","titles":[]},"114":{"title":"Weird","titles":[]},"115":{"title":"/now","titles":[]},"116":{"title":"Life","titles":["/now"]},"117":{"title":"IndieWeb","titles":["/now"]},"118":{"title":"Commune","titles":["/now"]},"119":{"title":"Incremental Social","titles":["/now"]},"120":{"title":"Chromatic Lattice","titles":["/now"]},"121":{"title":"Kronos","titles":["/now"]}},"dirtCount":0,"index":[["😜",{"2":{"120":1}}],["😉",{"2":{"49":1}}],["`",{"2":{"105":1}}],["7l1i6k",{"2":{"70":1}}],["7l0vgq",{"2":{"70":1}}],["5",{"2":{"70":1}}],["5x",{"2":{"62":1}}],["2",{"0":{"72":1},"2":{"36":1,"67":1,"105":1}}],["2017",{"2":{"68":1}}],["20",{"2":{"11":1}}],["zero",{"2":{"34":1}}],["zitadel",{"2":{"15":1}}],["0",{"2":{"30":1,"61":1}}],["yet",{"2":{"30":1}}],["young",{"2":{"56":2}}],["yourself",{"2":{"13":1,"59":1}}],["your",{"2":{"12":1,"17":1,"18":2,"21":1,"22":1,"30":2,"31":3,"34":2,"35":3,"41":3,"52":1,"56":2,"57":5,"58":2,"59":4,"61":1,"63":4,"64":1,"92":1,"96":1,"97":1,"117":1}}],["you",{"2":{"4":2,"9":1,"13":3,"17":2,"18":9,"21":1,"22":5,"30":7,"31":3,"34":4,"35":11,"36":4,"38":2,"39":1,"40":1,"41":13,"45":2,"46":1,"47":1,"50":3,"52":1,"53":1,"56":4,"57":13,"58":4,"59":4,"60":2,"61":2,"62":9,"63":15,"64":4,"81":1,"90":1,"92":2,"102":1}}],["x",{"2":{"18":1}}],["jacorb",{"2":{"91":1}}],["jam",{"2":{"91":1}}],["javascript",{"2":{"30":2}}],["jesse",{"2":{"68":2}}],["jumping",{"2":{"63":1}}],["judge",{"2":{"44":1}}],["justify",{"2":{"107":1}}],["justified",{"2":{"63":1}}],["justifiably",{"2":{"45":1}}],["justifications",{"2":{"63":1}}],["justification",{"2":{"42":1,"63":2}}],["just",{"2":{"18":1,"20":3,"30":1,"31":1,"34":3,"35":1,"40":2,"41":3,"42":2,"43":1,"45":2,"46":4,"47":1,"49":1,"50":1,"57":1,"60":4,"61":2,"62":3,"63":3,"64":2,"70":1}}],["journey",{"2":{"56":1,"59":1}}],["journal",{"2":{"18":1,"104":1}}],["job",{"2":{"38":3,"105":1}}],["js",{"2":{"4":1}}],["queries",{"2":{"92":1}}],["queue",{"2":{"62":1}}],["questions",{"2":{"53":1}}],["question",{"2":{"53":1,"63":1}}],["qualifier",{"2":{"63":1}}],["qualifiers",{"2":{"63":1}}],["qualify",{"2":{"39":1,"44":1,"46":1,"49":1}}],["quality",{"2":{"60":1}}],["quaternion",{"2":{"13":1}}],["quickly",{"2":{"60":1,"62":1,"64":1}}],["quicker",{"2":{"13":1}}],["quite",{"2":{"30":1,"31":1,"32":1,"34":1,"35":1,"38":1,"42":1,"46":1,"60":1,"62":1,"70":2}}],["quoting",{"2":{"41":1}}],["quot",{"2":{"2":2,"7":4,"10":2,"12":2,"13":8,"18":6,"20":2,"32":2,"33":4,"35":8,"36":2,"37":4,"38":2,"39":6,"40":6,"41":28,"42":18,"44":10,"45":4,"46":6,"47":2,"49":2,"60":8,"61":2,"62":6,"63":8,"64":2,"68":2,"73":2,"91":2,"92":2,"99":2,"105":8,"113":4,"115":2}}],["3",{"2":{"13":1,"70":2}}],["3d",{"2":{"5":1,"85":1}}],["kronos",{"0":{"67":1,"121":1},"2":{"80":1,"81":1,"91":1,"105":1}}],["kate",{"2":{"68":1}}],["karla",{"2":{"66":1}}],["kasperzutterman",{"2":{"14":1}}],["knight",{"2":{"50":1}}],["known",{"2":{"95":1,"99":1,"120":1}}],["knowledge",{"0":{"104":1},"2":{"7":1,"14":1,"28":1,"30":1,"35":1,"75":1,"98":1,"104":1,"111":1}}],["know",{"2":{"1":1,"19":1,"31":1,"53":1,"63":1,"107":1}}],["kit",{"2":{"68":1}}],["kitten",{"2":{"45":1}}],["kittens",{"2":{"32":1}}],["kimonja",{"2":{"66":1}}],["kidding",{"2":{"45":1}}],["kind",{"2":{"41":2,"58":1}}],["kinds",{"2":{"36":1}}],["keeps",{"2":{"35":1}}],["keep",{"2":{"20":1,"35":1,"37":2,"41":2,"47":1,"52":1,"57":1,"59":2,"60":1}}],["keychains",{"2":{"89":1}}],["key",{"2":{"18":2,"20":1,"21":3,"22":2,"105":1}}],["keys",{"2":{"18":2}}],["keypairs",{"2":{"15":1,"22":1}}],["k",{"2":{"9":2}}],["rsi",{"2":{"61":1}}],["rss",{"0":{"28":1},"2":{"7":1,"12":1,"14":1,"26":3,"28":3,"104":2}}],["ridge",{"2":{"86":1}}],["rise",{"2":{"38":1}}],["right",{"2":{"17":1,"62":1,"84":1}}],["r",{"2":{"31":1,"35":2,"41":1,"70":2}}],["raising",{"2":{"107":1}}],["race",{"2":{"107":1}}],["ratio",{"2":{"90":1}}],["rather",{"2":{"35":2,"44":1,"61":1,"70":1,"113":1}}],["rarely",{"2":{"47":1}}],["rarer",{"2":{"42":1}}],["rauthy",{"2":{"15":1}}],["ran",{"2":{"18":1}}],["random",{"2":{"13":1,"99":1}}],["range",{"2":{"13":1}}],["rule",{"2":{"50":1}}],["rules",{"2":{"12":1,"21":1,"22":1,"92":1,"118":1}}],["ruined",{"2":{"38":1,"41":1}}],["running",{"2":{"119":1}}],["runs",{"2":{"34":1,"35":1}}],["run",{"2":{"13":1,"17":1,"30":1}}],["rocket",{"2":{"63":2}}],["roblox",{"2":{"63":1}}],["robert",{"2":{"4":1}}],["route",{"2":{"63":1}}],["room",{"2":{"45":1,"46":1,"113":4}}],["roguetemple",{"2":{"44":1}}],["rogue",{"2":{"43":1}}],["roguelike",{"2":{"44":4}}],["roguelikeness",{"2":{"44":1}}],["roguelikes",{"2":{"34":2,"43":1,"44":2}}],["roguelites",{"0":{"43":1,"49":1},"1":{"44":1,"45":1,"46":1,"47":1,"48":1,"49":1},"2":{"43":5}}],["roguelite",{"2":{"40":1,"49":1}}],["rolling",{"2":{"13":3}}],["road",{"0":{"66":1},"2":{"11":3,"66":1,"112":1}}],["rpgs",{"2":{"42":6,"51":1}}],["rpg",{"2":{"4":1}}],["rehosted",{"2":{"97":1}}],["reblogging",{"2":{"97":1}}],["red",{"2":{"86":2}}],["redistribute",{"2":{"84":1}}],["reddit",{"2":{"70":2,"77":1}}],["reduce",{"2":{"46":1,"60":1}}],["reduced",{"2":{"41":1,"47":2}}],["redundancy",{"2":{"22":1}}],["return",{"2":{"89":1}}],["returning",{"2":{"74":1}}],["returns",{"2":{"62":1}}],["rethinking",{"2":{"17":1}}],["reveals",{"2":{"43":1}}],["revealing",{"2":{"41":1,"74":1}}],["reward",{"2":{"41":1,"62":1,"63":1}}],["rewards",{"2":{"41":2}}],["rewarding",{"2":{"35":1,"63":1}}],["regard",{"2":{"63":1}}],["regardless",{"2":{"57":1,"71":1}}],["regarding",{"2":{"52":1}}],["regen",{"2":{"38":1}}],["regularly",{"2":{"59":1}}],["regular",{"2":{"32":1}}],["reiterate",{"2":{"34":1}}],["requiring",{"2":{"33":1,"41":1}}],["requirements",{"2":{"64":1,"110":1}}],["required",{"2":{"19":1,"48":1,"107":1}}],["requires",{"2":{"17":1,"41":1,"48":1}}],["require",{"2":{"15":1,"19":1,"30":1}}],["request",{"2":{"21":1}}],["requests",{"2":{"21":1}}],["recognize",{"2":{"58":1}}],["recommend",{"2":{"27":1,"38":1}}],["recommended",{"0":{"103":1},"2":{"13":1}}],["recent",{"2":{"63":1}}],["recently",{"2":{"33":1}}],["receive",{"2":{"57":1,"90":1}}],["received",{"2":{"19":1,"59":2}}],["receiving",{"2":{"22":2,"58":1,"90":1}}],["reasoning",{"2":{"47":1}}],["reason",{"2":{"42":1,"63":1}}],["reasonable",{"2":{"39":1}}],["reasons",{"2":{"29":1,"35":1,"40":1,"46":1,"59":1,"90":1}}],["reading",{"0":{"57":1},"2":{"61":1,"63":1}}],["readily",{"2":{"38":1}}],["read",{"2":{"56":1,"57":1}}],["readers",{"2":{"113":1}}],["reader",{"2":{"33":1}}],["readable",{"2":{"18":1}}],["reactivity",{"2":{"91":1}}],["reacting",{"2":{"20":1}}],["reached",{"2":{"62":1}}],["reach",{"2":{"18":1,"35":1,"36":1,"53":1,"63":2}}],["realm",{"2":{"45":1}}],["really",{"2":{"2":1,"7":1,"35":1,"46":1,"63":2,"68":1,"70":1,"71":1}}],["real",{"2":{"1":1,"34":1,"35":1,"41":1,"78":1,"85":1,"86":1,"90":1}}],["reliant",{"2":{"48":1,"114":1}}],["rely",{"2":{"38":1,"69":1}}],["relying",{"2":{"15":1,"69":1}}],["relevant",{"2":{"34":1,"39":1,"52":1,"63":1,"113":1}}],["relaying",{"2":{"21":1,"22":1}}],["relays",{"2":{"18":1,"19":2,"20":1,"21":1}}],["relay",{"2":{"17":1,"19":2,"21":1,"22":2}}],["relationships",{"2":{"94":1}}],["relationship",{"2":{"68":1,"94":1}}],["relation",{"2":{"42":1}}],["relative",{"2":{"13":1}}],["relates",{"2":{"42":1}}],["relate",{"2":{"10":1}}],["related",{"0":{"51":1},"2":{"10":2,"13":1,"30":1,"42":1,"50":2,"113":3}}],["resume",{"2":{"48":1}}],["results",{"2":{"13":1}}],["result",{"2":{"1":1,"39":1}}],["resource",{"2":{"47":1,"48":1,"49":1,"63":1}}],["resources",{"2":{"14":1,"35":1,"41":2,"42":1,"47":1,"69":1,"100":1}}],["resets",{"2":{"63":1}}],["resetting",{"2":{"63":1}}],["reset",{"2":{"40":1,"43":1,"46":2,"63":7}}],["restrain",{"2":{"91":1}}],["rest",{"2":{"40":1,"50":1,"72":1}}],["responsibility",{"2":{"69":1}}],["response",{"2":{"34":1,"41":1,"59":1}}],["responding",{"0":{"59":1}}],["respectively",{"2":{"62":1}}],["respect",{"2":{"21":1}}],["respected",{"2":{"20":1}}],["render",{"2":{"105":1}}],["rendered",{"2":{"104":1}}],["renderers",{"2":{"105":2}}],["renderer",{"2":{"4":1}}],["rendering",{"2":{"13":1,"30":1}}],["remember",{"2":{"59":1}}],["remembering",{"2":{"9":1}}],["remind",{"2":{"59":1}}],["reminder",{"2":{"47":1}}],["reminded",{"2":{"35":1}}],["removing",{"2":{"21":1,"38":1}}],["removes",{"2":{"13":1}}],["re",{"2":{"5":1,"10":1,"31":1,"35":3,"36":2,"38":1,"43":1,"46":1,"48":1,"56":1,"57":2,"58":1,"60":1,"61":2,"62":5,"63":5,"64":1,"74":1,"97":1}}],["repurcussions",{"2":{"47":1}}],["representation",{"2":{"47":2}}],["repetitive",{"2":{"37":1}}],["repeatable",{"0":{"62":1},"2":{"62":6}}],["repeat",{"2":{"35":1}}],["report",{"2":{"57":1}}],["reports",{"2":{"21":4}}],["reportedly",{"2":{"34":1}}],["reported",{"2":{"21":1}}],["repository",{"2":{"4":1,"24":1}}],["replacing",{"2":{"34":1,"63":2}}],["replaced",{"2":{"44":1,"45":1,"48":1}}],["replace",{"2":{"20":1,"46":1}}],["replying",{"2":{"20":1,"21":1}}],["reply",{"2":{"20":1,"21":1}}],["replicated",{"2":{"105":1}}],["replied",{"2":{"20":1}}],["replies",{"2":{"19":2,"20":1,"21":3}}],["replit",{"2":{"4":1,"31":1}}],["referred",{"2":{"46":1}}],["refer",{"2":{"41":2,"46":1}}],["refers",{"2":{"2":1,"23":1,"95":1,"97":1}}],["referenced",{"2":{"0":1,"2":1,"3":1,"6":1,"7":1,"8":1,"10":1,"11":1,"12":1,"13":1,"14":1,"15":1,"16":1,"23":1,"24":1,"25":1,"26":1,"28":1,"65":1,"66":1,"67":1,"75":1,"76":1,"77":1,"78":1,"79":1,"83":1,"84":1,"89":1,"90":1,"91":1,"92":1,"93":1,"95":1,"98":1,"104":1,"106":1,"111":1,"113":1,"114":1}}],["ndi",{"2":{"86":1}}],["n",{"2":{"64":2,"86":1}}],["numeric",{"2":{"48":1}}],["numerous",{"2":{"39":1}}],["numbers",{"0":{"34":1},"2":{"34":2,"38":1,"40":1,"41":1,"42":7,"48":2,"62":1}}],["number",{"2":{"3":1,"13":1,"30":1,"34":1,"60":1,"64":1}}],["ngu",{"0":{"42":1},"2":{"32":1,"45":1,"50":1}}],["national",{"2":{"86":1}}],["natural",{"2":{"56":1}}],["naturally",{"2":{"20":1,"34":1,"59":1}}],["nature",{"2":{"32":2}}],["navigate",{"2":{"56":1}}],["navigating",{"0":{"56":1},"1":{"57":1,"58":1,"59":1},"2":{"55":1}}],["narrow",{"2":{"45":1}}],["narratively",{"2":{"74":2,"121":1}}],["narrative",{"2":{"13":1,"39":2,"42":1,"63":2,"68":1,"112":1}}],["naked",{"2":{"41":1}}],["naming",{"2":{"18":8}}],["namely",{"2":{"87":1}}],["nameserver",{"2":{"18":1}}],["names",{"2":{"18":1,"42":1,"117":1}}],["name",{"2":{"9":1,"16":1,"18":3}}],["nih",{"2":{"86":1}}],["nitpicky",{"2":{"60":1}}],["nicely",{"2":{"30":1}}],["nicky",{"2":{"2":1}}],["nine",{"2":{"13":1}}],["nomadic",{"2":{"102":1}}],["novel",{"2":{"86":1}}],["nor",{"2":{"53":1,"69":1}}],["norm",{"2":{"32":1}}],["normal",{"2":{"30":1,"62":2}}],["normals",{"2":{"13":1}}],["node",{"2":{"46":2}}],["nonexistent",{"2":{"63":1}}],["none",{"2":{"48":1,"63":1,"94":1}}],["non",{"0":{"82":1},"2":{"17":1,"32":1,"33":1,"42":1,"47":1,"48":1,"61":1,"63":1,"99":1}}],["no",{"2":{"12":3,"18":1,"19":2,"22":1,"30":1,"39":1,"42":1,"44":1,"48":2,"56":1,"59":1,"61":1,"63":3,"64":1,"90":1,"94":1,"110":1}}],["nostr",{"0":{"83":1},"2":{"12":1,"17":1,"23":1,"83":1}}],["notable",{"2":{"50":4}}],["notably",{"2":{"42":1,"46":1,"65":1}}],["nothing",{"2":{"39":1,"60":1}}],["notice",{"2":{"38":1}}],["not",{"2":{"10":1,"13":3,"15":2,"17":2,"18":1,"22":2,"26":1,"28":1,"33":2,"34":3,"35":4,"36":1,"38":4,"39":2,"41":8,"42":4,"43":1,"44":3,"46":1,"47":2,"48":1,"53":1,"57":4,"60":2,"61":9,"62":4,"63":4,"69":3,"86":1,"91":1,"92":1,"95":2,"97":1,"104":2,"107":1,"114":1,"118":1}}],["notes",{"2":{"117":1}}],["note",{"2":{"4":1,"34":1,"36":1,"38":1,"44":1,"52":2,"63":1}}],["now",{"0":{"115":1},"1":{"116":1,"117":1,"118":1,"119":1,"120":1,"121":1},"2":{"10":1,"11":1,"30":1,"31":1,"45":2,"50":1,"63":3,"65":1,"87":1,"98":1,"115":2,"120":1}}],["netizens",{"2":{"114":1}}],["network",{"2":{"16":1,"19":1,"20":2,"113":1}}],["neocities",{"2":{"100":1,"102":1}}],["neutral",{"2":{"63":1}}],["nearly",{"2":{"63":1}}],["never",{"2":{"47":1,"49":1,"57":3,"59":1,"62":1,"105":1}}],["neither",{"2":{"41":1}}],["nebulous",{"2":{"39":1}}],["necessarily",{"2":{"41":1,"61":1,"63":1}}],["necessary",{"2":{"18":1,"30":1,"33":1}}],["necessity",{"2":{"39":1}}],["negative",{"2":{"33":1,"57":1,"59":3}}],["next",{"2":{"13":2,"42":1,"46":1,"61":1,"62":1,"64":2,"114":1}}],["needing",{"2":{"63":1}}],["need",{"2":{"4":1,"17":1,"18":2,"19":1,"30":4,"40":1,"42":1,"47":1,"57":2,"60":1,"61":1,"62":2,"92":1}}],["newly",{"2":{"46":1}}],["newer",{"2":{"45":1}}],["new",{"2":{"1":1,"13":3,"16":1,"18":3,"19":1,"20":1,"22":2,"30":1,"31":3,"34":1,"43":1,"44":1,"48":1,"63":7,"64":1,"87":1,"114":2}}],["+",{"2":{"2":1,"13":1}}],["4o",{"2":{"2":1}}],["vue",{"2":{"91":1}}],["vulkan",{"2":{"105":1}}],["vulintus",{"2":{"86":1}}],["vulnerable",{"2":{"56":1}}],["v",{"0":{"105":1},"2":{"67":1,"80":1,"82":1,"105":1}}],["voxel",{"2":{"105":2}}],["vouch",{"2":{"18":1}}],["voice",{"2":{"2":1,"62":1,"68":1}}],["varying",{"2":{"104":1}}],["variant",{"2":{"49":1}}],["variation",{"2":{"49":1}}],["variety",{"2":{"40":1,"45":1}}],["various",{"2":{"10":1,"13":1,"37":1,"39":1,"52":1,"61":1,"63":1,"100":1,"114":1,"117":2}}],["vague",{"2":{"40":1,"42":1,"57":1}}],["valid",{"2":{"61":1}}],["validating",{"2":{"15":1}}],["value",{"0":{"47":1,"48":1},"2":{"39":1,"41":2,"46":1,"47":1,"48":2,"60":1,"74":1}}],["vampire",{"2":{"33":3,"34":2,"35":1,"36":3,"39":3}}],["vex",{"2":{"105":1}}],["version",{"2":{"67":1,"87":1}}],["versions",{"2":{"41":1}}],["versus",{"2":{"42":2}}],["verifies",{"2":{"18":1,"20":1}}],["verify",{"2":{"18":2}}],["very",{"2":{"9":1,"10":1,"31":1,"32":1,"34":1,"39":1,"41":2,"44":1,"47":1,"56":1,"63":1,"68":1,"69":1,"74":1,"121":1}}],["ve",{"2":{"13":3,"18":1,"31":1,"32":1,"34":1,"36":1,"40":1,"45":1,"47":1,"53":1,"58":2,"59":2,"60":1,"62":3,"63":1,"67":1,"71":1,"72":1,"117":2}}],["v2",{"0":{"16":1},"1":{"17":1,"18":1,"19":1,"20":1,"21":1,"22":1},"2":{"10":1,"12":1,"15":1,"23":1,"92":1,"114":2}}],["virtual",{"2":{"86":1}}],["virtue",{"2":{"17":1,"23":1}}],["vitepress",{"0":{"111":1},"2":{"84":1,"104":1,"111":1}}],["vital",{"2":{"57":1}}],["views",{"2":{"52":1}}],["viewed",{"2":{"17":1,"86":1}}],["viable",{"2":{"30":1,"43":1}}],["via",{"2":{"18":1,"41":1}}],["vision",{"2":{"59":1,"113":1}}],["visit",{"2":{"5":1,"13":2}}],["visual",{"2":{"9":1,"47":2,"85":1}}],["videos",{"0":{"103":1},"2":{"41":1}}],["video",{"0":{"106":1},"1":{"107":1,"108":1,"109":1,"110":1},"2":{"2":1,"20":1,"33":7,"35":2,"38":1,"39":2,"40":1,"41":2,"52":1,"68":1,"74":1,"78":2,"86":2,"89":1,"94":1}}],["vr",{"2":{"5":2}}],["vs",{"0":{"25":1,"41":2},"2":{"2":1,"7":2,"25":1,"26":2,"39":1,"42":1}}],["gci",{"2":{"63":1}}],["guy",{"2":{"38":1}}],["guidance",{"2":{"58":1}}],["guiding",{"2":{"42":1}}],["guides",{"2":{"63":1}}],["guide",{"0":{"29":1,"33":1,"40":1,"52":1,"56":1,"60":1,"94":1},"1":{"30":1,"31":1,"32":1,"34":1,"35":1,"36":1,"37":1,"38":1,"39":1,"41":1,"42":1,"43":1,"44":1,"45":1,"46":1,"47":1,"48":1,"49":1,"50":1,"51":1,"53":1,"54":1,"55":1,"57":1,"58":1,"59":1,"61":1,"62":1,"63":1,"64":1},"2":{"11":3,"13":1,"34":1,"40":1,"41":2,"46":1,"48":1,"52":1,"53":1,"54":4,"55":1,"63":2,"94":2}}],["guild",{"2":{"10":1}}],["g",{"2":{"18":1,"86":1,"113":1}}],["glimpse",{"2":{"115":1}}],["glitch",{"2":{"31":1}}],["glyph",{"2":{"13":1}}],["glue",{"0":{"6":1},"2":{"6":1,"10":1}}],["gds",{"2":{"13":1}}],["got",{"2":{"68":1,"69":2,"71":1}}],["gotten",{"2":{"63":1}}],["gods",{"2":{"50":1}}],["goes",{"2":{"35":1,"61":1,"62":1,"67":1,"117":1}}],["gone",{"2":{"35":1}}],["goals",{"2":{"61":2}}],["goal",{"2":{"35":1,"41":1,"48":2,"49":1,"60":2}}],["goods",{"2":{"89":2}}],["good",{"0":{"38":1},"2":{"27":1,"33":1,"35":2,"36":1,"38":8,"41":1,"43":1,"53":1,"58":1,"62":1,"63":1,"68":1,"70":1,"71":1}}],["go",{"2":{"13":1,"30":1,"40":1,"41":1,"50":1,"61":1,"62":1,"63":2,"64":1}}],["going",{"0":{"34":1},"2":{"13":2,"30":1,"34":2,"40":1,"42":5,"46":1,"61":1,"63":4,"81":1,"87":1}}],["git",{"2":{"28":1,"104":1}}],["github",{"2":{"4":1,"14":3,"31":1,"100":1}}],["giving",{"2":{"13":1,"38":1,"41":2,"62":1,"114":1}}],["gives",{"2":{"104":1}}],["given",{"2":{"19":1,"89":1,"90":1}}],["give",{"2":{"13":1,"38":1,"40":1,"63":3,"64":1}}],["gimli",{"2":{"10":1}}],["graph",{"2":{"114":1}}],["graphics",{"2":{"107":2}}],["grave",{"2":{"105":1}}],["grasshopping",{"2":{"63":1}}],["grasshop",{"2":{"63":1}}],["grass",{"2":{"63":6}}],["grain",{"2":{"57":1}}],["grants",{"2":{"84":1}}],["granting",{"2":{"21":1}}],["grant",{"2":{"5":2}}],["groundhog",{"2":{"50":1}}],["group",{"2":{"20":1,"92":3}}],["groups",{"2":{"20":1,"21":1,"92":1}}],["grown",{"2":{"69":1}}],["grow",{"2":{"48":1,"56":1,"113":1}}],["growth",{"2":{"48":2,"50":1}}],["growing",{"2":{"45":1}}],["grinder",{"2":{"45":1}}],["grdn",{"2":{"28":2}}],["green",{"2":{"86":2}}],["grey",{"2":{"39":1}}],["greyed",{"2":{"13":1}}],["great",{"2":{"10":1,"38":1,"41":1,"57":1}}],["gathering",{"2":{"63":1}}],["gain",{"2":{"36":1,"64":1}}],["gaining",{"2":{"34":1,"42":1}}],["gambling",{"2":{"35":2}}],["gamers",{"2":{"32":1,"38":1,"39":1,"61":1}}],["gamedev",{"2":{"30":1}}],["gameplay",{"2":{"13":1,"35":2,"37":4,"38":1,"39":1,"41":1,"42":2,"46":2,"47":1,"60":1,"61":1,"63":2,"67":1,"105":1}}],["games",{"0":{"45":1,"81":1,"82":1,"107":1,"108":1},"2":{"1":1,"11":1,"29":1,"30":1,"31":5,"32":7,"33":5,"34":5,"35":19,"36":5,"37":1,"38":7,"39":11,"40":10,"41":43,"42":16,"43":3,"44":5,"45":5,"46":8,"47":1,"48":4,"49":1,"50":9,"51":3,"52":3,"53":3,"56":3,"57":1,"58":1,"60":6,"61":5,"63":4,"64":1,"65":1,"68":2,"74":1,"78":1,"80":1,"91":3,"105":1,"107":3,"113":2}}],["game",{"0":{"27":1,"38":1,"106":1,"110":1},"1":{"107":1,"108":1,"109":1,"110":1},"2":{"1":4,"5":2,"11":1,"13":13,"27":3,"30":1,"31":4,"32":2,"33":1,"34":6,"35":10,"36":3,"37":2,"38":13,"39":4,"40":4,"41":13,"42":2,"44":5,"45":2,"46":5,"47":9,"48":5,"49":3,"50":1,"52":2,"53":3,"56":3,"57":6,"58":4,"59":2,"60":3,"61":2,"62":1,"63":10,"64":1,"66":1,"67":1,"68":2,"69":2,"70":2,"72":1,"73":1,"74":5,"78":1,"80":1,"81":1,"84":1,"88":3,"89":3,"90":1,"91":1,"94":2,"105":3,"110":1,"112":2,"113":2,"120":1,"121":1}}],["gardeners",{"2":{"14":1}}],["garden",{"0":{"28":1},"2":{"14":1,"26":2,"52":1,"91":1,"104":2}}],["gardening",{"2":{"10":1,"28":1}}],["gardens",{"0":{"14":1},"2":{"7":2,"10":2,"14":3,"26":1,"28":2,"95":2,"104":1,"118":1}}],["geocities",{"2":{"102":1}}],["gets",{"2":{"34":1,"46":1,"62":2,"63":1}}],["get",{"2":{"34":1,"35":2,"41":1,"42":1,"45":2,"48":1,"51":1,"56":1,"57":2,"58":1,"59":1,"60":1,"61":1,"63":4,"68":1,"70":1,"74":1}}],["getting",{"2":{"31":1,"35":1,"38":2,"51":1,"58":1,"59":2,"62":1,"63":1,"74":1,"92":1}}],["gen",{"2":{"114":1}}],["generic",{"2":{"63":2}}],["generalize",{"2":{"33":1}}],["general",{"2":{"21":1,"31":1,"46":1,"70":1,"87":1}}],["generator",{"2":{"111":1}}],["generators",{"2":{"2":1}}],["generated",{"2":{"105":1}}],["generate",{"2":{"13":1,"22":1}}],["generative",{"2":{"2":1}}],["genres",{"0":{"50":1,"51":1},"2":{"30":3,"35":1,"38":1,"39":1,"40":1,"41":3,"42":1,"43":1,"44":2,"48":1,"50":1,"53":1,"63":1}}],["genre",{"0":{"40":1},"1":{"41":1,"42":1,"43":1,"44":1,"45":1,"46":1,"47":1,"48":1,"49":1,"50":1,"51":1},"2":{"29":2,"30":1,"32":1,"33":1,"35":1,"38":1,"40":3,"41":12,"42":4,"43":3,"44":4,"45":1,"46":1,"47":1,"50":4,"51":1,"52":2,"54":1,"63":1}}],["genuine",{"2":{"22":1}}],["gemini",{"2":{"2":1}}],["c418",{"2":{"66":1}}],["cycle",{"2":{"35":1,"63":1}}],["cyborgs",{"2":{"2":1}}],["cross",{"2":{"113":1}}],["crystallizes",{"2":{"63":1}}],["crystallize",{"2":{"63":1}}],["crypto",{"2":{"17":1}}],["credentials",{"2":{"53":1}}],["create",{"2":{"13":1,"18":2,"64":1}}],["created",{"2":{"10":1,"13":4,"19":1,"26":1,"39":1,"66":1,"94":1,"98":1}}],["creators",{"2":{"52":1,"56":1,"94":1}}],["creator",{"2":{"11":1,"20":2,"39":2}}],["creative",{"2":{"13":1,"102":1}}],["creations",{"2":{"105":1}}],["creation",{"2":{"7":2,"91":1}}],["creating",{"2":{"4":1,"10":1,"14":1,"28":1,"102":1,"114":1}}],["crank",{"2":{"45":1}}],["critique",{"2":{"41":1}}],["criticizing",{"2":{"41":1,"62":1,"63":1}}],["criticized",{"2":{"32":2,"35":1}}],["criticisms",{"2":{"56":1,"63":1,"70":1}}],["criticism",{"0":{"56":1},"1":{"57":1,"58":1,"59":1},"2":{"32":1,"34":1,"41":1,"55":1,"56":3,"57":2}}],["celebrate",{"2":{"59":1}}],["centered",{"2":{"105":1}}],["center",{"2":{"51":1}}],["centers",{"2":{"31":1,"91":1}}],["centric",{"2":{"16":2}}],["centralized",{"2":{"15":1}}],["centralization",{"2":{"12":2}}],["central",{"2":{"12":1}}],["certain",{"2":{"10":1,"13":1,"35":1,"41":1,"48":1,"58":2,"63":1}}],["certainly",{"2":{"9":1,"10":1,"32":1,"34":1,"41":3,"42":2,"49":1,"53":1,"71":1}}],["cmd",{"2":{"9":1}}],["ctrl",{"2":{"9":1}}],["cleaning",{"2":{"87":1}}],["clearing",{"2":{"50":1}}],["clearly",{"2":{"40":1,"69":1}}],["clear",{"2":{"31":1,"35":1,"38":2,"40":1,"41":1}}],["close",{"2":{"73":1}}],["closer",{"2":{"47":1}}],["closest",{"2":{"13":1}}],["clicks",{"2":{"61":1}}],["clicking",{"2":{"35":1,"61":1,"63":1}}],["click",{"2":{"35":1,"41":2,"61":3}}],["clickers",{"0":{"41":1}}],["clicker",{"2":{"33":1,"36":1,"39":1,"41":6,"45":1,"62":1}}],["clients",{"2":{"18":1,"19":1,"20":1,"21":3,"22":3}}],["client",{"2":{"8":1,"10":1,"16":1,"17":1,"22":4}}],["claimed",{"2":{"97":1}}],["claim",{"2":{"33":1}}],["clarify",{"2":{"32":1,"60":1,"62":1}}],["classrooms",{"2":{"68":1}}],["classifying",{"2":{"53":1}}],["classic",{"2":{"41":1,"62":1}}],["class",{"2":{"5":1}}],["circumstances",{"2":{"63":1}}],["city",{"2":{"13":1}}],["citadel",{"0":{"5":1},"2":{"80":1,"81":1}}],["cinny",{"0":{"8":1},"2":{"8":1,"65":1,"76":1,"84":1}}],["c",{"2":{"4":1,"13":1}}],["cultivation",{"2":{"51":1}}],["culture",{"2":{"17":1,"32":3}}],["cutting",{"2":{"63":6}}],["cut",{"2":{"38":1}}],["cutscene",{"2":{"13":6}}],["cutscenes",{"2":{"4":2,"13":2}}],["currencies",{"2":{"78":1}}],["currency",{"0":{"90":1},"2":{"34":2,"50":1,"63":2,"64":3,"78":1,"89":1,"90":1}}],["current",{"2":{"13":3,"101":1,"107":1,"114":1}}],["currently",{"2":{"3":1,"10":1,"17":1,"114":1}}],["customers",{"2":{"41":1,"89":1}}],["custom",{"2":{"13":4}}],["customize",{"2":{"12":1,"21":1}}],["chromatic",{"0":{"120":1}}],["chronological",{"0":{"7":1,"25":1},"2":{"7":4,"14":2,"25":2,"26":2,"98":1}}],["cheap",{"2":{"102":1}}],["checked",{"2":{"13":1}}],["check",{"2":{"4":1,"13":2,"61":1}}],["china",{"2":{"51":1}}],["choices",{"2":{"68":1}}],["choosing",{"2":{"62":1}}],["choose",{"2":{"13":1,"21":3,"30":1,"92":1}}],["chores",{"2":{"63":1}}],["chore",{"2":{"62":1,"63":1}}],["chose",{"2":{"39":1,"45":1}}],["chosen",{"2":{"13":1}}],["character",{"2":{"69":1}}],["characters",{"2":{"34":1,"39":1,"51":1,"70":1}}],["chapters",{"2":{"68":1,"70":1}}],["chapter",{"2":{"67":1,"69":1,"72":1,"105":1}}],["challenges",{"2":{"56":1,"63":1}}],["challenge",{"2":{"34":1}}],["chain",{"2":{"18":1}}],["channel",{"2":{"113":1}}],["channels",{"2":{"10":1,"31":1}}],["changelog",{"2":{"52":1,"104":1}}],["change",{"2":{"37":1,"61":1,"63":1,"104":1}}],["changed",{"2":{"13":1}}],["changes",{"2":{"13":2,"28":1,"37":1,"46":1,"84":1,"86":2,"87":1}}],["changing",{"2":{"4":1}}],["chance",{"2":{"13":1}}],["chatting",{"2":{"6":1,"113":1}}],["chat",{"0":{"6":1},"2":{"6":1,"10":1}}],["chatgpt",{"2":{"2":2}}],["came",{"2":{"97":1}}],["campaign",{"2":{"13":1}}],["campaigns",{"2":{"4":1}}],["cardboardempress",{"2":{"119":1}}],["carstens",{"2":{"87":1}}],["care",{"2":{"42":1}}],["causing",{"2":{"61":1}}],["cause",{"2":{"34":1}}],["causes",{"2":{"12":1}}],["cavernous",{"2":{"50":1}}],["cash",{"2":{"89":1}}],["casino",{"2":{"41":1}}],["case",{"2":{"2":1,"13":1,"34":1,"41":1,"63":1}}],["category",{"2":{"50":1}}],["categorization",{"2":{"40":1}}],["catch",{"2":{"2":1}}],["callback",{"2":{"98":1}}],["called",{"2":{"59":1,"81":1}}],["calling",{"2":{"41":2}}],["call",{"2":{"13":1,"28":1,"38":1,"105":1}}],["captain",{"0":{"71":1}}],["capture",{"0":{"5":1},"2":{"80":1,"81":1}}],["capitalist",{"2":{"41":2}}],["capitalism",{"2":{"2":1,"39":1,"41":3}}],["canon",{"0":{"45":1},"2":{"44":4,"45":2,"46":2,"47":1}}],["can",{"2":{"2":1,"4":2,"10":2,"12":3,"13":7,"17":1,"18":9,"19":2,"20":1,"21":9,"22":1,"23":1,"30":4,"31":3,"32":1,"33":1,"34":2,"35":3,"36":1,"37":1,"38":2,"39":5,"40":3,"41":4,"43":2,"44":5,"46":2,"48":2,"49":1,"50":1,"56":3,"57":1,"58":2,"59":2,"60":1,"61":1,"62":4,"63":2,"64":2,"67":1,"77":1,"81":1,"86":1,"87":1,"92":1,"94":1,"98":1,"100":1,"102":1,"113":2}}],["cannot",{"2":{"2":1,"21":1,"22":1,"46":1}}],["cosmetics",{"2":{"89":1}}],["costs",{"2":{"64":1}}],["cost",{"2":{"62":1,"64":1,"78":1,"107":2}}],["color",{"2":{"86":2}}],["colors",{"0":{"73":1}}],["collecting",{"2":{"56":1,"58":1,"63":1,"104":1}}],["collections",{"2":{"14":2,"105":1}}],["collection",{"2":{"7":1,"23":1,"26":2,"68":1,"113":1}}],["college",{"2":{"5":1,"85":1}}],["cover",{"2":{"38":2}}],["copied",{"2":{"31":1}}],["copyright",{"2":{"2":1}}],["correlated",{"2":{"48":1}}],["correct",{"2":{"21":1}}],["core",{"2":{"41":2,"50":3,"63":5}}],["corporations",{"2":{"17":1}}],["cozy",{"0":{"95":1},"2":{"14":2,"95":1,"98":1,"112":1}}],["cocked",{"2":{"13":1}}],["cod",{"2":{"38":1}}],["coding",{"2":{"13":1,"56":1}}],["codeberg",{"2":{"100":1}}],["code",{"2":{"4":1,"9":1,"13":1,"14":1,"24":1,"30":2,"84":2,"105":1}}],["coming",{"2":{"41":1,"43":1}}],["comic",{"2":{"6":1,"71":1}}],["comfortably",{"2":{"38":1}}],["come",{"2":{"35":1,"43":1,"48":1,"57":1,"74":1}}],["comes",{"2":{"9":1,"34":1,"41":1,"63":1,"89":1,"105":1}}],["combat",{"2":{"34":2,"42":2}}],["com",{"2":{"14":3,"44":1,"70":2}}],["companies",{"2":{"89":1,"90":1}}],["company",{"2":{"89":1}}],["comparable",{"2":{"98":1}}],["comparatively",{"2":{"34":1}}],["compare",{"2":{"49":1}}],["compared",{"2":{"30":1,"34":1,"37":1}}],["comparing",{"2":{"34":1}}],["comparison",{"2":{"3":1}}],["complicatedness",{"2":{"63":1}}],["complicated",{"2":{"63":2,"102":1}}],["completing",{"2":{"67":1}}],["completeness",{"2":{"104":1}}],["completed",{"2":{"63":1}}],["complete",{"2":{"34":1,"50":1,"63":1}}],["completely",{"2":{"31":1,"32":1}}],["complexity",{"2":{"46":1}}],["complex",{"2":{"42":1,"105":1}}],["compromise",{"2":{"62":1}}],["compromised",{"2":{"18":1}}],["comprehensive",{"2":{"52":1}}],["compulsively",{"2":{"41":1}}],["computer",{"2":{"30":1,"40":1}}],["competition",{"2":{"109":1}}],["competitive",{"2":{"35":2}}],["compelled",{"2":{"57":1}}],["compelling",{"2":{"35":1}}],["compels",{"2":{"34":1}}],["component",{"2":{"13":1}}],["commercial",{"2":{"99":1}}],["comments",{"2":{"56":1,"57":3,"58":1,"59":1,"70":2,"94":1}}],["commentary",{"2":{"41":1,"94":1}}],["comment",{"2":{"39":1,"41":2,"57":1}}],["commenting",{"2":{"35":1,"39":1,"41":1}}],["commit",{"2":{"89":1}}],["communication",{"2":{"18":1}}],["communities",{"2":{"10":1,"19":1,"20":1,"31":2,"56":1,"58":2,"113":7}}],["community",{"2":{"1":1,"10":1,"14":1,"15":1,"16":1,"17":1,"20":2,"29":1,"31":2,"32":4,"43":1,"57":1,"60":1,"65":1,"68":2}}],["communal",{"2":{"10":1,"118":1}}],["commune",{"0":{"10":1,"118":1},"2":{"6":1,"10":4,"12":1,"14":1,"15":2,"17":1,"26":1,"76":1,"84":1,"92":1,"113":1,"114":2,"118":1}}],["commonly",{"2":{"50":1}}],["common",{"2":{"2":1,"10":1,"12":1,"34":1,"41":1,"42":1,"46":3,"62":1,"89":1}}],["commands",{"2":{"13":1}}],["command",{"0":{"9":1},"2":{"2":1,"9":6,"13":1,"75":1}}],["cookie",{"2":{"33":1,"36":1,"39":1,"41":1,"62":1}}],["cooked",{"2":{"2":1}}],["cooperation",{"2":{"2":1}}],["cool",{"2":{"1":1,"27":1,"59":1,"88":1}}],["connect",{"2":{"100":1}}],["conducted",{"2":{"86":1}}],["condensed",{"2":{"70":1}}],["conditions",{"2":{"36":1}}],["conditioned",{"2":{"35":1}}],["condition",{"2":{"35":1,"41":1,"61":1}}],["conform",{"2":{"63":1}}],["confidence",{"2":{"56":1}}],["configured",{"2":{"15":1}}],["conclusion",{"2":{"69":2}}],["conclude",{"2":{"49":1}}],["concerning",{"2":{"60":1}}],["concerns",{"2":{"2":1}}],["concepts",{"2":{"39":1}}],["concept",{"2":{"10":1,"39":1,"59":1}}],["congruent",{"2":{"45":1}}],["congress",{"2":{"18":1}}],["conversion",{"2":{"90":1}}],["conversation",{"2":{"38":1}}],["conversational",{"2":{"9":1}}],["conversations",{"2":{"6":1,"18":1}}],["convert",{"2":{"29":1}}],["convey",{"2":{"20":1}}],["consistently",{"2":{"100":1}}],["consider",{"2":{"33":1,"43":1,"52":1,"58":1}}],["considered",{"2":{"7":1,"15":1,"26":1,"32":1,"36":1,"41":1,"42":2,"44":1,"49":2,"61":1}}],["console",{"2":{"105":1}}],["consolidated",{"2":{"101":1}}],["consolidates",{"2":{"90":1}}],["consonant",{"2":{"86":2}}],["consumers",{"2":{"94":1}}],["consumer",{"2":{"74":1}}],["consumed",{"2":{"39":1}}],["consuming",{"2":{"63":1}}],["consecutive",{"2":{"61":1}}],["consequence",{"2":{"47":1}}],["consequences",{"2":{"42":1,"47":1,"69":2}}],["consensus",{"2":{"39":1,"43":1}}],["conservatively",{"2":{"38":1}}],["constitutes",{"2":{"61":1}}],["constructive",{"2":{"56":1,"57":3,"58":1}}],["constructed",{"2":{"13":1}}],["constrained",{"2":{"45":1}}],["constantly",{"2":{"62":1}}],["constant",{"2":{"37":1}}],["continually",{"2":{"57":1}}],["continuation",{"2":{"33":1}}],["continued",{"2":{"85":1}}],["continues",{"2":{"63":1}}],["continue",{"2":{"35":1,"39":1,"41":1,"56":1,"63":1}}],["continuing",{"2":{"35":1,"114":1}}],["contextual",{"2":{"42":1}}],["contextualize",{"2":{"33":1,"52":1,"60":1,"63":1}}],["contextualized",{"2":{"33":1}}],["contexts",{"2":{"35":1,"41":1}}],["context",{"2":{"34":1,"39":3,"41":1}}],["content",{"0":{"20":1,"60":1},"1":{"61":1,"62":1,"63":1,"64":1},"2":{"1":1,"2":2,"7":1,"13":1,"17":1,"19":1,"20":4,"21":2,"26":1,"34":1,"35":1,"46":1,"54":1,"56":1,"60":12,"61":6,"62":7,"63":13,"64":2,"96":1,"97":3,"98":1,"99":1,"110":1}}],["contain",{"2":{"41":1,"113":1}}],["contains",{"2":{"20":1,"46":1,"100":1}}],["contact",{"2":{"18":2}}],["contacts",{"2":{"18":5}}],["controversial",{"2":{"45":1,"61":2,"63":1}}],["controlling",{"2":{"13":1}}],["controlled",{"2":{"4":1}}],["control",{"2":{"11":1,"13":1,"47":1}}],["contributing",{"2":{"17":1,"118":1}}],["contributions",{"2":{"13":1}}],["contrast",{"2":{"16":1,"38":2,"69":1}}],["cough",{"2":{"74":1}}],["counter",{"2":{"61":1}}],["count",{"2":{"61":1}}],["counts",{"2":{"41":1,"60":1}}],["countless",{"2":{"30":1}}],["could",{"2":{"4":1,"13":1,"18":1,"19":1,"20":1,"22":2,"28":1,"36":1,"39":1,"40":1,"42":1,"43":1,"45":2,"46":2,"49":1,"61":2,"62":1,"105":1,"113":1,"118":1}}],["couple",{"2":{"1":1,"40":1,"53":1,"62":1,"63":1,"105":1}}],["course",{"2":{"1":1,"13":1,"35":1,"38":1,"41":1}}],["lua",{"2":{"105":2}}],["ludology",{"0":{"54":1},"2":{"53":1}}],["lucrative",{"2":{"32":1}}],["llc",{"2":{"116":1}}],["ll",{"2":{"33":2,"35":2,"38":1,"41":1,"44":1,"56":1,"57":1,"60":1,"63":4,"89":1,"104":2}}],["llms",{"2":{"2":1}}],["lyz",{"2":{"14":1}}],["levied",{"2":{"70":1}}],["levels",{"2":{"58":1,"104":1}}],["level",{"2":{"21":1,"32":1,"35":2,"41":2,"63":2,"114":1}}],["lenient",{"2":{"42":1,"44":1}}],["lend",{"2":{"35":1}}],["legitimate",{"2":{"35":1,"39":1}}],["lecture",{"2":{"35":1}}],["lets",{"2":{"63":1}}],["let",{"2":{"29":1,"38":2,"39":1,"41":1,"61":1,"63":1}}],["left",{"2":{"13":1}}],["leave",{"2":{"35":1,"58":1}}],["learning",{"2":{"30":1,"35":1,"36":2,"58":1,"69":1,"86":1,"117":1}}],["learn",{"2":{"30":2,"45":1,"50":1,"57":1,"69":1,"102":1}}],["learned",{"2":{"17":1,"69":1}}],["least",{"2":{"13":1,"22":1,"42":1,"62":1,"63":1}}],["leading",{"2":{"63":1}}],["lead",{"2":{"13":2,"61":1,"89":1}}],["lesser",{"2":{"35":1}}],["lessons",{"2":{"17":1,"69":1}}],["less",{"2":{"7":1,"34":1,"35":1,"38":1,"39":1,"48":1,"62":1,"89":1}}],["lgbt",{"2":{"10":1}}],["located",{"2":{"86":1}}],["locations",{"2":{"13":1}}],["location",{"2":{"13":2}}],["logic",{"2":{"41":1,"62":1}}],["logseq",{"0":{"75":1},"2":{"9":1,"75":1,"84":1,"104":1}}],["love",{"2":{"40":1,"41":1,"60":1,"102":1}}],["lore",{"2":{"39":1}}],["loosely",{"2":{"63":1,"91":1}}],["loops",{"2":{"50":2}}],["loop",{"2":{"37":2,"50":2,"63":1}}],["look",{"2":{"35":1,"57":1,"61":1,"91":1,"100":1,"114":1,"118":1}}],["looking",{"2":{"21":1,"31":1,"38":1,"41":1,"62":1}}],["looks",{"2":{"9":1,"13":1,"22":1}}],["lowers",{"2":{"35":1}}],["low",{"0":{"48":1},"2":{"30":2,"31":1,"34":1,"38":1,"47":1,"48":2,"60":2}}],["load",{"2":{"19":1}}],["lost",{"2":{"62":1}}],["losing",{"2":{"18":1,"47":1}}],["loss",{"2":{"13":1}}],["lots",{"2":{"109":1}}],["lot",{"2":{"17":1,"29":2,"31":1,"32":1,"33":2,"34":3,"35":3,"39":2,"42":1,"43":1,"45":1,"47":1,"50":1,"53":1,"56":3,"68":1,"69":1,"95":1,"102":1,"105":1,"107":1,"117":1}}],["longer",{"2":{"37":1,"46":1,"48":1,"60":1,"63":2}}],["long",{"2":{"13":1,"35":1,"41":1,"44":1,"47":1,"60":1,"62":1,"67":1,"81":1,"114":1,"121":2}}],["laid",{"2":{"114":1}}],["launch",{"2":{"89":1}}],["laura",{"2":{"68":1}}],["labs",{"2":{"116":1}}],["lab",{"2":{"87":1}}],["label",{"2":{"39":1}}],["last",{"2":{"69":1,"70":1}}],["lashing",{"2":{"59":1}}],["lack",{"2":{"39":3,"60":1}}],["layer",{"2":{"50":1,"62":1,"63":2,"88":1}}],["layers",{"2":{"41":1,"43":1,"63":2,"114":1}}],["lay",{"2":{"30":1}}],["lattice",{"0":{"120":1}}],["latter",{"2":{"13":1,"35":1,"41":1,"57":1}}],["later",{"2":{"11":1,"35":1,"63":1,"68":1,"72":1}}],["laxla",{"2":{"10":1}}],["lawn",{"2":{"5":1}}],["languages",{"2":{"30":1}}],["language",{"2":{"2":1,"30":1,"86":1}}],["larger",{"2":{"48":1,"62":1,"90":1}}],["largest",{"2":{"47":1,"56":1,"67":1}}],["large",{"2":{"1":1,"2":1,"3":1,"9":1,"12":1,"17":3,"32":1,"41":1,"42":1,"46":2,"64":1,"113":1}}],["libraries",{"2":{"113":1}}],["library",{"2":{"13":1}}],["limited",{"2":{"105":1}}],["limitations",{"2":{"92":1}}],["limits",{"2":{"39":1}}],["license",{"2":{"84":1}}],["live",{"2":{"69":1}}],["living",{"2":{"13":1,"26":1,"52":1,"69":1,"109":1,"116":1}}],["lis2",{"2":{"71":1,"72":1}}],["lis1",{"2":{"68":1,"70":1,"72":1,"74":1}}],["lis",{"2":{"68":1,"70":1}}],["list",{"2":{"13":4,"44":3,"45":2,"46":1,"61":1}}],["little",{"2":{"63":1,"73":1}}],["literally",{"2":{"34":1}}],["links",{"2":{"99":1}}],["linking",{"2":{"38":1}}],["link",{"2":{"31":1,"98":1,"113":1}}],["linked",{"2":{"22":1,"114":1}}],["line",{"2":{"42":2}}],["lines",{"2":{"30":1}}],["linearly",{"2":{"63":1}}],["linear",{"2":{"6":1,"9":1,"63":3}}],["lighten",{"2":{"19":1}}],["likes",{"2":{"35":1,"38":1,"43":1}}],["liked",{"2":{"33":1}}],["likely",{"2":{"22":3,"58":1,"63":1,"89":1}}],["like",{"2":{"2":3,"4":1,"10":1,"13":4,"19":1,"32":5,"33":1,"34":3,"35":5,"36":2,"38":3,"39":6,"40":1,"41":4,"50":1,"59":1,"60":1,"62":1,"63":2,"64":1,"71":1,"73":1,"80":1,"92":1,"100":1,"104":1,"114":1,"118":1}}],["lifeisstrange",{"2":{"70":2}}],["life",{"0":{"68":1,"70":1,"72":1,"73":1,"74":1,"116":1},"1":{"69":1,"70":1,"71":1,"72":1,"73":1,"74":1},"2":{"1":2,"35":1,"41":2,"50":1,"68":1,"69":1,"78":1,"106":1,"115":1}}],["utilize",{"2":{"108":1}}],["ut",{"2":{"87":1}}],["ue",{"2":{"71":1}}],["ui",{"2":{"47":2}}],["umbrella",{"2":{"41":1,"42":1,"50":1}}],["ultimately",{"2":{"38":1,"41":2,"45":1,"56":1,"57":1,"60":1}}],["url",{"2":{"20":1}}],["us",{"2":{"45":1,"59":1}}],["usually",{"2":{"43":1}}],["using",{"2":{"13":3,"20":1,"30":1,"31":1,"33":1,"38":1,"41":1,"42":1,"62":1,"91":1,"97":1,"105":1}}],["usenet",{"2":{"17":1}}],["username",{"2":{"18":1}}],["users",{"2":{"17":1,"19":1,"21":2,"36":1,"84":1,"92":1}}],["user",{"2":{"17":1,"22":1,"114":1,"118":1}}],["uses",{"2":{"13":1,"15":1,"35":1,"41":1}}],["useful",{"2":{"13":1,"19":1,"28":1,"41":2,"57":1,"59":1,"62":1,"90":1,"99":1}}],["use",{"2":{"4":1,"9":2,"13":3,"20":1,"30":2,"41":4,"42":1,"57":1,"62":1,"90":1,"100":2,"102":1,"107":1}}],["used",{"2":{"3":1,"4":2,"13":2,"18":1,"41":2,"42":2,"43":1,"44":2,"50":2,"57":1,"62":1,"64":1}}],["unmanageable",{"2":{"63":1}}],["unhelpful",{"2":{"57":2}}],["unfortunate",{"2":{"63":1}}],["unfortunately",{"2":{"35":1,"72":1}}],["unfolding",{"2":{"46":1}}],["unrelated",{"2":{"43":1}}],["unknown",{"2":{"31":1}}],["unlocks",{"2":{"64":3}}],["unlock",{"2":{"48":1,"63":1,"64":1}}],["unlocking",{"2":{"34":1,"63":1}}],["unlocked",{"2":{"1":1,"63":1}}],["unlike",{"2":{"30":1,"41":1,"63":1}}],["unlikely",{"2":{"22":2}}],["unless",{"2":{"21":1,"41":1}}],["until",{"2":{"13":1,"62":1,"104":1}}],["unit",{"2":{"87":1}}],["units",{"2":{"62":1}}],["unity",{"2":{"13":1,"87":1}}],["universal",{"2":{"45":1,"46":1}}],["universally",{"2":{"41":1}}],["university",{"2":{"11":1}}],["uniquely",{"2":{"30":1,"42":1}}],["unique",{"2":{"19":1,"69":1}}],["undefined",{"2":{"94":1}}],["underlying",{"2":{"38":1}}],["understanding",{"2":{"60":1,"61":1}}],["understand",{"2":{"13":1,"41":1,"42":1,"58":1,"60":1,"61":1,"62":1}}],["under",{"2":{"2":1,"13":1,"36":1,"41":1,"42":2,"50":1,"69":1}}],["undressing",{"2":{"41":1}}],["undoing",{"2":{"13":1}}],["upgrade",{"2":{"50":1,"62":1,"64":4}}],["upgrades",{"2":{"40":1,"50":3,"63":6}}],["upon",{"2":{"39":1,"41":1,"57":1,"63":1}}],["uploaded",{"2":{"31":1}}],["updating",{"2":{"20":1,"87":1}}],["updates",{"2":{"13":1,"104":1}}],["upvotes",{"2":{"20":1,"22":1}}],["upset",{"2":{"37":1}}],["upsides",{"2":{"17":1}}],["ups",{"2":{"10":1,"59":1}}],["up",{"0":{"34":1},"2":{"1":1,"13":4,"30":1,"34":1,"38":1,"40":2,"41":1,"42":5,"45":2,"46":2,"47":2,"61":2,"62":1,"63":1,"67":1,"74":1,"87":1,"100":1,"113":1}}],["errant",{"2":{"94":1}}],["errors",{"2":{"86":1}}],["erlend",{"2":{"10":1,"114":1}}],["e3",{"2":{"70":1}}],["eyes",{"2":{"70":1}}],["ecs",{"0":{"105":1},"2":{"67":1,"80":1,"82":1,"105":2}}],["ecosystem",{"2":{"12":1}}],["egregious",{"2":{"62":1}}],["episode",{"2":{"70":1}}],["ep",{"2":{"62":5}}],["equal",{"2":{"57":1}}],["equipped",{"2":{"13":2}}],["equipping",{"2":{"13":1}}],["education",{"2":{"53":1}}],["editions",{"2":{"74":1,"89":1,"107":1}}],["edited",{"2":{"20":1,"26":1}}],["edits",{"2":{"20":1,"21":1}}],["editor",{"2":{"13":5}}],["edit",{"2":{"7":2,"13":2,"21":2}}],["elements",{"2":{"47":1}}],["elicited",{"2":{"39":1}}],["else",{"2":{"10":1,"41":1,"42":1,"97":1}}],["evidence",{"2":{"41":1}}],["evolutions",{"2":{"36":1}}],["event",{"2":{"69":1}}],["events",{"2":{"13":1}}],["eventually",{"2":{"9":1,"41":1,"56":1,"62":1,"63":1,"105":1}}],["even",{"2":{"7":1,"13":1,"19":1,"21":1,"22":1,"30":1,"32":1,"35":3,"38":1,"39":3,"40":1,"41":3,"43":1,"57":1,"63":2,"102":1}}],["ever",{"2":{"4":1,"22":1,"41":2,"42":1,"67":1}}],["everything",{"2":{"13":2,"32":1,"33":1,"52":1,"63":1,"91":1}}],["everyone",{"2":{"12":2,"57":1,"63":1,"74":1,"92":1,"114":1}}],["every",{"2":{"1":1,"17":1,"22":1,"35":2,"40":1,"46":3,"57":1,"61":1,"62":2,"104":3}}],["effortless",{"2":{"35":1}}],["effortlessness",{"0":{"35":1}}],["effects",{"2":{"38":1,"61":1,"63":5,"64":2}}],["effectively",{"2":{"20":2,"21":1,"38":2,"62":1,"63":1,"64":1}}],["effect",{"2":{"13":2,"34":1,"63":2,"90":1}}],["established",{"2":{"46":1}}],["essential",{"2":{"56":1}}],["essentially",{"2":{"19":1,"38":1,"63":1,"104":1}}],["essay",{"2":{"38":1}}],["especially",{"2":{"9":1,"104":1}}],["either",{"2":{"13":1,"35":1,"48":1,"53":1,"61":1,"63":1}}],["earn",{"2":{"50":1,"107":1}}],["earned",{"2":{"34":1}}],["early",{"2":{"45":1,"62":1}}],["earlier",{"2":{"35":1,"38":1,"43":1,"47":1,"48":1,"74":1}}],["ease",{"2":{"35":1,"39":1}}],["easy",{"0":{"30":1,"31":1},"2":{"13":1,"30":1,"31":1,"35":2,"42":1,"63":1,"102":1}}],["easily",{"2":{"13":1,"38":1,"45":1,"46":1,"87":1,"102":1,"105":1}}],["easier",{"2":{"9":1,"13":1,"36":3,"41":1,"63":1}}],["each",{"2":{"13":5,"20":1,"23":1,"31":1,"46":3,"47":1,"61":2,"62":3,"63":1,"98":1,"100":1,"105":2,"113":2}}],["embargo",{"2":{"89":1}}],["embrace",{"2":{"56":1}}],["ema",{"2":{"87":1}}],["emails",{"2":{"118":1}}],["email",{"2":{"12":2}}],["empathy",{"2":{"73":1}}],["empty",{"2":{"41":2}}],["emphasizes",{"2":{"34":1}}],["employee",{"2":{"10":1}}],["emotional",{"2":{"58":1,"68":1}}],["emotionally",{"2":{"41":1,"57":1}}],["emotion",{"2":{"13":1}}],["eternity",{"2":{"62":2}}],["etc",{"2":{"10":1,"19":1,"21":1,"22":1,"30":1,"34":1,"39":1,"53":1,"56":1,"89":1,"92":2,"118":1}}],["ethical",{"0":{"110":1},"2":{"2":2}}],["ensure",{"2":{"56":1,"92":1,"97":1}}],["ensuring",{"2":{"38":1}}],["encourage",{"2":{"39":1,"56":1}}],["encourages",{"2":{"38":1}}],["encouraging",{"2":{"38":2}}],["english",{"2":{"51":1,"86":1}}],["engage",{"2":{"60":1,"61":2}}],["engaged",{"2":{"37":1,"68":1}}],["engaging",{"2":{"39":1,"61":1,"62":1,"63":1}}],["engine",{"2":{"4":1,"13":1,"30":1,"91":1,"99":1,"105":4}}],["enemies",{"2":{"36":1}}],["enjoyed",{"2":{"68":2,"70":2,"71":1}}],["enjoying",{"2":{"35":1}}],["enjoyable",{"2":{"34":2,"38":1,"63":1}}],["enjoy",{"2":{"34":1,"35":1,"38":1,"58":1}}],["entries",{"2":{"91":1}}],["entry",{"2":{"31":1,"35":1}}],["enthusiastically",{"2":{"56":1}}],["entertain",{"2":{"46":1}}],["entities",{"2":{"47":1}}],["entity",{"2":{"12":1,"19":1,"62":1}}],["entirely",{"2":{"20":1}}],["entire",{"2":{"13":1,"35":1,"39":1,"62":1,"69":1,"70":1}}],["enough",{"2":{"15":1,"44":1,"49":2,"62":1,"63":1,"105":1}}],["envisioning",{"2":{"5":1}}],["endorsing",{"2":{"113":1}}],["endorses",{"2":{"15":1}}],["endings",{"2":{"69":1,"74":1}}],["ending",{"0":{"69":1},"2":{"69":3,"70":1}}],["ends",{"2":{"13":1}}],["end",{"2":{"1":1,"13":2,"42":1,"44":1,"52":1,"61":1,"69":2,"100":1}}],["ended",{"2":{"1":1,"38":1}}],["e",{"2":{"2":1,"18":1,"86":1,"113":1}}],["excited",{"2":{"74":1}}],["exciting",{"2":{"56":1}}],["exclusive",{"2":{"47":1,"89":1}}],["exception",{"2":{"81":1}}],["exceptions",{"2":{"32":1}}],["except",{"2":{"63":1}}],["excess",{"2":{"39":1}}],["exhibit",{"2":{"46":1}}],["extreme",{"2":{"39":1,"61":1}}],["extremely",{"2":{"38":1}}],["extrinsic",{"2":{"35":1,"48":1}}],["extensive",{"2":{"102":1}}],["extensions",{"2":{"28":1}}],["extension",{"2":{"21":1,"95":1}}],["extent",{"2":{"33":1,"35":2}}],["exaggerated",{"2":{"42":2}}],["exaggerating",{"2":{"34":1}}],["example",{"2":{"38":3,"46":1,"61":1,"62":1,"63":1,"64":1}}],["examples",{"2":{"2":1,"12":1,"38":2,"46":2,"50":4,"52":2}}],["exacerbate",{"2":{"35":1,"41":1}}],["expansions",{"2":{"110":1}}],["expanding",{"2":{"42":1}}],["exposure",{"0":{"74":1}}],["exposes",{"2":{"10":1}}],["expose",{"2":{"9":1}}],["exponentially",{"2":{"62":1}}],["expression",{"2":{"39":1}}],["expertise",{"2":{"104":1}}],["experiencing",{"2":{"57":1}}],["experiences",{"2":{"38":1}}],["experience",{"2":{"12":2,"33":1,"35":2,"38":4,"41":3,"58":1,"60":1,"61":1,"74":1}}],["expensive",{"2":{"102":1,"107":1}}],["expecting",{"2":{"35":1,"49":1}}],["expected",{"2":{"32":1}}],["expect",{"2":{"31":1,"34":1,"35":1,"63":1}}],["expectations",{"2":{"30":1,"40":1}}],["explains",{"2":{"59":1}}],["explained",{"2":{"32":1}}],["explanation",{"2":{"43":1}}],["exploring",{"2":{"34":1,"39":1}}],["explore",{"2":{"29":1,"52":1,"56":1,"60":1}}],["exploiting",{"2":{"32":1}}],["explicitly",{"2":{"15":1,"44":1,"65":1,"99":1}}],["ex",{"2":{"10":1}}],["exists",{"2":{"104":1}}],["exist",{"2":{"2":1,"14":1,"40":1,"114":1}}],["existing",{"2":{"2":1,"13":1,"17":1,"19":1,"28":1,"46":1}}],["www",{"2":{"70":2}}],["wonderful",{"2":{"56":2}}],["won",{"2":{"15":1,"38":1,"47":1,"63":2,"98":1}}],["wouldn",{"2":{"18":1}}],["would",{"2":{"13":1,"18":1,"19":1,"20":1,"33":1,"38":1,"40":2,"42":2,"43":1,"46":1,"47":1,"49":4,"50":2,"57":1,"61":1,"62":4,"68":1,"71":1,"73":1,"107":2,"113":3,"114":1}}],["words",{"2":{"41":1}}],["worlds",{"2":{"105":5}}],["world",{"2":{"35":1,"51":1,"90":1,"105":3}}],["worth",{"2":{"33":1,"39":1}}],["worry",{"2":{"30":1}}],["worrying",{"2":{"13":1}}],["worse",{"2":{"12":1,"61":1,"74":1}}],["working",{"2":{"35":1,"61":1,"117":2,"118":1,"120":1,"121":1}}],["workshop",{"2":{"105":1}}],["works",{"2":{"13":1,"57":1,"105":1}}],["work",{"0":{"87":1},"2":{"7":1,"19":2,"28":2,"35":1,"48":1,"57":1,"86":1,"105":1,"116":1}}],["wrt",{"2":{"46":1}}],["wrong",{"2":{"41":1,"42":1,"60":1}}],["wrote",{"2":{"13":2}}],["writing",{"2":{"104":1}}],["written",{"2":{"39":1,"52":1,"95":2,"104":1}}],["writer",{"2":{"13":1}}],["write",{"2":{"10":1,"18":1,"96":1}}],["wreden",{"0":{"11":1},"2":{"11":2,"66":3,"94":3,"112":1}}],["wife",{"2":{"116":1}}],["wise",{"2":{"62":1}}],["wishes",{"2":{"21":1}}],["wizard",{"2":{"50":1}}],["wikipedia",{"2":{"104":1}}],["wikis",{"2":{"98":1}}],["wiki",{"2":{"26":1}}],["winning",{"2":{"13":3}}],["win",{"2":{"13":2,"34":1}}],["will",{"2":{"9":1,"10":2,"13":6,"20":1,"22":2,"32":2,"34":1,"35":1,"38":1,"40":2,"41":1,"42":1,"43":1,"46":1,"48":1,"52":2,"56":1,"57":1,"58":2,"59":2,"62":1,"63":4,"64":1,"67":1,"70":1,"74":2,"89":1}}],["within",{"2":{"16":1,"20":2,"33":1,"36":1,"38":1,"39":2,"41":2,"44":2,"47":2,"50":1,"57":1}}],["without",{"2":{"13":1,"15":1,"21":1,"33":1,"34":3,"35":1,"39":2,"74":1,"107":1}}],["with",{"2":{"1":1,"4":1,"6":1,"7":2,"9":2,"10":2,"11":1,"12":1,"13":6,"15":1,"17":3,"18":3,"19":1,"20":4,"21":4,"22":1,"28":1,"31":3,"32":1,"33":2,"35":3,"37":1,"38":2,"39":3,"40":2,"41":6,"43":3,"44":1,"45":1,"46":5,"47":1,"48":4,"51":1,"56":3,"57":1,"59":2,"60":2,"61":2,"62":1,"63":5,"64":1,"68":2,"69":4,"70":1,"72":2,"74":1,"84":1,"86":3,"89":1,"91":3,"92":2,"97":1,"99":1,"100":1,"104":2,"105":3,"109":1,"113":1,"114":1,"116":1,"118":2,"119":1}}],["whole",{"2":{"41":2,"98":1}}],["whom",{"2":{"38":1}}],["who",{"2":{"30":1,"34":1,"35":2,"38":1,"39":1,"41":1,"60":2,"61":1,"63":1,"74":1,"89":2,"95":1,"113":1}}],["why",{"0":{"53":1,"102":1},"2":{"28":1,"29":1,"33":1,"34":1,"35":2,"39":3,"41":2,"42":1,"52":1,"56":1,"63":5}}],["whitelisted",{"2":{"21":1}}],["white",{"2":{"18":1}}],["while",{"2":{"13":1,"33":1,"34":2,"35":4,"38":2,"41":3,"42":2,"46":2,"51":1,"56":1,"57":1,"62":2,"86":1,"118":1}}],["which",{"2":{"13":5,"15":2,"28":1,"31":2,"33":2,"34":1,"37":1,"38":3,"39":2,"44":1,"47":1,"50":1,"62":1,"63":3,"64":1,"70":1,"98":1,"104":1,"105":1,"114":1}}],["whether",{"2":{"35":1,"39":2,"42":1,"49":1}}],["wheel",{"2":{"13":1}}],["whenever",{"2":{"62":1}}],["when",{"2":{"13":4,"19":2,"26":1,"35":1,"38":1,"39":1,"41":2,"42":2,"46":1,"56":1,"58":1,"62":1,"63":4,"64":1,"86":2}}],["whereas",{"2":{"30":1}}],["where",{"2":{"9":1,"19":1,"34":2,"36":2,"37":1,"38":1,"41":1,"42":1,"43":1,"47":1,"48":1,"50":1,"58":1,"61":1,"63":4,"90":1,"113":1,"116":1}}],["whatever",{"2":{"13":1,"22":1,"57":1}}],["what",{"0":{"60":1},"1":{"61":1,"62":1,"63":1,"64":1},"2":{"2":1,"9":1,"13":3,"33":3,"34":2,"36":2,"38":1,"39":3,"40":3,"41":2,"42":2,"43":4,"44":2,"45":1,"46":2,"47":1,"53":1,"54":1,"57":1,"60":3,"61":1,"62":2,"63":2,"70":1,"74":1,"115":2,"118":1}}],["were",{"2":{"105":1}}],["we",{"2":{"40":1,"42":2,"43":1,"46":1,"49":1,"56":1,"60":2,"63":5,"68":1,"72":1,"104":1}}],["weapons",{"2":{"34":1}}],["went",{"2":{"33":1}}],["welcoming",{"2":{"56":1}}],["welcome",{"2":{"31":1}}],["well",{"2":{"7":1,"9":1,"10":2,"20":1,"31":2,"36":1,"38":1,"40":1,"44":1,"53":1,"62":1,"71":1,"89":1,"104":1,"105":1}}],["weird",{"0":{"114":1},"2":{"10":2,"15":1,"16":2,"23":1,"84":1,"100":1,"114":3}}],["webs",{"2":{"97":1,"101":1}}],["websites",{"0":{"100":1},"1":{"101":1},"2":{"23":1,"28":1,"50":1,"79":1,"98":1,"99":1,"100":1,"102":5,"113":2,"114":1}}],["website",{"0":{"79":1},"2":{"4":1,"18":1,"65":1,"96":1,"98":1,"117":1}}],["webrings",{"0":{"113":1},"2":{"10":1,"65":1,"98":1,"99":1,"113":1}}],["web",{"0":{"95":1,"98":1,"99":1,"102":1,"103":1},"1":{"99":1,"100":1,"101":1,"102":1,"103":1},"2":{"6":1,"7":1,"8":1,"10":4,"14":3,"26":1,"28":1,"30":3,"32":3,"63":3,"64":1,"79":1,"91":1,"95":5,"98":3,"99":1,"100":1,"101":2,"104":1,"113":1,"114":1,"117":1}}],["wave",{"2":{"86":2}}],["walking",{"2":{"39":1}}],["wait",{"2":{"38":1,"48":1,"64":1}}],["waiting",{"2":{"35":1,"48":1,"61":2}}],["watching",{"2":{"90":1}}],["watch",{"2":{"33":1,"35":1}}],["watched",{"2":{"33":1}}],["ware",{"2":{"32":1}}],["wanderstop",{"0":{"112":1},"2":{"11":1,"66":1,"112":1}}],["wanted",{"2":{"38":1,"72":1}}],["wants",{"2":{"10":1,"19":1,"63":1,"114":1}}],["want",{"0":{"102":1},"2":{"9":1,"10":1,"18":2,"52":1,"60":4,"61":1,"62":1,"96":1}}],["ways",{"2":{"10":1,"19":1,"62":1,"74":1,"98":1}}],["way",{"2":{"1":1,"19":1,"21":1,"33":1,"34":1,"35":2,"37":1,"38":1,"40":1,"41":2,"42":1,"44":1,"52":1,"56":1,"91":1,"98":1}}],["wasted",{"2":{"39":1}}],["waste",{"2":{"39":1}}],["was",{"2":{"1":1,"4":1,"13":2,"18":1,"20":1,"22":1,"26":1,"27":1,"41":1,"49":1,"52":1,"63":1,"69":2,"74":1,"97":1,"98":1,"102":1,"105":1}}],["bts",{"2":{"70":1}}],["bonuses",{"0":{"89":1},"2":{"89":3,"90":1,"107":1}}],["bought",{"2":{"62":1}}],["books",{"2":{"51":1}}],["borrow",{"2":{"43":1}}],["borders",{"2":{"41":1}}],["boils",{"2":{"38":1}}],["boxes",{"2":{"35":1,"41":2}}],["box",{"2":{"35":1,"41":2}}],["bother",{"2":{"63":1}}],["both",{"2":{"31":1,"41":2,"63":1,"77":1}}],["bots",{"2":{"22":1}}],["bot",{"2":{"22":2}}],["bias",{"2":{"46":1,"59":1}}],["biasing",{"2":{"45":1}}],["biased",{"2":{"40":1,"104":1}}],["bill",{"2":{"43":1}}],["biggest",{"2":{"74":1}}],["big",{"2":{"34":2,"38":1,"42":3,"60":1,"115":1}}],["bit",{"2":{"20":1,"35":1,"38":3,"39":1,"42":2,"60":1,"63":1}}],["binary",{"2":{"20":1}}],["bridge",{"2":{"113":1}}],["bring",{"2":{"38":1}}],["breached",{"2":{"18":2}}],["browsing",{"0":{"99":1}}],["browser",{"2":{"30":2,"31":1}}],["brought",{"2":{"47":1}}],["broadly",{"2":{"94":1}}],["broad",{"2":{"17":1,"42":1}}],["broken",{"2":{"13":1}}],["brain",{"2":{"14":1}}],["branching",{"2":{"6":1}}],["blame",{"2":{"109":1}}],["blocks",{"0":{"96":1},"2":{"97":1,"100":1,"117":2}}],["blogs",{"2":{"14":1}}],["blogging",{"2":{"10":1}}],["blog",{"2":{"10":2,"44":1}}],["blends",{"2":{"61":1}}],["blurriness",{"2":{"44":1}}],["blurred",{"2":{"42":1}}],["blurry",{"2":{"41":1}}],["bluesky",{"2":{"3":1}}],["baby",{"2":{"116":1}}],["babble",{"0":{"4":1},"2":{"4":2,"13":4,"80":1,"82":1}}],["balancing",{"2":{"52":1,"56":1}}],["balance",{"2":{"13":2}}],["battles",{"2":{"50":1}}],["badgood",{"2":{"41":1}}],["bad",{"2":{"17":1,"38":6,"41":4,"58":1,"63":1}}],["back",{"2":{"13":1,"35":1,"38":1,"39":1,"41":1,"43":1,"59":1,"70":1,"101":1,"102":1,"107":1}}],["basically",{"2":{"104":1}}],["basics",{"2":{"13":1}}],["baseline",{"2":{"60":1}}],["bases",{"2":{"43":1}}],["base",{"2":{"34":1,"50":1,"63":1,"107":1,"110":1}}],["based",{"2":{"10":1,"13":1,"18":1,"32":1,"39":1,"44":2,"50":1,"63":3,"64":1,"90":1,"91":1,"104":1,"105":1,"118":1}}],["barrier",{"2":{"31":1,"35":1}}],["bars",{"2":{"9":1}}],["bar",{"2":{"9":1,"70":1,"94":1}}],["barbee",{"2":{"5":1}}],["barefoot",{"2":{"2":1}}],["bunch",{"2":{"113":1}}],["bulk",{"2":{"90":1}}],["bursts",{"2":{"61":1}}],["buffed",{"2":{"46":1}}],["buying",{"2":{"41":1,"50":1,"62":2,"63":1,"89":1}}],["buy",{"2":{"13":3,"50":1,"62":3,"63":3,"89":1}}],["built",{"2":{"10":2,"35":1,"67":1,"85":1,"113":1,"114":1}}],["builds",{"2":{"46":1}}],["builders",{"2":{"42":3,"100":1}}],["buildings",{"2":{"62":1}}],["building",{"0":{"100":1},"1":{"101":1},"2":{"10":1,"63":1,"100":1,"117":1}}],["build",{"2":{"2":1,"13":1,"28":1,"52":1,"63":1,"114":1}}],["buds",{"0":{"4":1},"2":{"4":1,"13":4,"80":1,"82":1}}],["button",{"2":{"13":2,"30":2,"34":1,"35":1,"62":1,"99":1,"105":1}}],["buttons",{"2":{"13":2,"35":1}}],["but",{"2":{"1":1,"4":1,"13":2,"21":1,"22":1,"32":2,"34":4,"35":4,"38":2,"39":2,"40":2,"41":8,"42":3,"43":4,"44":2,"45":2,"46":2,"47":1,"53":1,"59":1,"60":2,"61":4,"62":2,"63":5,"69":1,"70":1,"72":1,"73":1,"74":1,"81":1,"102":2,"104":1,"105":1}}],["benefit",{"2":{"89":1}}],["benefits",{"2":{"89":1}}],["begs",{"2":{"63":1}}],["beginners",{"2":{"30":1}}],["beginner",{"0":{"94":1},"2":{"11":3,"94":2}}],["berlin",{"0":{"44":1},"2":{"44":2,"49":3}}],["belong",{"2":{"41":1,"50":1,"92":1}}],["believe",{"2":{"4":1,"34":1,"41":1,"42":1,"43":1,"44":1,"57":1,"61":1,"62":1}}],["beyond",{"2":{"39":1,"50":1,"61":1,"62":2}}],["behavior",{"2":{"41":1}}],["behave",{"2":{"38":1,"91":1}}],["behind",{"2":{"38":2}}],["beats",{"2":{"74":1}}],["beating",{"2":{"34":1}}],["beat",{"2":{"34":2}}],["been",{"2":{"32":1,"33":3,"39":1,"42":1,"45":1,"58":1,"60":1,"62":2,"71":1,"86":1,"117":2}}],["best",{"2":{"14":1,"33":1,"36":1,"42":1,"45":1,"53":1,"57":1,"59":1,"97":1,"104":1}}],["between",{"2":{"13":1,"14":1,"22":1,"25":1,"34":1,"35":1,"36":1,"42":4,"43":1,"47":1,"57":1,"61":2,"62":2,"94":1,"98":1}}],["better",{"2":{"10":1,"26":1,"28":1,"38":1,"41":2,"56":1,"57":1,"69":1,"114":1}}],["becoming",{"2":{"56":1,"63":1}}],["becomes",{"2":{"35":1,"63":3}}],["become",{"2":{"9":1,"13":1,"41":1,"46":1,"50":1,"61":1,"62":2,"63":3}}],["became",{"2":{"13":1,"68":1,"105":1}}],["because",{"2":{"4":1,"13":1,"35":2,"39":1,"40":1,"42":1,"43":1,"56":1,"61":1,"63":1}}],["be",{"2":{"4":1,"10":2,"13":5,"15":1,"17":2,"18":1,"20":2,"21":1,"22":8,"31":3,"32":2,"33":3,"34":3,"35":6,"36":2,"38":2,"39":5,"40":3,"41":9,"42":4,"43":4,"44":10,"45":2,"46":2,"47":2,"48":1,"49":4,"50":1,"52":1,"53":1,"56":1,"57":4,"60":1,"61":6,"62":3,"63":8,"64":1,"67":2,"74":1,"86":1,"97":1,"98":1,"102":1,"107":1,"113":3}}],["being",{"2":{"1":1,"17":2,"32":3,"35":2,"36":2,"38":1,"42":1,"43":1,"48":1,"50":1,"51":1,"70":1,"114":1}}],["before",{"0":{"70":1},"2":{"1":1,"39":1,"41":1,"46":2,"48":1,"52":1,"58":1,"62":1,"63":2,"64":1,"89":2,"92":1,"98":1}}],["by",{"2":{"0":1,"1":1,"2":3,"3":2,"4":3,"5":1,"6":2,"7":1,"8":1,"10":3,"11":2,"12":2,"13":4,"14":2,"15":3,"16":1,"17":3,"20":1,"21":3,"22":1,"23":2,"24":1,"25":1,"26":1,"28":1,"32":1,"33":2,"34":5,"35":1,"38":3,"40":2,"41":1,"42":2,"44":4,"45":1,"48":1,"50":3,"57":1,"63":2,"64":2,"65":2,"66":2,"67":1,"68":1,"75":1,"76":1,"77":1,"78":1,"79":1,"80":1,"83":1,"84":1,"89":1,"90":1,"91":4,"92":2,"93":1,"94":1,"95":3,"98":2,"104":1,"105":2,"106":1,"111":1,"112":1,"113":1,"114":2,"117":1}}],["dfw",{"2":{"116":1}}],["dynamic",{"2":{"88":1}}],["dynamically",{"2":{"13":3}}],["ddr",{"2":{"35":1}}],["d",{"2":{"22":2,"32":1,"33":1,"34":2,"35":1,"39":2,"40":1,"41":3,"43":1,"45":1,"50":1,"60":1,"61":1,"63":1,"64":1,"68":1,"86":1,"102":1}}],["dressing",{"2":{"41":1}}],["drops",{"2":{"38":1}}],["dropdown",{"2":{"13":1}}],["driven",{"2":{"68":1,"74":2,"121":1}}],["drive",{"2":{"22":1,"39":1,"89":1}}],["drawing",{"2":{"33":1}}],["draw",{"2":{"29":1}}],["dramatic",{"2":{"13":1}}],["dragging",{"2":{"13":1}}],["drag",{"2":{"13":1}}],["due",{"2":{"32":2,"33":1,"38":1,"39":1,"42":1,"43":1,"46":1,"57":1,"70":1,"107":1}}],["duels",{"2":{"13":3}}],["dueling",{"2":{"13":3}}],["duel",{"2":{"13":4}}],["duty",{"2":{"21":1,"38":1}}],["during",{"2":{"13":2}}],["dodger",{"2":{"68":1}}],["documentation",{"2":{"87":1}}],["document",{"2":{"52":2}}],["documents",{"2":{"26":1,"114":1}}],["dopamine",{"2":{"41":2}}],["doom",{"2":{"38":3}}],["double",{"0":{"74":1},"2":{"21":1}}],["doesn",{"2":{"17":1,"22":1,"36":1,"40":1,"41":1,"42":1,"46":1,"62":1,"63":1,"74":1}}],["does",{"2":{"15":1,"34":2,"38":4,"42":1,"43":1,"46":1,"47":1,"61":1,"62":1,"63":1,"73":1}}],["downs",{"2":{"59":1}}],["downvotes",{"2":{"20":1,"22":1}}],["down",{"2":{"13":1,"33":2,"38":1}}],["downloading",{"2":{"22":1}}],["downloaded",{"2":{"22":1}}],["download",{"2":{"13":1,"22":1}}],["do",{"2":{"13":1,"18":1,"22":1,"31":1,"33":1,"34":1,"41":3,"42":1,"43":1,"53":2,"56":1,"57":1,"61":2,"62":2,"63":4,"64":1,"72":1,"74":1,"92":1,"104":1}}],["doing",{"2":{"13":1,"35":2}}],["donation",{"2":{"32":1}}],["done",{"2":{"22":1}}],["don",{"2":{"4":1,"17":2,"22":1,"27":1,"30":3,"34":1,"38":1,"40":1,"41":1,"42":1,"43":1,"52":1,"57":2,"62":1,"63":2,"64":1,"109":1}}],["diminishing",{"2":{"62":1}}],["dimensions",{"2":{"50":1,"62":9}}],["diverse",{"2":{"58":1,"98":1}}],["diversity",{"2":{"44":1}}],["didn",{"2":{"70":3}}],["did",{"2":{"38":1,"70":1}}],["diff",{"2":{"104":1}}],["differences",{"2":{"58":1}}],["difference",{"2":{"42":1,"62":1,"64":1}}],["differently",{"2":{"118":1}}],["differentiates",{"2":{"40":1}}],["different",{"2":{"2":1,"19":2,"32":1,"38":4,"41":1,"45":1,"47":1,"50":1,"57":1,"58":2,"61":1,"62":1,"63":1}}],["diffs",{"2":{"28":1}}],["difficulties",{"2":{"43":1}}],["difficulty",{"2":{"36":1,"63":2}}],["difficult",{"2":{"17":1,"30":1,"35":1,"42":1,"50":1}}],["direction",{"2":{"63":1}}],["directly",{"2":{"41":1,"63":1,"64":1,"90":1,"118":1}}],["direct",{"2":{"17":1}}],["director",{"2":{"13":1}}],["diegetic",{"2":{"47":1}}],["die",{"2":{"13":4}}],["disparate",{"2":{"74":1}}],["displaying",{"2":{"25":1}}],["display",{"2":{"18":4,"19":1,"28":1,"41":1,"47":1}}],["displays",{"2":{"7":1,"19":1,"105":1}}],["disservice",{"2":{"69":1}}],["dissipates",{"2":{"46":1}}],["disengaging",{"2":{"63":1}}],["disengage",{"2":{"63":1}}],["disregard",{"2":{"57":1}}],["distancing",{"2":{"57":1}}],["distinguish",{"2":{"57":1}}],["distinct",{"2":{"42":1}}],["distilled",{"2":{"41":1}}],["distract",{"2":{"38":1}}],["disagreeing",{"2":{"46":1}}],["disagree",{"2":{"38":1}}],["disagreed",{"2":{"33":1}}],["disclaimer",{"2":{"40":1}}],["discussing",{"2":{"70":1}}],["discussion",{"2":{"33":1,"34":1}}],["discussions",{"2":{"16":1,"31":1,"118":1}}],["discuss",{"2":{"38":1,"47":1}}],["discussed",{"2":{"33":1,"39":1}}],["discusses",{"2":{"2":1,"9":1,"97":1,"114":1}}],["discourage",{"2":{"100":1}}],["discourse",{"2":{"10":1}}],["discounts",{"2":{"90":1}}],["discover",{"2":{"63":1}}],["discovering",{"2":{"34":1,"39":1}}],["discovery",{"2":{"19":1}}],["discord",{"2":{"10":1,"113":1}}],["dictate",{"2":{"20":1}}],["dichotomy",{"0":{"25":1},"2":{"7":2,"25":1,"26":2}}],["dice",{"0":{"13":1},"2":{"4":1,"13":24,"80":1,"81":1,"84":1}}],["digital",{"0":{"14":1},"2":{"7":2,"10":2,"14":4,"26":1,"28":2,"52":1,"89":1,"95":2,"104":2,"118":1}}],["dark",{"2":{"14":1,"45":1,"46":1,"95":1}}],["davey",{"0":{"11":1},"2":{"11":2,"66":3,"94":3,"112":1}}],["date",{"2":{"7":2,"13":2,"89":1}}],["data",{"2":{"2":1,"12":1,"17":1,"92":1,"114":1}}],["dallas",{"2":{"87":1}}],["dall",{"2":{"2":1}}],["days",{"2":{"1":1,"17":1,"102":1}}],["day",{"2":{"1":1,"102":1,"104":1}}],["demo",{"2":{"71":1,"110":1}}],["demonstrate",{"2":{"42":1}}],["deadbones",{"2":{"68":1,"70":1}}],["deals",{"2":{"89":1}}],["deal",{"2":{"48":1}}],["default",{"2":{"105":1}}],["defend",{"2":{"62":2}}],["defended",{"2":{"62":1}}],["define",{"2":{"39":1,"40":2,"42":2,"44":1}}],["defined",{"2":{"6":1,"40":1,"42":1,"43":1,"44":1,"50":3,"118":1}}],["defining",{"0":{"40":1},"1":{"41":1,"42":1,"43":1,"44":1,"45":1,"46":1,"47":1,"48":1,"49":1,"50":1,"51":1},"2":{"39":1,"40":1,"41":1,"43":1,"44":2,"52":1,"54":1}}],["definite",{"2":{"44":1}}],["definitely",{"2":{"34":1}}],["definitions",{"2":{"40":1,"41":1}}],["definition",{"2":{"40":1,"41":2,"42":5,"43":4,"44":2,"45":1,"46":1,"60":1}}],["definitively",{"2":{"39":1,"64":1}}],["debug",{"2":{"105":1}}],["debugging",{"2":{"56":1}}],["debt",{"2":{"87":1}}],["debate",{"2":{"42":1}}],["degree",{"2":{"50":1}}],["derived",{"2":{"44":2}}],["deeply",{"2":{"50":1,"56":1}}],["deep",{"2":{"39":1}}],["de",{"2":{"34":1}}],["depending",{"2":{"84":1}}],["dependencies",{"2":{"18":1}}],["depression",{"2":{"68":1}}],["depth",{"2":{"34":2,"39":3}}],["dedicated",{"2":{"30":1,"31":1,"69":1}}],["delaying",{"2":{"61":1}}],["delay",{"2":{"22":1}}],["deletion",{"2":{"21":2}}],["delete",{"2":{"21":5,"22":1}}],["decreasing",{"2":{"90":1}}],["deciding",{"2":{"42":1,"47":2,"50":1,"58":1}}],["decide",{"2":{"18":1,"19":1}}],["decision",{"2":{"39":1,"63":1}}],["decisions",{"2":{"36":1,"42":1,"45":1,"61":1,"63":1}}],["decent",{"2":{"64":1}}],["decentralized",{"0":{"12":1},"2":{"0":1,"3":1,"10":1,"15":1,"17":1,"18":1,"23":2,"76":1,"83":1,"92":2,"114":1}}],["december",{"2":{"1":1}}],["detriment",{"2":{"41":1}}],["detract",{"2":{"34":1,"36":1}}],["determine",{"2":{"22":2,"44":1,"45":1,"46":1,"49":1,"50":1,"57":1}}],["determines",{"2":{"13":1}}],["detects",{"2":{"13":1,"105":1}}],["details",{"2":{"5":1,"17":1}}],["deserves",{"2":{"41":1}}],["described",{"2":{"43":1,"60":1}}],["describe",{"2":{"42":1}}],["describes",{"2":{"25":1,"28":1}}],["descriptive",{"2":{"41":1}}],["descriptions",{"2":{"9":1}}],["desired",{"2":{"21":1}}],["designs",{"2":{"118":1}}],["designing",{"2":{"86":1}}],["designer",{"2":{"38":1}}],["designers",{"2":{"13":3}}],["designed",{"2":{"3":1,"6":1,"38":2,"88":1,"91":1}}],["design",{"0":{"38":1},"2":{"9":1,"38":10,"39":1,"41":3,"50":1,"52":2,"57":1,"58":1,"63":3,"105":1,"113":1}}],["devolving",{"2":{"39":1}}],["device",{"2":{"35":1}}],["dev",{"0":{"27":1},"2":{"80":1,"81":1,"84":1}}],["developing",{"2":{"56":1}}],["develop",{"2":{"41":1,"116":1}}],["developer",{"2":{"31":1,"33":1,"56":1,"57":1,"64":1,"116":1}}],["developers",{"0":{"29":1,"64":1,"109":1},"1":{"30":1,"31":1,"32":1},"2":{"2":1,"29":3,"30":1,"31":3,"32":1,"38":1,"41":1,"52":1,"54":1,"56":2,"57":1,"58":2,"91":1}}],["developed",{"2":{"30":1}}],["development",{"2":{"10":1,"13":2,"30":1,"53":1,"56":1,"57":1,"59":1,"67":1,"81":1,"85":1,"100":1,"113":1,"114":1}}],["devs",{"2":{"1":1,"53":2}}],["switching",{"2":{"71":1}}],["switch",{"2":{"52":1}}],["swarm",{"2":{"50":1,"62":1}}],["snippets",{"2":{"52":1}}],["smart",{"2":{"36":1}}],["smaller",{"2":{"90":1,"113":2}}],["smallest",{"2":{"13":1}}],["small",{"0":{"98":1,"99":1,"102":1,"103":1},"1":{"99":1,"100":1,"101":1,"102":1,"103":1},"2":{"3":1,"6":1,"7":1,"14":1,"26":1,"28":1,"46":1,"59":1,"64":1,"79":1,"90":1,"95":1,"98":2,"99":2,"100":1,"104":1,"113":1,"114":1,"117":1}}],["synapse",{"0":{"93":1},"2":{"65":1,"76":1,"84":1,"93":1}}],["synergism",{"2":{"45":1}}],["synergies",{"2":{"34":1,"36":1}}],["systems",{"2":{"34":1,"35":1,"87":1,"105":3}}],["system",{"2":{"6":1,"20":1,"34":2,"85":1,"86":1,"88":1,"102":1,"105":1}}],["skinner",{"2":{"35":2,"41":4}}],["skill",{"2":{"34":3,"40":1,"46":3,"57":1}}],["skilling",{"2":{"32":1}}],["skills",{"2":{"30":1,"41":2,"56":1}}],["skip",{"2":{"13":2,"72":1}}],["slightly",{"2":{"61":1}}],["slight",{"2":{"46":1,"89":1}}],["slowly",{"2":{"38":1}}],["slots",{"2":{"13":1}}],["sleep",{"2":{"35":1,"41":1}}],["slay",{"2":{"5":1,"35":1}}],["sands",{"2":{"105":2}}],["salt",{"2":{"57":1}}],["satisfy",{"2":{"57":1}}],["satisfying",{"2":{"34":2}}],["satisfactory",{"2":{"42":1}}],["satire",{"2":{"41":1}}],["sake",{"2":{"39":1,"40":1,"42":1,"60":1}}],["safely",{"2":{"61":1}}],["safe",{"2":{"38":1,"42":1}}],["said",{"2":{"32":1,"33":1,"57":1,"61":1,"64":1,"89":1}}],["say",{"2":{"18":2,"35":1,"38":1,"42":1,"46":1,"49":1,"57":1,"61":3,"62":1,"64":1,"74":1}}],["saying",{"2":{"18":2}}],["same",{"2":{"13":1,"18":2,"20":1,"36":1,"41":1,"62":2,"63":3,"64":1,"113":1}}],["save",{"2":{"13":1,"47":1}}],["scams",{"2":{"92":1}}],["scale",{"2":{"9":1}}],["sculpture",{"2":{"39":1}}],["schedule",{"2":{"35":1,"41":1}}],["school",{"2":{"19":1}}],["scientific",{"2":{"18":1,"85":1}}],["screen",{"2":{"41":1,"105":1}}],["screenshot",{"2":{"13":1}}],["scriptable",{"2":{"13":1}}],["scripts",{"2":{"13":2}}],["scenes",{"2":{"105":1}}],["scene",{"2":{"13":1,"35":1,"70":1}}],["sitting",{"2":{"35":1}}],["sites",{"2":{"23":1,"98":2,"100":1,"113":1}}],["site",{"2":{"13":1,"18":1,"53":1,"97":1,"100":1,"104":1,"111":1,"119":1}}],["since",{"2":{"33":2,"35":1,"44":1,"58":1,"62":1,"74":1,"113":1}}],["sink",{"2":{"13":1}}],["single",{"2":{"12":1,"13":1,"17":1,"39":1,"46":3,"61":1,"114":1,"121":1}}],["side",{"2":{"13":1,"62":1}}],["sides",{"2":{"13":1,"35":1,"42":1}}],["simple",{"2":{"105":1}}],["simply",{"2":{"42":1,"47":1,"63":1,"64":1}}],["sim",{"2":{"62":1}}],["simulate",{"2":{"13":1}}],["simulator",{"2":{"13":1,"39":1,"50":1}}],["similarities",{"2":{"40":1,"42":1}}],["similarity",{"2":{"35":1}}],["similarly",{"2":{"39":1,"41":1,"63":1}}],["similar",{"2":{"10":2,"28":1,"32":1,"40":1,"42":1,"43":1,"62":1,"98":1}}],["signal",{"2":{"48":1,"94":1}}],["signature",{"0":{"96":1},"2":{"20":2,"21":1,"97":1,"117":1}}],["significantly",{"2":{"46":1,"89":1}}],["significant",{"2":{"35":1,"43":1}}],["signed",{"2":{"18":1,"68":1,"96":1,"97":1}}],["sign",{"2":{"13":1}}],["shirt",{"2":{"68":1}}],["shift",{"0":{"46":1},"2":{"46":6,"49":1}}],["shifts",{"2":{"37":1,"46":5}}],["shields",{"2":{"38":3}}],["shake",{"2":{"46":1}}],["share",{"2":{"58":1,"59":1,"105":1,"113":1}}],["shared",{"2":{"4":1,"23":1,"113":2}}],["sharing",{"2":{"57":1}}],["sharp",{"2":{"38":1}}],["shape",{"2":{"27":1}}],["shallow",{"2":{"19":1}}],["shoes",{"2":{"58":1}}],["shooters",{"2":{"38":1}}],["shorthand",{"2":{"40":1}}],["short",{"2":{"34":1,"60":1,"61":1,"62":1}}],["shortcut",{"2":{"9":1}}],["shouldn",{"2":{"42":1,"43":1,"45":1}}],["should",{"2":{"17":1,"20":3,"28":1,"41":1,"42":1,"44":2,"45":1,"46":1,"57":3,"61":3,"64":1,"97":1}}],["shop",{"2":{"13":3}}],["shows",{"2":{"44":1,"69":1,"86":2}}],["shown",{"2":{"13":1,"31":1}}],["showing",{"2":{"13":1}}],["show",{"2":{"13":1,"38":1,"46":1,"77":1,"88":1,"105":1}}],["severely",{"2":{"105":1}}],["several",{"2":{"10":1,"22":1,"41":1,"47":1,"48":1,"63":1,"81":1,"105":1}}],["series",{"2":{"50":1,"62":1,"68":2,"69":1,"71":1,"97":1,"101":1}}],["serving",{"2":{"20":1}}],["service",{"2":{"15":1}}],["serve",{"2":{"41":1,"89":1}}],["serves",{"2":{"20":1,"86":1}}],["servers",{"0":{"19":1},"2":{"12":1,"19":4,"20":2,"22":5,"102":1,"113":1,"114":1}}],["server",{"2":{"12":1,"15":1,"16":1,"17":3,"18":1,"19":2,"21":1,"22":2,"93":1,"100":1}}],["sell",{"2":{"89":1}}],["selected",{"2":{"46":1}}],["self",{"2":{"15":1,"17":1,"92":1}}],["section",{"2":{"38":1}}],["second",{"2":{"13":1,"14":1,"61":1,"63":1}}],["separates",{"2":{"63":1}}],["separate",{"2":{"36":1}}],["separated",{"2":{"4":2}}],["sensors",{"2":{"86":1}}],["sense",{"2":{"34":1,"35":2,"36":2,"41":1,"42":2,"43":1,"46":2,"63":2,"64":1}}],["sends",{"2":{"22":1}}],["sending",{"2":{"19":2,"21":1,"22":1}}],["send",{"2":{"18":1,"19":1,"20":1,"21":2}}],["sent",{"2":{"18":1}}],["settle",{"2":{"60":1}}],["setting",{"2":{"39":1}}],["settings",{"2":{"13":1}}],["setup",{"2":{"21":1}}],["set",{"2":{"13":1,"28":1,"40":1,"44":1,"58":1,"113":1}}],["sets",{"2":{"13":2}}],["seemed",{"2":{"71":1}}],["seem",{"2":{"41":1,"59":1,"60":1,"61":1,"73":1}}],["seems",{"2":{"10":1,"29":1,"39":1,"43":1,"73":1}}],["seeking",{"0":{"58":1},"2":{"41":2}}],["seek",{"2":{"35":2,"41":1,"63":2}}],["seen",{"2":{"35":1,"40":1,"47":1,"63":1}}],["seeing",{"2":{"34":2}}],["see",{"2":{"13":1,"32":1,"35":3,"39":1,"41":2,"46":1,"52":1}}],["semester",{"2":{"13":3}}],["search",{"2":{"9":2,"99":1}}],["summary",{"2":{"104":1}}],["summarize",{"2":{"13":1}}],["suggested",{"2":{"104":1}}],["suggest",{"2":{"64":1}}],["suggestions",{"2":{"40":1,"57":2}}],["sure",{"2":{"45":1,"60":1,"64":1}}],["surface",{"2":{"41":1}}],["survivors",{"2":{"33":3,"34":2,"35":1,"36":3,"39":3}}],["sustainable",{"2":{"109":1}}],["suspect",{"2":{"34":2}}],["susceptibility",{"2":{"32":1}}],["successes",{"2":{"59":1}}],["successful",{"2":{"36":1}}],["success",{"2":{"31":1,"57":1}}],["such",{"2":{"10":1,"13":1,"21":2,"22":2,"41":1,"42":3,"44":1,"48":1,"50":1,"63":1,"69":1}}],["subject",{"2":{"86":1,"92":1}}],["subjective",{"2":{"63":1}}],["sub",{"0":{"50":1},"2":{"42":4,"50":5}}],["subset",{"2":{"36":1}}],["subscriptions",{"2":{"19":1}}],["subscribe",{"2":{"19":2,"22":2}}],["subscribed",{"2":{"19":1}}],["subscribing",{"2":{"19":2,"20":2,"22":1}}],["submenu",{"2":{"9":1}}],["suffice",{"2":{"38":1}}],["suffices",{"2":{"19":1}}],["sufficiently",{"2":{"36":1,"45":1,"63":3}}],["sufficient",{"2":{"18":1,"34":1}}],["suffers",{"2":{"17":1}}],["suffer",{"2":{"12":1}}],["suppose",{"2":{"60":1}}],["supports",{"2":{"102":1}}],["supported",{"2":{"15":1}}],["support",{"2":{"13":1,"15":1,"42":1,"58":2,"86":1,"87":2}}],["superlinear",{"2":{"48":1}}],["supersedes",{"2":{"39":1}}],["supercede",{"2":{"18":1}}],["super",{"2":{"1":2}}],["suitable",{"2":{"7":1}}],["s",{"0":{"94":1},"2":{"5":2,"7":1,"10":1,"11":4,"13":4,"15":1,"18":1,"19":1,"20":2,"22":1,"26":1,"27":1,"28":1,"29":1,"30":1,"32":1,"33":2,"34":2,"35":4,"38":4,"39":3,"40":6,"41":7,"42":2,"43":2,"44":1,"45":2,"46":4,"49":1,"52":1,"53":1,"56":3,"57":4,"58":1,"59":4,"60":2,"61":3,"62":3,"63":8,"68":2,"69":2,"74":2,"86":1,"91":2,"92":1,"94":2,"97":1,"104":1,"112":1,"113":1,"114":1,"120":2}}],["sphere",{"2":{"86":3}}],["spoilers",{"2":{"74":1,"94":1}}],["spirit",{"0":{"71":1}}],["spire",{"2":{"5":1,"35":1}}],["spaces",{"2":{"113":2}}],["space",{"2":{"63":1}}],["span",{"2":{"41":1}}],["spawn",{"2":{"36":1}}],["spamming",{"2":{"41":2}}],["spam",{"2":{"22":2,"61":1}}],["speech",{"0":{"85":1},"1":{"86":1,"87":1},"2":{"80":1,"82":1,"85":3,"86":1,"87":1}}],["speed",{"2":{"35":2}}],["spent",{"2":{"61":2,"69":1,"90":1}}],["spend",{"2":{"41":1}}],["spends",{"2":{"38":1}}],["spending",{"2":{"34":1}}],["spectrum",{"2":{"41":1,"61":1,"63":2}}],["specially",{"2":{"20":1,"21":2}}],["specialized",{"2":{"2":1}}],["specification",{"2":{"28":1}}],["specifically",{"2":{"28":1,"35":1,"36":1,"38":1,"39":1,"40":1,"114":1}}],["specific",{"2":{"15":1,"19":2,"22":1,"31":1,"40":1,"44":1,"46":1,"57":3,"58":1,"60":1,"62":1,"63":1,"64":1,"92":1,"114":1}}],["sprites",{"2":{"30":1}}],["steam",{"2":{"105":1}}],["stealing",{"2":{"105":1}}],["steel",{"2":{"63":1}}],["steelie",{"2":{"63":1}}],["steps",{"2":{"46":1}}],["step",{"2":{"43":1,"62":1}}],["stick",{"2":{"59":1}}],["stimuli",{"2":{"41":1}}],["still",{"2":{"12":1,"13":1,"17":2,"18":1,"32":1,"34":1,"36":1,"39":1,"41":1,"42":1,"47":1,"61":2,"63":1,"67":1,"70":1,"92":1,"98":1}}],["stream",{"2":{"104":1}}],["stretch",{"2":{"49":1}}],["stretching",{"2":{"35":1,"60":1}}],["strict",{"2":{"90":1}}],["strictly",{"2":{"41":1}}],["struggles",{"2":{"58":1}}],["struggling",{"2":{"35":1}}],["stronger",{"2":{"48":1,"50":1,"51":1,"63":1}}],["strong",{"2":{"43":1,"47":1}}],["strongly",{"2":{"38":1,"48":1}}],["strange",{"0":{"68":1,"70":1,"72":1,"73":1,"74":1},"1":{"69":1,"70":1,"71":1,"72":1,"73":1,"74":1},"2":{"68":1,"69":1,"106":1}}],["straight",{"2":{"13":1}}],["strategies",{"2":{"13":4,"36":1,"41":1,"42":1}}],["strategy",{"0":{"36":1},"2":{"4":1,"13":2,"36":4,"40":2,"42":8,"44":2}}],["stopgaming",{"2":{"35":1,"41":1}}],["stop",{"2":{"21":1}}],["stopped",{"2":{"13":2}}],["stolen",{"2":{"18":1}}],["storefronts",{"2":{"32":1,"89":2}}],["store",{"2":{"18":2,"90":1}}],["stores",{"2":{"7":1}}],["storing",{"2":{"17":1,"19":1}}],["stories",{"2":{"11":1}}],["storm",{"0":{"70":1},"2":{"13":1}}],["story",{"2":{"13":2,"39":1,"69":1,"70":1,"74":2,"90":1}}],["studying",{"2":{"35":1}}],["studios",{"2":{"89":1,"107":1}}],["studio",{"2":{"9":1,"66":1}}],["stuck",{"2":{"32":1,"50":1}}],["stuff",{"2":{"4":1,"13":1,"38":1}}],["stability",{"2":{"87":1}}],["staple",{"2":{"63":1}}],["stale",{"2":{"46":1,"62":1}}],["staleness",{"0":{"37":1}}],["staying",{"2":{"59":1}}],["stay",{"2":{"45":1}}],["stagnating",{"2":{"37":1}}],["stage",{"2":{"4":1}}],["starcraft",{"2":{"36":1}}],["starter",{"2":{"68":2}}],["started",{"2":{"1":1,"13":1,"34":1,"56":1}}],["starting",{"2":{"13":1}}],["starts",{"2":{"13":1}}],["start",{"2":{"13":2,"30":1,"34":1,"38":1,"41":2,"45":1,"62":1,"63":2,"68":1}}],["stat",{"2":{"46":1}}],["stating",{"2":{"44":1}}],["static",{"2":{"37":1,"62":1,"100":1,"102":3,"111":1}}],["stats",{"2":{"34":1}}],["states",{"2":{"47":1}}],["statement",{"2":{"46":1}}],["state",{"2":{"13":1,"35":1,"40":1,"41":1,"43":1,"47":1,"59":1}}],["stance",{"2":{"41":2,"62":1}}],["standards",{"2":{"100":1}}],["stands",{"2":{"39":1}}],["stand",{"2":{"34":1}}],["stanley",{"2":{"11":2}}],["style",{"2":{"1":1,"5":1,"26":1,"63":1,"77":2}}],["son",{"2":{"116":1}}],["song",{"2":{"69":1}}],["sorts",{"2":{"67":1}}],["sort",{"2":{"48":1,"50":1,"102":1}}],["sorting",{"2":{"41":1,"92":1}}],["sortings",{"2":{"7":1}}],["soundtrack",{"2":{"89":1}}],["sound",{"2":{"86":1}}],["sounds",{"2":{"42":1,"74":1,"86":1}}],["south",{"2":{"68":1}}],["soul",{"2":{"56":1}}],["souls",{"2":{"38":2}}],["source",{"0":{"84":1},"2":{"1":1,"8":1,"10":1,"12":1,"13":1,"18":1,"24":1,"27":1,"41":1,"75":1,"77":1,"84":1,"88":1,"91":1,"93":1,"111":1,"114":1}}],["sole",{"2":{"87":1}}],["solely",{"2":{"39":1,"57":1,"61":1}}],["solving",{"2":{"47":1}}],["solved",{"2":{"38":1}}],["solve",{"0":{"22":1},"2":{"6":1}}],["solution",{"2":{"36":1,"57":2}}],["sold",{"2":{"13":1}}],["sogge",{"2":{"10":1}}],["so",{"2":{"4":1,"13":3,"18":1,"30":1,"35":3,"36":1,"38":2,"40":2,"41":1,"42":2,"44":1,"45":1,"46":3,"47":1,"57":1,"59":1,"60":1,"61":2,"62":2,"63":5,"69":1,"70":1,"72":1,"87":1,"104":1,"105":1}}],["softwares",{"2":{"9":1}}],["software",{"2":{"2":2,"24":1,"75":1,"77":1,"93":1,"116":1}}],["sometimes",{"2":{"97":1}}],["something",{"2":{"12":1,"22":1,"33":1,"35":3,"41":2,"48":1,"61":2,"64":1,"104":2}}],["somewhat",{"2":{"39":1}}],["somewhere",{"2":{"36":1}}],["someone",{"2":{"21":1,"34":1,"35":1,"41":1,"46":1,"97":1}}],["some",{"2":{"1":1,"2":1,"9":2,"12":1,"13":1,"19":2,"20":2,"27":1,"32":1,"33":2,"34":1,"35":3,"38":1,"39":1,"40":1,"41":2,"42":3,"45":1,"46":3,"48":2,"49":1,"50":2,"53":1,"56":1,"61":1,"63":7,"64":1,"88":1,"97":1,"102":1,"105":1,"114":1}}],["social",{"0":{"65":1,"92":1,"119":1},"2":{"0":1,"3":1,"7":1,"8":1,"10":2,"12":1,"15":1,"16":1,"17":2,"19":1,"23":2,"24":1,"65":1,"77":1,"80":1,"82":1,"83":1,"92":3,"93":1,"98":1,"100":1,"113":1,"119":2}}],["hyped",{"2":{"71":1}}],["hyper",{"2":{"32":1}}],["hyping",{"2":{"46":1}}],["html",{"2":{"30":1}}],["https",{"2":{"14":3,"44":1,"70":2,"79":1}}],["hitting",{"2":{"86":1}}],["hit",{"2":{"38":1,"61":1,"86":2}}],["hide",{"2":{"38":2,"41":1}}],["hiding",{"2":{"21":1}}],["his",{"2":{"33":1}}],["history",{"2":{"20":1}}],["hierarchy",{"2":{"21":2}}],["highest",{"2":{"46":1}}],["higher",{"2":{"35":1,"45":1,"50":1,"62":1,"107":2}}],["highly",{"2":{"38":1,"105":1}}],["highlighting",{"2":{"62":1}}],["highlight",{"2":{"13":1}}],["high",{"0":{"47":1},"2":{"13":1,"47":1,"114":1}}],["huge",{"2":{"69":1}}],["hurtful",{"2":{"57":1}}],["hunger",{"2":{"41":1}}],["hubs",{"2":{"18":3}}],["hub",{"0":{"104":1},"2":{"14":1,"18":5,"28":1,"75":1,"98":1,"104":1,"111":1}}],["human",{"2":{"2":2,"18":1,"113":1}}],["homogenized",{"2":{"98":1,"100":1}}],["home",{"2":{"2":1}}],["horrible",{"2":{"74":1}}],["horribly",{"2":{"40":1}}],["hope",{"2":{"52":1,"74":1}}],["honest",{"2":{"49":1}}],["honestly",{"2":{"40":1,"43":1,"63":1}}],["hobbyist",{"2":{"32":1}}],["house",{"2":{"18":1}}],["host",{"2":{"113":1}}],["hosts",{"2":{"65":1}}],["hosting",{"2":{"17":1,"24":1,"92":1,"97":1,"100":1,"102":3}}],["hosted",{"2":{"15":1,"65":1}}],["hotkey",{"2":{"9":1}}],["however",{"2":{"32":1,"33":1,"34":1,"38":1,"39":2,"41":1,"56":1,"59":1,"60":1,"62":1,"63":1,"64":1,"67":1}}],["how",{"2":{"1":1,"2":2,"10":2,"17":1,"18":3,"19":1,"20":1,"21":1,"28":1,"36":1,"38":1,"40":1,"41":4,"42":2,"44":1,"46":2,"52":1,"56":1,"58":1,"59":2,"60":2,"62":3,"63":1,"64":1,"89":1,"98":1,"102":1,"113":1,"114":1}}],["half",{"2":{"70":1}}],["haley",{"2":{"68":1,"72":2}}],["harsh",{"2":{"62":1}}],["hardest",{"2":{"56":1}}],["harder",{"2":{"36":1,"56":1}}],["hardly",{"2":{"41":1}}],["hard",{"2":{"22":2,"35":2,"46":1,"63":1,"92":1,"109":1}}],["having",{"2":{"13":1,"17":1,"18":1,"31":1,"34":1,"38":3,"39":2,"40":1,"42":1,"43":1,"47":1,"48":1,"49":1,"50":3,"60":1,"64":1,"69":2,"95":1,"114":1}}],["haven",{"2":{"30":1,"53":1,"72":1,"73":1}}],["have",{"2":{"9":1,"13":2,"15":1,"17":1,"18":2,"19":1,"21":2,"22":2,"30":3,"31":1,"32":1,"34":2,"35":4,"36":2,"37":1,"38":4,"39":4,"40":2,"42":3,"43":1,"44":1,"45":1,"46":3,"47":4,"48":2,"50":1,"53":4,"56":1,"58":1,"59":1,"60":1,"61":3,"62":3,"63":4,"64":4,"67":1,"70":1,"81":2,"89":2,"92":1,"98":1,"104":2,"113":1,"114":1}}],["happen",{"2":{"46":1,"48":1,"63":1}}],["happens",{"2":{"41":1,"62":1,"63":1}}],["happening",{"2":{"13":1}}],["happy",{"2":{"1":1,"63":1,"105":1}}],["has",{"2":{"13":4,"18":1,"22":1,"31":1,"32":2,"33":4,"34":2,"38":3,"39":3,"41":1,"44":2,"48":2,"61":1,"62":1,"63":2,"64":1,"67":1,"69":1,"73":1,"86":1,"95":1,"102":1,"113":1}}],["handling",{"2":{"56":1}}],["handled",{"2":{"20":1}}],["handle",{"2":{"10":1,"17":1,"18":1,"36":1}}],["hands",{"2":{"13":1}}],["hand",{"2":{"12":1,"41":2,"89":1}}],["handful",{"2":{"12":1,"44":2}}],["hades",{"2":{"45":1}}],["had",{"2":{"1":1,"62":1,"73":1}}],["hence",{"2":{"41":1}}],["head",{"2":{"61":1,"86":1}}],["heart",{"2":{"56":1}}],["hears",{"2":{"19":1}}],["heavily",{"2":{"40":1,"48":1}}],["heavy",{"2":{"35":1}}],["health",{"2":{"38":3,"86":1}}],["healthy",{"2":{"35":1,"41":1}}],["hell",{"2":{"30":1,"39":1,"41":1}}],["helpful",{"2":{"58":1}}],["helps",{"2":{"37":1,"38":1}}],["help",{"2":{"2":1,"13":1,"31":1,"35":1,"40":1,"41":1,"100":1}}],["heuristic",{"2":{"21":1,"22":1,"89":1}}],["heggen",{"2":{"10":1}}],["heroes",{"2":{"45":1}}],["her",{"2":{"9":1,"69":5}}],["here",{"2":{"1":1,"4":1,"10":1,"13":4,"27":1,"34":1,"40":3,"41":1,"43":1,"44":2,"45":2,"46":1,"61":1,"62":1,"64":1,"67":1,"70":1,"81":1,"86":1,"88":1}}],["hectic",{"2":{"1":1}}],["10x",{"2":{"62":1}}],["100",{"2":{"61":2}}],["10",{"2":{"45":2}}],["1e10",{"2":{"34":1}}],["1e100",{"2":{"34":1}}],["1e1001",{"2":{"34":1}}],["1e1000",{"2":{"34":1}}],["1",{"2":{"1":1}}],["twitter",{"2":{"77":1}}],["two",{"2":{"13":2,"42":1,"43":1,"62":2,"69":1,"74":2}}],["type",{"2":{"58":1}}],["types",{"2":{"38":1,"58":1}}],["typically",{"2":{"18":2,"23":1,"30":1,"35":1,"41":1,"42":3,"46":1,"47":2,"48":1,"57":1,"84":1,"89":2,"95":1,"98":1,"108":1}}],["typing",{"2":{"9":1,"105":1}}],["tycoon",{"2":{"27":1}}],["templates",{"2":{"100":1}}],["template",{"2":{"91":1}}],["temple",{"2":{"44":1}}],["temporarily",{"2":{"22":1}}],["tell",{"2":{"39":1}}],["teaches",{"2":{"56":1}}],["teaching",{"2":{"38":1,"86":1}}],["team",{"2":{"13":1,"114":1}}],["tend",{"2":{"31":1,"32":1,"37":1,"38":1,"42":1,"47":2,"48":1,"50":1}}],["tends",{"2":{"31":1,"41":1,"59":1}}],["textual",{"2":{"47":1}}],["text",{"2":{"20":2,"41":1}}],["tests",{"2":{"87":1}}],["test",{"2":{"13":1,"105":1}}],["testing",{"2":{"13":1,"86":1}}],["techniques",{"2":{"107":1}}],["technically",{"2":{"30":1,"34":1,"62":1,"91":1}}],["tech",{"2":{"10":1,"87":1}}],["terms",{"2":{"41":3,"42":1,"61":1}}],["term",{"2":{"2":1,"41":6,"46":1,"63":1,"81":1,"114":1,"121":1}}],["tiers",{"2":{"114":1}}],["tied",{"2":{"7":1,"26":1,"35":1,"46":1,"63":1}}],["tip",{"2":{"64":1}}],["tips",{"0":{"64":1},"2":{"64":1}}],["til",{"2":{"45":1}}],["title",{"2":{"41":1,"105":1}}],["titles",{"2":{"41":2,"45":1}}],["times",{"2":{"37":1,"39":1,"48":1,"61":2,"62":2,"64":1}}],["timescale",{"2":{"13":1}}],["time",{"2":{"13":1,"32":1,"35":3,"38":1,"39":2,"45":2,"50":1,"51":1,"57":1,"60":1,"61":8,"62":4,"63":2,"67":1,"70":1,"72":1,"73":1,"85":1,"86":1,"87":1,"94":1,"105":2}}],["timeline",{"2":{"7":1}}],["timelines",{"2":{"6":1,"7":1,"74":1}}],["t",{"2":{"4":1,"15":1,"17":3,"18":1,"22":2,"27":1,"30":4,"34":3,"35":4,"36":1,"38":3,"40":3,"41":2,"42":3,"43":4,"45":1,"46":2,"47":2,"48":1,"49":1,"52":1,"53":1,"57":2,"62":2,"63":7,"64":2,"70":3,"72":1,"73":1,"74":1,"81":1,"92":1,"98":1,"109":1}}],["tampered",{"2":{"97":1}}],["target",{"2":{"86":2}}],["targeted",{"2":{"60":1}}],["tangible",{"2":{"74":1}}],["tangent",{"2":{"41":1}}],["tab",{"2":{"62":1}}],["table",{"2":{"13":1}}],["talker",{"2":{"86":2}}],["talk",{"2":{"23":1,"38":1,"39":1,"63":1}}],["talking",{"2":{"13":1,"38":1,"40":1}}],["talks",{"2":{"11":1,"86":1,"101":1}}],["taking",{"2":{"13":1,"34":1,"35":1,"39":1,"41":2,"69":1}}],["taken",{"2":{"33":2,"50":1}}],["takes",{"2":{"13":1,"35":1,"40":1,"57":1,"61":1}}],["take",{"2":{"2":1,"7":1,"13":1,"35":1,"39":1,"46":2,"47":1,"48":1,"57":1,"61":2,"62":3,"92":1,"114":1}}],["tagged",{"2":{"11":1,"12":1,"80":1,"91":2}}],["tags",{"2":{"0":1,"1":1,"3":1,"4":1,"5":1,"13":1,"15":1,"23":1,"27":1,"65":1,"66":1,"67":1,"83":1,"85":1,"88":1,"91":1,"94":1,"105":1,"112":1}}],["turn",{"2":{"13":1}}],["turned",{"2":{"1":1}}],["tutorials",{"2":{"30":1}}],["tutorial",{"2":{"13":2}}],["tube",{"2":{"2":1}}],["trial",{"2":{"92":1}}],["trivial",{"2":{"62":1}}],["trivially",{"2":{"35":1,"64":1}}],["tricky",{"2":{"42":1}}],["treats",{"2":{"118":1}}],["treating",{"2":{"86":1}}],["tremendous",{"2":{"31":1}}],["tree",{"0":{"27":1},"2":{"40":1,"41":2,"46":1,"67":1,"80":1,"81":1,"84":1,"91":1}}],["trends",{"2":{"50":2}}],["trended",{"2":{"41":1}}],["trend",{"2":{"12":1,"41":1,"63":3}}],["true",{"0":{"73":1},"2":{"59":1,"63":1,"64":1}}],["truly",{"2":{"40":1,"57":1,"60":1,"63":1}}],["truth",{"2":{"18":1}}],["trust",{"2":{"18":6,"22":1,"113":1}}],["trying",{"2":{"38":1,"45":1,"46":1,"61":1,"109":1}}],["try",{"2":{"12":1,"56":1,"57":1,"61":1,"64":1}}],["track",{"2":{"47":1}}],["traditional",{"2":{"44":1,"45":1,"92":1}}],["trailer",{"2":{"74":1}}],["trait",{"2":{"46":1}}],["traits",{"2":{"43":1,"45":1}}],["training",{"2":{"2":1,"85":1}}],["trained",{"2":{"2":1,"58":1}}],["transferrable",{"2":{"102":1}}],["transitioning",{"2":{"101":1}}],["transparent",{"2":{"86":1}}],["translated",{"2":{"51":1}}],["transaction",{"2":{"35":1}}],["transcribing",{"2":{"6":1}}],["tropes",{"2":{"1":1,"27":1,"39":1,"88":1}}],["toward",{"2":{"60":1}}],["towards",{"2":{"12":1,"40":1,"45":1,"46":1,"48":1,"57":1,"61":2,"63":1}}],["totally",{"2":{"49":1}}],["tongue",{"2":{"86":2}}],["tons",{"2":{"41":1,"60":1}}],["tone",{"2":{"11":1}}],["tolerant",{"2":{"38":1}}],["too",{"2":{"38":2,"41":2,"46":2,"60":1,"62":2,"63":2,"92":1,"100":1}}],["tools",{"0":{"82":1},"2":{"13":1,"30":1,"62":1,"80":1,"102":1,"105":1,"114":1}}],["tool",{"2":{"4":1,"57":1}}],["toy",{"2":{"35":1}}],["topaz",{"2":{"116":2}}],["topic",{"2":{"33":1,"38":1,"113":1}}],["topics",{"2":{"10":2}}],["top",{"2":{"13":2,"38":1,"46":1}}],["together",{"2":{"10":1,"61":1}}],["to",{"0":{"22":1,"29":2,"30":1,"31":1,"33":2,"40":1,"52":1,"56":1,"59":1,"60":1,"108":1},"1":{"30":2,"31":2,"32":2,"34":2,"35":2,"36":2,"37":2,"38":2,"39":2,"41":1,"42":1,"43":1,"44":1,"45":1,"46":1,"47":1,"48":1,"49":1,"50":1,"51":1,"53":1,"54":1,"55":1,"57":1,"58":1,"59":1,"61":1,"62":1,"63":1,"64":1},"2":{"2":2,"3":1,"4":2,"6":1,"7":1,"9":1,"10":4,"12":2,"13":36,"14":1,"15":2,"16":1,"17":6,"18":11,"19":11,"20":10,"21":6,"22":13,"23":2,"26":2,"28":4,"29":2,"30":11,"31":6,"32":6,"33":5,"34":19,"35":30,"36":8,"37":3,"38":18,"39":11,"40":7,"41":31,"42":11,"43":6,"44":8,"45":6,"46":13,"47":9,"48":6,"49":6,"50":9,"52":6,"53":2,"54":6,"55":1,"56":13,"57":12,"58":5,"59":6,"60":10,"61":16,"62":15,"63":28,"64":6,"67":1,"69":6,"70":2,"71":1,"72":2,"73":3,"74":6,"81":1,"84":1,"86":2,"87":2,"88":1,"89":6,"91":2,"92":6,"94":1,"95":1,"96":1,"97":2,"98":3,"100":1,"101":1,"102":3,"104":3,"105":2,"107":4,"108":1,"109":1,"113":6,"114":5,"117":1,"118":1}}],["tv",{"2":{"1":1,"27":1,"88":1}}],["thousands",{"2":{"31":1,"41":1}}],["thoughts",{"2":{"104":2}}],["thought",{"2":{"39":1,"62":1}}],["though",{"2":{"20":1,"34":1,"39":1,"49":1,"63":1}}],["those",{"2":{"20":1,"21":1,"30":1,"33":1,"35":3,"38":1,"39":1,"40":1,"41":4,"44":1,"49":1,"60":3,"61":1,"62":1,"63":1,"84":1,"107":1}}],["threads",{"2":{"70":1,"77":1}}],["threshold",{"2":{"13":1,"30":1,"42":1}}],["throughline",{"2":{"63":2}}],["throughout",{"2":{"37":1,"63":1,"69":1}}],["through",{"2":{"9":2,"13":4,"18":1,"39":1,"48":1,"68":2,"70":1,"72":1}}],["thing",{"2":{"60":1,"62":1,"63":1}}],["things",{"2":{"1":1,"2":1,"7":1,"10":1,"13":1,"19":1,"27":1,"30":1,"35":2,"39":2,"41":2,"62":1,"63":5,"64":1,"68":1,"88":1,"102":1}}],["thin",{"2":{"35":1}}],["thinking",{"2":{"33":1}}],["think",{"2":{"33":1,"34":1,"35":1,"38":2,"39":3,"40":1,"41":4,"42":1,"43":1,"45":2,"49":1,"56":3,"58":1,"60":1,"61":1,"63":1,"69":2,"74":1}}],["this",{"0":{"53":1,"104":1},"2":{"1":3,"7":1,"9":1,"13":4,"14":1,"16":1,"17":1,"18":3,"19":2,"20":3,"21":1,"27":2,"28":1,"29":1,"30":1,"31":1,"32":3,"33":2,"34":4,"35":4,"36":2,"37":1,"38":8,"40":2,"41":8,"42":10,"43":1,"44":2,"45":1,"46":2,"47":1,"48":3,"50":1,"52":4,"53":2,"56":2,"57":1,"60":2,"61":5,"62":3,"63":15,"64":3,"68":1,"69":1,"70":1,"72":1,"73":1,"74":4,"75":1,"86":3,"88":2,"91":2,"95":2,"98":1,"104":3,"107":1,"111":1,"113":3,"114":1,"115":2,"117":1,"121":1}}],["than",{"2":{"1":1,"7":1,"9":1,"10":1,"13":1,"34":1,"35":1,"36":1,"38":2,"39":2,"40":1,"41":2,"42":1,"46":1,"48":1,"49":1,"56":1,"59":1,"70":1,"74":1,"107":1,"113":1}}],["that",{"2":{"1":1,"2":2,"7":2,"9":1,"10":1,"12":1,"13":6,"16":1,"18":2,"19":2,"20":5,"21":3,"22":4,"23":1,"26":2,"28":1,"30":3,"31":1,"32":4,"33":5,"34":6,"35":9,"36":6,"38":5,"39":8,"40":2,"41":23,"42":8,"43":5,"44":1,"45":1,"46":10,"47":1,"48":1,"49":4,"50":5,"51":1,"53":1,"56":2,"57":6,"59":1,"60":2,"61":7,"62":8,"63":12,"64":4,"67":1,"69":1,"70":1,"74":3,"78":1,"86":1,"90":1,"91":1,"92":2,"95":1,"98":1,"100":1,"102":2,"105":2,"107":1,"113":2,"114":1,"118":1,"120":2}}],["theory",{"2":{"95":1}}],["theoretically",{"2":{"17":1}}],["theoretical",{"2":{"6":1,"16":1,"26":1,"28":1}}],["thepaperpilot",{"2":{"18":1,"79":1}}],["then",{"2":{"13":3,"22":1,"39":1,"40":1,"41":1,"57":1,"61":1,"62":1,"63":2,"64":2,"90":1}}],["thematic",{"2":{"69":1}}],["theme",{"2":{"42":1,"71":1}}],["themes",{"2":{"10":1,"69":1}}],["themselves",{"2":{"21":1,"34":1,"35":1,"38":1,"42":1,"43":1,"57":1,"58":1}}],["them",{"2":{"13":4,"14":1,"18":1,"19":1,"22":1,"29":1,"30":1,"33":1,"35":4,"36":1,"37":1,"38":1,"39":2,"40":1,"41":3,"42":1,"43":1,"44":1,"47":1,"48":1,"51":1,"57":1,"62":3,"64":1,"74":1,"90":1,"105":1,"109":1,"118":1}}],["they",{"2":{"10":5,"13":4,"18":4,"21":1,"28":1,"34":1,"35":7,"36":2,"38":2,"39":5,"40":2,"41":3,"42":3,"43":2,"44":1,"46":3,"47":2,"48":4,"50":1,"56":1,"57":1,"58":3,"59":1,"60":3,"61":2,"62":7,"63":6,"68":1,"74":1,"89":1,"100":1,"113":1}}],["these",{"2":{"9":1,"10":2,"13":1,"17":1,"19":1,"20":1,"31":1,"32":1,"33":1,"35":2,"37":1,"41":6,"42":1,"45":1,"47":4,"48":3,"50":1,"61":2,"62":1,"63":3,"70":1,"98":2,"102":1,"105":1,"113":1}}],["thereof",{"2":{"39":1,"41":1}}],["therefore",{"2":{"22":1,"32":1,"41":1,"63":1}}],["there",{"2":{"7":1,"10":1,"13":4,"16":1,"22":1,"29":1,"30":2,"32":1,"34":1,"35":3,"38":3,"40":2,"41":1,"42":4,"43":2,"44":1,"46":2,"47":2,"48":2,"49":1,"50":1,"56":2,"59":1,"60":2,"62":1,"63":4,"64":1,"102":4}}],["their",{"2":{"4":1,"5":1,"12":1,"13":2,"17":1,"18":1,"19":1,"21":2,"22":1,"31":1,"32":1,"35":2,"36":1,"38":2,"39":1,"41":2,"42":2,"43":3,"45":1,"46":1,"56":1,"63":2,"74":1,"81":1,"92":1,"100":1,"105":1,"109":1,"114":1,"116":1}}],["the",{"0":{"5":1,"40":1,"44":1,"45":1,"46":1,"69":1,"70":1,"71":1,"86":1,"94":1,"95":1,"96":1,"97":1,"98":1,"99":1,"101":1,"102":1,"103":1},"1":{"41":1,"42":1,"43":1,"44":1,"45":1,"46":1,"47":1,"48":1,"49":1,"50":1,"51":1,"99":1,"100":1,"101":1,"102":1,"103":1},"2":{"1":7,"3":1,"4":6,"5":2,"6":3,"7":2,"8":1,"9":5,"10":5,"11":6,"12":6,"13":91,"14":4,"15":3,"16":2,"17":5,"18":11,"19":3,"20":12,"21":3,"22":6,"26":2,"27":2,"28":2,"29":3,"30":5,"31":5,"32":6,"33":12,"34":16,"35":21,"36":7,"37":5,"38":14,"39":18,"40":5,"41":51,"42":15,"43":7,"44":16,"45":3,"46":17,"47":14,"48":9,"49":5,"50":9,"51":1,"52":4,"53":3,"54":1,"56":3,"57":12,"58":5,"59":4,"60":14,"61":13,"62":28,"63":50,"64":9,"65":1,"67":2,"68":5,"69":10,"70":8,"71":4,"72":2,"73":1,"74":6,"79":1,"80":1,"81":2,"84":4,"85":2,"86":9,"87":5,"88":2,"89":3,"90":1,"91":4,"92":1,"93":1,"94":5,"95":7,"97":4,"98":3,"99":1,"100":2,"101":2,"102":1,"104":5,"105":14,"107":5,"109":1,"112":1,"113":2,"114":3,"117":4,"118":2,"119":1}}],["oil",{"2":{"63":1}}],["oidc",{"2":{"15":1}}],["oom",{"2":{"62":3}}],["oscillating",{"2":{"62":1}}],["ostensibly",{"2":{"41":1}}],["okay",{"2":{"57":1,"59":1}}],["occur",{"2":{"48":1}}],["omega",{"2":{"41":1}}],["oxymoronic",{"2":{"41":1}}],["older",{"2":{"63":2,"67":1}}],["old",{"2":{"39":1,"63":2}}],["oauth",{"2":{"15":1}}],["ought",{"2":{"39":1,"44":1}}],["our",{"2":{"13":1,"49":1,"68":1,"101":1}}],["outlining",{"2":{"75":1}}],["outfits",{"2":{"69":1}}],["output",{"2":{"13":1}}],["out",{"2":{"1":1,"4":2,"10":1,"13":4,"18":1,"22":1,"30":1,"34":1,"35":1,"36":1,"39":1,"53":1,"56":1,"61":1,"63":2,"89":1,"102":1,"114":1}}],["obvious",{"2":{"63":1,"74":1}}],["obey",{"2":{"57":1}}],["objective",{"2":{"45":1}}],["objects",{"2":{"13":3}}],["observed",{"2":{"41":1}}],["obtained",{"2":{"2":1}}],["opus",{"2":{"67":1}}],["opposed",{"2":{"63":1}}],["opposite",{"2":{"61":1}}],["opposing",{"2":{"52":1}}],["opponent",{"2":{"13":2}}],["opponents",{"2":{"13":3}}],["opinions",{"2":{"52":1}}],["opinion",{"2":{"49":1,"61":1,"63":1,"69":1}}],["opinionated",{"2":{"38":1,"45":1}}],["optispeech",{"2":{"86":1}}],["opti",{"0":{"85":1},"1":{"86":1,"87":1},"2":{"80":1,"82":1,"85":2}}],["option",{"2":{"62":1}}],["options",{"2":{"13":1,"47":1,"102":1}}],["optimal",{"2":{"42":1,"62":1,"63":1}}],["optimizing",{"2":{"42":1}}],["optimization",{"2":{"42":1,"47":2}}],["optimized",{"2":{"36":1}}],["opens",{"2":{"13":1}}],["open",{"0":{"84":1},"2":{"1":1,"8":1,"9":1,"10":1,"13":1,"24":1,"27":1,"31":1,"75":1,"77":1,"88":1,"91":1,"93":1,"111":1,"114":1}}],["owns",{"2":{"20":1}}],["owners",{"2":{"21":1}}],["ownership",{"2":{"12":1}}],["owner",{"2":{"15":1,"18":1,"21":1}}],["owned",{"2":{"13":1}}],["own",{"2":{"4":2,"17":1,"39":1,"40":1,"41":1,"42":1,"52":1,"57":1,"81":1,"92":1,"97":1,"114":1}}],["org",{"2":{"79":1}}],["organized",{"2":{"13":1}}],["oriented",{"2":{"48":1,"49":1}}],["originally",{"2":{"85":1}}],["original",{"0":{"86":1},"2":{"20":2,"63":4,"105":1}}],["originated",{"2":{"19":1}}],["or",{"2":{"2":2,"7":3,"9":1,"10":1,"13":4,"14":1,"18":4,"19":4,"21":4,"22":1,"26":1,"30":3,"31":3,"32":3,"34":2,"35":7,"36":2,"39":3,"40":2,"41":14,"42":3,"45":1,"47":1,"48":2,"53":1,"57":1,"58":1,"60":1,"61":1,"62":3,"63":6,"64":1,"90":2,"91":1,"95":1,"98":1,"99":1,"100":1,"117":1,"118":1}}],["order",{"0":{"89":1},"2":{"2":1,"62":3,"89":1,"90":1,"107":1,"108":1}}],["online",{"2":{"18":2,"39":1}}],["only",{"2":{"3":1,"13":1,"18":3,"20":1,"22":2,"34":1,"41":2,"42":2,"43":1,"48":1,"62":1,"63":1,"67":2,"72":1,"89":1,"91":1,"104":1}}],["once",{"2":{"13":1,"31":1,"36":1,"62":1,"63":2,"69":1}}],["on",{"2":{"1":1,"2":1,"4":1,"5":1,"9":1,"10":2,"13":6,"15":1,"17":3,"18":1,"22":2,"27":1,"31":1,"32":4,"33":2,"35":2,"38":4,"39":3,"40":2,"41":7,"42":2,"43":1,"44":2,"46":3,"47":1,"48":1,"50":3,"53":1,"56":1,"57":1,"58":1,"60":3,"61":3,"62":1,"63":13,"64":1,"68":2,"69":3,"81":2,"84":1,"85":1,"86":1,"88":1,"89":3,"90":2,"91":1,"92":1,"94":2,"96":1,"97":1,"100":1,"102":1,"104":3,"105":1,"113":1,"114":5,"115":1,"117":2,"118":3,"120":1,"121":1}}],["ones",{"2":{"31":1,"41":1,"53":1,"63":2}}],["one",{"2":{"1":1,"13":2,"15":1,"20":1,"34":1,"38":1,"41":1,"42":1,"46":1,"56":2,"60":1,"61":1,"68":1,"69":1,"74":1,"90":1,"91":1,"92":2,"94":1,"113":1}}],["otherwise",{"2":{"18":1,"48":1,"49":1}}],["others",{"2":{"4":1,"38":1}}],["other",{"0":{"51":1,"82":1},"2":{"1":1,"3":1,"7":1,"13":1,"19":1,"20":1,"21":1,"23":1,"30":4,"31":1,"34":2,"35":2,"38":2,"40":2,"41":3,"42":3,"44":1,"45":1,"46":1,"48":1,"49":1,"52":2,"53":1,"57":2,"58":1,"61":1,"62":1,"63":3,"64":2,"69":2,"74":3,"98":1,"99":2,"100":2,"102":1,"105":1,"113":3,"117":1}}],["oftentimes",{"2":{"41":1,"46":1}}],["often",{"2":{"31":1,"32":2,"34":1,"35":5,"38":1,"41":2,"42":4,"43":1,"47":2,"48":2,"50":1,"57":1,"62":1,"104":1}}],["offense",{"2":{"62":1}}],["offers",{"2":{"57":1,"115":1}}],["offer",{"2":{"19":1,"41":1,"58":1}}],["official",{"2":{"13":1}}],["off",{"2":{"4":1,"13":2,"59":1,"63":1,"70":1,"88":1}}],["of",{"0":{"71":1},"2":{"1":6,"2":2,"3":1,"4":1,"5":1,"6":1,"7":4,"9":3,"10":2,"12":4,"13":22,"14":3,"17":4,"18":5,"21":3,"22":2,"23":2,"26":3,"27":1,"28":1,"29":2,"30":2,"31":3,"32":8,"33":6,"34":8,"35":16,"36":5,"37":1,"38":12,"39":11,"40":3,"41":27,"42":12,"43":8,"44":11,"45":4,"46":10,"47":11,"48":7,"49":2,"50":5,"51":3,"52":1,"53":2,"56":3,"57":2,"58":5,"59":2,"60":12,"61":8,"62":7,"63":22,"64":7,"65":1,"67":2,"68":4,"69":6,"70":3,"71":1,"72":2,"74":1,"81":1,"86":2,"87":1,"88":1,"89":2,"90":4,"91":1,"94":2,"95":4,"97":2,"100":1,"101":1,"102":3,"104":4,"105":10,"107":2,"109":1,"113":3,"114":2,"118":2}}],["overwhelming",{"2":{"113":1}}],["overhead",{"2":{"105":1}}],["overrun",{"2":{"92":1}}],["overall",{"2":{"39":1}}],["overcoming",{"2":{"35":1}}],["overlap",{"2":{"35":1,"42":1,"43":1,"49":1}}],["overuses",{"2":{"7":1}}],["over",{"2":{"1":1,"2":1,"12":1,"13":2,"35":2,"40":1,"41":1,"43":1,"51":1,"60":1,"62":1,"63":2}}],["p",{"2":{"67":1}}],["psychology",{"2":{"59":1}}],["petnames",{"2":{"18":1}}],["people",{"0":{"102":1},"2":{"17":1,"18":3,"21":1,"33":1,"34":2,"35":3,"40":1,"41":1,"45":1,"46":1,"59":1,"89":1,"92":1,"100":1,"102":2,"105":1,"114":1}}],["period",{"2":{"92":1}}],["permanently",{"2":{"92":1}}],["permission",{"2":{"21":2}}],["per",{"2":{"50":1}}],["percentage",{"2":{"46":1}}],["perceived",{"2":{"39":1}}],["persists",{"2":{"34":1}}],["perspective",{"2":{"33":1}}],["person",{"2":{"18":1,"57":2,"92":1}}],["personally",{"2":{"34":1,"39":1}}],["personalized",{"2":{"2":1}}],["personal",{"0":{"79":1,"100":1},"1":{"101":1},"2":{"2":3,"10":2,"14":1,"38":1,"40":1,"79":1,"98":2,"113":1,"114":1,"118":1}}],["performance",{"2":{"105":2}}],["performing",{"2":{"42":1}}],["perform",{"2":{"35":1,"42":1}}],["performs",{"2":{"13":1,"62":1}}],["perfectly",{"2":{"30":1}}],["perfect",{"2":{"30":1,"40":1}}],["perhaps",{"2":{"20":1,"21":1,"22":2,"64":1,"70":1,"94":1}}],["photo",{"2":{"116":1}}],["phone",{"2":{"30":1}}],["phrases",{"2":{"42":1}}],["physical",{"2":{"39":1,"89":2}}],["physics",{"2":{"13":1,"30":1}}],["philosophies",{"2":{"38":1}}],["philosophy",{"2":{"2":1}}],["pushed",{"2":{"104":1}}],["pushes",{"2":{"43":1}}],["push",{"2":{"104":1}}],["punch",{"2":{"70":1}}],["punishes",{"2":{"62":1}}],["purchasing",{"2":{"90":1}}],["purchaseable",{"2":{"78":1}}],["purchased",{"2":{"62":1}}],["purchases",{"0":{"62":1},"2":{"62":4,"64":1,"90":2}}],["purchase",{"2":{"47":1,"48":1,"62":5,"63":1,"64":3}}],["purposes",{"2":{"86":1}}],["purpose",{"2":{"60":1}}],["purposefully",{"2":{"45":1}}],["pure",{"2":{"47":1}}],["put",{"2":{"39":1,"42":1,"56":1,"62":2,"105":1}}],["puts",{"2":{"13":1}}],["puzzle",{"2":{"36":1}}],["pull",{"2":{"21":1}}],["publish",{"2":{"20":1}}],["publicly",{"2":{"19":1,"21":1,"56":1,"59":1,"84":1,"120":1}}],["publickey",{"2":{"18":5}}],["public",{"2":{"15":1,"18":1,"20":1,"21":6,"22":2}}],["puppet",{"2":{"4":1,"13":1}}],["puppets",{"2":{"4":2}}],["plenty",{"2":{"61":1,"63":1,"102":1}}],["please",{"2":{"13":1}}],["platformers",{"2":{"63":1}}],["platformer",{"2":{"63":1}}],["plainly",{"2":{"38":1,"41":1}}],["plans",{"2":{"105":1,"114":2}}],["planar",{"0":{"88":1},"2":{"80":1,"81":1,"84":1,"91":2}}],["plane",{"2":{"47":1}}],["plan",{"2":{"17":1}}],["placed",{"2":{"22":1,"40":1,"86":1}}],["placeholder",{"2":{"16":1}}],["place",{"2":{"13":1}}],["placement",{"2":{"13":1}}],["playthroughs",{"2":{"68":1}}],["playable",{"2":{"34":1,"70":1}}],["playstyle",{"2":{"38":1}}],["plays",{"2":{"31":1,"74":1}}],["playerbase",{"2":{"42":1}}],["player",{"2":{"13":9,"34":3,"38":2,"39":1,"40":1,"42":2,"43":1,"46":2,"47":1,"48":5,"50":1,"57":2,"60":1,"61":2,"62":3,"63":5,"68":1,"121":1}}],["players",{"0":{"31":1,"33":1},"1":{"34":1,"35":1,"36":1,"37":1,"38":1,"39":1},"2":{"13":4,"29":1,"31":2,"32":2,"33":1,"34":2,"35":2,"36":1,"37":1,"38":8,"39":1,"41":1,"46":1,"54":1,"58":2,"60":3,"63":4,"89":1}}],["played",{"2":{"11":1,"31":1,"34":1,"35":1,"67":1,"70":1,"72":1}}],["playing",{"2":{"11":1,"35":3,"38":3,"41":3,"68":1}}],["play",{"0":{"108":1},"2":{"1":1,"13":3,"27":1,"31":2,"34":1,"35":5,"36":1,"38":1,"39":1,"40":1,"41":1,"46":1,"68":1,"72":2,"73":1,"81":3,"88":1}}],["picture",{"2":{"115":1}}],["pick",{"2":{"12":1,"92":2}}],["pioneers",{"0":{"88":1},"2":{"80":1,"81":1,"84":1,"91":2}}],["piece",{"2":{"57":1,"61":1}}],["pieces",{"2":{"1":1}}],["pins",{"2":{"32":1,"89":1}}],["praising",{"2":{"38":1}}],["practices",{"2":{"97":1}}],["practice",{"2":{"12":1,"57":1,"74":1}}],["prudent",{"2":{"35":1,"41":1}}],["premium",{"0":{"90":1},"2":{"74":1,"78":1,"89":1,"107":1}}],["premise",{"2":{"42":1}}],["previous",{"2":{"63":1}}],["previously",{"2":{"18":2}}],["predominant",{"2":{"47":1}}],["predatory",{"2":{"35":1}}],["precludes",{"2":{"43":1}}],["pretty",{"2":{"39":1,"42":1,"64":1,"102":1}}],["preoccupied",{"2":{"39":1}}],["prefer",{"2":{"58":1}}],["preferences",{"2":{"38":1,"40":1,"57":1}}],["preferred",{"2":{"21":1}}],["press",{"2":{"62":1}}],["prestiges",{"2":{"63":1}}],["prestige",{"2":{"41":1,"63":2}}],["president",{"2":{"18":1}}],["presents",{"2":{"47":1}}],["presentation",{"2":{"47":1}}],["present",{"2":{"13":1,"44":1}}],["pre",{"0":{"89":1},"2":{"15":1,"62":1,"89":1,"90":1,"107":1}}],["primordia",{"2":{"91":1}}],["primarily",{"2":{"89":1}}],["prices",{"2":{"107":1}}],["price",{"2":{"90":1,"107":3}}],["printing",{"2":{"41":1}}],["principles",{"2":{"38":1}}],["prioritize",{"2":{"57":1}}],["prioritized",{"2":{"13":1}}],["priority",{"2":{"35":1,"41":1}}],["privileges",{"2":{"30":1}}],["private",{"2":{"15":1,"18":3,"19":1,"104":1}}],["privacy",{"2":{"12":1}}],["procedurally",{"2":{"105":1}}],["process",{"2":{"41":1,"43":1,"56":1,"104":1}}],["pronounced",{"2":{"105":1}}],["prone",{"2":{"35":3,"74":1}}],["providing",{"2":{"74":1}}],["provide",{"2":{"46":1,"60":1,"62":2}}],["providers",{"2":{"15":2}}],["prominently",{"2":{"59":1}}],["prose",{"2":{"52":1}}],["product",{"2":{"116":1}}],["production",{"2":{"39":2,"42":1,"87":1}}],["productive",{"2":{"35":1}}],["producer",{"2":{"13":1}}],["produce",{"2":{"2":1}}],["properly",{"2":{"38":1}}],["property",{"2":{"20":1}}],["propose",{"2":{"44":1}}],["proposes",{"2":{"28":1,"42":1}}],["proposal",{"2":{"28":1,"96":1,"117":1}}],["profit",{"2":{"41":2,"108":1}}],["profile",{"2":{"18":1}}],["profectus",{"0":{"91":1},"2":{"1":2,"67":1,"80":1,"82":1,"84":1,"88":2,"91":3}}],["probably",{"2":{"15":1,"22":1,"36":1,"42":1,"46":1,"47":1,"48":1,"49":1,"63":1}}],["problem",{"2":{"12":1,"17":1,"40":1,"41":1,"43":2,"57":2,"62":1,"63":1}}],["problems",{"0":{"22":1},"2":{"6":1,"42":1,"47":2}}],["program",{"2":{"87":2}}],["programming",{"2":{"30":1,"31":1,"41":1}}],["programmer",{"2":{"13":2,"87":1}}],["programmers",{"2":{"13":1}}],["progresses",{"2":{"48":1}}],["progressively",{"2":{"50":1}}],["progressing",{"2":{"47":1}}],["progression",{"2":{"13":1,"34":10,"35":1,"37":1,"42":2,"43":3,"49":1,"62":1,"63":3,"90":1}}],["progress",{"2":{"34":1,"35":3,"36":1,"42":1,"47":1,"48":2,"50":1,"61":1,"62":1,"63":5}}],["projectors",{"2":{"68":1}}],["project",{"0":{"86":1},"2":{"4":2,"5":1,"13":2,"81":1,"85":1,"86":1,"114":1,"118":1,"121":1}}],["projects",{"0":{"80":1},"1":{"81":1,"82":1},"2":{"1":1,"4":1,"5":1,"10":2,"11":1,"13":1,"27":1,"65":1,"67":1,"84":1,"85":1,"88":1,"91":1,"105":1}}],["protocols",{"2":{"3":1,"17":1}}],["protocol",{"2":{"0":1,"3":2,"8":1,"20":2,"23":1,"76":1,"83":1,"93":1}}],["pollinating",{"2":{"113":1}}],["polynomial",{"2":{"50":2}}],["power",{"2":{"73":1}}],["powers",{"2":{"69":2}}],["powerful",{"2":{"9":1}}],["potentially",{"2":{"56":1,"61":1}}],["poorly",{"2":{"38":1}}],["points",{"2":{"52":1}}],["pointed",{"2":{"39":1}}],["point",{"2":{"35":1,"36":1,"39":2,"42":1,"43":1,"46":1,"61":1,"62":1,"63":4,"64":1,"115":1}}],["popularized",{"2":{"95":1}}],["popularity",{"2":{"46":1}}],["popular",{"2":{"32":2,"40":2,"41":1,"44":1,"45":1,"50":1,"51":1,"53":1,"60":1,"61":1,"90":1}}],["populated",{"2":{"13":2}}],["positive",{"2":{"56":1,"58":1,"59":3}}],["possibly",{"2":{"102":1}}],["possible",{"2":{"13":1,"34":1,"35":2,"41":1,"46":1,"60":1}}],["possibility",{"2":{"47":1}}],["poses",{"2":{"40":1}}],["posted",{"2":{"31":1}}],["poster",{"2":{"19":2,"20":2}}],["posts",{"2":{"21":1,"35":1,"77":1}}],["posting",{"2":{"20":1,"96":1}}],["post",{"2":{"20":1,"56":1,"68":1,"86":1}}],["portrays",{"2":{"69":1}}],["portray",{"2":{"41":2}}],["portraits",{"2":{"13":2}}],["ported",{"2":{"4":1,"13":1}}],["packed",{"2":{"109":1}}],["pax",{"2":{"68":1}}],["panel",{"2":{"47":1}}],["painting",{"2":{"39":1}}],["paid",{"2":{"32":1,"110":2,"114":1}}],["paying",{"2":{"35":1}}],["passion",{"2":{"59":2}}],["passionate",{"2":{"53":1}}],["passively",{"2":{"38":1}}],["passes",{"2":{"49":1,"89":1}}],["pass",{"2":{"22":1,"42":1,"49":1}}],["password",{"2":{"19":1}}],["paperclips",{"2":{"45":1,"46":1}}],["paper",{"2":{"18":2,"85":1}}],["parody",{"2":{"41":2}}],["parodies",{"2":{"41":7}}],["parallelization",{"2":{"105":1}}],["parasocial",{"2":{"94":1}}],["paragraph",{"2":{"63":1}}],["paradigm",{"0":{"46":1},"2":{"37":1,"46":10,"49":1}}],["parable",{"2":{"11":2}}],["parent",{"2":{"20":2,"21":1}}],["partially",{"2":{"92":1}}],["participating",{"2":{"118":1}}],["participate",{"2":{"32":1}}],["particular",{"2":{"39":1,"41":1,"42":1}}],["particularly",{"2":{"35":1,"41":1,"62":1}}],["partnership",{"2":{"86":1}}],["parts",{"2":{"13":1,"41":1,"60":1,"63":2}}],["part",{"2":{"7":1,"26":1,"32":1,"34":1,"35":1,"39":1,"43":1,"63":1,"70":1,"95":2}}],["pattern",{"2":{"9":2,"105":1}}],["palette",{"2":{"9":2}}],["palettes",{"0":{"9":1},"2":{"2":1,"9":3,"75":1}}],["pals",{"2":{"4":1}}],["pages",{"2":{"20":1,"31":1,"81":1,"98":1,"100":3,"102":1,"104":3}}],["page",{"2":{"1":1,"5":1,"27":1,"30":1,"41":1,"47":1,"56":1,"60":1,"81":1,"88":1,"91":1,"102":1,"115":2}}],["mtx",{"0":{"78":1},"2":{"90":1,"107":1,"108":1,"110":1}}],["mbin",{"0":{"77":1},"2":{"23":1,"65":1,"77":1,"84":1}}],["mutually",{"2":{"47":1}}],["multiplayer",{"2":{"120":1}}],["multiply",{"2":{"64":1}}],["multiplier",{"2":{"62":1}}],["multipliers",{"2":{"62":6}}],["multiple",{"2":{"22":1,"62":1,"113":2}}],["multitasking",{"2":{"35":1}}],["must",{"2":{"34":1,"44":1,"48":1,"63":1}}],["music",{"2":{"30":1}}],["much",{"2":{"13":2,"32":1,"33":1,"36":1,"38":2,"41":2,"46":1,"58":1,"59":1,"60":1,"62":3,"63":1,"69":1,"70":1,"107":1}}],["mindless",{"2":{"61":1}}],["mind",{"2":{"52":1,"57":1,"59":1,"63":1,"69":1}}],["minimize",{"2":{"61":1}}],["minigame",{"2":{"50":1}}],["minion",{"2":{"50":1}}],["mine",{"2":{"38":1,"81":1}}],["misplaying",{"2":{"47":1}}],["missile",{"2":{"13":1}}],["microtransactions",{"2":{"41":1}}],["micro",{"2":{"35":1}}],["might",{"2":{"34":2,"38":1,"39":1,"42":1,"46":2,"113":1}}],["mirrors",{"2":{"33":1}}],["middleground",{"2":{"14":1}}],["middle",{"2":{"13":1}}],["midjourney",{"2":{"2":1}}],["marginalia",{"2":{"99":1}}],["marketers",{"2":{"95":1,"98":1}}],["market",{"2":{"40":1}}],["magnum",{"2":{"67":1}}],["maggieappleton",{"2":{"14":1}}],["maggie",{"2":{"9":1,"95":1}}],["machines",{"2":{"63":1}}],["max",{"2":{"62":3,"69":4,"74":1}}],["majority",{"2":{"41":1}}],["major",{"2":{"39":1,"69":2}}],["mastered",{"2":{"36":1}}],["mastodon",{"2":{"17":1}}],["maintainability",{"2":{"87":1}}],["maintains",{"2":{"10":2}}],["mainstream",{"2":{"41":2}}],["mainly",{"2":{"32":2,"62":1}}],["making",{"0":{"53":1,"55":1},"2":{"13":1,"17":1,"30":2,"34":1,"35":2,"36":1,"42":1,"45":2,"53":1,"58":1,"61":1,"62":2,"74":1,"80":1,"91":2,"100":1,"102":1,"105":1}}],["makes",{"2":{"30":1,"31":1,"33":1,"34":1,"38":1,"40":1,"41":1,"42":2,"70":1}}],["make",{"0":{"30":1},"2":{"9":1,"10":1,"12":1,"13":2,"21":1,"30":4,"32":1,"34":2,"35":1,"38":1,"39":1,"40":1,"41":2,"43":2,"45":2,"60":1,"61":1,"63":1,"64":1,"89":1,"102":3,"104":1,"107":3,"109":1,"114":1}}],["managed",{"2":{"102":1}}],["manages",{"2":{"63":1}}],["management",{"2":{"47":1,"49":1}}],["managers",{"2":{"13":1}}],["manual",{"2":{"42":1}}],["manually",{"2":{"13":1}}],["manipulation",{"2":{"41":1}}],["manipulative",{"2":{"41":3}}],["manipulating",{"2":{"35":1,"41":4}}],["manipulates",{"2":{"41":2}}],["manipulate",{"2":{"41":1}}],["manner",{"2":{"25":1}}],["many",{"2":{"2":1,"9":2,"13":2,"17":1,"32":1,"33":1,"34":4,"38":1,"39":2,"40":1,"41":1,"43":1,"44":1,"46":3,"56":1,"61":1,"63":1,"64":1,"92":1}}],["matter",{"2":{"59":1}}],["material",{"2":{"22":2,"41":1,"52":1}}],["matching",{"2":{"21":1}}],["matches",{"2":{"20":1}}],["math",{"2":{"13":1}}],["matrix",{"0":{"76":1},"2":{"8":1,"10":2,"12":1,"76":1,"93":1,"113":1}}],["maybe",{"2":{"43":1}}],["may",{"2":{"9":1,"19":2,"35":4,"36":2,"39":1,"41":3,"46":1,"48":3,"50":1,"51":1,"58":1,"59":1,"61":1,"63":2,"64":1,"98":1}}],["made",{"2":{"1":1,"2":1,"13":3,"14":1,"20":1,"21":1,"33":2,"34":2,"39":3,"49":1,"52":1,"53":2,"57":1,"62":1,"64":3,"65":1,"67":1,"68":2,"91":2,"105":3}}],["meet",{"2":{"70":1}}],["measure",{"2":{"60":1}}],["mean",{"2":{"40":1}}],["meaning",{"2":{"39":1,"48":1}}],["meaningfully",{"2":{"61":1}}],["meaningful",{"2":{"37":1,"62":3}}],["meantime",{"2":{"4":1}}],["means",{"2":{"2":1,"41":2,"42":1,"43":1,"44":1,"47":1,"60":1,"63":3}}],["methods",{"2":{"92":1}}],["method",{"2":{"62":1}}],["met",{"2":{"61":1}}],["metric",{"2":{"41":1}}],["meta",{"2":{"34":6,"43":2,"49":1}}],["mentioned",{"2":{"43":1,"63":1}}],["mentions",{"2":{"1":1,"27":1,"88":1}}],["mental",{"2":{"40":1,"62":1}}],["merit",{"0":{"39":1},"2":{"39":5}}],["merely",{"2":{"19":1}}],["melee",{"2":{"38":1}}],["mechanically",{"2":{"45":1}}],["mechanic",{"2":{"38":3,"40":2,"41":1,"46":3,"48":1,"50":4,"60":2,"61":1,"63":8}}],["mechanics",{"2":{"34":1,"39":1,"40":1,"42":1,"43":1,"46":2,"48":1,"50":1,"58":1,"63":3}}],["mechana",{"2":{"13":1}}],["me",{"2":{"33":1,"34":1,"38":1,"39":1,"65":1,"71":1}}],["messages",{"2":{"17":1,"19":6,"20":4,"21":9,"22":7,"118":1}}],["message",{"2":{"10":1,"18":1,"19":2,"20":7,"21":3,"22":2}}],["messaging",{"2":{"8":1,"76":1}}],["media",{"0":{"92":1},"2":{"0":1,"3":1,"7":1,"10":2,"12":1,"16":1,"17":2,"23":1,"83":1,"92":3,"98":1,"119":1}}],["m",{"2":{"1":1,"13":1,"18":1,"38":4,"39":1,"40":1,"45":1,"46":1,"60":1,"61":1,"62":2,"63":1,"74":1,"104":1,"115":1,"116":1,"117":1,"118":3,"119":1,"120":1,"121":1}}],["mockup",{"2":{"118":1}}],["mocking",{"2":{"38":1}}],["moment",{"2":{"46":1}}],["motivated",{"2":{"59":1}}],["motivation",{"2":{"48":1}}],["motivations",{"2":{"35":1}}],["motivating",{"2":{"31":1}}],["motive",{"2":{"41":1}}],["mobile",{"2":{"32":7,"41":1}}],["movie",{"2":{"39":1}}],["moving",{"2":{"13":1,"30":1,"118":1}}],["move",{"2":{"4":1,"13":1,"62":1,"71":1}}],["moddable",{"2":{"105":1}}],["modding",{"2":{"67":1,"91":1}}],["modifiers",{"2":{"63":1}}],["modifier",{"2":{"46":1}}],["modify",{"2":{"13":1,"84":1}}],["model",{"2":{"86":1}}],["models",{"2":{"2":2}}],["moderate",{"2":{"113":1}}],["moderator",{"2":{"21":1,"22":1}}],["moderation",{"0":{"21":1},"2":{"21":1,"22":1,"41":1,"92":1}}],["modern",{"2":{"10":1,"41":1,"61":1,"87":1,"113":1}}],["mode",{"2":{"13":3}}],["moran",{"2":{"4":1}}],["more",{"2":{"1":1,"2":1,"5":1,"10":1,"13":1,"17":1,"30":1,"34":2,"35":4,"36":3,"38":5,"39":2,"40":2,"41":2,"42":3,"44":2,"46":1,"48":1,"50":3,"58":1,"59":1,"61":2,"62":2,"63":6,"64":1,"69":2,"74":1,"81":2,"87":2,"89":1,"91":1,"105":2,"107":1}}],["monetized",{"2":{"32":2}}],["monetization",{"0":{"32":1,"106":1,"110":1},"1":{"107":1,"108":1,"109":1,"110":1},"2":{"4":1,"32":3,"74":1,"78":1,"89":1,"109":1}}],["money",{"2":{"13":2,"18":1,"32":1,"35":1,"41":1,"50":1,"74":2,"107":2}}],["months",{"2":{"1":1}}],["month",{"2":{"1":1}}],["mostly",{"2":{"31":1,"40":1,"60":1,"107":1}}],["most",{"2":{"1":1,"13":1,"18":2,"35":3,"39":3,"40":2,"41":1,"42":3,"44":1,"47":2,"53":2,"57":1,"60":1,"62":1,"63":1,"65":1,"67":1,"81":1,"104":1,"113":1}}],["myriad",{"2":{"62":1}}],["mystery",{"2":{"46":1}}],["myself",{"2":{"1":1,"53":1,"60":1,"79":1,"105":1}}],["my",{"0":{"79":1,"80":1,"87":1},"1":{"81":1,"82":1},"2":{"1":2,"4":1,"5":1,"13":2,"18":3,"27":3,"33":1,"38":1,"40":3,"41":2,"45":1,"49":1,"52":1,"53":1,"58":1,"60":1,"63":1,"65":1,"67":2,"68":1,"69":2,"70":1,"81":1,"85":1,"87":1,"88":1,"91":1,"92":1,"94":1,"98":1,"104":5,"105":1,"114":1,"115":1,"116":1}}],["iroh",{"2":{"114":2}}],["irl",{"2":{"59":1}}],["io",{"2":{"81":1}}],["ignores",{"2":{"63":1}}],["ignored",{"2":{"21":1}}],["ip",{"2":{"62":6}}],["ii",{"2":{"50":1}}],["illustrate",{"2":{"52":1}}],["illustrated",{"2":{"42":1}}],["illegal",{"2":{"22":2}}],["iap",{"2":{"32":1}}],["iaps",{"2":{"32":1}}],["imagine",{"2":{"62":1}}],["image",{"2":{"20":1}}],["immediately",{"2":{"64":1}}],["immersing",{"2":{"38":1}}],["immune",{"2":{"56":1}}],["impacts",{"2":{"89":1}}],["impact",{"2":{"46":2,"62":1,"64":1}}],["implications",{"2":{"63":1,"114":1}}],["implies",{"2":{"40":1,"42":1}}],["implying",{"2":{"42":1}}],["imply",{"2":{"40":1}}],["implement",{"2":{"30":1,"63":1}}],["implemented",{"2":{"20":1}}],["implementation",{"2":{"17":1}}],["implementations",{"2":{"15":1,"23":1}}],["implementing",{"2":{"16":1,"23":1,"30":1,"117":1}}],["imperfectly",{"2":{"38":1}}],["impossible",{"2":{"34":1}}],["important",{"2":{"18":2,"34":1,"40":1,"56":1,"58":1,"94":2}}],["improve",{"2":{"87":1}}],["improvement",{"2":{"35":1,"57":1}}],["improved",{"2":{"10":1}}],["improving",{"2":{"12":1,"36":1,"57":3,"87":1,"119":1}}],["idling",{"2":{"50":1}}],["idler",{"2":{"41":2}}],["idlers",{"0":{"41":1}}],["idle",{"2":{"32":3,"35":1,"41":3,"45":1,"50":3,"61":1}}],["ids",{"2":{"21":1}}],["id",{"2":{"19":2,"20":4}}],["identical",{"2":{"22":1}}],["identified",{"2":{"22":1}}],["identities",{"2":{"18":3,"102":1,"114":1}}],["identity",{"0":{"15":1,"18":1},"2":{"10":2,"12":1,"15":4,"17":1,"18":3,"19":1,"22":1,"57":1,"65":1,"92":1,"114":2}}],["ideally",{"2":{"102":1}}],["ideal",{"2":{"92":1}}],["ideals",{"2":{"44":1}}],["ideas",{"2":{"17":1,"63":1,"97":1}}],["idea",{"2":{"1":1,"17":1,"41":1,"64":1}}],["ivy",{"0":{"66":1},"2":{"11":3,"66":1,"112":1}}],["if",{"2":{"7":1,"13":3,"17":1,"18":4,"20":1,"21":2,"22":2,"30":2,"31":1,"32":1,"34":1,"35":3,"38":2,"39":2,"40":1,"41":3,"42":2,"43":2,"45":1,"47":1,"48":1,"49":1,"53":1,"57":3,"60":1,"61":1,"62":1,"63":5,"64":3}}],["i",{"0":{"53":1},"2":{"1":4,"4":4,"9":1,"11":1,"13":10,"18":3,"27":1,"32":2,"33":8,"34":8,"35":1,"38":10,"39":8,"40":6,"41":7,"42":2,"43":2,"44":2,"45":5,"46":4,"47":1,"49":2,"50":1,"52":1,"53":4,"56":3,"60":4,"61":4,"62":10,"63":3,"64":1,"67":2,"68":5,"69":3,"70":3,"71":2,"72":2,"73":1,"74":4,"80":1,"81":1,"85":1,"91":1,"96":1,"104":3,"105":5,"109":1,"114":1,"115":1,"116":3,"117":3,"118":3,"119":1,"120":1,"121":1}}],["innovative",{"2":{"63":1}}],["infinite",{"2":{"105":1}}],["infinity",{"2":{"62":3}}],["influencers",{"2":{"92":1}}],["inflated",{"2":{"60":1}}],["inflating",{"2":{"60":1,"62":1}}],["infrequent",{"2":{"61":1}}],["information",{"2":{"7":1,"13":2,"14":1,"18":1,"25":1,"26":1}}],["inexperienced",{"2":{"56":1}}],["inevitably",{"2":{"20":1,"56":1,"63":1}}],["inherently",{"2":{"41":2}}],["inherit",{"2":{"36":1}}],["investment",{"2":{"89":1}}],["invested",{"2":{"70":1}}],["inventory",{"2":{"13":1}}],["invalidate",{"2":{"64":1}}],["involved",{"2":{"87":1,"105":1}}],["involves",{"2":{"86":1}}],["involve",{"2":{"42":1}}],["involvement",{"2":{"33":1}}],["initial",{"2":{"22":1,"31":1,"59":1}}],["incoming",{"2":{"118":1}}],["incomplete",{"2":{"52":1}}],["inconsistencies",{"2":{"70":1}}],["including",{"2":{"20":1,"41":1,"61":1,"105":1}}],["included",{"2":{"89":1}}],["includes",{"2":{"36":1,"87":1}}],["include",{"2":{"10":1,"20":1,"46":1,"50":4,"105":1}}],["incredible",{"2":{"35":1}}],["incredibly",{"2":{"13":1,"30":1,"31":1,"32":1,"35":1,"38":1,"58":1,"62":1,"74":1,"102":1}}],["increlution",{"2":{"32":1,"45":1,"46":1,"50":1}}],["increasing",{"2":{"39":2,"41":1,"42":2,"46":1}}],["increasingly",{"2":{"9":1,"50":1,"63":1}}],["increase",{"2":{"34":1,"63":1}}],["increases",{"2":{"34":1,"63":2}}],["increased",{"2":{"12":1,"34":1}}],["incrementalness",{"2":{"44":1,"45":1,"46":1}}],["incrementals",{"0":{"29":1,"30":1,"33":1,"40":1,"41":1,"42":1,"43":1,"49":1,"52":1,"56":1,"60":1},"1":{"30":1,"31":1,"32":1,"34":1,"35":1,"36":1,"37":1,"38":1,"39":1,"41":1,"42":1,"43":1,"44":2,"45":2,"46":2,"47":2,"48":2,"49":2,"50":1,"51":1,"53":1,"54":1,"55":1,"57":1,"58":1,"59":1,"61":1,"62":1,"63":1,"64":1},"2":{"30":2,"32":1,"34":1,"38":1,"39":2,"41":2,"42":7,"43":4,"46":2,"47":4,"48":2,"54":4,"55":1}}],["incremental",{"0":{"1":1,"45":1,"55":1,"65":1,"119":1},"2":{"1":1,"8":1,"15":1,"23":1,"24":1,"27":1,"29":1,"30":1,"31":3,"32":3,"33":1,"34":3,"35":11,"36":1,"37":1,"38":3,"39":7,"40":8,"41":24,"42":12,"43":3,"44":1,"45":1,"46":4,"47":3,"48":6,"49":4,"50":3,"51":1,"52":3,"53":4,"56":2,"60":2,"61":1,"63":6,"65":2,"67":1,"77":1,"80":2,"81":1,"82":1,"84":1,"91":2,"93":1,"100":1,"105":3,"113":3,"119":1,"120":1,"121":1}}],["industry",{"2":{"109":1}}],["indeed",{"2":{"34":1,"35":1,"39":1}}],["indexable",{"2":{"10":1,"95":1}}],["indicator",{"2":{"46":1}}],["indicators",{"2":{"13":1}}],["indicate",{"2":{"20":2,"36":1,"46":1,"47":1}}],["indie",{"0":{"109":1},"2":{"66":1,"89":1,"101":1}}],["indieweb",{"0":{"96":1,"97":1,"117":1},"2":{"15":1,"20":1,"96":1,"97":1,"100":1,"104":1,"117":2}}],["indieauth",{"2":{"15":2}}],["individually",{"2":{"61":1}}],["individual",{"2":{"13":1,"14":1,"90":1,"98":2}}],["individuals",{"2":{"2":1,"98":1}}],["introduced",{"2":{"62":2,"63":1}}],["introducing",{"2":{"60":1,"63":1}}],["intrinsically",{"2":{"38":1}}],["into",{"2":{"4":2,"6":1,"7":1,"13":3,"29":1,"35":1,"39":2,"40":1,"41":2,"50":1,"51":1,"56":1,"59":1,"62":3,"90":1,"91":1,"115":1,"118":1}}],["intent",{"2":{"91":1}}],["intention",{"2":{"67":1}}],["intentionally",{"2":{"38":1}}],["intended",{"2":{"4":1,"38":3}}],["integrating",{"2":{"13":1}}],["integrate",{"2":{"10":1}}],["internet",{"2":{"95":1,"97":1,"101":1}}],["internalize",{"2":{"57":1}}],["internal",{"2":{"19":1}}],["interpret",{"2":{"57":1}}],["interpretation",{"0":{"44":1},"2":{"41":1,"42":1,"44":2,"49":3}}],["interchangeably",{"2":{"41":1}}],["interest",{"2":{"53":1,"56":1,"104":1}}],["interests",{"2":{"41":1}}],["interesting",{"2":{"33":1,"41":1,"51":1,"62":1,"63":1,"73":1}}],["interested",{"2":{"10":1,"41":1,"113":1}}],["interactive",{"2":{"52":2}}],["interactions",{"2":{"61":1,"63":1}}],["interaction",{"0":{"61":1},"1":{"62":1},"2":{"48":2,"61":2}}],["interacting",{"2":{"4":1,"47":1}}],["interacted",{"2":{"18":1}}],["interfere",{"2":{"13":1}}],["interface",{"2":{"13":1,"47":1,"87":1}}],["interfaces",{"2":{"9":1}}],["interviews",{"2":{"11":1}}],["intelligence",{"0":{"2":1},"2":{"9":1,"13":1}}],["insults",{"2":{"57":1}}],["insatiable",{"2":{"41":1}}],["institutes",{"2":{"86":1}}],["instinctively",{"2":{"35":1}}],["instructions",{"0":{"63":1},"2":{"63":1}}],["instead",{"2":{"34":1,"48":1,"57":1,"62":1,"63":3,"90":1,"105":1}}],["instance",{"2":{"17":1,"65":1,"92":3,"100":1}}],["instances",{"2":{"3":1,"17":1,"48":1,"114":1}}],["inspiration",{"0":{"17":1}}],["inspired",{"2":{"4":1}}],["inspector",{"2":{"13":1}}],["inspectors",{"2":{"13":1}}],["input",{"2":{"2":1,"86":1}}],["in",{"2":{"1":2,"2":1,"3":1,"4":3,"5":1,"9":2,"10":3,"12":1,"13":15,"14":1,"16":1,"18":1,"20":1,"21":2,"25":1,"29":2,"30":3,"31":3,"32":2,"34":8,"35":6,"36":1,"37":1,"38":6,"39":2,"40":2,"41":9,"42":3,"43":1,"46":5,"47":1,"48":4,"49":1,"50":3,"51":2,"53":2,"56":1,"57":2,"58":1,"59":3,"60":2,"61":5,"62":10,"63":10,"64":1,"67":2,"68":1,"69":3,"70":2,"78":1,"81":1,"85":1,"86":3,"87":2,"89":1,"90":1,"91":1,"98":2,"100":1,"102":1,"104":4,"105":3,"108":1,"113":1,"114":4,"115":1,"116":1}}],["item",{"2":{"90":1}}],["items",{"2":{"78":1,"90":1}}],["itrtg",{"2":{"50":1}}],["itch",{"2":{"31":1,"81":1}}],["itself",{"2":{"13":1,"18":1,"20":1,"30":1,"39":2,"40":1,"41":1,"59":1}}],["its",{"2":{"4":3,"7":1,"13":3,"19":1,"20":1,"32":1,"34":2,"38":1,"39":2,"40":2,"41":1,"44":2,"59":1,"69":1}}],["it",{"2":{"1":3,"4":4,"13":12,"17":1,"18":1,"20":2,"22":2,"26":1,"27":3,"28":2,"30":1,"31":2,"32":2,"33":4,"34":11,"35":10,"36":3,"38":7,"39":10,"40":7,"41":10,"42":6,"43":3,"44":3,"45":1,"46":6,"49":1,"52":2,"56":4,"57":3,"58":1,"59":4,"60":5,"61":5,"62":10,"63":16,"64":3,"67":1,"68":1,"69":2,"70":1,"71":1,"72":1,"73":1,"74":2,"87":1,"88":1,"89":2,"91":2,"94":1,"95":1,"104":1,"105":1,"112":1,"114":1,"117":1}}],["isn",{"2":{"34":2,"35":2,"38":1,"47":1,"49":1,"63":2,"64":1}}],["issues",{"2":{"10":1,"12":1,"28":1,"61":1,"70":1}}],["is",{"0":{"60":1,"68":1,"70":1,"72":1,"73":1,"74":1},"1":{"61":1,"62":1,"63":1,"64":1,"69":1,"70":1,"71":1,"72":1,"73":1,"74":1},"2":{"0":1,"1":1,"2":1,"3":2,"4":1,"7":2,"8":1,"9":1,"10":3,"13":19,"16":1,"17":2,"18":5,"20":2,"21":1,"22":3,"24":1,"26":2,"28":1,"30":2,"31":1,"32":2,"33":2,"34":9,"35":5,"36":2,"38":6,"39":6,"40":3,"41":13,"42":12,"44":4,"45":2,"46":4,"47":6,"48":4,"49":1,"50":2,"52":3,"54":1,"56":5,"57":3,"58":1,"59":2,"60":5,"61":7,"62":5,"63":20,"64":2,"65":1,"66":1,"67":1,"68":2,"69":2,"70":1,"74":3,"75":1,"76":1,"77":1,"81":1,"83":1,"86":2,"90":1,"91":2,"92":2,"93":1,"94":1,"95":3,"97":1,"98":1,"99":1,"101":1,"102":1,"104":2,"105":2,"106":1,"109":2,"111":1,"112":1,"114":1,"115":1,"121":1}}],["fps",{"2":{"105":1}}],["fly",{"2":{"45":1,"50":1}}],["flow",{"2":{"35":1}}],["flood",{"2":{"31":1}}],["flagged",{"2":{"20":1,"21":2}}],["flag",{"2":{"20":1}}],["flagship",{"2":{"116":1}}],["flags",{"2":{"13":1}}],["flashy",{"2":{"13":1}}],["flash",{"2":{"13":1,"50":1}}],["flip",{"2":{"13":1}}],["fidget",{"2":{"35":1}}],["fits",{"2":{"71":1}}],["fitting",{"2":{"69":1}}],["fit",{"2":{"28":1,"43":1}}],["filtering",{"2":{"22":1}}],["filters",{"2":{"19":1,"99":2}}],["filter",{"2":{"13":2}}],["file",{"2":{"13":1}}],["fields",{"2":{"13":1,"20":1}}],["field",{"2":{"13":2}}],["figured",{"2":{"36":1}}],["figure",{"2":{"13":1}}],["first",{"2":{"13":1,"27":2,"39":1,"62":1,"63":1,"68":1,"72":1,"112":1}}],["fine",{"2":{"32":1,"63":2}}],["finished",{"2":{"31":1}}],["finisher",{"2":{"13":2}}],["finally",{"2":{"63":1}}],["final",{"2":{"5":1,"13":1}}],["finding",{"2":{"9":1,"63":1}}],["find",{"0":{"31":1},"2":{"4":1,"34":1,"41":1,"51":1,"57":1,"60":1,"74":1,"81":1}}],["folder",{"2":{"105":1}}],["fold",{"2":{"50":1}}],["following",{"0":{"63":1},"2":{"63":1,"118":1}}],["followed",{"2":{"21":1}}],["follow",{"2":{"12":1,"22":1,"46":1,"74":1,"99":1}}],["focus",{"2":{"41":1,"42":1,"57":1,"68":1,"118":1}}],["focused",{"2":{"17":1,"32":2,"34":1,"50":1,"58":1,"112":1,"115":1}}],["focuses",{"2":{"17":1}}],["found",{"2":{"36":1,"72":1,"86":1}}],["forward",{"2":{"87":1}}],["forget",{"2":{"62":1}}],["forgejo",{"0":{"24":1},"2":{"24":1,"65":1,"84":1}}],["foreign",{"2":{"86":1}}],["forefront",{"2":{"41":1}}],["forest",{"2":{"14":1,"95":1}}],["force",{"2":{"13":1}}],["former",{"2":{"57":1}}],["formal",{"2":{"43":1,"53":1}}],["formally",{"2":{"42":1}}],["forms",{"2":{"32":1,"94":1}}],["forming",{"2":{"18":1}}],["form",{"2":{"7":1,"9":1,"21":1,"35":1,"40":1,"90":1,"98":1,"104":1,"113":1}}],["for",{"0":{"64":1},"2":{"0":1,"3":2,"4":4,"5":2,"8":1,"10":1,"12":1,"13":15,"14":1,"15":1,"16":1,"17":2,"18":3,"19":1,"20":2,"21":3,"22":4,"26":1,"28":3,"30":4,"31":3,"32":2,"33":2,"34":2,"35":3,"37":1,"38":4,"39":2,"40":3,"41":10,"42":3,"43":1,"44":3,"45":1,"46":6,"47":2,"48":1,"49":1,"57":4,"58":1,"59":1,"60":4,"61":1,"62":5,"63":7,"64":1,"65":1,"67":1,"68":1,"71":1,"74":2,"76":1,"79":1,"83":1,"85":1,"86":1,"87":1,"90":2,"91":1,"92":1,"93":1,"94":1,"95":1,"96":1,"97":1,"99":2,"100":1,"102":2,"104":1,"105":2,"109":1,"113":2,"114":3,"117":1,"120":1}}],["f3",{"2":{"10":1}}],["fashion",{"2":{"61":1}}],["fast",{"2":{"48":1}}],["faster",{"2":{"9":1,"48":1}}],["fail",{"2":{"47":1}}],["fails",{"2":{"18":1}}],["fairly",{"2":{"41":1,"61":1}}],["fantasy",{"2":{"51":1}}],["fans",{"2":{"41":1,"43":1,"74":1}}],["fan",{"2":{"41":1,"51":1,"60":1,"69":1}}],["fancy",{"2":{"30":1}}],["fallen",{"2":{"61":1}}],["fall",{"2":{"41":1,"42":2,"50":1}}],["familiarity",{"2":{"41":1}}],["familiar",{"2":{"40":1}}],["famous",{"2":{"38":1}}],["favorite",{"2":{"38":1,"68":1,"94":1}}],["far",{"2":{"35":1,"44":1,"61":1,"62":2,"63":1}}],["face",{"2":{"13":3,"56":1}}],["factor",{"2":{"44":1,"46":2,"48":1}}],["factors",{"0":{"47":1,"48":1},"2":{"44":6,"45":1,"47":3,"48":2}}],["factorio",{"2":{"42":1}}],["factory",{"2":{"42":3,"63":1}}],["fact",{"2":{"9":1,"39":2,"42":1,"60":1,"61":1,"62":1,"70":1,"104":1}}],["future",{"0":{"101":1},"2":{"57":1,"63":2}}],["fulfillment",{"2":{"41":2}}],["full",{"2":{"13":1,"20":1,"67":1}}],["fully",{"2":{"12":1,"18":1,"21":1,"33":1,"61":1,"63":1}}],["funnily",{"2":{"73":1}}],["fun",{"2":{"35":2,"38":2,"39":1,"41":3,"56":1,"57":1}}],["functionality",{"2":{"9":1}}],["further",{"2":{"16":1,"63":1}}],["fuzzy",{"2":{"9":1}}],["feels",{"2":{"42":1,"62":1,"63":1}}],["feelings",{"2":{"38":1}}],["feeling",{"2":{"34":1,"36":1,"39":1}}],["feel",{"2":{"33":1,"34":3,"35":3,"36":1,"38":2,"41":1,"53":1,"56":1,"57":1,"59":1,"62":1,"70":1}}],["feedback",{"0":{"57":1,"58":1,"59":1},"2":{"56":1,"57":7,"58":3,"59":4,"85":1}}],["feeding",{"2":{"35":1}}],["feeds",{"2":{"7":2,"28":1}}],["feed",{"2":{"7":1,"104":1}}],["few",{"2":{"17":1,"30":1,"35":1,"51":1}}],["feature",{"2":{"64":3}}],["featured",{"2":{"50":1}}],["features",{"2":{"10":1,"41":1,"87":1}}],["feats",{"2":{"35":1}}],["feasibility",{"2":{"17":1}}],["federation",{"2":{"17":1,"114":1}}],["federated",{"0":{"15":1},"2":{"0":1,"3":1,"10":3,"12":1,"15":1,"16":1,"17":1,"18":1,"65":1,"83":1,"92":1,"114":1}}],["fedi",{"0":{"16":1},"1":{"17":1,"18":1,"19":1,"20":1,"21":1,"22":1},"2":{"10":1,"12":1,"15":1,"23":1,"92":1,"114":2}}],["fediverse",{"0":{"23":1},"2":{"0":1,"3":2,"12":3,"16":1,"65":1,"77":1,"83":1,"92":1,"114":3}}],["friction",{"2":{"90":1}}],["friendly",{"2":{"31":1}}],["frankly",{"2":{"41":1}}],["framework",{"2":{"33":1,"41":1,"42":1,"63":1}}],["frequency",{"2":{"63":2}}],["frequently",{"2":{"62":1,"63":1}}],["frequent",{"2":{"61":1}}],["freshness",{"2":{"37":1}}],["freely",{"2":{"13":1}}],["free",{"0":{"108":1},"2":{"13":1,"18":1,"35":1,"53":1,"90":1,"100":1,"102":2,"110":1}}],["freeform",{"0":{"25":1,"26":1},"2":{"7":2,"10":1,"14":1,"25":2,"26":4,"28":2,"98":1}}],["from",{"2":{"4":1,"9":1,"10":1,"12":1,"13":2,"17":1,"19":2,"30":1,"32":1,"33":1,"34":4,"35":1,"36":1,"37":1,"38":2,"39":1,"40":1,"41":5,"43":2,"44":2,"47":1,"52":2,"56":2,"57":2,"58":2,"62":1,"63":5,"74":3,"86":3,"97":1,"99":1,"101":1,"113":1}}],["aaa",{"0":{"107":1},"2":{"107":3}}],["aalto",{"2":{"11":1}}],["aesthetic",{"2":{"71":1}}],["aesthetics",{"2":{"41":1}}],["affordable",{"2":{"62":1}}],["affects",{"2":{"60":1}}],["affect",{"2":{"50":1,"56":1}}],["after",{"2":{"13":2,"22":1,"38":1,"60":1,"61":1,"62":3,"63":1,"89":1}}],["afterward",{"2":{"13":1}}],["apart",{"2":{"38":1}}],["app",{"2":{"118":1}}],["appropriate",{"2":{"43":1,"59":1}}],["approach",{"2":{"42":1}}],["appear",{"2":{"41":1}}],["appealing",{"2":{"43":1,"52":1,"113":1}}],["appeals",{"2":{"29":1,"35":1,"36":1,"39":1}}],["appeal",{"0":{"29":1,"33":1},"1":{"30":1,"31":1,"32":1,"34":1,"35":1,"36":1,"37":1,"38":1,"39":1},"2":{"33":1,"34":1,"35":2,"36":2,"41":1,"46":1,"54":2,"61":1,"63":1}}],["apparent",{"2":{"38":1}}],["applicable",{"2":{"64":1}}],["applied",{"2":{"44":1}}],["applies",{"2":{"18":1,"32":1,"36":1}}],["apply",{"2":{"41":1,"47":1,"49":1,"63":1,"94":1}}],["appleton",{"2":{"9":1,"95":1}}],["apps",{"2":{"9":2}}],["ag501",{"2":{"87":1}}],["again",{"2":{"62":1,"63":1,"69":1}}],["against",{"2":{"13":2,"38":1,"57":1,"62":1}}],["aggressively",{"2":{"38":1}}],["aggressive",{"2":{"38":1}}],["agree",{"2":{"38":1}}],["avoid",{"2":{"45":1}}],["avoiding",{"0":{"37":1}}],["available",{"2":{"13":2,"30":1,"32":2,"51":1,"63":1,"68":1,"79":1,"114":1}}],["away",{"2":{"41":1,"62":3,"63":3}}],["aware",{"2":{"32":2,"38":1}}],["awesome",{"0":{"71":1},"2":{"1":1,"74":1}}],["augmenting",{"2":{"63":1}}],["augments",{"2":{"34":1}}],["automating",{"2":{"63":2}}],["automation",{"2":{"48":1,"63":3}}],["automatic",{"2":{"42":1,"48":1,"104":1}}],["automatically",{"2":{"42":1,"48":2}}],["automated",{"2":{"62":2,"63":3}}],["automate",{"2":{"41":1,"62":1,"63":1}}],["authentication",{"2":{"19":1}}],["author",{"2":{"18":1,"97":1}}],["authoritative",{"2":{"18":1}}],["authority",{"2":{"12":1,"44":1,"53":1}}],["audio",{"2":{"20":1}}],["admittedly",{"2":{"63":1}}],["admin",{"2":{"30":1}}],["ads",{"2":{"32":1,"90":1,"92":1,"95":1,"98":1,"108":1}}],["adoption",{"2":{"17":1}}],["adds",{"2":{"34":1,"49":1}}],["adding",{"2":{"52":1,"63":2,"117":1}}],["addiction",{"2":{"35":5,"41":1}}],["addictive",{"2":{"32":2,"35":1}}],["additional",{"2":{"13":1,"21":1,"41":1,"53":1,"87":1}}],["additionally",{"2":{"13":1,"30":1,"41":1,"42":1,"46":1}}],["addition",{"2":{"13":1,"87":1}}],["address",{"2":{"17":1}}],["added",{"2":{"13":1,"18":1,"87":1}}],["add",{"2":{"13":1,"18":1,"21":1,"30":1,"52":1,"63":2}}],["advantage",{"2":{"13":1,"34":1,"57":1}}],["advantages",{"2":{"12":1}}],["adventures",{"0":{"71":1}}],["adventure",{"2":{"41":2}}],["advent",{"0":{"1":1},"2":{"1":1,"80":1,"81":1,"84":1,"91":2}}],["ability",{"2":{"104":1}}],["abilities",{"2":{"13":1}}],["absent",{"2":{"94":1}}],["absolutely",{"2":{"63":1}}],["abstracts",{"2":{"63":1,"90":1}}],["abstract",{"2":{"63":3}}],["absurdly",{"2":{"13":1}}],["able",{"2":{"35":1,"36":1,"56":1,"63":1}}],["abundant",{"2":{"32":1}}],["abundance",{"2":{"32":1}}],["above",{"2":{"13":1,"32":1,"41":1,"42":1,"46":1,"63":2}}],["about",{"0":{"103":1},"2":{"1":1,"10":1,"13":2,"16":1,"19":1,"27":1,"30":1,"33":5,"35":3,"36":2,"38":2,"39":2,"40":1,"41":1,"42":2,"44":1,"53":1,"63":3,"69":1,"88":1,"95":1,"101":1,"113":1,"117":1}}],["ask",{"2":{"60":1}}],["asked",{"2":{"45":1,"57":1}}],["ascension",{"2":{"41":1}}],["ascribes",{"2":{"41":1}}],["aside",{"2":{"39":1}}],["associating",{"2":{"17":1,"92":1}}],["associated",{"2":{"17":1,"63":1,"92":1}}],["associate",{"2":{"17":1}}],["assistants",{"2":{"2":1}}],["as",{"0":{"42":1,"43":1},"1":{"44":1,"45":1,"46":1,"47":1,"48":1,"49":1},"2":{"7":1,"10":2,"13":7,"18":6,"19":2,"20":5,"21":5,"22":1,"31":3,"33":3,"34":4,"35":9,"36":3,"38":2,"39":5,"40":1,"41":16,"42":5,"43":2,"44":3,"46":3,"47":3,"48":3,"52":1,"53":2,"57":3,"60":5,"61":5,"62":7,"63":11,"69":1,"70":4,"86":1,"87":1,"98":1,"104":2,"105":2,"116":1}}],["acamaeda",{"2":{"62":1,"91":1}}],["achieving",{"2":{"61":1}}],["achieve",{"2":{"35":1}}],["acknowledged",{"2":{"44":1}}],["across",{"2":{"43":1,"48":1,"57":1}}],["actors",{"2":{"68":1}}],["actual",{"2":{"27":1,"34":1,"42":2,"57":1,"61":1}}],["actually",{"2":{"16":1,"17":1,"20":1,"33":1,"34":1,"35":2,"92":1,"97":1}}],["act",{"2":{"19":1,"39":1}}],["activity",{"2":{"61":1}}],["activitypub",{"0":{"0":1},"2":{"0":1,"10":1,"12":1,"23":2}}],["active",{"2":{"41":1}}],["actively",{"2":{"30":1,"35":1,"61":1}}],["actions",{"2":{"9":2,"50":1,"69":1}}],["action",{"2":{"9":1,"13":2,"22":2,"48":1}}],["accomplishment",{"2":{"36":1,"59":1}}],["accounts",{"2":{"21":1,"44":1}}],["account",{"2":{"7":1,"19":1,"22":1}}],["access",{"2":{"74":1,"114":1}}],["accessibility",{"2":{"61":1}}],["accessible",{"2":{"10":1,"30":1,"84":1}}],["accept",{"2":{"42":1}}],["accepting",{"2":{"32":1}}],["acceptable",{"2":{"13":1}}],["arc",{"2":{"69":2}}],["arcane",{"2":{"9":1,"13":1}}],["arguably",{"2":{"49":1}}],["arguing",{"2":{"38":1,"39":1}}],["argumentative",{"2":{"104":1}}],["argument",{"2":{"33":1,"35":1,"38":1,"39":1,"62":1}}],["arguments",{"2":{"33":2,"39":1}}],["argues",{"2":{"43":1}}],["argued",{"2":{"34":1,"38":1,"44":3}}],["argue",{"2":{"33":1,"34":2,"35":2,"38":1,"39":2,"41":1,"46":1,"50":2,"63":1}}],["arms",{"2":{"31":1,"107":1}}],["armor",{"0":{"13":1},"2":{"4":1,"13":3,"80":1,"81":1,"84":1}}],["around",{"2":{"30":1,"31":1,"51":1,"68":1,"91":1,"105":1}}],["arbitrary",{"2":{"13":1,"20":1}}],["area",{"2":{"39":1}}],["aren",{"2":{"35":2,"43":1,"46":1,"48":1,"81":1}}],["are",{"0":{"30":1,"31":1,"49":1},"2":{"7":1,"9":1,"10":2,"13":5,"14":1,"15":1,"16":1,"17":1,"18":1,"19":1,"20":3,"21":2,"22":1,"28":1,"29":1,"30":5,"31":1,"32":5,"33":3,"34":2,"35":11,"36":2,"38":4,"39":6,"40":1,"41":13,"42":12,"43":2,"44":1,"45":1,"46":3,"47":2,"48":3,"50":4,"51":1,"56":2,"57":3,"58":1,"61":1,"62":7,"63":5,"64":1,"89":1,"98":1,"100":1,"102":4,"104":2,"105":1,"113":2,"114":2}}],["articulate",{"2":{"58":1}}],["article",{"2":{"9":1,"17":1,"95":1}}],["artistic",{"0":{"39":1},"2":{"39":5}}],["artist",{"2":{"13":1,"94":1}}],["artificially",{"2":{"60":2,"61":1}}],["artificial",{"0":{"2":1},"2":{"9":1,"13":1}}],["art",{"2":{"2":1,"30":1,"39":11,"41":1,"94":2}}],["attain",{"2":{"50":1}}],["attaching",{"2":{"39":1}}],["attacks",{"2":{"38":1}}],["attack",{"2":{"13":1,"57":1,"59":1,"60":1}}],["attention",{"2":{"33":1,"35":1,"69":1}}],["at",{"2":{"3":1,"12":1,"13":3,"18":1,"21":2,"22":1,"34":1,"35":3,"36":1,"37":1,"38":3,"41":3,"42":1,"43":1,"52":1,"57":2,"61":1,"62":3,"63":2,"68":2,"70":2,"79":1,"86":1,"87":2,"115":1,"116":1}}],["atproto",{"0":{"3":1},"2":{"3":1,"12":1,"17":1,"23":2}}],["algorithms",{"2":{"113":1}}],["algorithmic",{"2":{"7":1}}],["alveolar",{"2":{"86":3}}],["alone",{"2":{"63":1,"74":1}}],["alongside",{"2":{"61":1,"85":1}}],["along",{"2":{"46":1,"52":1,"63":1,"118":1,"119":1}}],["alright",{"2":{"45":1}}],["already",{"2":{"13":1,"33":1,"39":1,"40":1,"46":1,"47":1,"113":1}}],["always",{"2":{"31":1,"41":1}}],["although",{"2":{"34":1,"38":1,"39":1,"41":1,"43":1,"46":1,"62":1,"63":1,"71":1,"73":1,"74":1}}],["alt",{"2":{"17":1}}],["alternatives",{"2":{"14":1}}],["alternative",{"2":{"10":1,"26":1,"28":2,"48":1}}],["almost",{"2":{"9":1,"32":1,"41":1}}],["also",{"2":{"2":1,"9":1,"10":2,"13":3,"18":1,"21":1,"32":1,"34":1,"41":3,"43":1,"49":3,"50":1,"53":1,"62":1,"63":3,"84":1,"94":1,"95":1,"114":1,"117":1}}],["allowed",{"2":{"15":1,"57":1}}],["allow",{"2":{"15":1,"45":1,"50":1}}],["allows",{"2":{"13":1,"35":1,"36":1,"113":1,"114":1}}],["allowing",{"2":{"13":1,"35":1,"44":1,"46":1}}],["all",{"2":{"2":1,"13":8,"16":1,"17":1,"18":1,"19":2,"22":4,"23":1,"30":1,"31":1,"35":4,"36":1,"39":1,"40":2,"41":4,"42":1,"43":1,"44":2,"47":1,"57":1,"59":2,"62":3,"63":6,"70":1,"94":2,"97":1,"105":1,"113":1,"120":1}}],["amp",{"2":{"114":1}}],["amplification",{"0":{"97":1},"2":{"97":1}}],["american",{"2":{"86":1}}],["amazing",{"2":{"70":1}}],["am",{"0":{"53":1}}],["amongst",{"2":{"46":1,"61":1,"62":1,"99":1,"105":1}}],["amount",{"2":{"35":1,"40":1,"48":2,"60":3,"63":1,"64":2}}],["amounts",{"2":{"2":1,"9":1,"17":1,"90":1}}],["ambitious",{"2":{"1":1,"67":1}}],["aims",{"2":{"114":1}}],["ai",{"2":{"2":6,"21":1,"116":1}}],["announced",{"2":{"74":1}}],["angry",{"2":{"59":1}}],["angle",{"2":{"13":1}}],["angles",{"2":{"13":1}}],["anime",{"2":{"51":1}}],["anecdotal",{"2":{"41":1}}],["another",{"2":{"40":1,"41":1,"42":2,"43":1,"47":1,"62":1,"64":1}}],["anonymity",{"2":{"22":2}}],["anonymous",{"2":{"21":1}}],["anonymously",{"2":{"17":1}}],["answers",{"2":{"45":1}}],["answering",{"2":{"33":1}}],["answer",{"2":{"33":1,"40":1,"63":1}}],["analytical",{"2":{"45":1}}],["analyses",{"2":{"33":1,"94":1}}],["analyze",{"2":{"57":1}}],["analyzed",{"2":{"33":1}}],["analyzing",{"2":{"21":1}}],["anyways",{"2":{"41":1}}],["any",{"2":{"13":1,"19":3,"21":1,"30":1,"31":1,"34":2,"35":1,"39":9,"40":2,"41":3,"44":4,"46":1,"49":2,"53":1,"60":2,"61":1,"62":2,"63":2,"69":1,"74":1,"100":1,"105":1,"114":1}}],["anyone",{"2":{"12":1,"18":2,"31":1,"56":1}}],["anything",{"2":{"7":1,"10":1,"20":1,"26":1,"35":2,"49":1,"53":1,"104":1}}],["antimatter",{"2":{"50":1,"62":4}}],["anticipate",{"2":{"58":2}}],["anticipated",{"2":{"1":1}}],["anticipating",{"2":{"46":1}}],["anti",{"2":{"32":1,"74":1}}],["anthony",{"2":{"5":1}}],["and",{"0":{"82":1},"2":{"1":2,"2":2,"4":2,"5":1,"7":1,"9":1,"10":4,"11":1,"12":2,"13":25,"14":2,"15":3,"17":1,"18":6,"19":1,"20":4,"21":6,"22":5,"28":1,"29":1,"30":3,"31":5,"32":7,"33":7,"34":10,"35":16,"36":10,"37":2,"38":12,"39":13,"40":4,"41":15,"42":8,"43":1,"44":5,"45":2,"46":2,"47":2,"48":2,"49":2,"50":7,"51":1,"52":8,"53":1,"56":10,"57":12,"58":8,"59":6,"60":8,"61":6,"62":12,"63":26,"64":3,"65":2,"66":1,"67":3,"68":4,"69":6,"70":1,"71":2,"72":1,"77":1,"80":1,"81":1,"84":1,"86":3,"87":3,"91":1,"92":2,"94":3,"97":3,"98":1,"99":1,"100":1,"102":2,"104":3,"105":7,"107":1,"108":1,"116":1,"117":1,"118":2,"119":1}}],["an",{"0":{"55":1},"2":{"1":2,"8":1,"9":1,"10":1,"13":6,"14":1,"19":1,"20":2,"22":1,"24":1,"28":1,"30":2,"32":1,"35":2,"38":4,"39":4,"40":3,"41":3,"42":4,"44":1,"45":1,"46":3,"47":2,"48":3,"49":2,"52":1,"56":1,"57":1,"59":2,"61":1,"62":1,"63":3,"64":2,"65":1,"67":1,"75":1,"77":1,"86":2,"88":1,"90":1,"91":1,"92":2,"93":1,"94":1,"95":1,"102":1,"104":2,"105":2,"111":1,"114":1,"118":1}}],["a",{"2":{"0":1,"1":1,"3":2,"4":2,"5":2,"6":1,"7":2,"9":2,"10":3,"12":2,"13":27,"14":1,"15":1,"16":2,"17":8,"18":16,"19":6,"20":7,"21":6,"22":10,"23":2,"25":2,"26":3,"28":1,"29":2,"30":6,"31":1,"32":4,"33":8,"34":14,"35":16,"36":3,"37":3,"38":12,"39":12,"40":12,"41":19,"42":10,"43":9,"44":13,"45":6,"46":13,"47":9,"48":5,"49":2,"50":11,"51":3,"52":4,"53":4,"56":6,"57":6,"58":1,"59":3,"60":5,"61":9,"62":19,"63":24,"64":8,"65":1,"66":1,"67":2,"68":5,"69":7,"70":2,"71":1,"73":1,"74":1,"76":1,"79":1,"81":1,"83":1,"85":1,"86":6,"87":1,"89":1,"90":4,"91":1,"92":1,"95":1,"96":1,"97":1,"98":2,"99":2,"101":1,"102":1,"104":3,"105":10,"107":1,"109":1,"112":1,"113":8,"114":1,"115":2,"116":1,"117":2,"118":2,"120":1,"121":2}}]],"serializationVersion":2}';export{e as default}; diff --git a/assets/chunks/VPLocalSearchBox.B3jfi5U8.js b/assets/chunks/VPLocalSearchBox.B3jfi5U8.js deleted file mode 100644 index 227fac47..00000000 --- a/assets/chunks/VPLocalSearchBox.B3jfi5U8.js +++ /dev/null @@ -1,7 +0,0 @@ -var Nt=Object.defineProperty;var Ct=(o,e,t)=>e in o?Nt(o,e,{enumerable:!0,configurable:!0,writable:!0,value:t}):o[e]=t;var ke=(o,e,t)=>(Ct(o,typeof e!="symbol"?e+"":e,t),t);import{X as It,s as ie,v as Ve,aD as Dt,aE as kt,d as Ot,G as we,aF as et,h as xe,aG as Rt,aH as _t,x as Mt,aI as Lt,y as Oe,R as he,Q as Fe,aJ as Pt,a3 as zt,Y as Bt,U as Vt,aK as $t,o as X,b as Wt,j as k,a1 as Kt,k as G,aL as Jt,aM as Ut,aN as jt,c as te,n as tt,e as Ee,E as rt,F as at,a as de,t as ve,aO as Gt,p as Qt,l as Ht,aP as nt,aQ as qt,as as Yt,ay as Zt,aR as Xt,_ as er}from"./framework.CK8QU5WH.js";import{u as tr,c as rr}from"./theme.Lm1E6I-W.js";const ar={root:()=>It(()=>import("./@localSearchIndexroot.Dijcf9Pd.js"),[])};/*! -* tabbable 6.2.0 -* @license MIT, https://github.com/focus-trap/tabbable/blob/master/LICENSE -*/var pt=["input:not([inert])","select:not([inert])","textarea:not([inert])","a[href]:not([inert])","button:not([inert])","[tabindex]:not(slot):not([inert])","audio[controls]:not([inert])","video[controls]:not([inert])",'[contenteditable]:not([contenteditable="false"]):not([inert])',"details>summary:first-of-type:not([inert])","details:not([inert])"],Te=pt.join(","),yt=typeof Element>"u",se=yt?function(){}:Element.prototype.matches||Element.prototype.msMatchesSelector||Element.prototype.webkitMatchesSelector,Ne=!yt&&Element.prototype.getRootNode?function(o){var e;return o==null||(e=o.getRootNode)===null||e===void 0?void 0:e.call(o)}:function(o){return o==null?void 0:o.ownerDocument},Ce=function o(e,t){var r;t===void 0&&(t=!0);var n=e==null||(r=e.getAttribute)===null||r===void 0?void 0:r.call(e,"inert"),a=n===""||n==="true",i=a||t&&e&&o(e.parentNode);return i},nr=function(e){var t,r=e==null||(t=e.getAttribute)===null||t===void 0?void 0:t.call(e,"contenteditable");return r===""||r==="true"},mt=function(e,t,r){if(Ce(e))return[];var n=Array.prototype.slice.apply(e.querySelectorAll(Te));return t&&se.call(e,Te)&&n.unshift(e),n=n.filter(r),n},gt=function o(e,t,r){for(var n=[],a=Array.from(e);a.length;){var i=a.shift();if(!Ce(i,!1))if(i.tagName==="SLOT"){var s=i.assignedElements(),u=s.length?s:i.children,l=o(u,!0,r);r.flatten?n.push.apply(n,l):n.push({scopeParent:i,candidates:l})}else{var d=se.call(i,Te);d&&r.filter(i)&&(t||!e.includes(i))&&n.push(i);var h=i.shadowRoot||typeof r.getShadowRoot=="function"&&r.getShadowRoot(i),v=!Ce(h,!1)&&(!r.shadowRootFilter||r.shadowRootFilter(i));if(h&&v){var m=o(h===!0?i.children:h.children,!0,r);r.flatten?n.push.apply(n,m):n.push({scopeParent:i,candidates:m})}else a.unshift.apply(a,i.children)}}return n},bt=function(e){return!isNaN(parseInt(e.getAttribute("tabindex"),10))},oe=function(e){if(!e)throw new Error("No node provided");return e.tabIndex<0&&(/^(AUDIO|VIDEO|DETAILS)$/.test(e.tagName)||nr(e))&&!bt(e)?0:e.tabIndex},ir=function(e,t){var r=oe(e);return r<0&&t&&!bt(e)?0:r},or=function(e,t){return e.tabIndex===t.tabIndex?e.documentOrder-t.documentOrder:e.tabIndex-t.tabIndex},wt=function(e){return e.tagName==="INPUT"},sr=function(e){return wt(e)&&e.type==="hidden"},ur=function(e){var t=e.tagName==="DETAILS"&&Array.prototype.slice.apply(e.children).some(function(r){return r.tagName==="SUMMARY"});return t},lr=function(e,t){for(var r=0;rsummary:first-of-type"),i=a?e.parentElement:e;if(se.call(i,"details:not([open]) *"))return!0;if(!r||r==="full"||r==="legacy-full"){if(typeof n=="function"){for(var s=e;e;){var u=e.parentElement,l=Ne(e);if(u&&!u.shadowRoot&&n(u)===!0)return it(e);e.assignedSlot?e=e.assignedSlot:!u&&l!==e.ownerDocument?e=l.host:e=u}e=s}if(dr(e))return!e.getClientRects().length;if(r!=="legacy-full")return!0}else if(r==="non-zero-area")return it(e);return!1},pr=function(e){if(/^(INPUT|BUTTON|SELECT|TEXTAREA)$/.test(e.tagName))for(var t=e.parentElement;t;){if(t.tagName==="FIELDSET"&&t.disabled){for(var r=0;r=0)},mr=function o(e){var t=[],r=[];return e.forEach(function(n,a){var i=!!n.scopeParent,s=i?n.scopeParent:n,u=ir(s,i),l=i?o(n.candidates):s;u===0?i?t.push.apply(t,l):t.push(s):r.push({documentOrder:a,tabIndex:u,item:n,isScope:i,content:l})}),r.sort(or).reduce(function(n,a){return a.isScope?n.push.apply(n,a.content):n.push(a.content),n},[]).concat(t)},gr=function(e,t){t=t||{};var r;return t.getShadowRoot?r=gt([e],t.includeContainer,{filter:$e.bind(null,t),flatten:!1,getShadowRoot:t.getShadowRoot,shadowRootFilter:yr}):r=mt(e,t.includeContainer,$e.bind(null,t)),mr(r)},br=function(e,t){t=t||{};var r;return t.getShadowRoot?r=gt([e],t.includeContainer,{filter:Ie.bind(null,t),flatten:!0,getShadowRoot:t.getShadowRoot}):r=mt(e,t.includeContainer,Ie.bind(null,t)),r},ue=function(e,t){if(t=t||{},!e)throw new Error("No node provided");return se.call(e,Te)===!1?!1:$e(t,e)},wr=pt.concat("iframe").join(","),Re=function(e,t){if(t=t||{},!e)throw new Error("No node provided");return se.call(e,wr)===!1?!1:Ie(t,e)};/*! -* focus-trap 7.5.4 -* @license MIT, https://github.com/focus-trap/focus-trap/blob/master/LICENSE -*/function ot(o,e){var t=Object.keys(o);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(o);e&&(r=r.filter(function(n){return Object.getOwnPropertyDescriptor(o,n).enumerable})),t.push.apply(t,r)}return t}function st(o){for(var e=1;e0){var r=e[e.length-1];r!==t&&r.pause()}var n=e.indexOf(t);n===-1||e.splice(n,1),e.push(t)},deactivateTrap:function(e,t){var r=e.indexOf(t);r!==-1&&e.splice(r,1),e.length>0&&e[e.length-1].unpause()}},Sr=function(e){return e.tagName&&e.tagName.toLowerCase()==="input"&&typeof e.select=="function"},Ar=function(e){return(e==null?void 0:e.key)==="Escape"||(e==null?void 0:e.key)==="Esc"||(e==null?void 0:e.keyCode)===27},me=function(e){return(e==null?void 0:e.key)==="Tab"||(e==null?void 0:e.keyCode)===9},Tr=function(e){return me(e)&&!e.shiftKey},Nr=function(e){return me(e)&&e.shiftKey},lt=function(e){return setTimeout(e,0)},ct=function(e,t){var r=-1;return e.every(function(n,a){return t(n)?(r=a,!1):!0}),r},pe=function(e){for(var t=arguments.length,r=new Array(t>1?t-1:0),n=1;n1?p-1:0),N=1;N=0)f=r.activeElement;else{var c=i.tabbableGroups[0],p=c&&c.firstTabbableNode;f=p||d("fallbackFocus")}if(!f)throw new Error("Your focus-trap needs to have at least one focusable element");return f},v=function(){if(i.containerGroups=i.containers.map(function(f){var c=gr(f,a.tabbableOptions),p=br(f,a.tabbableOptions),C=c.length>0?c[0]:void 0,N=c.length>0?c[c.length-1]:void 0,M=p.find(function(w){return ue(w)}),z=p.slice().reverse().find(function(w){return ue(w)}),y=!!c.find(function(w){return oe(w)>0});return{container:f,tabbableNodes:c,focusableNodes:p,posTabIndexesFound:y,firstTabbableNode:C,lastTabbableNode:N,firstDomTabbableNode:M,lastDomTabbableNode:z,nextTabbableNode:function(B){var U=arguments.length>1&&arguments[1]!==void 0?arguments[1]:!0,K=c.indexOf(B);return K<0?U?p.slice(p.indexOf(B)+1).find(function(J){return ue(J)}):p.slice(0,p.indexOf(B)).reverse().find(function(J){return ue(J)}):c[K+(U?1:-1)]}}}),i.tabbableGroups=i.containerGroups.filter(function(f){return f.tabbableNodes.length>0}),i.tabbableGroups.length<=0&&!d("fallbackFocus"))throw new Error("Your focus-trap must have at least one container with at least one tabbable node in it at all times");if(i.containerGroups.find(function(f){return f.posTabIndexesFound})&&i.containerGroups.length>1)throw new Error("At least one node with a positive tabindex was found in one of your focus-trap's multiple containers. Positive tabindexes are only supported in single-container focus-traps.")},m=function F(f){var c=f.activeElement;if(c)return c.shadowRoot&&c.shadowRoot.activeElement!==null?F(c.shadowRoot):c},g=function F(f){if(f!==!1&&f!==m(document)){if(!f||!f.focus){F(h());return}f.focus({preventScroll:!!a.preventScroll}),i.mostRecentlyFocusedNode=f,Sr(f)&&f.select()}},b=function(f){var c=d("setReturnFocus",f);return c||(c===!1?!1:f)},x=function(f){var c=f.target,p=f.event,C=f.isBackward,N=C===void 0?!1:C;c=c||Se(p),v();var M=null;if(i.tabbableGroups.length>0){var z=l(c,p),y=z>=0?i.containerGroups[z]:void 0;if(z<0)N?M=i.tabbableGroups[i.tabbableGroups.length-1].lastTabbableNode:M=i.tabbableGroups[0].firstTabbableNode;else if(N){var w=ct(i.tabbableGroups,function(j){var H=j.firstTabbableNode;return c===H});if(w<0&&(y.container===c||Re(c,a.tabbableOptions)&&!ue(c,a.tabbableOptions)&&!y.nextTabbableNode(c,!1))&&(w=z),w>=0){var B=w===0?i.tabbableGroups.length-1:w-1,U=i.tabbableGroups[B];M=oe(c)>=0?U.lastTabbableNode:U.lastDomTabbableNode}else me(p)||(M=y.nextTabbableNode(c,!1))}else{var K=ct(i.tabbableGroups,function(j){var H=j.lastTabbableNode;return c===H});if(K<0&&(y.container===c||Re(c,a.tabbableOptions)&&!ue(c,a.tabbableOptions)&&!y.nextTabbableNode(c))&&(K=z),K>=0){var J=K===i.tabbableGroups.length-1?0:K+1,V=i.tabbableGroups[J];M=oe(c)>=0?V.firstTabbableNode:V.firstDomTabbableNode}else me(p)||(M=y.nextTabbableNode(c))}}else M=d("fallbackFocus");return M},S=function(f){var c=Se(f);if(!(l(c,f)>=0)){if(pe(a.clickOutsideDeactivates,f)){s.deactivate({returnFocus:a.returnFocusOnDeactivate});return}pe(a.allowOutsideClick,f)||f.preventDefault()}},T=function(f){var c=Se(f),p=l(c,f)>=0;if(p||c instanceof Document)p&&(i.mostRecentlyFocusedNode=c);else{f.stopImmediatePropagation();var C,N=!0;if(i.mostRecentlyFocusedNode)if(oe(i.mostRecentlyFocusedNode)>0){var M=l(i.mostRecentlyFocusedNode),z=i.containerGroups[M].tabbableNodes;if(z.length>0){var y=z.findIndex(function(w){return w===i.mostRecentlyFocusedNode});y>=0&&(a.isKeyForward(i.recentNavEvent)?y+1=0&&(C=z[y-1],N=!1))}}else i.containerGroups.some(function(w){return w.tabbableNodes.some(function(B){return oe(B)>0})})||(N=!1);else N=!1;N&&(C=x({target:i.mostRecentlyFocusedNode,isBackward:a.isKeyBackward(i.recentNavEvent)})),g(C||i.mostRecentlyFocusedNode||h())}i.recentNavEvent=void 0},A=function(f){var c=arguments.length>1&&arguments[1]!==void 0?arguments[1]:!1;i.recentNavEvent=f;var p=x({event:f,isBackward:c});p&&(me(f)&&f.preventDefault(),g(p))},_=function(f){if(Ar(f)&&pe(a.escapeDeactivates,f)!==!1){f.preventDefault(),s.deactivate();return}(a.isKeyForward(f)||a.isKeyBackward(f))&&A(f,a.isKeyBackward(f))},L=function(f){var c=Se(f);l(c,f)>=0||pe(a.clickOutsideDeactivates,f)||pe(a.allowOutsideClick,f)||(f.preventDefault(),f.stopImmediatePropagation())},P=function(){if(i.active)return ut.activateTrap(n,s),i.delayInitialFocusTimer=a.delayInitialFocus?lt(function(){g(h())}):g(h()),r.addEventListener("focusin",T,!0),r.addEventListener("mousedown",S,{capture:!0,passive:!1}),r.addEventListener("touchstart",S,{capture:!0,passive:!1}),r.addEventListener("click",L,{capture:!0,passive:!1}),r.addEventListener("keydown",_,{capture:!0,passive:!1}),s},I=function(){if(i.active)return r.removeEventListener("focusin",T,!0),r.removeEventListener("mousedown",S,!0),r.removeEventListener("touchstart",S,!0),r.removeEventListener("click",L,!0),r.removeEventListener("keydown",_,!0),s},E=function(f){var c=f.some(function(p){var C=Array.from(p.removedNodes);return C.some(function(N){return N===i.mostRecentlyFocusedNode})});c&&g(h())},O=typeof window<"u"&&"MutationObserver"in window?new MutationObserver(E):void 0,R=function(){O&&(O.disconnect(),i.active&&!i.paused&&i.containers.map(function(f){O.observe(f,{subtree:!0,childList:!0})}))};return s={get active(){return i.active},get paused(){return i.paused},activate:function(f){if(i.active)return this;var c=u(f,"onActivate"),p=u(f,"onPostActivate"),C=u(f,"checkCanFocusTrap");C||v(),i.active=!0,i.paused=!1,i.nodeFocusedBeforeActivation=r.activeElement,c==null||c();var N=function(){C&&v(),P(),R(),p==null||p()};return C?(C(i.containers.concat()).then(N,N),this):(N(),this)},deactivate:function(f){if(!i.active)return this;var c=st({onDeactivate:a.onDeactivate,onPostDeactivate:a.onPostDeactivate,checkCanReturnFocus:a.checkCanReturnFocus},f);clearTimeout(i.delayInitialFocusTimer),i.delayInitialFocusTimer=void 0,I(),i.active=!1,i.paused=!1,R(),ut.deactivateTrap(n,s);var p=u(c,"onDeactivate"),C=u(c,"onPostDeactivate"),N=u(c,"checkCanReturnFocus"),M=u(c,"returnFocus","returnFocusOnDeactivate");p==null||p();var z=function(){lt(function(){M&&g(b(i.nodeFocusedBeforeActivation)),C==null||C()})};return M&&N?(N(b(i.nodeFocusedBeforeActivation)).then(z,z),this):(z(),this)},pause:function(f){if(i.paused||!i.active)return this;var c=u(f,"onPause"),p=u(f,"onPostPause");return i.paused=!0,c==null||c(),I(),R(),p==null||p(),this},unpause:function(f){if(!i.paused||!i.active)return this;var c=u(f,"onUnpause"),p=u(f,"onPostUnpause");return i.paused=!1,c==null||c(),v(),P(),R(),p==null||p(),this},updateContainerElements:function(f){var c=[].concat(f).filter(Boolean);return i.containers=c.map(function(p){return typeof p=="string"?r.querySelector(p):p}),i.active&&v(),R(),this}},s.updateContainerElements(e),s};function Dr(o,e={}){let t;const{immediate:r,...n}=e,a=ie(!1),i=ie(!1),s=h=>t&&t.activate(h),u=h=>t&&t.deactivate(h),l=()=>{t&&(t.pause(),i.value=!0)},d=()=>{t&&(t.unpause(),i.value=!1)};return Ve(()=>Dt(o),h=>{h&&(t=Ir(h,{...n,onActivate(){a.value=!0,e.onActivate&&e.onActivate()},onDeactivate(){a.value=!1,e.onDeactivate&&e.onDeactivate()}}),r&&s())},{flush:"post"}),kt(()=>u()),{hasFocus:a,isPaused:i,activate:s,deactivate:u,pause:l,unpause:d}}class ce{constructor(e,t=!0,r=[],n=5e3){this.ctx=e,this.iframes=t,this.exclude=r,this.iframesTimeout=n}static matches(e,t){const r=typeof t=="string"?[t]:t,n=e.matches||e.matchesSelector||e.msMatchesSelector||e.mozMatchesSelector||e.oMatchesSelector||e.webkitMatchesSelector;if(n){let a=!1;return r.every(i=>n.call(e,i)?(a=!0,!1):!0),a}else return!1}getContexts(){let e,t=[];return typeof this.ctx>"u"||!this.ctx?e=[]:NodeList.prototype.isPrototypeOf(this.ctx)?e=Array.prototype.slice.call(this.ctx):Array.isArray(this.ctx)?e=this.ctx:typeof this.ctx=="string"?e=Array.prototype.slice.call(document.querySelectorAll(this.ctx)):e=[this.ctx],e.forEach(r=>{const n=t.filter(a=>a.contains(r)).length>0;t.indexOf(r)===-1&&!n&&t.push(r)}),t}getIframeContents(e,t,r=()=>{}){let n;try{const a=e.contentWindow;if(n=a.document,!a||!n)throw new Error("iframe inaccessible")}catch{r()}n&&t(n)}isIframeBlank(e){const t="about:blank",r=e.getAttribute("src").trim();return e.contentWindow.location.href===t&&r!==t&&r}observeIframeLoad(e,t,r){let n=!1,a=null;const i=()=>{if(!n){n=!0,clearTimeout(a);try{this.isIframeBlank(e)||(e.removeEventListener("load",i),this.getIframeContents(e,t,r))}catch{r()}}};e.addEventListener("load",i),a=setTimeout(i,this.iframesTimeout)}onIframeReady(e,t,r){try{e.contentWindow.document.readyState==="complete"?this.isIframeBlank(e)?this.observeIframeLoad(e,t,r):this.getIframeContents(e,t,r):this.observeIframeLoad(e,t,r)}catch{r()}}waitForIframes(e,t){let r=0;this.forEachIframe(e,()=>!0,n=>{r++,this.waitForIframes(n.querySelector("html"),()=>{--r||t()})},n=>{n||t()})}forEachIframe(e,t,r,n=()=>{}){let a=e.querySelectorAll("iframe"),i=a.length,s=0;a=Array.prototype.slice.call(a);const u=()=>{--i<=0&&n(s)};i||u(),a.forEach(l=>{ce.matches(l,this.exclude)?u():this.onIframeReady(l,d=>{t(l)&&(s++,r(d)),u()},u)})}createIterator(e,t,r){return document.createNodeIterator(e,t,r,!1)}createInstanceOnIframe(e){return new ce(e.querySelector("html"),this.iframes)}compareNodeIframe(e,t,r){const n=e.compareDocumentPosition(r),a=Node.DOCUMENT_POSITION_PRECEDING;if(n&a)if(t!==null){const i=t.compareDocumentPosition(r),s=Node.DOCUMENT_POSITION_FOLLOWING;if(i&s)return!0}else return!0;return!1}getIteratorNode(e){const t=e.previousNode();let r;return t===null?r=e.nextNode():r=e.nextNode()&&e.nextNode(),{prevNode:t,node:r}}checkIframeFilter(e,t,r,n){let a=!1,i=!1;return n.forEach((s,u)=>{s.val===r&&(a=u,i=s.handled)}),this.compareNodeIframe(e,t,r)?(a===!1&&!i?n.push({val:r,handled:!0}):a!==!1&&!i&&(n[a].handled=!0),!0):(a===!1&&n.push({val:r,handled:!1}),!1)}handleOpenIframes(e,t,r,n){e.forEach(a=>{a.handled||this.getIframeContents(a.val,i=>{this.createInstanceOnIframe(i).forEachNode(t,r,n)})})}iterateThroughNodes(e,t,r,n,a){const i=this.createIterator(t,e,n);let s=[],u=[],l,d,h=()=>({prevNode:d,node:l}=this.getIteratorNode(i),l);for(;h();)this.iframes&&this.forEachIframe(t,v=>this.checkIframeFilter(l,d,v,s),v=>{this.createInstanceOnIframe(v).forEachNode(e,m=>u.push(m),n)}),u.push(l);u.forEach(v=>{r(v)}),this.iframes&&this.handleOpenIframes(s,e,r,n),a()}forEachNode(e,t,r,n=()=>{}){const a=this.getContexts();let i=a.length;i||n(),a.forEach(s=>{const u=()=>{this.iterateThroughNodes(e,s,t,r,()=>{--i<=0&&n()})};this.iframes?this.waitForIframes(s,u):u()})}}let kr=class{constructor(e){this.ctx=e,this.ie=!1;const t=window.navigator.userAgent;(t.indexOf("MSIE")>-1||t.indexOf("Trident")>-1)&&(this.ie=!0)}set opt(e){this._opt=Object.assign({},{element:"",className:"",exclude:[],iframes:!1,iframesTimeout:5e3,separateWordSearch:!0,diacritics:!0,synonyms:{},accuracy:"partially",acrossElements:!1,caseSensitive:!1,ignoreJoiners:!1,ignoreGroups:0,ignorePunctuation:[],wildcards:"disabled",each:()=>{},noMatch:()=>{},filter:()=>!0,done:()=>{},debug:!1,log:window.console},e)}get opt(){return this._opt}get iterator(){return new ce(this.ctx,this.opt.iframes,this.opt.exclude,this.opt.iframesTimeout)}log(e,t="debug"){const r=this.opt.log;this.opt.debug&&typeof r=="object"&&typeof r[t]=="function"&&r[t](`mark.js: ${e}`)}escapeStr(e){return e.replace(/[\-\[\]\/\{\}\(\)\*\+\?\.\\\^\$\|]/g,"\\$&")}createRegExp(e){return this.opt.wildcards!=="disabled"&&(e=this.setupWildcardsRegExp(e)),e=this.escapeStr(e),Object.keys(this.opt.synonyms).length&&(e=this.createSynonymsRegExp(e)),(this.opt.ignoreJoiners||this.opt.ignorePunctuation.length)&&(e=this.setupIgnoreJoinersRegExp(e)),this.opt.diacritics&&(e=this.createDiacriticsRegExp(e)),e=this.createMergedBlanksRegExp(e),(this.opt.ignoreJoiners||this.opt.ignorePunctuation.length)&&(e=this.createJoinersRegExp(e)),this.opt.wildcards!=="disabled"&&(e=this.createWildcardsRegExp(e)),e=this.createAccuracyRegExp(e),e}createSynonymsRegExp(e){const t=this.opt.synonyms,r=this.opt.caseSensitive?"":"i",n=this.opt.ignoreJoiners||this.opt.ignorePunctuation.length?"\0":"";for(let a in t)if(t.hasOwnProperty(a)){const i=t[a],s=this.opt.wildcards!=="disabled"?this.setupWildcardsRegExp(a):this.escapeStr(a),u=this.opt.wildcards!=="disabled"?this.setupWildcardsRegExp(i):this.escapeStr(i);s!==""&&u!==""&&(e=e.replace(new RegExp(`(${this.escapeStr(s)}|${this.escapeStr(u)})`,`gm${r}`),n+`(${this.processSynomyms(s)}|${this.processSynomyms(u)})`+n))}return e}processSynomyms(e){return(this.opt.ignoreJoiners||this.opt.ignorePunctuation.length)&&(e=this.setupIgnoreJoinersRegExp(e)),e}setupWildcardsRegExp(e){return e=e.replace(/(?:\\)*\?/g,t=>t.charAt(0)==="\\"?"?":""),e.replace(/(?:\\)*\*/g,t=>t.charAt(0)==="\\"?"*":"")}createWildcardsRegExp(e){let t=this.opt.wildcards==="withSpaces";return e.replace(/\u0001/g,t?"[\\S\\s]?":"\\S?").replace(/\u0002/g,t?"[\\S\\s]*?":"\\S*")}setupIgnoreJoinersRegExp(e){return e.replace(/[^(|)\\]/g,(t,r,n)=>{let a=n.charAt(r+1);return/[(|)\\]/.test(a)||a===""?t:t+"\0"})}createJoinersRegExp(e){let t=[];const r=this.opt.ignorePunctuation;return Array.isArray(r)&&r.length&&t.push(this.escapeStr(r.join(""))),this.opt.ignoreJoiners&&t.push("\\u00ad\\u200b\\u200c\\u200d"),t.length?e.split(/\u0000+/).join(`[${t.join("")}]*`):e}createDiacriticsRegExp(e){const t=this.opt.caseSensitive?"":"i",r=this.opt.caseSensitive?["aàáảãạăằắẳẵặâầấẩẫậäåāą","AÀÁẢÃẠĂẰẮẲẴẶÂẦẤẨẪẬÄÅĀĄ","cçćč","CÇĆČ","dđď","DĐĎ","eèéẻẽẹêềếểễệëěēę","EÈÉẺẼẸÊỀẾỂỄỆËĚĒĘ","iìíỉĩịîïī","IÌÍỈĨỊÎÏĪ","lł","LŁ","nñňń","NÑŇŃ","oòóỏõọôồốổỗộơởỡớờợöøō","OÒÓỎÕỌÔỒỐỔỖỘƠỞỠỚỜỢÖØŌ","rř","RŘ","sšśșş","SŠŚȘŞ","tťțţ","TŤȚŢ","uùúủũụưừứửữựûüůū","UÙÚỦŨỤƯỪỨỬỮỰÛÜŮŪ","yýỳỷỹỵÿ","YÝỲỶỸỴŸ","zžżź","ZŽŻŹ"]:["aàáảãạăằắẳẵặâầấẩẫậäåāąAÀÁẢÃẠĂẰẮẲẴẶÂẦẤẨẪẬÄÅĀĄ","cçćčCÇĆČ","dđďDĐĎ","eèéẻẽẹêềếểễệëěēęEÈÉẺẼẸÊỀẾỂỄỆËĚĒĘ","iìíỉĩịîïīIÌÍỈĨỊÎÏĪ","lłLŁ","nñňńNÑŇŃ","oòóỏõọôồốổỗộơởỡớờợöøōOÒÓỎÕỌÔỒỐỔỖỘƠỞỠỚỜỢÖØŌ","rřRŘ","sšśșşSŠŚȘŞ","tťțţTŤȚŢ","uùúủũụưừứửữựûüůūUÙÚỦŨỤƯỪỨỬỮỰÛÜŮŪ","yýỳỷỹỵÿYÝỲỶỸỴŸ","zžżźZŽŻŹ"];let n=[];return e.split("").forEach(a=>{r.every(i=>{if(i.indexOf(a)!==-1){if(n.indexOf(i)>-1)return!1;e=e.replace(new RegExp(`[${i}]`,`gm${t}`),`[${i}]`),n.push(i)}return!0})}),e}createMergedBlanksRegExp(e){return e.replace(/[\s]+/gmi,"[\\s]+")}createAccuracyRegExp(e){const t="!\"#$%&'()*+,-./:;<=>?@[\\]^_`{|}~¡¿";let r=this.opt.accuracy,n=typeof r=="string"?r:r.value,a=typeof r=="string"?[]:r.limiters,i="";switch(a.forEach(s=>{i+=`|${this.escapeStr(s)}`}),n){case"partially":default:return`()(${e})`;case"complementary":return i="\\s"+(i||this.escapeStr(t)),`()([^${i}]*${e}[^${i}]*)`;case"exactly":return`(^|\\s${i})(${e})(?=$|\\s${i})`}}getSeparatedKeywords(e){let t=[];return e.forEach(r=>{this.opt.separateWordSearch?r.split(" ").forEach(n=>{n.trim()&&t.indexOf(n)===-1&&t.push(n)}):r.trim()&&t.indexOf(r)===-1&&t.push(r)}),{keywords:t.sort((r,n)=>n.length-r.length),length:t.length}}isNumeric(e){return Number(parseFloat(e))==e}checkRanges(e){if(!Array.isArray(e)||Object.prototype.toString.call(e[0])!=="[object Object]")return this.log("markRanges() will only accept an array of objects"),this.opt.noMatch(e),[];const t=[];let r=0;return e.sort((n,a)=>n.start-a.start).forEach(n=>{let{start:a,end:i,valid:s}=this.callNoMatchOnInvalidRanges(n,r);s&&(n.start=a,n.length=i-a,t.push(n),r=i)}),t}callNoMatchOnInvalidRanges(e,t){let r,n,a=!1;return e&&typeof e.start<"u"?(r=parseInt(e.start,10),n=r+parseInt(e.length,10),this.isNumeric(e.start)&&this.isNumeric(e.length)&&n-t>0&&n-r>0?a=!0:(this.log(`Ignoring invalid or overlapping range: ${JSON.stringify(e)}`),this.opt.noMatch(e))):(this.log(`Ignoring invalid range: ${JSON.stringify(e)}`),this.opt.noMatch(e)),{start:r,end:n,valid:a}}checkWhitespaceRanges(e,t,r){let n,a=!0,i=r.length,s=t-i,u=parseInt(e.start,10)-s;return u=u>i?i:u,n=u+parseInt(e.length,10),n>i&&(n=i,this.log(`End range automatically set to the max value of ${i}`)),u<0||n-u<0||u>i||n>i?(a=!1,this.log(`Invalid range: ${JSON.stringify(e)}`),this.opt.noMatch(e)):r.substring(u,n).replace(/\s+/g,"")===""&&(a=!1,this.log("Skipping whitespace only range: "+JSON.stringify(e)),this.opt.noMatch(e)),{start:u,end:n,valid:a}}getTextNodes(e){let t="",r=[];this.iterator.forEachNode(NodeFilter.SHOW_TEXT,n=>{r.push({start:t.length,end:(t+=n.textContent).length,node:n})},n=>this.matchesExclude(n.parentNode)?NodeFilter.FILTER_REJECT:NodeFilter.FILTER_ACCEPT,()=>{e({value:t,nodes:r})})}matchesExclude(e){return ce.matches(e,this.opt.exclude.concat(["script","style","title","head","html"]))}wrapRangeInTextNode(e,t,r){const n=this.opt.element?this.opt.element:"mark",a=e.splitText(t),i=a.splitText(r-t);let s=document.createElement(n);return s.setAttribute("data-markjs","true"),this.opt.className&&s.setAttribute("class",this.opt.className),s.textContent=a.textContent,a.parentNode.replaceChild(s,a),i}wrapRangeInMappedTextNode(e,t,r,n,a){e.nodes.every((i,s)=>{const u=e.nodes[s+1];if(typeof u>"u"||u.start>t){if(!n(i.node))return!1;const l=t-i.start,d=(r>i.end?i.end:r)-i.start,h=e.value.substr(0,i.start),v=e.value.substr(d+i.start);if(i.node=this.wrapRangeInTextNode(i.node,l,d),e.value=h+v,e.nodes.forEach((m,g)=>{g>=s&&(e.nodes[g].start>0&&g!==s&&(e.nodes[g].start-=d),e.nodes[g].end-=d)}),r-=d,a(i.node.previousSibling,i.start),r>i.end)t=i.end;else return!1}return!0})}wrapMatches(e,t,r,n,a){const i=t===0?0:t+1;this.getTextNodes(s=>{s.nodes.forEach(u=>{u=u.node;let l;for(;(l=e.exec(u.textContent))!==null&&l[i]!=="";){if(!r(l[i],u))continue;let d=l.index;if(i!==0)for(let h=1;h{let u;for(;(u=e.exec(s.value))!==null&&u[i]!=="";){let l=u.index;if(i!==0)for(let h=1;hr(u[i],h),(h,v)=>{e.lastIndex=v,n(h)})}a()})}wrapRangeFromIndex(e,t,r,n){this.getTextNodes(a=>{const i=a.value.length;e.forEach((s,u)=>{let{start:l,end:d,valid:h}=this.checkWhitespaceRanges(s,i,a.value);h&&this.wrapRangeInMappedTextNode(a,l,d,v=>t(v,s,a.value.substring(l,d),u),v=>{r(v,s)})}),n()})}unwrapMatches(e){const t=e.parentNode;let r=document.createDocumentFragment();for(;e.firstChild;)r.appendChild(e.removeChild(e.firstChild));t.replaceChild(r,e),this.ie?this.normalizeTextNode(t):t.normalize()}normalizeTextNode(e){if(e){if(e.nodeType===3)for(;e.nextSibling&&e.nextSibling.nodeType===3;)e.nodeValue+=e.nextSibling.nodeValue,e.parentNode.removeChild(e.nextSibling);else this.normalizeTextNode(e.firstChild);this.normalizeTextNode(e.nextSibling)}}markRegExp(e,t){this.opt=t,this.log(`Searching with expression "${e}"`);let r=0,n="wrapMatches";const a=i=>{r++,this.opt.each(i)};this.opt.acrossElements&&(n="wrapMatchesAcrossElements"),this[n](e,this.opt.ignoreGroups,(i,s)=>this.opt.filter(s,i,r),a,()=>{r===0&&this.opt.noMatch(e),this.opt.done(r)})}mark(e,t){this.opt=t;let r=0,n="wrapMatches";const{keywords:a,length:i}=this.getSeparatedKeywords(typeof e=="string"?[e]:e),s=this.opt.caseSensitive?"":"i",u=l=>{let d=new RegExp(this.createRegExp(l),`gm${s}`),h=0;this.log(`Searching with expression "${d}"`),this[n](d,1,(v,m)=>this.opt.filter(m,l,r,h),v=>{h++,r++,this.opt.each(v)},()=>{h===0&&this.opt.noMatch(l),a[i-1]===l?this.opt.done(r):u(a[a.indexOf(l)+1])})};this.opt.acrossElements&&(n="wrapMatchesAcrossElements"),i===0?this.opt.done(r):u(a[0])}markRanges(e,t){this.opt=t;let r=0,n=this.checkRanges(e);n&&n.length?(this.log("Starting to mark with the following ranges: "+JSON.stringify(n)),this.wrapRangeFromIndex(n,(a,i,s,u)=>this.opt.filter(a,i,s,u),(a,i)=>{r++,this.opt.each(a,i)},()=>{this.opt.done(r)})):this.opt.done(r)}unmark(e){this.opt=e;let t=this.opt.element?this.opt.element:"*";t+="[data-markjs]",this.opt.className&&(t+=`.${this.opt.className}`),this.log(`Removal selector "${t}"`),this.iterator.forEachNode(NodeFilter.SHOW_ELEMENT,r=>{this.unwrapMatches(r)},r=>{const n=ce.matches(r,t),a=this.matchesExclude(r);return!n||a?NodeFilter.FILTER_REJECT:NodeFilter.FILTER_ACCEPT},this.opt.done)}};function Or(o){const e=new kr(o);return this.mark=(t,r)=>(e.mark(t,r),this),this.markRegExp=(t,r)=>(e.markRegExp(t,r),this),this.markRanges=(t,r)=>(e.markRanges(t,r),this),this.unmark=t=>(e.unmark(t),this),this}var $=function(){return $=Object.assign||function(e){for(var t,r=1,n=arguments.length;r0&&a[a.length-1])&&(l[0]===6||l[0]===2)){t=0;continue}if(l[0]===3&&(!a||l[1]>a[0]&&l[1]=o.length&&(o=void 0),{value:o&&o[r++],done:!o}}};throw new TypeError(e?"Object is not iterable.":"Symbol.iterator is not defined.")}function W(o,e){var t=typeof Symbol=="function"&&o[Symbol.iterator];if(!t)return o;var r=t.call(o),n,a=[],i;try{for(;(e===void 0||e-- >0)&&!(n=r.next()).done;)a.push(n.value)}catch(s){i={error:s}}finally{try{n&&!n.done&&(t=r.return)&&t.call(r)}finally{if(i)throw i.error}}return a}var Mr="ENTRIES",xt="KEYS",Ft="VALUES",Q="",_e=function(){function o(e,t){var r=e._tree,n=Array.from(r.keys());this.set=e,this._type=t,this._path=n.length>0?[{node:r,keys:n}]:[]}return o.prototype.next=function(){var e=this.dive();return this.backtrack(),e},o.prototype.dive=function(){if(this._path.length===0)return{done:!0,value:void 0};var e=le(this._path),t=e.node,r=e.keys;if(le(r)===Q)return{done:!1,value:this.result()};var n=t.get(le(r));return this._path.push({node:n,keys:Array.from(n.keys())}),this.dive()},o.prototype.backtrack=function(){if(this._path.length!==0){var e=le(this._path).keys;e.pop(),!(e.length>0)&&(this._path.pop(),this.backtrack())}},o.prototype.key=function(){return this.set._prefix+this._path.map(function(e){var t=e.keys;return le(t)}).filter(function(e){return e!==Q}).join("")},o.prototype.value=function(){return le(this._path).node.get(Q)},o.prototype.result=function(){switch(this._type){case Ft:return this.value();case xt:return this.key();default:return[this.key(),this.value()]}},o.prototype[Symbol.iterator]=function(){return this},o}(),le=function(o){return o[o.length-1]},Lr=function(o,e,t){var r=new Map;if(e===void 0)return r;for(var n=e.length+1,a=n+t,i=new Uint8Array(a*n).fill(t+1),s=0;st)continue e}Et(o.get(m),e,t,r,n,b,i,s+m)}}}catch(c){u={error:c}}finally{try{v&&!v.done&&(l=h.return)&&l.call(h)}finally{if(u)throw u.error}}},Me=function(){function o(e,t){e===void 0&&(e=new Map),t===void 0&&(t=""),this._size=void 0,this._tree=e,this._prefix=t}return o.prototype.atPrefix=function(e){var t,r;if(!e.startsWith(this._prefix))throw new Error("Mismatched prefix");var n=W(De(this._tree,e.slice(this._prefix.length)),2),a=n[0],i=n[1];if(a===void 0){var s=W(Ue(i),2),u=s[0],l=s[1];try{for(var d=D(u.keys()),h=d.next();!h.done;h=d.next()){var v=h.value;if(v!==Q&&v.startsWith(l)){var m=new Map;return m.set(v.slice(l.length),u.get(v)),new o(m,e)}}}catch(g){t={error:g}}finally{try{h&&!h.done&&(r=d.return)&&r.call(d)}finally{if(t)throw t.error}}}return new o(a,e)},o.prototype.clear=function(){this._size=void 0,this._tree.clear()},o.prototype.delete=function(e){return this._size=void 0,Pr(this._tree,e)},o.prototype.entries=function(){return new _e(this,Mr)},o.prototype.forEach=function(e){var t,r;try{for(var n=D(this),a=n.next();!a.done;a=n.next()){var i=W(a.value,2),s=i[0],u=i[1];e(s,u,this)}}catch(l){t={error:l}}finally{try{a&&!a.done&&(r=n.return)&&r.call(n)}finally{if(t)throw t.error}}},o.prototype.fuzzyGet=function(e,t){return Lr(this._tree,e,t)},o.prototype.get=function(e){var t=We(this._tree,e);return t!==void 0?t.get(Q):void 0},o.prototype.has=function(e){var t=We(this._tree,e);return t!==void 0&&t.has(Q)},o.prototype.keys=function(){return new _e(this,xt)},o.prototype.set=function(e,t){if(typeof e!="string")throw new Error("key must be a string");this._size=void 0;var r=Le(this._tree,e);return r.set(Q,t),this},Object.defineProperty(o.prototype,"size",{get:function(){if(this._size)return this._size;this._size=0;for(var e=this.entries();!e.next().done;)this._size+=1;return this._size},enumerable:!1,configurable:!0}),o.prototype.update=function(e,t){if(typeof e!="string")throw new Error("key must be a string");this._size=void 0;var r=Le(this._tree,e);return r.set(Q,t(r.get(Q))),this},o.prototype.fetch=function(e,t){if(typeof e!="string")throw new Error("key must be a string");this._size=void 0;var r=Le(this._tree,e),n=r.get(Q);return n===void 0&&r.set(Q,n=t()),n},o.prototype.values=function(){return new _e(this,Ft)},o.prototype[Symbol.iterator]=function(){return this.entries()},o.from=function(e){var t,r,n=new o;try{for(var a=D(e),i=a.next();!i.done;i=a.next()){var s=W(i.value,2),u=s[0],l=s[1];n.set(u,l)}}catch(d){t={error:d}}finally{try{i&&!i.done&&(r=a.return)&&r.call(a)}finally{if(t)throw t.error}}return n},o.fromObject=function(e){return o.from(Object.entries(e))},o}(),De=function(o,e,t){var r,n;if(t===void 0&&(t=[]),e.length===0||o==null)return[o,t];try{for(var a=D(o.keys()),i=a.next();!i.done;i=a.next()){var s=i.value;if(s!==Q&&e.startsWith(s))return t.push([o,s]),De(o.get(s),e.slice(s.length),t)}}catch(u){r={error:u}}finally{try{i&&!i.done&&(n=a.return)&&n.call(a)}finally{if(r)throw r.error}}return t.push([o,e]),De(void 0,"",t)},We=function(o,e){var t,r;if(e.length===0||o==null)return o;try{for(var n=D(o.keys()),a=n.next();!a.done;a=n.next()){var i=a.value;if(i!==Q&&e.startsWith(i))return We(o.get(i),e.slice(i.length))}}catch(s){t={error:s}}finally{try{a&&!a.done&&(r=n.return)&&r.call(n)}finally{if(t)throw t.error}}},Le=function(o,e){var t,r,n=e.length;e:for(var a=0;o&&a0)throw new Error("Expected documents to be present. Omit the argument to remove all documents.");this._index=new Me,this._documentCount=0,this._documentIds=new Map,this._idToShortId=new Map,this._fieldLength=new Map,this._avgFieldLength=[],this._storedFields=new Map,this._nextId=0}},o.prototype.discard=function(e){var t=this,r=this._idToShortId.get(e);if(r==null)throw new Error("MiniSearch: cannot discard document with ID ".concat(e,": it is not in the index"));this._idToShortId.delete(e),this._documentIds.delete(r),this._storedFields.delete(r),(this._fieldLength.get(r)||[]).forEach(function(n,a){t.removeFieldLength(r,a,t._documentCount,n)}),this._fieldLength.delete(r),this._documentCount-=1,this._dirtCount+=1,this.maybeAutoVacuum()},o.prototype.maybeAutoVacuum=function(){if(this._options.autoVacuum!==!1){var e=this._options.autoVacuum,t=e.minDirtFactor,r=e.minDirtCount,n=e.batchSize,a=e.batchWait;this.conditionalVacuum({batchSize:n,batchWait:a},{minDirtCount:r,minDirtFactor:t})}},o.prototype.discardAll=function(e){var t,r,n=this._options.autoVacuum;try{this._options.autoVacuum=!1;try{for(var a=D(e),i=a.next();!i.done;i=a.next()){var s=i.value;this.discard(s)}}catch(u){t={error:u}}finally{try{i&&!i.done&&(r=a.return)&&r.call(a)}finally{if(t)throw t.error}}}finally{this._options.autoVacuum=n}this.maybeAutoVacuum()},o.prototype.replace=function(e){var t=this._options,r=t.idField,n=t.extractField,a=n(e,r);this.discard(a),this.add(e)},o.prototype.vacuum=function(e){return e===void 0&&(e={}),this.conditionalVacuum(e)},o.prototype.conditionalVacuum=function(e,t){var r=this;return this._currentVacuum?(this._enqueuedVacuumConditions=this._enqueuedVacuumConditions&&t,this._enqueuedVacuum!=null?this._enqueuedVacuum:(this._enqueuedVacuum=this._currentVacuum.then(function(){var n=r._enqueuedVacuumConditions;return r._enqueuedVacuumConditions=Je,r.performVacuuming(e,n)}),this._enqueuedVacuum)):this.vacuumConditionsMet(t)===!1?Promise.resolve():(this._currentVacuum=this.performVacuuming(e),this._currentVacuum)},o.prototype.performVacuuming=function(e,t){return Rr(this,void 0,void 0,function(){var r,n,a,i,s,u,l,d,h,v,m,g,b,x,S,T,A,_,L,P,I,E,O,R,F;return _r(this,function(f){switch(f.label){case 0:if(r=this._dirtCount,!this.vacuumConditionsMet(t))return[3,10];n=e.batchSize||Ke.batchSize,a=e.batchWait||Ke.batchWait,i=1,f.label=1;case 1:f.trys.push([1,7,8,9]),s=D(this._index),u=s.next(),f.label=2;case 2:if(u.done)return[3,6];l=W(u.value,2),d=l[0],h=l[1];try{for(v=(E=void 0,D(h)),m=v.next();!m.done;m=v.next()){g=W(m.value,2),b=g[0],x=g[1];try{for(S=(R=void 0,D(x)),T=S.next();!T.done;T=S.next())A=W(T.value,1),_=A[0],!this._documentIds.has(_)&&(x.size<=1?h.delete(b):x.delete(_))}catch(c){R={error:c}}finally{try{T&&!T.done&&(F=S.return)&&F.call(S)}finally{if(R)throw R.error}}}}catch(c){E={error:c}}finally{try{m&&!m.done&&(O=v.return)&&O.call(v)}finally{if(E)throw E.error}}return this._index.get(d).size===0&&this._index.delete(d),i%n!==0?[3,4]:[4,new Promise(function(c){return setTimeout(c,a)})];case 3:f.sent(),f.label=4;case 4:i+=1,f.label=5;case 5:return u=s.next(),[3,2];case 6:return[3,9];case 7:return L=f.sent(),P={error:L},[3,9];case 8:try{u&&!u.done&&(I=s.return)&&I.call(s)}finally{if(P)throw P.error}return[7];case 9:this._dirtCount-=r,f.label=10;case 10:return[4,null];case 11:return f.sent(),this._currentVacuum=this._enqueuedVacuum,this._enqueuedVacuum=null,[2]}})})},o.prototype.vacuumConditionsMet=function(e){if(e==null)return!0;var t=e.minDirtCount,r=e.minDirtFactor;return t=t||Be.minDirtCount,r=r||Be.minDirtFactor,this.dirtCount>=t&&this.dirtFactor>=r},Object.defineProperty(o.prototype,"isVacuuming",{get:function(){return this._currentVacuum!=null},enumerable:!1,configurable:!0}),Object.defineProperty(o.prototype,"dirtCount",{get:function(){return this._dirtCount},enumerable:!1,configurable:!0}),Object.defineProperty(o.prototype,"dirtFactor",{get:function(){return this._dirtCount/(1+this._documentCount+this._dirtCount)},enumerable:!1,configurable:!0}),o.prototype.has=function(e){return this._idToShortId.has(e)},o.prototype.getStoredFields=function(e){var t=this._idToShortId.get(e);if(t!=null)return this._storedFields.get(t)},o.prototype.search=function(e,t){var r,n;t===void 0&&(t={});var a=this.executeQuery(e,t),i=[];try{for(var s=D(a),u=s.next();!u.done;u=s.next()){var l=W(u.value,2),d=l[0],h=l[1],v=h.score,m=h.terms,g=h.match,b=m.length||1,x={id:this._documentIds.get(d),score:v*b,terms:Object.keys(g),queryTerms:m,match:g};Object.assign(x,this._storedFields.get(d)),(t.filter==null||t.filter(x))&&i.push(x)}}catch(S){r={error:S}}finally{try{u&&!u.done&&(n=s.return)&&n.call(s)}finally{if(r)throw r.error}}return e===o.wildcard&&t.boostDocument==null&&this._options.searchOptions.boostDocument==null||i.sort(dt),i},o.prototype.autoSuggest=function(e,t){var r,n,a,i;t===void 0&&(t={}),t=$($({},this._options.autoSuggestOptions),t);var s=new Map;try{for(var u=D(this.search(e,t)),l=u.next();!l.done;l=u.next()){var d=l.value,h=d.score,v=d.terms,m=v.join(" "),g=s.get(m);g!=null?(g.score+=h,g.count+=1):s.set(m,{score:h,terms:v,count:1})}}catch(L){r={error:L}}finally{try{l&&!l.done&&(n=u.return)&&n.call(u)}finally{if(r)throw r.error}}var b=[];try{for(var x=D(s),S=x.next();!S.done;S=x.next()){var T=W(S.value,2),g=T[0],A=T[1],h=A.score,v=A.terms,_=A.count;b.push({suggestion:g,terms:v,score:h/_})}}catch(L){a={error:L}}finally{try{S&&!S.done&&(i=x.return)&&i.call(x)}finally{if(a)throw a.error}}return b.sort(dt),b},Object.defineProperty(o.prototype,"documentCount",{get:function(){return this._documentCount},enumerable:!1,configurable:!0}),Object.defineProperty(o.prototype,"termCount",{get:function(){return this._index.size},enumerable:!1,configurable:!0}),o.loadJSON=function(e,t){if(t==null)throw new Error("MiniSearch: loadJSON should be given the same options used when serializing the index");return this.loadJS(JSON.parse(e),t)},o.getDefault=function(e){if(ze.hasOwnProperty(e))return Pe(ze,e);throw new Error('MiniSearch: unknown option "'.concat(e,'"'))},o.loadJS=function(e,t){var r,n,a,i,s,u,l=e.index,d=e.documentCount,h=e.nextId,v=e.documentIds,m=e.fieldIds,g=e.fieldLength,b=e.averageFieldLength,x=e.storedFields,S=e.dirtCount,T=e.serializationVersion;if(T!==1&&T!==2)throw new Error("MiniSearch: cannot deserialize an index created with an incompatible version");var A=new o(t);A._documentCount=d,A._nextId=h,A._documentIds=Ae(v),A._idToShortId=new Map,A._fieldIds=m,A._fieldLength=Ae(g),A._avgFieldLength=b,A._storedFields=Ae(x),A._dirtCount=S||0,A._index=new Me;try{for(var _=D(A._documentIds),L=_.next();!L.done;L=_.next()){var P=W(L.value,2),I=P[0],E=P[1];A._idToShortId.set(E,I)}}catch(y){r={error:y}}finally{try{L&&!L.done&&(n=_.return)&&n.call(_)}finally{if(r)throw r.error}}try{for(var O=D(l),R=O.next();!R.done;R=O.next()){var F=W(R.value,2),f=F[0],c=F[1],p=new Map;try{for(var C=(s=void 0,D(Object.keys(c))),N=C.next();!N.done;N=C.next()){var M=N.value,z=c[M];T===1&&(z=z.ds),p.set(parseInt(M,10),Ae(z))}}catch(y){s={error:y}}finally{try{N&&!N.done&&(u=C.return)&&u.call(C)}finally{if(s)throw s.error}}A._index.set(f,p)}}catch(y){a={error:y}}finally{try{R&&!R.done&&(i=O.return)&&i.call(O)}finally{if(a)throw a.error}}return A},o.prototype.executeQuery=function(e,t){var r=this;if(t===void 0&&(t={}),e===o.wildcard)return this.executeWildcardQuery(t);if(typeof e!="string"){var n=$($($({},t),e),{queries:void 0}),a=e.queries.map(function(x){return r.executeQuery(x,n)});return this.combineResults(a,n.combineWith)}var i=this._options,s=i.tokenize,u=i.processTerm,l=i.searchOptions,d=$($({tokenize:s,processTerm:u},l),t),h=d.tokenize,v=d.processTerm,m=h(e).flatMap(function(x){return v(x)}).filter(function(x){return!!x}),g=m.map(Kr(d)),b=g.map(function(x){return r.executeQuerySpec(x,d)});return this.combineResults(b,d.combineWith)},o.prototype.executeQuerySpec=function(e,t){var r,n,a,i,s=$($({},this._options.searchOptions),t),u=(s.fields||this._options.fields).reduce(function(M,z){var y;return $($({},M),(y={},y[z]=Pe(s.boost,z)||1,y))},{}),l=s.boostDocument,d=s.weights,h=s.maxFuzzy,v=s.bm25,m=$($({},ft.weights),d),g=m.fuzzy,b=m.prefix,x=this._index.get(e.term),S=this.termResults(e.term,e.term,1,x,u,l,v),T,A;if(e.prefix&&(T=this._index.atPrefix(e.term)),e.fuzzy){var _=e.fuzzy===!0?.2:e.fuzzy,L=_<1?Math.min(h,Math.round(e.term.length*_)):_;L&&(A=this._index.fuzzyGet(e.term,L))}if(T)try{for(var P=D(T),I=P.next();!I.done;I=P.next()){var E=W(I.value,2),O=E[0],R=E[1],F=O.length-e.term.length;if(F){A==null||A.delete(O);var f=b*O.length/(O.length+.3*F);this.termResults(e.term,O,f,R,u,l,v,S)}}}catch(M){r={error:M}}finally{try{I&&!I.done&&(n=P.return)&&n.call(P)}finally{if(r)throw r.error}}if(A)try{for(var c=D(A.keys()),p=c.next();!p.done;p=c.next()){var O=p.value,C=W(A.get(O),2),N=C[0],F=C[1];if(F){var f=g*O.length/(O.length+F);this.termResults(e.term,O,f,N,u,l,v,S)}}}catch(M){a={error:M}}finally{try{p&&!p.done&&(i=c.return)&&i.call(c)}finally{if(a)throw a.error}}return S},o.prototype.executeWildcardQuery=function(e){var t,r,n=new Map,a=$($({},this._options.searchOptions),e);try{for(var i=D(this._documentIds),s=i.next();!s.done;s=i.next()){var u=W(s.value,2),l=u[0],d=u[1],h=a.boostDocument?a.boostDocument(d,"",this._storedFields.get(l)):1;n.set(l,{score:h,terms:[],match:{}})}}catch(v){t={error:v}}finally{try{s&&!s.done&&(r=i.return)&&r.call(i)}finally{if(t)throw t.error}}return n},o.prototype.combineResults=function(e,t){if(t===void 0&&(t=je),e.length===0)return new Map;var r=t.toLowerCase();return e.reduce(Vr[r])||new Map},o.prototype.toJSON=function(){var e,t,r,n,a=[];try{for(var i=D(this._index),s=i.next();!s.done;s=i.next()){var u=W(s.value,2),l=u[0],d=u[1],h={};try{for(var v=(r=void 0,D(d)),m=v.next();!m.done;m=v.next()){var g=W(m.value,2),b=g[0],x=g[1];h[b]=Object.fromEntries(x)}}catch(S){r={error:S}}finally{try{m&&!m.done&&(n=v.return)&&n.call(v)}finally{if(r)throw r.error}}a.push([l,h])}}catch(S){e={error:S}}finally{try{s&&!s.done&&(t=i.return)&&t.call(i)}finally{if(e)throw e.error}}return{documentCount:this._documentCount,nextId:this._nextId,documentIds:Object.fromEntries(this._documentIds),fieldIds:this._fieldIds,fieldLength:Object.fromEntries(this._fieldLength),averageFieldLength:this._avgFieldLength,storedFields:Object.fromEntries(this._storedFields),dirtCount:this._dirtCount,index:a,serializationVersion:2}},o.prototype.termResults=function(e,t,r,n,a,i,s,u){var l,d,h,v,m;if(u===void 0&&(u=new Map),n==null)return u;try{for(var g=D(Object.keys(a)),b=g.next();!b.done;b=g.next()){var x=b.value,S=a[x],T=this._fieldIds[x],A=n.get(T);if(A!=null){var _=A.size,L=this._avgFieldLength[T];try{for(var P=(h=void 0,D(A.keys())),I=P.next();!I.done;I=P.next()){var E=I.value;if(!this._documentIds.has(E)){this.removeTerm(T,E,t),_-=1;continue}var O=i?i(this._documentIds.get(E),t,this._storedFields.get(E)):1;if(O){var R=A.get(E),F=this._fieldLength.get(E)[T],f=Wr(R,_,this._documentCount,F,L,s),c=r*S*O*f,p=u.get(E);if(p){p.score+=c,Ur(p.terms,e);var C=Pe(p.match,t);C?C.push(x):p.match[t]=[x]}else u.set(E,{score:c,terms:[e],match:(m={},m[t]=[x],m)})}}}catch(N){h={error:N}}finally{try{I&&!I.done&&(v=P.return)&&v.call(P)}finally{if(h)throw h.error}}}}}catch(N){l={error:N}}finally{try{b&&!b.done&&(d=g.return)&&d.call(g)}finally{if(l)throw l.error}}return u},o.prototype.addTerm=function(e,t,r){var n=this._index.fetch(r,vt),a=n.get(e);if(a==null)a=new Map,a.set(t,1),n.set(e,a);else{var i=a.get(t);a.set(t,(i||0)+1)}},o.prototype.removeTerm=function(e,t,r){if(!this._index.has(r)){this.warnDocumentChanged(t,e,r);return}var n=this._index.fetch(r,vt),a=n.get(e);a==null||a.get(t)==null?this.warnDocumentChanged(t,e,r):a.get(t)<=1?a.size<=1?n.delete(e):a.delete(t):a.set(t,a.get(t)-1),this._index.get(r).size===0&&this._index.delete(r)},o.prototype.warnDocumentChanged=function(e,t,r){var n,a;try{for(var i=D(Object.keys(this._fieldIds)),s=i.next();!s.done;s=i.next()){var u=s.value;if(this._fieldIds[u]===t){this._options.logger("warn","MiniSearch: document with ID ".concat(this._documentIds.get(e),' has changed before removal: term "').concat(r,'" was not present in field "').concat(u,'". Removing a document after it has changed can corrupt the index!'),"version_conflict");return}}}catch(l){n={error:l}}finally{try{s&&!s.done&&(a=i.return)&&a.call(i)}finally{if(n)throw n.error}}},o.prototype.addDocumentId=function(e){var t=this._nextId;return this._idToShortId.set(e,t),this._documentIds.set(t,e),this._documentCount+=1,this._nextId+=1,t},o.prototype.addFields=function(e){for(var t=0;t(Qt("data-v-639d7ab9"),o=o(),Ht(),o),Qr=["aria-owns"],Hr={class:"shell"},qr=["title"],Yr=Y(()=>k("span",{"aria-hidden":"true",class:"vpi-search search-icon local-search-icon"},null,-1)),Zr=[Yr],Xr={class:"search-actions before"},ea=["title"],ta=Y(()=>k("span",{class:"vpi-arrow-left local-search-icon"},null,-1)),ra=[ta],aa=["placeholder"],na={class:"search-actions"},ia=["title"],oa=Y(()=>k("span",{class:"vpi-layout-list local-search-icon"},null,-1)),sa=[oa],ua=["disabled","title"],la=Y(()=>k("span",{class:"vpi-delete local-search-icon"},null,-1)),ca=[la],fa=["id","role","aria-labelledby"],ha=["aria-selected"],da=["href","aria-label","onMouseenter","onFocusin"],va={class:"titles"},pa=Y(()=>k("span",{class:"title-icon"},"#",-1)),ya=["innerHTML"],ma=Y(()=>k("span",{class:"vpi-chevron-right local-search-icon"},null,-1)),ga={class:"title main"},ba=["innerHTML"],wa={key:0,class:"excerpt-wrapper"},xa={key:0,class:"excerpt",inert:""},Fa=["innerHTML"],Ea=Y(()=>k("div",{class:"excerpt-gradient-bottom"},null,-1)),Sa=Y(()=>k("div",{class:"excerpt-gradient-top"},null,-1)),Aa={key:0,class:"no-results"},Ta={class:"search-keyboard-shortcuts"},Na=["aria-label"],Ca=Y(()=>k("span",{class:"vpi-arrow-up navigate-icon"},null,-1)),Ia=[Ca],Da=["aria-label"],ka=Y(()=>k("span",{class:"vpi-arrow-down navigate-icon"},null,-1)),Oa=[ka],Ra=["aria-label"],_a=Y(()=>k("span",{class:"vpi-corner-down-left navigate-icon"},null,-1)),Ma=[_a],La=["aria-label"],Pa=Ot({__name:"VPLocalSearchBox",emits:["close"],setup(o,{emit:e}){var M,z;const t=we(),r=we(),n=we(ar),a=tr(),{activate:i}=Dr(t,{immediate:!0,allowOutsideClick:!0,clickOutsideDeactivates:!0,escapeDeactivates:!0}),{localeIndex:s,theme:u}=a,l=et(async()=>{var y,w,B,U,K,J,V,j,H;return nt(Br.loadJSON((B=await((w=(y=n.value)[s.value])==null?void 0:w.call(y)))==null?void 0:B.default,{fields:["title","titles","text"],storeFields:["title","titles"],searchOptions:{fuzzy:.2,prefix:!0,boost:{title:4,text:2,titles:1},...((U=u.value.search)==null?void 0:U.provider)==="local"&&((J=(K=u.value.search.options)==null?void 0:K.miniSearch)==null?void 0:J.searchOptions)},...((V=u.value.search)==null?void 0:V.provider)==="local"&&((H=(j=u.value.search.options)==null?void 0:j.miniSearch)==null?void 0:H.options)}))}),h=xe(()=>{var y,w;return((y=u.value.search)==null?void 0:y.provider)==="local"&&((w=u.value.search.options)==null?void 0:w.disableQueryPersistence)===!0}).value?ie(""):Rt("vitepress:local-search-filter",""),v=_t("vitepress:local-search-detailed-list",((M=u.value.search)==null?void 0:M.provider)==="local"&&((z=u.value.search.options)==null?void 0:z.detailedView)===!0),m=xe(()=>{var y,w,B;return((y=u.value.search)==null?void 0:y.provider)==="local"&&(((w=u.value.search.options)==null?void 0:w.disableDetailedView)===!0||((B=u.value.search.options)==null?void 0:B.detailedView)===!1)}),g=xe(()=>{var w,B,U,K,J,V,j;const y=((w=u.value.search)==null?void 0:w.options)??u.value.algolia;return((J=(K=(U=(B=y==null?void 0:y.locales)==null?void 0:B[s.value])==null?void 0:U.translations)==null?void 0:K.button)==null?void 0:J.buttonText)||((j=(V=y==null?void 0:y.translations)==null?void 0:V.button)==null?void 0:j.buttonText)||"Search"});Mt(()=>{m.value&&(v.value=!1)});const b=we([]),x=ie(!1);Ve(h,()=>{x.value=!1});const S=et(async()=>{if(r.value)return nt(new Or(r.value))},null),T=new Gr(16);Lt(()=>[l.value,h.value,v.value],async([y,w,B],U,K)=>{var ge,Ge,Qe,He;(U==null?void 0:U[0])!==y&&T.clear();let J=!1;if(K(()=>{J=!0}),!y)return;b.value=y.search(w).slice(0,16),x.value=!0;const V=B?await Promise.all(b.value.map(q=>A(q.id))):[];if(J)return;for(const{id:q,mod:re}of V){const ae=q.slice(0,q.indexOf("#"));let ee=T.get(ae);if(ee)continue;ee=new Map,T.set(ae,ee);const Z=re.default??re;if(Z!=null&&Z.render||Z!=null&&Z.setup){const ne=qt(Z);ne.config.warnHandler=()=>{},ne.provide(Yt,a),Object.defineProperties(ne.config.globalProperties,{$frontmatter:{get(){return a.frontmatter.value}},$params:{get(){return a.page.value.params}}});const qe=document.createElement("div");ne.mount(qe),qe.querySelectorAll("h1, h2, h3, h4, h5, h6").forEach(fe=>{var Xe;const be=(Xe=fe.querySelector("a"))==null?void 0:Xe.getAttribute("href"),Ye=(be==null?void 0:be.startsWith("#"))&&be.slice(1);if(!Ye)return;let Ze="";for(;(fe=fe.nextElementSibling)&&!/^h[1-6]$/i.test(fe.tagName);)Ze+=fe.outerHTML;ee.set(Ye,Ze)}),ne.unmount()}if(J)return}const j=new Set;if(b.value=b.value.map(q=>{const[re,ae]=q.id.split("#"),ee=T.get(re),Z=(ee==null?void 0:ee.get(ae))??"";for(const ne in q.match)j.add(ne);return{...q,text:Z}}),await he(),J)return;await new Promise(q=>{var re;(re=S.value)==null||re.unmark({done:()=>{var ae;(ae=S.value)==null||ae.markRegExp(N(j),{done:q})}})});const H=((ge=t.value)==null?void 0:ge.querySelectorAll(".result .excerpt"))??[];for(const q of H)(Ge=q.querySelector('mark[data-markjs="true"]'))==null||Ge.scrollIntoView({block:"center"});(He=(Qe=r.value)==null?void 0:Qe.firstElementChild)==null||He.scrollIntoView({block:"start"})},{debounce:200,immediate:!0});async function A(y){const w=Zt(y.slice(0,y.indexOf("#")));try{if(!w)throw new Error(`Cannot find file for id: ${y}`);return{id:y,mod:await import(w)}}catch(B){return console.error(B),{id:y,mod:{}}}}const _=ie(),L=xe(()=>{var y;return((y=h.value)==null?void 0:y.length)<=0});function P(y=!0){var w,B;(w=_.value)==null||w.focus(),y&&((B=_.value)==null||B.select())}Oe(()=>{P()});function I(y){y.pointerType==="mouse"&&P()}const E=ie(-1),O=ie(!1);Ve(b,y=>{E.value=y.length?0:-1,R()});function R(){he(()=>{const y=document.querySelector(".result.selected");y==null||y.scrollIntoView({block:"nearest"})})}Fe("ArrowUp",y=>{y.preventDefault(),E.value--,E.value<0&&(E.value=b.value.length-1),O.value=!0,R()}),Fe("ArrowDown",y=>{y.preventDefault(),E.value++,E.value>=b.value.length&&(E.value=0),O.value=!0,R()});const F=Pt();Fe("Enter",y=>{if(y.isComposing||y.target instanceof HTMLButtonElement&&y.target.type!=="submit")return;const w=b.value[E.value];if(y.target instanceof HTMLInputElement&&!w){y.preventDefault();return}w&&(F.go(w.id),e("close"))}),Fe("Escape",()=>{e("close")});const c=rr({modal:{displayDetails:"Display detailed list",resetButtonTitle:"Reset search",backButtonTitle:"Close search",noResultsText:"No results for",footer:{selectText:"to select",selectKeyAriaLabel:"enter",navigateText:"to navigate",navigateUpKeyAriaLabel:"up arrow",navigateDownKeyAriaLabel:"down arrow",closeText:"to close",closeKeyAriaLabel:"escape"}}});Oe(()=>{window.history.pushState(null,"",null)}),zt("popstate",y=>{y.preventDefault(),e("close")});const p=Bt(Vt?document.body:null);Oe(()=>{he(()=>{p.value=!0,he().then(()=>i())})}),$t(()=>{p.value=!1});function C(){h.value="",he().then(()=>P(!1))}function N(y){return new RegExp([...y].sort((w,B)=>B.length-w.length).map(w=>`(${Xt(w)})`).join("|"),"gi")}return(y,w)=>{var B,U,K,J;return X(),Wt(Gt,{to:"body"},[k("div",{ref_key:"el",ref:t,role:"button","aria-owns":(B=b.value)!=null&&B.length?"localsearch-list":void 0,"aria-expanded":"true","aria-haspopup":"listbox","aria-labelledby":"localsearch-label",class:"VPLocalSearchBox"},[k("div",{class:"backdrop",onClick:w[0]||(w[0]=V=>y.$emit("close"))}),k("div",Hr,[k("form",{class:"search-bar",onPointerup:w[4]||(w[4]=V=>I(V)),onSubmit:w[5]||(w[5]=Kt(()=>{},["prevent"]))},[k("label",{title:g.value,id:"localsearch-label",for:"localsearch-input"},Zr,8,qr),k("div",Xr,[k("button",{class:"back-button",title:G(c)("modal.backButtonTitle"),onClick:w[1]||(w[1]=V=>y.$emit("close"))},ra,8,ea)]),Jt(k("input",{ref_key:"searchInput",ref:_,"onUpdate:modelValue":w[2]||(w[2]=V=>jt(h)?h.value=V:null),placeholder:g.value,id:"localsearch-input","aria-labelledby":"localsearch-label",class:"search-input"},null,8,aa),[[Ut,G(h)]]),k("div",na,[m.value?Ee("",!0):(X(),te("button",{key:0,class:tt(["toggle-layout-button",{"detailed-list":G(v)}]),type:"button",title:G(c)("modal.displayDetails"),onClick:w[3]||(w[3]=V=>E.value>-1&&(v.value=!G(v)))},sa,10,ia)),k("button",{class:"clear-button",type:"reset",disabled:L.value,title:G(c)("modal.resetButtonTitle"),onClick:C},ca,8,ua)])],32),k("ul",{ref_key:"resultsEl",ref:r,id:(U=b.value)!=null&&U.length?"localsearch-list":void 0,role:(K=b.value)!=null&&K.length?"listbox":void 0,"aria-labelledby":(J=b.value)!=null&&J.length?"localsearch-label":void 0,class:"results",onMousemove:w[7]||(w[7]=V=>O.value=!1)},[(X(!0),te(at,null,rt(b.value,(V,j)=>(X(),te("li",{key:V.id,role:"option","aria-selected":E.value===j?"true":"false"},[k("a",{href:V.id,class:tt(["result",{selected:E.value===j}]),"aria-label":[...V.titles,V.title].join(" > "),onMouseenter:H=>!O.value&&(E.value=j),onFocusin:H=>E.value=j,onClick:w[6]||(w[6]=H=>y.$emit("close"))},[k("div",null,[k("div",va,[pa,(X(!0),te(at,null,rt(V.titles,(H,ge)=>(X(),te("span",{key:ge,class:"title"},[k("span",{class:"text",innerHTML:H},null,8,ya),ma]))),128)),k("span",ga,[k("span",{class:"text",innerHTML:V.title},null,8,ba)])]),G(v)?(X(),te("div",wa,[V.text?(X(),te("div",xa,[k("div",{class:"vp-doc",innerHTML:V.text},null,8,Fa)])):Ee("",!0),Ea,Sa])):Ee("",!0)])],42,da)],8,ha))),128)),G(h)&&!b.value.length&&x.value?(X(),te("li",Aa,[de(ve(G(c)("modal.noResultsText"))+' "',1),k("strong",null,ve(G(h)),1),de('" ')])):Ee("",!0)],40,fa),k("div",Ta,[k("span",null,[k("kbd",{"aria-label":G(c)("modal.footer.navigateUpKeyAriaLabel")},Ia,8,Na),k("kbd",{"aria-label":G(c)("modal.footer.navigateDownKeyAriaLabel")},Oa,8,Da),de(" "+ve(G(c)("modal.footer.navigateText")),1)]),k("span",null,[k("kbd",{"aria-label":G(c)("modal.footer.selectKeyAriaLabel")},Ma,8,Ra),de(" "+ve(G(c)("modal.footer.selectText")),1)]),k("span",null,[k("kbd",{"aria-label":G(c)("modal.footer.closeKeyAriaLabel")},"esc",8,La),de(" "+ve(G(c)("modal.footer.closeText")),1)])])])],8,Qr)])}}}),Ka=er(Pa,[["__scopeId","data-v-639d7ab9"]]);export{Ka as default}; diff --git a/assets/chunks/framework.CK8QU5WH.js b/assets/chunks/framework.CK8QU5WH.js deleted file mode 100644 index e8e6109b..00000000 --- a/assets/chunks/framework.CK8QU5WH.js +++ /dev/null @@ -1 +0,0 @@ -function _r(e,t){const n=Object.create(null),r=e.split(",");for(let s=0;s!!n[s]}const te={},gt=[],Me=()=>{},di=()=>!1,hi=/^on[^a-z]/,Vt=e=>hi.test(e),yr=e=>e.startsWith("onUpdate:"),ce=Object.assign,vr=(e,t)=>{const n=e.indexOf(t);n>-1&&e.splice(n,1)},pi=Object.prototype.hasOwnProperty,Y=(e,t)=>pi.call(e,t),k=Array.isArray,mt=e=>Cn(e)==="[object Map]",Ws=e=>Cn(e)==="[object Set]",W=e=>typeof e=="function",oe=e=>typeof e=="string",br=e=>typeof e=="symbol",ee=e=>e!==null&&typeof e=="object",wr=e=>ee(e)&&W(e.then)&&W(e.catch),Vs=Object.prototype.toString,Cn=e=>Vs.call(e),gi=e=>Cn(e).slice(8,-1),qs=e=>Cn(e)==="[object Object]",Er=e=>oe(e)&&e!=="NaN"&&e[0]!=="-"&&""+parseInt(e,10)===e,Ft=_r(",key,ref,ref_for,ref_key,onVnodeBeforeMount,onVnodeMounted,onVnodeBeforeUpdate,onVnodeUpdated,onVnodeBeforeUnmount,onVnodeUnmounted"),xn=e=>{const t=Object.create(null);return n=>t[n]||(t[n]=e(n))},mi=/-(\w)/g,He=xn(e=>e.replace(mi,(t,n)=>n?n.toUpperCase():"")),_i=/\B([A-Z])/g,ut=xn(e=>e.replace(_i,"-$1").toLowerCase()),Tn=xn(e=>e.charAt(0).toUpperCase()+e.slice(1)),un=xn(e=>e?`on${Tn(e)}`:""),Dt=(e,t)=>!Object.is(e,t),fn=(e,t)=>{for(let n=0;n{Object.defineProperty(e,t,{configurable:!0,enumerable:!1,value:n})},nr=e=>{const t=parseFloat(e);return isNaN(t)?e:t},yi=e=>{const t=oe(e)?Number(e):NaN;return isNaN(t)?e:t};let Qr;const rr=()=>Qr||(Qr=typeof globalThis<"u"?globalThis:typeof self<"u"?self:typeof window<"u"?window:typeof global<"u"?global:{});function Cr(e){if(k(e)){const t={};for(let n=0;n{if(n){const r=n.split(bi);r.length>1&&(t[r[0].trim()]=r[1].trim())}}),t}function xr(e){let t="";if(oe(e))t=e;else if(k(e))for(let n=0;noe(e)?e:e==null?"":k(e)||ee(e)&&(e.toString===Vs||!W(e.toString))?JSON.stringify(e,Ys,2):String(e),Ys=(e,t)=>t&&t.__v_isRef?Ys(e,t.value):mt(t)?{[`Map(${t.size})`]:[...t.entries()].reduce((n,[r,s])=>(n[`${r} =>`]=s,n),{})}:Ws(t)?{[`Set(${t.size})`]:[...t.values()]}:ee(t)&&!k(t)&&!qs(t)?String(t):t;let be;class Ti{constructor(t=!1){this.detached=t,this._active=!0,this.effects=[],this.cleanups=[],this.parent=be,!t&&be&&(this.index=(be.scopes||(be.scopes=[])).push(this)-1)}get active(){return this._active}run(t){if(this._active){const n=be;try{return be=this,t()}finally{be=n}}}on(){be=this}off(){be=this.parent}stop(t){if(this._active){let n,r;for(n=0,r=this.effects.length;n{const t=new Set(e);return t.w=0,t.n=0,t},Js=e=>(e.w&Je)>0,Qs=e=>(e.n&Je)>0,Oi=({deps:e})=>{if(e.length)for(let t=0;t{const{deps:t}=e;if(t.length){let n=0;for(let r=0;r{(f==="length"||f>=c)&&l.push(a)})}else switch(n!==void 0&&l.push(i.get(n)),t){case"add":k(e)?Er(n)&&l.push(i.get("length")):(l.push(i.get(ct)),mt(e)&&l.push(i.get(or)));break;case"delete":k(e)||(l.push(i.get(ct)),mt(e)&&l.push(i.get(or)));break;case"set":mt(e)&&l.push(i.get(ct));break}if(l.length===1)l[0]&&ir(l[0]);else{const c=[];for(const a of l)a&&c.push(...a);ir(Tr(c))}}function ir(e,t){const n=k(e)?e:[...e];for(const r of n)r.computed&&Gr(r);for(const r of n)r.computed||Gr(r)}function Gr(e,t){(e!==Se||e.allowRecurse)&&(e.scheduler?e.scheduler():e.run())}function Ii(e,t){var n;return(n=gn.get(e))==null?void 0:n.get(t)}const Pi=_r("__proto__,__v_isRef,__isVue"),eo=new Set(Object.getOwnPropertyNames(Symbol).filter(e=>e!=="arguments"&&e!=="caller").map(e=>Symbol[e]).filter(br)),Fi=Sr(),Li=Sr(!1,!0),Mi=Sr(!0),es=Ni();function Ni(){const e={};return["includes","indexOf","lastIndexOf"].forEach(t=>{e[t]=function(...n){const r=X(this);for(let o=0,i=this.length;o{e[t]=function(...n){Tt();const r=X(this)[t].apply(this,n);return At(),r}}),e}function $i(e){const t=X(this);return _e(t,"has",e),t.hasOwnProperty(e)}function Sr(e=!1,t=!1){return function(r,s,o){if(s==="__v_isReactive")return!e;if(s==="__v_isReadonly")return e;if(s==="__v_isShallow")return t;if(s==="__v_raw"&&o===(e?t?Zi:oo:t?so:ro).get(r))return r;const i=k(r);if(!e){if(i&&Y(es,s))return Reflect.get(es,s,o);if(s==="hasOwnProperty")return $i}const l=Reflect.get(r,s,o);return(br(s)?eo.has(s):Pi(s))||(e||_e(r,"get",s),t)?l:ue(l)?i&&Er(s)?l:l.value:ee(l)?e?On(l):Sn(l):l}}const Hi=to(),ji=to(!0);function to(e=!1){return function(n,r,s,o){let i=n[r];if(wt(i)&&ue(i)&&!ue(s))return!1;if(!e&&(!mn(s)&&!wt(s)&&(i=X(i),s=X(s)),!k(n)&&ue(i)&&!ue(s)))return i.value=s,!0;const l=k(n)&&Er(r)?Number(r)e,An=e=>Reflect.getPrototypeOf(e);function Qt(e,t,n=!1,r=!1){e=e.__v_raw;const s=X(e),o=X(t);n||(t!==o&&_e(s,"get",t),_e(s,"get",o));const{has:i}=An(s),l=r?Or:n?Pr:Ut;if(i.call(s,t))return l(e.get(t));if(i.call(s,o))return l(e.get(o));e!==s&&e.get(t)}function Zt(e,t=!1){const n=this.__v_raw,r=X(n),s=X(e);return t||(e!==s&&_e(r,"has",e),_e(r,"has",s)),e===s?n.has(e):n.has(e)||n.has(s)}function Gt(e,t=!1){return e=e.__v_raw,!t&&_e(X(e),"iterate",ct),Reflect.get(e,"size",e)}function ts(e){e=X(e);const t=X(this);return An(t).has.call(t,e)||(t.add(e),Ue(t,"add",e,e)),this}function ns(e,t){t=X(t);const n=X(this),{has:r,get:s}=An(n);let o=r.call(n,e);o||(e=X(e),o=r.call(n,e));const i=s.call(n,e);return n.set(e,t),o?Dt(t,i)&&Ue(n,"set",e,t):Ue(n,"add",e,t),this}function rs(e){const t=X(this),{has:n,get:r}=An(t);let s=n.call(t,e);s||(e=X(e),s=n.call(t,e)),r&&r.call(t,e);const o=t.delete(e);return s&&Ue(t,"delete",e,void 0),o}function ss(){const e=X(this),t=e.size!==0,n=e.clear();return t&&Ue(e,"clear",void 0,void 0),n}function en(e,t){return function(r,s){const o=this,i=o.__v_raw,l=X(i),c=t?Or:e?Pr:Ut;return!e&&_e(l,"iterate",ct),i.forEach((a,f)=>r.call(s,c(a),c(f),o))}}function tn(e,t,n){return function(...r){const s=this.__v_raw,o=X(s),i=mt(o),l=e==="entries"||e===Symbol.iterator&&i,c=e==="keys"&&i,a=s[e](...r),f=n?Or:t?Pr:Ut;return!t&&_e(o,"iterate",c?or:ct),{next(){const{value:h,done:p}=a.next();return p?{value:h,done:p}:{value:l?[f(h[0]),f(h[1])]:f(h),done:p}},[Symbol.iterator](){return this}}}}function ke(e){return function(...t){return e==="delete"?!1:this}}function Wi(){const e={get(o){return Qt(this,o)},get size(){return Gt(this)},has:Zt,add:ts,set:ns,delete:rs,clear:ss,forEach:en(!1,!1)},t={get(o){return Qt(this,o,!1,!0)},get size(){return Gt(this)},has:Zt,add:ts,set:ns,delete:rs,clear:ss,forEach:en(!1,!0)},n={get(o){return Qt(this,o,!0)},get size(){return Gt(this,!0)},has(o){return Zt.call(this,o,!0)},add:ke("add"),set:ke("set"),delete:ke("delete"),clear:ke("clear"),forEach:en(!0,!1)},r={get(o){return Qt(this,o,!0,!0)},get size(){return Gt(this,!0)},has(o){return Zt.call(this,o,!0)},add:ke("add"),set:ke("set"),delete:ke("delete"),clear:ke("clear"),forEach:en(!0,!0)};return["keys","values","entries",Symbol.iterator].forEach(o=>{e[o]=tn(o,!1,!1),n[o]=tn(o,!0,!1),t[o]=tn(o,!1,!0),r[o]=tn(o,!0,!0)}),[e,n,t,r]}const[Vi,qi,zi,Yi]=Wi();function Rr(e,t){const n=t?e?Yi:zi:e?qi:Vi;return(r,s,o)=>s==="__v_isReactive"?!e:s==="__v_isReadonly"?e:s==="__v_raw"?r:Reflect.get(Y(n,s)&&s in r?n:r,s,o)}const Xi={get:Rr(!1,!1)},Ji={get:Rr(!1,!0)},Qi={get:Rr(!0,!1)},ro=new WeakMap,so=new WeakMap,oo=new WeakMap,Zi=new WeakMap;function Gi(e){switch(e){case"Object":case"Array":return 1;case"Map":case"Set":case"WeakMap":case"WeakSet":return 2;default:return 0}}function el(e){return e.__v_skip||!Object.isExtensible(e)?0:Gi(gi(e))}function Sn(e){return wt(e)?e:Ir(e,!1,no,Xi,ro)}function tl(e){return Ir(e,!1,Ki,Ji,so)}function On(e){return Ir(e,!0,ki,Qi,oo)}function Ir(e,t,n,r,s){if(!ee(e)||e.__v_raw&&!(t&&e.__v_isReactive))return e;const o=s.get(e);if(o)return o;const i=el(e);if(i===0)return e;const l=new Proxy(e,i===2?r:n);return s.set(e,l),l}function _t(e){return wt(e)?_t(e.__v_raw):!!(e&&e.__v_isReactive)}function wt(e){return!!(e&&e.__v_isReadonly)}function mn(e){return!!(e&&e.__v_isShallow)}function io(e){return _t(e)||wt(e)}function X(e){const t=e&&e.__v_raw;return t?X(t):e}function Lt(e){return pn(e,"__v_skip",!0),e}const Ut=e=>ee(e)?Sn(e):e,Pr=e=>ee(e)?On(e):e;function Fr(e){ze&&Se&&(e=X(e),Gs(e.dep||(e.dep=Tr())))}function Lr(e,t){e=X(e);const n=e.dep;n&&ir(n)}function ue(e){return!!(e&&e.__v_isRef===!0)}function se(e){return lo(e,!1)}function Mr(e){return lo(e,!0)}function lo(e,t){return ue(e)?e:new nl(e,t)}class nl{constructor(t,n){this.__v_isShallow=n,this.dep=void 0,this.__v_isRef=!0,this._rawValue=n?t:X(t),this._value=n?t:Ut(t)}get value(){return Fr(this),this._value}set value(t){const n=this.__v_isShallow||mn(t)||wt(t);t=n?t:X(t),Dt(t,this._rawValue)&&(this._rawValue=t,this._value=n?t:Ut(t),Lr(this))}}function co(e){return ue(e)?e.value:e}const rl={get:(e,t,n)=>co(Reflect.get(e,t,n)),set:(e,t,n,r)=>{const s=e[t];return ue(s)&&!ue(n)?(s.value=n,!0):Reflect.set(e,t,n,r)}};function ao(e){return _t(e)?e:new Proxy(e,rl)}class sl{constructor(t){this.dep=void 0,this.__v_isRef=!0;const{get:n,set:r}=t(()=>Fr(this),()=>Lr(this));this._get=n,this._set=r}get value(){return this._get()}set value(t){this._set(t)}}function ol(e){return new sl(e)}class il{constructor(t,n,r){this._object=t,this._key=n,this._defaultValue=r,this.__v_isRef=!0}get value(){const t=this._object[this._key];return t===void 0?this._defaultValue:t}set value(t){this._object[this._key]=t}get dep(){return Ii(X(this._object),this._key)}}class ll{constructor(t){this._getter=t,this.__v_isRef=!0,this.__v_isReadonly=!0}get value(){return this._getter()}}function cl(e,t,n){return ue(e)?e:W(e)?new ll(e):ee(e)&&arguments.length>1?al(e,t,n):se(e)}function al(e,t,n){const r=e[t];return ue(r)?r:new il(e,t,n)}class ul{constructor(t,n,r,s){this._setter=n,this.dep=void 0,this.__v_isRef=!0,this.__v_isReadonly=!1,this._dirty=!0,this.effect=new Ar(t,()=>{this._dirty||(this._dirty=!0,Lr(this))}),this.effect.computed=this,this.effect.active=this._cacheable=!s,this.__v_isReadonly=r}get value(){const t=X(this);return Fr(t),(t._dirty||!t._cacheable)&&(t._dirty=!1,t._value=t.effect.run()),t._value}set value(t){this._setter(t)}}function fl(e,t,n=!1){let r,s;const o=W(e);return o?(r=e,s=Me):(r=e.get,s=e.set),new ul(r,s,o||!s,n)}function Ye(e,t,n,r){let s;try{s=r?e(...r):e()}catch(o){qt(o,t,n)}return s}function xe(e,t,n,r){if(W(e)){const o=Ye(e,t,n,r);return o&&wr(o)&&o.catch(i=>{qt(i,t,n)}),o}const s=[];for(let o=0;o>>1;kt(he[r])Le&&he.splice(t,1)}function gl(e){k(e)?yt.push(...e):(!De||!De.includes(e,e.allowRecurse?st+1:st))&&yt.push(e),fo()}function os(e,t=Bt?Le+1:0){for(;tkt(n)-kt(r)),st=0;ste.id==null?1/0:e.id,ml=(e,t)=>{const n=kt(e)-kt(t);if(n===0){if(e.pre&&!t.pre)return-1;if(t.pre&&!e.pre)return 1}return n};function ho(e){lr=!1,Bt=!0,he.sort(ml);try{for(Le=0;Leoe(b)?b.trim():b)),h&&(s=n.map(nr))}let l,c=r[l=un(t)]||r[l=un(He(t))];!c&&o&&(c=r[l=un(ut(t))]),c&&xe(c,e,6,s);const a=r[l+"Once"];if(a){if(!e.emitted)e.emitted={};else if(e.emitted[l])return;e.emitted[l]=!0,xe(a,e,6,s)}}function po(e,t,n=!1){const r=t.emitsCache,s=r.get(e);if(s!==void 0)return s;const o=e.emits;let i={},l=!1;if(!W(e)){const c=a=>{const f=po(a,t,!0);f&&(l=!0,ce(i,f))};!n&&t.mixins.length&&t.mixins.forEach(c),e.extends&&c(e.extends),e.mixins&&e.mixins.forEach(c)}return!o&&!l?(ee(e)&&r.set(e,null),null):(k(o)?o.forEach(c=>i[c]=null):ce(i,o),ee(e)&&r.set(e,i),i)}function Pn(e,t){return!e||!Vt(t)?!1:(t=t.slice(2).replace(/Once$/,""),Y(e,t[0].toLowerCase()+t.slice(1))||Y(e,ut(t))||Y(e,t))}let fe=null,Fn=null;function yn(e){const t=fe;return fe=e,Fn=e&&e.type.__scopeId||null,t}function Ka(e){Fn=e}function Wa(){Fn=null}function yl(e,t=fe,n){if(!t||e._n)return e;const r=(...s)=>{r._d&&ys(-1);const o=yn(t);let i;try{i=e(...s)}finally{yn(o),r._d&&ys(1)}return i};return r._n=!0,r._c=!0,r._d=!0,r}function Un(e){const{type:t,vnode:n,proxy:r,withProxy:s,props:o,propsOptions:[i],slots:l,attrs:c,emit:a,render:f,renderCache:h,data:p,setupState:b,ctx:E,inheritAttrs:S}=e;let L,_;const m=yn(e);try{if(n.shapeFlag&4){const T=s||r;L=Ae(f.call(T,T,h,o,b,p,E)),_=c}else{const T=t;L=Ae(T.length>1?T(o,{attrs:c,slots:l,emit:a}):T(o,null)),_=t.props?c:vl(c)}}catch(T){Ht.length=0,qt(T,e,1),L=ie(we)}let N=L;if(_&&S!==!1){const T=Object.keys(_),{shapeFlag:D}=N;T.length&&D&7&&(i&&T.some(yr)&&(_=bl(_,i)),N=Qe(N,_))}return n.dirs&&(N=Qe(N),N.dirs=N.dirs?N.dirs.concat(n.dirs):n.dirs),n.transition&&(N.transition=n.transition),L=N,yn(m),L}const vl=e=>{let t;for(const n in e)(n==="class"||n==="style"||Vt(n))&&((t||(t={}))[n]=e[n]);return t},bl=(e,t)=>{const n={};for(const r in e)(!yr(r)||!(r.slice(9)in t))&&(n[r]=e[r]);return n};function wl(e,t,n){const{props:r,children:s,component:o}=e,{props:i,children:l,patchFlag:c}=t,a=o.emitsOptions;if(t.dirs||t.transition)return!0;if(n&&c>=0){if(c&1024)return!0;if(c&16)return r?is(r,i,a):!!i;if(c&8){const f=t.dynamicProps;for(let h=0;he.__isSuspense;function go(e,t){t&&t.pendingBranch?k(e)?t.effects.push(...e):t.effects.push(e):gl(e)}function $r(e,t){return Ln(e,null,t)}function Va(e,t){return Ln(e,null,{flush:"post"})}const nn={};function Ne(e,t,n){return Ln(e,t,n)}function Ln(e,t,{immediate:n,deep:r,flush:s,onTrack:o,onTrigger:i}=te){var l;const c=Xs()===((l=ae)==null?void 0:l.scope)?ae:null;let a,f=!1,h=!1;if(ue(e)?(a=()=>e.value,f=mn(e)):_t(e)?(a=()=>e,r=!0):k(e)?(h=!0,f=e.some(T=>_t(T)||mn(T)),a=()=>e.map(T=>{if(ue(T))return T.value;if(_t(T))return lt(T);if(W(T))return Ye(T,c,2)})):W(e)?t?a=()=>Ye(e,c,2):a=()=>{if(!(c&&c.isUnmounted))return p&&p(),xe(e,c,3,[b])}:a=Me,t&&r){const T=a;a=()=>lt(T())}let p,b=T=>{p=m.onStop=()=>{Ye(T,c,4)}},E;if(Ct)if(b=Me,t?n&&xe(t,c,3,[a(),h?[]:void 0,b]):a(),s==="sync"){const T=vc();E=T.__watcherHandles||(T.__watcherHandles=[])}else return Me;let S=h?new Array(e.length).fill(nn):nn;const L=()=>{if(m.active)if(t){const T=m.run();(r||f||(h?T.some((D,V)=>Dt(D,S[V])):Dt(T,S)))&&(p&&p(),xe(t,c,3,[T,S===nn?void 0:h&&S[0]===nn?[]:S,b]),S=T)}else m.run()};L.allowRecurse=!!t;let _;s==="sync"?_=L:s==="post"?_=()=>ge(L,c&&c.suspense):(L.pre=!0,c&&(L.id=c.uid),_=()=>In(L));const m=new Ar(a,_);t?n?L():S=m.run():s==="post"?ge(m.run.bind(m),c&&c.suspense):m.run();const N=()=>{m.stop(),c&&c.scope&&vr(c.scope.effects,m)};return E&&E.push(N),N}function xl(e,t,n){const r=this.proxy,s=oe(e)?e.includes(".")?mo(r,e):()=>r[e]:e.bind(r,r);let o;W(t)?o=t:(o=t.handler,n=t);const i=ae;Ze(this);const l=Ln(s,o.bind(r),n);return i?Ze(i):Xe(),l}function mo(e,t){const n=t.split(".");return()=>{let r=e;for(let s=0;s{lt(n,t)});else if(qs(e))for(const n in e)lt(e[n],t);return e}function qa(e,t){const n=fe;if(n===null)return e;const r=Hn(n)||n.proxy,s=e.dirs||(e.dirs=[]);for(let o=0;o{e.isMounted=!0}),wo(()=>{e.isUnmounting=!0}),e}const Ee=[Function,Array],_o={mode:String,appear:Boolean,persisted:Boolean,onBeforeEnter:Ee,onEnter:Ee,onAfterEnter:Ee,onEnterCancelled:Ee,onBeforeLeave:Ee,onLeave:Ee,onAfterLeave:Ee,onLeaveCancelled:Ee,onBeforeAppear:Ee,onAppear:Ee,onAfterAppear:Ee,onAppearCancelled:Ee},Al={name:"BaseTransition",props:_o,setup(e,{slots:t}){const n=Yt(),r=Tl();let s;return()=>{const o=t.default&&vo(t.default(),!0);if(!o||!o.length)return;let i=o[0];if(o.length>1){for(const S of o)if(S.type!==we){i=S;break}}const l=X(e),{mode:c}=l;if(r.isLeaving)return Bn(i);const a=ls(i);if(!a)return Bn(i);const f=cr(a,l,r,n);ar(a,f);const h=n.subTree,p=h&&ls(h);let b=!1;const{getTransitionKey:E}=a.type;if(E){const S=E();s===void 0?s=S:S!==s&&(s=S,b=!0)}if(p&&p.type!==we&&(!ot(a,p)||b)){const S=cr(p,l,r,n);if(ar(p,S),c==="out-in")return r.isLeaving=!0,S.afterLeave=()=>{r.isLeaving=!1,n.update.active!==!1&&n.update()},Bn(i);c==="in-out"&&a.type!==we&&(S.delayLeave=(L,_,m)=>{const N=yo(r,p);N[String(p.key)]=p,L._leaveCb=()=>{_(),L._leaveCb=void 0,delete f.delayedLeave},f.delayedLeave=m})}return i}}},Sl=Al;function yo(e,t){const{leavingVNodes:n}=e;let r=n.get(t.type);return r||(r=Object.create(null),n.set(t.type,r)),r}function cr(e,t,n,r){const{appear:s,mode:o,persisted:i=!1,onBeforeEnter:l,onEnter:c,onAfterEnter:a,onEnterCancelled:f,onBeforeLeave:h,onLeave:p,onAfterLeave:b,onLeaveCancelled:E,onBeforeAppear:S,onAppear:L,onAfterAppear:_,onAppearCancelled:m}=t,N=String(e.key),T=yo(n,e),D=(C,B)=>{C&&xe(C,r,9,B)},V=(C,B)=>{const O=B[1];D(C,B),k(C)?C.every($=>$.length<=1)&&O():C.length<=1&&O()},U={mode:o,persisted:i,beforeEnter(C){let B=l;if(!n.isMounted)if(s)B=S||l;else return;C._leaveCb&&C._leaveCb(!0);const O=T[N];O&&ot(e,O)&&O.el._leaveCb&&O.el._leaveCb(),D(B,[C])},enter(C){let B=c,O=a,$=f;if(!n.isMounted)if(s)B=L||c,O=_||a,$=m||f;else return;let P=!1;const q=C._enterCb=M=>{P||(P=!0,M?D($,[C]):D(O,[C]),U.delayedLeave&&U.delayedLeave(),C._enterCb=void 0)};B?V(B,[C,q]):q()},leave(C,B){const O=String(e.key);if(C._enterCb&&C._enterCb(!0),n.isUnmounting)return B();D(h,[C]);let $=!1;const P=C._leaveCb=q=>{$||($=!0,B(),q?D(E,[C]):D(b,[C]),C._leaveCb=void 0,T[O]===e&&delete T[O])};T[O]=e,p?V(p,[C,P]):P()},clone(C){return cr(C,t,n,r)}};return U}function Bn(e){if(zt(e))return e=Qe(e),e.children=null,e}function ls(e){return zt(e)?e.children?e.children[0]:void 0:e}function ar(e,t){e.shapeFlag&6&&e.component?ar(e.component.subTree,t):e.shapeFlag&128?(e.ssContent.transition=t.clone(e.ssContent),e.ssFallback.transition=t.clone(e.ssFallback)):e.transition=t}function vo(e,t=!1,n){let r=[],s=0;for(let o=0;o1)for(let o=0;o!!e.type.__asyncLoader;function za(e){W(e)&&(e={loader:e});const{loader:t,loadingComponent:n,errorComponent:r,delay:s=200,timeout:o,suspensible:i=!0,onError:l}=e;let c=null,a,f=0;const h=()=>(f++,c=null,p()),p=()=>{let b;return c||(b=c=t().catch(E=>{if(E=E instanceof Error?E:new Error(String(E)),l)return new Promise((S,L)=>{l(E,()=>S(h()),()=>L(E),f+1)});throw E}).then(E=>b!==c&&c?c:(E&&(E.__esModule||E[Symbol.toStringTag]==="Module")&&(E=E.default),a=E,E)))};return Hr({name:"AsyncComponentWrapper",__asyncLoader:p,get __asyncResolved(){return a},setup(){const b=ae;if(a)return()=>kn(a,b);const E=m=>{c=null,qt(m,b,13,!r)};if(i&&b.suspense||Ct)return p().then(m=>()=>kn(m,b)).catch(m=>(E(m),()=>r?ie(r,{error:m}):null));const S=se(!1),L=se(),_=se(!!s);return s&&setTimeout(()=>{_.value=!1},s),o!=null&&setTimeout(()=>{if(!S.value&&!L.value){const m=new Error(`Async component timed out after ${o}ms.`);E(m),L.value=m}},o),p().then(()=>{S.value=!0,b.parent&&zt(b.parent.vnode)&&In(b.parent.update)}).catch(m=>{E(m),L.value=m}),()=>{if(S.value&&a)return kn(a,b);if(L.value&&r)return ie(r,{error:L.value});if(n&&!_.value)return ie(n)}}})}function kn(e,t){const{ref:n,props:r,children:s,ce:o}=t.vnode,i=ie(e,r,s);return i.ref=n,i.ce=o,delete t.vnode.ce,i}const zt=e=>e.type.__isKeepAlive;function Ol(e,t){bo(e,"a",t)}function Rl(e,t){bo(e,"da",t)}function bo(e,t,n=ae){const r=e.__wdc||(e.__wdc=()=>{let s=n;for(;s;){if(s.isDeactivated)return;s=s.parent}return e()});if(Mn(t,r,n),n){let s=n.parent;for(;s&&s.parent;)zt(s.parent.vnode)&&Il(r,t,n,s),s=s.parent}}function Il(e,t,n,r){const s=Mn(t,e,r,!0);Nn(()=>{vr(r[t],s)},n)}function Mn(e,t,n=ae,r=!1){if(n){const s=n[e]||(n[e]=[]),o=t.__weh||(t.__weh=(...i)=>{if(n.isUnmounted)return;Tt(),Ze(n);const l=xe(t,n,e,i);return Xe(),At(),l});return r?s.unshift(o):s.push(o),o}}const Be=e=>(t,n=ae)=>(!Ct||e==="sp")&&Mn(e,(...r)=>t(...r),n),Pl=Be("bm"),St=Be("m"),Fl=Be("bu"),Ll=Be("u"),wo=Be("bum"),Nn=Be("um"),Ml=Be("sp"),Nl=Be("rtg"),$l=Be("rtc");function Hl(e,t=ae){Mn("ec",e,t)}const Eo="components";function Ya(e,t){return xo(Eo,e,!0,t)||e}const Co=Symbol.for("v-ndc");function Xa(e){return oe(e)?xo(Eo,e,!1)||e:e||Co}function xo(e,t,n=!0,r=!1){const s=fe||ae;if(s){const o=s.type;{const l=mc(o,!1);if(l&&(l===t||l===He(t)||l===Tn(He(t))))return o}const i=cs(s[e]||o[e],t)||cs(s.appContext[e],t);return!i&&r?o:i}}function cs(e,t){return e&&(e[t]||e[He(t)]||e[Tn(He(t))])}function Ja(e,t,n,r){let s;const o=n;if(k(e)||oe(e)){s=new Array(e.length);for(let i=0,l=e.length;it(i,l,void 0,o));else{const i=Object.keys(e);s=new Array(i.length);for(let l=0,c=i.length;lEn(t)?!(t.type===we||t.type===me&&!To(t.children)):!0)?e:null}function Za(e,t){const n={};for(const r in e)n[/[A-Z]/.test(r)?`on:${r}`:un(r)]=e[r];return n}const ur=e=>e?Bo(e)?Hn(e)||e.proxy:ur(e.parent):null,Mt=ce(Object.create(null),{$:e=>e,$el:e=>e.vnode.el,$data:e=>e.data,$props:e=>e.props,$attrs:e=>e.attrs,$slots:e=>e.slots,$refs:e=>e.refs,$parent:e=>ur(e.parent),$root:e=>ur(e.root),$emit:e=>e.emit,$options:e=>jr(e),$forceUpdate:e=>e.f||(e.f=()=>In(e.update)),$nextTick:e=>e.n||(e.n=Rn.bind(e.proxy)),$watch:e=>xl.bind(e)}),Kn=(e,t)=>e!==te&&!e.__isScriptSetup&&Y(e,t),jl={get({_:e},t){const{ctx:n,setupState:r,data:s,props:o,accessCache:i,type:l,appContext:c}=e;let a;if(t[0]!=="$"){const b=i[t];if(b!==void 0)switch(b){case 1:return r[t];case 2:return s[t];case 4:return n[t];case 3:return o[t]}else{if(Kn(r,t))return i[t]=1,r[t];if(s!==te&&Y(s,t))return i[t]=2,s[t];if((a=e.propsOptions[0])&&Y(a,t))return i[t]=3,o[t];if(n!==te&&Y(n,t))return i[t]=4,n[t];fr&&(i[t]=0)}}const f=Mt[t];let h,p;if(f)return t==="$attrs"&&_e(e,"get",t),f(e);if((h=l.__cssModules)&&(h=h[t]))return h;if(n!==te&&Y(n,t))return i[t]=4,n[t];if(p=c.config.globalProperties,Y(p,t))return p[t]},set({_:e},t,n){const{data:r,setupState:s,ctx:o}=e;return Kn(s,t)?(s[t]=n,!0):r!==te&&Y(r,t)?(r[t]=n,!0):Y(e.props,t)||t[0]==="$"&&t.slice(1)in e?!1:(o[t]=n,!0)},has({_:{data:e,setupState:t,accessCache:n,ctx:r,appContext:s,propsOptions:o}},i){let l;return!!n[i]||e!==te&&Y(e,i)||Kn(t,i)||(l=o[0])&&Y(l,i)||Y(r,i)||Y(Mt,i)||Y(s.config.globalProperties,i)},defineProperty(e,t,n){return n.get!=null?e._.accessCache[t]=0:Y(n,"value")&&this.set(e,t,n.value,null),Reflect.defineProperty(e,t,n)}};function Ga(){return Dl().slots}function Dl(){const e=Yt();return e.setupContext||(e.setupContext=Ko(e))}function as(e){return k(e)?e.reduce((t,n)=>(t[n]=null,t),{}):e}function eu(e){const t=Yt();let n=e();return Xe(),wr(n)&&(n=n.catch(r=>{throw Ze(t),r})),[n,()=>Ze(t)]}let fr=!0;function Ul(e){const t=jr(e),n=e.proxy,r=e.ctx;fr=!1,t.beforeCreate&&us(t.beforeCreate,e,"bc");const{data:s,computed:o,methods:i,watch:l,provide:c,inject:a,created:f,beforeMount:h,mounted:p,beforeUpdate:b,updated:E,activated:S,deactivated:L,beforeDestroy:_,beforeUnmount:m,destroyed:N,unmounted:T,render:D,renderTracked:V,renderTriggered:U,errorCaptured:C,serverPrefetch:B,expose:O,inheritAttrs:$,components:P,directives:q,filters:M}=t;if(a&&Bl(a,r,null),i)for(const ne in i){const Z=i[ne];W(Z)&&(r[ne]=Z.bind(n))}if(s){const ne=s.call(n,n);ee(ne)&&(e.data=Sn(ne))}if(fr=!0,o)for(const ne in o){const Z=o[ne],Ge=W(Z)?Z.bind(n,n):W(Z.get)?Z.get.bind(n,n):Me,Xt=!W(Z)&&W(Z.set)?Z.set.bind(n):Me,et=re({get:Ge,set:Xt});Object.defineProperty(r,ne,{enumerable:!0,configurable:!0,get:()=>et.value,set:Ie=>et.value=Ie})}if(l)for(const ne in l)Ao(l[ne],r,n,ne);if(c){const ne=W(c)?c.call(n):c;Reflect.ownKeys(ne).forEach(Z=>{zl(Z,ne[Z])})}f&&us(f,e,"c");function J(ne,Z){k(Z)?Z.forEach(Ge=>ne(Ge.bind(n))):Z&&ne(Z.bind(n))}if(J(Pl,h),J(St,p),J(Fl,b),J(Ll,E),J(Ol,S),J(Rl,L),J(Hl,C),J($l,V),J(Nl,U),J(wo,m),J(Nn,T),J(Ml,B),k(O))if(O.length){const ne=e.exposed||(e.exposed={});O.forEach(Z=>{Object.defineProperty(ne,Z,{get:()=>n[Z],set:Ge=>n[Z]=Ge})})}else e.exposed||(e.exposed={});D&&e.render===Me&&(e.render=D),$!=null&&(e.inheritAttrs=$),P&&(e.components=P),q&&(e.directives=q)}function Bl(e,t,n=Me){k(e)&&(e=dr(e));for(const r in e){const s=e[r];let o;ee(s)?"default"in s?o=bt(s.from||r,s.default,!0):o=bt(s.from||r):o=bt(s),ue(o)?Object.defineProperty(t,r,{enumerable:!0,configurable:!0,get:()=>o.value,set:i=>o.value=i}):t[r]=o}}function us(e,t,n){xe(k(e)?e.map(r=>r.bind(t.proxy)):e.bind(t.proxy),t,n)}function Ao(e,t,n,r){const s=r.includes(".")?mo(n,r):()=>n[r];if(oe(e)){const o=t[e];W(o)&&Ne(s,o)}else if(W(e))Ne(s,e.bind(n));else if(ee(e))if(k(e))e.forEach(o=>Ao(o,t,n,r));else{const o=W(e.handler)?e.handler.bind(n):t[e.handler];W(o)&&Ne(s,o,e)}}function jr(e){const t=e.type,{mixins:n,extends:r}=t,{mixins:s,optionsCache:o,config:{optionMergeStrategies:i}}=e.appContext,l=o.get(t);let c;return l?c=l:!s.length&&!n&&!r?c=t:(c={},s.length&&s.forEach(a=>vn(c,a,i,!0)),vn(c,t,i)),ee(t)&&o.set(t,c),c}function vn(e,t,n,r=!1){const{mixins:s,extends:o}=t;o&&vn(e,o,n,!0),s&&s.forEach(i=>vn(e,i,n,!0));for(const i in t)if(!(r&&i==="expose")){const l=kl[i]||n&&n[i];e[i]=l?l(e[i],t[i]):t[i]}return e}const kl={data:fs,props:ds,emits:ds,methods:Pt,computed:Pt,beforeCreate:pe,created:pe,beforeMount:pe,mounted:pe,beforeUpdate:pe,updated:pe,beforeDestroy:pe,beforeUnmount:pe,destroyed:pe,unmounted:pe,activated:pe,deactivated:pe,errorCaptured:pe,serverPrefetch:pe,components:Pt,directives:Pt,watch:Wl,provide:fs,inject:Kl};function fs(e,t){return t?e?function(){return ce(W(e)?e.call(this,this):e,W(t)?t.call(this,this):t)}:t:e}function Kl(e,t){return Pt(dr(e),dr(t))}function dr(e){if(k(e)){const t={};for(let n=0;n1)return n&&W(t)?t.call(r&&r.proxy):t}}function Yl(e,t,n,r=!1){const s={},o={};pn(o,$n,1),e.propsDefaults=Object.create(null),Oo(e,t,s,o);for(const i in e.propsOptions[0])i in s||(s[i]=void 0);n?e.props=r?s:tl(s):e.type.props?e.props=s:e.props=o,e.attrs=o}function Xl(e,t,n,r){const{props:s,attrs:o,vnode:{patchFlag:i}}=e,l=X(s),[c]=e.propsOptions;let a=!1;if((r||i>0)&&!(i&16)){if(i&8){const f=e.vnode.dynamicProps;for(let h=0;h{c=!0;const[p,b]=Ro(h,t,!0);ce(i,p),b&&l.push(...b)};!n&&t.mixins.length&&t.mixins.forEach(f),e.extends&&f(e.extends),e.mixins&&e.mixins.forEach(f)}if(!o&&!c)return ee(e)&&r.set(e,gt),gt;if(k(o))for(let f=0;f-1,b[1]=S<0||E-1||Y(b,"default"))&&l.push(h)}}}const a=[i,l];return ee(e)&&r.set(e,a),a}function hs(e){return e[0]!=="$"}function ps(e){const t=e&&e.toString().match(/^\s*(function|class) (\w+)/);return t?t[2]:e===null?"null":""}function gs(e,t){return ps(e)===ps(t)}function ms(e,t){return k(t)?t.findIndex(n=>gs(n,e)):W(t)&&gs(t,e)?0:-1}const Io=e=>e[0]==="_"||e==="$stable",Dr=e=>k(e)?e.map(Ae):[Ae(e)],Jl=(e,t,n)=>{if(t._n)return t;const r=yl((...s)=>Dr(t(...s)),n);return r._c=!1,r},Po=(e,t,n)=>{const r=e._ctx;for(const s in e){if(Io(s))continue;const o=e[s];if(W(o))t[s]=Jl(s,o,r);else if(o!=null){const i=Dr(o);t[s]=()=>i}}},Fo=(e,t)=>{const n=Dr(t);e.slots.default=()=>n},Ql=(e,t)=>{if(e.vnode.shapeFlag&32){const n=t._;n?(e.slots=X(t),pn(t,"_",n)):Po(t,e.slots={})}else e.slots={},t&&Fo(e,t);pn(e.slots,$n,1)},Zl=(e,t,n)=>{const{vnode:r,slots:s}=e;let o=!0,i=te;if(r.shapeFlag&32){const l=t._;l?n&&l===1?o=!1:(ce(s,t),!n&&l===1&&delete s._):(o=!t.$stable,Po(t,s)),i=t}else t&&(Fo(e,t),i={default:1});if(o)for(const l in s)!Io(l)&&!(l in i)&&delete s[l]};function wn(e,t,n,r,s=!1){if(k(e)){e.forEach((p,b)=>wn(p,t&&(k(t)?t[b]:t),n,r,s));return}if(vt(r)&&!s)return;const o=r.shapeFlag&4?Hn(r.component)||r.component.proxy:r.el,i=s?null:o,{i:l,r:c}=e,a=t&&t.r,f=l.refs===te?l.refs={}:l.refs,h=l.setupState;if(a!=null&&a!==c&&(oe(a)?(f[a]=null,Y(h,a)&&(h[a]=null)):ue(a)&&(a.value=null)),W(c))Ye(c,l,12,[i,f]);else{const p=oe(c),b=ue(c);if(p||b){const E=()=>{if(e.f){const S=p?Y(h,c)?h[c]:f[c]:c.value;s?k(S)&&vr(S,o):k(S)?S.includes(o)||S.push(o):p?(f[c]=[o],Y(h,c)&&(h[c]=f[c])):(c.value=[o],e.k&&(f[e.k]=c.value))}else p?(f[c]=i,Y(h,c)&&(h[c]=i)):b&&(c.value=i,e.k&&(f[e.k]=i))};i?(E.id=-1,ge(E,n)):E()}}}let Ke=!1;const rn=e=>/svg/.test(e.namespaceURI)&&e.tagName!=="foreignObject",sn=e=>e.nodeType===8;function Gl(e){const{mt:t,p:n,o:{patchProp:r,createText:s,nextSibling:o,parentNode:i,remove:l,insert:c,createComment:a}}=e,f=(_,m)=>{if(!m.hasChildNodes()){n(null,_,m),_n(),m._vnode=_;return}Ke=!1,h(m.firstChild,_,null,null,null),_n(),m._vnode=_,Ke&&console.error("Hydration completed but contains mismatches.")},h=(_,m,N,T,D,V=!1)=>{const U=sn(_)&&_.data==="[",C=()=>S(_,m,N,T,D,U),{type:B,ref:O,shapeFlag:$,patchFlag:P}=m;let q=_.nodeType;m.el=_,P===-2&&(V=!1,m.dynamicChildren=null);let M=null;switch(B){case Et:q!==3?m.children===""?(c(m.el=s(""),i(_),_),M=_):M=C():(_.data!==m.children&&(Ke=!0,_.data=m.children),M=o(_));break;case we:q!==8||U?M=C():M=o(_);break;case $t:if(U&&(_=o(_),q=_.nodeType),q===1||q===3){M=_;const ye=!m.children.length;for(let J=0;J{V=V||!!m.dynamicChildren;const{type:U,props:C,patchFlag:B,shapeFlag:O,dirs:$}=m,P=U==="input"&&$||U==="option";if(P||B!==-1){if($&&Fe(m,null,N,"created"),C)if(P||!V||B&48)for(const M in C)(P&&M.endsWith("value")||Vt(M)&&!Ft(M))&&r(_,M,null,C[M],!1,void 0,N);else C.onClick&&r(_,"onClick",null,C.onClick,!1,void 0,N);let q;if((q=C&&C.onVnodeBeforeMount)&&Ce(q,N,m),$&&Fe(m,null,N,"beforeMount"),((q=C&&C.onVnodeMounted)||$)&&go(()=>{q&&Ce(q,N,m),$&&Fe(m,null,N,"mounted")},T),O&16&&!(C&&(C.innerHTML||C.textContent))){let M=b(_.firstChild,m,_,N,T,D,V);for(;M;){Ke=!0;const ye=M;M=M.nextSibling,l(ye)}}else O&8&&_.textContent!==m.children&&(Ke=!0,_.textContent=m.children)}return _.nextSibling},b=(_,m,N,T,D,V,U)=>{U=U||!!m.dynamicChildren;const C=m.children,B=C.length;for(let O=0;O{const{slotScopeIds:U}=m;U&&(D=D?D.concat(U):U);const C=i(_),B=b(o(_),m,C,N,T,D,V);return B&&sn(B)&&B.data==="]"?o(m.anchor=B):(Ke=!0,c(m.anchor=a("]"),C,B),B)},S=(_,m,N,T,D,V)=>{if(Ke=!0,m.el=null,V){const B=L(_);for(;;){const O=o(_);if(O&&O!==B)l(O);else break}}const U=o(_),C=i(_);return l(_),n(null,m,C,U,N,T,rn(C),D),U},L=_=>{let m=0;for(;_;)if(_=o(_),_&&sn(_)&&(_.data==="["&&m++,_.data==="]")){if(m===0)return o(_);m--}return _};return[f,h]}const ge=go;function ec(e){return Lo(e)}function tc(e){return Lo(e,Gl)}function Lo(e,t){const n=rr();n.__VUE__=!0;const{insert:r,remove:s,patchProp:o,createElement:i,createText:l,createComment:c,setText:a,setElementText:f,parentNode:h,nextSibling:p,setScopeId:b=Me,insertStaticContent:E}=e,S=(u,d,g,v=null,y=null,A=null,I=!1,x=null,R=!!d.dynamicChildren)=>{if(u===d)return;u&&!ot(u,d)&&(v=Jt(u),Ie(u,y,A,!0),u=null),d.patchFlag===-2&&(R=!1,d.dynamicChildren=null);const{type:w,ref:H,shapeFlag:F}=d;switch(w){case Et:L(u,d,g,v);break;case we:_(u,d,g,v);break;case $t:u==null&&m(d,g,v,I);break;case me:P(u,d,g,v,y,A,I,x,R);break;default:F&1?D(u,d,g,v,y,A,I,x,R):F&6?q(u,d,g,v,y,A,I,x,R):(F&64||F&128)&&w.process(u,d,g,v,y,A,I,x,R,ft)}H!=null&&y&&wn(H,u&&u.ref,A,d||u,!d)},L=(u,d,g,v)=>{if(u==null)r(d.el=l(d.children),g,v);else{const y=d.el=u.el;d.children!==u.children&&a(y,d.children)}},_=(u,d,g,v)=>{u==null?r(d.el=c(d.children||""),g,v):d.el=u.el},m=(u,d,g,v)=>{[u.el,u.anchor]=E(u.children,d,g,v,u.el,u.anchor)},N=({el:u,anchor:d},g,v)=>{let y;for(;u&&u!==d;)y=p(u),r(u,g,v),u=y;r(d,g,v)},T=({el:u,anchor:d})=>{let g;for(;u&&u!==d;)g=p(u),s(u),u=g;s(d)},D=(u,d,g,v,y,A,I,x,R)=>{I=I||d.type==="svg",u==null?V(d,g,v,y,A,I,x,R):B(u,d,y,A,I,x,R)},V=(u,d,g,v,y,A,I,x)=>{let R,w;const{type:H,props:F,shapeFlag:j,transition:K,dirs:z}=u;if(R=u.el=i(u.type,A,F&&F.is,F),j&8?f(R,u.children):j&16&&C(u.children,R,null,v,y,A&&H!=="foreignObject",I,x),z&&Fe(u,null,v,"created"),U(R,u,u.scopeId,I,v),F){for(const Q in F)Q!=="value"&&!Ft(Q)&&o(R,Q,null,F[Q],A,u.children,v,y,je);"value"in F&&o(R,"value",null,F.value),(w=F.onVnodeBeforeMount)&&Ce(w,v,u)}z&&Fe(u,null,v,"beforeMount");const G=(!y||y&&!y.pendingBranch)&&K&&!K.persisted;G&&K.beforeEnter(R),r(R,d,g),((w=F&&F.onVnodeMounted)||G||z)&&ge(()=>{w&&Ce(w,v,u),G&&K.enter(R),z&&Fe(u,null,v,"mounted")},y)},U=(u,d,g,v,y)=>{if(g&&b(u,g),v)for(let A=0;A{for(let w=R;w{const x=d.el=u.el;let{patchFlag:R,dynamicChildren:w,dirs:H}=d;R|=u.patchFlag&16;const F=u.props||te,j=d.props||te;let K;g&&tt(g,!1),(K=j.onVnodeBeforeUpdate)&&Ce(K,g,d,u),H&&Fe(d,u,g,"beforeUpdate"),g&&tt(g,!0);const z=y&&d.type!=="foreignObject";if(w?O(u.dynamicChildren,w,x,g,v,z,A):I||Z(u,d,x,null,g,v,z,A,!1),R>0){if(R&16)$(x,d,F,j,g,v,y);else if(R&2&&F.class!==j.class&&o(x,"class",null,j.class,y),R&4&&o(x,"style",F.style,j.style,y),R&8){const G=d.dynamicProps;for(let Q=0;Q{K&&Ce(K,g,d,u),H&&Fe(d,u,g,"updated")},v)},O=(u,d,g,v,y,A,I)=>{for(let x=0;x{if(g!==v){if(g!==te)for(const x in g)!Ft(x)&&!(x in v)&&o(u,x,g[x],null,I,d.children,y,A,je);for(const x in v){if(Ft(x))continue;const R=v[x],w=g[x];R!==w&&x!=="value"&&o(u,x,w,R,I,d.children,y,A,je)}"value"in v&&o(u,"value",g.value,v.value)}},P=(u,d,g,v,y,A,I,x,R)=>{const w=d.el=u?u.el:l(""),H=d.anchor=u?u.anchor:l("");let{patchFlag:F,dynamicChildren:j,slotScopeIds:K}=d;K&&(x=x?x.concat(K):K),u==null?(r(w,g,v),r(H,g,v),C(d.children,g,H,y,A,I,x,R)):F>0&&F&64&&j&&u.dynamicChildren?(O(u.dynamicChildren,j,g,y,A,I,x),(d.key!=null||y&&d===y.subTree)&&Ur(u,d,!0)):Z(u,d,g,H,y,A,I,x,R)},q=(u,d,g,v,y,A,I,x,R)=>{d.slotScopeIds=x,u==null?d.shapeFlag&512?y.ctx.activate(d,g,v,I,R):M(d,g,v,y,A,I,R):ye(u,d,R)},M=(u,d,g,v,y,A,I)=>{const x=u.component=dc(u,v,y);if(zt(u)&&(x.ctx.renderer=ft),hc(x),x.asyncDep){if(y&&y.registerDep(x,J),!u.el){const R=x.subTree=ie(we);_(null,R,d,g)}return}J(x,u,d,g,y,A,I)},ye=(u,d,g)=>{const v=d.component=u.component;if(wl(u,d,g))if(v.asyncDep&&!v.asyncResolved){ne(v,d,g);return}else v.next=d,pl(v.update),v.update();else d.el=u.el,v.vnode=d},J=(u,d,g,v,y,A,I)=>{const x=()=>{if(u.isMounted){let{next:H,bu:F,u:j,parent:K,vnode:z}=u,G=H,Q;tt(u,!1),H?(H.el=z.el,ne(u,H,I)):H=z,F&&fn(F),(Q=H.props&&H.props.onVnodeBeforeUpdate)&&Ce(Q,K,H,z),tt(u,!0);const le=Un(u),Te=u.subTree;u.subTree=le,S(Te,le,h(Te.el),Jt(Te),u,y,A),H.el=le.el,G===null&&El(u,le.el),j&&ge(j,y),(Q=H.props&&H.props.onVnodeUpdated)&&ge(()=>Ce(Q,K,H,z),y)}else{let H;const{el:F,props:j}=d,{bm:K,m:z,parent:G}=u,Q=vt(d);if(tt(u,!1),K&&fn(K),!Q&&(H=j&&j.onVnodeBeforeMount)&&Ce(H,G,d),tt(u,!0),F&&Dn){const le=()=>{u.subTree=Un(u),Dn(F,u.subTree,u,y,null)};Q?d.type.__asyncLoader().then(()=>!u.isUnmounted&&le()):le()}else{const le=u.subTree=Un(u);S(null,le,g,v,u,y,A),d.el=le.el}if(z&&ge(z,y),!Q&&(H=j&&j.onVnodeMounted)){const le=d;ge(()=>Ce(H,G,le),y)}(d.shapeFlag&256||G&&vt(G.vnode)&&G.vnode.shapeFlag&256)&&u.a&&ge(u.a,y),u.isMounted=!0,d=g=v=null}},R=u.effect=new Ar(x,()=>In(w),u.scope),w=u.update=()=>R.run();w.id=u.uid,tt(u,!0),w()},ne=(u,d,g)=>{d.component=u;const v=u.vnode.props;u.vnode=d,u.next=null,Xl(u,d.props,v,g),Zl(u,d.children,g),Tt(),os(),At()},Z=(u,d,g,v,y,A,I,x,R=!1)=>{const w=u&&u.children,H=u?u.shapeFlag:0,F=d.children,{patchFlag:j,shapeFlag:K}=d;if(j>0){if(j&128){Xt(w,F,g,v,y,A,I,x,R);return}else if(j&256){Ge(w,F,g,v,y,A,I,x,R);return}}K&8?(H&16&&je(w,y,A),F!==w&&f(g,F)):H&16?K&16?Xt(w,F,g,v,y,A,I,x,R):je(w,y,A,!0):(H&8&&f(g,""),K&16&&C(F,g,v,y,A,I,x,R))},Ge=(u,d,g,v,y,A,I,x,R)=>{u=u||gt,d=d||gt;const w=u.length,H=d.length,F=Math.min(w,H);let j;for(j=0;jH?je(u,y,A,!0,!1,F):C(d,g,v,y,A,I,x,R,F)},Xt=(u,d,g,v,y,A,I,x,R)=>{let w=0;const H=d.length;let F=u.length-1,j=H-1;for(;w<=F&&w<=j;){const K=u[w],z=d[w]=R?qe(d[w]):Ae(d[w]);if(ot(K,z))S(K,z,g,null,y,A,I,x,R);else break;w++}for(;w<=F&&w<=j;){const K=u[F],z=d[j]=R?qe(d[j]):Ae(d[j]);if(ot(K,z))S(K,z,g,null,y,A,I,x,R);else break;F--,j--}if(w>F){if(w<=j){const K=j+1,z=Kj)for(;w<=F;)Ie(u[w],y,A,!0),w++;else{const K=w,z=w,G=new Map;for(w=z;w<=j;w++){const ve=d[w]=R?qe(d[w]):Ae(d[w]);ve.key!=null&&G.set(ve.key,w)}let Q,le=0;const Te=j-z+1;let dt=!1,Yr=0;const Ot=new Array(Te);for(w=0;w=Te){Ie(ve,y,A,!0);continue}let Pe;if(ve.key!=null)Pe=G.get(ve.key);else for(Q=z;Q<=j;Q++)if(Ot[Q-z]===0&&ot(ve,d[Q])){Pe=Q;break}Pe===void 0?Ie(ve,y,A,!0):(Ot[Pe-z]=w+1,Pe>=Yr?Yr=Pe:dt=!0,S(ve,d[Pe],g,null,y,A,I,x,R),le++)}const Xr=dt?nc(Ot):gt;for(Q=Xr.length-1,w=Te-1;w>=0;w--){const ve=z+w,Pe=d[ve],Jr=ve+1{const{el:A,type:I,transition:x,children:R,shapeFlag:w}=u;if(w&6){et(u.component.subTree,d,g,v);return}if(w&128){u.suspense.move(d,g,v);return}if(w&64){I.move(u,d,g,ft);return}if(I===me){r(A,d,g);for(let F=0;Fx.enter(A),y);else{const{leave:F,delayLeave:j,afterLeave:K}=x,z=()=>r(A,d,g),G=()=>{F(A,()=>{z(),K&&K()})};j?j(A,z,G):G()}else r(A,d,g)},Ie=(u,d,g,v=!1,y=!1)=>{const{type:A,props:I,ref:x,children:R,dynamicChildren:w,shapeFlag:H,patchFlag:F,dirs:j}=u;if(x!=null&&wn(x,null,g,u,!0),H&256){d.ctx.deactivate(u);return}const K=H&1&&j,z=!vt(u);let G;if(z&&(G=I&&I.onVnodeBeforeUnmount)&&Ce(G,d,u),H&6)fi(u.component,g,v);else{if(H&128){u.suspense.unmount(g,v);return}K&&Fe(u,null,d,"beforeUnmount"),H&64?u.type.remove(u,d,g,y,ft,v):w&&(A!==me||F>0&&F&64)?je(w,d,g,!1,!0):(A===me&&F&384||!y&&H&16)&&je(R,d,g),v&&qr(u)}(z&&(G=I&&I.onVnodeUnmounted)||K)&&ge(()=>{G&&Ce(G,d,u),K&&Fe(u,null,d,"unmounted")},g)},qr=u=>{const{type:d,el:g,anchor:v,transition:y}=u;if(d===me){ui(g,v);return}if(d===$t){T(u);return}const A=()=>{s(g),y&&!y.persisted&&y.afterLeave&&y.afterLeave()};if(u.shapeFlag&1&&y&&!y.persisted){const{leave:I,delayLeave:x}=y,R=()=>I(g,A);x?x(u.el,A,R):R()}else A()},ui=(u,d)=>{let g;for(;u!==d;)g=p(u),s(u),u=g;s(d)},fi=(u,d,g)=>{const{bum:v,scope:y,update:A,subTree:I,um:x}=u;v&&fn(v),y.stop(),A&&(A.active=!1,Ie(I,u,d,g)),x&&ge(x,d),ge(()=>{u.isUnmounted=!0},d),d&&d.pendingBranch&&!d.isUnmounted&&u.asyncDep&&!u.asyncResolved&&u.suspenseId===d.pendingId&&(d.deps--,d.deps===0&&d.resolve())},je=(u,d,g,v=!1,y=!1,A=0)=>{for(let I=A;Iu.shapeFlag&6?Jt(u.component.subTree):u.shapeFlag&128?u.suspense.next():p(u.anchor||u.el),zr=(u,d,g)=>{u==null?d._vnode&&Ie(d._vnode,null,null,!0):S(d._vnode||null,u,d,null,null,null,g),os(),_n(),d._vnode=u},ft={p:S,um:Ie,m:et,r:qr,mt:M,mc:C,pc:Z,pbc:O,n:Jt,o:e};let jn,Dn;return t&&([jn,Dn]=t(ft)),{render:zr,hydrate:jn,createApp:ql(zr,jn)}}function tt({effect:e,update:t},n){e.allowRecurse=t.allowRecurse=n}function Ur(e,t,n=!1){const r=e.children,s=t.children;if(k(r)&&k(s))for(let o=0;o>1,e[n[l]]0&&(t[r]=n[o-1]),n[o]=r)}}for(o=n.length,i=n[o-1];o-- >0;)n[o]=i,i=t[i];return n}const rc=e=>e.__isTeleport,Nt=e=>e&&(e.disabled||e.disabled===""),_s=e=>typeof SVGElement<"u"&&e instanceof SVGElement,pr=(e,t)=>{const n=e&&e.to;return oe(n)?t?t(n):null:n},sc={__isTeleport:!0,process(e,t,n,r,s,o,i,l,c,a){const{mc:f,pc:h,pbc:p,o:{insert:b,querySelector:E,createText:S,createComment:L}}=a,_=Nt(t.props);let{shapeFlag:m,children:N,dynamicChildren:T}=t;if(e==null){const D=t.el=S(""),V=t.anchor=S("");b(D,n,r),b(V,n,r);const U=t.target=pr(t.props,E),C=t.targetAnchor=S("");U&&(b(C,U),i=i||_s(U));const B=(O,$)=>{m&16&&f(N,O,$,s,o,i,l,c)};_?B(n,V):U&&B(U,C)}else{t.el=e.el;const D=t.anchor=e.anchor,V=t.target=e.target,U=t.targetAnchor=e.targetAnchor,C=Nt(e.props),B=C?n:V,O=C?D:U;if(i=i||_s(V),T?(p(e.dynamicChildren,T,B,s,o,i,l),Ur(e,t,!0)):c||h(e,t,B,O,s,o,i,l,!1),_)C||on(t,n,D,a,1);else if((t.props&&t.props.to)!==(e.props&&e.props.to)){const $=t.target=pr(t.props,E);$&&on(t,$,null,a,0)}else C&&on(t,V,U,a,1)}Mo(t)},remove(e,t,n,r,{um:s,o:{remove:o}},i){const{shapeFlag:l,children:c,anchor:a,targetAnchor:f,target:h,props:p}=e;if(h&&o(f),(i||!Nt(p))&&(o(a),l&16))for(let b=0;b0?Oe||gt:null,ic(),Kt>0&&Oe&&Oe.push(e),e}function nu(e,t,n,r,s,o){return $o(Do(e,t,n,r,s,o,!0))}function Ho(e,t,n,r,s){return $o(ie(e,t,n,r,s,!0))}function En(e){return e?e.__v_isVNode===!0:!1}function ot(e,t){return e.type===t.type&&e.key===t.key}const $n="__vInternal",jo=({key:e})=>e??null,dn=({ref:e,ref_key:t,ref_for:n})=>(typeof e=="number"&&(e=""+e),e!=null?oe(e)||ue(e)||W(e)?{i:fe,r:e,k:t,f:!!n}:e:null);function Do(e,t=null,n=null,r=0,s=null,o=e===me?0:1,i=!1,l=!1){const c={__v_isVNode:!0,__v_skip:!0,type:e,props:t,key:t&&jo(t),ref:t&&dn(t),scopeId:Fn,slotScopeIds:null,children:n,component:null,suspense:null,ssContent:null,ssFallback:null,dirs:null,transition:null,el:null,anchor:null,target:null,targetAnchor:null,staticCount:0,shapeFlag:o,patchFlag:r,dynamicProps:s,dynamicChildren:null,appContext:null,ctx:fe};return l?(Br(c,n),o&128&&e.normalize(c)):n&&(c.shapeFlag|=oe(n)?8:16),Kt>0&&!i&&Oe&&(c.patchFlag>0||o&6)&&c.patchFlag!==32&&Oe.push(c),c}const ie=lc;function lc(e,t=null,n=null,r=0,s=null,o=!1){if((!e||e===Co)&&(e=we),En(e)){const l=Qe(e,t,!0);return n&&Br(l,n),Kt>0&&!o&&Oe&&(l.shapeFlag&6?Oe[Oe.indexOf(e)]=l:Oe.push(l)),l.patchFlag|=-2,l}if(_c(e)&&(e=e.__vccOpts),t){t=cc(t);let{class:l,style:c}=t;l&&!oe(l)&&(t.class=xr(l)),ee(c)&&(io(c)&&!k(c)&&(c=ce({},c)),t.style=Cr(c))}const i=oe(e)?1:Cl(e)?128:rc(e)?64:ee(e)?4:W(e)?2:0;return Do(e,t,n,r,s,i,o,!0)}function cc(e){return e?io(e)||$n in e?ce({},e):e:null}function Qe(e,t,n=!1){const{props:r,ref:s,patchFlag:o,children:i}=e,l=t?ac(r||{},t):r;return{__v_isVNode:!0,__v_skip:!0,type:e.type,props:l,key:l&&jo(l),ref:t&&t.ref?n&&s?k(s)?s.concat(dn(t)):[s,dn(t)]:dn(t):s,scopeId:e.scopeId,slotScopeIds:e.slotScopeIds,children:i,target:e.target,targetAnchor:e.targetAnchor,staticCount:e.staticCount,shapeFlag:e.shapeFlag,patchFlag:t&&e.type!==me?o===-1?16:o|16:o,dynamicProps:e.dynamicProps,dynamicChildren:e.dynamicChildren,appContext:e.appContext,dirs:e.dirs,transition:e.transition,component:e.component,suspense:e.suspense,ssContent:e.ssContent&&Qe(e.ssContent),ssFallback:e.ssFallback&&Qe(e.ssFallback),el:e.el,anchor:e.anchor,ctx:e.ctx,ce:e.ce}}function Uo(e=" ",t=0){return ie(Et,null,e,t)}function ru(e,t){const n=ie($t,null,e);return n.staticCount=t,n}function su(e="",t=!1){return t?(No(),Ho(we,null,e)):ie(we,null,e)}function Ae(e){return e==null||typeof e=="boolean"?ie(we):k(e)?ie(me,null,e.slice()):typeof e=="object"?qe(e):ie(Et,null,String(e))}function qe(e){return e.el===null&&e.patchFlag!==-1||e.memo?e:Qe(e)}function Br(e,t){let n=0;const{shapeFlag:r}=e;if(t==null)t=null;else if(k(t))n=16;else if(typeof t=="object")if(r&65){const s=t.default;s&&(s._c&&(s._d=!1),Br(e,s()),s._c&&(s._d=!0));return}else{n=32;const s=t._;!s&&!($n in t)?t._ctx=fe:s===3&&fe&&(fe.slots._===1?t._=1:(t._=2,e.patchFlag|=1024))}else W(t)?(t={default:t,_ctx:fe},n=32):(t=String(t),r&64?(n=16,t=[Uo(t)]):n=8);e.children=t,e.shapeFlag|=n}function ac(...e){const t={};for(let n=0;nae||fe;let kr,ht,vs="__VUE_INSTANCE_SETTERS__";(ht=rr()[vs])||(ht=rr()[vs]=[]),ht.push(e=>ae=e),kr=e=>{ht.length>1?ht.forEach(t=>t(e)):ht[0](e)};const Ze=e=>{kr(e),e.scope.on()},Xe=()=>{ae&&ae.scope.off(),kr(null)};function Bo(e){return e.vnode.shapeFlag&4}let Ct=!1;function hc(e,t=!1){Ct=t;const{props:n,children:r}=e.vnode,s=Bo(e);Yl(e,n,s,t),Ql(e,r);const o=s?pc(e,t):void 0;return Ct=!1,o}function pc(e,t){const n=e.type;e.accessCache=Object.create(null),e.proxy=Lt(new Proxy(e.ctx,jl));const{setup:r}=n;if(r){const s=e.setupContext=r.length>1?Ko(e):null;Ze(e),Tt();const o=Ye(r,e,0,[e.props,s]);if(At(),Xe(),wr(o)){if(o.then(Xe,Xe),t)return o.then(i=>{bs(e,i,t)}).catch(i=>{qt(i,e,0)});e.asyncDep=o}else bs(e,o,t)}else ko(e,t)}function bs(e,t,n){W(t)?e.type.__ssrInlineRender?e.ssrRender=t:e.render=t:ee(t)&&(e.setupState=ao(t)),ko(e,n)}let ws;function ko(e,t,n){const r=e.type;if(!e.render){if(!t&&ws&&!r.render){const s=r.template||jr(e).template;if(s){const{isCustomElement:o,compilerOptions:i}=e.appContext.config,{delimiters:l,compilerOptions:c}=r,a=ce(ce({isCustomElement:o,delimiters:l},i),c);r.render=ws(s,a)}}e.render=r.render||Me}Ze(e),Tt(),Ul(e),At(),Xe()}function gc(e){return e.attrsProxy||(e.attrsProxy=new Proxy(e.attrs,{get(t,n){return _e(e,"get","$attrs"),t[n]}}))}function Ko(e){const t=n=>{e.exposed=n||{}};return{get attrs(){return gc(e)},slots:e.slots,emit:e.emit,expose:t}}function Hn(e){if(e.exposed)return e.exposeProxy||(e.exposeProxy=new Proxy(ao(Lt(e.exposed)),{get(t,n){if(n in t)return t[n];if(n in Mt)return Mt[n](e)},has(t,n){return n in t||n in Mt}}))}function mc(e,t=!0){return W(e)?e.displayName||e.name:e.name||t&&e.__name}function _c(e){return W(e)&&"__vccOpts"in e}const re=(e,t)=>fl(e,t,Ct);function gr(e,t,n){const r=arguments.length;return r===2?ee(t)&&!k(t)?En(t)?ie(e,null,[t]):ie(e,t):ie(e,null,t):(r>3?n=Array.prototype.slice.call(arguments,2):r===3&&En(n)&&(n=[n]),ie(e,t,n))}const yc=Symbol.for("v-scx"),vc=()=>bt(yc),bc="3.3.4",wc="http://www.w3.org/2000/svg",it=typeof document<"u"?document:null,Es=it&&it.createElement("template"),Ec={insert:(e,t,n)=>{t.insertBefore(e,n||null)},remove:e=>{const t=e.parentNode;t&&t.removeChild(e)},createElement:(e,t,n,r)=>{const s=t?it.createElementNS(wc,e):it.createElement(e,n?{is:n}:void 0);return e==="select"&&r&&r.multiple!=null&&s.setAttribute("multiple",r.multiple),s},createText:e=>it.createTextNode(e),createComment:e=>it.createComment(e),setText:(e,t)=>{e.nodeValue=t},setElementText:(e,t)=>{e.textContent=t},parentNode:e=>e.parentNode,nextSibling:e=>e.nextSibling,querySelector:e=>it.querySelector(e),setScopeId(e,t){e.setAttribute(t,"")},insertStaticContent(e,t,n,r,s,o){const i=n?n.previousSibling:t.lastChild;if(s&&(s===o||s.nextSibling))for(;t.insertBefore(s.cloneNode(!0),n),!(s===o||!(s=s.nextSibling)););else{Es.innerHTML=r?`${e}`:e;const l=Es.content;if(r){const c=l.firstChild;for(;c.firstChild;)l.appendChild(c.firstChild);l.removeChild(c)}t.insertBefore(l,n)}return[i?i.nextSibling:t.firstChild,n?n.previousSibling:t.lastChild]}};function Cc(e,t,n){const r=e._vtc;r&&(t=(t?[t,...r]:[...r]).join(" ")),t==null?e.removeAttribute("class"):n?e.setAttribute("class",t):e.className=t}function xc(e,t,n){const r=e.style,s=oe(n);if(n&&!s){if(t&&!oe(t))for(const o in t)n[o]==null&&mr(r,o,"");for(const o in n)mr(r,o,n[o])}else{const o=r.display;s?t!==n&&(r.cssText=n):t&&e.removeAttribute("style"),"_vod"in e&&(r.display=o)}}const Cs=/\s*!important$/;function mr(e,t,n){if(k(n))n.forEach(r=>mr(e,t,r));else if(n==null&&(n=""),t.startsWith("--"))e.setProperty(t,n);else{const r=Tc(e,t);Cs.test(n)?e.setProperty(ut(r),n.replace(Cs,""),"important"):e[r]=n}}const xs=["Webkit","Moz","ms"],Wn={};function Tc(e,t){const n=Wn[t];if(n)return n;let r=He(t);if(r!=="filter"&&r in e)return Wn[t]=r;r=Tn(r);for(let s=0;sVn||(Pc.then(()=>Vn=0),Vn=Date.now());function Lc(e,t){const n=r=>{if(!r._vts)r._vts=Date.now();else if(r._vts<=n.attached)return;xe(Mc(r,n.value),t,5,[r])};return n.value=e,n.attached=Fc(),n}function Mc(e,t){if(k(t)){const n=e.stopImmediatePropagation;return e.stopImmediatePropagation=()=>{n.call(e),e._stopped=!0},t.map(r=>s=>!s._stopped&&r&&r(s))}else return t}const Ss=/^on[a-z]/,Nc=(e,t,n,r,s=!1,o,i,l,c)=>{t==="class"?Cc(e,r,s):t==="style"?xc(e,n,r):Vt(t)?yr(t)||Rc(e,t,n,r,i):(t[0]==="."?(t=t.slice(1),!0):t[0]==="^"?(t=t.slice(1),!1):$c(e,t,r,s))?Sc(e,t,r,o,i,l,c):(t==="true-value"?e._trueValue=r:t==="false-value"&&(e._falseValue=r),Ac(e,t,r,s))};function $c(e,t,n,r){return r?!!(t==="innerHTML"||t==="textContent"||t in e&&Ss.test(t)&&W(n)):t==="spellcheck"||t==="draggable"||t==="translate"||t==="form"||t==="list"&&e.tagName==="INPUT"||t==="type"&&e.tagName==="TEXTAREA"||Ss.test(t)&&oe(n)?!1:t in e}const We="transition",Rt="animation",Wo=(e,{slots:t})=>gr(Sl,Hc(e),t);Wo.displayName="Transition";const Vo={name:String,type:String,css:{type:Boolean,default:!0},duration:[String,Number,Object],enterFromClass:String,enterActiveClass:String,enterToClass:String,appearFromClass:String,appearActiveClass:String,appearToClass:String,leaveFromClass:String,leaveActiveClass:String,leaveToClass:String};Wo.props=ce({},_o,Vo);const nt=(e,t=[])=>{k(e)?e.forEach(n=>n(...t)):e&&e(...t)},Os=e=>e?k(e)?e.some(t=>t.length>1):e.length>1:!1;function Hc(e){const t={};for(const P in e)P in Vo||(t[P]=e[P]);if(e.css===!1)return t;const{name:n="v",type:r,duration:s,enterFromClass:o=`${n}-enter-from`,enterActiveClass:i=`${n}-enter-active`,enterToClass:l=`${n}-enter-to`,appearFromClass:c=o,appearActiveClass:a=i,appearToClass:f=l,leaveFromClass:h=`${n}-leave-from`,leaveActiveClass:p=`${n}-leave-active`,leaveToClass:b=`${n}-leave-to`}=e,E=jc(s),S=E&&E[0],L=E&&E[1],{onBeforeEnter:_,onEnter:m,onEnterCancelled:N,onLeave:T,onLeaveCancelled:D,onBeforeAppear:V=_,onAppear:U=m,onAppearCancelled:C=N}=t,B=(P,q,M)=>{rt(P,q?f:l),rt(P,q?a:i),M&&M()},O=(P,q)=>{P._isLeaving=!1,rt(P,h),rt(P,b),rt(P,p),q&&q()},$=P=>(q,M)=>{const ye=P?U:m,J=()=>B(q,P,M);nt(ye,[q,J]),Rs(()=>{rt(q,P?c:o),Ve(q,P?f:l),Os(ye)||Is(q,r,S,J)})};return ce(t,{onBeforeEnter(P){nt(_,[P]),Ve(P,o),Ve(P,i)},onBeforeAppear(P){nt(V,[P]),Ve(P,c),Ve(P,a)},onEnter:$(!1),onAppear:$(!0),onLeave(P,q){P._isLeaving=!0;const M=()=>O(P,q);Ve(P,h),Bc(),Ve(P,p),Rs(()=>{P._isLeaving&&(rt(P,h),Ve(P,b),Os(T)||Is(P,r,L,M))}),nt(T,[P,M])},onEnterCancelled(P){B(P,!1),nt(N,[P])},onAppearCancelled(P){B(P,!0),nt(C,[P])},onLeaveCancelled(P){O(P),nt(D,[P])}})}function jc(e){if(e==null)return null;if(ee(e))return[qn(e.enter),qn(e.leave)];{const t=qn(e);return[t,t]}}function qn(e){return yi(e)}function Ve(e,t){t.split(/\s+/).forEach(n=>n&&e.classList.add(n)),(e._vtc||(e._vtc=new Set)).add(t)}function rt(e,t){t.split(/\s+/).forEach(r=>r&&e.classList.remove(r));const{_vtc:n}=e;n&&(n.delete(t),n.size||(e._vtc=void 0))}function Rs(e){requestAnimationFrame(()=>{requestAnimationFrame(e)})}let Dc=0;function Is(e,t,n,r){const s=e._endId=++Dc,o=()=>{s===e._endId&&r()};if(n)return setTimeout(o,n);const{type:i,timeout:l,propCount:c}=Uc(e,t);if(!i)return r();const a=i+"end";let f=0;const h=()=>{e.removeEventListener(a,p),o()},p=b=>{b.target===e&&++f>=c&&h()};setTimeout(()=>{f(n[E]||"").split(", "),s=r(`${We}Delay`),o=r(`${We}Duration`),i=Ps(s,o),l=r(`${Rt}Delay`),c=r(`${Rt}Duration`),a=Ps(l,c);let f=null,h=0,p=0;t===We?i>0&&(f=We,h=i,p=o.length):t===Rt?a>0&&(f=Rt,h=a,p=c.length):(h=Math.max(i,a),f=h>0?i>a?We:Rt:null,p=f?f===We?o.length:c.length:0);const b=f===We&&/\b(transform|all)(,|$)/.test(r(`${We}Property`).toString());return{type:f,timeout:h,propCount:p,hasTransform:b}}function Ps(e,t){for(;e.lengthFs(n)+Fs(e[r])))}function Fs(e){return Number(e.slice(0,-1).replace(",","."))*1e3}function Bc(){return document.body.offsetHeight}const Ls=e=>{const t=e.props["onUpdate:modelValue"]||!1;return k(t)?n=>fn(t,n):t};function kc(e){e.target.composing=!0}function Ms(e){const t=e.target;t.composing&&(t.composing=!1,t.dispatchEvent(new Event("input")))}const ou={created(e,{modifiers:{lazy:t,trim:n,number:r}},s){e._assign=Ls(s);const o=r||s.props&&s.props.type==="number";pt(e,t?"change":"input",i=>{if(i.target.composing)return;let l=e.value;n&&(l=l.trim()),o&&(l=nr(l)),e._assign(l)}),n&&pt(e,"change",()=>{e.value=e.value.trim()}),t||(pt(e,"compositionstart",kc),pt(e,"compositionend",Ms),pt(e,"change",Ms))},mounted(e,{value:t}){e.value=t??""},beforeUpdate(e,{value:t,modifiers:{lazy:n,trim:r,number:s}},o){if(e._assign=Ls(o),e.composing||document.activeElement===e&&e.type!=="range"&&(n||r&&e.value.trim()===t||(s||e.type==="number")&&nr(e.value)===t))return;const i=t??"";e.value!==i&&(e.value=i)}},Kc=["ctrl","shift","alt","meta"],Wc={stop:e=>e.stopPropagation(),prevent:e=>e.preventDefault(),self:e=>e.target!==e.currentTarget,ctrl:e=>!e.ctrlKey,shift:e=>!e.shiftKey,alt:e=>!e.altKey,meta:e=>!e.metaKey,left:e=>"button"in e&&e.button!==0,middle:e=>"button"in e&&e.button!==1,right:e=>"button"in e&&e.button!==2,exact:(e,t)=>Kc.some(n=>e[`${n}Key`]&&!t.includes(n))},iu=(e,t)=>(n,...r)=>{for(let s=0;sn=>{if(!("key"in n))return;const r=ut(n.key);if(t.some(s=>s===r||Vc[s]===r))return e(n)},qo=ce({patchProp:Nc},Ec);let jt,Ns=!1;function qc(){return jt||(jt=ec(qo))}function zc(){return jt=Ns?jt:tc(qo),Ns=!0,jt}const cu=(...e)=>{const t=qc().createApp(...e),{mount:n}=t;return t.mount=r=>{const s=zo(r);if(!s)return;const o=t._component;!W(o)&&!o.render&&!o.template&&(o.template=s.innerHTML),s.innerHTML="";const i=n(s,!1,s instanceof SVGElement);return s instanceof Element&&(s.removeAttribute("v-cloak"),s.setAttribute("data-v-app","")),i},t},au=(...e)=>{const t=zc().createApp(...e),{mount:n}=t;return t.mount=r=>{const s=zo(r);if(s)return n(s,!0,s instanceof SVGElement)},t};function zo(e){return oe(e)?document.querySelector(e):e}const uu=(e,t)=>{const n=e.__vccOpts||e;for(const[r,s]of t)n[r]=s;return n},fu="/garden/screenshot_1717381273245_0.png",du="/garden/da2_1717378483173_0.png",hu="/garden/editors_1717378509527_0.png",pu="/garden/simulator_1717378525890_0.jpg",gu="/garden/da1_1717378469912_0.png",mu="/garden/da6_1717379962786_0.png",_u="/garden/da7_1717379991458_0.png",yu="/garden/da8_1717380011914_0.png",vu="/garden/da3_1717380046653_0.png",bu="/garden/da9_1717380177060_0.png",wu="/garden/6346b024-885e-45e0-9df6-5ee0311133f7_1718332409063_0.png",Eu="/garden/ce7b2612-2ddb-423e-82eb-95c2ed08c4da_1718332277410_0.png",Cu="/garden/system-architecture-600_1717384793933_0.jpg",xu="/garden/new-interface_1717384734845_0.png",Tu="/garden/documentation_1717384823218_0.png",Au="/garden/unittests_1717384825666_0.png",Su="/garden/screenshot_1717383987886_0.png",Ou="/garden/debug_1717384018620_0.png",Ru="/garden/sandsoftime_1717383994964_0.png",Yc="modulepreload",Xc=function(e){return"/"+e},$s={},Iu=function(t,n,r){let s=Promise.resolve();if(n&&n.length>0){document.getElementsByTagName("link");const o=document.querySelector("meta[property=csp-nonce]"),i=(o==null?void 0:o.nonce)||(o==null?void 0:o.getAttribute("nonce"));s=Promise.all(n.map(l=>{if(l=Xc(l),l in $s)return;$s[l]=!0;const c=l.endsWith(".css"),a=c?'[rel="stylesheet"]':"";if(document.querySelector(`link[href="${l}"]${a}`))return;const f=document.createElement("link");if(f.rel=c?"stylesheet":Yc,c||(f.as="script",f.crossOrigin=""),f.href=l,i&&f.setAttribute("nonce",i),document.head.appendChild(f),c)return new Promise((h,p)=>{f.addEventListener("load",h),f.addEventListener("error",()=>p(new Error(`Unable to preload CSS for ${l}`)))})}))}return s.then(()=>t()).catch(o=>{const i=new Event("vite:preloadError",{cancelable:!0});if(i.payload=o,window.dispatchEvent(i),!i.defaultPrevented)throw o})},Jc=window.__VP_SITE_DATA__;function Kr(e){return Xs()?(Si(e),!0):!1}function $e(e){return typeof e=="function"?e():co(e)}const Yo=typeof window<"u"&&typeof document<"u";typeof WorkerGlobalScope<"u"&&globalThis instanceof WorkerGlobalScope;const Qc=Object.prototype.toString,Zc=e=>Qc.call(e)==="[object Object]",Wt=()=>{},Hs=Gc();function Gc(){var e,t;return Yo&&((e=window==null?void 0:window.navigator)==null?void 0:e.userAgent)&&(/iP(?:ad|hone|od)/.test(window.navigator.userAgent)||((t=window==null?void 0:window.navigator)==null?void 0:t.maxTouchPoints)>2&&/iPad|Macintosh/.test(window==null?void 0:window.navigator.userAgent))}function ea(e,t){function n(...r){return new Promise((s,o)=>{Promise.resolve(e(()=>t.apply(this,r),{fn:t,thisArg:this,args:r})).then(s).catch(o)})}return n}const Xo=e=>e();function ta(e,t={}){let n,r,s=Wt;const o=l=>{clearTimeout(l),s(),s=Wt};return l=>{const c=$e(e),a=$e(t.maxWait);return n&&o(n),c<=0||a!==void 0&&a<=0?(r&&(o(r),r=null),Promise.resolve(l())):new Promise((f,h)=>{s=t.rejectOnCancel?h:f,a&&!r&&(r=setTimeout(()=>{n&&o(n),r=null,f(l())},a)),n=setTimeout(()=>{r&&o(r),r=null,f(l())},c)})}}function na(e=Xo){const t=se(!0);function n(){t.value=!1}function r(){t.value=!0}const s=(...o)=>{t.value&&e(...o)};return{isActive:On(t),pause:n,resume:r,eventFilter:s}}function ra(e){return Yt()}function Jo(...e){if(e.length!==1)return cl(...e);const t=e[0];return typeof t=="function"?On(ol(()=>({get:t,set:Wt}))):se(t)}function Qo(e,t,n={}){const{eventFilter:r=Xo,...s}=n;return Ne(e,ea(r,t),s)}function sa(e,t,n={}){const{eventFilter:r,...s}=n,{eventFilter:o,pause:i,resume:l,isActive:c}=na(r);return{stop:Qo(e,t,{...s,eventFilter:o}),pause:i,resume:l,isActive:c}}function Wr(e,t=!0,n){ra()?St(e,n):t?e():Rn(e)}function Pu(e,t,n={}){const{debounce:r=0,maxWait:s=void 0,...o}=n;return Qo(e,t,{...o,eventFilter:ta(r,{maxWait:s})})}function Fu(e,t,n){let r;ue(n)?r={evaluating:n}:r={};const{lazy:s=!1,evaluating:o=void 0,shallow:i=!0,onError:l=Wt}=r,c=se(!s),a=i?Mr(t):se(t);let f=0;return $r(async h=>{if(!c.value)return;f++;const p=f;let b=!1;o&&Promise.resolve().then(()=>{o.value=!0});try{const E=await e(S=>{h(()=>{o&&(o.value=!1),b||S()})});p===f&&(a.value=E)}catch(E){l(E)}finally{o&&p===f&&(o.value=!1),b=!0}}),s?re(()=>(c.value=!0,a.value)):a}function Zo(e){var t;const n=$e(e);return(t=n==null?void 0:n.$el)!=null?t:n}const Re=Yo?window:void 0;function xt(...e){let t,n,r,s;if(typeof e[0]=="string"||Array.isArray(e[0])?([n,r,s]=e,t=Re):[t,n,r,s]=e,!t)return Wt;Array.isArray(n)||(n=[n]),Array.isArray(r)||(r=[r]);const o=[],i=()=>{o.forEach(f=>f()),o.length=0},l=(f,h,p,b)=>(f.addEventListener(h,p,b),()=>f.removeEventListener(h,p,b)),c=Ne(()=>[Zo(t),$e(s)],([f,h])=>{if(i(),!f)return;const p=Zc(h)?{...h}:h;o.push(...n.flatMap(b=>r.map(E=>l(f,b,E,p))))},{immediate:!0,flush:"post"}),a=()=>{c(),i()};return Kr(a),a}function oa(e){return typeof e=="function"?e:typeof e=="string"?t=>t.key===e:Array.isArray(e)?t=>e.includes(t.key):()=>!0}function Lu(...e){let t,n,r={};e.length===3?(t=e[0],n=e[1],r=e[2]):e.length===2?typeof e[1]=="object"?(t=!0,n=e[0],r=e[1]):(t=e[0],n=e[1]):(t=!0,n=e[0]);const{target:s=Re,eventName:o="keydown",passive:i=!1,dedupe:l=!1}=r,c=oa(t);return xt(s,o,f=>{f.repeat&&$e(l)||c(f)&&n(f)},i)}function ia(){const e=se(!1),t=Yt();return t&&St(()=>{e.value=!0},t),e}function la(e){const t=ia();return re(()=>(t.value,!!e()))}function Go(e,t={}){const{window:n=Re}=t,r=la(()=>n&&"matchMedia"in n&&typeof n.matchMedia=="function");let s;const o=se(!1),i=a=>{o.value=a.matches},l=()=>{s&&("removeEventListener"in s?s.removeEventListener("change",i):s.removeListener(i))},c=$r(()=>{r.value&&(l(),s=n.matchMedia($e(e)),"addEventListener"in s?s.addEventListener("change",i):s.addListener(i),o.value=s.matches)});return Kr(()=>{c(),l(),s=void 0}),o}const ln=typeof globalThis<"u"?globalThis:typeof window<"u"?window:typeof global<"u"?global:typeof self<"u"?self:{},cn="__vueuse_ssr_handlers__",ca=aa();function aa(){return cn in ln||(ln[cn]=ln[cn]||{}),ln[cn]}function ei(e,t){return ca[e]||t}function ua(e){return e==null?"any":e instanceof Set?"set":e instanceof Map?"map":e instanceof Date?"date":typeof e=="boolean"?"boolean":typeof e=="string"?"string":typeof e=="object"?"object":Number.isNaN(e)?"any":"number"}const fa={boolean:{read:e=>e==="true",write:e=>String(e)},object:{read:e=>JSON.parse(e),write:e=>JSON.stringify(e)},number:{read:e=>Number.parseFloat(e),write:e=>String(e)},any:{read:e=>e,write:e=>String(e)},string:{read:e=>e,write:e=>String(e)},map:{read:e=>new Map(JSON.parse(e)),write:e=>JSON.stringify(Array.from(e.entries()))},set:{read:e=>new Set(JSON.parse(e)),write:e=>JSON.stringify(Array.from(e))},date:{read:e=>new Date(e),write:e=>e.toISOString()}},js="vueuse-storage";function Vr(e,t,n,r={}){var s;const{flush:o="pre",deep:i=!0,listenToStorageChanges:l=!0,writeDefaults:c=!0,mergeDefaults:a=!1,shallow:f,window:h=Re,eventFilter:p,onError:b=O=>{console.error(O)},initOnMounted:E}=r,S=(f?Mr:se)(typeof t=="function"?t():t);if(!n)try{n=ei("getDefaultStorage",()=>{var O;return(O=Re)==null?void 0:O.localStorage})()}catch(O){b(O)}if(!n)return S;const L=$e(t),_=ua(L),m=(s=r.serializer)!=null?s:fa[_],{pause:N,resume:T}=sa(S,()=>V(S.value),{flush:o,deep:i,eventFilter:p});h&&l&&Wr(()=>{xt(h,"storage",C),xt(h,js,B),E&&C()}),E||C();function D(O,$){h&&h.dispatchEvent(new CustomEvent(js,{detail:{key:e,oldValue:O,newValue:$,storageArea:n}}))}function V(O){try{const $=n.getItem(e);if(O==null)D($,null),n.removeItem(e);else{const P=m.write(O);$!==P&&(n.setItem(e,P),D($,P))}}catch($){b($)}}function U(O){const $=O?O.newValue:n.getItem(e);if($==null)return c&&L!=null&&n.setItem(e,m.write(L)),L;if(!O&&a){const P=m.read($);return typeof a=="function"?a(P,L):_==="object"&&!Array.isArray(P)?{...L,...P}:P}else return typeof $!="string"?$:m.read($)}function C(O){if(!(O&&O.storageArea!==n)){if(O&&O.key==null){S.value=L;return}if(!(O&&O.key!==e)){N();try{(O==null?void 0:O.newValue)!==m.write(S.value)&&(S.value=U(O))}catch($){b($)}finally{O?Rn(T):T()}}}}function B(O){C(O.detail)}return S}function ti(e){return Go("(prefers-color-scheme: dark)",e)}function da(e={}){const{selector:t="html",attribute:n="class",initialValue:r="auto",window:s=Re,storage:o,storageKey:i="vueuse-color-scheme",listenToStorageChanges:l=!0,storageRef:c,emitAuto:a,disableTransition:f=!0}=e,h={auto:"",light:"light",dark:"dark",...e.modes||{}},p=ti({window:s}),b=re(()=>p.value?"dark":"light"),E=c||(i==null?Jo(r):Vr(i,r,o,{window:s,listenToStorageChanges:l})),S=re(()=>E.value==="auto"?b.value:E.value),L=ei("updateHTMLAttrs",(T,D,V)=>{const U=typeof T=="string"?s==null?void 0:s.document.querySelector(T):Zo(T);if(!U)return;let C;if(f&&(C=s.document.createElement("style"),C.appendChild(document.createTextNode("*,*::before,*::after{-webkit-transition:none!important;-moz-transition:none!important;-o-transition:none!important;-ms-transition:none!important;transition:none!important}")),s.document.head.appendChild(C)),D==="class"){const B=V.split(/\s/g);Object.values(h).flatMap(O=>(O||"").split(/\s/g)).filter(Boolean).forEach(O=>{B.includes(O)?U.classList.add(O):U.classList.remove(O)})}else U.setAttribute(D,V);f&&(s.getComputedStyle(C).opacity,document.head.removeChild(C))});function _(T){var D;L(t,n,(D=h[T])!=null?D:T)}function m(T){e.onChanged?e.onChanged(T,_):_(T)}Ne(S,m,{flush:"post",immediate:!0}),Wr(()=>m(S.value));const N=re({get(){return a?E.value:S.value},set(T){E.value=T}});try{return Object.assign(N,{store:E,system:b,state:S})}catch{return N}}function ha(e={}){const{valueDark:t="dark",valueLight:n="",window:r=Re}=e,s=da({...e,onChanged:(l,c)=>{var a;e.onChanged?(a=e.onChanged)==null||a.call(e,l==="dark",c,l):c(l)},modes:{dark:t,light:n}}),o=re(()=>s.system?s.system.value:ti({window:r}).value?"dark":"light");return re({get(){return s.value==="dark"},set(l){const c=l?"dark":"light";o.value===c?s.value="auto":s.value=c}})}function zn(e){return typeof Window<"u"&&e instanceof Window?e.document.documentElement:typeof Document<"u"&&e instanceof Document?e.documentElement:e}function Mu(e,t,n={}){const{window:r=Re}=n;return Vr(e,t,r==null?void 0:r.localStorage,n)}function ni(e){const t=window.getComputedStyle(e);if(t.overflowX==="scroll"||t.overflowY==="scroll"||t.overflowX==="auto"&&e.clientWidth1?!0:(t.preventDefault&&t.preventDefault(),!1)}const Yn=new WeakMap;function Nu(e,t=!1){const n=se(t);let r=null,s="";Ne(Jo(e),l=>{const c=zn($e(l));if(c){const a=c;if(Yn.get(a)||Yn.set(a,a.style.overflow),a.style.overflow!=="hidden"&&(s=a.style.overflow),a.style.overflow==="hidden")return n.value=!0;if(n.value)return a.style.overflow="hidden"}},{immediate:!0});const o=()=>{const l=zn($e(e));!l||n.value||(Hs&&(r=xt(l,"touchmove",c=>{pa(c)},{passive:!1})),l.style.overflow="hidden",n.value=!0)},i=()=>{const l=zn($e(e));!l||!n.value||(Hs&&(r==null||r()),l.style.overflow=s,Yn.delete(l),n.value=!1)};return Kr(i),re({get(){return n.value},set(l){l?o():i()}})}function $u(e,t,n={}){const{window:r=Re}=n;return Vr(e,t,r==null?void 0:r.sessionStorage,n)}function Hu(e={}){const{window:t=Re,behavior:n="auto"}=e;if(!t)return{x:se(0),y:se(0)};const r=se(t.scrollX),s=se(t.scrollY),o=re({get(){return r.value},set(l){scrollTo({left:l,behavior:n})}}),i=re({get(){return s.value},set(l){scrollTo({top:l,behavior:n})}});return xt(t,"scroll",()=>{r.value=t.scrollX,s.value=t.scrollY},{capture:!1,passive:!0}),{x:o,y:i}}function ju(e={}){const{window:t=Re,initialWidth:n=Number.POSITIVE_INFINITY,initialHeight:r=Number.POSITIVE_INFINITY,listenOrientation:s=!0,includeScrollbar:o=!0}=e,i=se(n),l=se(r),c=()=>{t&&(o?(i.value=t.innerWidth,l.value=t.innerHeight):(i.value=t.document.documentElement.clientWidth,l.value=t.document.documentElement.clientHeight))};if(c(),Wr(c),xt("resize",c,{passive:!0}),s){const a=Go("(orientation: portrait)");Ne(a,()=>c())}return{width:i,height:l}}var Xn={BASE_URL:"/",MODE:"production",DEV:!1,PROD:!0,SSR:!1},Jn={};const ri=/^(?:[a-z]+:|\/\/)/i,ga="vitepress-theme-appearance",ma=/#.*$/,_a=/[?#].*$/,ya=/(?:(^|\/)index)?\.(?:md|html)$/,de=typeof document<"u",si={relativePath:"404.md",filePath:"",title:"404",description:"Not Found",headers:[],frontmatter:{sidebar:!1,layout:"page"},lastUpdated:0,isNotFound:!0};function va(e,t,n=!1){if(t===void 0)return!1;if(e=Ds(`/${e}`),n)return new RegExp(t).test(e);if(Ds(t)!==e)return!1;const r=t.match(ma);return r?(de?location.hash:"")===r[0]:!0}function Ds(e){return decodeURI(e).replace(_a,"").replace(ya,"$1")}function ba(e){return ri.test(e)}function wa(e,t){return Object.keys((e==null?void 0:e.locales)||{}).find(n=>n!=="root"&&!ba(n)&&va(t,`/${n}/`,!0))||"root"}function Ea(e,t){var r,s,o,i,l,c,a;const n=wa(e,t);return Object.assign({},e,{localeIndex:n,lang:((r=e.locales[n])==null?void 0:r.lang)??e.lang,dir:((s=e.locales[n])==null?void 0:s.dir)??e.dir,title:((o=e.locales[n])==null?void 0:o.title)??e.title,titleTemplate:((i=e.locales[n])==null?void 0:i.titleTemplate)??e.titleTemplate,description:((l=e.locales[n])==null?void 0:l.description)??e.description,head:ii(e.head,((c=e.locales[n])==null?void 0:c.head)??[]),themeConfig:{...e.themeConfig,...(a=e.locales[n])==null?void 0:a.themeConfig}})}function oi(e,t){const n=t.title||e.title,r=t.titleTemplate??e.titleTemplate;if(typeof r=="string"&&r.includes(":title"))return r.replace(/:title/g,n);const s=Ca(e.title,r);return n===s.slice(3)?n:`${n}${s}`}function Ca(e,t){return t===!1?"":t===!0||t===void 0?` | ${e}`:e===t?"":` | ${t}`}function xa(e,t){const[n,r]=t;if(n!=="meta")return!1;const s=Object.entries(r)[0];return s==null?!1:e.some(([o,i])=>o===n&&i[s[0]]===s[1])}function ii(e,t){return[...e.filter(n=>!xa(t,n)),...t]}const Ta=/[\u0000-\u001F"#$&*+,:;<=>?[\]^`{|}\u007F]/g,Aa=/^[a-z]:/i;function Us(e){const t=Aa.exec(e),n=t?t[0]:"";return n+e.slice(n.length).replace(Ta,"_").replace(/(^|\/)_+(?=[^/]*$)/,"$1")}const Qn=new Set;function Sa(e){if(Qn.size===0){const n=typeof process=="object"&&(Jn==null?void 0:Jn.VITE_EXTRA_EXTENSIONS)||(Xn==null?void 0:Xn.VITE_EXTRA_EXTENSIONS)||"";("3g2,3gp,aac,ai,apng,au,avif,bin,bmp,cer,class,conf,crl,css,csv,dll,doc,eps,epub,exe,gif,gz,ics,ief,jar,jpe,jpeg,jpg,js,json,jsonld,m4a,man,mid,midi,mjs,mov,mp2,mp3,mp4,mpe,mpeg,mpg,mpp,oga,ogg,ogv,ogx,opus,otf,p10,p7c,p7m,p7s,pdf,png,ps,qt,roff,rtf,rtx,ser,svg,t,tif,tiff,tr,ts,tsv,ttf,txt,vtt,wav,weba,webm,webp,woff,woff2,xhtml,xml,yaml,yml,zip"+(n&&typeof n=="string"?","+n:"")).split(",").forEach(r=>Qn.add(r))}const t=e.split(".").pop();return t==null||!Qn.has(t.toLowerCase())}function Du(e){return e.replace(/[|\\{}()[\]^$+*?.]/g,"\\$&").replace(/-/g,"\\x2d")}const Oa=Symbol(),at=Mr(Jc);function Uu(e){const t=re(()=>Ea(at.value,e.data.relativePath)),n=t.value.appearance,r=n==="force-dark"?se(!0):n?ha({storageKey:ga,initialValue:()=>typeof n=="string"?n:"auto",...typeof n=="object"?n:{}}):se(!1),s=se(de?location.hash:"");return de&&window.addEventListener("hashchange",()=>{s.value=location.hash}),Ne(()=>e.data,()=>{s.value=de?location.hash:""}),{site:t,theme:re(()=>t.value.themeConfig),page:re(()=>e.data),frontmatter:re(()=>e.data.frontmatter),params:re(()=>e.data.params),lang:re(()=>t.value.lang),dir:re(()=>e.data.frontmatter.dir||t.value.dir),localeIndex:re(()=>t.value.localeIndex||"root"),title:re(()=>oi(t.value,e.data)),description:re(()=>e.data.description||t.value.description),isDark:r,hash:re(()=>s.value)}}function Ra(){const e=bt(Oa);if(!e)throw new Error("vitepress data not properly injected in app");return e}function Ia(e,t){return`${e}${t}`.replace(/\/+/g,"/")}function Bs(e){return ri.test(e)||!e.startsWith("/")?e:Ia(at.value.base,e)}function Pa(e){let t=e.replace(/\.html$/,"");if(t=decodeURIComponent(t),t=t.replace(/\/$/,"/index"),de){const n="/";t=Us(t.slice(n.length).replace(/\//g,"_")||"index")+".md";let r=__VP_HASH_MAP__[t.toLowerCase()];if(r||(t=t.endsWith("_index.md")?t.slice(0,-9)+".md":t.slice(0,-3)+"_index.md",r=__VP_HASH_MAP__[t.toLowerCase()]),!r)return null;t=`${n}assets/${t}.${r}.js`}else t=`./${Us(t.slice(1).replace(/\//g,"_"))}.md.js`;return t}let hn=[];function Bu(e){hn.push(e),Nn(()=>{hn=hn.filter(t=>t!==e)})}function Fa(){let e=at.value.scrollOffset,t=0,n=24;if(typeof e=="object"&&"padding"in e&&(n=e.padding,e=e.selector),typeof e=="number")t=e;else if(typeof e=="string")t=ks(e,n);else if(Array.isArray(e))for(const r of e){const s=ks(r,n);if(s){t=s;break}}return t}function ks(e,t){const n=document.querySelector(e);if(!n)return 0;const r=n.getBoundingClientRect().bottom;return r<0?0:r+t}const La=Symbol(),li="http://a.com",Ma=()=>({path:"/",component:null,data:si});function ku(e,t){const n=Sn(Ma()),r={route:n,go:s};async function s(l=de?location.href:"/"){var c,a;l=Zn(l),await((c=r.onBeforeRouteChange)==null?void 0:c.call(r,l))!==!1&&(de&&l!==Zn(location.href)&&(history.replaceState({scrollPosition:window.scrollY},""),history.pushState({},"",l)),await i(l),await((a=r.onAfterRouteChanged)==null?void 0:a.call(r,l)))}let o=null;async function i(l,c=0,a=!1){var p;if(await((p=r.onBeforePageLoad)==null?void 0:p.call(r,l))===!1)return;const f=new URL(l,li),h=o=f.pathname;try{let b=await e(h);if(!b)throw new Error(`Page not found: ${h}`);if(o===h){o=null;const{default:E,__pageData:S}=b;if(!E)throw new Error(`Invalid route component: ${E}`);n.path=de?h:Bs(h),n.component=Lt(E),n.data=Lt(S),de&&Rn(()=>{let L=at.value.base+S.relativePath.replace(/(?:(^|\/)index)?\.md$/,"$1");if(!at.value.cleanUrls&&!L.endsWith("/")&&(L+=".html"),L!==f.pathname&&(f.pathname=L,l=L+f.search+f.hash,history.replaceState({},"",l)),f.hash&&!c){let _=null;try{_=document.getElementById(decodeURIComponent(f.hash).slice(1))}catch(m){console.warn(m)}if(_){Ks(_,f.hash);return}}window.scrollTo(0,c)})}}catch(b){if(!/fetch|Page not found/.test(b.message)&&!/^\/404(\.html|\/)?$/.test(l)&&console.error(b),!a)try{const E=await fetch(at.value.base+"hashmap.json");window.__VP_HASH_MAP__=await E.json(),await i(l,c,!0);return}catch{}if(o===h){o=null,n.path=de?h:Bs(h),n.component=t?Lt(t):null;const E=de?h.replace(/(^|\/)$/,"$1index").replace(/(\.html)?$/,".md").replace(/^\//,""):"404.md";n.data={...si,relativePath:E}}}}return de&&(history.state===null&&history.replaceState({},""),window.addEventListener("click",l=>{if(l.target.closest("button"))return;const a=l.target.closest("a");if(a&&!a.closest(".vp-raw")&&(a instanceof SVGElement||!a.download)){const{target:f}=a,{href:h,origin:p,pathname:b,hash:E,search:S}=new URL(a.href instanceof SVGAnimatedString?a.href.animVal:a.href,a.baseURI),L=new URL(location.href);!l.ctrlKey&&!l.shiftKey&&!l.altKey&&!l.metaKey&&!f&&p===L.origin&&Sa(b)&&(l.preventDefault(),b===L.pathname&&S===L.search?(E!==L.hash&&(history.pushState({},"",h),window.dispatchEvent(new HashChangeEvent("hashchange",{oldURL:L.href,newURL:h}))),E?Ks(a,E,a.classList.contains("header-anchor")):window.scrollTo(0,0)):s(h))}},{capture:!0}),window.addEventListener("popstate",async l=>{var c;l.state!==null&&(await i(Zn(location.href),l.state&&l.state.scrollPosition||0),(c=r.onAfterRouteChanged)==null||c.call(r,location.href))}),window.addEventListener("hashchange",l=>{l.preventDefault()})),r}function Na(){const e=bt(La);if(!e)throw new Error("useRouter() is called without provider.");return e}function ci(){return Na().route}function Ks(e,t,n=!1){let r=null;try{r=e.classList.contains("header-anchor")?e:document.getElementById(decodeURIComponent(t).slice(1))}catch(s){console.warn(s)}if(r){let s=function(){!n||Math.abs(i-window.scrollY)>window.innerHeight?window.scrollTo(0,i):window.scrollTo({left:0,top:i,behavior:"smooth"})};const o=parseInt(window.getComputedStyle(r).paddingTop,10),i=window.scrollY+r.getBoundingClientRect().top-Fa()+o;requestAnimationFrame(s)}}function Zn(e){const t=new URL(e,li);return t.pathname=t.pathname.replace(/(^|\/)index(\.html)?$/,"$1"),at.value.cleanUrls?t.pathname=t.pathname.replace(/\.html$/,""):!t.pathname.endsWith("/")&&!t.pathname.endsWith(".html")&&(t.pathname+=".html"),t.pathname+t.search+t.hash}const Gn=()=>hn.forEach(e=>e()),Ku=Hr({name:"VitePressContent",props:{as:{type:[Object,String],default:"div"}},setup(e){const t=ci(),{site:n}=Ra();return()=>gr(e.as,n.value.contentProps??{style:{position:"relative"}},[t.component?gr(t.component,{onVnodeMounted:Gn,onVnodeUpdated:Gn,onVnodeUnmounted:Gn}):"404 Page Not Found"])}}),Wu=Hr({setup(e,{slots:t}){const n=se(!1);return St(()=>{n.value=!0}),()=>n.value&&t.default?t.default():null}});function Vu(){de&&window.addEventListener("click",e=>{var n;const t=e.target;if(t.matches(".vp-code-group input")){const r=(n=t.parentElement)==null?void 0:n.parentElement;if(!r)return;const s=Array.from(r.querySelectorAll("input")).indexOf(t);if(s<0)return;const o=r.querySelector(".blocks");if(!o)return;const i=Array.from(o.children).find(a=>a.classList.contains("active"));if(!i)return;const l=o.children[s];if(!l||i===l)return;i.classList.remove("active"),l.classList.add("active");const c=r==null?void 0:r.querySelector(`label[for="${t.id}"]`);c==null||c.scrollIntoView({block:"nearest"})}})}function qu(){if(de){const e=new WeakMap;window.addEventListener("click",t=>{var r;const n=t.target;if(n.matches('div[class*="language-"] > button.copy')){const s=n.parentElement,o=(r=n.nextElementSibling)==null?void 0:r.nextElementSibling;if(!s||!o)return;const i=/language-(shellscript|shell|bash|sh|zsh)/.test(s.className),l=[".vp-copy-ignore",".diff.remove"],c=o.cloneNode(!0);c.querySelectorAll(l.join(",")).forEach(f=>f.remove());let a=c.textContent||"";i&&(a=a.replace(/^ *(\$|>) /gm,"").trim()),$a(a).then(()=>{n.classList.add("copied"),clearTimeout(e.get(n));const f=setTimeout(()=>{n.classList.remove("copied"),n.blur(),e.delete(n)},2e3);e.set(n,f)})}})}}async function $a(e){try{return navigator.clipboard.writeText(e)}catch{const t=document.createElement("textarea"),n=document.activeElement;t.value=e,t.setAttribute("readonly",""),t.style.contain="strict",t.style.position="absolute",t.style.left="-9999px",t.style.fontSize="12pt";const r=document.getSelection(),s=r?r.rangeCount>0&&r.getRangeAt(0):null;document.body.appendChild(t),t.select(),t.selectionStart=0,t.selectionEnd=e.length,document.execCommand("copy"),document.body.removeChild(t),s&&(r.removeAllRanges(),r.addRange(s)),n&&n.focus()}}function zu(e,t){let n=!0,r=[];const s=o=>{if(n){n=!1,o.forEach(l=>{const c=er(l);for(const a of document.head.children)if(a.isEqualNode(c)){r.push(a);return}});return}const i=o.map(er);r.forEach((l,c)=>{const a=i.findIndex(f=>f==null?void 0:f.isEqualNode(l??null));a!==-1?delete i[a]:(l==null||l.remove(),delete r[c])}),i.forEach(l=>l&&document.head.appendChild(l)),r=[...r,...i].filter(Boolean)};$r(()=>{const o=e.data,i=t.value,l=o&&o.description,c=o&&o.frontmatter.head||[],a=oi(i,o);a!==document.title&&(document.title=a);const f=l||i.description;let h=document.querySelector("meta[name=description]");h?h.getAttribute("content")!==f&&h.setAttribute("content",f):er(["meta",{name:"description",content:f}]),s(ii(i.head,ja(c)))})}function er([e,t,n]){const r=document.createElement(e);for(const s in t)r.setAttribute(s,t[s]);return n&&(r.innerHTML=n),e==="script"&&!t.async&&(r.async=!1),r}function Ha(e){return e[0]==="meta"&&e[1]&&e[1].name==="description"}function ja(e){return e.filter(t=>!Ha(t))}const tr=new Set,ai=()=>document.createElement("link"),Da=e=>{const t=ai();t.rel="prefetch",t.href=e,document.head.appendChild(t)},Ua=e=>{const t=new XMLHttpRequest;t.open("GET",e,t.withCredentials=!0),t.send()};let an;const Ba=de&&(an=ai())&&an.relList&&an.relList.supports&&an.relList.supports("prefetch")?Da:Ua;function Yu(){if(!de||!window.IntersectionObserver)return;let e;if((e=navigator.connection)&&(e.saveData||/2g/.test(e.effectiveType)))return;const t=window.requestIdleCallback||setTimeout;let n=null;const r=()=>{n&&n.disconnect(),n=new IntersectionObserver(o=>{o.forEach(i=>{if(i.isIntersecting){const l=i.target;n.unobserve(l);const{pathname:c}=l;if(!tr.has(c)){tr.add(c);const a=Pa(c);a&&Ba(a)}}})}),t(()=>{document.querySelectorAll("#app a").forEach(o=>{const{hostname:i,pathname:l}=new URL(o.href instanceof SVGAnimatedString?o.href.animVal:o.href,o.baseURI),c=l.match(/\.\w+$/);c&&c[0]!==".html"||o.target!=="_blank"&&i===location.hostname&&(l!==location.pathname?n.observe(o):tr.add(l))})})};St(r);const s=ci();Ne(()=>s.path,r),Nn(()=>{n&&n.disconnect()})}export{lu as $,Va as A,Ll as B,Fa as C,Ya as D,Ja as E,me as F,Mr as G,Bu as H,ie as I,Xa as J,ri as K,ci as L,ac as M,bt as N,ju as O,Cr as P,Lu as Q,Rn as R,Hu as S,Wo as T,de as U,On as V,za as W,Iu as X,Nu as Y,zl as Z,uu as _,Uo as a,Za as a0,iu as a1,Ga as a2,xt as a3,eu as a4,ru as a5,fu as a6,du as a7,hu as a8,pu as a9,qu as aA,Vu as aB,gr as aC,Zo as aD,Kr as aE,Fu as aF,$u as aG,Mu as aH,Pu as aI,Na as aJ,wo as aK,qa as aL,ou as aM,ue as aN,tu as aO,Lt as aP,cu as aQ,Du as aR,gu as aa,mu as ab,_u as ac,yu as ad,vu as ae,bu as af,wu as ag,Eu as ah,Cu as ai,xu as aj,Tu as ak,Au as al,Su as am,Ou as an,Ru as ao,zu as ap,La as aq,Uu as ar,Oa as as,Ku as at,Wu as au,at as av,au as aw,ku as ax,Pa as ay,Yu as az,Ho as b,nu as c,Hr as d,su as e,Sa as f,Bs as g,re as h,ba as i,Do as j,co as k,Wa as l,va as m,xr as n,No as o,Ka as p,Go as q,Qa as r,se as s,ka as t,Ra as u,Ne as v,yl as w,$r as x,St as y,Nn as z}; diff --git a/assets/chunks/theme.Lm1E6I-W.js b/assets/chunks/theme.Lm1E6I-W.js deleted file mode 100644 index 8ee35164..00000000 --- a/assets/chunks/theme.Lm1E6I-W.js +++ /dev/null @@ -1,2 +0,0 @@ -const __vite__fileDeps=["assets/chunks/VPLocalSearchBox.B3jfi5U8.js","assets/chunks/framework.CK8QU5WH.js"],__vite__mapDeps=i=>i.map(i=>__vite__fileDeps[i]); -import{d as _,o as a,c,r as l,n as N,a as E,t as S,b as g,w as v,e as f,T as ve,_ as b,u as Ke,i as Re,f as We,g as pe,h as y,j as d,k as r,p as C,l as B,m as z,q as ie,s as I,v as O,x,y as q,z as he,A as Ve,B as Ye,C as Je,D as K,F as M,E as F,G as Se,H as ee,I as m,J as W,K as we,L as Y,M as X,N as te,O as Xe,P as Te,Q as le,R as Ie,S as Ne,U as oe,V as Qe,W as Ze,X as xe,Y as Me,Z as Ae,$ as et,a0 as tt,a1 as ot,a2 as st,a3 as nt,a4 as ye}from"./framework.CK8QU5WH.js";const at=_({__name:"VPBadge",props:{text:{},type:{default:"tip"}},setup(o){return(e,t)=>(a(),c("span",{class:N(["VPBadge",e.type])},[l(e.$slots,"default",{},()=>[E(S(e.text),1)])],2))}}),rt={key:0,class:"VPBackdrop"},it=_({__name:"VPBackdrop",props:{show:{type:Boolean}},setup(o){return(e,t)=>(a(),g(ve,{name:"fade"},{default:v(()=>[e.show?(a(),c("div",rt)):f("",!0)]),_:1}))}}),lt=b(it,[["__scopeId","data-v-c79a1216"]]),P=Ke;function ct(o,e){let t,n=!1;return()=>{t&&clearTimeout(t),n?t=setTimeout(o,e):(o(),(n=!0)&&setTimeout(()=>n=!1,e))}}function ce(o){return/^\//.test(o)?o:`/${o}`}function fe(o){const{pathname:e,search:t,hash:n,protocol:s}=new URL(o,"http://a.com");if(Re(o)||o.startsWith("#")||!s.startsWith("http")||!We(e))return o;const{site:i}=P(),u=e.endsWith("/")||e.endsWith(".html")?o:o.replace(/(?:(^\.+)\/)?.*$/,`$1${e.replace(/(\.md)?$/,i.value.cleanUrls?"":".html")}${t}${n}`);return pe(u)}function J({correspondingLink:o=!1}={}){const{site:e,localeIndex:t,page:n,theme:s,hash:i}=P(),u=y(()=>{var p,$;return{label:(p=e.value.locales[t.value])==null?void 0:p.label,link:(($=e.value.locales[t.value])==null?void 0:$.link)||(t.value==="root"?"/":`/${t.value}/`)}});return{localeLinks:y(()=>Object.entries(e.value.locales).flatMap(([p,$])=>u.value.label===$.label?[]:{text:$.label,link:ut($.link||(p==="root"?"/":`/${p}/`),s.value.i18nRouting!==!1&&o,n.value.relativePath.slice(u.value.link.length-1),!e.value.cleanUrls)+i.value})),currentLang:u}}function ut(o,e,t,n){return e?o.replace(/\/$/,"")+ce(t.replace(/(^|\/)index\.md$/,"$1").replace(/\.md$/,n?".html":"")):o}const dt=o=>(C("data-v-d6be1790"),o=o(),B(),o),vt={class:"NotFound"},pt={class:"code"},ht={class:"title"},ft=dt(()=>d("div",{class:"divider"},null,-1)),_t={class:"quote"},mt={class:"action"},kt=["href","aria-label"],bt=_({__name:"NotFound",setup(o){const{theme:e}=P(),{currentLang:t}=J();return(n,s)=>{var i,u,h,p,$;return a(),c("div",vt,[d("p",pt,S(((i=r(e).notFound)==null?void 0:i.code)??"404"),1),d("h1",ht,S(((u=r(e).notFound)==null?void 0:u.title)??"PAGE NOT FOUND"),1),ft,d("blockquote",_t,S(((h=r(e).notFound)==null?void 0:h.quote)??"But if you don't change your direction, and if you keep looking, you may end up where you are heading."),1),d("div",mt,[d("a",{class:"link",href:r(pe)(r(t).link),"aria-label":((p=r(e).notFound)==null?void 0:p.linkLabel)??"go to home"},S((($=r(e).notFound)==null?void 0:$.linkText)??"Take me home"),9,kt)])])}}}),gt=b(bt,[["__scopeId","data-v-d6be1790"]]);function He(o,e){if(Array.isArray(o))return Q(o);if(o==null)return[];e=ce(e);const t=Object.keys(o).sort((s,i)=>i.split("/").length-s.split("/").length).find(s=>e.startsWith(ce(s))),n=t?o[t]:[];return Array.isArray(n)?Q(n):Q(n.items,n.base)}function $t(o){const e=[];let t=0;for(const n in o){const s=o[n];if(s.items){t=e.push(s);continue}e[t]||e.push({items:[]}),e[t].items.push(s)}return e}function yt(o){const e=[];function t(n){for(const s of n)s.text&&s.link&&e.push({text:s.text,link:s.link,docFooterText:s.docFooterText}),s.items&&t(s.items)}return t(o),e}function ue(o,e){return Array.isArray(e)?e.some(t=>ue(o,t)):z(o,e.link)?!0:e.items?ue(o,e.items):!1}function Q(o,e){return[...o].map(t=>{const n={...t},s=n.base||e;return s&&n.link&&(n.link=s+n.link),n.items&&(n.items=Q(n.items,s)),n})}function U(){const{frontmatter:o,page:e,theme:t}=P(),n=ie("(min-width: 960px)"),s=I(!1),i=y(()=>{const H=t.value.sidebar,w=e.value.relativePath;return H?He(H,w):[]}),u=I(i.value);O(i,(H,w)=>{JSON.stringify(H)!==JSON.stringify(w)&&(u.value=i.value)});const h=y(()=>o.value.sidebar!==!1&&u.value.length>0&&o.value.layout!=="home"),p=y(()=>$?o.value.aside==null?t.value.aside==="left":o.value.aside==="left":!1),$=y(()=>o.value.layout==="home"?!1:o.value.aside!=null?!!o.value.aside:t.value.aside!==!1),L=y(()=>h.value&&n.value),k=y(()=>h.value?$t(u.value):[]);function V(){s.value=!0}function T(){s.value=!1}function A(){s.value?T():V()}return{isOpen:s,sidebar:u,sidebarGroups:k,hasSidebar:h,hasAside:$,leftAside:p,isSidebarEnabled:L,open:V,close:T,toggle:A}}function Pt(o,e){let t;x(()=>{t=o.value?document.activeElement:void 0}),q(()=>{window.addEventListener("keyup",n)}),he(()=>{window.removeEventListener("keyup",n)});function n(s){s.key==="Escape"&&o.value&&(e(),t==null||t.focus())}}function Lt(o){const{page:e,hash:t}=P(),n=I(!1),s=y(()=>o.value.collapsed!=null),i=y(()=>!!o.value.link),u=I(!1),h=()=>{u.value=z(e.value.relativePath,o.value.link)};O([e,o,t],h),q(h);const p=y(()=>u.value?!0:o.value.items?ue(e.value.relativePath,o.value.items):!1),$=y(()=>!!(o.value.items&&o.value.items.length));x(()=>{n.value=!!(s.value&&o.value.collapsed)}),Ve(()=>{(u.value||p.value)&&(n.value=!1)});function L(){s.value&&(n.value=!n.value)}return{collapsed:n,collapsible:s,isLink:i,isActiveLink:u,hasActiveLink:p,hasChildren:$,toggle:L}}function Vt(){const{hasSidebar:o}=U(),e=ie("(min-width: 960px)"),t=ie("(min-width: 1280px)");return{isAsideEnabled:y(()=>!t.value&&!e.value?!1:o.value?t.value:e.value)}}const de=[];function Ce(o){return typeof o.outline=="object"&&!Array.isArray(o.outline)&&o.outline.label||o.outlineTitle||"On this page"}function _e(o){const e=[...document.querySelectorAll(".VPDoc :where(h1,h2,h3,h4,h5,h6)")].filter(t=>t.id&&t.hasChildNodes()).map(t=>{const n=Number(t.tagName[1]);return{element:t,title:St(t),link:"#"+t.id,level:n}});return wt(e,o)}function St(o){let e="";for(const t of o.childNodes)if(t.nodeType===1){if(t.classList.contains("VPBadge")||t.classList.contains("header-anchor")||t.classList.contains("ignore-header"))continue;e+=t.textContent}else t.nodeType===3&&(e+=t.textContent);return e.trim()}function wt(o,e){if(e===!1)return[];const t=(typeof e=="object"&&!Array.isArray(e)?e.level:e)||2,[n,s]=typeof t=="number"?[t,t]:t==="deep"?[2,6]:t;o=o.filter(u=>u.level>=n&&u.level<=s),de.length=0;for(const{element:u,link:h}of o)de.push({element:u,link:h});const i=[];e:for(let u=0;u=0;p--){const $=o[p];if($.level{requestAnimationFrame(i),window.addEventListener("scroll",n)}),Ye(()=>{u(location.hash)}),he(()=>{window.removeEventListener("scroll",n)});function i(){if(!t.value)return;const h=window.scrollY,p=window.innerHeight,$=document.body.offsetHeight,L=Math.abs(h+p-$)<1,k=de.map(({element:T,link:A})=>({link:A,top:It(T)})).filter(({top:T})=>!Number.isNaN(T)).sort((T,A)=>T.top-A.top);if(!k.length){u(null);return}if(h<1){u(null);return}if(L){u(k[k.length-1].link);return}let V=null;for(const{link:T,top:A}of k){if(A>h+Je()+4)break;V=T}u(V)}function u(h){s&&s.classList.remove("active"),h==null?s=null:s=o.value.querySelector(`a[href="${decodeURIComponent(h)}"]`);const p=s;p?(p.classList.add("active"),e.value.style.top=p.offsetTop+39+"px",e.value.style.opacity="1"):(e.value.style.top="33px",e.value.style.opacity="0")}}function It(o){let e=0;for(;o!==document.body;){if(o===null)return NaN;e+=o.offsetTop,o=o.offsetParent}return e}const Nt=["href","title"],Mt=_({__name:"VPDocOutlineItem",props:{headers:{},root:{type:Boolean}},setup(o){function e({target:t}){const n=t.href.split("#")[1],s=document.getElementById(decodeURIComponent(n));s==null||s.focus({preventScroll:!0})}return(t,n)=>{const s=K("VPDocOutlineItem",!0);return a(),c("ul",{class:N(["VPDocOutlineItem",t.root?"root":"nested"])},[(a(!0),c(M,null,F(t.headers,({children:i,link:u,title:h})=>(a(),c("li",null,[d("a",{class:"outline-link",href:u,onClick:e,title:h},S(h),9,Nt),i!=null&&i.length?(a(),g(s,{key:0,headers:i},null,8,["headers"])):f("",!0)]))),256))],2)}}}),Be=b(Mt,[["__scopeId","data-v-b933a997"]]),At={class:"content"},Ht={"aria-level":"2",class:"outline-title",id:"doc-outline-aria-label",role:"heading"},Ct=_({__name:"VPDocAsideOutline",setup(o){const{frontmatter:e,theme:t}=P(),n=Se([]);ee(()=>{n.value=_e(e.value.outline??t.value.outline)});const s=I(),i=I();return Tt(s,i),(u,h)=>(a(),c("nav",{"aria-labelledby":"doc-outline-aria-label",class:N(["VPDocAsideOutline",{"has-outline":n.value.length>0}]),ref_key:"container",ref:s},[d("div",At,[d("div",{class:"outline-marker",ref_key:"marker",ref:i},null,512),d("div",Ht,S(r(Ce)(r(t))),1),m(Be,{headers:n.value,root:!0},null,8,["headers"])])],2))}}),Bt=b(Ct,[["__scopeId","data-v-a5bbad30"]]),Et={class:"VPDocAsideCarbonAds"},Ft=_({__name:"VPDocAsideCarbonAds",props:{carbonAds:{}},setup(o){const e=()=>null;return(t,n)=>(a(),c("div",Et,[m(r(e),{"carbon-ads":t.carbonAds},null,8,["carbon-ads"])]))}}),Dt=o=>(C("data-v-3f215769"),o=o(),B(),o),Ot={class:"VPDocAside"},Ut=Dt(()=>d("div",{class:"spacer"},null,-1)),Gt=_({__name:"VPDocAside",setup(o){const{theme:e}=P();return(t,n)=>(a(),c("div",Ot,[l(t.$slots,"aside-top",{},void 0,!0),l(t.$slots,"aside-outline-before",{},void 0,!0),m(Bt),l(t.$slots,"aside-outline-after",{},void 0,!0),Ut,l(t.$slots,"aside-ads-before",{},void 0,!0),r(e).carbonAds?(a(),g(Ft,{key:0,"carbon-ads":r(e).carbonAds},null,8,["carbon-ads"])):f("",!0),l(t.$slots,"aside-ads-after",{},void 0,!0),l(t.$slots,"aside-bottom",{},void 0,!0)]))}}),jt=b(Gt,[["__scopeId","data-v-3f215769"]]);function zt(){const{theme:o,page:e}=P();return y(()=>{const{text:t="Edit this page",pattern:n=""}=o.value.editLink||{};let s;return typeof n=="function"?s=n(e.value):s=n.replace(/:path/g,e.value.filePath),{url:s,text:t}})}function qt(){const{page:o,theme:e,frontmatter:t}=P();return y(()=>{var $,L,k,V,T,A,H,w;const n=He(e.value.sidebar,o.value.relativePath),s=yt(n),i=Kt(s,G=>G.link.replace(/[?#].*$/,"")),u=i.findIndex(G=>z(o.value.relativePath,G.link)),h=(($=e.value.docFooter)==null?void 0:$.prev)===!1&&!t.value.prev||t.value.prev===!1,p=((L=e.value.docFooter)==null?void 0:L.next)===!1&&!t.value.next||t.value.next===!1;return{prev:h?void 0:{text:(typeof t.value.prev=="string"?t.value.prev:typeof t.value.prev=="object"?t.value.prev.text:void 0)??((k=i[u-1])==null?void 0:k.docFooterText)??((V=i[u-1])==null?void 0:V.text),link:(typeof t.value.prev=="object"?t.value.prev.link:void 0)??((T=i[u-1])==null?void 0:T.link)},next:p?void 0:{text:(typeof t.value.next=="string"?t.value.next:typeof t.value.next=="object"?t.value.next.text:void 0)??((A=i[u+1])==null?void 0:A.docFooterText)??((H=i[u+1])==null?void 0:H.text),link:(typeof t.value.next=="object"?t.value.next.link:void 0)??((w=i[u+1])==null?void 0:w.link)}}})}function Kt(o,e){const t=new Set;return o.filter(n=>{const s=e(n);return t.has(s)?!1:t.add(s)})}const D=_({__name:"VPLink",props:{tag:{},href:{},noIcon:{type:Boolean},target:{},rel:{}},setup(o){const e=o,t=y(()=>e.tag??(e.href?"a":"span")),n=y(()=>e.href&&we.test(e.href)||e.target==="_blank");return(s,i)=>(a(),g(W(t.value),{class:N(["VPLink",{link:s.href,"vp-external-link-icon":n.value,"no-icon":s.noIcon}]),href:s.href?r(fe)(s.href):void 0,target:s.target??(n.value?"_blank":void 0),rel:s.rel??(n.value?"noreferrer":void 0)},{default:v(()=>[l(s.$slots,"default")]),_:3},8,["class","href","target","rel"]))}}),Rt={class:"VPLastUpdated"},Wt=["datetime"],Yt=_({__name:"VPDocFooterLastUpdated",setup(o){const{theme:e,page:t,frontmatter:n,lang:s}=P(),i=y(()=>new Date(n.value.lastUpdated??t.value.lastUpdated)),u=y(()=>i.value.toISOString()),h=I("");return q(()=>{x(()=>{var p,$,L;h.value=new Intl.DateTimeFormat(($=(p=e.value.lastUpdated)==null?void 0:p.formatOptions)!=null&&$.forceLocale?s.value:void 0,((L=e.value.lastUpdated)==null?void 0:L.formatOptions)??{dateStyle:"short",timeStyle:"short"}).format(i.value)})}),(p,$)=>{var L;return a(),c("p",Rt,[E(S(((L=r(e).lastUpdated)==null?void 0:L.text)||r(e).lastUpdatedText||"Last updated")+": ",1),d("time",{datetime:u.value},S(h.value),9,Wt)])}}}),Jt=b(Yt,[["__scopeId","data-v-7e05ebdb"]]),Ee=o=>(C("data-v-d4a0bba5"),o=o(),B(),o),Xt={key:0,class:"VPDocFooter"},Qt={key:0,class:"edit-info"},Zt={key:0,class:"edit-link"},xt=Ee(()=>d("span",{class:"vpi-square-pen edit-link-icon"},null,-1)),eo={key:1,class:"last-updated"},to={key:1,class:"prev-next","aria-labelledby":"doc-footer-aria-label"},oo=Ee(()=>d("span",{class:"visually-hidden",id:"doc-footer-aria-label"},"Pager",-1)),so={class:"pager"},no=["innerHTML"],ao=["innerHTML"],ro={class:"pager"},io=["innerHTML"],lo=["innerHTML"],co=_({__name:"VPDocFooter",setup(o){const{theme:e,page:t,frontmatter:n}=P(),s=zt(),i=qt(),u=y(()=>e.value.editLink&&n.value.editLink!==!1),h=y(()=>t.value.lastUpdated&&n.value.lastUpdated!==!1),p=y(()=>u.value||h.value||i.value.prev||i.value.next);return($,L)=>{var k,V,T,A;return p.value?(a(),c("footer",Xt,[l($.$slots,"doc-footer-before",{},void 0,!0),u.value||h.value?(a(),c("div",Qt,[u.value?(a(),c("div",Zt,[m(D,{class:"edit-link-button",href:r(s).url,"no-icon":!0},{default:v(()=>[xt,E(" "+S(r(s).text),1)]),_:1},8,["href"])])):f("",!0),h.value?(a(),c("div",eo,[m(Jt)])):f("",!0)])):f("",!0),(k=r(i).prev)!=null&&k.link||(V=r(i).next)!=null&&V.link?(a(),c("nav",to,[oo,d("div",so,[(T=r(i).prev)!=null&&T.link?(a(),g(D,{key:0,class:"pager-link prev",href:r(i).prev.link},{default:v(()=>{var H;return[d("span",{class:"desc",innerHTML:((H=r(e).docFooter)==null?void 0:H.prev)||"Previous page"},null,8,no),d("span",{class:"title",innerHTML:r(i).prev.text},null,8,ao)]}),_:1},8,["href"])):f("",!0)]),d("div",ro,[(A=r(i).next)!=null&&A.link?(a(),g(D,{key:0,class:"pager-link next",href:r(i).next.link},{default:v(()=>{var H;return[d("span",{class:"desc",innerHTML:((H=r(e).docFooter)==null?void 0:H.next)||"Next page"},null,8,io),d("span",{class:"title",innerHTML:r(i).next.text},null,8,lo)]}),_:1},8,["href"])):f("",!0)])])):f("",!0)])):f("",!0)}}}),uo=b(co,[["__scopeId","data-v-d4a0bba5"]]),vo=o=>(C("data-v-39a288b8"),o=o(),B(),o),po={class:"container"},ho=vo(()=>d("div",{class:"aside-curtain"},null,-1)),fo={class:"aside-container"},_o={class:"aside-content"},mo={class:"content"},ko={class:"content-container"},bo={class:"main"},go=_({__name:"VPDoc",setup(o){const{theme:e}=P(),t=Y(),{hasSidebar:n,hasAside:s,leftAside:i}=U(),u=y(()=>t.path.replace(/[./]+/g,"_").replace(/_html$/,""));return(h,p)=>{const $=K("Content");return a(),c("div",{class:N(["VPDoc",{"has-sidebar":r(n),"has-aside":r(s)}])},[l(h.$slots,"doc-top",{},void 0,!0),d("div",po,[r(s)?(a(),c("div",{key:0,class:N(["aside",{"left-aside":r(i)}])},[ho,d("div",fo,[d("div",_o,[m(jt,null,{"aside-top":v(()=>[l(h.$slots,"aside-top",{},void 0,!0)]),"aside-bottom":v(()=>[l(h.$slots,"aside-bottom",{},void 0,!0)]),"aside-outline-before":v(()=>[l(h.$slots,"aside-outline-before",{},void 0,!0)]),"aside-outline-after":v(()=>[l(h.$slots,"aside-outline-after",{},void 0,!0)]),"aside-ads-before":v(()=>[l(h.$slots,"aside-ads-before",{},void 0,!0)]),"aside-ads-after":v(()=>[l(h.$slots,"aside-ads-after",{},void 0,!0)]),_:3})])])],2)):f("",!0),d("div",mo,[d("div",ko,[l(h.$slots,"doc-before",{},void 0,!0),d("main",bo,[m($,{class:N(["vp-doc",[u.value,r(e).externalLinkIcon&&"external-link-icon-enabled"]])},null,8,["class"])]),m(uo,null,{"doc-footer-before":v(()=>[l(h.$slots,"doc-footer-before",{},void 0,!0)]),_:3}),l(h.$slots,"doc-after",{},void 0,!0)])])]),l(h.$slots,"doc-bottom",{},void 0,!0)],2)}}}),$o=b(go,[["__scopeId","data-v-39a288b8"]]),yo=_({__name:"VPButton",props:{tag:{},size:{default:"medium"},theme:{default:"brand"},text:{},href:{},target:{},rel:{}},setup(o){const e=o,t=y(()=>e.href&&we.test(e.href)),n=y(()=>e.tag||e.href?"a":"button");return(s,i)=>(a(),g(W(n.value),{class:N(["VPButton",[s.size,s.theme]]),href:s.href?r(fe)(s.href):void 0,target:e.target??(t.value?"_blank":void 0),rel:e.rel??(t.value?"noreferrer":void 0)},{default:v(()=>[E(S(s.text),1)]),_:1},8,["class","href","target","rel"]))}}),Po=b(yo,[["__scopeId","data-v-cad61b99"]]),Lo=["src","alt"],Vo=_({inheritAttrs:!1,__name:"VPImage",props:{image:{},alt:{}},setup(o){return(e,t)=>{const n=K("VPImage",!0);return e.image?(a(),c(M,{key:0},[typeof e.image=="string"||"src"in e.image?(a(),c("img",X({key:0,class:"VPImage"},typeof e.image=="string"?e.$attrs:{...e.image,...e.$attrs},{src:r(pe)(typeof e.image=="string"?e.image:e.image.src),alt:e.alt??(typeof e.image=="string"?"":e.image.alt||"")}),null,16,Lo)):(a(),c(M,{key:1},[m(n,X({class:"dark",image:e.image.dark,alt:e.image.alt},e.$attrs),null,16,["image","alt"]),m(n,X({class:"light",image:e.image.light,alt:e.image.alt},e.$attrs),null,16,["image","alt"])],64))],64)):f("",!0)}}}),Z=b(Vo,[["__scopeId","data-v-8426fc1a"]]),So=o=>(C("data-v-303bb580"),o=o(),B(),o),wo={class:"container"},To={class:"main"},Io={key:0,class:"name"},No=["innerHTML"],Mo=["innerHTML"],Ao=["innerHTML"],Ho={key:0,class:"actions"},Co={key:0,class:"image"},Bo={class:"image-container"},Eo=So(()=>d("div",{class:"image-bg"},null,-1)),Fo=_({__name:"VPHero",props:{name:{},text:{},tagline:{},image:{},actions:{}},setup(o){const e=te("hero-image-slot-exists");return(t,n)=>(a(),c("div",{class:N(["VPHero",{"has-image":t.image||r(e)}])},[d("div",wo,[d("div",To,[l(t.$slots,"home-hero-info-before",{},void 0,!0),l(t.$slots,"home-hero-info",{},()=>[t.name?(a(),c("h1",Io,[d("span",{innerHTML:t.name,class:"clip"},null,8,No)])):f("",!0),t.text?(a(),c("p",{key:1,innerHTML:t.text,class:"text"},null,8,Mo)):f("",!0),t.tagline?(a(),c("p",{key:2,innerHTML:t.tagline,class:"tagline"},null,8,Ao)):f("",!0)],!0),l(t.$slots,"home-hero-info-after",{},void 0,!0),t.actions?(a(),c("div",Ho,[(a(!0),c(M,null,F(t.actions,s=>(a(),c("div",{key:s.link,class:"action"},[m(Po,{tag:"a",size:"medium",theme:s.theme,text:s.text,href:s.link,target:s.target,rel:s.rel},null,8,["theme","text","href","target","rel"])]))),128))])):f("",!0),l(t.$slots,"home-hero-actions-after",{},void 0,!0)]),t.image||r(e)?(a(),c("div",Co,[d("div",Bo,[Eo,l(t.$slots,"home-hero-image",{},()=>[t.image?(a(),g(Z,{key:0,class:"image-src",image:t.image},null,8,["image"])):f("",!0)],!0)])])):f("",!0)])],2))}}),Do=b(Fo,[["__scopeId","data-v-303bb580"]]),Oo=_({__name:"VPHomeHero",setup(o){const{frontmatter:e}=P();return(t,n)=>r(e).hero?(a(),g(Do,{key:0,class:"VPHomeHero",name:r(e).hero.name,text:r(e).hero.text,tagline:r(e).hero.tagline,image:r(e).hero.image,actions:r(e).hero.actions},{"home-hero-info-before":v(()=>[l(t.$slots,"home-hero-info-before")]),"home-hero-info":v(()=>[l(t.$slots,"home-hero-info")]),"home-hero-info-after":v(()=>[l(t.$slots,"home-hero-info-after")]),"home-hero-actions-after":v(()=>[l(t.$slots,"home-hero-actions-after")]),"home-hero-image":v(()=>[l(t.$slots,"home-hero-image")]),_:3},8,["name","text","tagline","image","actions"])):f("",!0)}}),Uo=o=>(C("data-v-a3976bdc"),o=o(),B(),o),Go={class:"box"},jo={key:0,class:"icon"},zo=["innerHTML"],qo=["innerHTML"],Ko=["innerHTML"],Ro={key:4,class:"link-text"},Wo={class:"link-text-value"},Yo=Uo(()=>d("span",{class:"vpi-arrow-right link-text-icon"},null,-1)),Jo=_({__name:"VPFeature",props:{icon:{},title:{},details:{},link:{},linkText:{},rel:{},target:{}},setup(o){return(e,t)=>(a(),g(D,{class:"VPFeature",href:e.link,rel:e.rel,target:e.target,"no-icon":!0,tag:e.link?"a":"div"},{default:v(()=>[d("article",Go,[typeof e.icon=="object"&&e.icon.wrap?(a(),c("div",jo,[m(Z,{image:e.icon,alt:e.icon.alt,height:e.icon.height||48,width:e.icon.width||48},null,8,["image","alt","height","width"])])):typeof e.icon=="object"?(a(),g(Z,{key:1,image:e.icon,alt:e.icon.alt,height:e.icon.height||48,width:e.icon.width||48},null,8,["image","alt","height","width"])):e.icon?(a(),c("div",{key:2,class:"icon",innerHTML:e.icon},null,8,zo)):f("",!0),d("h2",{class:"title",innerHTML:e.title},null,8,qo),e.details?(a(),c("p",{key:3,class:"details",innerHTML:e.details},null,8,Ko)):f("",!0),e.linkText?(a(),c("div",Ro,[d("p",Wo,[E(S(e.linkText)+" ",1),Yo])])):f("",!0)])]),_:1},8,["href","rel","target","tag"]))}}),Xo=b(Jo,[["__scopeId","data-v-a3976bdc"]]),Qo={key:0,class:"VPFeatures"},Zo={class:"container"},xo={class:"items"},es=_({__name:"VPFeatures",props:{features:{}},setup(o){const e=o,t=y(()=>{const n=e.features.length;if(n){if(n===2)return"grid-2";if(n===3)return"grid-3";if(n%3===0)return"grid-6";if(n>3)return"grid-4"}else return});return(n,s)=>n.features?(a(),c("div",Qo,[d("div",Zo,[d("div",xo,[(a(!0),c(M,null,F(n.features,i=>(a(),c("div",{key:i.title,class:N(["item",[t.value]])},[m(Xo,{icon:i.icon,title:i.title,details:i.details,link:i.link,"link-text":i.linkText,rel:i.rel,target:i.target},null,8,["icon","title","details","link","link-text","rel","target"])],2))),128))])])])):f("",!0)}}),ts=b(es,[["__scopeId","data-v-a6181336"]]),os=_({__name:"VPHomeFeatures",setup(o){const{frontmatter:e}=P();return(t,n)=>r(e).features?(a(),g(ts,{key:0,class:"VPHomeFeatures",features:r(e).features},null,8,["features"])):f("",!0)}}),ss=_({__name:"VPHomeContent",setup(o){const{width:e}=Xe({initialWidth:0,includeScrollbar:!1});return(t,n)=>(a(),c("div",{class:"vp-doc container",style:Te(r(e)?{"--vp-offset":`calc(50% - ${r(e)/2}px)`}:{})},[l(t.$slots,"default",{},void 0,!0)],4))}}),ns=b(ss,[["__scopeId","data-v-8e2d4988"]]),as={class:"VPHome"},rs=_({__name:"VPHome",setup(o){const{frontmatter:e}=P();return(t,n)=>{const s=K("Content");return a(),c("div",as,[l(t.$slots,"home-hero-before",{},void 0,!0),m(Oo,null,{"home-hero-info-before":v(()=>[l(t.$slots,"home-hero-info-before",{},void 0,!0)]),"home-hero-info":v(()=>[l(t.$slots,"home-hero-info",{},void 0,!0)]),"home-hero-info-after":v(()=>[l(t.$slots,"home-hero-info-after",{},void 0,!0)]),"home-hero-actions-after":v(()=>[l(t.$slots,"home-hero-actions-after",{},void 0,!0)]),"home-hero-image":v(()=>[l(t.$slots,"home-hero-image",{},void 0,!0)]),_:3}),l(t.$slots,"home-hero-after",{},void 0,!0),l(t.$slots,"home-features-before",{},void 0,!0),m(os),l(t.$slots,"home-features-after",{},void 0,!0),r(e).markdownStyles!==!1?(a(),g(ns,{key:0},{default:v(()=>[m(s)]),_:1})):(a(),g(s,{key:1}))])}}}),is=b(rs,[["__scopeId","data-v-686f80a6"]]),ls={},cs={class:"VPPage"};function us(o,e){const t=K("Content");return a(),c("div",cs,[l(o.$slots,"page-top"),m(t),l(o.$slots,"page-bottom")])}const ds=b(ls,[["render",us]]),vs=_({__name:"VPContent",setup(o){const{page:e,frontmatter:t}=P(),{hasSidebar:n}=U();return(s,i)=>(a(),c("div",{class:N(["VPContent",{"has-sidebar":r(n),"is-home":r(t).layout==="home"}]),id:"VPContent"},[r(e).isNotFound?l(s.$slots,"not-found",{key:0},()=>[m(gt)],!0):r(t).layout==="page"?(a(),g(ds,{key:1},{"page-top":v(()=>[l(s.$slots,"page-top",{},void 0,!0)]),"page-bottom":v(()=>[l(s.$slots,"page-bottom",{},void 0,!0)]),_:3})):r(t).layout==="home"?(a(),g(is,{key:2},{"home-hero-before":v(()=>[l(s.$slots,"home-hero-before",{},void 0,!0)]),"home-hero-info-before":v(()=>[l(s.$slots,"home-hero-info-before",{},void 0,!0)]),"home-hero-info":v(()=>[l(s.$slots,"home-hero-info",{},void 0,!0)]),"home-hero-info-after":v(()=>[l(s.$slots,"home-hero-info-after",{},void 0,!0)]),"home-hero-actions-after":v(()=>[l(s.$slots,"home-hero-actions-after",{},void 0,!0)]),"home-hero-image":v(()=>[l(s.$slots,"home-hero-image",{},void 0,!0)]),"home-hero-after":v(()=>[l(s.$slots,"home-hero-after",{},void 0,!0)]),"home-features-before":v(()=>[l(s.$slots,"home-features-before",{},void 0,!0)]),"home-features-after":v(()=>[l(s.$slots,"home-features-after",{},void 0,!0)]),_:3})):r(t).layout&&r(t).layout!=="doc"?(a(),g(W(r(t).layout),{key:3})):(a(),g($o,{key:4},{"doc-top":v(()=>[l(s.$slots,"doc-top",{},void 0,!0)]),"doc-bottom":v(()=>[l(s.$slots,"doc-bottom",{},void 0,!0)]),"doc-footer-before":v(()=>[l(s.$slots,"doc-footer-before",{},void 0,!0)]),"doc-before":v(()=>[l(s.$slots,"doc-before",{},void 0,!0)]),"doc-after":v(()=>[l(s.$slots,"doc-after",{},void 0,!0)]),"aside-top":v(()=>[l(s.$slots,"aside-top",{},void 0,!0)]),"aside-outline-before":v(()=>[l(s.$slots,"aside-outline-before",{},void 0,!0)]),"aside-outline-after":v(()=>[l(s.$slots,"aside-outline-after",{},void 0,!0)]),"aside-ads-before":v(()=>[l(s.$slots,"aside-ads-before",{},void 0,!0)]),"aside-ads-after":v(()=>[l(s.$slots,"aside-ads-after",{},void 0,!0)]),"aside-bottom":v(()=>[l(s.$slots,"aside-bottom",{},void 0,!0)]),_:3}))],2))}}),ps=b(vs,[["__scopeId","data-v-1428d186"]]),hs={class:"container"},fs=["innerHTML"],_s=["innerHTML"],ms=_({__name:"VPFooter",setup(o){const{theme:e,frontmatter:t}=P(),{hasSidebar:n}=U();return(s,i)=>r(e).footer&&r(t).footer!==!1?(a(),c("footer",{key:0,class:N(["VPFooter",{"has-sidebar":r(n)}])},[d("div",hs,[r(e).footer.message?(a(),c("p",{key:0,class:"message",innerHTML:r(e).footer.message},null,8,fs)):f("",!0),r(e).footer.copyright?(a(),c("p",{key:1,class:"copyright",innerHTML:r(e).footer.copyright},null,8,_s)):f("",!0)])],2)):f("",!0)}}),ks=b(ms,[["__scopeId","data-v-e315a0ad"]]);function bs(){const{theme:o,frontmatter:e}=P(),t=Se([]),n=y(()=>t.value.length>0);return ee(()=>{t.value=_e(e.value.outline??o.value.outline)}),{headers:t,hasLocalNav:n}}const gs=o=>(C("data-v-17a5e62e"),o=o(),B(),o),$s={class:"menu-text"},ys=gs(()=>d("span",{class:"vpi-chevron-right icon"},null,-1)),Ps={class:"header"},Ls={class:"outline"},Vs=_({__name:"VPLocalNavOutlineDropdown",props:{headers:{},navHeight:{}},setup(o){const e=o,{theme:t}=P(),n=I(!1),s=I(0),i=I(),u=I();function h(k){var V;(V=i.value)!=null&&V.contains(k.target)||(n.value=!1)}O(n,k=>{if(k){document.addEventListener("click",h);return}document.removeEventListener("click",h)}),le("Escape",()=>{n.value=!1}),ee(()=>{n.value=!1});function p(){n.value=!n.value,s.value=window.innerHeight+Math.min(window.scrollY-e.navHeight,0)}function $(k){k.target.classList.contains("outline-link")&&(u.value&&(u.value.style.transition="none"),Ie(()=>{n.value=!1}))}function L(){n.value=!1,window.scrollTo({top:0,left:0,behavior:"smooth"})}return(k,V)=>(a(),c("div",{class:"VPLocalNavOutlineDropdown",style:Te({"--vp-vh":s.value+"px"}),ref_key:"main",ref:i},[k.headers.length>0?(a(),c("button",{key:0,onClick:p,class:N({open:n.value})},[d("span",$s,S(r(Ce)(r(t))),1),ys],2)):(a(),c("button",{key:1,onClick:L},S(r(t).returnToTopLabel||"Return to top"),1)),m(ve,{name:"flyout"},{default:v(()=>[n.value?(a(),c("div",{key:0,ref_key:"items",ref:u,class:"items",onClick:$},[d("div",Ps,[d("a",{class:"top-link",href:"#",onClick:L},S(r(t).returnToTopLabel||"Return to top"),1)]),d("div",Ls,[m(Be,{headers:k.headers},null,8,["headers"])])],512)):f("",!0)]),_:1})],4))}}),Ss=b(Vs,[["__scopeId","data-v-17a5e62e"]]),ws=o=>(C("data-v-a6f0e41e"),o=o(),B(),o),Ts={class:"container"},Is=["aria-expanded"],Ns=ws(()=>d("span",{class:"vpi-align-left menu-icon"},null,-1)),Ms={class:"menu-text"},As=_({__name:"VPLocalNav",props:{open:{type:Boolean}},emits:["open-menu"],setup(o){const{theme:e,frontmatter:t}=P(),{hasSidebar:n}=U(),{headers:s}=bs(),{y:i}=Ne(),u=I(0);q(()=>{u.value=parseInt(getComputedStyle(document.documentElement).getPropertyValue("--vp-nav-height"))}),ee(()=>{s.value=_e(t.value.outline??e.value.outline)});const h=y(()=>s.value.length===0),p=y(()=>h.value&&!n.value),$=y(()=>({VPLocalNav:!0,"has-sidebar":n.value,empty:h.value,fixed:p.value}));return(L,k)=>r(t).layout!=="home"&&(!p.value||r(i)>=u.value)?(a(),c("div",{key:0,class:N($.value)},[d("div",Ts,[r(n)?(a(),c("button",{key:0,class:"menu","aria-expanded":L.open,"aria-controls":"VPSidebarNav",onClick:k[0]||(k[0]=V=>L.$emit("open-menu"))},[Ns,d("span",Ms,S(r(e).sidebarMenuLabel||"Menu"),1)],8,Is)):f("",!0),m(Ss,{headers:r(s),navHeight:u.value},null,8,["headers","navHeight"])])],2)):f("",!0)}}),Hs=b(As,[["__scopeId","data-v-a6f0e41e"]]);function Cs(){const o=I(!1);function e(){o.value=!0,window.addEventListener("resize",s)}function t(){o.value=!1,window.removeEventListener("resize",s)}function n(){o.value?t():e()}function s(){window.outerWidth>=768&&t()}const i=Y();return O(()=>i.path,t),{isScreenOpen:o,openScreen:e,closeScreen:t,toggleScreen:n}}const Bs={},Es={class:"VPSwitch",type:"button",role:"switch"},Fs={class:"check"},Ds={key:0,class:"icon"};function Os(o,e){return a(),c("button",Es,[d("span",Fs,[o.$slots.default?(a(),c("span",Ds,[l(o.$slots,"default",{},void 0,!0)])):f("",!0)])])}const Us=b(Bs,[["render",Os],["__scopeId","data-v-1d5665e3"]]),Fe=o=>(C("data-v-d1f28634"),o=o(),B(),o),Gs=Fe(()=>d("span",{class:"vpi-sun sun"},null,-1)),js=Fe(()=>d("span",{class:"vpi-moon moon"},null,-1)),zs=_({__name:"VPSwitchAppearance",setup(o){const{isDark:e,theme:t}=P(),n=te("toggle-appearance",()=>{e.value=!e.value}),s=y(()=>e.value?t.value.lightModeSwitchTitle||"Switch to light theme":t.value.darkModeSwitchTitle||"Switch to dark theme");return(i,u)=>(a(),g(Us,{title:s.value,class:"VPSwitchAppearance","aria-checked":r(e),onClick:r(n)},{default:v(()=>[Gs,js]),_:1},8,["title","aria-checked","onClick"]))}}),me=b(zs,[["__scopeId","data-v-d1f28634"]]),qs={key:0,class:"VPNavBarAppearance"},Ks=_({__name:"VPNavBarAppearance",setup(o){const{site:e}=P();return(t,n)=>r(e).appearance&&r(e).appearance!=="force-dark"?(a(),c("div",qs,[m(me)])):f("",!0)}}),Rs=b(Ks,[["__scopeId","data-v-e6aabb21"]]),ke=I();let De=!1,re=0;function Ws(o){const e=I(!1);if(oe){!De&&Ys(),re++;const t=O(ke,n=>{var s,i,u;n===o.el.value||(s=o.el.value)!=null&&s.contains(n)?(e.value=!0,(i=o.onFocus)==null||i.call(o)):(e.value=!1,(u=o.onBlur)==null||u.call(o))});he(()=>{t(),re--,re||Js()})}return Qe(e)}function Ys(){document.addEventListener("focusin",Oe),De=!0,ke.value=document.activeElement}function Js(){document.removeEventListener("focusin",Oe)}function Oe(){ke.value=document.activeElement}const Xs={class:"VPMenuLink"},Qs=_({__name:"VPMenuLink",props:{item:{}},setup(o){const{page:e}=P();return(t,n)=>(a(),c("div",Xs,[m(D,{class:N({active:r(z)(r(e).relativePath,t.item.activeMatch||t.item.link,!!t.item.activeMatch)}),href:t.item.link,target:t.item.target,rel:t.item.rel},{default:v(()=>[E(S(t.item.text),1)]),_:1},8,["class","href","target","rel"])]))}}),se=b(Qs,[["__scopeId","data-v-43f1e123"]]),Zs={class:"VPMenuGroup"},xs={key:0,class:"title"},en=_({__name:"VPMenuGroup",props:{text:{},items:{}},setup(o){return(e,t)=>(a(),c("div",Zs,[e.text?(a(),c("p",xs,S(e.text),1)):f("",!0),(a(!0),c(M,null,F(e.items,n=>(a(),c(M,null,["link"in n?(a(),g(se,{key:0,item:n},null,8,["item"])):f("",!0)],64))),256))]))}}),tn=b(en,[["__scopeId","data-v-69e747b5"]]),on={class:"VPMenu"},sn={key:0,class:"items"},nn=_({__name:"VPMenu",props:{items:{}},setup(o){return(e,t)=>(a(),c("div",on,[e.items?(a(),c("div",sn,[(a(!0),c(M,null,F(e.items,n=>(a(),c(M,{key:n.text},["link"in n?(a(),g(se,{key:0,item:n},null,8,["item"])):(a(),g(tn,{key:1,text:n.text,items:n.items},null,8,["text","items"]))],64))),128))])):f("",!0),l(e.$slots,"default",{},void 0,!0)]))}}),an=b(nn,[["__scopeId","data-v-e7ea1737"]]),rn=o=>(C("data-v-b6c34ac9"),o=o(),B(),o),ln=["aria-expanded","aria-label"],cn={key:0,class:"text"},un=["innerHTML"],dn=rn(()=>d("span",{class:"vpi-chevron-down text-icon"},null,-1)),vn={key:1,class:"vpi-more-horizontal icon"},pn={class:"menu"},hn=_({__name:"VPFlyout",props:{icon:{},button:{},label:{},items:{}},setup(o){const e=I(!1),t=I();Ws({el:t,onBlur:n});function n(){e.value=!1}return(s,i)=>(a(),c("div",{class:"VPFlyout",ref_key:"el",ref:t,onMouseenter:i[1]||(i[1]=u=>e.value=!0),onMouseleave:i[2]||(i[2]=u=>e.value=!1)},[d("button",{type:"button",class:"button","aria-haspopup":"true","aria-expanded":e.value,"aria-label":s.label,onClick:i[0]||(i[0]=u=>e.value=!e.value)},[s.button||s.icon?(a(),c("span",cn,[s.icon?(a(),c("span",{key:0,class:N([s.icon,"option-icon"])},null,2)):f("",!0),s.button?(a(),c("span",{key:1,innerHTML:s.button},null,8,un)):f("",!0),dn])):(a(),c("span",vn))],8,ln),d("div",pn,[m(an,{items:s.items},{default:v(()=>[l(s.$slots,"default",{},void 0,!0)]),_:3},8,["items"])])],544))}}),be=b(hn,[["__scopeId","data-v-b6c34ac9"]]),fn=["href","aria-label","innerHTML"],_n=_({__name:"VPSocialLink",props:{icon:{},link:{},ariaLabel:{}},setup(o){const e=o,t=y(()=>typeof e.icon=="object"?e.icon.svg:``);return(n,s)=>(a(),c("a",{class:"VPSocialLink no-icon",href:n.link,"aria-label":n.ariaLabel??(typeof n.icon=="string"?n.icon:""),target:"_blank",rel:"noopener",innerHTML:t.value},null,8,fn))}}),mn=b(_n,[["__scopeId","data-v-eee4e7cb"]]),kn={class:"VPSocialLinks"},bn=_({__name:"VPSocialLinks",props:{links:{}},setup(o){return(e,t)=>(a(),c("div",kn,[(a(!0),c(M,null,F(e.links,({link:n,icon:s,ariaLabel:i})=>(a(),g(mn,{key:n,icon:s,link:n,ariaLabel:i},null,8,["icon","link","ariaLabel"]))),128))]))}}),ge=b(bn,[["__scopeId","data-v-7bc22406"]]),gn={key:0,class:"group translations"},$n={class:"trans-title"},yn={key:1,class:"group"},Pn={class:"item appearance"},Ln={class:"label"},Vn={class:"appearance-action"},Sn={key:2,class:"group"},wn={class:"item social-links"},Tn=_({__name:"VPNavBarExtra",setup(o){const{site:e,theme:t}=P(),{localeLinks:n,currentLang:s}=J({correspondingLink:!0}),i=y(()=>n.value.length&&s.value.label||e.value.appearance||t.value.socialLinks);return(u,h)=>i.value?(a(),g(be,{key:0,class:"VPNavBarExtra",label:"extra navigation"},{default:v(()=>[r(n).length&&r(s).label?(a(),c("div",gn,[d("p",$n,S(r(s).label),1),(a(!0),c(M,null,F(r(n),p=>(a(),g(se,{key:p.link,item:p},null,8,["item"]))),128))])):f("",!0),r(e).appearance&&r(e).appearance!=="force-dark"?(a(),c("div",yn,[d("div",Pn,[d("p",Ln,S(r(t).darkModeSwitchLabel||"Appearance"),1),d("div",Vn,[m(me)])])])):f("",!0),r(t).socialLinks?(a(),c("div",Sn,[d("div",wn,[m(ge,{class:"social-links-list",links:r(t).socialLinks},null,8,["links"])])])):f("",!0)]),_:1})):f("",!0)}}),In=b(Tn,[["__scopeId","data-v-d0bd9dde"]]),Nn=o=>(C("data-v-e5dd9c1c"),o=o(),B(),o),Mn=["aria-expanded"],An=Nn(()=>d("span",{class:"container"},[d("span",{class:"top"}),d("span",{class:"middle"}),d("span",{class:"bottom"})],-1)),Hn=[An],Cn=_({__name:"VPNavBarHamburger",props:{active:{type:Boolean}},emits:["click"],setup(o){return(e,t)=>(a(),c("button",{type:"button",class:N(["VPNavBarHamburger",{active:e.active}]),"aria-label":"mobile navigation","aria-expanded":e.active,"aria-controls":"VPNavScreen",onClick:t[0]||(t[0]=n=>e.$emit("click"))},Hn,10,Mn))}}),Bn=b(Cn,[["__scopeId","data-v-e5dd9c1c"]]),En=["innerHTML"],Fn=_({__name:"VPNavBarMenuLink",props:{item:{}},setup(o){const{page:e}=P();return(t,n)=>(a(),g(D,{class:N({VPNavBarMenuLink:!0,active:r(z)(r(e).relativePath,t.item.activeMatch||t.item.link,!!t.item.activeMatch)}),href:t.item.link,noIcon:t.item.noIcon,target:t.item.target,rel:t.item.rel,tabindex:"0"},{default:v(()=>[d("span",{innerHTML:t.item.text},null,8,En)]),_:1},8,["class","href","noIcon","target","rel"]))}}),Dn=b(Fn,[["__scopeId","data-v-9c663999"]]),On=_({__name:"VPNavBarMenuGroup",props:{item:{}},setup(o){const e=o,{page:t}=P(),n=i=>"link"in i?z(t.value.relativePath,i.link,!!e.item.activeMatch):i.items.some(n),s=y(()=>n(e.item));return(i,u)=>(a(),g(be,{class:N({VPNavBarMenuGroup:!0,active:r(z)(r(t).relativePath,i.item.activeMatch,!!i.item.activeMatch)||s.value}),button:i.item.text,items:i.item.items},null,8,["class","button","items"]))}}),Un=o=>(C("data-v-7f418b0f"),o=o(),B(),o),Gn={key:0,"aria-labelledby":"main-nav-aria-label",class:"VPNavBarMenu"},jn=Un(()=>d("span",{id:"main-nav-aria-label",class:"visually-hidden"},"Main Navigation",-1)),zn=_({__name:"VPNavBarMenu",setup(o){const{theme:e}=P();return(t,n)=>r(e).nav?(a(),c("nav",Gn,[jn,(a(!0),c(M,null,F(r(e).nav,s=>(a(),c(M,{key:s.text},["link"in s?(a(),g(Dn,{key:0,item:s},null,8,["item"])):(a(),g(On,{key:1,item:s},null,8,["item"]))],64))),128))])):f("",!0)}}),qn=b(zn,[["__scopeId","data-v-7f418b0f"]]);function Kn(o){const{localeIndex:e,theme:t}=P();function n(s){var A,H,w;const i=s.split("."),u=(A=t.value.search)==null?void 0:A.options,h=u&&typeof u=="object",p=h&&((w=(H=u.locales)==null?void 0:H[e.value])==null?void 0:w.translations)||null,$=h&&u.translations||null;let L=p,k=$,V=o;const T=i.pop();for(const G of i){let j=null;const R=V==null?void 0:V[G];R&&(j=V=R);const ne=k==null?void 0:k[G];ne&&(j=k=ne);const ae=L==null?void 0:L[G];ae&&(j=L=ae),R||(V=j),ne||(k=j),ae||(L=j)}return(L==null?void 0:L[T])??(k==null?void 0:k[T])??(V==null?void 0:V[T])??""}return n}const Rn=["aria-label"],Wn={class:"DocSearch-Button-Container"},Yn=d("span",{class:"vp-icon DocSearch-Search-Icon"},null,-1),Jn={class:"DocSearch-Button-Placeholder"},Xn=d("span",{class:"DocSearch-Button-Keys"},[d("kbd",{class:"DocSearch-Button-Key"}),d("kbd",{class:"DocSearch-Button-Key"},"K")],-1),Pe=_({__name:"VPNavBarSearchButton",setup(o){const t=Kn({button:{buttonText:"Search",buttonAriaLabel:"Search"}});return(n,s)=>(a(),c("button",{type:"button",class:"DocSearch DocSearch-Button","aria-label":r(t)("button.buttonAriaLabel")},[d("span",Wn,[Yn,d("span",Jn,S(r(t)("button.buttonText")),1)]),Xn],8,Rn))}}),Qn={class:"VPNavBarSearch"},Zn={id:"local-search"},xn={key:1,id:"docsearch"},ea=_({__name:"VPNavBarSearch",setup(o){const e=Ze(()=>xe(()=>import("./VPLocalSearchBox.B3jfi5U8.js"),__vite__mapDeps([0,1]))),t=()=>null,{theme:n}=P(),s=I(!1),i=I(!1);q(()=>{});function u(){s.value||(s.value=!0,setTimeout(h,16))}function h(){const k=new Event("keydown");k.key="k",k.metaKey=!0,window.dispatchEvent(k),setTimeout(()=>{document.querySelector(".DocSearch-Modal")||h()},16)}function p(k){const V=k.target,T=V.tagName;return V.isContentEditable||T==="INPUT"||T==="SELECT"||T==="TEXTAREA"}const $=I(!1);le("k",k=>{(k.ctrlKey||k.metaKey)&&(k.preventDefault(),$.value=!0)}),le("/",k=>{p(k)||(k.preventDefault(),$.value=!0)});const L="local";return(k,V)=>{var T;return a(),c("div",Qn,[r(L)==="local"?(a(),c(M,{key:0},[$.value?(a(),g(r(e),{key:0,onClose:V[0]||(V[0]=A=>$.value=!1)})):f("",!0),d("div",Zn,[m(Pe,{onClick:V[1]||(V[1]=A=>$.value=!0)})])],64)):r(L)==="algolia"?(a(),c(M,{key:1},[s.value?(a(),g(r(t),{key:0,algolia:((T=r(n).search)==null?void 0:T.options)??r(n).algolia,onVnodeBeforeMount:V[2]||(V[2]=A=>i.value=!0)},null,8,["algolia"])):f("",!0),i.value?f("",!0):(a(),c("div",xn,[m(Pe,{onClick:u})]))],64)):f("",!0)])}}}),ta=_({__name:"VPNavBarSocialLinks",setup(o){const{theme:e}=P();return(t,n)=>r(e).socialLinks?(a(),g(ge,{key:0,class:"VPNavBarSocialLinks",links:r(e).socialLinks},null,8,["links"])):f("",!0)}}),oa=b(ta,[["__scopeId","data-v-0394ad82"]]),sa=["href","rel","target"],na={key:1},aa={key:2},ra=_({__name:"VPNavBarTitle",setup(o){const{site:e,theme:t}=P(),{hasSidebar:n}=U(),{currentLang:s}=J(),i=y(()=>{var p;return typeof t.value.logoLink=="string"?t.value.logoLink:(p=t.value.logoLink)==null?void 0:p.link}),u=y(()=>{var p;return typeof t.value.logoLink=="string"||(p=t.value.logoLink)==null?void 0:p.rel}),h=y(()=>{var p;return typeof t.value.logoLink=="string"||(p=t.value.logoLink)==null?void 0:p.target});return(p,$)=>(a(),c("div",{class:N(["VPNavBarTitle",{"has-sidebar":r(n)}])},[d("a",{class:"title",href:i.value??r(fe)(r(s).link),rel:u.value,target:h.value},[l(p.$slots,"nav-bar-title-before",{},void 0,!0),r(t).logo?(a(),g(Z,{key:0,class:"logo",image:r(t).logo},null,8,["image"])):f("",!0),r(t).siteTitle?(a(),c("span",na,S(r(t).siteTitle),1)):r(t).siteTitle===void 0?(a(),c("span",aa,S(r(e).title),1)):f("",!0),l(p.$slots,"nav-bar-title-after",{},void 0,!0)],8,sa)],2))}}),ia=b(ra,[["__scopeId","data-v-ab179fa1"]]),la={class:"items"},ca={class:"title"},ua=_({__name:"VPNavBarTranslations",setup(o){const{theme:e}=P(),{localeLinks:t,currentLang:n}=J({correspondingLink:!0});return(s,i)=>r(t).length&&r(n).label?(a(),g(be,{key:0,class:"VPNavBarTranslations",icon:"vpi-languages",label:r(e).langMenuLabel||"Change language"},{default:v(()=>[d("div",la,[d("p",ca,S(r(n).label),1),(a(!0),c(M,null,F(r(t),u=>(a(),g(se,{key:u.link,item:u},null,8,["item"]))),128))])]),_:1},8,["label"])):f("",!0)}}),da=b(ua,[["__scopeId","data-v-88af2de4"]]),va=o=>(C("data-v-ccf7ddec"),o=o(),B(),o),pa={class:"wrapper"},ha={class:"container"},fa={class:"title"},_a={class:"content"},ma={class:"content-body"},ka=va(()=>d("div",{class:"divider"},[d("div",{class:"divider-line"})],-1)),ba=_({__name:"VPNavBar",props:{isScreenOpen:{type:Boolean}},emits:["toggle-screen"],setup(o){const{y:e}=Ne(),{hasSidebar:t}=U(),{frontmatter:n}=P(),s=I({});return Ve(()=>{s.value={"has-sidebar":t.value,home:n.value.layout==="home",top:e.value===0}}),(i,u)=>(a(),c("div",{class:N(["VPNavBar",s.value])},[d("div",pa,[d("div",ha,[d("div",fa,[m(ia,null,{"nav-bar-title-before":v(()=>[l(i.$slots,"nav-bar-title-before",{},void 0,!0)]),"nav-bar-title-after":v(()=>[l(i.$slots,"nav-bar-title-after",{},void 0,!0)]),_:3})]),d("div",_a,[d("div",ma,[l(i.$slots,"nav-bar-content-before",{},void 0,!0),m(ea,{class:"search"}),m(qn,{class:"menu"}),m(da,{class:"translations"}),m(Rs,{class:"appearance"}),m(oa,{class:"social-links"}),m(In,{class:"extra"}),l(i.$slots,"nav-bar-content-after",{},void 0,!0),m(Bn,{class:"hamburger",active:i.isScreenOpen,onClick:u[0]||(u[0]=h=>i.$emit("toggle-screen"))},null,8,["active"])])])])]),ka],2))}}),ga=b(ba,[["__scopeId","data-v-ccf7ddec"]]),$a={key:0,class:"VPNavScreenAppearance"},ya={class:"text"},Pa=_({__name:"VPNavScreenAppearance",setup(o){const{site:e,theme:t}=P();return(n,s)=>r(e).appearance&&r(e).appearance!=="force-dark"?(a(),c("div",$a,[d("p",ya,S(r(t).darkModeSwitchLabel||"Appearance"),1),m(me)])):f("",!0)}}),La=b(Pa,[["__scopeId","data-v-2d7af913"]]),Va=_({__name:"VPNavScreenMenuLink",props:{item:{}},setup(o){const e=te("close-screen");return(t,n)=>(a(),g(D,{class:"VPNavScreenMenuLink",href:t.item.link,target:t.item.target,rel:t.item.rel,onClick:r(e),innerHTML:t.item.text},null,8,["href","target","rel","onClick","innerHTML"]))}}),Sa=b(Va,[["__scopeId","data-v-7f31e1f6"]]),wa=_({__name:"VPNavScreenMenuGroupLink",props:{item:{}},setup(o){const e=te("close-screen");return(t,n)=>(a(),g(D,{class:"VPNavScreenMenuGroupLink",href:t.item.link,target:t.item.target,rel:t.item.rel,onClick:r(e)},{default:v(()=>[E(S(t.item.text),1)]),_:1},8,["href","target","rel","onClick"]))}}),Ue=b(wa,[["__scopeId","data-v-19976ae1"]]),Ta={class:"VPNavScreenMenuGroupSection"},Ia={key:0,class:"title"},Na=_({__name:"VPNavScreenMenuGroupSection",props:{text:{},items:{}},setup(o){return(e,t)=>(a(),c("div",Ta,[e.text?(a(),c("p",Ia,S(e.text),1)):f("",!0),(a(!0),c(M,null,F(e.items,n=>(a(),g(Ue,{key:n.text,item:n},null,8,["item"]))),128))]))}}),Ma=b(Na,[["__scopeId","data-v-8133b170"]]),Aa=o=>(C("data-v-ff6087d4"),o=o(),B(),o),Ha=["aria-controls","aria-expanded"],Ca=["innerHTML"],Ba=Aa(()=>d("span",{class:"vpi-plus button-icon"},null,-1)),Ea=["id"],Fa={key:1,class:"group"},Da=_({__name:"VPNavScreenMenuGroup",props:{text:{},items:{}},setup(o){const e=o,t=I(!1),n=y(()=>`NavScreenGroup-${e.text.replace(" ","-").toLowerCase()}`);function s(){t.value=!t.value}return(i,u)=>(a(),c("div",{class:N(["VPNavScreenMenuGroup",{open:t.value}])},[d("button",{class:"button","aria-controls":n.value,"aria-expanded":t.value,onClick:s},[d("span",{class:"button-text",innerHTML:i.text},null,8,Ca),Ba],8,Ha),d("div",{id:n.value,class:"items"},[(a(!0),c(M,null,F(i.items,h=>(a(),c(M,{key:h.text},["link"in h?(a(),c("div",{key:h.text,class:"item"},[m(Ue,{item:h},null,8,["item"])])):(a(),c("div",Fa,[m(Ma,{text:h.text,items:h.items},null,8,["text","items"])]))],64))),128))],8,Ea)],2))}}),Oa=b(Da,[["__scopeId","data-v-ff6087d4"]]),Ua={key:0,class:"VPNavScreenMenu"},Ga=_({__name:"VPNavScreenMenu",setup(o){const{theme:e}=P();return(t,n)=>r(e).nav?(a(),c("nav",Ua,[(a(!0),c(M,null,F(r(e).nav,s=>(a(),c(M,{key:s.text},["link"in s?(a(),g(Sa,{key:0,item:s},null,8,["item"])):(a(),g(Oa,{key:1,text:s.text||"",items:s.items},null,8,["text","items"]))],64))),128))])):f("",!0)}}),ja=_({__name:"VPNavScreenSocialLinks",setup(o){const{theme:e}=P();return(t,n)=>r(e).socialLinks?(a(),g(ge,{key:0,class:"VPNavScreenSocialLinks",links:r(e).socialLinks},null,8,["links"])):f("",!0)}}),Ge=o=>(C("data-v-858fe1a4"),o=o(),B(),o),za=Ge(()=>d("span",{class:"vpi-languages icon lang"},null,-1)),qa=Ge(()=>d("span",{class:"vpi-chevron-down icon chevron"},null,-1)),Ka={class:"list"},Ra=_({__name:"VPNavScreenTranslations",setup(o){const{localeLinks:e,currentLang:t}=J({correspondingLink:!0}),n=I(!1);function s(){n.value=!n.value}return(i,u)=>r(e).length&&r(t).label?(a(),c("div",{key:0,class:N(["VPNavScreenTranslations",{open:n.value}])},[d("button",{class:"title",onClick:s},[za,E(" "+S(r(t).label)+" ",1),qa]),d("ul",Ka,[(a(!0),c(M,null,F(r(e),h=>(a(),c("li",{key:h.link,class:"item"},[m(D,{class:"link",href:h.link},{default:v(()=>[E(S(h.text),1)]),_:2},1032,["href"])]))),128))])],2)):f("",!0)}}),Wa=b(Ra,[["__scopeId","data-v-858fe1a4"]]),Ya={class:"container"},Ja=_({__name:"VPNavScreen",props:{open:{type:Boolean}},setup(o){const e=I(null),t=Me(oe?document.body:null);return(n,s)=>(a(),g(ve,{name:"fade",onEnter:s[0]||(s[0]=i=>t.value=!0),onAfterLeave:s[1]||(s[1]=i=>t.value=!1)},{default:v(()=>[n.open?(a(),c("div",{key:0,class:"VPNavScreen",ref_key:"screen",ref:e,id:"VPNavScreen"},[d("div",Ya,[l(n.$slots,"nav-screen-content-before",{},void 0,!0),m(Ga,{class:"menu"}),m(Wa,{class:"translations"}),m(La,{class:"appearance"}),m(ja,{class:"social-links"}),l(n.$slots,"nav-screen-content-after",{},void 0,!0)])],512)):f("",!0)]),_:3}))}}),Xa=b(Ja,[["__scopeId","data-v-cc5739dd"]]),Qa={key:0,class:"VPNav"},Za=_({__name:"VPNav",setup(o){const{isScreenOpen:e,closeScreen:t,toggleScreen:n}=Cs(),{frontmatter:s}=P(),i=y(()=>s.value.navbar!==!1);return Ae("close-screen",t),x(()=>{oe&&document.documentElement.classList.toggle("hide-nav",!i.value)}),(u,h)=>i.value?(a(),c("header",Qa,[m(ga,{"is-screen-open":r(e),onToggleScreen:r(n)},{"nav-bar-title-before":v(()=>[l(u.$slots,"nav-bar-title-before",{},void 0,!0)]),"nav-bar-title-after":v(()=>[l(u.$slots,"nav-bar-title-after",{},void 0,!0)]),"nav-bar-content-before":v(()=>[l(u.$slots,"nav-bar-content-before",{},void 0,!0)]),"nav-bar-content-after":v(()=>[l(u.$slots,"nav-bar-content-after",{},void 0,!0)]),_:3},8,["is-screen-open","onToggleScreen"]),m(Xa,{open:r(e)},{"nav-screen-content-before":v(()=>[l(u.$slots,"nav-screen-content-before",{},void 0,!0)]),"nav-screen-content-after":v(()=>[l(u.$slots,"nav-screen-content-after",{},void 0,!0)]),_:3},8,["open"])])):f("",!0)}}),xa=b(Za,[["__scopeId","data-v-ae24b3ad"]]),je=o=>(C("data-v-b8d55f3b"),o=o(),B(),o),er=["role","tabindex"],tr=je(()=>d("div",{class:"indicator"},null,-1)),or=["onKeydown"],sr=je(()=>d("span",{class:"vpi-chevron-right caret-icon"},null,-1)),nr=[sr],ar={key:1,class:"items"},rr=_({__name:"VPSidebarItem",props:{item:{},depth:{}},setup(o){const e=o,{collapsed:t,collapsible:n,isLink:s,isActiveLink:i,hasActiveLink:u,hasChildren:h,toggle:p}=Lt(y(()=>e.item)),$=y(()=>h.value?"section":"div"),L=y(()=>s.value?"a":"div"),k=y(()=>h.value?e.depth+2===7?"p":`h${e.depth+2}`:"p"),V=y(()=>s.value?void 0:"button"),T=y(()=>[[`level-${e.depth}`],{collapsible:n.value},{collapsed:t.value},{"is-link":s.value},{"is-active":i.value},{"has-active":u.value}]);function A(w){"key"in w&&w.key!=="Enter"||!e.item.link&&p()}function H(){e.item.link&&p()}return(w,G)=>{const j=K("VPSidebarItem",!0);return a(),g(W($.value),{class:N(["VPSidebarItem",T.value])},{default:v(()=>[w.item.text?(a(),c("div",X({key:0,class:"item",role:V.value},tt(w.item.items?{click:A,keydown:A}:{},!0),{tabindex:w.item.items&&0}),[tr,w.item.link?(a(),g(D,{key:0,tag:L.value,class:"link",href:w.item.link,rel:w.item.rel,target:w.item.target},{default:v(()=>[(a(),g(W(k.value),{class:"text",innerHTML:w.item.text},null,8,["innerHTML"]))]),_:1},8,["tag","href","rel","target"])):(a(),g(W(k.value),{key:1,class:"text",innerHTML:w.item.text},null,8,["innerHTML"])),w.item.collapsed!=null&&w.item.items&&w.item.items.length?(a(),c("div",{key:2,class:"caret",role:"button","aria-label":"toggle section",onClick:H,onKeydown:et(H,["enter"]),tabindex:"0"},nr,40,or)):f("",!0)],16,er)):f("",!0),w.item.items&&w.item.items.length?(a(),c("div",ar,[w.depth<5?(a(!0),c(M,{key:0},F(w.item.items,R=>(a(),g(j,{key:R.text,item:R,depth:w.depth+1},null,8,["item","depth"]))),128)):f("",!0)])):f("",!0)]),_:1},8,["class"])}}}),ir=b(rr,[["__scopeId","data-v-b8d55f3b"]]),ze=o=>(C("data-v-575e6a36"),o=o(),B(),o),lr=ze(()=>d("div",{class:"curtain"},null,-1)),cr={class:"nav",id:"VPSidebarNav","aria-labelledby":"sidebar-aria-label",tabindex:"-1"},ur=ze(()=>d("span",{class:"visually-hidden",id:"sidebar-aria-label"}," Sidebar Navigation ",-1)),dr=_({__name:"VPSidebar",props:{open:{type:Boolean}},setup(o){const e=o,{sidebarGroups:t,hasSidebar:n}=U(),s=I(null),i=Me(oe?document.body:null);return O([e,s],()=>{var u;e.open?(i.value=!0,(u=s.value)==null||u.focus()):i.value=!1},{immediate:!0,flush:"post"}),(u,h)=>r(n)?(a(),c("aside",{key:0,class:N(["VPSidebar",{open:u.open}]),ref_key:"navEl",ref:s,onClick:h[0]||(h[0]=ot(()=>{},["stop"]))},[lr,d("nav",cr,[ur,l(u.$slots,"sidebar-nav-before",{},void 0,!0),(a(!0),c(M,null,F(r(t),p=>(a(),c("div",{key:p.text,class:"group"},[m(ir,{item:p,depth:0},null,8,["item"])]))),128)),l(u.$slots,"sidebar-nav-after",{},void 0,!0)])],2)):f("",!0)}}),vr=b(dr,[["__scopeId","data-v-575e6a36"]]),pr=_({__name:"VPSkipLink",setup(o){const e=Y(),t=I();O(()=>e.path,()=>t.value.focus());function n({target:s}){const i=document.getElementById(decodeURIComponent(s.hash).slice(1));if(i){const u=()=>{i.removeAttribute("tabindex"),i.removeEventListener("blur",u)};i.setAttribute("tabindex","-1"),i.addEventListener("blur",u),i.focus(),window.scrollTo(0,0)}}return(s,i)=>(a(),c(M,null,[d("span",{ref_key:"backToTop",ref:t,tabindex:"-1"},null,512),d("a",{href:"#VPContent",class:"VPSkipLink visually-hidden",onClick:n}," Skip to content ")],64))}}),hr=b(pr,[["__scopeId","data-v-0f60ec36"]]),fr=_({__name:"Layout",setup(o){const{isOpen:e,open:t,close:n}=U(),s=Y();O(()=>s.path,n),Pt(e,n);const{frontmatter:i}=P(),u=st(),h=y(()=>!!u["home-hero-image"]);return Ae("hero-image-slot-exists",h),(p,$)=>{const L=K("Content");return r(i).layout!==!1?(a(),c("div",{key:0,class:N(["Layout",r(i).pageClass])},[l(p.$slots,"layout-top",{},void 0,!0),m(hr),m(lt,{class:"backdrop",show:r(e),onClick:r(n)},null,8,["show","onClick"]),m(xa,null,{"nav-bar-title-before":v(()=>[l(p.$slots,"nav-bar-title-before",{},void 0,!0)]),"nav-bar-title-after":v(()=>[l(p.$slots,"nav-bar-title-after",{},void 0,!0)]),"nav-bar-content-before":v(()=>[l(p.$slots,"nav-bar-content-before",{},void 0,!0)]),"nav-bar-content-after":v(()=>[l(p.$slots,"nav-bar-content-after",{},void 0,!0)]),"nav-screen-content-before":v(()=>[l(p.$slots,"nav-screen-content-before",{},void 0,!0)]),"nav-screen-content-after":v(()=>[l(p.$slots,"nav-screen-content-after",{},void 0,!0)]),_:3}),m(Hs,{open:r(e),onOpenMenu:r(t)},null,8,["open","onOpenMenu"]),m(vr,{open:r(e)},{"sidebar-nav-before":v(()=>[l(p.$slots,"sidebar-nav-before",{},void 0,!0)]),"sidebar-nav-after":v(()=>[l(p.$slots,"sidebar-nav-after",{},void 0,!0)]),_:3},8,["open"]),m(ps,null,{"page-top":v(()=>[l(p.$slots,"page-top",{},void 0,!0)]),"page-bottom":v(()=>[l(p.$slots,"page-bottom",{},void 0,!0)]),"not-found":v(()=>[l(p.$slots,"not-found",{},void 0,!0)]),"home-hero-before":v(()=>[l(p.$slots,"home-hero-before",{},void 0,!0)]),"home-hero-info-before":v(()=>[l(p.$slots,"home-hero-info-before",{},void 0,!0)]),"home-hero-info":v(()=>[l(p.$slots,"home-hero-info",{},void 0,!0)]),"home-hero-info-after":v(()=>[l(p.$slots,"home-hero-info-after",{},void 0,!0)]),"home-hero-actions-after":v(()=>[l(p.$slots,"home-hero-actions-after",{},void 0,!0)]),"home-hero-image":v(()=>[l(p.$slots,"home-hero-image",{},void 0,!0)]),"home-hero-after":v(()=>[l(p.$slots,"home-hero-after",{},void 0,!0)]),"home-features-before":v(()=>[l(p.$slots,"home-features-before",{},void 0,!0)]),"home-features-after":v(()=>[l(p.$slots,"home-features-after",{},void 0,!0)]),"doc-footer-before":v(()=>[l(p.$slots,"doc-footer-before",{},void 0,!0)]),"doc-before":v(()=>[l(p.$slots,"doc-before",{},void 0,!0)]),"doc-after":v(()=>[l(p.$slots,"doc-after",{},void 0,!0)]),"doc-top":v(()=>[l(p.$slots,"doc-top",{},void 0,!0)]),"doc-bottom":v(()=>[l(p.$slots,"doc-bottom",{},void 0,!0)]),"aside-top":v(()=>[l(p.$slots,"aside-top",{},void 0,!0)]),"aside-bottom":v(()=>[l(p.$slots,"aside-bottom",{},void 0,!0)]),"aside-outline-before":v(()=>[l(p.$slots,"aside-outline-before",{},void 0,!0)]),"aside-outline-after":v(()=>[l(p.$slots,"aside-outline-after",{},void 0,!0)]),"aside-ads-before":v(()=>[l(p.$slots,"aside-ads-before",{},void 0,!0)]),"aside-ads-after":v(()=>[l(p.$slots,"aside-ads-after",{},void 0,!0)]),_:3}),m(ks),l(p.$slots,"layout-bottom",{},void 0,!0)],2)):(a(),g(L,{key:1}))}}}),_r=b(fr,[["__scopeId","data-v-5d98c3a5"]]),qe={Layout:_r,enhanceApp:({app:o})=>{o.component("Badge",at)}},mr=_({__name:"HighlightTargetedHeading",setup(o){function e(){if(!window||!window.location||!window.location.hash)return;const n=decodeURIComponent(window.location.hash);if(!n)return;let s;try{s=document.querySelector(n)}catch(i){console.error(i);return}s&&(s.classList.contains("VPNolebaseHighlightTargetedHeading")||s.classList.add("VPNolebaseHighlightTargetedHeading"),s.classList.remove("VPNolebaseHighlightTargetedHeadingAnimated"),setTimeout(()=>{s&&s.classList.add("VPNolebaseHighlightTargetedHeadingAnimated")},10))}const t=Y();return q(e),O(t,async()=>{await Ie(),e()}),nt("hashchange",e),(n,s)=>l(n.$slots,"default")}}),Le={},$e=o=>(C("data-v-90dd949c"),o=o(),B(),o),kr={class:"vp-doc"},br=$e(()=>d("a",{rel:"license",href:"https://creativecommons.org/licenses/by-nc-sa/4.0/"},"CC BY-NC-SA 4.0",-1)),gr=$e(()=>d("div",null,"Any and all opinions listed here are my own and not representative of my employers; future, past and present.",-1)),$r=$e(()=>d("div",null,[d("a",{href:"https://resume.incremental.social/thepaperpilot/thepaperpilot"},"Resume"),E(" (not actively seeking new opportunities).")],-1)),yr=["href"],Pr=_({__name:"Layout",async setup(o){let e,t;const n=Le.promisify(Le.exec),s=([e,t]=ye(()=>n('git log -n 1 --format="https://code.incremental.social/thepaperpilot/pages/commit/%H"')),e=await e,t(),e).stdout.replaceAll(/\n$/g,""),i=([e,t]=ye(()=>n('git log -n 1 --date=format:"%A, %B %d, %Y at %X" --format=%ad')),e=await e,t(),e).stdout.replaceAll(/\n$/g,"");return(u,h)=>(a(),g(r(qe).Layout,null,{"layout-top":v(()=>[m(r(mr))]),"layout-bottom":v(()=>[d("footer",kr,[d("div",null,[E("CC "+S(new Date().getFullYear())+" The Paper Pilot. ",1),br,E(".")]),gr,$r,d("div",null,[E("Site built from "),d("a",{href:r(s)},"this commit",8,yr),E(" on "),d("time",null,S(r(i)),1),E(".")])])]),_:1}))}}),Lr=b(Pr,[["__scopeId","data-v-90dd949c"]]),Sr={...qe,Layout:Lr};export{Sr as R,Kn as c,P as u}; diff --git a/assets/garden_activitypub_index.md.CicDcQ2_.js b/assets/garden_activitypub_index.md.CicDcQ2_.js deleted file mode 100644 index 579672a7..00000000 --- a/assets/garden_activitypub_index.md.CicDcQ2_.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"ActivityPub","description":"","frontmatter":{"public":"true","slug":"activitypub","tags":["Decentralized"],"title":"ActivityPub","prev":false,"next":false},"headers":[],"relativePath":"garden/activitypub/index.md","filePath":"garden/activitypub/index.md"}'),r={name:"garden/activitypub/index.md"},c=i('

ActivityPub ​

Referenced by: Fediverse

Tags: Decentralized

ActivityPub is a protocol for Federated Social Media

',4),o=[c];function n(d,s,l,p,_,u){return a(),t("div",null,o)}const v=e(r,[["render",n]]);export{f as __pageData,v as default}; diff --git a/assets/garden_activitypub_index.md.CicDcQ2_.lean.js b/assets/garden_activitypub_index.md.CicDcQ2_.lean.js deleted file mode 100644 index b53d601b..00000000 --- a/assets/garden_activitypub_index.md.CicDcQ2_.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"ActivityPub","description":"","frontmatter":{"public":"true","slug":"activitypub","tags":["Decentralized"],"title":"ActivityPub","prev":false,"next":false},"headers":[],"relativePath":"garden/activitypub/index.md","filePath":"garden/activitypub/index.md"}'),r={name:"garden/activitypub/index.md"},c=i("",4),o=[c];function n(d,s,l,p,_,u){return a(),t("div",null,o)}const v=e(r,[["render",n]]);export{f as __pageData,v as default}; diff --git a/assets/garden_advent-incremental_index.md.C8yXdubg.js b/assets/garden_advent-incremental_index.md.C8yXdubg.js deleted file mode 100644 index f1fcfd95..00000000 --- a/assets/garden_advent-incremental_index.md.C8yXdubg.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as n}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Advent Incremental","description":"","frontmatter":{"public":"true","slug":"advent-incremental","tags":["My Projects","Profectus"],"title":"Advent Incremental","prev":false,"next":false},"headers":[],"relativePath":"garden/advent-incremental/index.md","filePath":"garden/advent-incremental/index.md"}'),r={name:"garden/advent-incremental/index.md"},o=n('

Advent Incremental ​

Tags: My Projects, Profectus

Play it here!

An Open Source game made in Profectus over the course of 1 month by myself and other devs I know in the Incremental Games community!

I had the idea of an advent-style game that unlocked new pieces of content every real-life day a couple days before December started.

This was one of the most hectic months of my life!

I'm super happy with how it turned out. It ended up being way more ambitious than I anticipated but the end result is super large and awesome!

The TV Tropes page on this game mentions some of the cool things about this game

',8),s=[o];function c(i,d,p,l,m,h){return a(),t("div",null,s)}const _=e(r,[["render",c]]);export{u as __pageData,_ as default}; diff --git a/assets/garden_advent-incremental_index.md.C8yXdubg.lean.js b/assets/garden_advent-incremental_index.md.C8yXdubg.lean.js deleted file mode 100644 index 1c4b9556..00000000 --- a/assets/garden_advent-incremental_index.md.C8yXdubg.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as n}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Advent Incremental","description":"","frontmatter":{"public":"true","slug":"advent-incremental","tags":["My Projects","Profectus"],"title":"Advent Incremental","prev":false,"next":false},"headers":[],"relativePath":"garden/advent-incremental/index.md","filePath":"garden/advent-incremental/index.md"}'),r={name:"garden/advent-incremental/index.md"},o=n("",8),s=[o];function c(i,d,p,l,m,h){return a(),t("div",null,s)}const _=e(r,[["render",c]]);export{u as __pageData,_ as default}; diff --git a/assets/garden_artificial-intelligence_index.md.DHIZV-Nf.js b/assets/garden_artificial-intelligence_index.md.DHIZV-Nf.js deleted file mode 100644 index fd8a0a71..00000000 --- a/assets/garden_artificial-intelligence_index.md.DHIZV-Nf.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as l}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Artificial Intelligence","description":"","frontmatter":{"public":"true","slug":"artificial-intelligence","title":"Artificial Intelligence","prev":false,"next":false},"headers":[],"relativePath":"garden/artificial-intelligence/index.md","filePath":"garden/artificial-intelligence/index.md"}'),i={name:"garden/artificial-intelligence/index.md"},r=l('

Artificial Intelligence ​

Referenced by: Command Palettes

Catch all term that refers to many different things

Generative AI

  • Models trained on large amounts of existing human made content in order to produce more of that content
  • Copyright concerns over how training data is obtained
  • Common Examples

Human + AI cooperation

',7),o=[r];function n(s,c,d,p,h,f){return t(),a("div",null,o)}const g=e(i,[["render",n]]);export{m as __pageData,g as default}; diff --git a/assets/garden_artificial-intelligence_index.md.DHIZV-Nf.lean.js b/assets/garden_artificial-intelligence_index.md.DHIZV-Nf.lean.js deleted file mode 100644 index 4056dc23..00000000 --- a/assets/garden_artificial-intelligence_index.md.DHIZV-Nf.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as l}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Artificial Intelligence","description":"","frontmatter":{"public":"true","slug":"artificial-intelligence","title":"Artificial Intelligence","prev":false,"next":false},"headers":[],"relativePath":"garden/artificial-intelligence/index.md","filePath":"garden/artificial-intelligence/index.md"}'),i={name:"garden/artificial-intelligence/index.md"},r=l("",7),o=[r];function n(s,c,d,p,h,f){return t(),a("div",null,o)}const g=e(i,[["render",n]]);export{m as __pageData,g as default}; diff --git a/assets/garden_atproto_index.md.DbIIfL4R.js b/assets/garden_atproto_index.md.DbIIfL4R.js deleted file mode 100644 index b58dd059..00000000 --- a/assets/garden_atproto_index.md.DbIIfL4R.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as r,o as t,a5 as a}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"ATProto","description":"","frontmatter":{"alias":"The AT Protocol","public":"true","slug":"atproto","tags":["Decentralized"],"title":"ATProto","prev":false,"next":false},"headers":[],"relativePath":"garden/atproto/index.md","filePath":"garden/atproto/index.md"}'),o={name:"garden/atproto/index.md"},n=a('

ATProto ​

Referenced by: Fediverse

Tags: Decentralized

The AT Protocol is a protocol for Federated Social Media

Currently only used by Bluesky

In comparison to other Fediverse protocols, ATProto is designed for a small number of large instances

',6),s=[n];function d(l,i,c,p,_,f){return t(),r("div",null,s)}const T=e(o,[["render",d]]);export{u as __pageData,T as default}; diff --git a/assets/garden_atproto_index.md.DbIIfL4R.lean.js b/assets/garden_atproto_index.md.DbIIfL4R.lean.js deleted file mode 100644 index cea279bd..00000000 --- a/assets/garden_atproto_index.md.DbIIfL4R.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as r,o as t,a5 as a}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"ATProto","description":"","frontmatter":{"alias":"The AT Protocol","public":"true","slug":"atproto","tags":["Decentralized"],"title":"ATProto","prev":false,"next":false},"headers":[],"relativePath":"garden/atproto/index.md","filePath":"garden/atproto/index.md"}'),o={name:"garden/atproto/index.md"},n=a("",6),s=[n];function d(l,i,c,p,_,f){return t(),r("div",null,s)}const T=e(o,[["render",d]]);export{u as __pageData,T as default}; diff --git a/assets/garden_babble-buds_index.md.D3H2b176.js b/assets/garden_babble-buds_index.md.D3H2b176.js deleted file mode 100644 index 61b7ccc3..00000000 --- a/assets/garden_babble-buds_index.md.D3H2b176.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as r}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Babble Buds","description":"","frontmatter":{"public":"true","slug":"babble-buds","tags":["My Projects"],"title":"Babble Buds","prev":false,"next":false},"headers":[],"relativePath":"garden/babble-buds/index.md","filePath":"garden/babble-buds/index.md"}'),o={name:"garden/babble-buds/index.md"},s=r('

Babble Buds ​

Tags: My Projects

Babble Buds is a tool for creating puppets and interacting with puppets controlled by others on a shared stage

Note: I need to move the website off replit because of their monetization strategy changing. In the meantime, you can check it out from its github repository

Inspired by Puppet Pals by Robert Moran

Intended for use in RPG Campaigns

The renderer was separated into its own project, babble.js, so it could be used for stuff like cutscenes

I ported the engine to C# and used it for the cutscenes in Dice Armor

  • I don't believe I ever separated it out into its own project, but you can find the code here
',9),b=[s];function n(i,l,d,p,c,u){return a(),t("div",null,b)}const _=e(o,[["render",n]]);export{f as __pageData,_ as default}; diff --git a/assets/garden_babble-buds_index.md.D3H2b176.lean.js b/assets/garden_babble-buds_index.md.D3H2b176.lean.js deleted file mode 100644 index 62de614d..00000000 --- a/assets/garden_babble-buds_index.md.D3H2b176.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as r}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Babble Buds","description":"","frontmatter":{"public":"true","slug":"babble-buds","tags":["My Projects"],"title":"Babble Buds","prev":false,"next":false},"headers":[],"relativePath":"garden/babble-buds/index.md","filePath":"garden/babble-buds/index.md"}'),o={name:"garden/babble-buds/index.md"},s=r("",9),b=[s];function n(i,l,d,p,c,u){return a(),t("div",null,b)}const _=e(o,[["render",n]]);export{f as __pageData,_ as default}; diff --git a/assets/garden_capture-the-citadel_index.md.CzfQmks-.js b/assets/garden_capture-the-citadel_index.md.CzfQmks-.js deleted file mode 100644 index c8dda2c0..00000000 --- a/assets/garden_capture-the-citadel_index.md.CzfQmks-.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as r,a6 as i}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Capture the Citadel","description":"","frontmatter":{"public":"true","slug":"capture-the-citadel","tags":["My Projects"],"title":"Capture the Citadel","prev":false,"next":false},"headers":[],"relativePath":"garden/capture-the-citadel/index.md","filePath":"garden/capture-the-citadel/index.md"}'),n={name:"garden/capture-the-citadel/index.md"},c=r('

Capture the Citadel ​

Tags: My Projects

A 3D VR re-envisioning of a Slay the Spire-style game by Anthony Lawn and Grant Barbee for their VR class in college's final project.

For more details, visit Grant's page on the game.

screenshot.png

',5),o=[c];function s(l,p,d,h,_,u){return a(),t("div",null,o)}const m=e(n,[["render",s]]);export{f as __pageData,m as default}; diff --git a/assets/garden_capture-the-citadel_index.md.CzfQmks-.lean.js b/assets/garden_capture-the-citadel_index.md.CzfQmks-.lean.js deleted file mode 100644 index b23ad417..00000000 --- a/assets/garden_capture-the-citadel_index.md.CzfQmks-.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as r,a6 as i}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Capture the Citadel","description":"","frontmatter":{"public":"true","slug":"capture-the-citadel","tags":["My Projects"],"title":"Capture the Citadel","prev":false,"next":false},"headers":[],"relativePath":"garden/capture-the-citadel/index.md","filePath":"garden/capture-the-citadel/index.md"}'),n={name:"garden/capture-the-citadel/index.md"},c=r("",5),o=[c];function s(l,p,d,h,_,u){return a(),t("div",null,o)}const m=e(n,[["render",s]]);export{f as __pageData,m as default}; diff --git a/assets/garden_chat-glue_index.md.BTV2mQC1.js b/assets/garden_chat-glue_index.md.BTV2mQC1.js deleted file mode 100644 index 64bdd412..00000000 --- a/assets/garden_chat-glue_index.md.BTV2mQC1.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as n}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Chat Glue","description":"","frontmatter":{"public":"true","slug":"chat-glue","title":"Chat Glue","prev":false,"next":false},"headers":[],"relativePath":"garden/chat-glue/index.md","filePath":"garden/chat-glue/index.md"}'),r={name:"garden/chat-glue/index.md"},o=n('

Chat Glue ​

Referenced by: Commune, The Small Web

A theoretical chat system designed to solve the problems of transcribing branching conversations into linear timelines.

Defined by the Chatting with Glue comic.

',4),l=[o];function c(i,s,h,d,_,u){return a(),t("div",null,l)}const g=e(r,[["render",c]]);export{p as __pageData,g as default}; diff --git a/assets/garden_chat-glue_index.md.BTV2mQC1.lean.js b/assets/garden_chat-glue_index.md.BTV2mQC1.lean.js deleted file mode 100644 index 086644d7..00000000 --- a/assets/garden_chat-glue_index.md.BTV2mQC1.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as n}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Chat Glue","description":"","frontmatter":{"public":"true","slug":"chat-glue","title":"Chat Glue","prev":false,"next":false},"headers":[],"relativePath":"garden/chat-glue/index.md","filePath":"garden/chat-glue/index.md"}'),r={name:"garden/chat-glue/index.md"},o=n("",4),l=[o];function c(i,s,h,d,_,u){return a(),t("div",null,l)}const g=e(r,[["render",c]]);export{p as __pageData,g as default}; diff --git a/assets/garden_chronological_index.md.CQEy-T7E.js b/assets/garden_chronological_index.md.CQEy-T7E.js deleted file mode 100644 index 97da3f9b..00000000 --- a/assets/garden_chronological_index.md.CQEy-T7E.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as o,c as e,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const _=JSON.parse('{"title":"Chronological","description":"","frontmatter":{"public":"true","slug":"chronological","title":"Chronological","prev":false,"next":false},"headers":[],"relativePath":"garden/chronological/index.md","filePath":"garden/chronological/index.md"}'),r={name:"garden/chronological/index.md"},i=t('

Chronological ​

Referenced by: Digital Gardens, Freeform vs Chronological Dichotomy, The Small Web

A collection of information that is tied to its creation or edit date

Part of the Freeform vs Chronological Dichotomy

Anything with a "timeline" or "feed" is considered chronological

  • Even if there's algorithmic sortings that take things other than creation or edit date into account!

Chronological displays are less suitable as stores of knowledge (Digital Gardens)

Social media overuses timelines and feeds

RSS feeds work really well with this form of content

',9),l=[i];function n(c,s,d,h,g,f){return a(),e("div",null,l)}const m=o(r,[["render",n]]);export{_ as __pageData,m as default}; diff --git a/assets/garden_chronological_index.md.CQEy-T7E.lean.js b/assets/garden_chronological_index.md.CQEy-T7E.lean.js deleted file mode 100644 index 0b80b8d4..00000000 --- a/assets/garden_chronological_index.md.CQEy-T7E.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as o,c as e,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const _=JSON.parse('{"title":"Chronological","description":"","frontmatter":{"public":"true","slug":"chronological","title":"Chronological","prev":false,"next":false},"headers":[],"relativePath":"garden/chronological/index.md","filePath":"garden/chronological/index.md"}'),r={name:"garden/chronological/index.md"},i=t("",9),l=[i];function n(c,s,d,h,g,f){return a(),e("div",null,l)}const m=o(r,[["render",n]]);export{_ as __pageData,m as default}; diff --git a/assets/garden_cinny_index.md.6lP2Zwso.js b/assets/garden_cinny_index.md.6lP2Zwso.js deleted file mode 100644 index 4394aefc..00000000 --- a/assets/garden_cinny_index.md.6lP2Zwso.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as n,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Cinny","description":"","frontmatter":{"public":"true","slug":"cinny","title":"Cinny","prev":false,"next":false},"headers":[],"relativePath":"garden/cinny/index.md","filePath":"garden/cinny/index.md"}'),r={name:"garden/cinny/index.md"},i=t('

Cinny ​

Referenced by: Incremental Social

Cinny is an Open Source web client for the Matrix messaging protocol

',3),c=[i];function o(s,l,_,d,p,f){return a(),n("div",null,c)}const u=e(r,[["render",o]]);export{m as __pageData,u as default}; diff --git a/assets/garden_cinny_index.md.6lP2Zwso.lean.js b/assets/garden_cinny_index.md.6lP2Zwso.lean.js deleted file mode 100644 index c3b02546..00000000 --- a/assets/garden_cinny_index.md.6lP2Zwso.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as n,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Cinny","description":"","frontmatter":{"public":"true","slug":"cinny","title":"Cinny","prev":false,"next":false},"headers":[],"relativePath":"garden/cinny/index.md","filePath":"garden/cinny/index.md"}'),r={name:"garden/cinny/index.md"},i=t("",3),c=[i];function o(s,l,_,d,p,f){return a(),n("div",null,c)}const u=e(r,[["render",o]]);export{m as __pageData,u as default}; diff --git a/assets/garden_command-palettes_index.md.aFoJwvWM.js b/assets/garden_command-palettes_index.md.aFoJwvWM.js deleted file mode 100644 index a2e61429..00000000 --- a/assets/garden_command-palettes_index.md.aFoJwvWM.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as n}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Command Palettes","description":"","frontmatter":{"public":"true","slug":"command-palettes","title":"Command Palettes","prev":false,"next":false},"headers":[],"relativePath":"garden/command-palettes/index.md","filePath":"garden/command-palettes/index.md"}'),l={name:"garden/command-palettes/index.md"},o=n('

Command Palettes ​

Command palettes are a design pattern where apps expose functionality through a search bar

Typing what you want is almost certainly easier and faster than finding the action in some submenu or remembering an arcane hotkey

  • Especially with fuzzy search that also looks through descriptions of actions
  • Command palettes scale very well with large amounts of actions

Artificial Intelligence will make command palettes increasingly powerful

  • Eventually these may become conversational interfaces

Maggie Appleton discusses this pattern in her article on Command K Bars

  • The name comes from the fact many apps use the ctrl/cmd k shortcut to open the command palette

Many softwares I use have some form of command palette

  • Linear
  • Logseq
  • Visual Studio Code
',10),s=[o];function i(r,m,c,p,d,h){return t(),a("div",null,s)}const _=e(l,[["render",i]]);export{f as __pageData,_ as default}; diff --git a/assets/garden_command-palettes_index.md.aFoJwvWM.lean.js b/assets/garden_command-palettes_index.md.aFoJwvWM.lean.js deleted file mode 100644 index 4cbad02c..00000000 --- a/assets/garden_command-palettes_index.md.aFoJwvWM.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as n}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Command Palettes","description":"","frontmatter":{"public":"true","slug":"command-palettes","title":"Command Palettes","prev":false,"next":false},"headers":[],"relativePath":"garden/command-palettes/index.md","filePath":"garden/command-palettes/index.md"}'),l={name:"garden/command-palettes/index.md"},o=n("",10),s=[o];function i(r,m,c,p,d,h){return t(),a("div",null,s)}const _=e(l,[["render",i]]);export{f as __pageData,_ as default}; diff --git a/assets/garden_commune_index.md.DRJ4sRzw.js b/assets/garden_commune_index.md.DRJ4sRzw.js deleted file mode 100644 index 2b7c8588..00000000 --- a/assets/garden_commune_index.md.DRJ4sRzw.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as t}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Commune","description":"","frontmatter":{"public":"true","slug":"commune","title":"Commune","prev":false,"next":false},"headers":[],"relativePath":"garden/commune/index.md","filePath":"garden/commune/index.md"}'),i={name:"garden/commune/index.md"},n=t('

Commune ​

Referenced by: Federated Identity, Fedi v2, /now, Webrings, Weird

An Open Source Matrix web client built to be better for communities than anything else out there

  • Currently in development
  • Exposes certain channels such that they are web indexable
  • Will include features like Chat Glue and communal Digital Gardens

Created by Erlend Sogge Heggen, a ex-employee from Discourse

  • Maintains the Commune Blog with great write ups on the issues of the modern web, social media, etc. and how they can be improved (by Commune or related projects)
  • Also maintains a Personal Blog about similar topics

The Commune community is very interested in various topics and how they can relate together:

Related projects:

  • @laxla@tech.lgbt is creating Gimli, a federated discord alternative
    • Built on ActivityPub
    • "Guild-based" in ways matrix is not?
    • Will integrate with F3 as well
    • Wants to handle blogging as well
    • Certainly seems similar to Commune's message gardening concept
',10),l=[n];function o(d,s,h,m,c,u){return r(),a("div",null,l)}const p=e(i,[["render",o]]);export{f as __pageData,p as default}; diff --git a/assets/garden_commune_index.md.DRJ4sRzw.lean.js b/assets/garden_commune_index.md.DRJ4sRzw.lean.js deleted file mode 100644 index ec34f424..00000000 --- a/assets/garden_commune_index.md.DRJ4sRzw.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as t}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Commune","description":"","frontmatter":{"public":"true","slug":"commune","title":"Commune","prev":false,"next":false},"headers":[],"relativePath":"garden/commune/index.md","filePath":"garden/commune/index.md"}'),i={name:"garden/commune/index.md"},n=t("",10),l=[n];function o(d,s,h,m,c,u){return r(),a("div",null,l)}const p=e(i,[["render",o]]);export{f as __pageData,p as default}; diff --git a/assets/garden_davey-wreden_index.md.DUU5axE-.js b/assets/garden_davey-wreden_index.md.DUU5axE-.js deleted file mode 100644 index 39a802d4..00000000 --- a/assets/garden_davey-wreden_index.md.DUU5axE-.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as n}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Davey Wreden","description":"","frontmatter":{"public":"true","slug":"davey-wreden","title":"Davey Wreden","prev":false,"next":false},"headers":[],"relativePath":"garden/davey-wreden/index.md","filePath":"garden/davey-wreden/index.md"}'),t={name:"garden/davey-wreden/index.md"},d=n('

Davey Wreden ​

Referenced by: Ivy Road, The Beginner's Guide

Tagged by: Ivy Road, The Beginner's Guide, Wanderstop

Projects:

Talks and Interviews:

',7),o=[d];function i(l,s,h,c,g,_){return r(),a("div",null,o)}const y=e(t,[["render",i]]);export{p as __pageData,y as default}; diff --git a/assets/garden_davey-wreden_index.md.DUU5axE-.lean.js b/assets/garden_davey-wreden_index.md.DUU5axE-.lean.js deleted file mode 100644 index 1c3d8adc..00000000 --- a/assets/garden_davey-wreden_index.md.DUU5axE-.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as n}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Davey Wreden","description":"","frontmatter":{"public":"true","slug":"davey-wreden","title":"Davey Wreden","prev":false,"next":false},"headers":[],"relativePath":"garden/davey-wreden/index.md","filePath":"garden/davey-wreden/index.md"}'),t={name:"garden/davey-wreden/index.md"},d=n("",7),o=[d];function i(l,s,h,c,g,_){return r(),a("div",null,o)}const y=e(t,[["render",i]]);export{p as __pageData,y as default}; diff --git a/assets/garden_decentralized_index.md.Cbrt43lP.js b/assets/garden_decentralized_index.md.Cbrt43lP.js deleted file mode 100644 index 510f8d84..00000000 --- a/assets/garden_decentralized_index.md.Cbrt43lP.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as t}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Decentralized","description":"","frontmatter":{"alias":"Federated","public":"true","slug":"decentralized","title":"Decentralized","prev":false,"next":false},"headers":[],"relativePath":"garden/decentralized/index.md","filePath":"garden/decentralized/index.md"}'),i={name:"garden/decentralized/index.md"},n=t('

Decentralized ​

Referenced by: Commune, Fedi v2, Matrix, Social Media

Tagged by: ATProto, ActivityPub, Federated Identity, Fediverse, Nostr

Something with no central source of authority

Common examples:

In practice, the "pick a server" problem causes email and the fediverse to trend towards a handful of large servers that still suffer from some of the issues of centralization

Advantages over centralization:

  • Data ownership
  • Increased privacy
  • No rules to follow
  • Can fully customize your experience
  • No single entity can make the experience worse for everyone
  • Anyone and everyone can try their hand at improving the ecosystem
',9),o=[n];function d(l,c,s,f,p,h){return r(),a("div",null,o)}const _=e(i,[["render",d]]);export{m as __pageData,_ as default}; diff --git a/assets/garden_decentralized_index.md.Cbrt43lP.lean.js b/assets/garden_decentralized_index.md.Cbrt43lP.lean.js deleted file mode 100644 index 10eeee6f..00000000 --- a/assets/garden_decentralized_index.md.Cbrt43lP.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as t}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Decentralized","description":"","frontmatter":{"alias":"Federated","public":"true","slug":"decentralized","title":"Decentralized","prev":false,"next":false},"headers":[],"relativePath":"garden/decentralized/index.md","filePath":"garden/decentralized/index.md"}'),i={name:"garden/decentralized/index.md"},n=t("",9),o=[n];function d(l,c,s,f,p,h){return r(),a("div",null,o)}const _=e(i,[["render",d]]);export{m as __pageData,_ as default}; diff --git a/assets/garden_dice-armor_index.md.CHYRQr4z.js b/assets/garden_dice-armor_index.md.CHYRQr4z.js deleted file mode 100644 index affd8b89..00000000 --- a/assets/garden_dice-armor_index.md.CHYRQr4z.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i,a7 as o,a8 as s,a9 as r,aa as n,ab as h,ac as l,ad as c,ae as d,af as p}from"./chunks/framework.CK8QU5WH.js";const q=JSON.parse('{"title":"Dice Armor","description":"","frontmatter":{"public":"true","slug":"dice-armor","tags":["My Projects"],"title":"Dice Armor","prev":false,"next":false},"headers":[],"relativePath":"garden/dice-armor/index.md","filePath":"garden/dice-armor/index.md"}'),m={name:"garden/dice-armor/index.md"},u=i('

Dice Armor ​

Referenced by: Babble Buds

Tags: My Projects

Download it here

Dice Armor is a game that started development as a semester-long project by a team of nine: a producer, a creative director, a narrative writer, an artist, two programmers, and 3 game designers. The information here is about my contributions as the lead programmer over the semester because I can show off stuff like the editor scripts I wrote. I was doing everything from interface coding, editor scripts, integrating Babble Buds, and of course, everything related to the gameplay itself. To date I'm still the lead programmer for the game; for more up-to-date information on the current state of the game please visit the official site.

The build available here was created for showing off at the end of the semester, and as such has some buttons present to make the game easier to skip parts of the game to see all the content: You start with all the dice in the game already in the shop, there's a button to give yourself free money to buy these dice with, and in the duel, there are buttons to force a win or a loss, which can be used to skip the tutorial (not recommended for first-time players).

Tutorial

Dice Armor is a dice dueling game. Players can use abilities, flip dice, and attack each other to win in a dice game that puts chance into the hands of the players. This is what the dueling scene looks like, with a tutorial cutscene happening on top to guide the player through the basics. Also, all the dice are constructed dynamically, using quaternion math to figure out the placement of each component relative to the face it is going on. The die in the middle has one of the player' and opponents' portraits on each of its sides.

Editors

For many of the objects I've created, I've made scriptable objects so that game designers can add and modify them easily. Additionally, I would create custom inspectors for the objects to help make them as easy to understand and edit as possible. The opponent's artificial intelligence is made up of many strategies, in a prioritized list. When it is the opponents' turn they go through each strategy and check if they can be run, and if so then the opponent performs the strategy and starts back over at the top of the list of strategies. The + sign under the list of strategies opens an organized dropdown of all the various strategies.

Simulator

In addition to custom inspector code, I've created new tools for the editor for our game designers to use. This is a duel simulator that will take two opponents and simulate an arbitrary number of duels between them, and output the results and summarize them for you, much much quicker than manually going through the duels, even with an absurdly high timeScale. This will become incredibly useful in making balance changes and testing new dice against existing sets. This is a screenshot of it in edit mode, but in play mode it removes the "Dueling Managers" field and will use whatever the current duel balance settings are, allowing for the GDs to test freely in play mode without worrying about undoing all their changes afterward.

da1.png

I created the Babble Buds puppet editor and ported the rendering library I wrote for it to C# so it could be used in Unity. Dice Armor has a full campaign using cutscenes made using the Babble Buds cutscene editor, taking advantage of its support for custom commands and fields to control things like talking, giving the player dice and money, starting duels, and controlling player progression through the story.

Action Wheel

When a cutscene ends, its final command is to either start a duel or set the next cutscene in the story. In the latter case, there is an additional field for what to call the next cutscene, and what location it takes place. The cutscene is then added to the player's save file, and when they visit the city locations are greyed out until they have at least one action to do there. Each location has a dynamically populated action wheel with a custom range of acceptable angles.

Shop

The dice shop is dynamically populated by a list of dice available to the player, which can be changed during cutscenes, and is checked against the dice owned by the player to generate sold-out indicators. On the left, the player can choose to filter the options down to a single dice effect, which also updates the "Buy All" button to buy only all the dice in the current filter.

Inventory

The inventory works most the same as the shop, but for equipping dice. It also allows you to drag individual dice or entire sets to the equipped dice glyph. While dragging it will highlight all the slots the new dice will be equipped into.

Dice Rolling

The dice rolling uses the physics engine and detects once the dice have stopped moving, then determines which side is face up based on which of the normals is closest to straight up. It flags the die as cocked if that smallest angle is above a threshold. The dice sink into the table when not rolling to not interfere with any dice that are rolling.

Missile Storm

During certain events like winning the game or having the face of a die broken, the players' portraits will flash an emotion for a second. After winning, a random living die from the winning player is chosen to play their "finisher move", a flashy and dramatic effect to end the game. Shown is the arcane mechana's finisher, "Missile Storm".

After development stopped, the project became Open Source - check it out here

',25),g=[u];function f(y,b,w,_,v,k){return a(),t("div",null,g)}const I=e(m,[["render",f]]);export{q as __pageData,I as default}; diff --git a/assets/garden_dice-armor_index.md.CHYRQr4z.lean.js b/assets/garden_dice-armor_index.md.CHYRQr4z.lean.js deleted file mode 100644 index 3ee9d253..00000000 --- a/assets/garden_dice-armor_index.md.CHYRQr4z.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i,a7 as o,a8 as s,a9 as r,aa as n,ab as h,ac as l,ad as c,ae as d,af as p}from"./chunks/framework.CK8QU5WH.js";const q=JSON.parse('{"title":"Dice Armor","description":"","frontmatter":{"public":"true","slug":"dice-armor","tags":["My Projects"],"title":"Dice Armor","prev":false,"next":false},"headers":[],"relativePath":"garden/dice-armor/index.md","filePath":"garden/dice-armor/index.md"}'),m={name:"garden/dice-armor/index.md"},u=i("",25),g=[u];function f(y,b,w,_,v,k){return a(),t("div",null,g)}const I=e(m,[["render",f]]);export{q as __pageData,I as default}; diff --git a/assets/garden_digital-gardens_index.md.-_Ah0Mkb.js b/assets/garden_digital-gardens_index.md.-_Ah0Mkb.js deleted file mode 100644 index e6f546ba..00000000 --- a/assets/garden_digital-gardens_index.md.-_Ah0Mkb.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as t}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Digital Gardens","description":"","frontmatter":{"alias":"Digital Garden, Second Brain, Personal Knowledge Management, The Zettelkasten Method","public":"true","slug":"digital-gardens","title":"Digital Gardens","prev":false,"next":false},"headers":[],"relativePath":"garden/digital-gardens/index.md","filePath":"garden/digital-gardens/index.md"}'),n={name:"garden/digital-gardens/index.md"},i=t('

Digital Gardens ​

Referenced by: Chronological, Commune, Garden-RSS, The Cozy Web, The Small Web

Digital Gardens are Freeform collections of information made by an individual or community

This Knowledge Hub

Collections of digital gardens and resources for creating them:

',7),o=[i];function l(d,s,g,h,c,f){return r(),a("div",null,o)}const u=e(n,[["render",l]]);export{m as __pageData,u as default}; diff --git a/assets/garden_digital-gardens_index.md.-_Ah0Mkb.lean.js b/assets/garden_digital-gardens_index.md.-_Ah0Mkb.lean.js deleted file mode 100644 index 97bf4c39..00000000 --- a/assets/garden_digital-gardens_index.md.-_Ah0Mkb.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as t}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Digital Gardens","description":"","frontmatter":{"alias":"Digital Garden, Second Brain, Personal Knowledge Management, The Zettelkasten Method","public":"true","slug":"digital-gardens","title":"Digital Gardens","prev":false,"next":false},"headers":[],"relativePath":"garden/digital-gardens/index.md","filePath":"garden/digital-gardens/index.md"}'),n={name:"garden/digital-gardens/index.md"},i=t("",7),o=[i];function l(d,s,g,h,c,f){return r(),a("div",null,o)}const u=e(n,[["render",l]]);export{m as __pageData,u as default}; diff --git a/assets/garden_federated-identity_index.md.DXhML-Yi.js b/assets/garden_federated-identity_index.md.DXhML-Yi.js deleted file mode 100644 index 0d3f0244..00000000 --- a/assets/garden_federated-identity_index.md.DXhML-Yi.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as r}from"./chunks/framework.CK8QU5WH.js";const _=JSON.parse('{"title":"Federated Identity","description":"","frontmatter":{"public":"true","slug":"federated-identity","tags":["Decentralized"],"title":"Federated Identity","prev":false,"next":false},"headers":[],"relativePath":"garden/federated-identity/index.md","filePath":"garden/federated-identity/index.md"}'),d={name:"garden/federated-identity/index.md"},i=r('

Federated Identity ​

Referenced by: Commune, Fedi v2, Weird

Tags: Decentralized

Allow for validating one's identity without relying on a specific centralized server

Implementations:

Self hosted identity providers are NOT enough to be considered federated identity

  • OIDC and OAuth require the service owner to have pre-configured with explicitly allowed identity providers

Incremental Social uses Zitadel which does NOT support IndieAuth and probably won't

',9),n=[i];function o(l,s,c,h,p,u){return a(),t("div",null,n)}const m=e(d,[["render",o]]);export{_ as __pageData,m as default}; diff --git a/assets/garden_federated-identity_index.md.DXhML-Yi.lean.js b/assets/garden_federated-identity_index.md.DXhML-Yi.lean.js deleted file mode 100644 index 9ac7c0c1..00000000 --- a/assets/garden_federated-identity_index.md.DXhML-Yi.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as r}from"./chunks/framework.CK8QU5WH.js";const _=JSON.parse('{"title":"Federated Identity","description":"","frontmatter":{"public":"true","slug":"federated-identity","tags":["Decentralized"],"title":"Federated Identity","prev":false,"next":false},"headers":[],"relativePath":"garden/federated-identity/index.md","filePath":"garden/federated-identity/index.md"}'),d={name:"garden/federated-identity/index.md"},i=r("",9),n=[i];function o(l,s,c,h,p,u){return a(),t("div",null,n)}const m=e(d,[["render",o]]);export{_ as __pageData,m as default}; diff --git a/assets/garden_fedi-v2_index.md.CtSaZdaZ.js b/assets/garden_fedi-v2_index.md.CtSaZdaZ.js deleted file mode 100644 index d1ecf859..00000000 --- a/assets/garden_fedi-v2_index.md.CtSaZdaZ.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as i,o as t,a5 as a}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Fedi v2","description":"","frontmatter":{"public":"true","slug":"fedi-v2","title":"Fedi v2","prev":false,"next":false},"headers":[],"relativePath":"garden/fedi-v2/index.md","filePath":"garden/fedi-v2/index.md"}'),l={name:"garden/fedi-v2/index.md"},s=a('

Fedi v2 ​

Referenced by: Social Media, Weird

A placeholder name for a theoretical new federated network that is client-centric, in contrast to the server-centric Fediverse

There are further discussions about actually implementing all this within the Weird community

Inspiration ​

  • A Plan for Social Media - Rethinking Federation
    • This article doesn't address many implementation details:
      • If the server is a relay, can content not be viewed anonymously?
      • How to handle storing large amounts of data on every client?
      • Don't you still need to associate with a server for people to direct their messages to?
  • Single-user Mastodon Instance is a Bad Idea
    • Focuses on the non-feasibility of self hosting, contributing to Federated Social Media not actually having all the upsides it should theoretically have by virtue of being Decentralized
  • The Commune community
  • Existing protocols:
    • Nostr
      • Currently suffers a culture problem by being associated with alt right and crypto users, making broad adoption more difficult
    • ATProto
      • Focused on a few large instances, to be run by large corporations. Still requires associating your identity with a server you don't own
  • A lot of these ideas are learned lessons from the usenet days

Identity ​

  • Federated Identity
  • Private and public keys anyone can create and store how they want
    • Fully free to create and store with no server dependencies
  • Profile information
    • Sent as a signed message through all the relays
    • How would you trust a username?
      • Petnames could be used to display human readable names via contacts or decentralized "naming hubs"
      • In most conversations online, you can trust their display name and add them as a contact as that display name
        • You only need to verify they are the same person you interacted with previously
        • You only need to trust people you want to send money to or otherwise "important identities"
        • For important identities, you can trust your contacts forming a chain of trust, or a authoritative naming hub
          • E.g. a white house ran naming hub that verifies the identities of the president and people of Congress
          • People typically wouldn't reach out to a naming hub, as it's not typically necessary
        • Contacts supercede naming hubs, so if a naming hub is breached, anyone I've previously added as a contact is still the source of truth
          • This only fails if the private key itself was breached
        • I'm just thepaperpilot, my display name. For most online communication, this is sufficient
          • My website can have a nameserver saying this publickey is the same as the site owner
          • If I write a paper at a scientific journal, they can say the author of x paper is my publickey
  • How to handle losing your private key
    • If you do have a naming hub you can verify with, they can say the identity has a new publickey
    • Contacts can "vouch" for a identity having a new publickey
    • Clients can decide to trust the new publickey based on contacts and naming hubs saying to
    • Also applies to stolen or compromised keys

Servers ​

  • Act as relays, merely storing messages and sending them to any clients or servers that have subscribed
  • May decide to publicly display messages its received
    • These servers are how discovery would work
    • Different servers may offer unique displays, filters, etc.
  • Users can send their content to any server - no authentication or account required, as the identity suffices
    • Even replies can work this way - no need to know from where a given message originated
  • Private servers could require some password when sending messages or subscribing to things
    • Useful for a school or other entity that wants an internal social network
  • Different ways to subscribe to a server's messages
    • All messages the relay hears about (new relays essentially subscribe like this to some existing relay)
    • All messages from a specific poster ID
    • Any replies to a message created with a specific poster ID
    • Shallow subscriptions, to lighten the load when subscribing to communities

Content ​

  • Protocol should dictate how to convey text, image, audio, video, and binary content
  • Protocol should include reacting to content with arbitrary text, including a URL
    • Upvotes and downvotes are implemented with this system
  • Each message contains fields for the poster's ID (public key) and a signature that verifies the content was made by that poster
    • That signature serves as an ID for the message itself
      • Anything can be replied to using the ID as the "parent" property in a new post
  • Edits are handled as replies with some flag to indicate it's updating the parent messages' content
    • Naturally, this reply would only be respected if it matches the same creator ID
    • Servers should replace the original message entirely with this one and indicate its an edited message
      • Some servers will inevitably keep a full history though
  • Groups/communities are just specially flagged messages
    • Posting to a community is just replying to that message
    • Subscribing to a community is just subscribing to that message
    • The original message creator effectively owns the group
  • IndieWeb pages could publish these messages as well, effectively serving as clients within the network
    • Perhaps use a bit to actually send those messages to other relays within the network

Moderation ​

  • In general, edits and delete requests are made by replying with a specially flagged message
  • Edit and deletion messages are ignored unless they have the correct public key and signature
    • Parent messages form a hierarchy of permission - if someone replies to your message, you can send a delete request for that message
    • Relay owners cannot fully delete messages, but can choose to stop relaying replies etc. of messages as the server owner wishes
  • Posts can be publicly reported with a specially flagged reply
    • How to make anonymous reports?
  • Users can send deletion or edit messages even without a matching public key, and clients (or relays) can choose to respect those messages if that public key is whitelisted as a moderator
    • Messages (and by extension, groups) can have replies granting or removing permission to other public IDs at that hierarchy level
    • People can setup accounts with their desired heuristic for sending delete messages, such as looking at public reports or analyzing the content with AI
      • This way clients can effectively customize their preferred moderation
  • Clients can also choose to add additional rules for hiding content, such as any reports by followed users
  • Perhaps delete messages pull double duty as public reports in and of themselves?

Problems to solve ​

  • No anonymity
    • All upvotes, downvotes, etc. are linked to your public key
    • Perhaps a client could generate new keypairs for every action for anonymity, but then it'd be hard to determine if such an account and action was a genuine user or a bot
  • Servers could probably determine the identity of clients sending their messages to them
    • A client that only ever sends messages with a specific public key is unlikely to be a server
    • A client that doesn't subscribe to all messages is unlikely to be a server
    • Perhaps clients and servers can be identified as such, and subscribing to new messages is something you only do to servers, not clients
  • Illegal material will likely be placed on the hard drive at least temporarily
    • Messages will be downloaded and, even if you follow a moderator bot that looks for illegal material, there's likely to be a delay between receiving the initial message and receiving the bots delete message
  • You have to download all spam messages
    • For redundancy, you'd likely subscribe to multiple relay servers
    • You cannot trust several relay servers to have identical rules on not relaying messages that don't pass whatever moderation heuristic
    • Therefore, the filtering out of spam has to be done by the client, after downloading it all
',16),o=[s];function r(n,u,d,h,c,y){return t(),i("div",null,o)}const g=e(l,[["render",r]]);export{p as __pageData,g as default}; diff --git a/assets/garden_fedi-v2_index.md.CtSaZdaZ.lean.js b/assets/garden_fedi-v2_index.md.CtSaZdaZ.lean.js deleted file mode 100644 index bd94d5b6..00000000 --- a/assets/garden_fedi-v2_index.md.CtSaZdaZ.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as i,o as t,a5 as a}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Fedi v2","description":"","frontmatter":{"public":"true","slug":"fedi-v2","title":"Fedi v2","prev":false,"next":false},"headers":[],"relativePath":"garden/fedi-v2/index.md","filePath":"garden/fedi-v2/index.md"}'),l={name:"garden/fedi-v2/index.md"},s=a("",16),o=[s];function r(n,u,d,h,c,y){return t(),i("div",null,o)}const g=e(l,[["render",r]]);export{p as __pageData,g as default}; diff --git a/assets/garden_fediverse_index.md.C7LEB0uc.js b/assets/garden_fediverse_index.md.C7LEB0uc.js deleted file mode 100644 index 480c4b58..00000000 --- a/assets/garden_fediverse_index.md.C7LEB0uc.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as t}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Fediverse","description":"","frontmatter":{"alias":"Federated Social Media","public":"true","slug":"fediverse","tags":["Decentralized"],"title":"Fediverse","prev":false,"next":false},"headers":[],"relativePath":"garden/fediverse/index.md","filePath":"garden/fediverse/index.md"}'),i={name:"garden/fediverse/index.md"},d=t('

Fediverse ​

Referenced by: ATProto, Decentralized, Fedi v2, Incremental Social, Mbin, Weird

Tags: Decentralized

A collection of Social Media websites that can all talk to each other by virtue of a shared protocol

Typically refers to sites implementing ActivityPub

Implementations:

',7),n=[d];function o(l,s,c,f,p,h){return r(),a("div",null,n)}const g=e(i,[["render",o]]);export{u as __pageData,g as default}; diff --git a/assets/garden_fediverse_index.md.C7LEB0uc.lean.js b/assets/garden_fediverse_index.md.C7LEB0uc.lean.js deleted file mode 100644 index b5a15e73..00000000 --- a/assets/garden_fediverse_index.md.C7LEB0uc.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as t}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Fediverse","description":"","frontmatter":{"alias":"Federated Social Media","public":"true","slug":"fediverse","tags":["Decentralized"],"title":"Fediverse","prev":false,"next":false},"headers":[],"relativePath":"garden/fediverse/index.md","filePath":"garden/fediverse/index.md"}'),i={name:"garden/fediverse/index.md"},d=t("",7),n=[d];function o(l,s,c,f,p,h){return r(),a("div",null,n)}const g=e(i,[["render",o]]);export{u as __pageData,g as default}; diff --git a/assets/garden_forgejo_index.md.2k8RiG3S.js b/assets/garden_forgejo_index.md.2k8RiG3S.js deleted file mode 100644 index f66a2ee1..00000000 --- a/assets/garden_forgejo_index.md.2k8RiG3S.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as o,o as r,a5 as a}from"./chunks/framework.CK8QU5WH.js";const h=JSON.parse('{"title":"Forgejo","description":"","frontmatter":{"public":"true","slug":"forgejo","title":"Forgejo","prev":false,"next":false},"headers":[],"relativePath":"garden/forgejo/index.md","filePath":"garden/forgejo/index.md"}'),t={name:"garden/forgejo/index.md"},n=a('

Forgejo ​

Referenced by: Incremental Social

Forgejo is an Open Source code repository hosting software

',3),s=[n];function c(i,_,d,l,f,g){return r(),o("div",null,s)}const u=e(t,[["render",c]]);export{h as __pageData,u as default}; diff --git a/assets/garden_forgejo_index.md.2k8RiG3S.lean.js b/assets/garden_forgejo_index.md.2k8RiG3S.lean.js deleted file mode 100644 index 083332c2..00000000 --- a/assets/garden_forgejo_index.md.2k8RiG3S.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as o,o as r,a5 as a}from"./chunks/framework.CK8QU5WH.js";const h=JSON.parse('{"title":"Forgejo","description":"","frontmatter":{"public":"true","slug":"forgejo","title":"Forgejo","prev":false,"next":false},"headers":[],"relativePath":"garden/forgejo/index.md","filePath":"garden/forgejo/index.md"}'),t={name:"garden/forgejo/index.md"},n=a("",3),s=[n];function c(i,_,d,l,f,g){return r(),o("div",null,s)}const u=e(t,[["render",c]]);export{h as __pageData,u as default}; diff --git a/assets/garden_freeform-vs-chronological-dichotomy_index.md.CC0rVLI6.js b/assets/garden_freeform-vs-chronological-dichotomy_index.md.CC0rVLI6.js deleted file mode 100644 index a84685d0..00000000 --- a/assets/garden_freeform-vs-chronological-dichotomy_index.md.CC0rVLI6.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as o,c as e,o as r,a5 as a}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Freeform vs Chronological Dichotomy","description":"","frontmatter":{"public":"true","slug":"freeform-vs-chronological-dichotomy","title":"Freeform vs Chronological Dichotomy","prev":false,"next":false},"headers":[],"relativePath":"garden/freeform-vs-chronological-dichotomy/index.md","filePath":"garden/freeform-vs-chronological-dichotomy/index.md"}'),c={name:"garden/freeform-vs-chronological-dichotomy/index.md"},n=a('

Freeform vs Chronological Dichotomy ​

Referenced by: Chronological, Freeform

Describes a dichotomy between displaying information in a Freeform vs Chronological manner

',3),t=[n];function i(l,h,s,f,m,d){return r(),e("div",null,t)}const p=o(c,[["render",i]]);export{g as __pageData,p as default}; diff --git a/assets/garden_freeform-vs-chronological-dichotomy_index.md.CC0rVLI6.lean.js b/assets/garden_freeform-vs-chronological-dichotomy_index.md.CC0rVLI6.lean.js deleted file mode 100644 index b342f53f..00000000 --- a/assets/garden_freeform-vs-chronological-dichotomy_index.md.CC0rVLI6.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as o,c as e,o as r,a5 as a}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Freeform vs Chronological Dichotomy","description":"","frontmatter":{"public":"true","slug":"freeform-vs-chronological-dichotomy","title":"Freeform vs Chronological Dichotomy","prev":false,"next":false},"headers":[],"relativePath":"garden/freeform-vs-chronological-dichotomy/index.md","filePath":"garden/freeform-vs-chronological-dichotomy/index.md"}'),c={name:"garden/freeform-vs-chronological-dichotomy/index.md"},n=a("",3),t=[n];function i(l,h,s,f,m,d){return r(),e("div",null,t)}const p=o(c,[["render",i]]);export{g as __pageData,p as default}; diff --git a/assets/garden_freeform_index.md.CvO7JCJh.js b/assets/garden_freeform_index.md.CvO7JCJh.js deleted file mode 100644 index aa099830..00000000 --- a/assets/garden_freeform_index.md.CvO7JCJh.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as r,o,a5 as a}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Freeform","description":"","frontmatter":{"public":"true","slug":"freeform","title":"Freeform","prev":false,"next":false},"headers":[],"relativePath":"garden/freeform/index.md","filePath":"garden/freeform/index.md"}'),t={name:"garden/freeform/index.md"},n=a('

Freeform ​

Referenced by: Commune, Digital Gardens, Freeform vs Chronological Dichotomy, Garden-RSS, The Small Web

A collection of information that is not tied to when it was created or edited

Part of the Freeform vs Chronological Dichotomy

Anything wiki-style is considered freeform

  • A collection of living documents

Garden-RSS, a theoretical alternative to RSS that's better for freeform content

',7),i=[n];function f(d,l,c,s,m,h){return o(),r("div",null,i)}const p=e(t,[["render",f]]);export{g as __pageData,p as default}; diff --git a/assets/garden_freeform_index.md.CvO7JCJh.lean.js b/assets/garden_freeform_index.md.CvO7JCJh.lean.js deleted file mode 100644 index 7a3c76f2..00000000 --- a/assets/garden_freeform_index.md.CvO7JCJh.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as r,o,a5 as a}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Freeform","description":"","frontmatter":{"public":"true","slug":"freeform","title":"Freeform","prev":false,"next":false},"headers":[],"relativePath":"garden/freeform/index.md","filePath":"garden/freeform/index.md"}'),t={name:"garden/freeform/index.md"},n=a("",7),i=[n];function f(d,l,c,s,m,h){return o(),r("div",null,i)}const p=e(t,[["render",f]]);export{g as __pageData,p as default}; diff --git a/assets/garden_game-dev-tree_index.md.CXDRxuvP.js b/assets/garden_game-dev-tree_index.md.CXDRxuvP.js deleted file mode 100644 index a0bb041e..00000000 --- a/assets/garden_game-dev-tree_index.md.CXDRxuvP.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as r}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Game Dev Tree","description":"","frontmatter":{"public":"true","slug":"game-dev-tree","tags":["My Projects"],"title":"Game Dev Tree","prev":false,"next":false},"headers":[],"relativePath":"garden/game-dev-tree/index.md","filePath":"garden/game-dev-tree/index.md"}'),o={name:"garden/game-dev-tree/index.md"},n=r('

Game Dev Tree ​

Tags: My Projects

Play it here!

My first (good) incremental game! (My actual first was Shape Tycoon - I don't recommend it!)

It's Open Source!

The TV Tropes page on this game mentions some of the cool things about this game

',6),s=[n];function p(i,c,d,m,h,l){return a(),t("div",null,s)}const f=e(o,[["render",p]]);export{g as __pageData,f as default}; diff --git a/assets/garden_game-dev-tree_index.md.CXDRxuvP.lean.js b/assets/garden_game-dev-tree_index.md.CXDRxuvP.lean.js deleted file mode 100644 index c6a3732f..00000000 --- a/assets/garden_game-dev-tree_index.md.CXDRxuvP.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as r}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Game Dev Tree","description":"","frontmatter":{"public":"true","slug":"game-dev-tree","tags":["My Projects"],"title":"Game Dev Tree","prev":false,"next":false},"headers":[],"relativePath":"garden/game-dev-tree/index.md","filePath":"garden/game-dev-tree/index.md"}'),o={name:"garden/game-dev-tree/index.md"},n=r("",6),s=[n];function p(i,c,d,m,h,l){return a(),t("div",null,s)}const f=e(o,[["render",p]]);export{g as __pageData,f as default}; diff --git a/assets/garden_garden-rss_index.md.CeZWgVca.js b/assets/garden_garden-rss_index.md.CeZWgVca.js deleted file mode 100644 index b67af7d7..00000000 --- a/assets/garden_garden-rss_index.md.CeZWgVca.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as r,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Garden-RSS","description":"","frontmatter":{"public":"true","slug":"garden-rss","title":"Garden-RSS","prev":false,"next":false},"headers":[],"relativePath":"garden/garden-rss/index.md","filePath":"garden/garden-rss/index.md"}'),s={name:"garden/garden-rss/index.md"},i=t('

Garden-RSS ​

Referenced by: Freeform, The Small Web, This Knowledge Hub

A theoretical alternative to RSS that's better for Freeform websites (and Digital Gardens specifically )

Why is it useful?

How should it work?

  • Could display changes similar to git diffs

Existing Work

',9),n=[i];function o(l,d,c,f,h,g){return a(),r("div",null,n)}const _=e(s,[["render",o]]);export{u as __pageData,_ as default}; diff --git a/assets/garden_garden-rss_index.md.CeZWgVca.lean.js b/assets/garden_garden-rss_index.md.CeZWgVca.lean.js deleted file mode 100644 index 449217f9..00000000 --- a/assets/garden_garden-rss_index.md.CeZWgVca.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as r,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Garden-RSS","description":"","frontmatter":{"public":"true","slug":"garden-rss","title":"Garden-RSS","prev":false,"next":false},"headers":[],"relativePath":"garden/garden-rss/index.md","filePath":"garden/garden-rss/index.md"}'),s={name:"garden/garden-rss/index.md"},i=t("",9),n=[i];function o(l,d,c,f,h,g){return a(),r("div",null,n)}const _=e(s,[["render",o]]);export{u as __pageData,_ as default}; diff --git a/assets/garden_guide-to-incrementals_appeal-to-developers_index.md.Diny6WsX.js b/assets/garden_guide-to-incrementals_appeal-to-developers_index.md.Diny6WsX.js deleted file mode 100644 index 7a1fe623..00000000 --- a/assets/garden_guide-to-incrementals_appeal-to-developers_index.md.Diny6WsX.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as o}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Guide to Incrementals/Appeal to Developers","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/appeal-to-developers","title":"Guide to Incrementals/Appeal to Developers","prev":false,"next":false},"headers":[],"relativePath":"garden/guide-to-incrementals/appeal-to-developers/index.md","filePath":"garden/guide-to-incrementals/appeal-to-developers/index.md"}'),n={name:"garden/guide-to-incrementals/appeal-to-developers/index.md"},i=o('

Guide to Incrementals/Appeal to Developers ​

There are a lot of developers in the incremental games community - the genre seems to draw them in, and convert a lot of players into developers. Let's explore the reasons why this genre appeals to developers.

Incrementals are Easy to Make ​

Compared to other genres, incrementals have quite low expectations. You don't need to make fancy art, or music, or lay things out nicely. If you can make a button and learn the few lines of code necessary to make a number go up, you can make an incremental. This low threshold makes the genre perfect for those who are actively learning to code and haven't developed any gamedev-related skills yet.

Additionally, unlike other genres incrementals are uniquely easy to implement in a normal web page - no need to worry about rendering sprites, moving them around, implementing physics, etc. New developers can just use HTML to add a button, and the game is now available in your browser. You don't need to choose an engine, have admin privileges, or hell for the dedicated you don't even need a computer - there are tools for web development that run in the browser itself, so you can technically use your phone if that's all you have.

Javascript is a perfectly viable language for making web games, whereas other genres are typically going to require using other more difficult languages to learn. There are countless javascript tutorials that start from 0 knowledge of programming, making it incredibly accessible to beginners.

Players are Easy to Find ​

Once you've finished your game and uploaded it on github pages or itch or just copied the link if you're using glitch or replit (all of which are easy to do), anyone can now play the game in their browser. This low barrier to entry has shown tremendous success in getting completely unknown developers to have thousands of plays.

The incremental games community, which mostly centers around r/incremental_games, is always looking for new games and tends to flood any new ones posted with initial players.

Having your games be played can be incredibly motivating, and the community makes it quite clear that you can expect players to play your game. These communities - both for incremental games in general as well as game-specific communities - tend to be very developer friendly as well. A lot of the developers know each other, and welcome new developers with open arms, often with dedicated channels for programming help and discussions.

Monetization ​

I'd like to clarify that everything I've said above mainly applies to web-based incrementals. Incremental games are also incredibly popular on mobile, but with a much different culture and community. Many mobile gamers will still participate in the web-focused community for the culture. This web-focused community has a culture that has been criticized for being "anti-monetization". Ads, IAPs, and similar forms of monetization are often criticized, mainly due to the abundance of completely non-monetized games available from hobbyist developers. There are exceptions, like paid games often being considered fine, like Increlution or Stuck in Time, or donation ware games like kittens game, but even popular games that have IAP see some level of regular criticism, like NGU Idle, Idle Skilling, or Idle Pins. A large part of this can be explained by the community being hyper-aware of the addictive) nature of this genre and its susceptibility to exploiting players.

On mobile, however, monetization is the norm and expected. If an incremental game is available on mobile, it almost certainly will be monetized, and mobile players are aware and accepting of that. Mobile incremental games, due to their addictive nature, tend to make a lot of money. It's very lucrative, and therefore these games are quite abundant on mobile storefronts.

',13),r=[i];function l(s,d,m,c,p,h){return t(),a("div",null,r)}const y=e(n,[["render",l]]);export{g as __pageData,y as default}; diff --git a/assets/garden_guide-to-incrementals_appeal-to-developers_index.md.Diny6WsX.lean.js b/assets/garden_guide-to-incrementals_appeal-to-developers_index.md.Diny6WsX.lean.js deleted file mode 100644 index 9251cfb7..00000000 --- a/assets/garden_guide-to-incrementals_appeal-to-developers_index.md.Diny6WsX.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as o}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Guide to Incrementals/Appeal to Developers","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/appeal-to-developers","title":"Guide to Incrementals/Appeal to Developers","prev":false,"next":false},"headers":[],"relativePath":"garden/guide-to-incrementals/appeal-to-developers/index.md","filePath":"garden/guide-to-incrementals/appeal-to-developers/index.md"}'),n={name:"garden/guide-to-incrementals/appeal-to-developers/index.md"},i=o("",13),r=[i];function l(s,d,m,c,p,h){return t(),a("div",null,r)}const y=e(n,[["render",l]]);export{g as __pageData,y as default}; diff --git a/assets/garden_guide-to-incrementals_appeal-to-players_index.md.CRDB23Hr.js b/assets/garden_guide-to-incrementals_appeal-to-players_index.md.CRDB23Hr.js deleted file mode 100644 index b9af71e8..00000000 --- a/assets/garden_guide-to-incrementals_appeal-to-players_index.md.CRDB23Hr.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Guide to Incrementals/Appeal to Players","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/appeal-to-players","title":"Guide to Incrementals/Appeal to Players","prev":false,"next":false},"headers":[],"relativePath":"garden/guide-to-incrementals/appeal-to-players/index.md","filePath":"garden/guide-to-incrementals/appeal-to-players/index.md"}'),n={name:"garden/guide-to-incrementals/appeal-to-players/index.md"},o=i('

Guide to Incrementals/Appeal to Players ​

This is something that has been discussed and analyzed by many people, and to some extent, I feel like everything that can be said on the topic already has. However, a lot of these analyses are from the perspective of those with not as much experience and involvement within the genre as I'd argue would be necessary for a fully contextualized answer. I recently watched a video about Vampire Survivors, which has since been taken down due to drawing negative attention, which made me think about some interesting arguments about what games are, and what makes them good. The video's argument that "Vampire Survivors is not a video game" mirrors a claim by the developer of Cookie Clicker that his games are "non-games". Using Vampire Survivors and the video made on it as a framework, I'll be answering why incremental games appeal to players. Since the video has been taken down, I'll do my best to contextualize and generalize the arguments of the video without requiring the reader to watch it. For what it's worth, while I disagreed with the video I actually liked a lot of the way it went about thinking about games, and I consider this a continuation of that discussion.

Numbers Going Up ​

This is a very common response to why people enjoy incremental games, although it's not one I find compels me personally, and I suspect it might be a stand-in for progression) or Guide to Incrementals/What is Content?. But reportedly, some people do just like seeing big numbers. I must reiterate I suspect the actual cause is seeing big numbers in context though - if you start at 1e1000 of a currency and get to 1e1001, that isn't going to feel as satisfying as going from 1e10 to 1e100, and in any case, I don't think a button that just adds a zero to your number will feel quite satisfying - I believe its the sense of having made progress, and comparing where you are to where you started and feeling like you've earned your way here that is enjoyable.

Progression

Vampire Survivors can be argued to have a comparatively low depth to its combat compared to many other games. I'd argue it has sufficient depth and more than someone might expect who has only played the game for a short while, but it still definitely gets beat out by many other combat-focused games. Instead, a lot of the progression in Vampire Survivors comes from a meta-progression system by which base stats are increased by spending a currency that persists between runs. While it is technically possible to win without this meta-progression system, and indeed in many roguelikes players like to challenge themselves by beating the game without any meta-progression, the criticism can be made that meta-progression de-emphasizes player skill by making it less important to have to beat the game. Certainly, in incremental games, it is often literally impossible to complete a game without taking advantage of the meta-progression systems. I'd argue this does not detract from the game, however, and is actually a part of what makes incremental games, and roguelikes, enjoyable to many players: meta-progression augments the increases in skill the player is naturally gaining as they play. In effect, it's not replacing the skill increase, but exaggerating it to make it feel more real to the player.

Note: There is also a lot of progression from exploring the mechanics and discovering synergies, unlocking new weapons or playable characters, etc. That just isn't as relevant to this discussion, but it does make up a lot of the appeal of the game.

Effortlessness ​

Incremental games are so easy, a lot of them even have you progress while you're not playing! Part of the appeal is being able to feel like you're making progress while doing something actually productive - multitasking, in a way. In this sense, the game is more of a fidget toy - not something to think hard about and play actively, but something to click a few buttons every so often while you're paying attention to a lecture or studying or working. Of course, not all incremental games lend themselves to being played this way - it's specifically "idle" games that work like this. These are games that take an incredibly long amount of time to see all the content, stretching it as thin as possible, but they aren't expecting you to be sitting at your device playing it the entire time. They expect you to leave and come back later to make a bit of progress and repeat the cycle.

If you look at the higher-level play of most games, you'll see them perform difficult feats with ease and speed. They'll achieve a "flow state" that takes all their knowledge and experience of the game and uses it to play the game as instinctively as possible. It's incredible to watch things like Slay the Spire speed runs or competitive DDR-likes. I'd argue the goal of a lot of games with a competitive scene is to get so good that the game becomes effortless. In that sense, a game that allows you to reach that point earlier isn't any less legitimate, but rather lowers the barrier to entry by allowing more people to get "really good" at the game. And to be clear, Vampire Survivors and (most) incremental games aren't trivially easy - they, and to an extent, every game will have some level of learning and improvement over time.

Addiction

A lot of these reasons for why incremental games appeal may have reminded you of why gambling appeals to people, particularly those prone to addiction. Indeed, incremental games are quite often criticized for their similarity to a skinner box. Some have gone as far as to say incremental games as a genre are commenting that all games are skinner boxes). The argument goes that some games are not fun, but rather condition players into continuing to play without actually getting anything from the experience. When tied to real-world money this is seen as predatory, and to a lesser extent, even free games may be feeding the addictive sides of people and making them more prone to seek out gambling or micro-transaction heavy games.

While incremental games can be fun and even healthy in certain contexts, they can exacerbate video game addiction more than other genres. If you feel like playing incremental games is taking priority over other things in your life, or manipulating your sleep schedule, it may be prudent to seek help. See r/StopGaming for resources.

Since incremental games are often built on extrinsic motivations in the form of progression systems, it's hard to argue whether players continue to play because they are enjoying the gameplay, or if they are just conditioned to keep doing it because the game keeps rewarding them. Unfortunately, it can often feel like it's the latter, as there isn't typically anything compelling about the "gameplay" of clicking a button and waiting. There may be a significant overlap between those who enjoy incremental games and those who are most prone to addiction, and there are often posts on r/incremental_games about someone either struggling with or overcoming video game addiction.

Strategy ​

Incremental games could be considered a subset of strategy games), and inherit the appeals of strategy games. This includes the appeal of feeling like you've found a good solution to a puzzle, or that you're learning more about the game and are improving at making decisions within it. This applies to Vampire Survivors specifically, where you're learning about evolutions and synergies and what kinds of enemies can spawn under what conditions, and how best to handle them.

Note that strategy games are not all the same difficulty, as well. Vampire Survivors is still easier to play than Starcraft 2, and Cookie Clicker is probably somewhere in between (once you progress sufficiently). Vampire Survivors being so successful may indicate that "easier" strategies may have their separate appeal to harder strategy games - players like to feel smart and that they figured the game out and have optimized or mastered it, and the game being easier doesn't detract from that sense of accomplishment as much as it allows more and more users to be able to reach the point where they gain that sense.

Avoiding Staleness ​

Incremental games tend to have "paradigm shifts", where the gameplay changes in a meaningful way at various times throughout the progression of the game. These upset and change the gameplay loop, which helps keep them from stagnating. This constant "freshness" to the gameplay can keep players engaged for longer, compared to a game with a repetitive and static gameplay loop.

Good Game Design ​

Incremental games tend to show their game design "plainly", so it's more readily apparent if a game has good game design while playing, even if you're not looking for it. While different players have different preferences and might enjoy different types of games more than others, there are underlying good and bad game design principles that players will notice the effects of. To be clear, this isn't talking about stuff like big numbers being enjoyable, where I can comfortably agree to disagree with other players. They don't intrinsically make my experience better, but I'm aware of those for whom it does and I won't argue against their feelings. However, the game designer in me does feel like there are some extremely clear-cut examples of good and bad game design philosophies.

Let's start by giving an example of a mechanic I think can be easily and strongly argued is good game design. There are of course many examples, but a personal favorite of mine is how DOOM encourages aggressive gameplay by linking health drops to melee attacks. It has an intended experience it's trying to give the player - immersing themselves as DOOM guy, who would not hide behind cover when low on health - and this mechanic does a great job at encouraging and effectively teaching players to behave properly. This is in sharp contrast to shooters like Call of Duty, which have you regen health passively, encouraging players to hide behind cover and wait after getting hit. Note that I'm not arguing CoD is poorly designed, as the games have different intended experiences. I'm specifically praising DOOM for having a mechanic that does a good job at ensuring the player has that intended experience.

To contrast with an example I think is bad game design, let's talk about shields in souls-likes. This is a bit of a famous example, and I highly recommend this video essay which spends quite a good bit of time on this topic. Essentially, the argument boils down to players of earlier games in the souls games using shields too much - playing slowly, conservatively, and ultimately having less fun. Players wanted to feel safe, so they ended up playing in a way that ruined the experience for them. The developers solved this by removing shields, apart from an intentionally bad one effectively mocking the playstyle, and it did its job at getting players to play more aggressively, and often have more fun.

To bring the conversation back to incrementals, I'm incredibly opinionated on what makes a good incremental game, which I'll discuss in the game design section. Suffice it to say, incremental games rely more on good game design than other genres, due to not having much to distract from bad game design. This helps (although imperfectly - gamers are a bit too tolerant of bad game design!) well-designed games rise to the top within the genre.

Artistic Merit ​

The Vampire Survivors video made me think back to the old arguments about whether games are art, and whether they ought to be. The video seems preoccupied with attaching value to games solely based on their mechanics and the depth thereof, to the point of arguing Vampire Survivors is a waste of time due to its lack of depth. However, even setting aside the fact that if players are having fun then it's not time wasted, I think games can have artistic merit that supersedes the necessity of having (any / engaging / "deep") gameplay. I think the consensus online is that games are definitively art, although I could see the argument that some genres, like incremental games, might be a bit in a grey area. Let's talk about Vampire Survivors first though - It has a story to tell, with lore and many characters, that drive the player and encourage them to continue exploring the game and discovering things within it. Like any walking simulator, it is no less legitimate of a game or the "art" label because of any lack perceived lack of depth. For what it's worth, most art can be consumed with more ease than VS - any painting, movie, sculpture, etc.

A lot of incrementals have a narrative context that can similarly qualify them as art. Cookie Clicker is, as has been pointed out numerous times before, commenting on excess and increasing production beyond any reasonable limits - devolving into increasing production for its own sake. Indeed, a lot of incremental games are written to comment upon various concepts like capitalism or tropes in games, as discussed when defining Incrementals). However, I'd like to argue most incremental games are still art, even without any narrative context. "Art" as a concept is pretty nebulous already, but I personally like those who define it as an act of expression more than any physical result. The creator and the context within which they created the art, and any meaning they put into it, are all relevant and a part of the art itself. Most incremental games have artistic merit from things like why the creator made it, why they chose to make it an incremental game, and why they made any particular design decision. Hell, even if you play through an entire incremental game without a single thought or feeling, that very fact it elicited nothing can itself be artistic merit!

I'm not an art major, and I may be taking a somewhat extreme take on what is art and what has artistic merit, but I'd argue the overall point stands that games, and incremental games specifically, can have artistic merit, which appeals to many gamers.

',28),s=[o];function r(l,h,m,g,d,c){return a(),t("div",null,s)}const y=e(n,[["render",r]]);export{u as __pageData,y as default}; diff --git a/assets/garden_guide-to-incrementals_appeal-to-players_index.md.CRDB23Hr.lean.js b/assets/garden_guide-to-incrementals_appeal-to-players_index.md.CRDB23Hr.lean.js deleted file mode 100644 index a4f4974e..00000000 --- a/assets/garden_guide-to-incrementals_appeal-to-players_index.md.CRDB23Hr.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Guide to Incrementals/Appeal to Players","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/appeal-to-players","title":"Guide to Incrementals/Appeal to Players","prev":false,"next":false},"headers":[],"relativePath":"garden/guide-to-incrementals/appeal-to-players/index.md","filePath":"garden/guide-to-incrementals/appeal-to-players/index.md"}'),n={name:"garden/guide-to-incrementals/appeal-to-players/index.md"},o=i("",28),s=[o];function r(l,h,m,g,d,c){return a(),t("div",null,s)}const y=e(n,[["render",r]]);export{u as __pageData,y as default}; diff --git a/assets/garden_guide-to-incrementals_defining-the-genre_index.md.DC5Wks2J.js b/assets/garden_guide-to-incrementals_defining-the-genre_index.md.DC5Wks2J.js deleted file mode 100644 index 33a5bf01..00000000 --- a/assets/garden_guide-to-incrementals_defining-the-genre_index.md.DC5Wks2J.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as r}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Guide to Incrementals/Defining the Genre","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/defining-the-genre","title":"Guide to Incrementals/Defining the Genre","prev":false,"next":false},"headers":[],"relativePath":"garden/guide-to-incrementals/defining-the-genre/index.md","filePath":"garden/guide-to-incrementals/defining-the-genre/index.md"}'),n={name:"garden/guide-to-incrementals/defining-the-genre/index.md"},o=r('

Guide to Incrementals/Defining the Genre ​

Video games are placed into genres for a variety of reasons. They can give a mental shorthand to set the player's expectations up, they can help a game market itself by its similarities to other, already popular games, and honestly, people just love categorization for its own sake. For this guide, it's important to define the genre so it is clear what games it's even talking about.

This poses a problem. "Incremental" is a horribly vague way to define games. Most games have numbers going up in some form or another. We need a more specific definition - similar to how "strategy" can't just mean any game with any amount of strategy because that would be most games. What specifically differentiates incremental games from the rest?

"Incremental" implies it's a genre defined by a game mechanic, but all those game mechanics it could imply exist in many other games. Having a skill tree or upgrades doesn't make you incremental, and if a reset mechanic is all it takes then every roguelite would be an incremental as well. So clearly there's more to it than that - what makes an incremental an incremental?

I'd like to go over a couple of popular suggestions I've seen on defining the genre here. I have my personal preferences and will state them here, but I don't think there's a truly perfect answer here.

Disclaimer: I mostly play incremental games on my computer, and my definitions will be heavily biased towards the games I'm familiar with.

Incrementals vs Idlers vs Clickers ​

Oftentimes people refer to this genre as idle games and/or clicker games. You'll even find a trend of oxymoronic game titles that contain both terms. "Incremental games" is the umbrella term both those terms fall under. However, I'd like to argue that not only is it better to just use the term "incremental games", but calling them "idle games" or "clicker games" is wrong. Almost universally, these terms are used interchangeably to refer to the same kind of game, where you start the game click spamming and eventually automate the process. Frankly, that kind of game deserves neither title, and the genre of incremental games has trended away from ever requiring click spamming, as it's a bad mechanic, anyways.

While these games do span a spectrum of how active it requires you to be, and sorting games by that metric can be useful for those looking for a particular experience, the borders of when an incremental game counts as an "idler" is too blurry for the term to be useful. "Incremental games" may not be a great descriptive term for the genre (hence this many thousands of words long page on defining what the genre even is), but it's strictly better than calling them "idler" or "clicker" games. This guide will always use the term "incremental games" unless quoting someone else, as it is the term you typically see on all modern games in the genre.

Incrementals as Parodies

Let's start with one of the most interesting definitions of incremental games. Incremental games appear to be distilled versions of games or genres, "revealing" the naked game design at the core of these games or genres not unlike how parodies comment upon their source material.

To understand what that means, think of how a casino uses skinner boxes to emotionally manipulate its customers to keep playing, but "dressing" up the skinner box with tons of stimuli to hide that ultimately the goal is to condition you into coming back compulsively. The idea that incremental games are parodies means taking the stance that at some level all games are similarly manipulating you, giving dopamine rewards in a way that manipulates you to keep playing while not necessarily giving you any value or fulfillment. Incremental games, then, are any games that plainly display the skinner box, and the manipulative core of the game, at the forefront of the experience.

While incremental games can be fun and even healthy in certain contexts, they can exacerbate video game addiction more than other genres. If you feel like playing incremental games is taking priority over other things in your life, or manipulating your sleep schedule, it may be prudent to seek help. See r/StopGaming for resources.

This "undressing" tends to go hand in hand with a reduced focus on aesthetics, often just printing the game state directly to the screen as text. This makes incremental games much easier to develop, particularly for those with programming skills but not art skills, but that's a tangent for why Incremental Games Guide to Incrementals/Appeal to Developers.

Before I continue, I'd like to make my stance clear that I love games and incremental games, and do not think they should be considered inherently bad or manipulative with the above logic. Skinner boxes are just a way of manipulating behavior via rewards. The games are still fun - that's the reward! I'd believe the real criticism here is that it is "empty fun", or "empty dopamine", that doesn't offer any additional value or sense of fulfillment. I don't think that's inherently bad in moderation, although it can become a problem if the game is manipulating you for profit-seeking, or if you play the game to the detriment of the other parts of your life.

Another interpretation of incremental games as parodies comes from several mainstream incremental games that are also parodies of capitalism, such as cookie clicker and adventure capitalist. It's a very common framework for incremental games to portray the ever-increasing numbers as an insatiable hunger for resources, like the ones observed within capitalism. Therefore, these games are used as evidence that the genre as a whole is about parody and commentary.

Popular videos on incremental games that portray the genre as parodies are Why Idle games make good satire, and how it was ruined. and Bad Game Design - Clicker Games. You may also be interested in this response to the latter video from a fan of incremental games: BadGood Game Design - Clicker Games.

I think that this definition ultimately ascribes a motive to the genre as a whole that only happens to apply to some of the more mainstream titles. There certainly are incremental games commenting on different things, including the genre itself as in the case of The Prestige Tree Classic, The Ascension Tree, or Omega Layers, but certainly not all. And of course, not all games that comment on something or parody something are incremental games! Additionally, a very large majority of incremental games are mobile games using these manipulative strategies to get players to spend as much money as possible - hell, Adventure Capitalist is ostensibly a critique on capitalism but features microtransactions and gameplay that manipulates you into buying them! These profit-seeking incremental games certainly belong within the genre but are hardly parodies when they too use manipulation to serve their interests. Also, from my own anecdotal experience, those who use this definition seem to do so from a fairly surface-level familiarity with the genre, and often in the context of criticizing the genre or the fans thereof.

Incrementals as NGU ​

Another broad definition often used is that incremental games are games where the focus of the game is "numbers going up". This definition proposes that other genres simply use increasing numbers as a means to an end, but incremental games uniquely only care about the numbers themselves going up. Put another way, it implies there should be no narrative justification for the numbers going up other than "why shouldn't they be going up?"

While this definition is common because it feels easy to understand, it is difficult to formally define. Often phrases are used to describe games using this framework, such as having an "exaggerated sense of progression" or "big" numbers. These terms are vague and don't demonstrate an actual threshold between non-incrementals and incrementals. Most games have a sense of progression, so when is it "exaggerated"? How big are "big" numbers? Most notably, RPGs that are typically not considered incrementals will often pass this definition.

Additionally, a lot of incrementals tend to have some theme guiding the gameplay, or at least the names of mechanics. This makes the line blurred between when numbers are going up for their own sake versus for a contextual reason. I believe this point is best illustrated that, while most RPGs are not considered incremental games, there is a sub-genre of "incremental RPGs" that typically relates to RPGs that perform combat automatically. This definition of incremental games does not support RPGs and "incremental RPGs" being on distinct sides of the line if the only difference between them is manual vs automatic combat.

Incrementals as Strategies

This is a rarer interpretation, but there are similarities between incremental games and strategy games, implying incrementals might just be a sub-genre of strategy games. By this approach, incremental games would be defined by their relation to strategy games, and how they involve player strategy. Incremental games are often large optimization problems - above all else, the actual gameplay the player is performing is deciding what to do next. The consequences of wrong decisions are typically more lenient in incremental games - such as just not making optimal progress - but they certainly get complex.

So if we accept the premise that incrementals could fall under strategy, we still need to define what makes a strategy game an incremental versus some other strategy sub-genre. This is a bit tricky due to one particular sub-genre of strategy games: Factory Builders.

Factory builders, such as Factorio or Satisfactory, are games about gaining ever increasing resources, optimizing production, and expanding more and more. That... sounds pretty similar, doesn't it? In fact, there's been some debate on whether factory builders would fall under the "incremental" umbrella. I think it's safe to say the two are certainly related, and probably have quite a bit of overlap in playerbase.

Roguelites as Incrementals? ​

Earlier on, I mentioned reset mechanics shouldn't be used in the definition because that could make all roguelites incrementals... But what if it does? A lot of incrementals can be described as games with a strong sense of progression, often with layers of meta-progression. Roguelites fit that bill to a T. What would make roguelites not incremental? I honestly don't think there's a good explanation here, but many fans of incremental games will state they do believe the two genres to be unrelated, even if there's a significant overlap between their player bases due to having similar appealing traits.

At this point, it'd be appropriate to consider what part of the definition of roguelites precludes them from also being incrementals, but that reveals a new problem: What are roguelites? They're usually defined as rogue_likes with meta-progression, but that just pushes the problem back a step: Incrementals aren't the only genre to have difficulties defining themselves, it seems! Roguelikes are another genre where the community argues over the formal definition of their genre, although that means we can borrow from their process of coming to a consensus, and maybe come across a viable definition for incremental games.

The Berlin Interpretation ​

By far the most popular way of defining roguelikes is the "Berlin Interpretation", which acknowledged the diversity of games within the genre and argued the definition should not be based on any ideals about what the genre ought to be, but rather defined by "its canon". They argued there are a handful of games that can be used to define the canon for roguelikes, and from those games, a list of factors can be derived to determine a game's "roguelikeness". The more factors a game has, the more of a roguelike it is. This strategy is very lenient, allowing a game to not present any specific factor so long as it shows enough, and accounts for the blurriness of any genre definition by not explicitly stating how many factors a game must have to qualify as a definite roguelike.

I believe this strategy for defining genres can be applied to other genres as well. A handful of games can be argued to be the incremental games canon, and a list of factors derived from them can be used to judge any game based on its "incrementalness". I'll propose such a canon and list of factors here, but by no means should it be considered the end-all-be-all.

Note: The "Temple of the roguelike", an authority within the genre, has since replaced the Berlin Interpretation with a new set of factors here: https://blog.roguetemple.com/what-is-a-traditional-roguelike/

The Incremental Games Canon ​

Alright, time to get controversial. Up til now, I've been trying my best to stay objective and analytical, but now it's time to start making some opinionated decisions. Here is a list of games I think could justifiably make up an Incremental Games Canon:

I chose a variety of games here, biasing towards newer games, purposefully to avoid making a narrow or "traditional" definition. The genre is growing and shouldn't be constrained by the traits of the early popular titles. A lot of these could easily be replaced with other games that are mechanically congruent, so ultimately I'm sure if you asked 10 people for their canon list you'd just get 10 different answers, but I think this should sufficiently allow us to determine what factors make a game have higher "incrementalness".

The Paradigm Shift ​

The Paradigm Shift is probably the highest possible value factor for an incremental. It's so common that for a while people referred to incrementals that exhibit this trait as "unfolding" games, to the point of trying to replace the term incremental due to their popularity. Paradigm shifts refer to when the gameplay significantly changes. There are too many examples to list here, but notably, every single reset mechanic is typically going to be a paradigm shift. Examples of games with paradigm shifts that aren't tied to reset mechanics include Universal Paperclips and A Dark Room.

There are many reasons for the appeal of paradigm shifts. Oftentimes each mechanic builds on top of the existing mechanics, increasing the complexity of the game in steps so the player can follow along. They provide a sense of mystery, with the player anticipating what will happen next. They shake up the gameplay before it gets too stale - allowing the game to entertain for longer before the sense of Guide to Incrementals/What is Content? dissipates. Of the canon games selected above, I would argue every single one contains a paradigm shift (although I could see someone disagreeing with that statement wrt Increlution).

I should take a moment to say that while I'm hyping up this specific factor, we cannot just reduce the genre definition to "does it have paradigm shifts". Many games have paradigm shifts that are not incremental, so it's just an indicator of incrementalness. Additionally, it can become quite hard to determine how large of a shift is a "paradigm" shift. Take, for example, any game with a skill tree. In some games, each skill node might have a large impact on how you play with the game, and qualify as a paradigm shift for some players. In other games, each skill node might just be a small percentage modifier on some stat that doesn't really impact much more than a slight bias towards an already established mechanic that's newly buffed. Every single canon game may show that it's common amongst incremental games, but could just as easily indicate that they're common in games in general.

High-Value Factors ​

I won't take as long to discuss the high and low-value factors, as you've already seen most of them brought up earlier on this page. As a reminder, a game does NOT need all of these to be an incremental game, but these are factors that each indicate a strong possibility the game is an incremental, so having several of these means they probably are. These factors apply to most of the canon incremental games.

"Pure UI" Display. Incrementals typically have a textual presentation of the game state - there isn't a visual representation of the entities within the game. The interface is closer to what would be just the UI of a game in another genre or the control panel of a plane. If there is a visual representation, the player is often still interacting with non-diegetic game elements.

Reduced Consequences. Incrementals tend to have reduced repurcussions for misplaying. They very rarely have fail states, where often the largest consequence is simply not progressing - never losing progress.

Optimization Problems. The predominant gameplay of incrementals is typically solving optimization problems, from deciding which purchase to save up for to reasoning and deciding between different mutually exclusive options the game presents.

Resource Management. Incrementals tend to have a lot of resources within the game to keep track of.

Low-Value Factors ​

These are low-value factors, meaning they aren't as strongly correlated with incremental games. Incremental games may have none of these, and non-incrementals may have several of these - if a game only has low-value factors, they're probably not an incremental.

Fast Numeric Growth. Numbers in incremental games tend to grow faster than in other genres. There are more instances of superlinear growth. The larger the numbers get, the stronger of a signal this factor is.

Automation. As an incremental game progresses, the player often no longer has to deal with earlier mechanics, by having them either happen automatically or otherwise be replaced with an alternative that requires less player interaction.

Goal-Oriented. Incrementals are often heavily reliant on extrinsic motivation to guide the player. Typically this is through some sort of in-game goal to work towards, such as a certain amount of a resource being required to unlock or purchase something new.

Waiting is a Mechanic. In incremental games, the player may come across times where there is no action they can take, and the game will progress automatically instead. The player must wait for some amount of this automatic progress to occur before they can resume interaction with the game.

Are Roguelites Incrementals? ​

Having made our variation of the Berlin Interpretation for incremental games, we can compare it to the Berlin Interpretation to determine if there's enough overlap that any game that "passes" the Berlin Interpretation would also pass the incremental variant. That is to say, whether any roguelite would also be considered an incremental game.

The meta-progression of an incremental game could arguably be considered a paradigm shift, and certainly adds some resource management. Goal-oriented would probably also apply. I think anything other than those would be a stretch, and in my opinion that just isn't enough to qualify. To be totally honest, I was never expecting to conclude otherwise though 😉

Sub-Genres ​

There are some trends in incremental games that go beyond just being a commonly used mechanic, such that they deeply affect the rest of the game design. These trends can be used to determine sub-genres within the incremental games umbrella:

Loops games are a sub-genre defined by having a core mechanic related to a loop, where the player is deciding the actions taken per loop. Notable examples include Idle Loops, Stuck in Time, Cavernous II, and Increlution. You may also argue Groundhog Life and Progress Knight fall into this sub-genre.

ITRTG-like games are a sub-genre defined by having a core mechanic based on clearing increasingly difficult battles and often tend to have a lot of different mechanics to become progressively stronger. Notable examples include Idling to Rule the Gods, NGU Idle, and Wizard and Minion Idle.

Polynomial Growth games are a sub-genre defined by having a core mechanic related to a higher degree polynomial. Notable examples include the base layer of Antimatter Dimensions and Swarm Simulator.

Upgrades Games is a category popular on flash games websites that featured games focused on buying upgrades that would allow you to attain more currency in some sort of minigame that would earn you more money to buy more upgrades, which I'd argue now belong under the fold of incremental games. Notable examples include the Learn to Fly series and Upgrade Complete.

Cultivation RPGs are a genre of games, books, and anime popular in China that center around being in a fantasy world with characters getting stronger over time. While few of them get translated into English, a fan of incremental games may find the available games interesting.

',64),i=[o];function s(l,h,m,g,c,u){return a(),t("div",null,i)}const f=e(n,[["render",s]]);export{p as __pageData,f as default}; diff --git a/assets/garden_guide-to-incrementals_defining-the-genre_index.md.DC5Wks2J.lean.js b/assets/garden_guide-to-incrementals_defining-the-genre_index.md.DC5Wks2J.lean.js deleted file mode 100644 index cbc198f3..00000000 --- a/assets/garden_guide-to-incrementals_defining-the-genre_index.md.DC5Wks2J.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as r}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Guide to Incrementals/Defining the Genre","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/defining-the-genre","title":"Guide to Incrementals/Defining the Genre","prev":false,"next":false},"headers":[],"relativePath":"garden/guide-to-incrementals/defining-the-genre/index.md","filePath":"garden/guide-to-incrementals/defining-the-genre/index.md"}'),n={name:"garden/guide-to-incrementals/defining-the-genre/index.md"},o=r("",64),i=[o];function s(l,h,m,g,c,u){return a(),t("div",null,i)}const f=e(n,[["render",s]]);export{p as __pageData,f as default}; diff --git a/assets/garden_guide-to-incrementals_index.md.BojXmdru.js b/assets/garden_guide-to-incrementals_index.md.BojXmdru.js deleted file mode 100644 index 8284a95b..00000000 --- a/assets/garden_guide-to-incrementals_index.md.BojXmdru.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as n}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Guide to Incrementals","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals","title":"Guide to Incrementals","prev":false,"next":false},"headers":[],"relativePath":"garden/guide-to-incrementals/index.md","filePath":"garden/guide-to-incrementals/index.md"}'),i={name:"garden/guide-to-incrementals/index.md"},o=n('

Guide to Incrementals ​

This is a comprehensive guide to Incremental Games, a genre of video games. It will explore defining the genre, why it's appealing, and how to design and build your own incremental game. Along the way will be interactive examples, snippets from other creators, and relevant material to contextualize everything.

Note: This is an incomplete document. I want to keep adding opinions and opposing views from other incremental games developers, and add interactive examples to illustrate various points regarding game design and balancing. Consider this a living document - and see the changelog at the end.

Note: This was made before my switch to a digital garden, and is written as prose. Hope you don't mind!

Why am I making this? ​

That's a good question! What authority do I have to be making this guide? I haven't made the best incremental games, nor the most incremental games, certainly not the most popular ones either. But I do have some formal education in game development, know a lot of incremental game devs (as well as other game devs), and have a passionate interest in ludology, classifying genres, etc. I've also made a couple of incremental games) myself.

If you have any additional questions about my credentials or anything on this site, feel free to reach out!

Ludology ​

Making an Incremental ​

',11),r=[o];function l(s,d,m,c,g,h){return t(),a("div",null,r)}const f=e(i,[["render",l]]);export{p as __pageData,f as default}; diff --git a/assets/garden_guide-to-incrementals_index.md.BojXmdru.lean.js b/assets/garden_guide-to-incrementals_index.md.BojXmdru.lean.js deleted file mode 100644 index a61318e3..00000000 --- a/assets/garden_guide-to-incrementals_index.md.BojXmdru.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as n}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Guide to Incrementals","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals","title":"Guide to Incrementals","prev":false,"next":false},"headers":[],"relativePath":"garden/guide-to-incrementals/index.md","filePath":"garden/guide-to-incrementals/index.md"}'),i={name:"garden/guide-to-incrementals/index.md"},o=n("",11),r=[o];function l(s,d,m,c,g,h){return t(),a("div",null,r)}const f=e(i,[["render",l]]);export{p as __pageData,f as default}; diff --git a/assets/garden_guide-to-incrementals_navigating-criticism_index.md.FUIN6tkG.js b/assets/garden_guide-to-incrementals_navigating-criticism_index.md.FUIN6tkG.js deleted file mode 100644 index 4f2154d0..00000000 --- a/assets/garden_guide-to-incrementals_navigating-criticism_index.md.FUIN6tkG.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Guide to Incrementals/Navigating Criticism","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/navigating-criticism","title":"Guide to Incrementals/Navigating Criticism","prev":false,"next":false},"headers":[],"relativePath":"garden/guide-to-incrementals/navigating-criticism/index.md","filePath":"garden/guide-to-incrementals/navigating-criticism/index.md"}'),n={name:"garden/guide-to-incrementals/navigating-criticism/index.md"},o=i('

Guide to Incrementals/Navigating Criticism ​

Developing games is fun and exciting and teaches a lot of wonderful skills - I enthusiastically encourage anyone with an interest in game development to try it out - and incremental games are a wonderful way to get started. However, there are many challenges young and inexperienced developers have to face, and I think the hardest one - harder than coding, debugging, balancing, etc. - is handling criticism. When you put your heart and soul into a game it is natural to feel very vulnerable. While I think there's a lot communities can do to ensure they're welcoming, positive and constructive with their criticisms, inevitably you will eventually read some, and potentially a lot, of comments that can deeply affect you. No one is immune to this, from young incremental game developers to the largest content creators you can think of. That's why it's important to be able to process and navigate criticism, because ultimately collecting feedback is essential to the journey to becoming a better developer. On this page, we'll explore how to embrace criticism, grow from it, and continue to post your games publicly with confidence.

Reading Feedback ​

Game development is a skill that takes time and practice to get truly great at. Criticism and other constructive feedback are vital to continually improving. It's useful to look at the criticism as solely a tool for improving this game and future games - that is to say, it should never be used against you as a person. Insults towards the developer(s) themselves are never okay and should not be allowed within whatever community you're sharing your works in. If you do come across a comment you interpret as an attack upon your person, you should report it. For other negative comments, try not to internalize them; instead, focus on improving the game. By distancing your own identity from your work emotionally, you can better analyze the game and use the feedback to your advantage.

Not all feedback is made equal, and you don't need to feel compelled to read and obey every piece of feedback you receive. Learn to distinguish between constructive feedback and unhelpful comments. Constructive feedback typically offers specific suggestions for improvement, while unhelpful comments are often vague or hurtful. Prioritize the former and disregard the latter. That said, most feedback you get will not be from game developers, so take specific suggestions with a grain of salt. Determine the actual problem they're experiencing, and design what you believe the best solution to that problem would be, regardless if that's the specific solution the player asked for. And keep in mind, due to different player preferences you'll never satisfy everyone, and you don't need to. Ultimately if even just you find the game fun, then that's a success.

Seeking Feedback ​

When deciding where to share your game, consider the type of players you anticipate getting, and the kind of feedback you can anticipate receiving. Different communities will have different levels of support for learning developers, and certain communities may prefer certain types of games or mechanics. It's important to get a diverse set of feedback focused on players you think will enjoy the specific game you're making.

Collecting feedback from other game developers is incredibly helpful. They've trained themselves to recognize good and bad game design and how to articulate the differences, and from my experience are much more likely to leave positive and constructive comments since they've been in your shoes before! They understand the struggles and can offer guidance and emotional support.

Responding to Feedback ​

Negative feedback can naturally feel like an attack, and it's okay to get angry. However, lashing back is never the appropriate response. It's best to cool off IRL, and keep in mind all the positive comments you've received. There's a concept in Psychology called negative bias that explains how negative feedback tends to stick with us much more prominently than positive feedback, so it's useful to regularly remind yourself of all the positive feedback you've received. Celebrate your successes, no matter how small they may seem - getting a game to a state you can publicly share it with people is an accomplishment in and of itself!

Remember your passion and your initial reasons for getting into game development. The journey will have its ups and downs, but staying true to your vision and passion will keep you motivated.

',11),r=[o];function s(c,l,d,u,m,h){return a(),t("div",null,r)}const f=e(n,[["render",s]]);export{p as __pageData,f as default}; diff --git a/assets/garden_guide-to-incrementals_navigating-criticism_index.md.FUIN6tkG.lean.js b/assets/garden_guide-to-incrementals_navigating-criticism_index.md.FUIN6tkG.lean.js deleted file mode 100644 index d1e6033a..00000000 --- a/assets/garden_guide-to-incrementals_navigating-criticism_index.md.FUIN6tkG.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Guide to Incrementals/Navigating Criticism","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/navigating-criticism","title":"Guide to Incrementals/Navigating Criticism","prev":false,"next":false},"headers":[],"relativePath":"garden/guide-to-incrementals/navigating-criticism/index.md","filePath":"garden/guide-to-incrementals/navigating-criticism/index.md"}'),n={name:"garden/guide-to-incrementals/navigating-criticism/index.md"},o=i("",11),r=[o];function s(c,l,d,u,m,h){return a(),t("div",null,r)}const f=e(n,[["render",s]]);export{p as __pageData,f as default}; diff --git a/assets/garden_guide-to-incrementals_what-is-content_index.md.BMETYiAP.js b/assets/garden_guide-to-incrementals_what-is-content_index.md.BMETYiAP.js deleted file mode 100644 index 531b4153..00000000 --- a/assets/garden_guide-to-incrementals_what-is-content_index.md.BMETYiAP.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as n}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Guide to Incrementals/What is Content?","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/what-is-content-","title":"Guide to Incrementals/What is Content?","prev":false,"next":false},"headers":[],"relativePath":"garden/guide-to-incrementals/what-is-content/index.md","filePath":"garden/guide-to-incrementals/what-is-content/index.md"}'),o={name:"garden/guide-to-incrementals/what-is-content/index.md"},i=n('

Guide to Incrementals/What is Content? ​

If you've been in the incremental games community for any amount of time, you'll quickly find the number one thing players want is content. They want as much of it as possible! The most popular incremental games have tons of content, so they just keep stretching on and on and on, introducing mechanic after mechanic, and players love it. In fact, players seem to value the amount of content over the quality of any specific content. However, there's a bit of a lack of understanding concerning what content is, and I'd like to explore what counts as content, and how we measure it. As a baseline definition, I think "content" can just be described as the parts of the game that engage the player, but to truly understand it we need to contextualize what that means and how it affects the gameplay experience.

To clarify the purpose of this page, my goal is not to get (too) nitpicky or to attack games with "low content". There's nothing wrong with short / low-content games - I'm quite a big fan of those games myself! This is mostly targeted toward those who ask for content and settle for "long" games, and those who want to provide content but want to make sure they're not just artificially inflating the game. Ultimately, I suppose the goal is to just reduce the amount of artificially inflated content for the sake of having a "longer" game.

Interaction ​

I think it should be a fairly non-controversial opinion that time spent solely waiting should not count towards content. That is not including the time reading various effects or making decisions in your head, but rather time spent waiting for a condition to be met so you can re-engage with the game.

That is not to say games should necessarily try to minimize this time. Plenty of games lead towards more infrequent interaction and still get popular. In fact, these games appeal to many gamers who want to have something to check up on in between bursts of working on some other activity. These games seem to have fallen slightly out of fashion amongst modern incremental games, but they're still fully valid. The point I'm trying to make here is just that this time is not content. As an extreme example, a game with no interactions and just a counter that goes up every second could safely be said to have 0 content beyond the time it takes to understand what's going on. If it has a list of "goals" to hit, then the time understanding those goals and a short time after achieving each one could be considered content, but not the idle times in between.

Let's take a look at the opposite end of the spectrum - interaction that is so frequent as to become mindless. This is any mechanic where you need to spam-click something to progress. This may be a more controversial take, but I do not believe this constitutes content either. It does not engage the player, because each consecutive click blends together and they do not individually change the gameplay experience. That is to say, a single click and 100 clicks are not meaningfully different in terms of engaging the player. I'd go as far as to say clicking 100 times would be actively worse, as it's artificially delaying the next piece of actual content, alongside the issues of accessibility and potentially causing RSI.

Repeatable Purchases ​

Imagine an entity in a game that you can purchase multiple times, each time it performs the same thing but for a higher cost. These are incredibly common, from the buildings in cookie clicker to the units in swarm sim to the IP and EP multipliers in antimatter dimensions. However, how much content is each specific purchase? Is it content beyond the first purchase? Does it have diminishing returns? What if you are oscillating between two different repeatable purchases? How much content is lost when you automate) away a repeatable purchase?

I don't want to take too harsh a stance against repeatable purchases. They're useful tools and can be used in a myriad of interesting ways. I feel they do become "stale" or less meaningful content over time, and this happens exponentially quickly the more frequently it can be purchased. A classic example that I believe goes too far is the IP/EP multipliers in Antimatter Dimensions. I would go as far as to say they are a chore and do not provide any meaningful content after you've bought them a couple of times. It's a method for inflating numbers (effectively making every OOM a 5x step instead of 10x), that punishes the player progression-wise whenever they forget to max it again, and eventually gets automated away as a reward to the player for making enough progress.

Just to voice the other side of this argument, Acamaeda defended the IP multiplier as giving the player a "good" upgrade every OOM. I can understand that to a point and need to clarify I'm mainly criticizing IP/EP multipliers after they've been introduced for a while. In fact, I would defend the multipliers for a short while after they're introduced using the same logic I would use to defend normal dimensions as repeatable purchases, at least pre-infinity. There's "content" to be had in looking at what dimensions will become affordable next, and then choosing which to buy amongst those. The IP/EP multipliers, early into infinity or eternity respectively, provide another option that gets put into that mental queue of things to buy with each OOM reached - although the optimal order is often quite trivial and not particularly engaging.

The IP/EP multipliers are not the only repeatable purchase in antimatter dimensions I take offense to. The time dimensions are also a series of repeatable purchases, that are all so similar and static that it doesn't take long before you never need to put any thought into buying them, how much you're buying at once, or the order you buy them in - you just press max all and move on. The entire tab could've been just the max all button and it would not have made a difference beyond the start of the eternity layer. The normal dimensions technically have this problem as well, but since you're constantly getting antimatter the order feels like it has a larger impact and it's more meaningful content, right up until they're automated away. Infinity dimensions are a compromise between the two, so I'm highlighting time dimensions here as the most egregious.

Following Instructions ​

We're getting more and more controversial as we go along! Let's talk about how linear content is not content now (in some circumstances). A trend in incremental games is adding difficulty by adding a web of effects that abstract the true change you can expect from any specific purchase or decision you make. If a game is both linear and sufficiently abstracts the effect of player decisions, then the player will no longer be engaging with the content - they'll simply be clicking on things as they become available. This isn't necessarily a bad thing, as plenty of players don't mind this style of gameplay, but I'd argue once you reach a point where players don't bother reading the effects, those interactions are no longer truly content. Note that unlike the previous qualifiers mentioned, this qualifier is based on the player, and therefore subjective. In effect, it's a spectrum where the more complicated the web of effects becomes, the more likely it is to disengage the player.

This over-complicatedness leading to disengaging the player can also happen from non-linear gameplay. If the web of effects becomes sufficiently complicated and finding the optimal progression route too time-consuming to discover, players will seek out guides from other players who've completed the game. The second they do this, the game effectively becomes linearly following the instructions of the guide and all the above criticisms apply. Similarly to as before, though, this is a spectrum and not everyone will seek out a guide at the same level of difficulty.

Automation

Automation is a staple of the genre, but it has certain implications for the design of the game. Why, when new content is introduced, must the older content be automated away - why is it a chore and it feels rewarding to not have to do it again? Why does the new mechanic have such appeal if we know it too will just be automated away later on, and we'll be happy when that happens? It honestly begs the question of why this framework of introducing content and automating the old content is even enjoyable - and nearly nonexistent in other genres. You're not going to reach a point in a platformer game where they just automate the jumping part - that's the core mechanic! Instead, platformers either add new mechanics that build on the core mechanic or at least re-contextualize the core mechanic. However, in incremental games new content very frequently means replacing older content, as opposed to augmenting it.

Admittedly, the above paragraph ignores the obvious answer that separates incremental games in this regard. These mechanics become chores as their frequency increases. The frequency increases to give a sense of progression, and automation is seen as a reward because it now manages what was becoming unmanageable. The new content then comes in and continues the loop to give a stronger sense of progression. That's all good and a fine justification for automating content instead of building upon the base mechanic. It's also much easier to design, as each layer essentially lets you start over instead of needing to think of ideas that conform to the original core mechanic.

So, what's the problem? Even if this trend is justified and easy to implement, there are some other effects it has on the game design. First off, and this is probably a neutral point, incremental games with this cycle of replacing old mechanics with new ones trend towards more and more abstract and further away from any narrative throughline as they add layers. There are only so many justifications for resetting progress, so if a game wants to have several of these layers they're inevitably going to become generic or increasingly loosely associated with the original content. It's most unfortunate, in my opinion when an interesting or innovative core mechanic gets fully automated once a generic "prestige" layer is unlocked.

A recent example is Really Grass Cutting Incremental, an incremental game about cutting grass (although I'm really criticizing the Roblox game it's based on). Except, it doesn't continue to be about cutting grass. After you buy enough upgrades to increase your grass cutting and level up sufficiently you "prestige", an abstract term that in this case means you reset all your progress to get some currency to buy upgrades that do the same things as the original upgrades, but these won't reset on future prestiges. You'll eventually be able to "crystallize", which means you reset all your progress to get some currency to buy upgrades that do the same things as the original upgrades (and a couple of new ones) and won't reset on future crystallizes. Fine. You'll progress a bit, complete some challenges, and finally get to... grasshop? Grasshopping is this mechanic where you reset all your progress to get some resource that isn't for buying upgrades - this time you just unlock different modifiers on everything based on their amount. You may have gotten the point by now, but there are also "steelie" resets which give you steel for some reason, before unlocking a factory with various machines - none of which are directly tied to cutting grass, and start gathering things like oil and reset for rocket parts and reset to go to space and so on and so on. Throughout all of this there is absolutely no narrative justification or throughline for the direction the game is going, or why cutting grass is still relevant when we're collecting things like rocket parts. I may be going a little hard on GCI, but it is far from alone.

Tips for Developers ​

If you're a developer, by this point you should have a pretty decent idea of how to create "true" content in your game. Here are some other specific tips I'd suggest:

An upgrade that simply unlocks another upgrade trivially isn't content. However, many games have an upgrade that just unlocks a feature, which then has a wait or other requirements before it can be used. Try to make sure when you unlock a feature, there is immediately something to do with the feature - for example, perhaps give them a small amount of the new currency it unlocks, if applicable.

If you don't have a large web of effects, and can definitively say the impact of a purchase is to multiply the gain of the cost currency by N, and the next purchase costs N times the amount of that same currency, then this purchase effectively made no difference and it may have made more sense to just go directly to the next upgrade. That said, having effects based on things like the number of purchases made will quickly invalidate this tip.

',24),s=[i];function r(h,l,c,u,m,d){return a(),t("div",null,s)}const f=e(o,[["render",r]]);export{p as __pageData,f as default}; diff --git a/assets/garden_guide-to-incrementals_what-is-content_index.md.BMETYiAP.lean.js b/assets/garden_guide-to-incrementals_what-is-content_index.md.BMETYiAP.lean.js deleted file mode 100644 index af9c7ecd..00000000 --- a/assets/garden_guide-to-incrementals_what-is-content_index.md.BMETYiAP.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as n}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Guide to Incrementals/What is Content?","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/what-is-content-","title":"Guide to Incrementals/What is Content?","prev":false,"next":false},"headers":[],"relativePath":"garden/guide-to-incrementals/what-is-content/index.md","filePath":"garden/guide-to-incrementals/what-is-content/index.md"}'),o={name:"garden/guide-to-incrementals/what-is-content/index.md"},i=n("",24),s=[i];function r(h,l,c,u,m,d){return a(),t("div",null,s)}const f=e(o,[["render",r]]);export{p as __pageData,f as default}; diff --git a/assets/garden_incremental-social_index.md.D80WDhip.js b/assets/garden_incremental-social_index.md.D80WDhip.js deleted file mode 100644 index 69f974d6..00000000 --- a/assets/garden_incremental-social_index.md.D80WDhip.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as n,a5 as t}from"./chunks/framework.CK8QU5WH.js";const h=JSON.parse('{"title":"Incremental Social","description":"","frontmatter":{"public":"tags:: My Projects","slug":"incremental-social","title":"Incremental Social","prev":false,"next":false},"headers":[],"relativePath":"garden/incremental-social/index.md","filePath":"garden/incremental-social/index.md"}'),r={name:"garden/incremental-social/index.md"},o=t('

Incremental Social ​

Referenced by: Federated Identity, /now, Webrings

Tags: My Projects

Incremental Social is a Fediverse website hosted by me!

Made explicitly for the incremental games community

Most notably hosts an instance of Mbin, Forgejo, and Synapse (and Cinny)

',6),i=[o];function c(s,l,d,m,f,p){return n(),a("div",null,i)}const g=e(r,[["render",c]]);export{h as __pageData,g as default}; diff --git a/assets/garden_incremental-social_index.md.D80WDhip.lean.js b/assets/garden_incremental-social_index.md.D80WDhip.lean.js deleted file mode 100644 index bd6ccdec..00000000 --- a/assets/garden_incremental-social_index.md.D80WDhip.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as n,a5 as t}from"./chunks/framework.CK8QU5WH.js";const h=JSON.parse('{"title":"Incremental Social","description":"","frontmatter":{"public":"tags:: My Projects","slug":"incremental-social","title":"Incremental Social","prev":false,"next":false},"headers":[],"relativePath":"garden/incremental-social/index.md","filePath":"garden/incremental-social/index.md"}'),r={name:"garden/incremental-social/index.md"},o=t("",6),i=[o];function c(s,l,d,m,f,p){return n(),a("div",null,i)}const g=e(r,[["render",c]]);export{h as __pageData,g as default}; diff --git a/assets/garden_ivy-road_index.md.I5lUYnjM.js b/assets/garden_ivy-road_index.md.I5lUYnjM.js deleted file mode 100644 index cbf8e045..00000000 --- a/assets/garden_ivy-road_index.md.I5lUYnjM.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as d}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Ivy Road","description":"","frontmatter":{"public":"true","slug":"ivy-road","tags":["Davey Wreden"],"title":"Ivy Road","prev":false,"next":false},"headers":[],"relativePath":"garden/ivy-road/index.md","filePath":"garden/ivy-road/index.md"}'),t={name:"garden/ivy-road/index.md"},o=d('

Ivy Road ​

Referenced by: Davey Wreden, Wanderstop

Tags: Davey Wreden

Ivy Road is a indie game studio created by Davey Wreden, Karla Kimonja, and C418

',4),n=[o];function i(s,c,_,l,p,v){return r(),a("div",null,n)}const h=e(t,[["render",i]]);export{f as __pageData,h as default}; diff --git a/assets/garden_ivy-road_index.md.I5lUYnjM.lean.js b/assets/garden_ivy-road_index.md.I5lUYnjM.lean.js deleted file mode 100644 index aacf7612..00000000 --- a/assets/garden_ivy-road_index.md.I5lUYnjM.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as d}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Ivy Road","description":"","frontmatter":{"public":"true","slug":"ivy-road","tags":["Davey Wreden"],"title":"Ivy Road","prev":false,"next":false},"headers":[],"relativePath":"garden/ivy-road/index.md","filePath":"garden/ivy-road/index.md"}'),t={name:"garden/ivy-road/index.md"},o=d("",4),n=[o];function i(s,c,_,l,p,v){return r(),a("div",null,n)}const h=e(t,[["render",i]]);export{f as __pageData,h as default}; diff --git a/assets/garden_kronos_index.md.iUhWCop9.js b/assets/garden_kronos_index.md.iUhWCop9.js deleted file mode 100644 index 2974df2f..00000000 --- a/assets/garden_kronos_index.md.iUhWCop9.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as o,o as t,a5 as a}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Kronos","description":"","frontmatter":{"public":"true","slug":"kronos","tags":["My Projects","Profectus"],"title":"Kronos","prev":false,"next":false},"headers":[],"relativePath":"garden/kronos/index.md","filePath":"garden/kronos/index.md"}'),r={name:"garden/kronos/index.md"},n=a('

Kronos ​

Referenced by: V-ecs

Tags: My Projects, Profectus

My largest and most ambitious incremental game I've ever made

  • A magnum opus, of sorts ;P

Still in development, and will be for a long time. I have full intention of completing it, however

An older version, that is built in The Modding Tree, only has the gameplay, and only goes up to Chapter 2, can be played here

',7),s=[n];function l(i,c,d,p,_,h){return t(),o("div",null,s)}const m=e(r,[["render",l]]);export{f as __pageData,m as default}; diff --git a/assets/garden_kronos_index.md.iUhWCop9.lean.js b/assets/garden_kronos_index.md.iUhWCop9.lean.js deleted file mode 100644 index ef9ef9be..00000000 --- a/assets/garden_kronos_index.md.iUhWCop9.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as o,o as t,a5 as a}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Kronos","description":"","frontmatter":{"public":"true","slug":"kronos","tags":["My Projects","Profectus"],"title":"Kronos","prev":false,"next":false},"headers":[],"relativePath":"garden/kronos/index.md","filePath":"garden/kronos/index.md"}'),r={name:"garden/kronos/index.md"},n=a("",7),s=[n];function l(i,c,d,p,_,h){return t(),o("div",null,s)}const m=e(r,[["render",l]]);export{f as __pageData,m as default}; diff --git a/assets/garden_life-is-strange_index.md.tdVgcS32.js b/assets/garden_life-is-strange_index.md.tdVgcS32.js deleted file mode 100644 index a5fd2627..00000000 --- a/assets/garden_life-is-strange_index.md.tdVgcS32.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i,ag as r,ah as o}from"./chunks/framework.CK8QU5WH.js";const w=JSON.parse('{"title":"Life is Strange","description":"","frontmatter":{"public":"true","slug":"life-is-strange","title":"Life is Strange","prev":false,"next":false},"headers":[],"relativePath":"garden/life-is-strange/index.md","filePath":"garden/life-is-strange/index.md"}'),s={name:"garden/life-is-strange/index.md"},n=i('

Life is Strange ​

A series of narrative driven video games with a focus on player choices

I really enjoyed the first game and engaged with the community a lot. I would get very emotional playing through the later chapters, and it became one of my favorite games.

Playthroughs I enjoyed:

Around the start of Haley and I's relationship, we'd play through LiS1 on projectors in our's classrooms

The ending ​

I was not a huge fan of the ending of Life is Strange. Of the two endings, one very clearly got a lot more resources spent on it, but I think Max's story has a better conclusion under the other.

In my mind, Max's arc (and major themes of the last chapter) was about learning not to rely on her powers, and to learn to live with the consequences of her actions. To that end, having the game end with her taking responsibility and living with the consequences of such a major event is a fitting thematic conclusion to the game and her character arc. In contrast, the other ending shows Max relying on her powers once again and, in my opinion, portrays Max as having not grown nor learned any lessons throughout the entire series. I think its a disservice this ending got so much more attention, with unique outfits and a song dedicated to it.

Life is Strange: Before the Storm ​

I really enjoyed this story. I didn't get quite as invested, perhaps due to it being a condensed 3 chapters rather than 5, but the characters will still just as amazing, which is what makes LiS so good. The ending didn't have as much of a punch as LiS1 - in fact, the entire back half of episode 3 didn't quite meet the bar in my eyes. At the time, I enjoyed these threads discussing criticisms levied at that part of the game:

Deadbones played through the game here

The Awesome Adventures of Captain Spirit ​

I enjoyed the demo, and it certainly got me hyped for LiS2 (although I would've been regardless). Switching to UE seemed like a really good move, and the comic theme fits the aesthetic of the series well.

Life is Strange 2 ​

Unfortunately, I've only played the first chapter of this game. I wanted to play through it with Haley, but we haven't found time to do so.

LATER Skip the rest of LiS1 and play LiS2 with Haley

Life is Strange: True Colors ​

This game seems interesting, although the power does seem a little funnily close to "has empathy". I haven't had time to play it, but would like to.

Life is Strange: Double Exposure ​

I'm very excited for this game! Returning to Max's story sounds awesome. Although I will say, from the trailer alone it's incredibly obvious what one of the story beats will be: Revealing that the two timelines follow the two disparate endings from LiS1.

This game was announced to come with premium editions that get access to the game earlier

  • I think this is a horrible anti-consumer practice
  • Since this game is narratively driven, it is prone to spoilers
  • They're getting more money from their biggest fans without providing any tangible value to them, other than making the experience worse for everyone who plays but doesn't cough up that money
  • I hope other narratively driven games find other ways to do Video Game Monetization
',25),l=[n];function h(d,g,c,m,f,u){return a(),t("div",null,l)}const _=e(s,[["render",h]]);export{w as __pageData,_ as default}; diff --git a/assets/garden_life-is-strange_index.md.tdVgcS32.lean.js b/assets/garden_life-is-strange_index.md.tdVgcS32.lean.js deleted file mode 100644 index 7ad2e021..00000000 --- a/assets/garden_life-is-strange_index.md.tdVgcS32.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i,ag as r,ah as o}from"./chunks/framework.CK8QU5WH.js";const w=JSON.parse('{"title":"Life is Strange","description":"","frontmatter":{"public":"true","slug":"life-is-strange","title":"Life is Strange","prev":false,"next":false},"headers":[],"relativePath":"garden/life-is-strange/index.md","filePath":"garden/life-is-strange/index.md"}'),s={name:"garden/life-is-strange/index.md"},n=i("",25),l=[n];function h(d,g,c,m,f,u){return a(),t("div",null,l)}const _=e(s,[["render",h]]);export{w as __pageData,_ as default}; diff --git a/assets/garden_logseq_index.md.BiLoV0bt.js b/assets/garden_logseq_index.md.BiLoV0bt.js deleted file mode 100644 index 7238997f..00000000 --- a/assets/garden_logseq_index.md.BiLoV0bt.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o,a5 as t}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Logseq","description":"","frontmatter":{"public":"true","slug":"logseq","title":"Logseq","prev":false,"next":false},"headers":[],"relativePath":"garden/logseq/index.md","filePath":"garden/logseq/index.md"}'),r={name:"garden/logseq/index.md"},s=t('

Logseq ​

Referenced by: Command Palettes, This Knowledge Hub

Logseq is an Open Source outlining software

',3),n=[s];function l(d,c,i,_,g,p){return o(),a("div",null,n)}const u=e(r,[["render",l]]);export{f as __pageData,u as default}; diff --git a/assets/garden_logseq_index.md.BiLoV0bt.lean.js b/assets/garden_logseq_index.md.BiLoV0bt.lean.js deleted file mode 100644 index c0acd8ca..00000000 --- a/assets/garden_logseq_index.md.BiLoV0bt.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o,a5 as t}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Logseq","description":"","frontmatter":{"public":"true","slug":"logseq","title":"Logseq","prev":false,"next":false},"headers":[],"relativePath":"garden/logseq/index.md","filePath":"garden/logseq/index.md"}'),r={name:"garden/logseq/index.md"},s=t("",3),n=[s];function l(d,c,i,_,g,p){return o(),a("div",null,n)}const u=e(r,[["render",l]]);export{f as __pageData,u as default}; diff --git a/assets/garden_matrix_index.md.CeSXZSDm.js b/assets/garden_matrix_index.md.CeSXZSDm.js deleted file mode 100644 index d7768c30..00000000 --- a/assets/garden_matrix_index.md.CeSXZSDm.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as t}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Matrix","description":"","frontmatter":{"public":"true","slug":"matrix","title":"Matrix","prev":false,"next":false},"headers":[],"relativePath":"garden/matrix/index.md","filePath":"garden/matrix/index.md"}'),n={name:"garden/matrix/index.md"},i=t('

Matrix ​

Referenced by: Cinny, Commune, Synapse

Matrix is a protocol for Decentralized messaging

',3),o=[i];function s(d,c,_,l,m,p){return r(),a("div",null,o)}const h=e(n,[["render",s]]);export{f as __pageData,h as default}; diff --git a/assets/garden_matrix_index.md.CeSXZSDm.lean.js b/assets/garden_matrix_index.md.CeSXZSDm.lean.js deleted file mode 100644 index 16624495..00000000 --- a/assets/garden_matrix_index.md.CeSXZSDm.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as t}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Matrix","description":"","frontmatter":{"public":"true","slug":"matrix","title":"Matrix","prev":false,"next":false},"headers":[],"relativePath":"garden/matrix/index.md","filePath":"garden/matrix/index.md"}'),n={name:"garden/matrix/index.md"},i=t("",3),o=[i];function s(d,c,_,l,m,p){return r(),a("div",null,o)}const h=e(n,[["render",s]]);export{f as __pageData,h as default}; diff --git a/assets/garden_mbin_index.md.BHK-Iuf3.js b/assets/garden_mbin_index.md.BHK-Iuf3.js deleted file mode 100644 index b368c1b4..00000000 --- a/assets/garden_mbin_index.md.BHK-Iuf3.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as n}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Mbin","description":"","frontmatter":{"public":"true","slug":"mbin","title":"Mbin","prev":false,"next":false},"headers":[],"relativePath":"garden/mbin/index.md","filePath":"garden/mbin/index.md"}'),r={name:"garden/mbin/index.md"},i=n('

Mbin ​

Referenced by: Incremental Social

Mbin is an Open Source Fediverse software

Can show both twitter-style posts and reddit-style threads

',4),o=[i];function s(d,c,l,_,p,b){return t(),a("div",null,o)}const f=e(r,[["render",s]]);export{m as __pageData,f as default}; diff --git a/assets/garden_mbin_index.md.BHK-Iuf3.lean.js b/assets/garden_mbin_index.md.BHK-Iuf3.lean.js deleted file mode 100644 index 43e87a14..00000000 --- a/assets/garden_mbin_index.md.BHK-Iuf3.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as n}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Mbin","description":"","frontmatter":{"public":"true","slug":"mbin","title":"Mbin","prev":false,"next":false},"headers":[],"relativePath":"garden/mbin/index.md","filePath":"garden/mbin/index.md"}'),r={name:"garden/mbin/index.md"},i=n("",4),o=[i];function s(d,c,l,_,p,b){return t(),a("div",null,o)}const f=e(r,[["render",s]]);export{m as __pageData,f as default}; diff --git a/assets/garden_mtx_index.md.BRzkTeai.js b/assets/garden_mtx_index.md.BRzkTeai.js deleted file mode 100644 index 3c9802be..00000000 --- a/assets/garden_mtx_index.md.BRzkTeai.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as a,c as n,o as r,j as e,a as t}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"MTX","description":"","frontmatter":{"alias":"Microtransactions, IAP, In-App Purchases","public":"true","slug":"mtx","title":"MTX","prev":false,"next":false},"headers":[],"relativePath":"garden/mtx/index.md","filePath":"garden/mtx/index.md"}'),s={name:"garden/mtx/index.md"},o=e("h1",{id:"mtx",tabindex:"-1"},[t("MTX "),e("a",{class:"header-anchor",href:"#mtx","aria-label":'Permalink to "MTX"'},"​")],-1),i=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/premium-currency/"},"Premium Currency"),t(", "),e("a",{href:"/garden/video-game-monetization/"},"Video Game Monetization")])],-1),c=e("p",null,"Purchaseable items in video games that cost real life currencies",-1),d=[o,i,c];function l(m,u,_,p,h,x){return r(),n("div",null,d)}const P=a(s,[["render",l]]);export{g as __pageData,P as default}; diff --git a/assets/garden_mtx_index.md.BRzkTeai.lean.js b/assets/garden_mtx_index.md.BRzkTeai.lean.js deleted file mode 100644 index 3c9802be..00000000 --- a/assets/garden_mtx_index.md.BRzkTeai.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as a,c as n,o as r,j as e,a as t}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"MTX","description":"","frontmatter":{"alias":"Microtransactions, IAP, In-App Purchases","public":"true","slug":"mtx","title":"MTX","prev":false,"next":false},"headers":[],"relativePath":"garden/mtx/index.md","filePath":"garden/mtx/index.md"}'),s={name:"garden/mtx/index.md"},o=e("h1",{id:"mtx",tabindex:"-1"},[t("MTX "),e("a",{class:"header-anchor",href:"#mtx","aria-label":'Permalink to "MTX"'},"​")],-1),i=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/premium-currency/"},"Premium Currency"),t(", "),e("a",{href:"/garden/video-game-monetization/"},"Video Game Monetization")])],-1),c=e("p",null,"Purchaseable items in video games that cost real life currencies",-1),d=[o,i,c];function l(m,u,_,p,h,x){return r(),n("div",null,d)}const P=a(s,[["render",l]]);export{g as __pageData,P as default}; diff --git a/assets/garden_my-personal-website_index.md.DwfKlijC.js b/assets/garden_my-personal-website_index.md.DwfKlijC.js deleted file mode 100644 index 544a0b34..00000000 --- a/assets/garden_my-personal-website_index.md.DwfKlijC.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as r}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"My Personal Website","description":"","frontmatter":{"public":"true","slug":"my-personal-website","title":"My Personal Website","prev":false,"next":false},"headers":[],"relativePath":"garden/my-personal-website/index.md","filePath":"garden/my-personal-website/index.md"}'),s={name:"garden/my-personal-website/index.md"},o=r('

My Personal Website ​

Referenced by: The Small Web

A Personal Websites for myself, available at https://thepaperpilot.org

',3),n=[o];function l(i,p,_,d,c,b){return t(),a("div",null,n)}const f=e(s,[["render",l]]);export{m as __pageData,f as default}; diff --git a/assets/garden_my-personal-website_index.md.DwfKlijC.lean.js b/assets/garden_my-personal-website_index.md.DwfKlijC.lean.js deleted file mode 100644 index 8ea40bef..00000000 --- a/assets/garden_my-personal-website_index.md.DwfKlijC.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as r}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"My Personal Website","description":"","frontmatter":{"public":"true","slug":"my-personal-website","title":"My Personal Website","prev":false,"next":false},"headers":[],"relativePath":"garden/my-personal-website/index.md","filePath":"garden/my-personal-website/index.md"}'),s={name:"garden/my-personal-website/index.md"},o=r("",3),n=[o];function l(i,p,_,d,c,b){return t(),a("div",null,n)}const f=e(s,[["render",l]]);export{m as __pageData,f as default}; diff --git a/assets/garden_my-projects_index.md.Cznm6ckc.js b/assets/garden_my-projects_index.md.Cznm6ckc.js deleted file mode 100644 index 1fc56fd3..00000000 --- a/assets/garden_my-projects_index.md.Cznm6ckc.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as t}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"My Projects","description":"","frontmatter":{"index":"true","public":"true","slug":"my-projects","title":"My Projects","prev":false,"next":false},"headers":[],"relativePath":"garden/my-projects/index.md","filePath":"garden/my-projects/index.md"}'),n={name:"garden/my-projects/index.md"},o=t('

My Projects ​

Tagged by: Advent Incremental, Babble Buds, Capture the Citadel, Dice Armor, Game Dev Tree, Incremental Social, Kronos, Opti-Speech, Planar Pioneers, Profectus, V-ecs

I like making games and tools!

Games ​

Tools (and other non-games) ​

',7),l=[o];function i(s,d,c,h,p,g){return r(),a("div",null,l)}const u=e(n,[["render",i]]);export{f as __pageData,u as default}; diff --git a/assets/garden_my-projects_index.md.Cznm6ckc.lean.js b/assets/garden_my-projects_index.md.Cznm6ckc.lean.js deleted file mode 100644 index 3721c737..00000000 --- a/assets/garden_my-projects_index.md.Cznm6ckc.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as t}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"My Projects","description":"","frontmatter":{"index":"true","public":"true","slug":"my-projects","title":"My Projects","prev":false,"next":false},"headers":[],"relativePath":"garden/my-projects/index.md","filePath":"garden/my-projects/index.md"}'),n={name:"garden/my-projects/index.md"},o=t("",7),l=[o];function i(s,d,c,h,p,g){return r(),a("div",null,l)}const u=e(n,[["render",i]]);export{f as __pageData,u as default}; diff --git a/assets/garden_nostr_index.md.CgleUUbP.js b/assets/garden_nostr_index.md.CgleUUbP.js deleted file mode 100644 index 3a5df30a..00000000 --- a/assets/garden_nostr_index.md.CgleUUbP.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as r,a5 as a}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Nostr","description":"","frontmatter":{"public":"true","slug":"nostr","tags":["Decentralized"],"title":"Nostr","prev":false,"next":false},"headers":[],"relativePath":"garden/nostr/index.md","filePath":"garden/nostr/index.md"}'),o={name:"garden/nostr/index.md"},n=a('

Nostr ​

Referenced by: Fediverse

Tags: Decentralized

Nostr is a protocol for Federated Social Media

',4),s=[n];function d(c,i,l,_,p,f){return r(),t("div",null,s)}const g=e(o,[["render",d]]);export{u as __pageData,g as default}; diff --git a/assets/garden_nostr_index.md.CgleUUbP.lean.js b/assets/garden_nostr_index.md.CgleUUbP.lean.js deleted file mode 100644 index f708a260..00000000 --- a/assets/garden_nostr_index.md.CgleUUbP.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as r,a5 as a}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Nostr","description":"","frontmatter":{"public":"true","slug":"nostr","tags":["Decentralized"],"title":"Nostr","prev":false,"next":false},"headers":[],"relativePath":"garden/nostr/index.md","filePath":"garden/nostr/index.md"}'),o={name:"garden/nostr/index.md"},n=a("",4),s=[n];function d(c,i,l,_,p,f){return r(),t("div",null,s)}const g=e(o,[["render",d]]);export{u as __pageData,g as default}; diff --git a/assets/garden_open-source_index.md.CrbIsKOD.js b/assets/garden_open-source_index.md.CrbIsKOD.js deleted file mode 100644 index 61ff6566..00000000 --- a/assets/garden_open-source_index.md.CrbIsKOD.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as n}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Open Source","description":"","frontmatter":{"public":"true","slug":"open-source","title":"Open Source","prev":false,"next":false},"headers":[],"relativePath":"garden/open-source/index.md","filePath":"garden/open-source/index.md"}'),o={name:"garden/open-source/index.md"},t=n('

Open Source ​

Referenced by: Advent Incremental, Cinny, Commune, Dice Armor, Forgejo, Game Dev Tree, Logseq, Mbin, Planar Pioneers, Profectus, Synapse, Vitepress, Weird

Projects with the source code publicly accessible

Typically also grants users the right to modify the code and redistribute those changes, depending on the license

',4),s=[t];function c(d,i,p,h,l,u){return r(),a("div",null,s)}const _=e(o,[["render",c]]);export{g as __pageData,_ as default}; diff --git a/assets/garden_open-source_index.md.CrbIsKOD.lean.js b/assets/garden_open-source_index.md.CrbIsKOD.lean.js deleted file mode 100644 index 6c1747ca..00000000 --- a/assets/garden_open-source_index.md.CrbIsKOD.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as n}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Open Source","description":"","frontmatter":{"public":"true","slug":"open-source","title":"Open Source","prev":false,"next":false},"headers":[],"relativePath":"garden/open-source/index.md","filePath":"garden/open-source/index.md"}'),o={name:"garden/open-source/index.md"},t=n("",4),s=[t];function c(d,i,p,h,l,u){return r(),a("div",null,s)}const _=e(o,[["render",c]]);export{g as __pageData,_ as default}; diff --git a/assets/garden_opti-speech_index.md.fV3laAf8.js b/assets/garden_opti-speech_index.md.fV3laAf8.js deleted file mode 100644 index 9dfe4ca0..00000000 --- a/assets/garden_opti-speech_index.md.fV3laAf8.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as a,c as r,o as i,a5 as t,j as e,ai as o,aj as s,ak as n,al as p}from"./chunks/framework.CK8QU5WH.js";const j=JSON.parse('{"title":"Opti-Speech","description":"","frontmatter":{"public":"true","slug":"opti-speech","tags":["My Projects"],"title":"Opti-Speech","prev":false,"next":false},"headers":[],"relativePath":"garden/opti-speech/index.md","filePath":"garden/opti-speech/index.md"}'),l={name:"garden/opti-speech/index.md"},c=t('

Opti-Speech ​

Tags: My Projects

In college I continued development on the Opti-Speech project, originally built alongside the scientific paper Opti-speech: a real-time, 3d visual feedback system for speech training

The Original Project ​

The Optispeech project involves designing and testing a real-time tongue model that can be viewed in a transparent head while a subject talks — for the purposes of treating speech errors and teaching foreign language sounds. This work has been conducted in partnership with Vulintus and with support from the National Institutes of Health (NIH).

system-architecture-600.jpg

',6),h=e("iframe",{width:"560",height:"315",src:"https://www.youtube.com/embed/9uHqIRs7ZjM",frameborder:"0",allow:"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture",allowfullscreen:"",style:{display:"block",margin:"auto"}},null,-1),d=e("p",null,"This video shows a talker with WAVE sensors placed on the tongue hitting a virtual target sphere located at the alveolar ridge. When an alveolar consonant is hit (e.g., /s/, /n/, /d/) the sphere changes color from red to green.",-1),m=e("iframe",{width:"560",height:"315",src:"https://www.youtube.com/embed/Oz42mKvlzqI",frameborder:"0",allow:"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture",allowfullscreen:"",style:{display:"block",margin:"auto"}},null,-1),u=t('

This video shows an American talker learning a novel sound not found in English. When the post-alveolar consonant is hit, the target sphere changes color from red to green. Here, the NDI WAVE system serves as input.

My Work ​

As the sole programmer at UT Dallas Speech Production Lab at the time, my changes involved updating to a more modern version of Unity, improving the interface, in general cleaning up tech debt so it can more easily support new features, and added support for additional EMA systems, namely the Carstens AG501.

new-interface.png

In addition, the program now includes documentation and unit tests to improve program stability and maintainability going forward.

documentation.png

unittests.png

',7),_=[c,h,d,m,u];function g(f,b,y,w,v,k){return i(),r("div",null,_)}const P=a(l,[["render",g]]);export{j as __pageData,P as default}; diff --git a/assets/garden_opti-speech_index.md.fV3laAf8.lean.js b/assets/garden_opti-speech_index.md.fV3laAf8.lean.js deleted file mode 100644 index 26ac16a3..00000000 --- a/assets/garden_opti-speech_index.md.fV3laAf8.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as a,c as r,o as i,a5 as t,j as e,ai as o,aj as s,ak as n,al as p}from"./chunks/framework.CK8QU5WH.js";const j=JSON.parse('{"title":"Opti-Speech","description":"","frontmatter":{"public":"true","slug":"opti-speech","tags":["My Projects"],"title":"Opti-Speech","prev":false,"next":false},"headers":[],"relativePath":"garden/opti-speech/index.md","filePath":"garden/opti-speech/index.md"}'),l={name:"garden/opti-speech/index.md"},c=t("",6),h=e("iframe",{width:"560",height:"315",src:"https://www.youtube.com/embed/9uHqIRs7ZjM",frameborder:"0",allow:"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture",allowfullscreen:"",style:{display:"block",margin:"auto"}},null,-1),d=e("p",null,"This video shows a talker with WAVE sensors placed on the tongue hitting a virtual target sphere located at the alveolar ridge. When an alveolar consonant is hit (e.g., /s/, /n/, /d/) the sphere changes color from red to green.",-1),m=e("iframe",{width:"560",height:"315",src:"https://www.youtube.com/embed/Oz42mKvlzqI",frameborder:"0",allow:"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture",allowfullscreen:"",style:{display:"block",margin:"auto"}},null,-1),u=t("",7),_=[c,h,d,m,u];function g(f,b,y,w,v,k){return i(),r("div",null,_)}const P=a(l,[["render",g]]);export{j as __pageData,P as default}; diff --git a/assets/garden_planar-pioneers_index.md.C66vsCjv.js b/assets/garden_planar-pioneers_index.md.C66vsCjv.js deleted file mode 100644 index 56ba1cb8..00000000 --- a/assets/garden_planar-pioneers_index.md.C66vsCjv.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as t}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Planar Pioneers","description":"","frontmatter":{"public":"true","slug":"planar-pioneers","tags":["My Projects","Profectus"],"title":"Planar Pioneers","prev":false,"next":false},"headers":[],"relativePath":"garden/planar-pioneers/index.md","filePath":"garden/planar-pioneers/index.md"}'),o={name:"garden/planar-pioneers/index.md"},n=t('

Planar Pioneers ​

Tags: My Projects, Profectus

Play it here!

An Open Source game designed to show off Profectus' dynamic layer system!

The TV Tropes page on this game mentions some of the cool things about this game

',5),s=[n];function p(i,l,c,d,_,h){return r(),a("div",null,s)}const m=e(o,[["render",p]]);export{g as __pageData,m as default}; diff --git a/assets/garden_planar-pioneers_index.md.C66vsCjv.lean.js b/assets/garden_planar-pioneers_index.md.C66vsCjv.lean.js deleted file mode 100644 index 122d5b55..00000000 --- a/assets/garden_planar-pioneers_index.md.C66vsCjv.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as t}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Planar Pioneers","description":"","frontmatter":{"public":"true","slug":"planar-pioneers","tags":["My Projects","Profectus"],"title":"Planar Pioneers","prev":false,"next":false},"headers":[],"relativePath":"garden/planar-pioneers/index.md","filePath":"garden/planar-pioneers/index.md"}'),o={name:"garden/planar-pioneers/index.md"},n=t("",5),s=[n];function p(i,l,c,d,_,h){return r(),a("div",null,s)}const m=e(o,[["render",p]]);export{g as __pageData,m as default}; diff --git a/assets/garden_pre-order-bonuses_index.md.C0-qMrbr.js b/assets/garden_pre-order-bonuses_index.md.C0-qMrbr.js deleted file mode 100644 index f2e70e3a..00000000 --- a/assets/garden_pre-order-bonuses_index.md.C0-qMrbr.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as o,o as i,a5 as r}from"./chunks/framework.CK8QU5WH.js";const _=JSON.parse('{"title":"Pre-Order Bonuses","description":"","frontmatter":{"public":"true","slug":"pre-order-bonuses","title":"Pre-Order Bonuses","prev":false,"next":false},"headers":[],"relativePath":"garden/pre-order-bonuses/index.md","filePath":"garden/pre-order-bonuses/index.md"}'),s={name:"garden/pre-order-bonuses/index.md"},l=r('

Pre-Order Bonuses ​

Referenced by: Video Game Monetization

Pre-order bonuses are benefits given to players who buy a game before it comes out

They primarily serve to benefit the company

  • People commit to buying before the embargo date passes
  • Heuristic of how well it'll sell after launch
  • Slight lead on return on investment
    • More significantly impacts indie studios, who will likely have less cash on hand
  • Companies make deals with storefronts to have exclusive bonuses, to drive customers to said storefronts

Common bonuses:

  • Digital goods:
  • Physical goods:
    • Typically pins, keychains, etc.
    • Typically only included in physical editions of the game
',7),t=[l];function a(n,d,u,c,p,m){return i(),o("div",null,t)}const f=e(s,[["render",a]]);export{_ as __pageData,f as default}; diff --git a/assets/garden_pre-order-bonuses_index.md.C0-qMrbr.lean.js b/assets/garden_pre-order-bonuses_index.md.C0-qMrbr.lean.js deleted file mode 100644 index ac001c0b..00000000 --- a/assets/garden_pre-order-bonuses_index.md.C0-qMrbr.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as o,o as i,a5 as r}from"./chunks/framework.CK8QU5WH.js";const _=JSON.parse('{"title":"Pre-Order Bonuses","description":"","frontmatter":{"public":"true","slug":"pre-order-bonuses","title":"Pre-Order Bonuses","prev":false,"next":false},"headers":[],"relativePath":"garden/pre-order-bonuses/index.md","filePath":"garden/pre-order-bonuses/index.md"}'),s={name:"garden/pre-order-bonuses/index.md"},l=r("",7),t=[l];function a(n,d,u,c,p,m){return i(),o("div",null,t)}const f=e(s,[["render",a]]);export{_ as __pageData,f as default}; diff --git a/assets/garden_premium-currency_index.md.CYRzDOj_.js b/assets/garden_premium-currency_index.md.CYRzDOj_.js deleted file mode 100644 index 6498043d..00000000 --- a/assets/garden_premium-currency_index.md.CYRzDOj_.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as r,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Premium Currency","description":"","frontmatter":{"public":"true","slug":"premium-currency","title":"Premium Currency","prev":false,"next":false},"headers":[],"relativePath":"garden/premium-currency/index.md","filePath":"garden/premium-currency/index.md"}'),n={name:"garden/premium-currency/index.md"},t=i('

Premium Currency ​

Referenced by: Pre-Order Bonuses

A popular form of MTX where instead of receiving a useful item or effect directly, you receive a currency that is then spent on an in game store

Reasons companies use them

  • Abstracts the real world price of items
    • No strict conversion ratio
    • Discounts for bulk purchasing
    • Small amounts given for free based on story progression or watching ads
  • Consolidates smaller purchases into a larger one (decreasing friction of individual purchases)
',5),o=[t];function s(c,u,l,m,d,p){return a(),r("div",null,o)}const h=e(n,[["render",s]]);export{f as __pageData,h as default}; diff --git a/assets/garden_premium-currency_index.md.CYRzDOj_.lean.js b/assets/garden_premium-currency_index.md.CYRzDOj_.lean.js deleted file mode 100644 index cd93b47c..00000000 --- a/assets/garden_premium-currency_index.md.CYRzDOj_.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as r,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Premium Currency","description":"","frontmatter":{"public":"true","slug":"premium-currency","title":"Premium Currency","prev":false,"next":false},"headers":[],"relativePath":"garden/premium-currency/index.md","filePath":"garden/premium-currency/index.md"}'),n={name:"garden/premium-currency/index.md"},t=i("",5),o=[t];function s(c,u,l,m,d,p){return a(),r("div",null,o)}const h=e(n,[["render",s]]);export{f as __pageData,h as default}; diff --git a/assets/garden_profectus_index.md.ykiRoiHE.js b/assets/garden_profectus_index.md.ykiRoiHE.js deleted file mode 100644 index a38ed468..00000000 --- a/assets/garden_profectus_index.md.ykiRoiHE.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as t}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Profectus","description":"","frontmatter":{"public":"true","slug":"profectus","tags":["My Projects"],"title":"Profectus","prev":false,"next":false},"headers":[],"relativePath":"garden/profectus/index.md","filePath":"garden/profectus/index.md"}'),o={name:"garden/profectus/index.md"},n=t('

Profectus ​

Referenced by: Advent Incremental, Planar Pioneers

Tagged by: Advent Incremental, Kronos, Planar Pioneers

Tags: My Projects

Profectus is an Open Source game engine I made, loosely based on The Modding Tree by Acamaeda

Technically it's more of a template for making web games

It centers around using Vue's reactivity and is designed with the intent to not restrain developers into making games that only look or behave "one way"

Games made with Profectus:

  • Everything in this garden tagged with this page!
  • The entries to the Profectus Creation Jam
  • Primordia by Jacorb
',9),s=[n];function i(c,l,d,p,f,u){return r(),a("div",null,s)}const m=e(o,[["render",i]]);export{g as __pageData,m as default}; diff --git a/assets/garden_profectus_index.md.ykiRoiHE.lean.js b/assets/garden_profectus_index.md.ykiRoiHE.lean.js deleted file mode 100644 index 7b3a9412..00000000 --- a/assets/garden_profectus_index.md.ykiRoiHE.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as t}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Profectus","description":"","frontmatter":{"public":"true","slug":"profectus","tags":["My Projects"],"title":"Profectus","prev":false,"next":false},"headers":[],"relativePath":"garden/profectus/index.md","filePath":"garden/profectus/index.md"}'),o={name:"garden/profectus/index.md"},n=t("",9),s=[n];function i(c,l,d,p,f,u){return r(),a("div",null,s)}const m=e(o,[["render",i]]);export{g as __pageData,m as default}; diff --git a/assets/garden_social-media_index.md.BbHjayFv.js b/assets/garden_social-media_index.md.BbHjayFv.js deleted file mode 100644 index 5f4bbc0f..00000000 --- a/assets/garden_social-media_index.md.BbHjayFv.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as i,a5 as t}from"./chunks/framework.CK8QU5WH.js";const _=JSON.parse('{"title":"Social Media","description":"","frontmatter":{"alias":"Social Web","public":"true","slug":"social-media","title":"Social Media","prev":false,"next":false},"headers":[],"relativePath":"garden/social-media/index.md","filePath":"garden/social-media/index.md"}'),o={name:"garden/social-media/index.md"},l=t('

Social Media ​

Referenced by: Commune, Fediverse

Traditional social media

  • Not Decentralized
    • Can't choose your own rules, sorting methods, data queries, etc.
  • Overrun by scams and ads and influencers

Federated Social Media

  • Partially Decentralized
    • Self hosting is too hard for everyone to do
    • Still subject to instance's moderation, limitations, etc.
  • Users need to pick an instance, associating their identity with one specific group
    • People belong to many groups
    • The person is permanently associated with that one group
    • You have to pick before getting a "trial period" to ensure you actually like that group/instance

My take on an ideal social media Fedi v2

',7),n=[l];function r(d,s,c,u,p,h){return i(),a("div",null,n)}const f=e(o,[["render",r]]);export{_ as __pageData,f as default}; diff --git a/assets/garden_social-media_index.md.BbHjayFv.lean.js b/assets/garden_social-media_index.md.BbHjayFv.lean.js deleted file mode 100644 index 8b5826b8..00000000 --- a/assets/garden_social-media_index.md.BbHjayFv.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as i,a5 as t}from"./chunks/framework.CK8QU5WH.js";const _=JSON.parse('{"title":"Social Media","description":"","frontmatter":{"alias":"Social Web","public":"true","slug":"social-media","title":"Social Media","prev":false,"next":false},"headers":[],"relativePath":"garden/social-media/index.md","filePath":"garden/social-media/index.md"}'),o={name:"garden/social-media/index.md"},l=t("",7),n=[l];function r(d,s,c,u,p,h){return i(),a("div",null,n)}const f=e(o,[["render",r]]);export{_ as __pageData,f as default}; diff --git a/assets/garden_synapse_index.md.C51ajr4V.js b/assets/garden_synapse_index.md.C51ajr4V.js deleted file mode 100644 index a38c43a6..00000000 --- a/assets/garden_synapse_index.md.C51ajr4V.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as n,a5 as t}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Synapse","description":"","frontmatter":{"public":"true","slug":"synapse","title":"Synapse","prev":false,"next":false},"headers":[],"relativePath":"garden/synapse/index.md","filePath":"garden/synapse/index.md"}'),r={name:"garden/synapse/index.md"},s=t('

Synapse ​

Referenced by: Incremental Social

Synapse is an Open Source server software for the Matrix protocol

',3),o=[s];function c(p,i,l,_,d,f){return n(),a("div",null,o)}const u=e(r,[["render",c]]);export{m as __pageData,u as default}; diff --git a/assets/garden_synapse_index.md.C51ajr4V.lean.js b/assets/garden_synapse_index.md.C51ajr4V.lean.js deleted file mode 100644 index d82da9fd..00000000 --- a/assets/garden_synapse_index.md.C51ajr4V.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as n,a5 as t}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Synapse","description":"","frontmatter":{"public":"true","slug":"synapse","title":"Synapse","prev":false,"next":false},"headers":[],"relativePath":"garden/synapse/index.md","filePath":"garden/synapse/index.md"}'),r={name:"garden/synapse/index.md"},s=t("",3),o=[s];function c(p,i,l,_,d,f){return n(),a("div",null,o)}const u=e(r,[["render",c]]);export{m as __pageData,u as default}; diff --git a/assets/garden_the-beginner-s-guide_index.md.BdmIJg3j.js b/assets/garden_the-beginner-s-guide_index.md.BdmIJg3j.js deleted file mode 100644 index a95fdb17..00000000 --- a/assets/garden_the-beginner-s-guide_index.md.BdmIJg3j.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as n}from"./chunks/framework.CK8QU5WH.js";const _=JSON.parse(`{"title":"The Beginner's Guide","description":"","frontmatter":{"public":"true","slug":"the-beginner-s-guide","tags":["Davey Wreden"],"title":"The Beginner's Guide","prev":false,"next":false},"headers":[],"relativePath":"garden/the-beginner-s-guide/index.md","filePath":"garden/the-beginner-s-guide/index.md"}`),t={name:"garden/the-beginner-s-guide/index.md"},i=n('

The Beginner's Guide ​

Tags: Davey Wreden

My favorite video game of all time, bar none. Created by Davey Wreden

The game broadly comments on the relationship between creators and consumers, and it can apply to all forms of art

  • Perhaps also an important commentary on parasocial relationships

Important analyses:

',7),o=[i];function s(l,d,h,u,c,g){return r(),a("div",null,o)}const f=e(t,[["render",s]]);export{_ as __pageData,f as default}; diff --git a/assets/garden_the-beginner-s-guide_index.md.BdmIJg3j.lean.js b/assets/garden_the-beginner-s-guide_index.md.BdmIJg3j.lean.js deleted file mode 100644 index c6887827..00000000 --- a/assets/garden_the-beginner-s-guide_index.md.BdmIJg3j.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as r,a5 as n}from"./chunks/framework.CK8QU5WH.js";const _=JSON.parse(`{"title":"The Beginner's Guide","description":"","frontmatter":{"public":"true","slug":"the-beginner-s-guide","tags":["Davey Wreden"],"title":"The Beginner's Guide","prev":false,"next":false},"headers":[],"relativePath":"garden/the-beginner-s-guide/index.md","filePath":"garden/the-beginner-s-guide/index.md"}`),t={name:"garden/the-beginner-s-guide/index.md"},i=n("",7),o=[i];function s(l,d,h,u,c,g){return r(),a("div",null,o)}const f=e(t,[["render",s]]);export{_ as __pageData,f as default}; diff --git a/assets/garden_the-cozy-web_index.md.BEzt5FqQ.js b/assets/garden_the-cozy-web_index.md.BEzt5FqQ.js deleted file mode 100644 index 17f752f8..00000000 --- a/assets/garden_the-cozy-web_index.md.BEzt5FqQ.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as o}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"The Cozy Web","description":"","frontmatter":{"public":"true","slug":"the-cozy-web","title":"The Cozy Web","prev":false,"next":false},"headers":[],"relativePath":"garden/the-cozy-web/index.md","filePath":"garden/the-cozy-web/index.md"}'),r={name:"garden/the-cozy-web/index.md"},n=o('

The Cozy Web ​

Referenced by: Digital Gardens, The Small Web

The Cozy Web is an extension of the dark forest theory of the Internet

It refers to the part of the web that is not web indexable

This part of the web is known for not typically having ads or marketers

Popularized by this article written by Maggie Appleton, who has also written a lot about Digital Gardens

',6),i=[n];function s(h,l,d,c,p,b){return a(),t("div",null,i)}const g=e(r,[["render",s]]);export{f as __pageData,g as default}; diff --git a/assets/garden_the-cozy-web_index.md.BEzt5FqQ.lean.js b/assets/garden_the-cozy-web_index.md.BEzt5FqQ.lean.js deleted file mode 100644 index 3e742de2..00000000 --- a/assets/garden_the-cozy-web_index.md.BEzt5FqQ.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as o}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"The Cozy Web","description":"","frontmatter":{"public":"true","slug":"the-cozy-web","title":"The Cozy Web","prev":false,"next":false},"headers":[],"relativePath":"garden/the-cozy-web/index.md","filePath":"garden/the-cozy-web/index.md"}'),r={name:"garden/the-cozy-web/index.md"},n=o("",6),i=[n];function s(h,l,d,c,p,b){return a(),t("div",null,i)}const g=e(r,[["render",s]]);export{f as __pageData,g as default}; diff --git a/assets/garden_the-indieweb_amplification_index.md.DT2TYsGY.js b/assets/garden_the-indieweb_amplification_index.md.DT2TYsGY.js deleted file mode 100644 index 3b903966..00000000 --- a/assets/garden_the-indieweb_amplification_index.md.DT2TYsGY.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as t,c as n,o as a,j as e,a as i}from"./chunks/framework.CK8QU5WH.js";const w=JSON.parse('{"title":"The IndieWeb/Amplification","description":"","frontmatter":{"public":"true","slug":"the-indieweb/amplification","title":"The IndieWeb/Amplification","prev":false,"next":false},"headers":[],"relativePath":"garden/the-indieweb/amplification/index.md","filePath":"garden/the-indieweb/amplification/index.md"}'),s={name:"garden/the-indieweb/amplification/index.md"},o=e("h1",{id:"the-indieweb-amplification",tabindex:"-1"},[i("The IndieWeb/Amplification "),e("a",{class:"header-anchor",href:"#the-indieweb-amplification","aria-label":'Permalink to "The IndieWeb/Amplification"'},"​")],-1),r=e("p",null,"Refers to reblogging (and re-hosting, sometimes) of someone else's content on your own site",-1),d=e("p",null,[e("a",{href:"https://aramzs.xyz/essays/the-internet-is-a-series-of-webs/",target:"_blank",rel:"noreferrer"},"The Internet is a series of webs"),i(" discusses some ideas and best practices for amplification")],-1),c=e("p",null,[i("To ensure the rehosted content actually came from the claimed author and was not tampered with, all content should be signed using "),e("a",{href:"/garden/the-indieweb/signature-blocks/"},"The IndieWeb/Signature Blocks")],-1),l=[o,r,d,c];function h(f,m,p,b,_,u){return a(),n("div",null,l)}const x=t(s,[["render",h]]);export{w as __pageData,x as default}; diff --git a/assets/garden_the-indieweb_amplification_index.md.DT2TYsGY.lean.js b/assets/garden_the-indieweb_amplification_index.md.DT2TYsGY.lean.js deleted file mode 100644 index 3b903966..00000000 --- a/assets/garden_the-indieweb_amplification_index.md.DT2TYsGY.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as t,c as n,o as a,j as e,a as i}from"./chunks/framework.CK8QU5WH.js";const w=JSON.parse('{"title":"The IndieWeb/Amplification","description":"","frontmatter":{"public":"true","slug":"the-indieweb/amplification","title":"The IndieWeb/Amplification","prev":false,"next":false},"headers":[],"relativePath":"garden/the-indieweb/amplification/index.md","filePath":"garden/the-indieweb/amplification/index.md"}'),s={name:"garden/the-indieweb/amplification/index.md"},o=e("h1",{id:"the-indieweb-amplification",tabindex:"-1"},[i("The IndieWeb/Amplification "),e("a",{class:"header-anchor",href:"#the-indieweb-amplification","aria-label":'Permalink to "The IndieWeb/Amplification"'},"​")],-1),r=e("p",null,"Refers to reblogging (and re-hosting, sometimes) of someone else's content on your own site",-1),d=e("p",null,[e("a",{href:"https://aramzs.xyz/essays/the-internet-is-a-series-of-webs/",target:"_blank",rel:"noreferrer"},"The Internet is a series of webs"),i(" discusses some ideas and best practices for amplification")],-1),c=e("p",null,[i("To ensure the rehosted content actually came from the claimed author and was not tampered with, all content should be signed using "),e("a",{href:"/garden/the-indieweb/signature-blocks/"},"The IndieWeb/Signature Blocks")],-1),l=[o,r,d,c];function h(f,m,p,b,_,u){return a(),n("div",null,l)}const x=t(s,[["render",h]]);export{w as __pageData,x as default}; diff --git a/assets/garden_the-indieweb_signature-blocks_index.md.BSUq9f2h.js b/assets/garden_the-indieweb_signature-blocks_index.md.BSUq9f2h.js deleted file mode 100644 index 403634a8..00000000 --- a/assets/garden_the-indieweb_signature-blocks_index.md.BSUq9f2h.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as n,c as a,o as i,j as e,a as t}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"The IndieWeb/Signature Blocks","description":"","frontmatter":{"public":"true","slug":"the-indieweb/signature-blocks","title":"The IndieWeb/Signature Blocks","prev":false,"next":false},"headers":[],"relativePath":"garden/the-indieweb/signature-blocks/index.md","filePath":"garden/the-indieweb/signature-blocks/index.md"}'),s={name:"garden/the-indieweb/signature-blocks/index.md"},r=e("h1",{id:"the-indieweb-signature-blocks",tabindex:"-1"},[t("The IndieWeb/Signature Blocks "),e("a",{class:"header-anchor",href:"#the-indieweb-signature-blocks","aria-label":'Permalink to "The IndieWeb/Signature Blocks"'},"​")],-1),o=e("p",null,[t("A proposal I want to write for posting signed content on your "),e("a",{href:"/garden/the-small-web/"},"IndieWeb"),t(" website")],-1),d=[r,o];function c(l,h,b,u,g,p){return i(),a("div",null,d)}const k=n(s,[["render",c]]);export{f as __pageData,k as default}; diff --git a/assets/garden_the-indieweb_signature-blocks_index.md.BSUq9f2h.lean.js b/assets/garden_the-indieweb_signature-blocks_index.md.BSUq9f2h.lean.js deleted file mode 100644 index 403634a8..00000000 --- a/assets/garden_the-indieweb_signature-blocks_index.md.BSUq9f2h.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as n,c as a,o as i,j as e,a as t}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"The IndieWeb/Signature Blocks","description":"","frontmatter":{"public":"true","slug":"the-indieweb/signature-blocks","title":"The IndieWeb/Signature Blocks","prev":false,"next":false},"headers":[],"relativePath":"garden/the-indieweb/signature-blocks/index.md","filePath":"garden/the-indieweb/signature-blocks/index.md"}'),s={name:"garden/the-indieweb/signature-blocks/index.md"},r=e("h1",{id:"the-indieweb-signature-blocks",tabindex:"-1"},[t("The IndieWeb/Signature Blocks "),e("a",{class:"header-anchor",href:"#the-indieweb-signature-blocks","aria-label":'Permalink to "The IndieWeb/Signature Blocks"'},"​")],-1),o=e("p",null,[t("A proposal I want to write for posting signed content on your "),e("a",{href:"/garden/the-small-web/"},"IndieWeb"),t(" website")],-1),d=[r,o];function c(l,h,b,u,g,p){return i(),a("div",null,d)}const k=n(s,[["render",c]]);export{f as __pageData,k as default}; diff --git a/assets/garden_the-small-web_index.md.DB8s7zLZ.js b/assets/garden_the-small-web_index.md.DB8s7zLZ.js deleted file mode 100644 index f63272c4..00000000 --- a/assets/garden_the-small-web_index.md.DB8s7zLZ.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as a,c as t,o as r,a5 as l,j as e}from"./chunks/framework.CK8QU5WH.js";const w=JSON.parse('{"title":"The Small Web","description":"","frontmatter":{"alias":"The IndieWeb, Personal Web, Personal Websites, IndieWeb","public":"true","slug":"the-small-web","title":"The Small Web","prev":false,"next":false},"headers":[],"relativePath":"garden/the-small-web/index.md","filePath":"garden/the-small-web/index.md"}'),i={name:"garden/the-small-web/index.md"},s=l('

The Small Web ​

Referenced by: /now, This Knowledge Hub

Small personal websites created by individuals

  • My Personal Website
  • A callback to how the web was before social media, which homogenized content
  • These pages are diverse and typically won't have ads or marketers

The small web as a whole is Freeform

  • Individual sites may be Chronological still
  • Individual sites link between each other in ways similar to wikis

Browsing the small web ​

  • Follow Webrings or other links from known small websites
  • Marginalia is a search engine for non-commercial content with a "random" button and filters for the small web explicitly (amongst other useful filters!)

Building personal websites ​

IndieWeb contains various resources

  • Their building blocks are standards people can use to help the small web connect with each other consistently
  • They discourage the use of site builders or templates that end up making sites look too homogenized

Free hosting for static websites:

Streams ​

Microsub is a proposed protocol to support this

  • That way, people could use microsub clients to subscribe to multiple streams and get them in one feed
  • Effectively a Federated Social Media that works through personal websites
  • Announce new posts using WebSub

This also allows your personal website to be the one source of truth for your posted content

Multiple streams can be hosted by one site/person so people can subscribe to the kind of content they're interested in

How viable would it be to include chat messages in a stream as well?

  • Perhaps with Chat Glue you could link to specific branches I chatted in

Digital Gardens ​

These sites may be useful to occasionally check up on rather than get notifications from on every post/change

  • Although Garden-RSS could allow those who want to receive notifications to do so

The future ​

The Internet is a series of webs talks about transitioning from our current consolidated web back to the indie web

Why people want the small web ​

There are tools these days that make making websites incredibly easy

  • Back in the day geocities was pretty complicated but a lot of people managed to make pages there
  • Neocities has an extensive page on Learn How to Make Websites!

Hosting can be expensive, but static websites are cheap

  • There are plenty of free options out there for hosting static websites
    • Ideally you'd use some sort of system that is easily transferrable to other servers, and possibly even supports nomadic identities
    • Free hosting for static websites:
    • People are creative and love creating things
',32),o=e("iframe",{width:"560",height:"315",src:"https://www.youtube.com/embed/00qwzmMrtok",title:"",frameBorder:"0",allowFullScreen:""},null,-1),n=e("iframe",{width:"560",height:"315",src:"https://www.youtube.com/embed/rTSEr0cRJY8",title:"",frameBorder:"0",allowFullScreen:""},null,-1),h=[s,o,n];function d(b,c,u,p,m,g){return r(),t("div",null,h)}const k=a(i,[["render",d]]);export{w as __pageData,k as default}; diff --git a/assets/garden_the-small-web_index.md.DB8s7zLZ.lean.js b/assets/garden_the-small-web_index.md.DB8s7zLZ.lean.js deleted file mode 100644 index af9fa36d..00000000 --- a/assets/garden_the-small-web_index.md.DB8s7zLZ.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as a,c as t,o as r,a5 as l,j as e}from"./chunks/framework.CK8QU5WH.js";const w=JSON.parse('{"title":"The Small Web","description":"","frontmatter":{"alias":"The IndieWeb, Personal Web, Personal Websites, IndieWeb","public":"true","slug":"the-small-web","title":"The Small Web","prev":false,"next":false},"headers":[],"relativePath":"garden/the-small-web/index.md","filePath":"garden/the-small-web/index.md"}'),i={name:"garden/the-small-web/index.md"},s=l("",32),o=e("iframe",{width:"560",height:"315",src:"https://www.youtube.com/embed/00qwzmMrtok",title:"",frameBorder:"0",allowFullScreen:""},null,-1),n=e("iframe",{width:"560",height:"315",src:"https://www.youtube.com/embed/rTSEr0cRJY8",title:"",frameBorder:"0",allowFullScreen:""},null,-1),h=[s,o,n];function d(b,c,u,p,m,g){return r(),t("div",null,h)}const k=a(i,[["render",d]]);export{w as __pageData,k as default}; diff --git a/assets/garden_this-knowledge-hub_index.md.CUdFhZdq.js b/assets/garden_this-knowledge-hub_index.md.CUdFhZdq.js deleted file mode 100644 index ba98ad58..00000000 --- a/assets/garden_this-knowledge-hub_index.md.CUdFhZdq.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as i}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"This Knowledge Hub","description":"","frontmatter":{"public":"true","slug":"this-knowledge-hub","title":"This Knowledge Hub","prev":false,"next":false},"headers":[],"relativePath":"garden/this-knowledge-hub/index.md","filePath":"garden/this-knowledge-hub/index.md"}'),n={name:"garden/this-knowledge-hub/index.md"},s=i('

This Knowledge Hub ​

Referenced by: Digital Gardens

This is my knowledge hub!

  • It's a Digital Garden collecting my thoughts in varying levels of completeness on basically anything I have interest in

This is not Wikipedia. My thoughts are biased and argumentative, but to the best of my ability based on fact and expertise

I'm writing on something essentially every day

  • Most of my pages are private, especially the journal pages
  • I'll only push updates to this site every so often (not an automatic process)
  • Until something like Garden-RSS exists, we'll have to make do with /changelog which gives a git diff summary for every pushed change, in the form of a The IndieWeb stream as well as an RSS feed

Written in Logseq and rendered with Vitepress

Suggested pages:

',10),l=[s];function r(o,d,h,g,p,u){return t(),a("div",null,l)}const b=e(n,[["render",r]]);export{f as __pageData,b as default}; diff --git a/assets/garden_this-knowledge-hub_index.md.CUdFhZdq.lean.js b/assets/garden_this-knowledge-hub_index.md.CUdFhZdq.lean.js deleted file mode 100644 index e021f5ba..00000000 --- a/assets/garden_this-knowledge-hub_index.md.CUdFhZdq.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as i}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"This Knowledge Hub","description":"","frontmatter":{"public":"true","slug":"this-knowledge-hub","title":"This Knowledge Hub","prev":false,"next":false},"headers":[],"relativePath":"garden/this-knowledge-hub/index.md","filePath":"garden/this-knowledge-hub/index.md"}'),n={name:"garden/this-knowledge-hub/index.md"},s=i("",10),l=[s];function r(o,d,h,g,p,u){return t(),a("div",null,l)}const b=e(n,[["render",r]]);export{f as __pageData,b as default}; diff --git a/assets/garden_v-ecs_index.md.DJKtb91L.js b/assets/garden_v-ecs_index.md.DJKtb91L.js deleted file mode 100644 index cbe72560..00000000 --- a/assets/garden_v-ecs_index.md.DJKtb91L.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as o,am as s,an as n,ao as r}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"V-ecs","description":"","frontmatter":{"public":"true","slug":"v-ecs","tags":["My Projects"],"title":"V-ecs","prev":false,"next":false},"headers":[],"relativePath":"garden/v-ecs/index.md","filePath":"garden/v-ecs/index.md"}'),l={name:"garden/v-ecs/index.md"},i=o('

V-ecs ​

Tags: My Projects

screenshot.png

V-ecs (pronounced "Vex") is a Vulkan-based engine I made for making highly moddable games and tools in Lua centered around the ECS design pattern and a work-stealing job system.

The engine works with "worlds", which are collections of systems and renderers. The engine comes with several worlds using systems and renderers I made, including a voxel world, an incremental game, and some test scenes. All of these include systems to render the fps as well as show a debug console by typing the grave key (`). The default world is a title screen that detects any worlds in the "worlds" folder and displays a button for each of them.

debug.png

The original plans were to eventually put it on the steam workshop so people could more easily share their creations amongst each other, but I never became happy enough with the performance of the engine - the parallelization of the lua code involved a lot of overhead that severely limited performance.

Instead, I made a couple of worlds by myself - an infinite procedurally generated voxel world, a simple incremental game, and a more complex incremental game I call "Sands of Time".

sandsoftime.png

The gameplay of Sands of Time was replicated in Kronos Chapter 2!

',10),d=[i];function c(p,h,m,g,u,f){return t(),a("div",null,d)}const v=e(l,[["render",c]]);export{y as __pageData,v as default}; diff --git a/assets/garden_v-ecs_index.md.DJKtb91L.lean.js b/assets/garden_v-ecs_index.md.DJKtb91L.lean.js deleted file mode 100644 index 88047eb8..00000000 --- a/assets/garden_v-ecs_index.md.DJKtb91L.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as o,am as s,an as n,ao as r}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"V-ecs","description":"","frontmatter":{"public":"true","slug":"v-ecs","tags":["My Projects"],"title":"V-ecs","prev":false,"next":false},"headers":[],"relativePath":"garden/v-ecs/index.md","filePath":"garden/v-ecs/index.md"}'),l={name:"garden/v-ecs/index.md"},i=o("",10),d=[i];function c(p,h,m,g,u,f){return t(),a("div",null,d)}const v=e(l,[["render",c]]);export{y as __pageData,v as default}; diff --git a/assets/garden_video-game-monetization_index.md.eY03jnxc.js b/assets/garden_video-game-monetization_index.md.eY03jnxc.js deleted file mode 100644 index 8ddd6c37..00000000 --- a/assets/garden_video-game-monetization_index.md.eY03jnxc.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as i,a5 as t}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Video Game Monetization","description":"","frontmatter":{"public":"true","slug":"video-game-monetization","title":"Video Game Monetization","prev":false,"next":false},"headers":[],"relativePath":"garden/video-game-monetization/index.md","filePath":"garden/video-game-monetization/index.md"}'),o={name:"garden/video-game-monetization/index.md"},n=t('

Video Game Monetization ​

Referenced by: Life is Strange

AAA games ​

Cost a lot of money to make, mostly due to the graphics arms race

The price required to make games that expensive earn the cost back would be much higher than the current price of AAA games

Graphics would not justify those higher prices, and AAA studios know this

Techniques AAA games use to make more money without raising the base price:

Free-to-play games ​

Typically utilize MTX and ads in order to profit

Indie developers ​

Trying to make a sustainable living is hard

The industry is packed with lots of competition

I don't blame them for their monetization

Ethical game monetization ​

Requirements:

  • Free demo
  • Paid base game
  • No MTX
  • Paid content expansions
',17),r=[n];function s(l,d,m,h,p,c){return i(),a("div",null,r)}const f=e(o,[["render",s]]);export{g as __pageData,f as default}; diff --git a/assets/garden_video-game-monetization_index.md.eY03jnxc.lean.js b/assets/garden_video-game-monetization_index.md.eY03jnxc.lean.js deleted file mode 100644 index e313618b..00000000 --- a/assets/garden_video-game-monetization_index.md.eY03jnxc.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as i,a5 as t}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Video Game Monetization","description":"","frontmatter":{"public":"true","slug":"video-game-monetization","title":"Video Game Monetization","prev":false,"next":false},"headers":[],"relativePath":"garden/video-game-monetization/index.md","filePath":"garden/video-game-monetization/index.md"}'),o={name:"garden/video-game-monetization/index.md"},n=t("",17),r=[n];function s(l,d,m,h,p,c){return i(),a("div",null,r)}const f=e(o,[["render",s]]);export{g as __pageData,f as default}; diff --git a/assets/garden_vitepress_index.md.CDGDOV5f.js b/assets/garden_vitepress_index.md.CDGDOV5f.js deleted file mode 100644 index cc0334e0..00000000 --- a/assets/garden_vitepress_index.md.CDGDOV5f.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as r,a5 as s}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Vitepress","description":"","frontmatter":{"public":"true","slug":"vitepress","title":"Vitepress","prev":false,"next":false},"headers":[],"relativePath":"garden/vitepress/index.md","filePath":"garden/vitepress/index.md"}'),a={name:"garden/vitepress/index.md"},i=s('

Vitepress ​

Referenced by: This Knowledge Hub

Vitepress is an Open Source static site generator

',3),n=[i];function o(p,d,c,_,l,h){return r(),t("div",null,n)}const g=e(a,[["render",o]]);export{u as __pageData,g as default}; diff --git a/assets/garden_vitepress_index.md.CDGDOV5f.lean.js b/assets/garden_vitepress_index.md.CDGDOV5f.lean.js deleted file mode 100644 index e5948ad9..00000000 --- a/assets/garden_vitepress_index.md.CDGDOV5f.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as r,a5 as s}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Vitepress","description":"","frontmatter":{"public":"true","slug":"vitepress","title":"Vitepress","prev":false,"next":false},"headers":[],"relativePath":"garden/vitepress/index.md","filePath":"garden/vitepress/index.md"}'),a={name:"garden/vitepress/index.md"},i=s("",3),n=[i];function o(p,d,c,_,l,h){return r(),t("div",null,n)}const g=e(a,[["render",o]]);export{u as __pageData,g as default}; diff --git a/assets/garden_wanderstop_index.md.BTJMeiHB.js b/assets/garden_wanderstop_index.md.BTJMeiHB.js deleted file mode 100644 index a88823da..00000000 --- a/assets/garden_wanderstop_index.md.BTJMeiHB.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as r}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Wanderstop","description":"","frontmatter":{"public":"true","slug":"wanderstop","tags":["Davey Wreden"],"title":"Wanderstop","prev":false,"next":false},"headers":[],"relativePath":"garden/wanderstop/index.md","filePath":"garden/wanderstop/index.md"}'),n={name:"garden/wanderstop/index.md"},o=r('

Wanderstop ​

Tags: Davey Wreden

Wanderstop is the first game by Ivy Road. It's a narrative focused cozy game

',3),s=[o];function d(p,_,c,i,l,f){return t(),a("div",null,s)}const g=e(n,[["render",d]]);export{m as __pageData,g as default}; diff --git a/assets/garden_wanderstop_index.md.BTJMeiHB.lean.js b/assets/garden_wanderstop_index.md.BTJMeiHB.lean.js deleted file mode 100644 index ed9b7340..00000000 --- a/assets/garden_wanderstop_index.md.BTJMeiHB.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as r}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Wanderstop","description":"","frontmatter":{"public":"true","slug":"wanderstop","tags":["Davey Wreden"],"title":"Wanderstop","prev":false,"next":false},"headers":[],"relativePath":"garden/wanderstop/index.md","filePath":"garden/wanderstop/index.md"}'),n={name:"garden/wanderstop/index.md"},o=r("",3),s=[o];function d(p,_,c,i,l,f){return t(),a("div",null,s)}const g=e(n,[["render",d]]);export{m as __pageData,g as default}; diff --git a/assets/garden_webrings_index.md.DVn_-9-u.js b/assets/garden_webrings_index.md.DVn_-9-u.js deleted file mode 100644 index 3026e990..00000000 --- a/assets/garden_webrings_index.md.DVn_-9-u.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as i,a5 as t}from"./chunks/framework.CK8QU5WH.js";const b=JSON.parse('{"title":"Webrings","description":"","frontmatter":{"public":"true","slug":"webrings","title":"Webrings","prev":false,"next":false},"headers":[],"relativePath":"garden/webrings/index.md","filePath":"garden/webrings/index.md"}'),l={name:"garden/webrings/index.md"},r=t('

Webrings ​

Referenced by: The Small Web

A collection of Personal Websites that link to each other

  • These websites are all endorsing each other
  • They form a network of related sites readers might be interested in
  • Built on human trust rather than algorithms

Commune has a vision for modern webrings

  • Have communities set up matrix spaces for chatting
  • Multiple spaces can contain the same room
  • Related communities can share a room about a relevant topic
    • e.g. a bunch of game development libraries shared a "Game Design" room
  • This allows smaller communities to grow from cross-pollinating with other related communities
  • Could Incremental Social host a shared "Incremental Games" room?
    • How to bridge one channel to multiple discord servers, since that's where most incremental games communities are
    • Would this be appealing to already large communities?
    • Would this be overwhelming to smaller communities?
    • Who would moderate?
',6),o=[r];function n(s,m,c,h,d,u){return i(),a("div",null,o)}const p=e(l,[["render",n]]);export{b as __pageData,p as default}; diff --git a/assets/garden_webrings_index.md.DVn_-9-u.lean.js b/assets/garden_webrings_index.md.DVn_-9-u.lean.js deleted file mode 100644 index 83a2e1f7..00000000 --- a/assets/garden_webrings_index.md.DVn_-9-u.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as i,a5 as t}from"./chunks/framework.CK8QU5WH.js";const b=JSON.parse('{"title":"Webrings","description":"","frontmatter":{"public":"true","slug":"webrings","title":"Webrings","prev":false,"next":false},"headers":[],"relativePath":"garden/webrings/index.md","filePath":"garden/webrings/index.md"}'),l={name:"garden/webrings/index.md"},r=t("",6),o=[r];function n(s,m,c,h,d,u){return i(),a("div",null,o)}const p=e(l,[["render",n]]);export{b as __pageData,p as default}; diff --git a/assets/garden_weird_index.md.5UcMgku5.js b/assets/garden_weird_index.md.5UcMgku5.js deleted file mode 100644 index 268628ea..00000000 --- a/assets/garden_weird_index.md.5UcMgku5.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as r,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Weird","description":"","frontmatter":{"public":"true","slug":"weird","title":"Weird","prev":false,"next":false},"headers":[],"relativePath":"garden/weird/index.md","filePath":"garden/weird/index.md"}'),t={name:"garden/weird/index.md"},n=i('

Weird ​

Referenced by: Commune, Fedi v2, The Small Web

Weird is an Open Source project by the Commune team currently in development

Aims to make creating Personal Websites with Federated Identity available to everyone

  • Also plans on having paid tiers for giving people access to single user instances of various Fediverse tools

Long term, Weird wants to build a new better fediverse

',7),o=[n];function s(d,l,c,h,f,p){return a(),r("div",null,o)}const _=e(t,[["render",s]]);export{m as __pageData,_ as default}; diff --git a/assets/garden_weird_index.md.5UcMgku5.lean.js b/assets/garden_weird_index.md.5UcMgku5.lean.js deleted file mode 100644 index 7e8f66b4..00000000 --- a/assets/garden_weird_index.md.5UcMgku5.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as r,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Weird","description":"","frontmatter":{"public":"true","slug":"weird","title":"Weird","prev":false,"next":false},"headers":[],"relativePath":"garden/weird/index.md","filePath":"garden/weird/index.md"}'),t={name:"garden/weird/index.md"},n=i("",7),o=[n];function s(d,l,c,h,f,p){return a(),r("div",null,o)}const _=e(t,[["render",s]]);export{m as __pageData,_ as default}; diff --git a/assets/guide-to-incrementals_design_criticism_index.md.DIKhcyDO.js b/assets/guide-to-incrementals_design_criticism_index.md.DIKhcyDO.js deleted file mode 100644 index 8d3a11d1..00000000 --- a/assets/guide-to-incrementals_design_criticism_index.md.DIKhcyDO.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Guide to Incrementals/Navigating Criticism","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/navigating-criticism","title":"Guide to Incrementals/Navigating Criticism","prev":false,"next":false},"headers":[],"relativePath":"guide-to-incrementals/design/criticism/index.md","filePath":"guide-to-incrementals/design/criticism/index.md"}'),n={name:"guide-to-incrementals/design/criticism/index.md"},o=i('

Guide to Incrementals/Navigating Criticism ​

Developing games is fun and exciting and teaches a lot of wonderful skills - I enthusiastically encourage anyone with an interest in game development to try it out - and incremental games are a wonderful way to get started. However, there are many challenges young and inexperienced developers have to face, and I think the hardest one - harder than coding, debugging, balancing, etc. - is handling criticism. When you put your heart and soul into a game it is natural to feel very vulnerable. While I think there's a lot communities can do to ensure they're welcoming, positive and constructive with their criticisms, inevitably you will eventually read some, and potentially a lot, of comments that can deeply affect you. No one is immune to this, from young incremental game developers to the largest content creators you can think of. That's why it's important to be able to process and navigate criticism, because ultimately collecting feedback is essential to the journey to becoming a better developer. On this page, we'll explore how to embrace criticism, grow from it, and continue to post your games publicly with confidence.

Reading Feedback ​

Game development is a skill that takes time and practice to get truly great at. Criticism and other constructive feedback are vital to continually improving. It's useful to look at the criticism as solely a tool for improving this game and future games - that is to say, it should never be used against you as a person. Insults towards the developer(s) themselves are never okay and should not be allowed within whatever community you're sharing your works in. If you do come across a comment you interpret as an attack upon your person, you should report it. For other negative comments, try not to internalize them; instead, focus on improving the game. By distancing your own identity from your work emotionally, you can better analyze the game and use the feedback to your advantage.

Not all feedback is made equal, and you don't need to feel compelled to read and obey every piece of feedback you receive. Learn to distinguish between constructive feedback and unhelpful comments. Constructive feedback typically offers specific suggestions for improvement, while unhelpful comments are often vague or hurtful. Prioritize the former and disregard the latter. That said, most feedback you get will not be from game developers, so take specific suggestions with a grain of salt. Determine the actual problem they're experiencing, and design what you believe the best solution to that problem would be, regardless if that's the specific solution the player asked for. And keep in mind, due to different player preferences you'll never satisfy everyone, and you don't need to. Ultimately if even just you find the game fun, then that's a success.

Seeking Feedback ​

When deciding where to share your game, consider the type of players you anticipate getting, and the kind of feedback you can anticipate receiving. Different communities will have different levels of support for learning developers, and certain communities may prefer certain types of games or mechanics. It's important to get a diverse set of feedback focused on players you think will enjoy the specific game you're making.

Collecting feedback from other game developers is incredibly helpful. They've trained themselves to recognize good and bad game design and how to articulate the differences, and from my experience are much more likely to leave positive and constructive comments since they've been in your shoes before! They understand the struggles and can offer guidance and emotional support.

Responding to Feedback ​

Negative feedback can naturally feel like an attack, and it's okay to get angry. However, lashing back is never the appropriate response. It's best to cool off IRL, and keep in mind all the positive comments you've received. There's a concept in Psychology called negative bias that explains how negative feedback tends to stick with us much more prominently than positive feedback, so it's useful to regularly remind yourself of all the positive feedback you've received. Celebrate your successes, no matter how small they may seem - getting a game to a state you can publicly share it with people is an accomplishment in and of itself!

Remember your passion and your initial reasons for getting into game development. The journey will have its ups and downs, but staying true to your vision and passion will keep you motivated.

',11),s=[o];function r(c,l,d,u,m,h){return a(),t("div",null,s)}const f=e(n,[["render",r]]);export{p as __pageData,f as default}; diff --git a/assets/guide-to-incrementals_design_criticism_index.md.DIKhcyDO.lean.js b/assets/guide-to-incrementals_design_criticism_index.md.DIKhcyDO.lean.js deleted file mode 100644 index 2c4546f3..00000000 --- a/assets/guide-to-incrementals_design_criticism_index.md.DIKhcyDO.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Guide to Incrementals/Navigating Criticism","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/navigating-criticism","title":"Guide to Incrementals/Navigating Criticism","prev":false,"next":false},"headers":[],"relativePath":"guide-to-incrementals/design/criticism/index.md","filePath":"guide-to-incrementals/design/criticism/index.md"}'),n={name:"guide-to-incrementals/design/criticism/index.md"},o=i("",11),s=[o];function r(c,l,d,u,m,h){return a(),t("div",null,s)}const f=e(n,[["render",r]]);export{p as __pageData,f as default}; diff --git a/assets/guide-to-incrementals_index.md.Q8NHkbU9.js b/assets/guide-to-incrementals_index.md.Q8NHkbU9.js deleted file mode 100644 index 8f3e9641..00000000 --- a/assets/guide-to-incrementals_index.md.Q8NHkbU9.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as n}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Guide to Incrementals","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals","title":"Guide to Incrementals","prev":false,"next":false},"headers":[],"relativePath":"guide-to-incrementals/index.md","filePath":"guide-to-incrementals/index.md"}'),i={name:"guide-to-incrementals/index.md"},o=n('

Guide to Incrementals ​

This is a comprehensive guide to Incremental Games, a genre of video games. It will explore defining the genre, why it's appealing, and how to design and build your own incremental game. Along the way will be interactive examples, snippets from other creators, and relevant material to contextualize everything.

Note: This is an incomplete document. I want to keep adding opinions and opposing views from other incremental games developers, and add interactive examples to illustrate various points regarding game design and balancing. Consider this a living document - and see the changelog at the end.

Note: This was made before my switch to a digital garden, and is written as prose. Hope you don't mind!

Why am I making this? ​

That's a good question! What authority do I have to be making this guide? I haven't made the best incremental games, nor the most incremental games, certainly not the most popular ones either. But I do have some formal education in game development, know a lot of incremental game devs (as well as other game devs), and have a passionate interest in ludology, classifying genres, etc. I've also made a couple of incremental games) myself.

If you have any additional questions about my credentials or anything on this site, feel free to reach out!

Ludology ​

Making an Incremental ​

',11),r=[o];function l(s,d,m,c,h,g){return t(),a("div",null,r)}const f=e(i,[["render",l]]);export{p as __pageData,f as default}; diff --git a/assets/guide-to-incrementals_index.md.Q8NHkbU9.lean.js b/assets/guide-to-incrementals_index.md.Q8NHkbU9.lean.js deleted file mode 100644 index c535a2bc..00000000 --- a/assets/guide-to-incrementals_index.md.Q8NHkbU9.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as n}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Guide to Incrementals","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals","title":"Guide to Incrementals","prev":false,"next":false},"headers":[],"relativePath":"guide-to-incrementals/index.md","filePath":"guide-to-incrementals/index.md"}'),i={name:"guide-to-incrementals/index.md"},o=n("",11),r=[o];function l(s,d,m,c,h,g){return t(),a("div",null,r)}const f=e(i,[["render",l]]);export{p as __pageData,f as default}; diff --git a/assets/guide-to-incrementals_ludology_appeal-developers_index.md.Cm_ScJQR.js b/assets/guide-to-incrementals_ludology_appeal-developers_index.md.Cm_ScJQR.js deleted file mode 100644 index 8aed6675..00000000 --- a/assets/guide-to-incrementals_ludology_appeal-developers_index.md.Cm_ScJQR.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as o}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Guide to Incrementals/Appeal to Developers","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/appeal-to-developers","title":"Guide to Incrementals/Appeal to Developers","prev":false,"next":false},"headers":[],"relativePath":"guide-to-incrementals/ludology/appeal-developers/index.md","filePath":"guide-to-incrementals/ludology/appeal-developers/index.md"}'),n={name:"guide-to-incrementals/ludology/appeal-developers/index.md"},i=o('

Guide to Incrementals/Appeal to Developers ​

There are a lot of developers in the incremental games community - the genre seems to draw them in, and convert a lot of players into developers. Let's explore the reasons why this genre appeals to developers.

Incrementals are Easy to Make ​

Compared to other genres, incrementals have quite low expectations. You don't need to make fancy art, or music, or lay things out nicely. If you can make a button and learn the few lines of code necessary to make a number go up, you can make an incremental. This low threshold makes the genre perfect for those who are actively learning to code and haven't developed any gamedev-related skills yet.

Additionally, unlike other genres incrementals are uniquely easy to implement in a normal web page - no need to worry about rendering sprites, moving them around, implementing physics, etc. New developers can just use HTML to add a button, and the game is now available in your browser. You don't need to choose an engine, have admin privileges, or hell for the dedicated you don't even need a computer - there are tools for web development that run in the browser itself, so you can technically use your phone if that's all you have.

Javascript is a perfectly viable language for making web games, whereas other genres are typically going to require using other more difficult languages to learn. There are countless javascript tutorials that start from 0 knowledge of programming, making it incredibly accessible to beginners.

Players are Easy to Find ​

Once you've finished your game and uploaded it on github pages or itch or just copied the link if you're using glitch or replit (all of which are easy to do), anyone can now play the game in their browser. This low barrier to entry has shown tremendous success in getting completely unknown developers to have thousands of plays.

The incremental games community, which mostly centers around r/incremental_games, is always looking for new games and tends to flood any new ones posted with initial players.

Having your games be played can be incredibly motivating, and the community makes it quite clear that you can expect players to play your game. These communities - both for incremental games in general as well as game-specific communities - tend to be very developer friendly as well. A lot of the developers know each other, and welcome new developers with open arms, often with dedicated channels for programming help and discussions.

Monetization ​

I'd like to clarify that everything I've said above mainly applies to web-based incrementals. Incremental games are also incredibly popular on mobile, but with a much different culture and community. Many mobile gamers will still participate in the web-focused community for the culture. This web-focused community has a culture that has been criticized for being "anti-monetization". Ads, IAPs, and similar forms of monetization are often criticized, mainly due to the abundance of completely non-monetized games available from hobbyist developers. There are exceptions, like paid games often being considered fine, like Increlution or Stuck in Time, or donation ware games like kittens game, but even popular games that have IAP see some level of regular criticism, like NGU Idle, Idle Skilling, or Idle Pins. A large part of this can be explained by the community being hyper-aware of the addictive) nature of this genre and its susceptibility to exploiting players.

On mobile, however, monetization is the norm and expected. If an incremental game is available on mobile, it almost certainly will be monetized, and mobile players are aware and accepting of that. Mobile incremental games, due to their addictive nature, tend to make a lot of money. It's very lucrative, and therefore these games are quite abundant on mobile storefronts.

',13),r=[i];function l(s,d,m,c,p,h){return t(),a("div",null,r)}const y=e(n,[["render",l]]);export{g as __pageData,y as default}; diff --git a/assets/guide-to-incrementals_ludology_appeal-developers_index.md.Cm_ScJQR.lean.js b/assets/guide-to-incrementals_ludology_appeal-developers_index.md.Cm_ScJQR.lean.js deleted file mode 100644 index 5710a70d..00000000 --- a/assets/guide-to-incrementals_ludology_appeal-developers_index.md.Cm_ScJQR.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as o}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Guide to Incrementals/Appeal to Developers","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/appeal-to-developers","title":"Guide to Incrementals/Appeal to Developers","prev":false,"next":false},"headers":[],"relativePath":"guide-to-incrementals/ludology/appeal-developers/index.md","filePath":"guide-to-incrementals/ludology/appeal-developers/index.md"}'),n={name:"guide-to-incrementals/ludology/appeal-developers/index.md"},i=o("",13),r=[i];function l(s,d,m,c,p,h){return t(),a("div",null,r)}const y=e(n,[["render",l]]);export{g as __pageData,y as default}; diff --git a/assets/guide-to-incrementals_ludology_appeal-gamers_index.md.B6xF3S0w.js b/assets/guide-to-incrementals_ludology_appeal-gamers_index.md.B6xF3S0w.js deleted file mode 100644 index 1f047f9e..00000000 --- a/assets/guide-to-incrementals_ludology_appeal-gamers_index.md.B6xF3S0w.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Guide to Incrementals/Appeal to Players","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/appeal-to-players","title":"Guide to Incrementals/Appeal to Players","prev":false,"next":false},"headers":[],"relativePath":"guide-to-incrementals/ludology/appeal-gamers/index.md","filePath":"guide-to-incrementals/ludology/appeal-gamers/index.md"}'),o={name:"guide-to-incrementals/ludology/appeal-gamers/index.md"},n=i('

Guide to Incrementals/Appeal to Players ​

This is something that has been discussed and analyzed by many people, and to some extent, I feel like everything that can be said on the topic already has. However, a lot of these analyses are from the perspective of those with not as much experience and involvement within the genre as I'd argue would be necessary for a fully contextualized answer. I recently watched a video about Vampire Survivors, which has since been taken down due to drawing negative attention, which made me think about some interesting arguments about what games are, and what makes them good. The video's argument that "Vampire Survivors is not a video game" mirrors a claim by the developer of Cookie Clicker that his games are "non-games". Using Vampire Survivors and the video made on it as a framework, I'll be answering why incremental games appeal to players. Since the video has been taken down, I'll do my best to contextualize and generalize the arguments of the video without requiring the reader to watch it. For what it's worth, while I disagreed with the video I actually liked a lot of the way it went about thinking about games, and I consider this a continuation of that discussion.

Numbers Going Up ​

This is a very common response to why people enjoy incremental games, although it's not one I find compels me personally, and I suspect it might be a stand-in for progression) or Guide to Incrementals/What is Content?. But reportedly, some people do just like seeing big numbers. I must reiterate I suspect the actual cause is seeing big numbers in context though - if you start at 1e1000 of a currency and get to 1e1001, that isn't going to feel as satisfying as going from 1e10 to 1e100, and in any case, I don't think a button that just adds a zero to your number will feel quite satisfying - I believe its the sense of having made progress, and comparing where you are to where you started and feeling like you've earned your way here that is enjoyable.

Progression

Vampire Survivors can be argued to have a comparatively low depth to its combat compared to many other games. I'd argue it has sufficient depth and more than someone might expect who has only played the game for a short while, but it still definitely gets beat out by many other combat-focused games. Instead, a lot of the progression in Vampire Survivors comes from a meta-progression system by which base stats are increased by spending a currency that persists between runs. While it is technically possible to win without this meta-progression system, and indeed in many roguelikes players like to challenge themselves by beating the game without any meta-progression, the criticism can be made that meta-progression de-emphasizes player skill by making it less important to have to beat the game. Certainly, in incremental games, it is often literally impossible to complete a game without taking advantage of the meta-progression systems. I'd argue this does not detract from the game, however, and is actually a part of what makes incremental games, and roguelikes, enjoyable to many players: meta-progression augments the increases in skill the player is naturally gaining as they play. In effect, it's not replacing the skill increase, but exaggerating it to make it feel more real to the player.

Note: There is also a lot of progression from exploring the mechanics and discovering synergies, unlocking new weapons or playable characters, etc. That just isn't as relevant to this discussion, but it does make up a lot of the appeal of the game.

Effortlessness ​

Incremental games are so easy, a lot of them even have you progress while you're not playing! Part of the appeal is being able to feel like you're making progress while doing something actually productive - multitasking, in a way. In this sense, the game is more of a fidget toy - not something to think hard about and play actively, but something to click a few buttons every so often while you're paying attention to a lecture or studying or working. Of course, not all incremental games lend themselves to being played this way - it's specifically "idle" games that work like this. These are games that take an incredibly long amount of time to see all the content, stretching it as thin as possible, but they aren't expecting you to be sitting at your device playing it the entire time. They expect you to leave and come back later to make a bit of progress and repeat the cycle.

If you look at the higher-level play of most games, you'll see them perform difficult feats with ease and speed. They'll achieve a "flow state" that takes all their knowledge and experience of the game and uses it to play the game as instinctively as possible. It's incredible to watch things like Slay the Spire speed runs or competitive DDR-likes. I'd argue the goal of a lot of games with a competitive scene is to get so good that the game becomes effortless. In that sense, a game that allows you to reach that point earlier isn't any less legitimate, but rather lowers the barrier to entry by allowing more people to get "really good" at the game. And to be clear, Vampire Survivors and (most) incremental games aren't trivially easy - they, and to an extent, every game will have some level of learning and improvement over time.

Addiction

A lot of these reasons for why incremental games appeal may have reminded you of why gambling appeals to people, particularly those prone to addiction. Indeed, incremental games are quite often criticized for their similarity to a skinner box. Some have gone as far as to say incremental games as a genre are commenting that all games are skinner boxes). The argument goes that some games are not fun, but rather condition players into continuing to play without actually getting anything from the experience. When tied to real-world money this is seen as predatory, and to a lesser extent, even free games may be feeding the addictive sides of people and making them more prone to seek out gambling or micro-transaction heavy games.

While incremental games can be fun and even healthy in certain contexts, they can exacerbate video game addiction more than other genres. If you feel like playing incremental games is taking priority over other things in your life, or manipulating your sleep schedule, it may be prudent to seek help. See r/StopGaming for resources.

Since incremental games are often built on extrinsic motivations in the form of progression systems, it's hard to argue whether players continue to play because they are enjoying the gameplay, or if they are just conditioned to keep doing it because the game keeps rewarding them. Unfortunately, it can often feel like it's the latter, as there isn't typically anything compelling about the "gameplay" of clicking a button and waiting. There may be a significant overlap between those who enjoy incremental games and those who are most prone to addiction, and there are often posts on r/incremental_games about someone either struggling with or overcoming video game addiction.

Strategy ​

Incremental games could be considered a subset of strategy games), and inherit the appeals of strategy games. This includes the appeal of feeling like you've found a good solution to a puzzle, or that you're learning more about the game and are improving at making decisions within it. This applies to Vampire Survivors specifically, where you're learning about evolutions and synergies and what kinds of enemies can spawn under what conditions, and how best to handle them.

Note that strategy games are not all the same difficulty, as well. Vampire Survivors is still easier to play than Starcraft 2, and Cookie Clicker is probably somewhere in between (once you progress sufficiently). Vampire Survivors being so successful may indicate that "easier" strategies may have their separate appeal to harder strategy games - players like to feel smart and that they figured the game out and have optimized or mastered it, and the game being easier doesn't detract from that sense of accomplishment as much as it allows more and more users to be able to reach the point where they gain that sense.

Avoiding Staleness ​

Incremental games tend to have "paradigm shifts", where the gameplay changes in a meaningful way at various times throughout the progression of the game. These upset and change the gameplay loop, which helps keep them from stagnating. This constant "freshness" to the gameplay can keep players engaged for longer, compared to a game with a repetitive and static gameplay loop.

Good Game Design ​

Incremental games tend to show their game design "plainly", so it's more readily apparent if a game has good game design while playing, even if you're not looking for it. While different players have different preferences and might enjoy different types of games more than others, there are underlying good and bad game design principles that players will notice the effects of. To be clear, this isn't talking about stuff like big numbers being enjoyable, where I can comfortably agree to disagree with other players. They don't intrinsically make my experience better, but I'm aware of those for whom it does and I won't argue against their feelings. However, the game designer in me does feel like there are some extremely clear-cut examples of good and bad game design philosophies.

Let's start by giving an example of a mechanic I think can be easily and strongly argued is good game design. There are of course many examples, but a personal favorite of mine is how DOOM encourages aggressive gameplay by linking health drops to melee attacks. It has an intended experience it's trying to give the player - immersing themselves as DOOM guy, who would not hide behind cover when low on health - and this mechanic does a great job at encouraging and effectively teaching players to behave properly. This is in sharp contrast to shooters like Call of Duty, which have you regen health passively, encouraging players to hide behind cover and wait after getting hit. Note that I'm not arguing CoD is poorly designed, as the games have different intended experiences. I'm specifically praising DOOM for having a mechanic that does a good job at ensuring the player has that intended experience.

To contrast with an example I think is bad game design, let's talk about shields in souls-likes. This is a bit of a famous example, and I highly recommend this video essay which spends quite a good bit of time on this topic. Essentially, the argument boils down to players of earlier games in the souls games using shields too much - playing slowly, conservatively, and ultimately having less fun. Players wanted to feel safe, so they ended up playing in a way that ruined the experience for them. The developers solved this by removing shields, apart from an intentionally bad one effectively mocking the playstyle, and it did its job at getting players to play more aggressively, and often have more fun.

To bring the conversation back to incrementals, I'm incredibly opinionated on what makes a good incremental game, which I'll discuss in the game design section. Suffice it to say, incremental games rely more on good game design than other genres, due to not having much to distract from bad game design. This helps (although imperfectly - gamers are a bit too tolerant of bad game design!) well-designed games rise to the top within the genre.

Artistic Merit ​

The Vampire Survivors video made me think back to the old arguments about whether games are art, and whether they ought to be. The video seems preoccupied with attaching value to games solely based on their mechanics and the depth thereof, to the point of arguing Vampire Survivors is a waste of time due to its lack of depth. However, even setting aside the fact that if players are having fun then it's not time wasted, I think games can have artistic merit that supersedes the necessity of having (any / engaging / "deep") gameplay. I think the consensus online is that games are definitively art, although I could see the argument that some genres, like incremental games, might be a bit in a grey area. Let's talk about Vampire Survivors first though - It has a story to tell, with lore and many characters, that drive the player and encourage them to continue exploring the game and discovering things within it. Like any walking simulator, it is no less legitimate of a game or the "art" label because of any lack perceived lack of depth. For what it's worth, most art can be consumed with more ease than VS - any painting, movie, sculpture, etc.

A lot of incrementals have a narrative context that can similarly qualify them as art. Cookie Clicker is, as has been pointed out numerous times before, commenting on excess and increasing production beyond any reasonable limits - devolving into increasing production for its own sake. Indeed, a lot of incremental games are written to comment upon various concepts like capitalism or tropes in games, as discussed when defining Incrementals). However, I'd like to argue most incremental games are still art, even without any narrative context. "Art" as a concept is pretty nebulous already, but I personally like those who define it as an act of expression more than any physical result. The creator and the context within which they created the art, and any meaning they put into it, are all relevant and a part of the art itself. Most incremental games have artistic merit from things like why the creator made it, why they chose to make it an incremental game, and why they made any particular design decision. Hell, even if you play through an entire incremental game without a single thought or feeling, that very fact it elicited nothing can itself be artistic merit!

I'm not an art major, and I may be taking a somewhat extreme take on what is art and what has artistic merit, but I'd argue the overall point stands that games, and incremental games specifically, can have artistic merit, which appeals to many gamers.

',28),s=[n];function r(l,h,m,g,d,c){return a(),t("div",null,s)}const y=e(o,[["render",r]]);export{u as __pageData,y as default}; diff --git a/assets/guide-to-incrementals_ludology_appeal-gamers_index.md.B6xF3S0w.lean.js b/assets/guide-to-incrementals_ludology_appeal-gamers_index.md.B6xF3S0w.lean.js deleted file mode 100644 index 8b0cae9a..00000000 --- a/assets/guide-to-incrementals_ludology_appeal-gamers_index.md.B6xF3S0w.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Guide to Incrementals/Appeal to Players","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/appeal-to-players","title":"Guide to Incrementals/Appeal to Players","prev":false,"next":false},"headers":[],"relativePath":"guide-to-incrementals/ludology/appeal-gamers/index.md","filePath":"guide-to-incrementals/ludology/appeal-gamers/index.md"}'),o={name:"guide-to-incrementals/ludology/appeal-gamers/index.md"},n=i("",28),s=[n];function r(l,h,m,g,d,c){return a(),t("div",null,s)}const y=e(o,[["render",r]]);export{u as __pageData,y as default}; diff --git a/assets/guide-to-incrementals_ludology_content_index.md.DktkMXz1.js b/assets/guide-to-incrementals_ludology_content_index.md.DktkMXz1.js deleted file mode 100644 index bd177cdb..00000000 --- a/assets/guide-to-incrementals_ludology_content_index.md.DktkMXz1.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as n}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Guide to Incrementals/What is Content?","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/what-is-content-","title":"Guide to Incrementals/What is Content?","prev":false,"next":false},"headers":[],"relativePath":"guide-to-incrementals/ludology/content/index.md","filePath":"guide-to-incrementals/ludology/content/index.md"}'),o={name:"guide-to-incrementals/ludology/content/index.md"},i=n('

Guide to Incrementals/What is Content? ​

If you've been in the incremental games community for any amount of time, you'll quickly find the number one thing players want is content. They want as much of it as possible! The most popular incremental games have tons of content, so they just keep stretching on and on and on, introducing mechanic after mechanic, and players love it. In fact, players seem to value the amount of content over the quality of any specific content. However, there's a bit of a lack of understanding concerning what content is, and I'd like to explore what counts as content, and how we measure it. As a baseline definition, I think "content" can just be described as the parts of the game that engage the player, but to truly understand it we need to contextualize what that means and how it affects the gameplay experience.

To clarify the purpose of this page, my goal is not to get (too) nitpicky or to attack games with "low content". There's nothing wrong with short / low-content games - I'm quite a big fan of those games myself! This is mostly targeted toward those who ask for content and settle for "long" games, and those who want to provide content but want to make sure they're not just artificially inflating the game. Ultimately, I suppose the goal is to just reduce the amount of artificially inflated content for the sake of having a "longer" game.

Interaction ​

I think it should be a fairly non-controversial opinion that time spent solely waiting should not count towards content. That is not including the time reading various effects or making decisions in your head, but rather time spent waiting for a condition to be met so you can re-engage with the game.

That is not to say games should necessarily try to minimize this time. Plenty of games lead towards more infrequent interaction and still get popular. In fact, these games appeal to many gamers who want to have something to check up on in between bursts of working on some other activity. These games seem to have fallen slightly out of fashion amongst modern incremental games, but they're still fully valid. The point I'm trying to make here is just that this time is not content. As an extreme example, a game with no interactions and just a counter that goes up every second could safely be said to have 0 content beyond the time it takes to understand what's going on. If it has a list of "goals" to hit, then the time understanding those goals and a short time after achieving each one could be considered content, but not the idle times in between.

Let's take a look at the opposite end of the spectrum - interaction that is so frequent as to become mindless. This is any mechanic where you need to spam-click something to progress. This may be a more controversial take, but I do not believe this constitutes content either. It does not engage the player, because each consecutive click blends together and they do not individually change the gameplay experience. That is to say, a single click and 100 clicks are not meaningfully different in terms of engaging the player. I'd go as far as to say clicking 100 times would be actively worse, as it's artificially delaying the next piece of actual content, alongside the issues of accessibility and potentially causing RSI.

Repeatable Purchases ​

Imagine an entity in a game that you can purchase multiple times, each time it performs the same thing but for a higher cost. These are incredibly common, from the buildings in cookie clicker to the units in swarm sim to the IP and EP multipliers in antimatter dimensions. However, how much content is each specific purchase? Is it content beyond the first purchase? Does it have diminishing returns? What if you are oscillating between two different repeatable purchases? How much content is lost when you automate) away a repeatable purchase?

I don't want to take too harsh a stance against repeatable purchases. They're useful tools and can be used in a myriad of interesting ways. I feel they do become "stale" or less meaningful content over time, and this happens exponentially quickly the more frequently it can be purchased. A classic example that I believe goes too far is the IP/EP multipliers in Antimatter Dimensions. I would go as far as to say they are a chore and do not provide any meaningful content after you've bought them a couple of times. It's a method for inflating numbers (effectively making every OOM a 5x step instead of 10x), that punishes the player progression-wise whenever they forget to max it again, and eventually gets automated away as a reward to the player for making enough progress.

Just to voice the other side of this argument, Acamaeda defended the IP multiplier as giving the player a "good" upgrade every OOM. I can understand that to a point and need to clarify I'm mainly criticizing IP/EP multipliers after they've been introduced for a while. In fact, I would defend the multipliers for a short while after they're introduced using the same logic I would use to defend normal dimensions as repeatable purchases, at least pre-infinity. There's "content" to be had in looking at what dimensions will become affordable next, and then choosing which to buy amongst those. The IP/EP multipliers, early into infinity or eternity respectively, provide another option that gets put into that mental queue of things to buy with each OOM reached - although the optimal order is often quite trivial and not particularly engaging.

The IP/EP multipliers are not the only repeatable purchase in antimatter dimensions I take offense to. The time dimensions are also a series of repeatable purchases, that are all so similar and static that it doesn't take long before you never need to put any thought into buying them, how much you're buying at once, or the order you buy them in - you just press max all and move on. The entire tab could've been just the max all button and it would not have made a difference beyond the start of the eternity layer. The normal dimensions technically have this problem as well, but since you're constantly getting antimatter the order feels like it has a larger impact and it's more meaningful content, right up until they're automated away. Infinity dimensions are a compromise between the two, so I'm highlighting time dimensions here as the most egregious.

Following Instructions ​

We're getting more and more controversial as we go along! Let's talk about how linear content is not content now (in some circumstances). A trend in incremental games is adding difficulty by adding a web of effects that abstract the true change you can expect from any specific purchase or decision you make. If a game is both linear and sufficiently abstracts the effect of player decisions, then the player will no longer be engaging with the content - they'll simply be clicking on things as they become available. This isn't necessarily a bad thing, as plenty of players don't mind this style of gameplay, but I'd argue once you reach a point where players don't bother reading the effects, those interactions are no longer truly content. Note that unlike the previous qualifiers mentioned, this qualifier is based on the player, and therefore subjective. In effect, it's a spectrum where the more complicated the web of effects becomes, the more likely it is to disengage the player.

This over-complicatedness leading to disengaging the player can also happen from non-linear gameplay. If the web of effects becomes sufficiently complicated and finding the optimal progression route too time-consuming to discover, players will seek out guides from other players who've completed the game. The second they do this, the game effectively becomes linearly following the instructions of the guide and all the above criticisms apply. Similarly to as before, though, this is a spectrum and not everyone will seek out a guide at the same level of difficulty.

Automation

Automation is a staple of the genre, but it has certain implications for the design of the game. Why, when new content is introduced, must the older content be automated away - why is it a chore and it feels rewarding to not have to do it again? Why does the new mechanic have such appeal if we know it too will just be automated away later on, and we'll be happy when that happens? It honestly begs the question of why this framework of introducing content and automating the old content is even enjoyable - and nearly nonexistent in other genres. You're not going to reach a point in a platformer game where they just automate the jumping part - that's the core mechanic! Instead, platformers either add new mechanics that build on the core mechanic or at least re-contextualize the core mechanic. However, in incremental games new content very frequently means replacing older content, as opposed to augmenting it.

Admittedly, the above paragraph ignores the obvious answer that separates incremental games in this regard. These mechanics become chores as their frequency increases. The frequency increases to give a sense of progression, and automation is seen as a reward because it now manages what was becoming unmanageable. The new content then comes in and continues the loop to give a stronger sense of progression. That's all good and a fine justification for automating content instead of building upon the base mechanic. It's also much easier to design, as each layer essentially lets you start over instead of needing to think of ideas that conform to the original core mechanic.

So, what's the problem? Even if this trend is justified and easy to implement, there are some other effects it has on the game design. First off, and this is probably a neutral point, incremental games with this cycle of replacing old mechanics with new ones trend towards more and more abstract and further away from any narrative throughline as they add layers. There are only so many justifications for resetting progress, so if a game wants to have several of these layers they're inevitably going to become generic or increasingly loosely associated with the original content. It's most unfortunate, in my opinion when an interesting or innovative core mechanic gets fully automated once a generic "prestige" layer is unlocked.

A recent example is Really Grass Cutting Incremental, an incremental game about cutting grass (although I'm really criticizing the Roblox game it's based on). Except, it doesn't continue to be about cutting grass. After you buy enough upgrades to increase your grass cutting and level up sufficiently you "prestige", an abstract term that in this case means you reset all your progress to get some currency to buy upgrades that do the same things as the original upgrades, but these won't reset on future prestiges. You'll eventually be able to "crystallize", which means you reset all your progress to get some currency to buy upgrades that do the same things as the original upgrades (and a couple of new ones) and won't reset on future crystallizes. Fine. You'll progress a bit, complete some challenges, and finally get to... grasshop? Grasshopping is this mechanic where you reset all your progress to get some resource that isn't for buying upgrades - this time you just unlock different modifiers on everything based on their amount. You may have gotten the point by now, but there are also "steelie" resets which give you steel for some reason, before unlocking a factory with various machines - none of which are directly tied to cutting grass, and start gathering things like oil and reset for rocket parts and reset to go to space and so on and so on. Throughout all of this there is absolutely no narrative justification or throughline for the direction the game is going, or why cutting grass is still relevant when we're collecting things like rocket parts. I may be going a little hard on GCI, but it is far from alone.

Tips for Developers ​

If you're a developer, by this point you should have a pretty decent idea of how to create "true" content in your game. Here are some other specific tips I'd suggest:

An upgrade that simply unlocks another upgrade trivially isn't content. However, many games have an upgrade that just unlocks a feature, which then has a wait or other requirements before it can be used. Try to make sure when you unlock a feature, there is immediately something to do with the feature - for example, perhaps give them a small amount of the new currency it unlocks, if applicable.

If you don't have a large web of effects, and can definitively say the impact of a purchase is to multiply the gain of the cost currency by N, and the next purchase costs N times the amount of that same currency, then this purchase effectively made no difference and it may have made more sense to just go directly to the next upgrade. That said, having effects based on things like the number of purchases made will quickly invalidate this tip.

',24),s=[i];function r(h,l,c,u,m,d){return a(),t("div",null,s)}const f=e(o,[["render",r]]);export{p as __pageData,f as default}; diff --git a/assets/guide-to-incrementals_ludology_content_index.md.DktkMXz1.lean.js b/assets/guide-to-incrementals_ludology_content_index.md.DktkMXz1.lean.js deleted file mode 100644 index e15bcde7..00000000 --- a/assets/guide-to-incrementals_ludology_content_index.md.DktkMXz1.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as n}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Guide to Incrementals/What is Content?","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/what-is-content-","title":"Guide to Incrementals/What is Content?","prev":false,"next":false},"headers":[],"relativePath":"guide-to-incrementals/ludology/content/index.md","filePath":"guide-to-incrementals/ludology/content/index.md"}'),o={name:"guide-to-incrementals/ludology/content/index.md"},i=n("",24),s=[i];function r(h,l,c,u,m,d){return a(),t("div",null,s)}const f=e(o,[["render",r]]);export{p as __pageData,f as default}; diff --git a/assets/guide-to-incrementals_ludology_definition_index.md.D2MCMru0.js b/assets/guide-to-incrementals_ludology_definition_index.md.D2MCMru0.js deleted file mode 100644 index 8793b816..00000000 --- a/assets/guide-to-incrementals_ludology_definition_index.md.D2MCMru0.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as r}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Guide to Incrementals/Defining the Genre","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/defining-the-genre","title":"Guide to Incrementals/Defining the Genre","prev":false,"next":false},"headers":[],"relativePath":"guide-to-incrementals/ludology/definition/index.md","filePath":"guide-to-incrementals/ludology/definition/index.md"}'),n={name:"guide-to-incrementals/ludology/definition/index.md"},o=r('

Guide to Incrementals/Defining the Genre ​

Video games are placed into genres for a variety of reasons. They can give a mental shorthand to set the player's expectations up, they can help a game market itself by its similarities to other, already popular games, and honestly, people just love categorization for its own sake. For this guide, it's important to define the genre so it is clear what games it's even talking about.

This poses a problem. "Incremental" is a horribly vague way to define games. Most games have numbers going up in some form or another. We need a more specific definition - similar to how "strategy" can't just mean any game with any amount of strategy because that would be most games. What specifically differentiates incremental games from the rest?

"Incremental" implies it's a genre defined by a game mechanic, but all those game mechanics it could imply exist in many other games. Having a skill tree or upgrades doesn't make you incremental, and if a reset mechanic is all it takes then every roguelite would be an incremental as well. So clearly there's more to it than that - what makes an incremental an incremental?

I'd like to go over a couple of popular suggestions I've seen on defining the genre here. I have my personal preferences and will state them here, but I don't think there's a truly perfect answer here.

Disclaimer: I mostly play incremental games on my computer, and my definitions will be heavily biased towards the games I'm familiar with.

Incrementals vs Idlers vs Clickers ​

Oftentimes people refer to this genre as idle games and/or clicker games. You'll even find a trend of oxymoronic game titles that contain both terms. "Incremental games" is the umbrella term both those terms fall under. However, I'd like to argue that not only is it better to just use the term "incremental games", but calling them "idle games" or "clicker games" is wrong. Almost universally, these terms are used interchangeably to refer to the same kind of game, where you start the game click spamming and eventually automate the process. Frankly, that kind of game deserves neither title, and the genre of incremental games has trended away from ever requiring click spamming, as it's a bad mechanic, anyways.

While these games do span a spectrum of how active it requires you to be, and sorting games by that metric can be useful for those looking for a particular experience, the borders of when an incremental game counts as an "idler" is too blurry for the term to be useful. "Incremental games" may not be a great descriptive term for the genre (hence this many thousands of words long page on defining what the genre even is), but it's strictly better than calling them "idler" or "clicker" games. This guide will always use the term "incremental games" unless quoting someone else, as it is the term you typically see on all modern games in the genre.

Incrementals as Parodies

Let's start with one of the most interesting definitions of incremental games. Incremental games appear to be distilled versions of games or genres, "revealing" the naked game design at the core of these games or genres not unlike how parodies comment upon their source material.

To understand what that means, think of how a casino uses skinner boxes to emotionally manipulate its customers to keep playing, but "dressing" up the skinner box with tons of stimuli to hide that ultimately the goal is to condition you into coming back compulsively. The idea that incremental games are parodies means taking the stance that at some level all games are similarly manipulating you, giving dopamine rewards in a way that manipulates you to keep playing while not necessarily giving you any value or fulfillment. Incremental games, then, are any games that plainly display the skinner box, and the manipulative core of the game, at the forefront of the experience.

While incremental games can be fun and even healthy in certain contexts, they can exacerbate video game addiction more than other genres. If you feel like playing incremental games is taking priority over other things in your life, or manipulating your sleep schedule, it may be prudent to seek help. See r/StopGaming for resources.

This "undressing" tends to go hand in hand with a reduced focus on aesthetics, often just printing the game state directly to the screen as text. This makes incremental games much easier to develop, particularly for those with programming skills but not art skills, but that's a tangent for why Incremental Games Guide to Incrementals/Appeal to Developers.

Before I continue, I'd like to make my stance clear that I love games and incremental games, and do not think they should be considered inherently bad or manipulative with the above logic. Skinner boxes are just a way of manipulating behavior via rewards. The games are still fun - that's the reward! I'd believe the real criticism here is that it is "empty fun", or "empty dopamine", that doesn't offer any additional value or sense of fulfillment. I don't think that's inherently bad in moderation, although it can become a problem if the game is manipulating you for profit-seeking, or if you play the game to the detriment of the other parts of your life.

Another interpretation of incremental games as parodies comes from several mainstream incremental games that are also parodies of capitalism, such as cookie clicker and adventure capitalist. It's a very common framework for incremental games to portray the ever-increasing numbers as an insatiable hunger for resources, like the ones observed within capitalism. Therefore, these games are used as evidence that the genre as a whole is about parody and commentary.

Popular videos on incremental games that portray the genre as parodies are Why Idle games make good satire, and how it was ruined. and Bad Game Design - Clicker Games. You may also be interested in this response to the latter video from a fan of incremental games: BadGood Game Design - Clicker Games.

I think that this definition ultimately ascribes a motive to the genre as a whole that only happens to apply to some of the more mainstream titles. There certainly are incremental games commenting on different things, including the genre itself as in the case of The Prestige Tree Classic, The Ascension Tree, or Omega Layers, but certainly not all. And of course, not all games that comment on something or parody something are incremental games! Additionally, a very large majority of incremental games are mobile games using these manipulative strategies to get players to spend as much money as possible - hell, Adventure Capitalist is ostensibly a critique on capitalism but features microtransactions and gameplay that manipulates you into buying them! These profit-seeking incremental games certainly belong within the genre but are hardly parodies when they too use manipulation to serve their interests. Also, from my own anecdotal experience, those who use this definition seem to do so from a fairly surface-level familiarity with the genre, and often in the context of criticizing the genre or the fans thereof.

Incrementals as NGU ​

Another broad definition often used is that incremental games are games where the focus of the game is "numbers going up". This definition proposes that other genres simply use increasing numbers as a means to an end, but incremental games uniquely only care about the numbers themselves going up. Put another way, it implies there should be no narrative justification for the numbers going up other than "why shouldn't they be going up?"

While this definition is common because it feels easy to understand, it is difficult to formally define. Often phrases are used to describe games using this framework, such as having an "exaggerated sense of progression" or "big" numbers. These terms are vague and don't demonstrate an actual threshold between non-incrementals and incrementals. Most games have a sense of progression, so when is it "exaggerated"? How big are "big" numbers? Most notably, RPGs that are typically not considered incrementals will often pass this definition.

Additionally, a lot of incrementals tend to have some theme guiding the gameplay, or at least the names of mechanics. This makes the line blurred between when numbers are going up for their own sake versus for a contextual reason. I believe this point is best illustrated that, while most RPGs are not considered incremental games, there is a sub-genre of "incremental RPGs" that typically relates to RPGs that perform combat automatically. This definition of incremental games does not support RPGs and "incremental RPGs" being on distinct sides of the line if the only difference between them is manual vs automatic combat.

Incrementals as Strategies

This is a rarer interpretation, but there are similarities between incremental games and strategy games, implying incrementals might just be a sub-genre of strategy games. By this approach, incremental games would be defined by their relation to strategy games, and how they involve player strategy. Incremental games are often large optimization problems - above all else, the actual gameplay the player is performing is deciding what to do next. The consequences of wrong decisions are typically more lenient in incremental games - such as just not making optimal progress - but they certainly get complex.

So if we accept the premise that incrementals could fall under strategy, we still need to define what makes a strategy game an incremental versus some other strategy sub-genre. This is a bit tricky due to one particular sub-genre of strategy games: Factory Builders.

Factory builders, such as Factorio or Satisfactory, are games about gaining ever increasing resources, optimizing production, and expanding more and more. That... sounds pretty similar, doesn't it? In fact, there's been some debate on whether factory builders would fall under the "incremental" umbrella. I think it's safe to say the two are certainly related, and probably have quite a bit of overlap in playerbase.

Roguelites as Incrementals? ​

Earlier on, I mentioned reset mechanics shouldn't be used in the definition because that could make all roguelites incrementals... But what if it does? A lot of incrementals can be described as games with a strong sense of progression, often with layers of meta-progression. Roguelites fit that bill to a T. What would make roguelites not incremental? I honestly don't think there's a good explanation here, but many fans of incremental games will state they do believe the two genres to be unrelated, even if there's a significant overlap between their player bases due to having similar appealing traits.

At this point, it'd be appropriate to consider what part of the definition of roguelites precludes them from also being incrementals, but that reveals a new problem: What are roguelites? They're usually defined as rogue_likes with meta-progression, but that just pushes the problem back a step: Incrementals aren't the only genre to have difficulties defining themselves, it seems! Roguelikes are another genre where the community argues over the formal definition of their genre, although that means we can borrow from their process of coming to a consensus, and maybe come across a viable definition for incremental games.

The Berlin Interpretation ​

By far the most popular way of defining roguelikes is the "Berlin Interpretation", which acknowledged the diversity of games within the genre and argued the definition should not be based on any ideals about what the genre ought to be, but rather defined by "its canon". They argued there are a handful of games that can be used to define the canon for roguelikes, and from those games, a list of factors can be derived to determine a game's "roguelikeness". The more factors a game has, the more of a roguelike it is. This strategy is very lenient, allowing a game to not present any specific factor so long as it shows enough, and accounts for the blurriness of any genre definition by not explicitly stating how many factors a game must have to qualify as a definite roguelike.

I believe this strategy for defining genres can be applied to other genres as well. A handful of games can be argued to be the incremental games canon, and a list of factors derived from them can be used to judge any game based on its "incrementalness". I'll propose such a canon and list of factors here, but by no means should it be considered the end-all-be-all.

Note: The "Temple of the roguelike", an authority within the genre, has since replaced the Berlin Interpretation with a new set of factors here: https://blog.roguetemple.com/what-is-a-traditional-roguelike/

The Incremental Games Canon ​

Alright, time to get controversial. Up til now, I've been trying my best to stay objective and analytical, but now it's time to start making some opinionated decisions. Here is a list of games I think could justifiably make up an Incremental Games Canon:

I chose a variety of games here, biasing towards newer games, purposefully to avoid making a narrow or "traditional" definition. The genre is growing and shouldn't be constrained by the traits of the early popular titles. A lot of these could easily be replaced with other games that are mechanically congruent, so ultimately I'm sure if you asked 10 people for their canon list you'd just get 10 different answers, but I think this should sufficiently allow us to determine what factors make a game have higher "incrementalness".

The Paradigm Shift ​

The Paradigm Shift is probably the highest possible value factor for an incremental. It's so common that for a while people referred to incrementals that exhibit this trait as "unfolding" games, to the point of trying to replace the term incremental due to their popularity. Paradigm shifts refer to when the gameplay significantly changes. There are too many examples to list here, but notably, every single reset mechanic is typically going to be a paradigm shift. Examples of games with paradigm shifts that aren't tied to reset mechanics include Universal Paperclips and A Dark Room.

There are many reasons for the appeal of paradigm shifts. Oftentimes each mechanic builds on top of the existing mechanics, increasing the complexity of the game in steps so the player can follow along. They provide a sense of mystery, with the player anticipating what will happen next. They shake up the gameplay before it gets too stale - allowing the game to entertain for longer before the sense of Guide to Incrementals/What is Content? dissipates. Of the canon games selected above, I would argue every single one contains a paradigm shift (although I could see someone disagreeing with that statement wrt Increlution).

I should take a moment to say that while I'm hyping up this specific factor, we cannot just reduce the genre definition to "does it have paradigm shifts". Many games have paradigm shifts that are not incremental, so it's just an indicator of incrementalness. Additionally, it can become quite hard to determine how large of a shift is a "paradigm" shift. Take, for example, any game with a skill tree. In some games, each skill node might have a large impact on how you play with the game, and qualify as a paradigm shift for some players. In other games, each skill node might just be a small percentage modifier on some stat that doesn't really impact much more than a slight bias towards an already established mechanic that's newly buffed. Every single canon game may show that it's common amongst incremental games, but could just as easily indicate that they're common in games in general.

High-Value Factors ​

I won't take as long to discuss the high and low-value factors, as you've already seen most of them brought up earlier on this page. As a reminder, a game does NOT need all of these to be an incremental game, but these are factors that each indicate a strong possibility the game is an incremental, so having several of these means they probably are. These factors apply to most of the canon incremental games.

"Pure UI" Display. Incrementals typically have a textual presentation of the game state - there isn't a visual representation of the entities within the game. The interface is closer to what would be just the UI of a game in another genre or the control panel of a plane. If there is a visual representation, the player is often still interacting with non-diegetic game elements.

Reduced Consequences. Incrementals tend to have reduced repurcussions for misplaying. They very rarely have fail states, where often the largest consequence is simply not progressing - never losing progress.

Optimization Problems. The predominant gameplay of incrementals is typically solving optimization problems, from deciding which purchase to save up for to reasoning and deciding between different mutually exclusive options the game presents.

Resource Management. Incrementals tend to have a lot of resources within the game to keep track of.

Low-Value Factors ​

These are low-value factors, meaning they aren't as strongly correlated with incremental games. Incremental games may have none of these, and non-incrementals may have several of these - if a game only has low-value factors, they're probably not an incremental.

Fast Numeric Growth. Numbers in incremental games tend to grow faster than in other genres. There are more instances of superlinear growth. The larger the numbers get, the stronger of a signal this factor is.

Automation. As an incremental game progresses, the player often no longer has to deal with earlier mechanics, by having them either happen automatically or otherwise be replaced with an alternative that requires less player interaction.

Goal-Oriented. Incrementals are often heavily reliant on extrinsic motivation to guide the player. Typically this is through some sort of in-game goal to work towards, such as a certain amount of a resource being required to unlock or purchase something new.

Waiting is a Mechanic. In incremental games, the player may come across times where there is no action they can take, and the game will progress automatically instead. The player must wait for some amount of this automatic progress to occur before they can resume interaction with the game.

Are Roguelites Incrementals? ​

Having made our variation of the Berlin Interpretation for incremental games, we can compare it to the Berlin Interpretation to determine if there's enough overlap that any game that "passes" the Berlin Interpretation would also pass the incremental variant. That is to say, whether any roguelite would also be considered an incremental game.

The meta-progression of an incremental game could arguably be considered a paradigm shift, and certainly adds some resource management. Goal-oriented would probably also apply. I think anything other than those would be a stretch, and in my opinion that just isn't enough to qualify. To be totally honest, I was never expecting to conclude otherwise though 😉

Sub-Genres ​

There are some trends in incremental games that go beyond just being a commonly used mechanic, such that they deeply affect the rest of the game design. These trends can be used to determine sub-genres within the incremental games umbrella:

Loops games are a sub-genre defined by having a core mechanic related to a loop, where the player is deciding the actions taken per loop. Notable examples include Idle Loops, Stuck in Time, Cavernous II, and Increlution. You may also argue Groundhog Life and Progress Knight fall into this sub-genre.

ITRTG-like games are a sub-genre defined by having a core mechanic based on clearing increasingly difficult battles and often tend to have a lot of different mechanics to become progressively stronger. Notable examples include Idling to Rule the Gods, NGU Idle, and Wizard and Minion Idle.

Polynomial Growth games are a sub-genre defined by having a core mechanic related to a higher degree polynomial. Notable examples include the base layer of Antimatter Dimensions and Swarm Simulator.

Upgrades Games is a category popular on flash games websites that featured games focused on buying upgrades that would allow you to attain more currency in some sort of minigame that would earn you more money to buy more upgrades, which I'd argue now belong under the fold of incremental games. Notable examples include the Learn to Fly series and Upgrade Complete.

Cultivation RPGs are a genre of games, books, and anime popular in China that center around being in a fantasy world with characters getting stronger over time. While few of them get translated into English, a fan of incremental games may find the available games interesting.

',64),i=[o];function s(l,h,m,g,c,u){return a(),t("div",null,i)}const f=e(n,[["render",s]]);export{p as __pageData,f as default}; diff --git a/assets/guide-to-incrementals_ludology_definition_index.md.D2MCMru0.lean.js b/assets/guide-to-incrementals_ludology_definition_index.md.D2MCMru0.lean.js deleted file mode 100644 index f27343ae..00000000 --- a/assets/guide-to-incrementals_ludology_definition_index.md.D2MCMru0.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as r}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"Guide to Incrementals/Defining the Genre","description":"","frontmatter":{"public":"true","slug":"guide-to-incrementals/defining-the-genre","title":"Guide to Incrementals/Defining the Genre","prev":false,"next":false},"headers":[],"relativePath":"guide-to-incrementals/ludology/definition/index.md","filePath":"guide-to-incrementals/ludology/definition/index.md"}'),n={name:"guide-to-incrementals/ludology/definition/index.md"},o=r("",64),i=[o];function s(l,h,m,g,c,u){return a(),t("div",null,i)}const f=e(n,[["render",s]]);export{p as __pageData,f as default}; diff --git a/assets/index.md.DsTbDkfQ.js b/assets/index.md.DsTbDkfQ.js deleted file mode 100644 index c5fbbbcf..00000000 --- a/assets/index.md.DsTbDkfQ.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a}from"./chunks/framework.CK8QU5WH.js";const d=JSON.parse(`{"title":"The Paper Pilot","description":"","frontmatter":{"title":"The Paper Pilot","layout":"home","sidebar":true,"hero":{"name":"The Paper Pilot","tagline":"I'm Anthony, or The Paper Pilot, and I make fun games and tools!","actions":[{"theme":"brand","text":"My Projects","link":"/projects/"},{"theme":"alt","text":"My Resume","link":"https://resume.incremental.social/thepaperpilot/thepaperpilot"}]},"features":[{"icon":"🧑‍💻","title":"Profectus","details":"A game engine that grows with you","link":"https://moddingtree.com"},{"icon":"👤","title":"Incremental Social","details":"A kind social media site for the incremental games community","link":"https://incremental.social"},{"icon":"🎮","title":"My Games","details":"Most of my games are playable on Itch","link":"https://thepaperpilot.itch.io"}]},"headers":[],"relativePath":"index.md","filePath":"index.md"}`),i={name:"index.md"};function o(n,r,s,l,c,m){return a(),t("div")}const h=e(i,[["render",o]]);export{d as __pageData,h as default}; diff --git a/assets/index.md.DsTbDkfQ.lean.js b/assets/index.md.DsTbDkfQ.lean.js deleted file mode 100644 index c5fbbbcf..00000000 --- a/assets/index.md.DsTbDkfQ.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a}from"./chunks/framework.CK8QU5WH.js";const d=JSON.parse(`{"title":"The Paper Pilot","description":"","frontmatter":{"title":"The Paper Pilot","layout":"home","sidebar":true,"hero":{"name":"The Paper Pilot","tagline":"I'm Anthony, or The Paper Pilot, and I make fun games and tools!","actions":[{"theme":"brand","text":"My Projects","link":"/projects/"},{"theme":"alt","text":"My Resume","link":"https://resume.incremental.social/thepaperpilot/thepaperpilot"}]},"features":[{"icon":"🧑‍💻","title":"Profectus","details":"A game engine that grows with you","link":"https://moddingtree.com"},{"icon":"👤","title":"Incremental Social","details":"A kind social media site for the incremental games community","link":"https://incremental.social"},{"icon":"🎮","title":"My Games","details":"Most of my games are playable on Itch","link":"https://thepaperpilot.itch.io"}]},"headers":[],"relativePath":"index.md","filePath":"index.md"}`),i={name:"index.md"};function o(n,r,s,l,c,m){return a(),t("div")}const h=e(i,[["render",o]]);export{d as __pageData,h as default}; diff --git a/assets/now_index.md.Bc55FAwk.js b/assets/now_index.md.Bc55FAwk.js deleted file mode 100644 index eb5bc2c6..00000000 --- a/assets/now_index.md.Bc55FAwk.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o,a5 as n}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"/now","description":"","frontmatter":{"public":"true","slug":"now","title":"/now","prev":false,"next":false},"headers":[],"relativePath":"now/index.md","filePath":"now/index.md"}'),i={name:"now/index.md"},t=n('

/now ​

This "now page" offers a big picture glimpse into what I’m focused on at this point in my life. What is a now page?

Life ​

I'm living in DFW with my wife and baby son. I work at Topaz Labs LLC as a software developer, where I develop their flagship product Topaz Photo AI.

IndieWeb ​

I've been learning a lot about The Small Web (or the various other names it goes by). I've been working on this website and implementing the various IndieWeb building blocks

I'm also working on a proposal for adding The IndieWeb/Signature Blocks to your notes

Commune ​

While I'm not contributing to the project directly, I'm following along and participating with the discussions and designs of Commune.

I'm working on a mockup of what an app could look like that treats incoming messages, emails, etc. differently based on user defined rules, with a focus on moving them into personal or communal digital gardens.

Incremental Social ​

I'm running and improving the social media site Incremental Social, along with CardboardEmpress.

Chromatic Lattice ​

I'm working on a multiplayer incremental game. That's all that's known publicly for now 😜.

Kronos ​

I'm working on a long single player narratively driven incremental game. This is a very long-term project.

',16),r=[t];function l(s,c,h,d,m,p){return o(),a("div",null,r)}const g=e(i,[["render",l]]);export{f as __pageData,g as default}; diff --git a/assets/now_index.md.Bc55FAwk.lean.js b/assets/now_index.md.Bc55FAwk.lean.js deleted file mode 100644 index a1fcdae8..00000000 --- a/assets/now_index.md.Bc55FAwk.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o,a5 as n}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"/now","description":"","frontmatter":{"public":"true","slug":"now","title":"/now","prev":false,"next":false},"headers":[],"relativePath":"now/index.md","filePath":"now/index.md"}'),i={name:"now/index.md"},t=n("",16),r=[t];function l(s,c,h,d,m,p){return o(),a("div",null,r)}const g=e(i,[["render",l]]);export{f as __pageData,g as default}; diff --git a/assets/public_gamedevtree_2.0-format-changes.md.3MaMo5-m.js b/assets/public_gamedevtree_2.0-format-changes.md.3MaMo5-m.js deleted file mode 100644 index e839c912..00000000 --- a/assets/public_gamedevtree_2.0-format-changes.md.3MaMo5-m.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as o}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"2.0 format changes","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/2.0-format-changes.md","filePath":"public/gamedevtree/2.0-format-changes.md"}'),i={name:"public/gamedevtree/2.0-format-changes.md"},n=o('

2.0 format changes ​

  • Temp format is changed from temp.something[layer] to temp[layer].something, for consistency
  • Challenges are now saved as an object with the amount of completions in each spot. (This will break saves.)
  • effectDisplay in Challenges and Upgrades no longer takes an argument, and neither does effect for Buyables
  • Buyable cost can take an argument for amount of buyables, but it needs to function if no argument is supplied (it should do the cost for the next purchase).
  • Generation of Points now happens in the main game loop (not in a layer update function), enabled by canGenPoints in game.js.
  • Changed fullLayerReset to layerDataReset, which takes an array of names of values to keep

In addition, many names were changed, mostly expanding abbreviations:

All instances of:

  • chall -> challenge
  • unl -> unlocked
  • upg -> upgrade (besides CSS)
  • amt -> amount
  • desc -> description
  • resCeil -> roundUpCost
  • order -> unlockOrder
  • incr_order -> increaseUnlockOrder

Challenges:

  • desc -> challengeDescription
  • reward -> rewardDescription
  • effect -> rewardEffect
  • effectDisplay -> rewardDisplay
  • active -> challengeActive
',7),l=[n];function s(r,c,d,g,h,m){return t(),a("div",null,l)}const u=e(i,[["render",s]]);export{p as __pageData,u as default}; diff --git a/assets/public_gamedevtree_2.0-format-changes.md.3MaMo5-m.lean.js b/assets/public_gamedevtree_2.0-format-changes.md.3MaMo5-m.lean.js deleted file mode 100644 index 336c26f9..00000000 --- a/assets/public_gamedevtree_2.0-format-changes.md.3MaMo5-m.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as o}from"./chunks/framework.CK8QU5WH.js";const p=JSON.parse('{"title":"2.0 format changes","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/2.0-format-changes.md","filePath":"public/gamedevtree/2.0-format-changes.md"}'),i={name:"public/gamedevtree/2.0-format-changes.md"},n=o("",7),l=[n];function s(r,c,d,g,h,m){return t(),a("div",null,l)}const u=e(i,[["render",s]]);export{p as __pageData,u as default}; diff --git a/assets/public_gamedevtree_README.md.C_ZitREW.js b/assets/public_gamedevtree_README.md.C_ZitREW.js deleted file mode 100644 index 3d35f90f..00000000 --- a/assets/public_gamedevtree_README.md.C_ZitREW.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as o,c as a,o as r,j as e,a as t}from"./chunks/framework.CK8QU5WH.js";const k=JSON.parse('{"title":"The-Modding-Tree","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/README.md","filePath":"public/gamedevtree/README.md"}'),i={name:"public/gamedevtree/README.md"},n=e("h1",{id:"the-modding-tree",tabindex:"-1"},[t("The-Modding-Tree "),e("a",{class:"header-anchor",href:"#the-modding-tree","aria-label":'Permalink to "The-Modding-Tree"'},"​")],-1),s=e("p",null,"A modified version of The Prestige Tree that is much easier to mod. It still requires programming knowledge, but it's mostly pretty easy things and copy/pasting.",-1),d=e("p",null,[e("a",{href:"./docs/getting-started"},"Look here for a tutorial on getting started with modding with TMT")],-1),l=e("p",null,[t("You can look in the "),e("a",{href:"./docs/!general-info"},"documentation"),t(" for more information on how it all works, or look at the code in layers.js to see what it all looks like.")],-1),c=[n,s,d,l];function h(m,g,p,_,f,u){return r(),a("div",null,c)}const E=o(i,[["render",h]]);export{k as __pageData,E as default}; diff --git a/assets/public_gamedevtree_README.md.C_ZitREW.lean.js b/assets/public_gamedevtree_README.md.C_ZitREW.lean.js deleted file mode 100644 index 3d35f90f..00000000 --- a/assets/public_gamedevtree_README.md.C_ZitREW.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as o,c as a,o as r,j as e,a as t}from"./chunks/framework.CK8QU5WH.js";const k=JSON.parse('{"title":"The-Modding-Tree","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/README.md","filePath":"public/gamedevtree/README.md"}'),i={name:"public/gamedevtree/README.md"},n=e("h1",{id:"the-modding-tree",tabindex:"-1"},[t("The-Modding-Tree "),e("a",{class:"header-anchor",href:"#the-modding-tree","aria-label":'Permalink to "The-Modding-Tree"'},"​")],-1),s=e("p",null,"A modified version of The Prestige Tree that is much easier to mod. It still requires programming knowledge, but it's mostly pretty easy things and copy/pasting.",-1),d=e("p",null,[e("a",{href:"./docs/getting-started"},"Look here for a tutorial on getting started with modding with TMT")],-1),l=e("p",null,[t("You can look in the "),e("a",{href:"./docs/!general-info"},"documentation"),t(" for more information on how it all works, or look at the code in layers.js to see what it all looks like.")],-1),c=[n,s,d,l];function h(m,g,p,_,f,u){return r(),a("div",null,c)}const E=o(i,[["render",h]]);export{k as __pageData,E as default}; diff --git a/assets/public_gamedevtree_changelog.md.DGS-7PiF.js b/assets/public_gamedevtree_changelog.md.DGS-7PiF.js deleted file mode 100644 index d913c52b..00000000 --- a/assets/public_gamedevtree_changelog.md.DGS-7PiF.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as l,a5 as i}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"The Game Dev Tree changelog:","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/changelog.md","filePath":"public/gamedevtree/changelog.md"}'),r={name:"public/gamedevtree/changelog.md"},o=i('

The Game Dev Tree changelog: ​

v1.0.4 Version Bump [rebalanced,debuggedx3] - 2020-11-09 ​

  • Fixed refactorings 2, 3, and 4 not actually affecting productivity

v1.0.3 Version Bump [rebalanced,debuggedx2] - 2020-11-08 ​

  • Fixed API milestone 4 not working

v1.0.2 Version Bump [rebalanced,debugged] - 2020-11-08 ​

  • Fixed tree lines being hidden after hitting "keepGoing" in the victory screen

v1.0.1 Version Bump [rebalanced] - 2020-11-08 ​

  • Buffed several TAs

v1.0 Version Bump - 2020-11-08 ​

  • Finished row 4
  • Added colored text to lore
  • Fixed some visual bugs with milestones
  • Probably other stuff lol its been a week

v0.2.3 Stylish - 2020-10-30 ​

  • Re-styled basically everything
  • Added favicon
  • Added header bar
  • Added changelog

v0.2.2 Row 3 - 2020-10-22 ​

  • Removed debug statement
  • Moved milestones in F layer beneath the buyables

v0.2.1 Row 3 - 2020-10-21 ​

  • Fixed layers hiding
  • Fixed typos/minor issues
  • Fixed S layer being highlighted before you can unlock the layer

v0.2 Row 3 - 2020-10-21 ​

  • Implemented row 3

v0.1.1 Cash Influx [rebalanced] - 2020-10-19 ​

  • Fixed notification issue
  • Rebalanced to make early game faster and late game slower
  • Fixed other minor issues

v0.1 Cash Influx - 2020-10-19 ​

  • Implemented row 2

v0.0 Initial Commit - 2020-10-18 ​

  • Implemented row 1
',25),n=[o];function t(d,h,s,u,c,b){return l(),a("div",null,n)}const g=e(r,[["render",t]]);export{m as __pageData,g as default}; diff --git a/assets/public_gamedevtree_changelog.md.DGS-7PiF.lean.js b/assets/public_gamedevtree_changelog.md.DGS-7PiF.lean.js deleted file mode 100644 index 7f5050bf..00000000 --- a/assets/public_gamedevtree_changelog.md.DGS-7PiF.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as l,a5 as i}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"The Game Dev Tree changelog:","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/changelog.md","filePath":"public/gamedevtree/changelog.md"}'),r={name:"public/gamedevtree/changelog.md"},o=i("",25),n=[o];function t(d,h,s,u,c,b){return l(),a("div",null,n)}const g=e(r,[["render",t]]);export{m as __pageData,g as default}; diff --git a/assets/public_gamedevtree_docs_!general-info.md.BwFSZwbZ.js b/assets/public_gamedevtree_docs_!general-info.md.BwFSZwbZ.js deleted file mode 100644 index fc3a1db8..00000000 --- a/assets/public_gamedevtree_docs_!general-info.md.BwFSZwbZ.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as o}from"./chunks/framework.CK8QU5WH.js";const b=JSON.parse('{"title":"The-Modding-Tree","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/!general-info.md","filePath":"public/gamedevtree/docs/!general-info.md"}'),n={name:"public/gamedevtree/docs/!general-info.md"},r=o('

The-Modding-Tree ​

The main way to add content is through creating layers. You can either add a layer directly in the layers object in layersSupportjs, or declare it in another file and then do "addLayer(layername, layerdata)" (good for breaking things up into smaller files). The existing layers are just examples and can be freely deleted. You can also use them as references and a base for your own layers.

The first thing you need to do is to edit the modInfo at the top of game.js to set your modID (a string). A unique modId will prevent your mod's saves from conflicting with other mods.

Most of the time, you won't need to dive deep into the code to create things, but you still can if you really want to.

The Modding Tree uses break_eternity.js to store large values. This means that many numbers are Decimal objects, and must be treated differently. For example, you have to use new Decimal(x) to create a Decimal value instead of a plain number, and perform operations on them by calling functions. e.g, instead of x = x + y, use x = x.add(y).

Almost all values can be either a constant value, or a dynamic value. Dynamic values are defined by putting a function that returns what the value should be at any given time.

All display text can be basic HTML instead (But you can't use most Vue features there).

Table of Contents: ​

General: ​

  • Getting Started: Getting your own copy of the code set up with Github Desktop.
  • Main mod info: How to set up general things for your mod in mod.js.
  • Basic layer breakdown: Breaking down the components of a layer with minimal features.
  • Layer features: Explanations of all of the different properties that you can give a layer.
  • Custom Tab Layouts: An optional way to give your tabs a different layout. You can even create entirely new components to use.
  • Updating TMT: Using Github Desktop to update your mod's version of TMT.

Common components ​

  • Upgrades: How to create upgrades for a layer.
  • Milestones: How to create milestones for a layer.
  • Buyables: Create rebuyable upgrades for your layer (with the option to make them respec-able). Can be used to make Enhancers or Space Buildings.
  • Clickables: A more generalized variant of buyables, for any kind of thing that is sometimes clickable. Between these and Buyables, you can do just about anything.

Other components ​

  • Challenges: How to create challenges for a layer.
  • Bars: Display some information as a progress bar, gague, or similar. They are highly customizable, and can be horizontal and vertical as well.
  • Subtabs and Microtabs: Create subtabs for your tabs, as well as "microtab" components that you can put inside the tabs.
  • Achievements: How to create achievements for a layer (or for the whole game).
  • Infoboxes: Boxes containing text that can be shown or hidden.
',14),i=[r];function s(l,d,c,h,u,m){return t(),a("div",null,i)}const p=e(n,[["render",s]]);export{b as __pageData,p as default}; diff --git a/assets/public_gamedevtree_docs_!general-info.md.BwFSZwbZ.lean.js b/assets/public_gamedevtree_docs_!general-info.md.BwFSZwbZ.lean.js deleted file mode 100644 index dded99cf..00000000 --- a/assets/public_gamedevtree_docs_!general-info.md.BwFSZwbZ.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as o}from"./chunks/framework.CK8QU5WH.js";const b=JSON.parse('{"title":"The-Modding-Tree","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/!general-info.md","filePath":"public/gamedevtree/docs/!general-info.md"}'),n={name:"public/gamedevtree/docs/!general-info.md"},r=o("",14),i=[r];function s(l,d,c,h,u,m){return t(),a("div",null,i)}const p=e(n,[["render",s]]);export{b as __pageData,p as default}; diff --git a/assets/public_gamedevtree_docs_achievements.md.DrDgZswR.js b/assets/public_gamedevtree_docs_achievements.md.DrDgZswR.js deleted file mode 100644 index 5be4f4db..00000000 --- a/assets/public_gamedevtree_docs_achievements.md.DrDgZswR.js +++ /dev/null @@ -1,9 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Achievements","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/achievements.md","filePath":"public/gamedevtree/docs/achievements.md"}'),s={name:"public/gamedevtree/docs/achievements.md"},n=i(`

Achievements ​

Achievements are awarded to the player when they meet a certain goal, and give some benefit. Currently, they are pretty basic, but additional features will be added later to help.

You can make global achievements by putting them in a side layer (make its row "side" instead of a number)

Useful functions for dealing with achievements and implementing their effects:

  • hasAchievement(layer, id): determine if the player has the Achievement
  • achievementEffect(layer, id): Returns the current effects of the achievement, if any

Achievements should be formatted like this:

js
    achievements: {
-        rows: # of rows
-        cols: # of columns
-        11: {
-            name: "Blah",
-            more features
-        }
-        etc
-    }

Each achievement should have an id where the first digit is the row and the second digit is the column. Individual achievement can have these features:

  • name: optional, displayed at the top of the achievement. The only visible text. It can also be a function that returns updating text. Can use basic HTML.

  • done(): A function returning a boolean to determine if the achievement should be awarded.

  • tooltip: Default tooltip for the achievement, appears when it is hovered over. Should convey the goal and any reward for completing the achievement. It can also be a function that returns updating text. Can use basic HTML.

  • effect(): optional, A function that calculates and returns the current values of any bonuses from the achievement. Can return a value or an object containing multiple values.

  • unlocked(): optional, A function returning a bool to determine if the achievement is visible or not. Default is unlocked.

  • onComplete() - optional, this function will be called when the achievement is completed.

  • style: Optional, Applies CSS to this achievement, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the achievement was stored under, for convenient access. The achievement in the example's id is 11.

  • goalTooltip: optional, depracated Appears when the achievement is hovered over and locked, overrides the basic tooltip. This is to display the goal (or a hint). It can also be a function that returns updating text. Can use basic HTML.

  • doneTooltip: optional, depracated Appears when the achievement is hovered over and completed, overrides the basic tooltip. This can display what the player achieved (the goal), and the rewards, if any. It can also be a function that returns updating text. Can use basic HTML.

`,9),l=[n];function h(o,r,p,c,d,u){return a(),t("div",null,l)}const k=e(s,[["render",h]]);export{g as __pageData,k as default}; diff --git a/assets/public_gamedevtree_docs_achievements.md.DrDgZswR.lean.js b/assets/public_gamedevtree_docs_achievements.md.DrDgZswR.lean.js deleted file mode 100644 index 97496e8f..00000000 --- a/assets/public_gamedevtree_docs_achievements.md.DrDgZswR.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Achievements","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/achievements.md","filePath":"public/gamedevtree/docs/achievements.md"}'),s={name:"public/gamedevtree/docs/achievements.md"},n=i("",9),l=[n];function h(o,r,p,c,d,u){return a(),t("div",null,l)}const k=e(s,[["render",h]]);export{g as __pageData,k as default}; diff --git a/assets/public_gamedevtree_docs_bars.md.CxNndqIx.js b/assets/public_gamedevtree_docs_bars.md.CxNndqIx.js deleted file mode 100644 index de89ffbc..00000000 --- a/assets/public_gamedevtree_docs_bars.md.CxNndqIx.js +++ /dev/null @@ -1,7 +0,0 @@ -import{_ as s,c as t,o as a,a5 as e}from"./chunks/framework.CK8QU5WH.js";const k=JSON.parse('{"title":"Bars","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/bars.md","filePath":"public/gamedevtree/docs/bars.md"}'),i={name:"public/gamedevtree/docs/bars.md"},n=e(`

Bars ​

Bars let you display information in a more direct way. It can be a progress bar, health bar, capacity gague, or anything else.

Bars are defined like other Big Features:

js
    bars: {
-        bigBar: {
-            display() {return "Blah"},
-            etc
-        }
-        etc
-    }

Features:

  • direction: UP, DOWN, LEFT, or RIGHT (not Strings). Determines the direction that the bar is filled as it progresses. RIGHT means from left to right.

  • width, height: The size in pixels of the bar, but as Numbers (no "px" at the end)

  • progress(): A function that returns the portion of the bar that is filled, from "empty" at 0 to "full" at 1. (Nothing bad happens if the value goes out of these bounds, and it can be a number or Decimal).

  • display(): optional, A function that returns text to be displayed on top of the bar, can use HTML.

  • unlocked(): optional, A function returning a bool to determine if the bar is visible or not. Default is unlocked.

  • baseStyle, fillStyle, borderStyle, textStyle: Optional, Apply CSS to the unfilled portion, filled portion, border, and display text on the bar, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the bar was stored under, for convenient access. The bar in the example's id is "bigBar".

`,6),r=[n];function l(o,p,h,d,c,u){return a(),t("div",null,r)}const b=s(i,[["render",l]]);export{k as __pageData,b as default}; diff --git a/assets/public_gamedevtree_docs_bars.md.CxNndqIx.lean.js b/assets/public_gamedevtree_docs_bars.md.CxNndqIx.lean.js deleted file mode 100644 index 014055a0..00000000 --- a/assets/public_gamedevtree_docs_bars.md.CxNndqIx.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as t,o as a,a5 as e}from"./chunks/framework.CK8QU5WH.js";const k=JSON.parse('{"title":"Bars","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/bars.md","filePath":"public/gamedevtree/docs/bars.md"}'),i={name:"public/gamedevtree/docs/bars.md"},n=e("",6),r=[n];function l(o,p,h,d,c,u){return a(),t("div",null,r)}const b=s(i,[["render",l]]);export{k as __pageData,b as default}; diff --git a/assets/public_gamedevtree_docs_basic-layer-breakdown.md.rhKMtsLX.js b/assets/public_gamedevtree_docs_basic-layer-breakdown.md.rhKMtsLX.js deleted file mode 100644 index 53b1f926..00000000 --- a/assets/public_gamedevtree_docs_basic-layer-breakdown.md.rhKMtsLX.js +++ /dev/null @@ -1,28 +0,0 @@ -import{_ as s,c as i,o as a,a5 as n}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Basic layer breakdown","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/basic-layer-breakdown.md","filePath":"public/gamedevtree/docs/basic-layer-breakdown.md"}'),e={name:"public/gamedevtree/docs/basic-layer-breakdown.md"},t=n(`

Basic layer breakdown ​

This is a very minimal layer with minimal features. Most things will require additional features.

js
    p: {
-        startData() { return {                  // startData is a function that returns default data for a layer. 
-            unlocked: false,                    // You can add more variables here to add them to your layer.
-            points: new Decimal(0),             // "points" is the internal name for the main resource of the layer.
-        }},
-
-        color: "#FE0102",                       // The color for this layer, which affects many elements
-        resource: "prestige points",            // The name of this layer's main prestige resource
-        row: 0,                                 // The row this layer is on (0 is the first row)
-
-        baseResource: "points",                 // The name of the resource your prestige gain is based on
-        baseAmount() {return player.points},    // A function to return the current value of that resource
-
-        requires: new Decimal(200),            // The amount of the base needed to  gain 1 of the prestige currency.
-                                                // Also the amount required to unlock the layer.
-        
-        type: "normal",                         // Determines the formula used for calculating prestige currency.
-        exponent: 0.5,                          // "normal" prestige gain is (currency^exponent)
-
-        gainMult() {                            // Returns your multiplier to your gain of the prestige resource
-            return new Decimal(1)               // Factor in any bonuses multiplying gain here
-        },
-        gainExp() {                             // Returns your exponent to your gain of the prestige resource
-            return new Decimal(1)
-        },
-
-        layerShown() {return true},             // Returns a bool for if this layer's node should be visible in the tree.
-    },
`,3),h=[t];function l(k,p,r,E,d,o){return a(),i("div",null,h)}const c=s(e,[["render",l]]);export{g as __pageData,c as default}; diff --git a/assets/public_gamedevtree_docs_basic-layer-breakdown.md.rhKMtsLX.lean.js b/assets/public_gamedevtree_docs_basic-layer-breakdown.md.rhKMtsLX.lean.js deleted file mode 100644 index d620274e..00000000 --- a/assets/public_gamedevtree_docs_basic-layer-breakdown.md.rhKMtsLX.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as i,o as a,a5 as n}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Basic layer breakdown","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/basic-layer-breakdown.md","filePath":"public/gamedevtree/docs/basic-layer-breakdown.md"}'),e={name:"public/gamedevtree/docs/basic-layer-breakdown.md"},t=n("",3),h=[t];function l(k,p,r,E,d,o){return a(),i("div",null,h)}const c=s(e,[["render",l]]);export{g as __pageData,c as default}; diff --git a/assets/public_gamedevtree_docs_buyables.md.DlXMZmV4.js b/assets/public_gamedevtree_docs_buyables.md.DlXMZmV4.js deleted file mode 100644 index ed024f85..00000000 --- a/assets/public_gamedevtree_docs_buyables.md.DlXMZmV4.js +++ /dev/null @@ -1,14 +0,0 @@ -import{_ as s,c as e,o as t,a5 as a}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Buyables","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/buyables.md","filePath":"public/gamedevtree/docs/buyables.md"}'),i={name:"public/gamedevtree/docs/buyables.md"},n=a(`

Buyables ​

Buyables are usually things that can be bought multiple times with scaling costs. If you set a respec function, the player can reset the purchases to get their currency back.

The amount of a buyable owned is a Decimal. You can get or set the amount of a buyable with getBuyableAmt(layer, id) and setBuyableAmt(layer, id, amt). You can use buyableEffect(layer, id) to get the current effects of a buyable.

Buyables should be formatted like this:

js
    buyables: {
-        rows: # of rows
-        cols: # of columns
-        respec() {}, //**optional**, implement it to reset things and give back your currency.
-                     // Having this function makes a respec button appear
-        respecText:// **optional**, text that appears on the respec button
-        showRespecButton(){} //**optional**, a function determining whether or not to show the button. Defaults to true if absent.
-        sellOneText, sellAllText:// **optional**, text that appears on the "sell one" and "sell all" buttons respectively (if you are using them)
-        11: {
-            display() {return "Blah"},
-            etc
-        }
-        etc
-    }

Features:

  • title: optional, displayed at the top in a larger font It can also be a function that returns updating text.

  • cost(): cost for buying the next buyable. Can have an optional argument "x" to calculate the cost of the x+1th object, but needs to use "current amount" as a default value for x. (x is a Decimal). Can return an object if there are multiple currencies.

  • effect(): optional, A function that calculates and returns the current values of bonuses of this buyable. Can return a value or an object containing multiple values.

  • display(): A function returning everything that should be displayed on the buyable after the title, likely including the description, amount bought, cost, and current effect. Can use basic HTML.

  • unlocked(): optional, A function returning a bool to determine if the buyable is visible or not. Default is unlocked.

  • canAfford(): A function returning a bool to determine if you can buy one of the buyables.

  • buy(): A function that implements buying one of the buyable, including spending the currency.

  • buyMax(): optional, A function that implements buying as many of the buyable as possible.

  • style: Optional, Applies CSS to this buyable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the buyable was stored under, for convenient access. The buyable in the example's id is 11.

Sell One/Sell All:

Including a sellOne or sellAll function will cause an additional button to appear beneath the buyable. They are functionally identical, but "sell one" appears above "sell all". You can also use them for other things.

sellOne/sellAll(): optional, Called when the button is pressed. The standard use would be to decrease/reset the amount of the buyable, And possibly return some currency to the player.

canSellOne/canSellAll(): optional, booleans determining whether or not to show the buttons. If "canSellOne/All" is absent but "sellOne/All" is present, the appropriate button will always show.

`,11),l=[n];function o(p,h,r,u,c,k){return t(),e("div",null,l)}const b=s(i,[["render",o]]);export{y as __pageData,b as default}; diff --git a/assets/public_gamedevtree_docs_buyables.md.DlXMZmV4.lean.js b/assets/public_gamedevtree_docs_buyables.md.DlXMZmV4.lean.js deleted file mode 100644 index e3cb689a..00000000 --- a/assets/public_gamedevtree_docs_buyables.md.DlXMZmV4.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as e,o as t,a5 as a}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Buyables","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/buyables.md","filePath":"public/gamedevtree/docs/buyables.md"}'),i={name:"public/gamedevtree/docs/buyables.md"},n=a("",11),l=[n];function o(p,h,r,u,c,k){return t(),e("div",null,l)}const b=s(i,[["render",o]]);export{y as __pageData,b as default}; diff --git a/assets/public_gamedevtree_docs_challenges.md.DEdsv7kR.js b/assets/public_gamedevtree_docs_challenges.md.DEdsv7kR.js deleted file mode 100644 index a4b9dfa4..00000000 --- a/assets/public_gamedevtree_docs_challenges.md.DEdsv7kR.js +++ /dev/null @@ -1,9 +0,0 @@ -import{_ as e,c as a,o as t,a5 as s}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Challenges","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/challenges.md","filePath":"public/gamedevtree/docs/challenges.md"}'),i={name:"public/gamedevtree/docs/challenges.md"},n=s(`

Challenges ​

Useful functions for dealing with Challenges and implementing their effects:

  • inChallenge(layer, id): determine if the player is in a given challenge (or another challenge on the same layer that counts as this one)
  • hasChallenge(layer, id): determine if the player has completed the challenge
  • challengeCompletions(layer, id): determine how many times the player completed the challenge
  • challEffect(layer, id): Returns the current effects of the challenge, if any

Challenges are stored in the following format:

js
    challenges: {
-        rows: # of rows
-        cols: # of columns
-        11: {
-            name: "Ouch",
-            etc
-        }
-        etc
-    }

Each challenge should have an id where the first digit is the row and the second digit is the column. Individual Challenges can have these features:

  • name: Name of the challenge, can be a string or a function. Can use basic HTML.

  • challengeDescription: A description of what makes the challenge a challenge. You will need to implement these elsewhere It can also be a function that returns updating text. Can use basic HTML.

  • rewardDescription: A description of the reward's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

  • rewardEffect(): optional, A function that calculates and returns the current values of any bonuses from the reward. Can return a value or an object containing multiple values. Can use basic HTML.

  • rewardDisplay(): optional, A function that returns a display of the current effects of the reward with formatting. Default behavior is to just display the a number appropriately formatted.

  • goal: A Decimal for the amount of currency required to beat the challenge. By default, the goal is in basic Points. The goal can also be a function if its value changes.

  • unlocked(): optional, A function returning a bool to determine if the challenge is visible or not. Default is unlocked.

  • onComplete() - optional, this function will be called when the challenge is completed when previously incomplete.

  • countsAs: optional, If a challenge combines the effects of other challenges in this layer, you can use this. An array of challenge ids. The player is effectively in all of those challenges when in the current one.

By default, challenges use basic Points for the goal. You can change that using these features.

  • currencyDisplayName: optional, the name to display for the currency for the goal

  • currencyInternalName: optional, the internal name for that currency

  • currencyLayer: optional, the internal name of the layer that currency is stored in. If it's not in a layer, omit. If it's not stored directly in a layer, instead use the next feature.

  • currencyLocation: optional, if your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

  • completionLimit: optional, the amount of times you can complete this challenge. Default is 1 completion.

  • style: Optional, Applies CSS to this challenge, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the challenge was stored under, for convenient access. The challenge in the example's id is 11.

`,9),l=[n];function o(h,r,c,p,g,u){return t(),a("div",null,l)}const y=e(i,[["render",o]]);export{f as __pageData,y as default}; diff --git a/assets/public_gamedevtree_docs_challenges.md.DEdsv7kR.lean.js b/assets/public_gamedevtree_docs_challenges.md.DEdsv7kR.lean.js deleted file mode 100644 index e31db671..00000000 --- a/assets/public_gamedevtree_docs_challenges.md.DEdsv7kR.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as s}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Challenges","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/challenges.md","filePath":"public/gamedevtree/docs/challenges.md"}'),i={name:"public/gamedevtree/docs/challenges.md"},n=s("",9),l=[n];function o(h,r,c,p,g,u){return t(),a("div",null,l)}const y=e(i,[["render",o]]);export{f as __pageData,y as default}; diff --git a/assets/public_gamedevtree_docs_clickables.md.Cyab8uw5.js b/assets/public_gamedevtree_docs_clickables.md.Cyab8uw5.js deleted file mode 100644 index 7b2a1c56..00000000 --- a/assets/public_gamedevtree_docs_clickables.md.Cyab8uw5.js +++ /dev/null @@ -1,13 +0,0 @@ -import{_ as s,c as i,o as a,a5 as e}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Clickables","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/clickables.md","filePath":"public/gamedevtree/docs/clickables.md"}'),t={name:"public/gamedevtree/docs/clickables.md"},l=e(`

Clickables ​

Clickables are any kind of thing that you can click for an effect. They're a more generalized version of Buyables.

DO NOT USE THESE TO MAKE THINGS THAT YOU CLICK REPEATEDLY FOR A BONUS BECAUSE THOSE ARE AWFUL.

There are several differences between the two. One is that a buyable's saved data is its amount as a Decimal, while Clickables store a "state" which can be a number or string, but not Decimal, array, or object). Buyables have a number of extra features which you can see on their page. Clickables also have a smaller default size.

You can get and set a clickable's state with getClickableState(layer, id) and setClickableState(layer, id, state). You can use clickableEffect(layer, id) to get the current effects of a clickable.

Clickables should be formatted like this:

js
    clickables: {
-        rows: # of rows
-        cols: # of columns
-        masterButtonPress() // **optional** If this is present, an additional button will appear above the clickables.
-                            // pressing it will call the function.
-        masterButtonText: "Press me!" // **optional** text to display on the Master Button
-        showMasterButton(){} //**optional**, a function determining whether or not to show the button. Defaults to true if absent.
-        11: {
-            display() {return "Blah"},
-            etc
-        }
-        etc
-    }

Features:

  • title: optional, displayed at the top in a larger font It can also be a function that returns updating text.

  • effect(): optional, A function that calculates and returns the current values of bonuses of this clickable. Can return a value or an object containing multiple values.

  • display(): A function returning everything that should be displayed on the clickable after the title, likely changing based on its state. Can use basic HTML.

  • unlocked(): optional, A function returning a bool to determine if the clickable is visible or not. Default is unlocked.

  • canClick(): A function returning a bool to determine if you can click the clickable.

  • onClick(): A function that implements clicking one of the clickable.

  • style: Optional, Applies CSS to this clickable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

  • id: Assigned automagically. It's the "key" which the clickable was stored under, for convenient access. The clickable in the example's id is 11.

`,9),n=[l];function h(p,o,r,c,k,d){return a(),i("div",null,n)}const E=s(t,[["render",h]]);export{g as __pageData,E as default}; diff --git a/assets/public_gamedevtree_docs_clickables.md.Cyab8uw5.lean.js b/assets/public_gamedevtree_docs_clickables.md.Cyab8uw5.lean.js deleted file mode 100644 index d6d02c5a..00000000 --- a/assets/public_gamedevtree_docs_clickables.md.Cyab8uw5.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as i,o as a,a5 as e}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Clickables","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/clickables.md","filePath":"public/gamedevtree/docs/clickables.md"}'),t={name:"public/gamedevtree/docs/clickables.md"},l=e("",9),n=[l];function h(p,o,r,c,k,d){return a(),i("div",null,n)}const E=s(t,[["render",h]]);export{g as __pageData,E as default}; diff --git a/assets/public_gamedevtree_docs_custom-tab-layouts.md.DO3JHVjV.js b/assets/public_gamedevtree_docs_custom-tab-layouts.md.DO3JHVjV.js deleted file mode 100644 index ac532ca7..00000000 --- a/assets/public_gamedevtree_docs_custom-tab-layouts.md.DO3JHVjV.js +++ /dev/null @@ -1,9 +0,0 @@ -import{_ as s,c as i,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const E=JSON.parse('{"title":"Custom tab layouts","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/custom-tab-layouts.md","filePath":"public/gamedevtree/docs/custom-tab-layouts.md"}'),e={name:"public/gamedevtree/docs/custom-tab-layouts.md"},n=t(`

Custom tab layouts ​

Note: If you are using subtabs, tabFormat is used differently, but you still use the same format within each subtabs. See here for more on subtabs

Custom tab layouts can be used to do basically anything in a tab window, especially combined with the "style" layer feature. The tabFormat feature is an array of things, like this:

js
    tabFormat: ["main-display",
-            ["prestige-button", function(){return "Melt your points into "}],
-            "blank",
-            ["display-text",
-                function() {return 'I have ' + format(player.points) + ' pointy points!'},
-                {"color": "red", "font-size": "32px", "font-family": "Comic Sans MS"}],
-            "blank",
-            ["toggle", ["c", "beep"]],
-            "milestones", "blank", "blank", "upgrades"]

It is a list of components, which can be either just a name, or an array with arguments. If it's an array, the first item is the name of the component, the second is the data passed into it, and the third (optional) applies a CSS style to it with a "CSS object", where the keys are CSS attributes.

These are the existing components, but you can create more in v.js:

  • display-text: Displays some text (can use basic HTML). The argument is the text to display. It can also be a function that returns updating text.

  • raw-html: Displays some basic HTML, can also be a function.

  • blank: Adds empty space. The default dimensions are 8px x 17px. The argument changes the dimensions. If it's a single value (e.g. "20px"), that determines the height. If you have a pair of arguments, the first is width and the second is height.

  • row: Display a list of components horizontally. The argument is an array of components in the tab layout format.

  • column: Display a list of components vertically. The argument is an array of components in the tab layout format. This is useful to display columns within a row.

  • main-display: The text that displays the main currency for the layer and its effects.

  • resource-display: The text that displays the currency that this layer is based on, as well as the best and/or total values for this layer's prestige currency (if they are put in startData for this layer)

  • prestige-button: The argument is a string that the prestige button should say before the amount of currency you will gain. It can also be a function that returns updating text.

  • upgrades, milestones, challs, achievements: Display the upgrades, milestones, and challenges for a layer, as appropriate.

  • buyables, clickables: Display all of the buyables/clickables for this layer, as appropriate. The argument optional, and is the size of the boxes in pixels.

  • microtabs: Display a set of subtabs for an area. The argument is the name of the set of microtabs in the "microtabs" feature.

  • bar: Display a bar. The argument is the id of the bar to display.

  • infobox: Display an infobox. The argument is the id of the infobox to display.

  • toggle: A toggle button that toggles a bool value. The data is a pair that identifies what bool to toggle, [layer, id]

The rest of the components are sub-components. They can be used just like other components, but are typically part of another component.

  • upgrade, milestone, chall, buyable, clickable, achievement: An individual upgrade, challenge, etc. The argument is the id. This can be used if you want to have upgrades split up across multiple subtabs, for example.

  • respec-button, master-button: The respec and master buttons for buyables and clickables, respectively.

  • sell-one, sell-all: The "sell one" and "sell all" for buyables, respectively. The argument is the id of the buyable.

`,9),l=[n];function h(p,o,r,k,u,d){return a(),i("div",null,l)}const c=s(e,[["render",h]]);export{E as __pageData,c as default}; diff --git a/assets/public_gamedevtree_docs_custom-tab-layouts.md.DO3JHVjV.lean.js b/assets/public_gamedevtree_docs_custom-tab-layouts.md.DO3JHVjV.lean.js deleted file mode 100644 index afaa842d..00000000 --- a/assets/public_gamedevtree_docs_custom-tab-layouts.md.DO3JHVjV.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as i,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const E=JSON.parse('{"title":"Custom tab layouts","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/custom-tab-layouts.md","filePath":"public/gamedevtree/docs/custom-tab-layouts.md"}'),e={name:"public/gamedevtree/docs/custom-tab-layouts.md"},n=t("",9),l=[n];function h(p,o,r,k,u,d){return a(),i("div",null,l)}const c=s(e,[["render",h]]);export{E as __pageData,c as default}; diff --git a/assets/public_gamedevtree_docs_getting-started.md.DzfYHbWF.js b/assets/public_gamedevtree_docs_getting-started.md.DzfYHbWF.js deleted file mode 100644 index 6f316a88..00000000 --- a/assets/public_gamedevtree_docs_getting-started.md.DzfYHbWF.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o,a5 as i}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Getting started","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/getting-started.md","filePath":"public/gamedevtree/docs/getting-started.md"}'),a={name:"public/gamedevtree/docs/getting-started.md"},n=i('

Getting started ​

Welcome to The Modding Tree!

Using the Modding Tree, at its simplest level, just requires getting a copy of it onto your computer. However, if you do it the right way, it will help in many ways.

Don't let the word "Github" scare you away. It's actually much easier to use than most people think, especially because most people use it the hard way. The key is Github Desktop, which lets you do everything you need to, without even touching the command line.

The benefits of using Github:

  • It makes it much, much easier to update The Modding Tree.
  • You can share your work without any extra effort using githack, or with a bit more effort, set up a github.io site.
  • It lets you undo changes to your code, and to have multiple versions of it.
  • It lets you collaborate with other people, if you want to.

Getting set up with Github and The Modding Tree: ​

  1. Install Github Desktop and Visual Studio Code.

  2. Make a Github account. You can handle this on your own.

  3. Log in on your browser, and go back to The Modding Tree page. At the top right, there should be a button that says "fork". Click on it, and then on your username. You now have your own fork, or copy, of The Modding Tree.

  4. Open Github Desktop and log in. Ignore everything else and choose "clone a repository". A "repository" is basically a "Github project", like The Modding Tree. "Cloning" is downloading a copy of the repository to your computer.

  5. Look for The Modding Tree in the list of repositiories (it should be the only one) and click "clone".

  6. Select that you're using it for your own purposes, and click continue. It will download the files and handle everything.

Using your repository ​

  1. Click on "show in finder" to the right, and then open index.html. This will let you view and test your project!

  2. To edit your project, click "open in VSCode" in Github Desktop.

  3. Open mod.js in VSCode, and look at the top part where it says "modInfo". On the lines below that, change the mod's name to whatever you want, and change the id as well. (It can be any string value, and it's used to determine where the savefile is. Make it something that's probably unique, and don't change it again later.)

  4. Save game.js, and then reload index.html. The title on the tab, as well as on the info page, will now be the new ones!

  5. Go back to Github Desktop. It's time to save your changes into the git system by making a "commit".

  6. At the bottom right corner, add a summary of your changes, and then click "commit to master".

  7. Finally, at the top middle, click "push origin" to push your changes out onto the online repository.

  8. You can view your project on line, or share it with others, by going to https://raw.githack.com/[YOUR-GITHUB-USERNAME]/The-Modding-Tree/master/index.html

And now, you have successfully used Github! You can look at the documentation to see how The Modding Tree's system works and to make your mod a reality.

',11),r=[n];function s(h,l,u,d,p,c){return o(),t("div",null,r)}const y=e(a,[["render",s]]);export{m as __pageData,y as default}; diff --git a/assets/public_gamedevtree_docs_getting-started.md.DzfYHbWF.lean.js b/assets/public_gamedevtree_docs_getting-started.md.DzfYHbWF.lean.js deleted file mode 100644 index c4a90491..00000000 --- a/assets/public_gamedevtree_docs_getting-started.md.DzfYHbWF.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o,a5 as i}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Getting started","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/getting-started.md","filePath":"public/gamedevtree/docs/getting-started.md"}'),a={name:"public/gamedevtree/docs/getting-started.md"},n=i("",11),r=[n];function s(h,l,u,d,p,c){return o(),t("div",null,r)}const y=e(a,[["render",s]]);export{m as __pageData,y as default}; diff --git a/assets/public_gamedevtree_docs_infoboxes.md.9a47XYCg.js b/assets/public_gamedevtree_docs_infoboxes.md.9a47XYCg.js deleted file mode 100644 index 54076798..00000000 --- a/assets/public_gamedevtree_docs_infoboxes.md.9a47XYCg.js +++ /dev/null @@ -1,7 +0,0 @@ -import{_ as s,c as e,o as i,a5 as a}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Infoboxes","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/infoboxes.md","filePath":"public/gamedevtree/docs/infoboxes.md"}'),t={name:"public/gamedevtree/docs/infoboxes.md"},n=a(`

Infoboxes ​

Infoboxes are good for displaying "lore", or story elements, as well as for explaining complicated things.

In the default tab layout, the first infobox will be displayed at the very top of the tab.

Infoboxes are defined like other Big Features:

js
    infoboxes: {
-        infobox: {
-            display() {return "Blah"},
-            etc
-        }
-        etc
-    }

Features:

  • title: The text displayed above the main box. Can be a function to be dynamic, and can use basic HTML.

  • body: The text displayed inside the box. Can be a function to be dynamic, and can use basic HTML.

  • style, titleStyle, bodyStyle: Optional, Apply CSS to the infobox, or to the title button or body of the infobox, in the form of an object where the keys are CSS attributes, and the values are the Values for those attributes (both as strings).

  • unlocked(): optional, A function returning a bool to determine if the infobox is visible or not. Default is unlocked.

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the bar was stored under, for convenient access. The bar in the example's id is "bigBar".

`,7),o=[n];function l(p,r,h,d,c,b){return i(),e("div",null,o)}const f=s(t,[["render",l]]);export{u as __pageData,f as default}; diff --git a/assets/public_gamedevtree_docs_infoboxes.md.9a47XYCg.lean.js b/assets/public_gamedevtree_docs_infoboxes.md.9a47XYCg.lean.js deleted file mode 100644 index 128a5d4c..00000000 --- a/assets/public_gamedevtree_docs_infoboxes.md.9a47XYCg.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as e,o as i,a5 as a}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Infoboxes","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/infoboxes.md","filePath":"public/gamedevtree/docs/infoboxes.md"}'),t={name:"public/gamedevtree/docs/infoboxes.md"},n=a("",7),o=[n];function l(p,r,h,d,c,b){return i(),e("div",null,o)}const f=s(t,[["render",l]]);export{u as __pageData,f as default}; diff --git a/assets/public_gamedevtree_docs_layer-features.md.y6Ef1VMc.js b/assets/public_gamedevtree_docs_layer-features.md.y6Ef1VMc.js deleted file mode 100644 index 8e751749..00000000 --- a/assets/public_gamedevtree_docs_layer-features.md.y6Ef1VMc.js +++ /dev/null @@ -1,16 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Layer Features","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/layer-features.md","filePath":"public/gamedevtree/docs/layer-features.md"}'),s={name:"public/gamedevtree/docs/layer-features.md"},n=i(`

Layer Features ​

This is a more comprehensive list of established features to add to layers. You can add more freely, if you want to have other functions or values associated with your layer. These have special functionality, though.

You can make almost any value dynamic by using a function in its place, including all display strings and styling/color features.

Key:

  • No label: This is required and the game will crash if it isn't included.
  • sometimes required: This is may be required, depending on other things in the layer.
  • optional: You can leave this out if you don't intend to use that feature for the layer.

Layer Definition features ​

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar to access the save value. It makes copying code to new layers easier. It is also assigned to all upgrades and buyables and such.

  • name: Optional, used in reset confirmations (and maybe other places). If absent, it just uses the layer's id.

  • startData(): A function to return the default save data for this layer. Add any variables you have to it. Any nonstandard Decimal variables need to be added to convertToDecimal as well. Standard values: Required: unlocked: a bool determining if this layer is unlocked or not points: a Decimal, the main currency for the layer Optional: total: A Decimal, tracks total amount of main prestige currency best: A Decimal, tracks highest amount of main prestige currency unlockOrder: used to keep track of relevant layers unlocked before this one.

  • color: A color associated with this layer, used in many places. (A string in hex format with a #)

  • row: The row of the layer, starting at 0. This affects where the node appears on the tree, and which resets affect the layer.

     Using "side" instead of a number will cause the layer to appear off to the side as a smaller node (useful for achievements
- and statistics). Side layers are not affected by resets unless you add a doReset to them.
-

  • resource: Name of the main currency you gain by resetting on this layer.

  • effect(): optional, A function that calculates and returns the current values of any bonuses inherent to the main currency. Can return a value or an object containing multiple values. You will also have to implement the effect where it is applied.

  • effectDescription: optional, A function that returns a description of this effect. If the text stays constant, it can just be a string.

  • layerShown(): A function returning a bool which determines if this layer's node should be visible on the tree. It can also return "ghost", which will hide the layer, but its node will still take up space in the tree.

  • hotkeys: optional, An array containing information on any hotkeys associated with this layer:

    js
    hotkeys: [
-    {key: "p", // What the hotkey button is. Use uppercase if it's combined with shift, or "ctrl+x" if ctrl is.
-    desc: "p: reset your points for prestige points", // The description of the hotkey used in the How To Play
-    onPress(){if (player.p.unlocked) doReset("p")}}, // This function is called when the hotkey is pressed.
-],

  • style: optional, a "CSS object" where the keys are CSS attributes ,containing any CSS that should affect this layer's entire tab.

  • tabFormat: optional, use this if you want to add extra things to your tab or change the layout. See here for more info.

  • midsection: optional, an alternative to tabFormat, which is inserted in between Milestones and Buyables in the standard tab layout. (cannot do subtabs)

Big features (all optional) ​

Prestige formula features ​

  • type: optional, Determines which prestige formula you use. Defaults to "none". "normal": The amount of currency you gain is independent of its current amount (like Prestige). formula before bonuses is based on baseResource^exponent "static": The cost is dependent on your total after reset. formula before bonuses is based on base^(x^exponent) "custom": You can define everything, from the calculations to the text on the button, yourself. (See more at the bottom) "none": This layer does not prestige, and therefore does not need any of the other features in this section.

  • baseResource: The name of the resource that determines how much of the main currency you gain on reset.

  • baseAmount(): A function that gets the current value of the base resource.

  • requires: A Decimal, the amount of the base needed to gain 1 of the prestige currency. Also the amount required to unlock the layer. You can instead make this a function, to make it harder if another layer was unlocked first (based on unlockOrder).

  • exponent: Used as described above.

  • base: sometimes required, required for "static" layers, used as described above. If absent, defaults to 2. Must be greater than 1.

  • roundUpCost: optional, a bool, which is true if the resource cost needs to be rounded up. (use if the base resource is a "static" currency.)

  • canBuyMax(): sometimes required, required for static layers, function used to determine if buying max is permitted.

  • gainMult(), gainExp(): optional, Functions that calculate the multiplier and exponent on resource gain from upgrades and boosts and such. Plug in any bonuses here.

  • onPrestige(gain): optional, A function that triggers when this layer prestiges, just before you gain the currency. Can be used to have secondary resource gain on prestige, or to recalculate things or whatnot.

  • resetDesc: optional, use this to replace "Reset for " on the Prestige button with something else.

  • prestigeButtonText(): Sometimes required, Use this to make the entirety of the text a Prestige button contains. Only required for custom layers, but usable by all types.

Tree/node features ​

  • symbol: optional, the text that appears on this layer's node. Default is the layer id with the first letter capitalized

  • position: optional, Determines the horizontal position of the layer in its row. By default, it uses the layer id, and layers are sorted in alphabetical order.

  • branches: optional, an array of layer ids. On a tree, a line will appear from this layer to all of the layers in the list. Alternatively, an entry in the array can be a 2-element array consisting of the layer id and a color value. The color value can either be a string with a hex color code, or a number from 1-3 (theme-affected colors)

  • nodeStyle: optional, a CSS object, where the keys are CSS attributes, which styles this layer's node on the tree

  • tooltip() / tooltipLocked(): optional Functions that return text, which is the tooltip for the node when the layer is unlocked or locked, respectively. By default the tooltips behave the same as in the original Prestige Tree.

Other features ​

  • doReset(resettingLayer): optional, is triggered when a layer on a row greater than or equal to this one does a reset. The default behavior is to reset everything on the row, but only if it was triggered by a layer in a higher row. (doReset is always called for side layers, but for these the default behavior is to reset nothing.)

              If you want to keep things, determine what to keep based on the resettingLayer, milestones, and such, then call
-          resetLayerData(layer, keep), where layer is this layer, and keep is an array of the names of things to keep.
-          It can include things like "points", "best", "total" (for this layer's prestige currency), "upgrades", 
-          any unique variables like "generatorPower", etc.
-          If you want to only keep specific upgrades or something like that, save them in a separate variable, then
-          call layerDataReset, and then set player[layer].upgrades to the saved upgrades.
-

  • update(diff): optional, this function is called every game tick. Use it for any passive resource production or time-based things. diff is the time since the last tick. Suggestion: use addPoints(layer, gain) when generating points to automatically update the best and total amounts.

  • automate(): optional, this function is called every game tick, after production. Use it to activate any autobuyers or auto-resets or similar on this layer, if appropriate.

  • resetsNothing: optional, returns true if this layer shouldn't trigger any resets when you prestige.

  • increaseUnlockOrder: optional, an array of layer ids. When this layer is unlocked for the first time, the unlockOrder value for any not-yet-unlocked layers in this list increases. This can be used to make them harder to unlock.

  • shouldNotify: optional, a function to return true if this layer should be highlighted in the tree. The layer will automatically be highlighted if you can buy an upgrade whether you have this or not.

  • componentStyles: optional, An object that contains a set of functions returning CSS objects. Each of these will be applied to any components on the layer with the type of its id. Example:

js
        componentStyles: {
-            "challenge"() {return {'height': '200px'}},
-            "prestige-button"() {return {'color': '#AA66AA'}},
-        },

Custom Prestige type ​

  • getResetGain(): For custom prestige type, Returns how many points you should get if you reset now. You can call getResetGain(this.layer, useType = "static") or similar to calculate what your gain would be under another prestige type (provided you have all of the required features in the layer.)

  • getNextAt(canMax=false): For custom prestige type, Returns how many of the base currency you need to get to the next point. canMax is an optional variable used with Static-ish layers to differentiate between if it's looking for the first point you can reset at, or the requirement for any gain at all. (Supporting both is good). You can also call getNextAt(this.layer, canMax=false, useType = "static") or similar to calculate what your next at would be under another prestige type (provided you have all of the required features in the layer.)

  • canReset(): For custom prestige type, return true only if you have the resources required to do a prestige here.

`,18),o=[n];function r(l,h,u,p,c,d){return a(),t("div",null,o)}const f=e(s,[["render",r]]);export{g as __pageData,f as default}; diff --git a/assets/public_gamedevtree_docs_layer-features.md.y6Ef1VMc.lean.js b/assets/public_gamedevtree_docs_layer-features.md.y6Ef1VMc.lean.js deleted file mode 100644 index 57b1fd85..00000000 --- a/assets/public_gamedevtree_docs_layer-features.md.y6Ef1VMc.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Layer Features","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/layer-features.md","filePath":"public/gamedevtree/docs/layer-features.md"}'),s={name:"public/gamedevtree/docs/layer-features.md"},n=i("",18),o=[n];function r(l,h,u,p,c,d){return a(),t("div",null,o)}const f=e(s,[["render",r]]);export{g as __pageData,f as default}; diff --git a/assets/public_gamedevtree_docs_main-mod-info.md.DYvAg_3w.js b/assets/public_gamedevtree_docs_main-mod-info.md.DYvAg_3w.js deleted file mode 100644 index 57d90f07..00000000 --- a/assets/public_gamedevtree_docs_main-mod-info.md.DYvAg_3w.js +++ /dev/null @@ -1,5 +0,0 @@ -import{_ as i,c as e,o as t,a5 as s}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"mod.js","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/main-mod-info.md","filePath":"public/gamedevtree/docs/main-mod-info.md"}'),a={name:"public/gamedevtree/docs/main-mod-info.md"},n=s(`

mod.js ​

All of the code and data that you're likely to edit is here in mod.js! Everything in mod.js will not be altered by updates, besides the addition of new things.

Here's a breakdown of what's in it:

  • modInfo is where most of the basic configuration for the mod is. It contains:

    • name: The name of your mod. (a string)
    • id: The id for your mod, a unique string that is used to determine savefile location. Setting it is important!
    • author: The name of the author, displayed in the info tab.
    • pointsName: This changes what is displayed instead of "points" for the main currency. (It does not affect it in the code.)
    • discordName, discordLink: If you have a Discord server or other discussion place, you can add a link to it. "discordName" is the text on the link, and "discordLink" is the url of an invite. If you're using a Discord invite, please make sure it's set to never expire.
    • changelogLink: You can use this to set a link to a page where your changelog for the game is displayed.
    • offlineLimit: The maximum amount of offline time that the player can accumulate, in hours. Any extra time is lost. (a number) This is useful because most of these mods are fast-paced enough that too much offline time ruins the balance, such as the time in between updates. That is why I suggest developers disable offline time on their own savefile.
    • initialStartPoints: A Decimal for the amount of points a new player should start with.

  • VERSION is used to describe the current version of your mod. It contains: num: The mod's version number, displayed at the top right of the tree tab. name: The version's name, displayed alongside the number in the info tab.

  • doNotCallTheseFunctionsEveryTick is very important. TMT calls every function anywhere in "layers" every tick to store the result, unless specifically told not to. Functions that have are used to do an action need to be identified. "Official" functions (those in the documentation) are all fine, but if you make any new ones, add their names to this array.

js
// (The ones here are examples, all official functions are already taken care of)
-var doNotCallTheseFunctionsEveryTick = ["doReset", "buy", "onPurchase", "blowUpEverything"]

  • getStartPoints(): A function to determine the amount of points the player starts with after a reset. (returns a Decimal value)

  • canGenPoints(): A function returning a boolean for if points should be generated. Use this if you want an upgrade to unlock generating points.

  • getPointGen(): A function that calculates your points per second. Anything that affects your point gain should go into the calculation here.

  • addedPlayerData(): A function that returns any non-layer-related data that you want to be added to the save data and "player" object.

js
function addedPlayerData() { return {
-	weather: "Yes",
-	happiness: new Decimal(72),
-}}

  • displayThings: An array of functions used to display extra things at the top of the tree tab. Each function returns a string, which is a line to display (with basic HTML support). If a function returns nothing, nothing is displayed (and it doesn't take up a line).

  • isEndgame(): A function to determine if the player has reached the end of the game, at which point the "you win!" screen appears.

Less important things beyond this point!

  • maxTickLength(): Returns the maximum tick length, in milliseconds. Only really useful if you have something that reduces over time, which long ticks mess up (usually a challenge).
`,10),o=[n];function l(h,r,d,p,u,c){return t(),e("div",null,o)}const y=i(a,[["render",l]]);export{m as __pageData,y as default}; diff --git a/assets/public_gamedevtree_docs_main-mod-info.md.DYvAg_3w.lean.js b/assets/public_gamedevtree_docs_main-mod-info.md.DYvAg_3w.lean.js deleted file mode 100644 index 6479db6f..00000000 --- a/assets/public_gamedevtree_docs_main-mod-info.md.DYvAg_3w.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as i,c as e,o as t,a5 as s}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"mod.js","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/main-mod-info.md","filePath":"public/gamedevtree/docs/main-mod-info.md"}'),a={name:"public/gamedevtree/docs/main-mod-info.md"},n=s("",10),o=[n];function l(h,r,d,p,u,c){return t(),e("div",null,o)}const y=i(a,[["render",l]]);export{m as __pageData,y as default}; diff --git a/assets/public_gamedevtree_docs_milestones.md.DiBU9uxR.js b/assets/public_gamedevtree_docs_milestones.md.DiBU9uxR.js deleted file mode 100644 index cdf59fdc..00000000 --- a/assets/public_gamedevtree_docs_milestones.md.DiBU9uxR.js +++ /dev/null @@ -1,7 +0,0 @@ -import{_ as e,c as s,o as t,a5 as i}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Milestones","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/milestones.md","filePath":"public/gamedevtree/docs/milestones.md"}'),a={name:"public/gamedevtree/docs/milestones.md"},n=i(`

Milestones ​

Milestones are awarded to the player when they meet a certain goal, and give some benefit. Milestones should be formatted like this:

js
    milestones: {
-        0: {
-            requirementDesc: "123 waffles",
-        }
-        etc
-    }

You can use hasMilestone(layer, id) to determine if the player has a given milestone

Milestone features:

  • requirementDesc: A string describing the requirement for unlocking this milestone. Suggestion: Use a "total". It can also be a function that returns updating text. Can use basic HTML.

  • effectDesc: A string describing the reward for having the milestone. You will have to implement the reward elsewhere. It can also be a function that returns updating text. Can use basic HTML.

  • done(): A function returning a boolean to determine if the milestone should be awarded.

  • toggles: optional, Creates toggle buttons that appear on the milestone when it is unlocked. The toggles can toggle a given boolean value in a layer. It is defined as an array of paired items, one pair per toggle. The first is the internal name of the layer the value being toggled is stored in, and the second is the internal name of the variable to toggle. (e.g. [["b", "auto"], ["g", "auto"])

         **Tip:** Toggles are not de-set if the milestone becomes locked! In this case, you should also check if the player has the milestone.
-

  • style: Optional, Applies CSS to this milestone, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

  • unlocked(): Optional A function returning a boolean to determine if the milestone should be shown. If absent, it is always shown.

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the milestone was stored under, for convenient access. The milestone in the example's id is 0.

`,6),o=[n];function l(r,h,p,d,c,u){return t(),s("div",null,o)}const k=e(a,[["render",l]]);export{m as __pageData,k as default}; diff --git a/assets/public_gamedevtree_docs_milestones.md.DiBU9uxR.lean.js b/assets/public_gamedevtree_docs_milestones.md.DiBU9uxR.lean.js deleted file mode 100644 index 07e6c8e2..00000000 --- a/assets/public_gamedevtree_docs_milestones.md.DiBU9uxR.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as s,o as t,a5 as i}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Milestones","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/milestones.md","filePath":"public/gamedevtree/docs/milestones.md"}'),a={name:"public/gamedevtree/docs/milestones.md"},n=i("",6),o=[n];function l(r,h,p,d,c,u){return t(),s("div",null,o)}const k=e(a,[["render",l]]);export{m as __pageData,k as default}; diff --git a/assets/public_gamedevtree_docs_subtabs-and-microtabs.md.C75eZZin.js b/assets/public_gamedevtree_docs_subtabs-and-microtabs.md.C75eZZin.js deleted file mode 100644 index 3a33599f..00000000 --- a/assets/public_gamedevtree_docs_subtabs-and-microtabs.md.C75eZZin.js +++ /dev/null @@ -1,23 +0,0 @@ -import{_ as s,c as a,o as t,a5 as i}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Subtabs and Microtabs","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/subtabs-and-microtabs.md","filePath":"public/gamedevtree/docs/subtabs-and-microtabs.md"}'),e={name:"public/gamedevtree/docs/subtabs-and-microtabs.md"},n=i(`

Subtabs and Microtabs ​

Subtabs are separate sections of a tab that you can view by selecting one at the top of the tab. Microtabs are smaller areas that function in much the same way.

Subtabs are defined by using the tab format like this, where each element of tabFormat is given the name of that subtab:

js
    tabFormat: {
-        "Main tab": {
-            *subtab features*
-        },
-        "Other tab": {
-            *subtab features*
-        },
-
-        etc
-    },

Microtabs are defined similarly, and use the same features, but are defined in the "microtabs" feature. Each entry is a group of tabs which will appear in a microtabs component. The first set, "stuff", has 2 tabs, and the second, "otherStuff", has none.

js
    microtabs: {
-        stuff: {
-            first: {
-            *subtab features*
-            },
-            second: {
-            *subtab features*
-            },
-        },
-
-        otherStuff: {
-            // There could be another set of microtabs here
-        }
-    },

Normal subtabs and microtab subtabs both use the same features:

Features: ​

  • content: The tab layout code for the subtab, in the tab layout format

  • style: Optional, Applies CSS to the whole subtab when switched to, in the form of an "CSS Object", where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

  • buttonStyle: Optional, A CSS object, which affects the appearance of the button for that subtab.

  • unlocked(): Optional, a function to determine if the button for this subtab should be visible. By default, a subtab is always unlocked. (You can't use the "this" keyword in this function.)

`,9),l=[n];function h(p,r,o,k,c,d){return t(),a("div",null,l)}const E=s(e,[["render",h]]);export{u as __pageData,E as default}; diff --git a/assets/public_gamedevtree_docs_subtabs-and-microtabs.md.C75eZZin.lean.js b/assets/public_gamedevtree_docs_subtabs-and-microtabs.md.C75eZZin.lean.js deleted file mode 100644 index 56550de2..00000000 --- a/assets/public_gamedevtree_docs_subtabs-and-microtabs.md.C75eZZin.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as a,o as t,a5 as i}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Subtabs and Microtabs","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/subtabs-and-microtabs.md","filePath":"public/gamedevtree/docs/subtabs-and-microtabs.md"}'),e={name:"public/gamedevtree/docs/subtabs-and-microtabs.md"},n=i("",9),l=[n];function h(p,r,o,k,c,d){return t(),a("div",null,l)}const E=s(e,[["render",h]]);export{u as __pageData,E as default}; diff --git a/assets/public_gamedevtree_docs_updating-tmt.md.37YMR_q4.js b/assets/public_gamedevtree_docs_updating-tmt.md.37YMR_q4.js deleted file mode 100644 index 708ade09..00000000 --- a/assets/public_gamedevtree_docs_updating-tmt.md.37YMR_q4.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as o}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Updating The Modding Tree","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/updating-tmt.md","filePath":"public/gamedevtree/docs/updating-tmt.md"}'),i={name:"public/gamedevtree/docs/updating-tmt.md"},n=o('

Updating The Modding Tree ​

This tutorial assumes that you have used the Getting Started Tutorial, and are using Github Desktop and VSCode for your mod.

Here's what you have to do when there's a TMT update:

  1. Look at the changelog. It will warn you if the update will break anything or require any changes. Decide if you want to try to update.

  2. Open Github Desktop, and at the top middle, click "fetch origin". This will make Github Desktop get information about the update.

  3. Click where it says "current branch: master" at the top middle, and at the bottom of the thing that appears, click "choose a branch to merge into master.

  4. Select upstream/master. It will likely say there are conflicts, but you have tools to resolve them. Click "Merge upstream/master into master".

  5. A conflict happens when the things you're trying to merge have both made changes in the same place. Click "open in Visual Studio Code" next to the first file.

  6. Scroll down through the file, and look for the parts highlighted in red and green. One of these is your code, and the other is some code that will be modified by the update. Do your best to try to edit things to keep the updated changes, but keep your content.

  7. Continue to do this for all remaining challenges.

  8. Do any other changes required by the update, run the game, fix issues, etc.

',4),r=[n];function d(h,s,l,p,u,c){return a(),t("div",null,r)}const _=e(i,[["render",d]]);export{m as __pageData,_ as default}; diff --git a/assets/public_gamedevtree_docs_updating-tmt.md.37YMR_q4.lean.js b/assets/public_gamedevtree_docs_updating-tmt.md.37YMR_q4.lean.js deleted file mode 100644 index 18786d88..00000000 --- a/assets/public_gamedevtree_docs_updating-tmt.md.37YMR_q4.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as o}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Updating The Modding Tree","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/updating-tmt.md","filePath":"public/gamedevtree/docs/updating-tmt.md"}'),i={name:"public/gamedevtree/docs/updating-tmt.md"},n=o("",4),r=[n];function d(h,s,l,p,u,c){return a(),t("div",null,r)}const _=e(i,[["render",d]]);export{m as __pageData,_ as default}; diff --git a/assets/public_gamedevtree_docs_upgrades.md.Msxg1C07.js b/assets/public_gamedevtree_docs_upgrades.md.Msxg1C07.js deleted file mode 100644 index a6c48b0d..00000000 --- a/assets/public_gamedevtree_docs_upgrades.md.Msxg1C07.js +++ /dev/null @@ -1,9 +0,0 @@ -import{_ as e,c as s,o as t,a5 as a}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Upgrades","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/upgrades.md","filePath":"public/gamedevtree/docs/upgrades.md"}'),i={name:"public/gamedevtree/docs/upgrades.md"},n=a(`

Upgrades ​

Useful functions for dealing with Upgrades and implementing their effects:

  • hasUpgrade(layer, id): determine if the player has the upgrade
  • upgradeEffect(layer, id): Returns the current effects of the upgrade, if any
  • buyUpgrade(layer, id): Buys an upgrade directly (if affordable)

Hint: Basic point gain is calculated in mod.js's "getPointGen".

Upgrades are stored in the following format:

js
    upgrades: {
-        rows: # of rows
-        cols: # of columns
-        11: {
-            description: "Blah",
-            more features
-        }
-        etc
-    }

Each upgrade should have an id where the first digit is the row and the second digit is the column. Individual upgrades can have these features:

  • title: optional, displayed at the top in a larger font It can also be a function that returns updating text. Can use basic HTML.

  • description: A description of the upgrade's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

  • effect(): optional, A function that calculates and returns the current values of any bonuses from the upgrade. Can return a value or an object containing multiple values.

  • effectDisplay(): optional, A function that returns a display of the current effects of the upgrade with formatting. Default behavior is to just display the a number appropriately formatted. Can use basic HTML.

  • cost: A Decimal for the cost of the upgrade. By default, upgrades cost the main prestige currency for the layer.

  • unlocked(): optional, A function returning a bool to determine if the upgrade is visible or not. Default is unlocked.

  • onPurchase() - optional, this function will be called when the upgrade is purchased. Good for upgrades like "makes this layer act like it was unlocked first".

By default, upgrades use the main prestige currency for the layer. You can include these to change them (but it needs to be a Decimal):

  • currencyDisplayName: optional, the name to display for the currency for the upgrade

  • currencyInternalName: optional, the internal name for that currency

  • currencyLayer: optional, the internal name of the layer that currency is stored in. If it's not in a layer (like Points), omit. If it's not stored directly in a layer, instead use the next feature.

  • currencyLocation: optional, if your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

  • style: Optional, Applies CSS to this upgrade, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the upgrade was stored under, for convenient access. The upgrade in the example's id is 11.

`,10),r=[n];function l(o,p,h,d,u,c){return t(),s("div",null,r)}const y=e(i,[["render",l]]);export{f as __pageData,y as default}; diff --git a/assets/public_gamedevtree_docs_upgrades.md.Msxg1C07.lean.js b/assets/public_gamedevtree_docs_upgrades.md.Msxg1C07.lean.js deleted file mode 100644 index 445b3fbe..00000000 --- a/assets/public_gamedevtree_docs_upgrades.md.Msxg1C07.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as s,o as t,a5 as a}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Upgrades","description":"","frontmatter":{},"headers":[],"relativePath":"public/gamedevtree/docs/upgrades.md","filePath":"public/gamedevtree/docs/upgrades.md"}'),i={name:"public/gamedevtree/docs/upgrades.md"},n=a("",10),r=[n];function l(o,p,h,d,u,c){return t(),s("div",null,r)}const y=e(i,[["render",l]]);export{f as __pageData,y as default}; diff --git a/assets/public_kronos_Old Things_2.0-format-changes.md.CuPSOvPY.js b/assets/public_kronos_Old Things_2.0-format-changes.md.CuPSOvPY.js deleted file mode 100644 index ccb35125..00000000 --- a/assets/public_kronos_Old Things_2.0-format-changes.md.CuPSOvPY.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as o}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"2.0 format changes","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/Old Things/2.0-format-changes.md","filePath":"public/kronos/Old Things/2.0-format-changes.md"}'),n={name:"public/kronos/Old Things/2.0-format-changes.md"},i=o('

2.0 format changes ​

  • Temp format is changed from temp.something[layer] to temp[layer].something, for consistency
  • Challenges are now saved as an object with the amount of completions in each spot. (This will break saves.)
  • effectDisplay in Challenges and Upgrades no longer takes an argument, and neither does effect for Buyables
  • Buyable cost can take an argument for amount of buyables, but it needs to function if no argument is supplied (it should do the cost for the next purchase).
  • Generation of Points now happens in the main game loop (not in a layer update function), enabled by canGenPoints in game.js.
  • Changed fullLayerReset to layerDataReset, which takes an array of names of values to keep

In addition, many names were changed, mostly expanding abbreviations:

All instances of:

  • chall -> challenge
  • unl -> unlocked
  • upg -> upgrade (besides CSS)
  • amt -> amount
  • desc -> description
  • resCeil -> roundUpCost
  • order -> unlockOrder
  • incr_order -> increaseUnlockOrder

Challenges:

  • desc -> challengeDescription
  • reward -> rewardDescription
  • effect -> rewardEffect
  • effectDisplay -> rewardDisplay
  • active -> challengeActive
',7),l=[i];function s(r,c,d,h,g,f){return t(),a("div",null,l)}const u=e(n,[["render",s]]);export{m as __pageData,u as default}; diff --git a/assets/public_kronos_Old Things_2.0-format-changes.md.CuPSOvPY.lean.js b/assets/public_kronos_Old Things_2.0-format-changes.md.CuPSOvPY.lean.js deleted file mode 100644 index dc6ad02b..00000000 --- a/assets/public_kronos_Old Things_2.0-format-changes.md.CuPSOvPY.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as o}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"2.0 format changes","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/Old Things/2.0-format-changes.md","filePath":"public/kronos/Old Things/2.0-format-changes.md"}'),n={name:"public/kronos/Old Things/2.0-format-changes.md"},i=o("",7),l=[i];function s(r,c,d,h,g,f){return t(),a("div",null,l)}const u=e(n,[["render",s]]);export{m as __pageData,u as default}; diff --git a/assets/public_kronos_README.md.CgBYWZCx.js b/assets/public_kronos_README.md.CgBYWZCx.js deleted file mode 100644 index fd1f5a9c..00000000 --- a/assets/public_kronos_README.md.CgBYWZCx.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as o,o as t,a5 as r}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Kronos","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/README.md","filePath":"public/kronos/README.md"}'),a={name:"public/kronos/README.md"},s=r('

Kronos ​

Play here.

Updating the website:

  • git submodule update --remote
  • git add -A
  • git commit -m "Updated kronos"
  • git push
',4),i=[s];function n(c,d,l,_,p,u){return t(),o("div",null,i)}const f=e(a,[["render",n]]);export{m as __pageData,f as default}; diff --git a/assets/public_kronos_README.md.CgBYWZCx.lean.js b/assets/public_kronos_README.md.CgBYWZCx.lean.js deleted file mode 100644 index 4907b95d..00000000 --- a/assets/public_kronos_README.md.CgBYWZCx.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as o,o as t,a5 as r}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Kronos","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/README.md","filePath":"public/kronos/README.md"}'),a={name:"public/kronos/README.md"},s=r("",4),i=[s];function n(c,d,l,_,p,u){return t(),o("div",null,i)}const f=e(a,[["render",n]]);export{m as __pageData,f as default}; diff --git a/assets/public_kronos_changelog.md.CfILpf_9.js b/assets/public_kronos_changelog.md.CfILpf_9.js deleted file mode 100644 index 654054e9..00000000 --- a/assets/public_kronos_changelog.md.CfILpf_9.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as i,o as a,a5 as l}from"./chunks/framework.CK8QU5WH.js";const b=JSON.parse('{"title":"The Modding Tree changelog:","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/changelog.md","filePath":"public/kronos/changelog.md"}'),t={name:"public/kronos/changelog.md"},o=l('

The Modding Tree changelog: ​

v2.5.9.2 - 5/19/21 ​

  • Fixed many issues with things not updating.

v2.5.9.1 - 5/18/21 ​

  • Made text inputs never give NaNs.

v2.5.9 - 5/18/21 ​

  • Fixed issue when using text inputs for Numbers.
  • Added particle color feature.
  • Particle speed and dir are updated as it moves.
  • Added setSpeed and setDir for particles.
  • Added more trig functions.

v2.5.8 - 5/17/21 ​

  • Added makeShinies, which creates a stationary particle in a random spot.
  • Bars will visually update more quickly.
  • Fixed a major particle-related issue.
  • Fixed autoUpgrade.
  • Fixed a minor visual issue with tree nodes.

v2.5.7 - 5/15/21 ​

  • Added a particle system! Not only can it be used for visual effects, but particles can interact with the mouse. They could be used to create golden cookies or collectables, for example.
  • Added marked feature to buyables, clickables, and challenges. By default, stars multi-completion challenges when maxed.
  • Added 'deactivated' feature to layers, which disables many features.
  • Improved number formatting slightly.

v2.5.6 - 5/14/21 ​

  • You can now use non-numeric ids for upgrades, buyables, etc.
  • Fixed an exploit that let you buy an extra buyable.
  • Moved basic getter/setter functions to easyAccess.js.

v2.5.5.2 - 5/12/21 ​

  • Fixed a major issue with buyables.
  • Fixed a variety of tabFormat-related issues.
  • Fixed commas appearing in decimal places (thanks to pg132!)

v2.5.5.1 - 5/12/21 ​

  • Fixed clickables.

v2.5.5 - 5/12/21 ​

  • Added grids! They are a grid of buttons which behave the same, but have their own data. Good for inventory grids, map tiles, and more!
  • Added "marked" feature to add a mark to a node. Can be an image instead of a star. (Originally by Jacorb)
  • Added "layer-proxy" component that lets you use components from another layer.
  • Added the ability to display non-whole numbers in main-display.

v2.5.4 - 5/10/21 ​

  • Added a setting to always use single-tab mode.
  • Added directMult, which multiplies prestige gain after exponents and softcaps. It actually multiplies gain for static layers.
  • Added onEnter and onExit for challenges.
  • Improved displaying numbers between 0.0001 and 0.1.
  • Added documentation on how gainMult/Exp work for static layers.
  • Fixed a visual issue on mobile, thanks to thepaperpilot.
  • Improved documentation in general.

v2.5.3 - 5/8/21 ​

  • Improved performance of tab formats and bars.
  • Respec confirmation settings are now kept on resets.
  • Improved compatibility with older browsers.
  • Fixed missing pixel on vertical bars.

v2.5.2.1 - 5/7/21 ​

  • Fixed microtabs making layers highlight incorrectly.

v2.5.2 - 5/7/21 ​

  • Added glowColor for subtabs.
  • Improved the display for extremely small numbers.
  • Fixed issues in the buyable docs.

v2.5.1 - 5/7/21 ​

  • Fixed dynamic things in tabFormat not updating.

v2.5: Dreams Really Do Come True - 5/7/21 ​

  • Optimizations, hopefully a significant amount.
  • Added OOM/s point gen display at high values (thanks to Ducdat!)
  • Only one tab will display if the window is not wide enough (also thanks to Ducdat!)
  • Holding down a buyable's button now buys it continuously.
  • New milestone setting will also show the most recently unlocked milestone. (Also renamed all settings to be clearer)
  • Added an onHold feature for clickables.
  • Layer nodes will be highlighted even if the player is on the same tab.
  • Added customizable node glowColor.
  • Added buyable purchaseLimit.
  • Amount is automatically supplied to buyable cost and effect functions.
  • Locked (not yet visible) milestones no longer take up space. Also fixed hidden milestones taking a tiny bit of space.
  • Re-centered respec buttons.
  • Force-displayed tooltips are not hidden by resets.
  • Added formatting support for very small numbers. Disabled in most places by default because rounding errors might cause issues. Access it with formatSmall, or enable it globally by adding "allowSmall: true" to modInfo.

v2.4.1 - 4/29/21 ​

  • A number of minor fixes, many thanks to thepaperpilot.
  • The respec confirmation checkbox is now part of the respec-button component. (This also fixes the checkbox appearing when there is no respec button)
  • Added a few undocumented changes to the 2.4 changelog (the two at the bottom)

v2.4: Rationalized Edition - 4/29/21 ​

  • Completely reworked tooltips. Shift-click a node to force its tooltip to stay displayed. (And hopefully finally fixed flickering!)

  • Added text-input and slider components.

  • Added the ability to toggle respec confirmations.

  • Added custom respec confirmation messages.

  • The red layer highlight will not appear before a layer is unlocked.

  • Added unlocking hotkeys.

  • You no longer need to supply 'rows' and 'cols' for any Big Features.

  • Node symbols can use HTML.

  • Added documentation for the respec button.

  • Added prestigeNotify to subtabs, and prestigeNotify in subtabs also highlights the layer node.

  • The version number no longer contains special characters or irrational numbers.

  • Added ctrlDown and shiftDown variables.

  • Tooltips now use HTML (this means you need to replace any newlines with
    )

v2.π.1 - 4/7/21 ​

  • Fixed formatting for some larger numbers.
  • Upgrades will expand if there is too much text to display.
  • Fixed styling challenges.
  • No longer attempts to display a base currency when there is none.

v2.π: Incrementally Updated - 2/5/21 ​

  • Performance improvements.
  • Fixed tooltips overlapping with the top display.
  • Clicking a popup dismisses it immediately.
  • Added support for bulk challenge completions.
  • "Best" is updated automatically.
  • Fixed keeping Decimal values on reset.
  • Code reorganization and style improvements by fudo.

v2.3.5 - 12/21/20 ​

  • Added resetTime, which tracks the time since a layer prestiged or was reset.
  • A layer node will be highlighted red if one of its subtabs is highlighted red.
  • Fixed issues with keeping challenges, buyables, and clickables on reset.
  • Improved the unlocking of custom layers.
  • Other minor fixes.

v2.3.4 - 12/16/20 ​

  • Added a node image feature.
  • Resource display now always shows the amount of the currency the layer's gain is based on.
  • Added spacing between tree nodes.
  • Another attempt to fix tooltip flickering.

v2.3.3 - 12/13/20 ​

  • Fixed the first node in a row always taking up space.
  • layerShown is now optional.
  • All prestige types can now use features for custom prestige types.

v2.3.2 - 12/13/20 ​

  • Fixed achievement/milestone popups.

v2.3.1 - 12/12/20 ​

  • Another attempt to fix flickering tooltips.
  • The "this" keyword should work everywhere except tabFormat arrays (although I may have missed some things).
  • Fixed tree branches not updating when scrolling on the right-side tab.
  • Fixed a spacing issue when a node's symbol is ""
  • Removed some old, unneeded files.

v2.3: Cooler and Newer Edition - 12/10/20 ​

  • Added achievement/milestone popups (thank you to Jacorb for this contribution!)
  • The changelog tab is back, and can be set in mod.js.
  • Layer nodes and respec buttons will not be clicked by pressing "enter".
  • Possible fix for flickering tooltips and strange transitions.
  • The victory screen text is configurable.
  • Added image and textStyle features to achievements.
  • Added an argument to use specific rows in an "upgrades" component.
  • Fixed the comma appearing in the main display when there was no effectDescription
  • Added the ability to easily make a tab that is a collection of layers in subtabs.
  • Improved spacing for embedding layers with subtabs into subtabs.

v2.2.8 - 12/03/20 ​

  • Double-clicking a layer node brings you to the main subtab for that layer.
  • Attempted to fix challenges visually updating a different way.
  • Added a softcap function for use in formulas.
  • Added displayRow feature, which lets layers be shown somewhere separate from where they are in the reset order (e.g. side layers)
  • Fixed autoupgrade issue.

v2.2.7 - 11/30/20 ​

  • Added autoUpgrade feature.
  • resource-display now shows resource gain per second if passiveGain is active.
  • Fixed formatting issues on some large numbers.
  • Better support for using classed objects in player and in layers/tmp.
  • Made hard resetting more effective.
  • Removed Herobrine from getStartClickables.

v2.2.6 - 11/30/20 ​

  • Added goalDescription for challenges and made the new "canComplete" system the standard.
  • Another attempt to fix challenges not visually updating.
  • Fixed side layers not appearing.
  • Fixed getStartClickables again.

v2.2.5 - 11/29/20 ​

  • Added features for overriding the displays and costs/goals of upgrades and challenges to make them fully custom.
  • best, total, and unlocked are always automatically added to layerData (but best and total will only display if you add them yourself).
  • Fixed getStartClickables.

v2.2.4 - 11/28/20 ​

  • Added softcap and softcapPower features (for Normal layers)
  • Offline time limit and default max tick length were fixed (previously the limits were 1000x too large)
  • Added fixOldSaves.
  • You can use HTML in main-display.
  • Fixed a number of minor oddities.

v2.2.3 - 11/28/20 ​

  • Layers will be highlighted if you can finish a challenge.
  • The "can complete challenge" color now overrides the "already completed" color.
  • Button nodes now work as side "layers".
  • Setting a tooltip to "" hides it entirely.

v2.2.2 - 11/22/20 ​

  • Fixed right half of the screen being unclickable in some circumstances.
  • Fixed tree branches being offset.
  • Fix to lastSafeTab.

v2.2.1 - 11/7/20 ​

  • Added a small highlight to layers you can meaningfully prestige on.
  • Added passiveGeneration and autoPrestige features to standardize prestige automation. (The old ways still work, but the new ones work better with other things)
  • Improved milestones visually a bit.
  • "best" and "total" are now only displayed if present in startData.
  • Fixed issues with things not updating visually. (Thank you to to Jacorb!)
  • Side layers and button nodes can now be highlighted.
  • Updated docs on the new tree-related features.

v2.2: Uprooted - 11/7/20 ​

  • You can now embed a layer inside of a subtab or microtab!
  • Added support for hiding or reformatting the tree tab
  • Added non-layer button nodes
  • Added shouldNotify to subtab/microtab buttons. (You can make them highlighted)
  • Added commas to large exponents.
  • Upgrades now only show "currently" if they have an effectDisplay (so not for constant effects).
  • Achievements are part of the default tab format.
  • NaN is now handled more intelligently.
  • Renamed files, and moved less relevant ones to another folder.
  • The "hide completed challenges" setting now only hides challenges at max completions.
  • Thank you to thepaperpilot for fixing errors in docs and improving the infobox appearance!
  • Many other minor fixes.

v2.1.4 - 10/25/20 ​

  • Added an infobox component. Thank you to thepaperpilot for this contribution!
  • Layer type is now optional, and defaults to "none".
  • Improved the look of bars and tab buttons.
  • Improved spacing between layer nodes (also thanks to thepaperpilot!)
  • Fixed the "blank" component breaking if only specifying the height.
  • Fixed some numbers not displaying with enough digits.
  • Made a few more things able to be functions.
  • A few other minor fixes.

v2.1.3.1 - 10/21/20 ​

  • Fixed the update function.

v2.1.3 - 10/21/20 ​

  • gainMult and gainExp are now optional.
  • Layer unlocking is now kept on reset.
  • Game should start up faster.
  • Layer updates now have a determined order and starts with earlier-rowed layers.
  • Automation now has a determined order and starts with later-rowed layers.
  • Fixed issues with resetting clickables and challenges.
  • Commas should no longer appear in the decimal places of a number.
  • Fixed potential issue in displaying the tree.

v2.1.2 - 10/19/20 ​

  • Added buyUpgrade function (buyUpg still works though)
  • Added author name to modInfo.
  • Fix to crash caused when the name of a subtab or microtab is changed.
  • Fixes to outdated information in docs.
  • Improvements to Discord links.
  • Thank you to thepaperpilot for contributing to this update!

v2.1.1 - 10/17/20 ​

  • Added resource-display component, which displays the base currency for the prestige layer, as well as the best and/or total of this layer's prestige currency.
  • Fixed the value for the base currency not updating in resource-display.

v2.1: We should have thought of this sooner! - 10/17/20 ​

  • Moved most of the code users will want to edit to mod.js, added documentation for it.
    • Specifically, modInfo, VERSION, canGenPoints, getPointGen, and maxTickLength
  • Added getStartPoints()
  • Added the ability to store non-layer-related data
  • Added the ability to display more things at the top of the tree tab below points.
  • Made the endgame condition customizable
  • Added "sell one" and "sell all" buttons for buyables.
  • Moved the old "game" to demo.js, and replaced it with a minimal game that won't cause issues when edited.
  • Fixed issues with version number
  • Fixed number formatting issue making things like "10e9" appear.

v2.0.5 - 10/16/20 ​

  • Made more features (including prestige parameters) able to be dynamic.
  • Layer nodes can be hidden but still take up space with "ghost" visibility
  • Added clickableEffect for real.
  • Fixed some visual issues with bars.
  • A few other minor tweaks and improvements.

v2.0.4 - 10/16/20 ​

  • Fixed HTML on buttons interfering with clicking on them.

v2.0.3 - 10/16/20 ​

  • Fixed hotkeys not displaying in info.
  • Fixed the game supressing all external hotkeys.
  • You can use more things as currencies for upgrade costs and challenge goals using currencyLocation.
  • Added maxTickLength, which can be used to prevent offline time or tab-switching from breaking time-limit based mechanics.
  • Made buyable respec buttons and clickable "master" buttons their own components, and gave them a hide/show feature.
  • Added a general "tooltip" feature for achievements.

v2.0.2 - 10/15/20 ​

  • Branches are now dynamic (they can be functions).
  • Fixed a crash related to offline time.
  • Fixed links being too wide.

v2.0.1 - 10/15/20 ​

  • Fixed side layers appearing multiple times.

v2.0: The Pinnacle of Achievement Mountain - 10/15/20 ​

  • Added progress bars, which are highly customizable and can be horizontal or vertical!
  • Added "side layers", displayed smaller and off to the side, and don't get reset by default. They can be used for global achievements and statistics. Speaking of which...
  • Added achievements!
  • Added clickables, a more generalized variant of buyables.
  • Almost every value in layer data can be either a function or a constant value!
  • Added support for multiple completions of challenges.
  • Added "none" prestige type, which removes the need for any other prestige-related features.
  • The points display and other gui elements stay at the top of the screen when the tree scrolls.
  • Added getter/setter functions for the amounts and effects of most Big Features
  • Moved modInfo to game.js, added a spot in modInfo for a Discord link, changelog link. Also added a separate mod version from the TMT version in VERSION.
  • Tree structure is based on layer data, no index.html editing is needed.
  • Tmp does not need to be manually updated.
  • You don't have to have the same amount of upgrades in every row (and challs and buyables)
  • "unlocked" is optional for all Big Components (defaults to true).
  • All displays will update correctly.
  • Changelog is no longer in index.html at all.
  • Generation of Points now happens in the main game loop
  • Changed the reset functions to make keeping things easier
  • Renamed many things to increase readability (see the list in the link below)
  • Improved documentation based on feedback

v1.3.5: ​

  • Completely automated convertToDecimal, now you never have to worry about it again.
  • Branches can be defined without a color id. But they can also use hex values for color ids!
  • Created a tutorial for getting started with TMT and Github.
  • Page title is now automatically taken from mod name.

v1.3.4 - 10/8/20 ​

  • Added "midsection" feature to add things to a tab's layout while still keeping the standard layout.
  • Fix for being able to buy more buyables than you should.

v1.3.3 - 10/7/20 ​

  • Fix for the "order of operations" issue in temp.

v1.3.1 - 10/7/20 ​

  • Added custom CSS and tooltips for Layer Nodes.
  • Added custom CSS for upgrades, buyables, milestones, and challenges, both individually and layer-wide.
  • You can now use HTML in most display text!
  • You can now make milestones unlockable and not display immediately.
  • Fixed importing saves, and issue with upgrades not appearing, and probably more.
  • Optional "name" layer feature, used in confirmation messages.

v1.3: Tabception... ception! - 10/7/20 ​

  • Added subtabs! And also a Micro-tab component to let you make smaller subtab-esque areas anywhere.
  • Added a "custom" prestige formula type, and a number of features to support it.
  • Added points/sec display (can be disabled).
  • Added h-line, v-line and image-display components, plus components for individual upgrades, challenges, and milestones.
  • Added upgEffect, buyableEffect, and challEffect functions.
  • Added "hide completed challenges" setting.
  • Moved old changelogs to a separate place.
  • Fixed hasMilestone and incr_order.
  • Static layers now show the currency amount needed for the next one if you can buy max.

v1.2.4 - 10/4/20 ​

  • Layers are now highlighted if you can buy an upgrade, and a new feature, shouldNotify, lets you make it highlight other ways.
  • Fixed bugs with hasUpg, hasChall, hasMilestone, and inChallenge.
  • Changed the sample code to use the above functions for convenience.

v1.2.3 - 10/3/20 ​

  • Added a row component, which displays a list of objects in a row.
  • Added a column component, which displays a list of objects in a column (useful within a row).
  • Changed blanks to have a customizable width and height.

v1.2: This Changes Everything! - 10/3/20 ​

  • Many layer features can now be static values or functions. (This made some formats change, which will break old things)
  • You can now use the "this" keyword, to make code easier to transfer when making new layers.
  • Also added "this.layer", which is the current layer's name, and works on existing subfeatures (e.g. individual upgrades) as well! Subfeatures also have "this.id".
  • Fixed a big save issue. If you use a unique mod id, your save will never conflict with other mods.
  • Added a configurable offline time limit in modinfo at the top of index.html. (default 1 hour)
  • Added a few minor features, and updated the docs with new information.

v1.1.1 - 9/30/20 ​

  • You can define hotkeys directly from layer config.

v1.1: Enhanced Edition - 9/30/20 ​

  • Added "Buyables", which can function like Space Buildings or Enhancers.
  • Custom CSS can now be used on any component! Make the third argument an object with CSS parameters.
  • Lots of minor good things.

v1.0 - 9/27/20 ​

  • First release.
',115),n=[o];function r(s,d,h,u,c,m){return a(),i("div",null,n)}const f=e(t,[["render",r]]);export{b as __pageData,f as default}; diff --git a/assets/public_kronos_changelog.md.CfILpf_9.lean.js b/assets/public_kronos_changelog.md.CfILpf_9.lean.js deleted file mode 100644 index 7de069f9..00000000 --- a/assets/public_kronos_changelog.md.CfILpf_9.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as i,o as a,a5 as l}from"./chunks/framework.CK8QU5WH.js";const b=JSON.parse('{"title":"The Modding Tree changelog:","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/changelog.md","filePath":"public/kronos/changelog.md"}'),t={name:"public/kronos/changelog.md"},o=l("",115),n=[o];function r(s,d,h,u,c,m){return a(),i("div",null,n)}const f=e(t,[["render",r]]);export{b as __pageData,f as default}; diff --git a/assets/public_kronos_docs_!general-info.md.h8u1FelN.js b/assets/public_kronos_docs_!general-info.md.h8u1FelN.js deleted file mode 100644 index 2553d5c0..00000000 --- a/assets/public_kronos_docs_!general-info.md.h8u1FelN.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as o}from"./chunks/framework.CK8QU5WH.js";const b=JSON.parse('{"title":"The-Modding-Tree","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/!general-info.md","filePath":"public/kronos/docs/!general-info.md"}'),n={name:"public/kronos/docs/!general-info.md"},r=o('

The-Modding-Tree ​

Making a game in The Modding Tree mostly involves defining parameters or functions on objects. If you aren't following the getting started guide, you should start by setting up your basic mod info in mod.js. It's important to set a mod id to ensure saving works properly.

Beyond that, the main way to add content is through creating layers, often in layers.js. You can add new layers by calling addLayer(layername, layerdata). There is an example of a basic layer in layers.js showing the recommended method. It is just an example and can be freely deleted. You can also use it as a reference or a base for your own layers.

Most of the time, you won't need to dive deep into the code to create things, but you still can if you really want to, for example to add new Vue components in components.js.

The Modding Tree uses break_eternity.js to store large values. This means that many numbers are Decimal objects, and must be treated differently. For example, you have to use new Decimal(x) to create a Decimal value instead of a plain number, and perform operations on them by calling functions. e.g, instead of x = x + y, use x = x.add(y). Keep in mind this also applies to comparison operators, which should be replaced with calling the .gt, .gte, .lt, .lte, .eq, and .neq functions. See the break_eternity.js docs for more details on working with Decimal values.

Almost all values can be either a constant value, or a dynamic value. Dynamic values are defined by putting a function that returns what the value should be at any given time.

All display text can use basic HTML elements (But you can't use most Vue features there).

While reading this documentation, the following key will be used when describing features:

  • No label: This is required and the game may crash if it isn't included.
  • sometimes required: This is may be required, depending on other things in the layer.
  • optional: You can leave this out if you don't intend to use that feature for the layer.
  • assigned automagically: This value will be set automatically and override any value you set.
  • deprecated: This feature is not recommended to be used, because newer features are able to achieve the same thing in a better, easier way.

Table of Contents ​

General ​

  • Getting Started: Getting your own copy of the code set up with Github Desktop.
  • Main mod info: How to set up general things for your mod in mod.js.
  • Basic layer breakdown: Breaking down the components of a layer with minimal features.
  • Layer features: Explanations of all of the different properties that you can give a layer.
  • Custom Tab Layouts: An optional way to give your tabs a different layout. You can even create entirely new components to use.
  • Custom game layouts: You can get rid of the tree tab, add buttons and other things to the tree, or even customize the tab's layout like a layer tab.
  • Updating TMT: Using Github Desktop to update your mod's version of TMT.

Common components ​

  • Upgrades: How to create upgrades for a layer.
  • Milestones: How to create milestones for a layer.
  • Buyables: Create rebuyable upgrades for your layer (with the option to make them respec-able). Can be used to make Enhancers or Space Buildings, for example.
  • Clickables: A more generalized variant of buyables, for any kind of thing that is sometimes clickable. Between these and Buyables, you can do just about anything.
  • Achievements: How to create achievements for a layer (or for the whole game).

Other components and features ​

  • Challenges: How to create challenges for a layer.
  • Bars: Display some information as a progress bar, gauge, or similar. They are highly customizable, and can be horizontal and vertical as well.
  • Subtabs and Microtabs: Create subtabs for your tabs, as well as "microtab" components that you can put inside the tabs. You can even use them to embed a layer inside another layer!
  • [Grids][grids.md]: Create a group buttons that behave the same, but have their own data. Good for map tiles, an inventory grid, and more!
  • Infoboxes: Boxes containing text that can be shown or hidden.
  • Trees: Make your own trees. You can make non-layer button nodes too!
  • Particle system: Can be used to create particles for visual effects, but also interactable things like golden cookies or collectables.
',16),i=[r];function s(l,d,c,h,u,m){return t(),a("div",null,i)}const y=e(n,[["render",s]]);export{b as __pageData,y as default}; diff --git a/assets/public_kronos_docs_!general-info.md.h8u1FelN.lean.js b/assets/public_kronos_docs_!general-info.md.h8u1FelN.lean.js deleted file mode 100644 index b66a55de..00000000 --- a/assets/public_kronos_docs_!general-info.md.h8u1FelN.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as o}from"./chunks/framework.CK8QU5WH.js";const b=JSON.parse('{"title":"The-Modding-Tree","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/!general-info.md","filePath":"public/kronos/docs/!general-info.md"}'),n={name:"public/kronos/docs/!general-info.md"},r=o("",16),i=[r];function s(l,d,c,h,u,m){return t(),a("div",null,i)}const y=e(n,[["render",s]]);export{b as __pageData,y as default}; diff --git a/assets/public_kronos_docs_achievements.md.DH7Fd1ef.js b/assets/public_kronos_docs_achievements.md.DH7Fd1ef.js deleted file mode 100644 index 8272e272..00000000 --- a/assets/public_kronos_docs_achievements.md.DH7Fd1ef.js +++ /dev/null @@ -1,7 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Achievements","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/achievements.md","filePath":"public/kronos/docs/achievements.md"}'),s={name:"public/kronos/docs/achievements.md"},n=i(`

Achievements ​

Achievements are awarded to the player when they meet a certain goal, and optionally give some benefit.

You can make global achievements by putting them in a side layer by making its row equal to "side" instead of a number.

Useful functions for dealing with achievements and implementing their effects:

  • hasAchievement(layer, id): determine if the player has the Achievement.
  • achievementEffect(layer, id): Returns the current effects of the achievement, if any.

Achievements should be formatted like this:

js
achievements: {
-    11: {
-        name: "Blah",
-        more features
-    },
-    etc
-}

Usually, each achievement should have an id where the first digit is the row and the second digit is the column.

Individual achievement can have these features:

  • name: optional. displayed at the top of the achievement. The only visible text. It can also be a function that returns updating text. Can use basic HTML.

  • done(): A function returning a boolean to determine if the achievement should be awarded.

  • tooltip: Default tooltip for the achievement, appears when it is hovered over. Should convey the goal and any reward for completing the achievement. It can also be a function that returns updating text. Can use basic HTML. Setting this to "" disables the tooltip.

  • effect(): optional. A function that calculates and returns the current values of any bonuses from the achievement. Can return a value or an object containing multiple values.

  • unlocked(): optional. A function returning a bool to determine if the achievement is visible or not. Default is unlocked.

  • onComplete() - optional. this function will be called when the achievement is completed.

  • image: optional, puts the image from the given URL (relative or absolute) in the achievement

  • style: optional. Applies CSS to this achievement, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • textStyle: optional. Applies CSS to the text, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

  • id: assigned automagically. It's the "key" which the achievement was stored under, for convenient access. The achievement in the example's id is 11.

  • goalTooltip: optional, deprecated. Appears when the achievement is hovered over and locked, overrides the basic tooltip. This is to display the goal (or a hint). It can also be a function that returns updating text. Can use basic HTML.

  • doneTooltip: optional, deprecated. Appears when the achievement is hovered over and completed, overrides the basic tooltip. This can display what the player achieved (the goal), and the rewards, if any. It can also be a function that returns updating text. Can use basic HTML.

Disable achievement popups by adding achievementsPopups: false to the layer.

`,11),o=[n];function l(h,r,p,c,d,u){return a(),t("div",null,o)}const v=e(s,[["render",l]]);export{g as __pageData,v as default}; diff --git a/assets/public_kronos_docs_achievements.md.DH7Fd1ef.lean.js b/assets/public_kronos_docs_achievements.md.DH7Fd1ef.lean.js deleted file mode 100644 index 7110f40a..00000000 --- a/assets/public_kronos_docs_achievements.md.DH7Fd1ef.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Achievements","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/achievements.md","filePath":"public/kronos/docs/achievements.md"}'),s={name:"public/kronos/docs/achievements.md"},n=i("",11),o=[n];function l(h,r,p,c,d,u){return a(),t("div",null,o)}const v=e(s,[["render",l]]);export{g as __pageData,v as default}; diff --git a/assets/public_kronos_docs_bars.md.C-Hikk54.js b/assets/public_kronos_docs_bars.md.C-Hikk54.js deleted file mode 100644 index 377e2a21..00000000 --- a/assets/public_kronos_docs_bars.md.C-Hikk54.js +++ /dev/null @@ -1,10 +0,0 @@ -import{_ as s,c as i,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Bars","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/bars.md","filePath":"public/kronos/docs/bars.md"}'),e={name:"public/kronos/docs/bars.md"},n=t(`

Bars ​

Bars let you display information in a more direct way. It can be a progress bar, health bar, capacity gauge, or anything else.

Bars are defined like other Big Features:

js
bars: {
-    bigBar: {
-        direction: RIGHT,
-        width: 200,
-        height: 50,
-        progress() { return 0 },
-        etc
-    },
-    etc
-}

Features:

  • direction: UP, DOWN, LEFT, or RIGHT (not strings). Determines the direction that the bar is filled as it progresses. RIGHT means from left to right.

  • width, height: The size in pixels of the bar, but as numbers (no "px" at the end).

  • progress(): A function that returns the portion of the bar that is filled, from "empty" at 0 to "full" at 1, updating automatically. (Nothing bad happens if the value goes out of these bounds, and it can be a number or Decimal)

  • display(): optional. A function that returns text to be displayed on top of the bar, can use HTML.

  • unlocked(): optional. A function returning a bool to determine if the bar is visible or not. Default is unlocked.

  • baseStyle, fillStyle, borderStyle, textStyle: Optional, Apply CSS to the unfilled portion, filled portion, border, and display text on the bar, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

  • id: assigned automagically. It's the "key" which the bar was stored under, for convenient access. The bar in the example's id is "bigBar".

`,6),l=[n];function r(o,p,h,d,k,c){return a(),i("div",null,l)}const E=s(e,[["render",r]]);export{u as __pageData,E as default}; diff --git a/assets/public_kronos_docs_bars.md.C-Hikk54.lean.js b/assets/public_kronos_docs_bars.md.C-Hikk54.lean.js deleted file mode 100644 index 17c3adf9..00000000 --- a/assets/public_kronos_docs_bars.md.C-Hikk54.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as i,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Bars","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/bars.md","filePath":"public/kronos/docs/bars.md"}'),e={name:"public/kronos/docs/bars.md"},n=t("",6),l=[n];function r(o,p,h,d,k,c){return a(),i("div",null,l)}const E=s(e,[["render",r]]);export{u as __pageData,E as default}; diff --git a/assets/public_kronos_docs_basic-layer-breakdown.md.Zf7IGRAq.js b/assets/public_kronos_docs_basic-layer-breakdown.md.Zf7IGRAq.js deleted file mode 100644 index 8175e795..00000000 --- a/assets/public_kronos_docs_basic-layer-breakdown.md.Zf7IGRAq.js +++ /dev/null @@ -1,32 +0,0 @@ -import{_ as s,c as i,o as a,a5 as n}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Basic layer breakdown","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/basic-layer-breakdown.md","filePath":"public/kronos/docs/basic-layer-breakdown.md"}'),e={name:"public/kronos/docs/basic-layer-breakdown.md"},t=n(`

Basic layer breakdown ​

This is a very minimal layer with minimal features. Most things will require additional features.

js
addLayer("p", {
-    startData() { return {                  // startData is a function that returns default data for a layer. 
-        unlocked: true,                     // You can add more variables here to add them to your layer.
-        points: new Decimal(0),             // "points" is the internal name for the main resource of the layer.
-    }},
-
-    color: "#4BDC13",                       // The color for this layer, which affects many elements.
-    resource: "prestige points",            // The name of this layer's main prestige resource.
-    row: 0,                                 // The row this layer is on (0 is the first row).
-
-    baseResource: "points",                 // The name of the resource your prestige gain is based on.
-    baseAmount() { return player.points },  // A function to return the current amount of baseResource.
-
-    requires: new Decimal(10),              // The amount of the base needed to  gain 1 of the prestige currency.
-                                            // Also the amount required to unlock the layer.
-
-    type: "normal",                         // Determines the formula used for calculating prestige currency.
-    exponent: 0.5,                          // "normal" prestige gain is (currency^exponent).
-
-    gainMult() {                            // Returns your multiplier to your gain of the prestige resource.
-        return new Decimal(1)               // Factor in any bonuses multiplying gain here.
-    },
-    gainExp() {                             // Returns your exponent to your gain of the prestige resource.
-        return new Decimal(1)
-    },
-
-    layerShown() { return true },          // Returns a bool for if this layer's node should be visible in the tree.
-
-    upgrades: {
-        // Look in the upgrades docs to see what goes here!
-    },
-})
`,3),h=[t];function l(p,k,r,E,d,o){return a(),i("div",null,h)}const c=s(e,[["render",l]]);export{g as __pageData,c as default}; diff --git a/assets/public_kronos_docs_basic-layer-breakdown.md.Zf7IGRAq.lean.js b/assets/public_kronos_docs_basic-layer-breakdown.md.Zf7IGRAq.lean.js deleted file mode 100644 index 30e43be6..00000000 --- a/assets/public_kronos_docs_basic-layer-breakdown.md.Zf7IGRAq.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as i,o as a,a5 as n}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Basic layer breakdown","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/basic-layer-breakdown.md","filePath":"public/kronos/docs/basic-layer-breakdown.md"}'),e={name:"public/kronos/docs/basic-layer-breakdown.md"},t=n("",3),h=[t];function l(p,k,r,E,d,o){return a(),i("div",null,h)}const c=s(e,[["render",l]]);export{g as __pageData,c as default}; diff --git a/assets/public_kronos_docs_buyables.md.DaAxmRa3.js b/assets/public_kronos_docs_buyables.md.DaAxmRa3.js deleted file mode 100644 index c4a65dc7..00000000 --- a/assets/public_kronos_docs_buyables.md.DaAxmRa3.js +++ /dev/null @@ -1,13 +0,0 @@ -import{_ as s,c as i,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const c=JSON.parse('{"title":"Buyables","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/buyables.md","filePath":"public/kronos/docs/buyables.md"}'),e={name:"public/kronos/docs/buyables.md"},n=t(`

Buyables ​

Buyables are usually things that can be bought multiple times with scaling costs. They come with optional buttons that can be used for respeccing or selling buyables, among other things.

The amount of a buyable owned is a Decimal.

Useful functions for dealing with buyables and implementing their effects:

  • getBuyableAmount(layer, id): get the amount of the buyable the player has
  • setBuyableAmount(layer, id, amount): set the amount of the buyable the player has
  • buyableEffect(layer, id): Returns the current effects of the buyable, if any.

Buyables should be formatted like this:

js
buyables: {
-    11: {
-        cost(x) { return new Decimal(1).mul(x) },
-        display() { return "Blah" },
-        canAfford() { return player[this.layer].points.gte(this.cost()) },
-        buy() {
-            player[this.layer].points = player[this.layer].points.sub(this.cost())
-            setBuyableAmount(this.layer, this.id, getBuyableAmount(this.layer, this.id).add(1))
-        },
-        etc
-    },
-    etc
-}

Features:

  • title: optional. displayed at the top in a larger font. It can also be a function that returns updating text.

  • cost(): cost for buying the next buyable. Can have an optional argument "x" to calculate the cost of the x+1th purchase. (x is a Decimal). Can return an object if there are multiple currencies.

  • effect(): optional. A function that calculates and returns the current values of bonuses of this buyable. Can have an optional argument "x" to calculate the effect of having x of the buyable.. Can return a value or an object containing multiple values.

  • display(): A function returning everything that should be displayed on the buyable after the title, likely including the description, amount bought, cost, and current effect. Can use basic HTML.

  • unlocked(): optional. A function returning a bool to determine if the buyable is visible or not. Default is unlocked.

  • canAfford(): A function returning a bool to determine if you can buy one of the buyables.

  • buy(): A function that implements buying one of the buyable, including spending the currency.

  • buyMax(): optional. A function that implements buying as many of the buyable as possible.

  • style: optional. Applies CSS to this buyable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • purchaseLimit: optional. The limit on how many of the buyable can be bought. The default is no limit.

  • marked: optional Adds a mark to the corner of the buyable. If it's "true" it will be a star, but it can also be an image URL.

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

  • id: assigned automagically. It's the "key" which the buyable was stored under, for convenient access. The buyable in the example's id is 11.

Sell One/Sell All:

Including a sellOne or sellAll function will cause an additional button to appear beneath the buyable. They are functionally identical, but "sell one" appears above "sell all". You can also use them for other things.

  • sellOne/sellAll(): optional. Called when the button is pressed. The standard use would be to decrease/reset the amount of the buyable, and possibly return some currency to the player.

  • canSellOne/canSellAll(): optional. booleans determining whether or not to show the buttons. If "canSellOne/All" is absent but "sellOne/All" is present, the appropriate button will always show.

To add a respec button, or something similar, add the respecBuyables function to the main buyables object (not individual buyables). You can use these features along with it:

  • respec(): optional. This is called when the button is pressed (after a toggleable confirmation message).

  • respecText: optional. Text to display on the respec Button.

  • showRespec(): optional. A function determining whether or not to show the button, if respecBuyables is defined. Defaults to true if absent.

  • respecMessage: optional. A custom confirmation message on respec, in place of the default one.

`,14),l=[n];function h(p,o,r,k,u,d){return a(),i("div",null,l)}const g=s(e,[["render",h]]);export{c as __pageData,g as default}; diff --git a/assets/public_kronos_docs_buyables.md.DaAxmRa3.lean.js b/assets/public_kronos_docs_buyables.md.DaAxmRa3.lean.js deleted file mode 100644 index e98a8d39..00000000 --- a/assets/public_kronos_docs_buyables.md.DaAxmRa3.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as i,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const c=JSON.parse('{"title":"Buyables","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/buyables.md","filePath":"public/kronos/docs/buyables.md"}'),e={name:"public/kronos/docs/buyables.md"},n=t("",14),l=[n];function h(p,o,r,k,u,d){return a(),i("div",null,l)}const g=s(e,[["render",h]]);export{c as __pageData,g as default}; diff --git a/assets/public_kronos_docs_challenges.md.DjtWlrsA.js b/assets/public_kronos_docs_challenges.md.DjtWlrsA.js deleted file mode 100644 index a7daa11f..00000000 --- a/assets/public_kronos_docs_challenges.md.DjtWlrsA.js +++ /dev/null @@ -1,9 +0,0 @@ -import{_ as e,c as t,o as i,a5 as a}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Challenges","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/challenges.md","filePath":"public/kronos/docs/challenges.md"}'),s={name:"public/kronos/docs/challenges.md"},n=a(`

Challenges ​

Challenges can have fully customizable win conditions. Useful functions for dealing with Challenges and implementing their effects:

  • inChallenge(layer, id): determine if the player is in a given challenge (or another challenge on the same layer that counts as this one).
  • hasChallenge(layer, id): determine if the player has completed the challenge.
  • challengeCompletions(layer, id): determine how many times the player completed the challenge.
  • maxedChallenge(layer, id): determines if the player has reached the maximum completions.
  • challengeEffect(layer, id): Returns the current effects of the challenge, if any.

Challenges are stored in the following format:

js
challenges: {
-    11: {
-        name: "Ouch",
-        challengeDescription: "description of ouchie",
-        canComplete: function() {return player.points.gte(100)},
-        etc
-    },
-    etc
-}

Usually, each challenge should have an id where the first digit is the row and the second digit is the column.

Individual Challenges can have these features:

  • name: Name of the challenge, can be a string or a function. Can use basic HTML.

  • challengeDescription: A description of what makes the challenge a challenge. You will need to implement these elsewhere. It can also be a function that returns updating text. Can use basic HTML.

  • goalDescription: A description of the win condition for the challenge. It can also be a function that returns updating text. Can use basic HTML. (Optional if using the old goal system)

  • canComplete(): A function that returns true if you meet the win condition for the challenge. Returning a number will allow bulk completing the challenge. (Optional if using the old goal system)

  • rewardDescription: A description of the reward's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

  • rewardEffect(): optional. A function that calculates and returns the current values of any bonuses from the reward. Can return a value or an object containing multiple values. Can use basic HTML.

  • rewardDisplay(): optional. A function that returns a display of the current effects of the reward with formatting. Default behavior is to just display the a number appropriately formatted.

  • fullDisplay(): OVERRIDE. Overrides the other displays and descriptions, and lets you set the full text for the challenge. Can use basic HTML.

  • unlocked(): optional. A function returning a bool to determine if the challenge is visible or not. Default is unlocked.

  • onComplete() - optional. this function will be called when the challenge is completed when previously incomplete.

  • onEnter() - optional. this function will be called when entering the challenge

  • onExit() - optional. this function will be called when exiting the challenge in any way

  • countsAs: optional. If a challenge combines the effects of other challenges in this layer, you can use this. An array of challenge ids. The player is effectively in all of those challenges when in the current one.

  • completionLimit: optional. the amount of times you can complete this challenge. Default is 1 completion.

  • style: optional. Applies CSS to this challenge, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • marked: optional Adds a mark to the corner of the challenge. If it's "true" it will be a star, but it can also be an image URL. By default, if the challenge has multiple completions, it will be starred at max completions.

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: assigned automagically. It's the "key" which the challenge was stored under, for convenient access. The challenge in the example's id is 11.

The old goal system uses these features:

  • goal: deprecated, A Decimal for the amount of currency required to beat the challenge. By default, the goal is in basic Points. The goal can also be a function if its value changes.

  • currencyDisplayName: deprecated. the name to display for the currency for the goal

  • currencyInternalName: deprecated. the internal name for that currency

  • currencyLayer: deprecated. the internal name of the layer that currency is stored in. If it's not in a layer, omit. If it's not stored directly in a layer, instead use the next feature.

  • currencyLocation(): deprecated. if your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

`,10),l=[n];function o(h,r,p,c,g,u){return i(),t("div",null,l)}const y=e(s,[["render",o]]);export{f as __pageData,y as default}; diff --git a/assets/public_kronos_docs_challenges.md.DjtWlrsA.lean.js b/assets/public_kronos_docs_challenges.md.DjtWlrsA.lean.js deleted file mode 100644 index 85059839..00000000 --- a/assets/public_kronos_docs_challenges.md.DjtWlrsA.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as i,a5 as a}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Challenges","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/challenges.md","filePath":"public/kronos/docs/challenges.md"}'),s={name:"public/kronos/docs/challenges.md"},n=a("",10),l=[n];function o(h,r,p,c,g,u){return i(),t("div",null,l)}const y=e(s,[["render",o]]);export{f as __pageData,y as default}; diff --git a/assets/public_kronos_docs_clickables.md.BvrZ942x.js b/assets/public_kronos_docs_clickables.md.BvrZ942x.js deleted file mode 100644 index 4840959a..00000000 --- a/assets/public_kronos_docs_clickables.md.BvrZ942x.js +++ /dev/null @@ -1,7 +0,0 @@ -import{_ as e,c as t,o as a,a5 as s}from"./chunks/framework.CK8QU5WH.js";const b=JSON.parse('{"title":"Clickables","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/clickables.md","filePath":"public/kronos/docs/clickables.md"}'),i={name:"public/kronos/docs/clickables.md"},l=s(`

Clickables ​

Clickables are any kind of thing that you can click for an effect. They're a more generalized version of Buyables.

DO NOT USE THESE TO MAKE THINGS THAT YOU CLICK REPEATEDLY FOR A BONUS BECAUSE THOSE ARE AWFUL.

There are several differences between the two. One is that a buyable's saved data is its amount as a Decimal, while Clickables store a "state" which can be a number or string, but not Decimal, array, or object). Buyables have a number of extra features which you can see on their page. Clickables also have a smaller default size.

Useful functions for dealing with clickables and implementing their effects:

  • getClickableState(layer, id): get the state of the clickable the player has
  • setClickableState(layer, id, state): set the state of the clickable the player has
  • clickableEffect(layer, id): Returns the current effects of the clickable, if any.

Clickables should be formatted like this:

js
clickables: {
-    11: {
-        display() {return "Blah"},
-        etc
-    }
-    etc
-}

Features:

  • title: optional. displayed at the top in a larger font. It can also be a function that returns updating text.

  • effect(): optional. A function that calculates and returns the current values of bonuses of this clickable. Can return a value or an object containing multiple values.

  • display(): A function returning everything that should be displayed on the clickable after the title, likely changing based on its state. Can use basic HTML.

  • unlocked(): optional. A function returning a bool to determine if the clickable is visible or not. Default is unlocked.

  • canClick(): A function returning a bool to determine if you can click the clickable.

  • onClick(): A function that implements clicking the clickable.

  • onHold(): optional A function that is called 20x/sec when the button is held for at least 0.25 seconds.

  • style: optional. Applies CSS to this clickable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • marked: optional Adds a mark to the corner of the clickable. If it's "true" it will be a star, but it can also be an image URL.

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

  • id: assigned automagically. It's the "key" which the clickable was stored under, for convenient access. The clickable in the example's id is 11.

You can also use these features on the clickables object to add a button above all the clickables, for implementing a respec button or similar.

  • masterButtonPress(): optional. If present, an additional button will appear above the clickables. Pressing it will call this function.

  • masterButtonText: optional. Text to display on the Master Button.

  • showMasterButton(): optional. A function determining whether or not to show the button, if masterButtonPress is defined. Defaults to true if absent.

`,12),n=[l];function o(c,r,p,h,u,d){return a(),t("div",null,n)}const g=e(i,[["render",o]]);export{b as __pageData,g as default}; diff --git a/assets/public_kronos_docs_clickables.md.BvrZ942x.lean.js b/assets/public_kronos_docs_clickables.md.BvrZ942x.lean.js deleted file mode 100644 index 603146ae..00000000 --- a/assets/public_kronos_docs_clickables.md.BvrZ942x.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as s}from"./chunks/framework.CK8QU5WH.js";const b=JSON.parse('{"title":"Clickables","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/clickables.md","filePath":"public/kronos/docs/clickables.md"}'),i={name:"public/kronos/docs/clickables.md"},l=s("",12),n=[l];function o(c,r,p,h,u,d){return a(),t("div",null,n)}const g=e(i,[["render",o]]);export{b as __pageData,g as default}; diff --git a/assets/public_kronos_docs_custom-tab-layouts.md.C9uDrIM0.js b/assets/public_kronos_docs_custom-tab-layouts.md.C9uDrIM0.js deleted file mode 100644 index a2a51bdd..00000000 --- a/assets/public_kronos_docs_custom-tab-layouts.md.C9uDrIM0.js +++ /dev/null @@ -1,14 +0,0 @@ -import{_ as s,c as a,o as i,a5 as t}from"./chunks/framework.CK8QU5WH.js";const c=JSON.parse('{"title":"Custom tab layouts","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/custom-tab-layouts.md","filePath":"public/kronos/docs/custom-tab-layouts.md"}'),e={name:"public/kronos/docs/custom-tab-layouts.md"},n=t(`

Custom tab layouts ​

Note: If you are using subtabs, tabFormat is used differently, but the same format is used for defining their layouts. See here for more on subtabs.

Custom tab layouts can be used to do basically anything in a tab window, especially combined with the "style" layer feature. The tabFormat feature is an array of things, like this:

js
tabFormat: [
-    "main-display",
-    ["prestige-button", function() { return "Melt your points into " }],
-    "blank",
-    ["display-text",
-        function() { return 'I have ' + format(player.points) + ' pointy points!' },
-        { "color": "red", "font-size": "32px", "font-family": "Comic Sans MS" }],
-    "blank",
-    ["toggle", ["c", "beep"]],
-    "milestones",
-    "blank",
-    "blank",
-    "upgrades"
-]

It is a list of components, which can be either just a name, or an array with arguments. If it's an array, the first item is the name of the component, the second is the data passed into it, and the third (optional) applies a CSS style to it with a "CSS object", where the keys are CSS attributes.

These are the existing components, but you can create more in components.js:

  • display-text: Displays some text (can use basic HTML). The argument is the text to display. It can also be a function that returns updating text.

  • raw-html: Displays some basic HTML, can also be a function.

  • blank: Adds empty space. The default dimensions are 8px x 17px. The argument changes the dimensions. If it's a single value (e.g. "20px"), that determines the height. If you have a pair of arguments, the first is width and the second is height.

  • row: Display a list of components horizontally. The argument is an array of components in the tab layout format.

  • column: Display a list of components vertically. The argument is an array of components in the tab layout format. This is useful to display columns within a row.

  • main-display: The text that displays the main currency for the layer and its effects. The argument is the amount of precision to use, allowing it to display non-whole numbers.

  • resource-display: The text that displays the currency that this layer is based on, as well as the best and/or total values for this layer's prestige currency (if they are put in startData for this layer).

  • prestige-button: The argument is a string that the prestige button should say before the amount of currency you will gain. It can also be a function that returns updating text.

  • text-input: A text input box. The argument is the name of the variable in player[layer] that the input is for, player[layer][argument] (Works with strings, numbers, and Decimals!)

  • slider: Lets the user input a value with a slider. The argument a 3-element array: [name, min, max]. The name is the name of the variable in player[layer] that the input that the input is for, and min and max are the limits of the slider. (Does not work for Decimal values)

  • upgrades: The layer's upgrades. The argument is optional, and is a the list of rows this component should include, if it doesn't have all of them.

  • milestones, challenges, achievements: Display the upgrades, milestones, and challenges for a layer, as appropriate.

  • buyables, clickables: Display all of the buyables/clickables for this layer, as appropriate. The argument is optional and is the size of the boxes in pixels.

  • microtabs: Display a set of subtabs for an area. The argument is the name of the set of microtabs in the "microtabs" feature.

  • bar: Display a bar. The argument is the id of the bar to display.

  • infobox: Display an infobox. The argument is the id of the infobox to display.

  • tree: Displays a tree. The argument is an array of arrays containing the names of the nodes in the tree (first by row, then by column) See here for more information on tree layouts and nodes!

  • toggle: A toggle button that toggles a bool value. The argument is a pair that identifies the location in player of the bool to toggle, e.g. [layer, id]. 'layer' also affects the color of the toggle.

  • grid: Displays the gridable grid for the layer. If you need more than one grid, use a layer proxy.

  • layer-proxy: Lets you use components from another layer. The argument is a pair, [layer, data], consisting of the id of the layer to proxy from, and the tabFormat for the components to show. (Note: you cannot use a microtab within a layer proxy)

The rest of the components are sub-components. They can be used just like other components, but are typically part of another component.

  • upgrade, milestone, challenge, buyable, clickable, achievement, gridable: An individual upgrade, challenge, etc. The argument is the id. This can be used if you want to have upgrades split up across multiple subtabs, for example.

  • respec-button, master-button: The respec and master buttons for buyables and clickables, respectively.

  • sell-one, sell-all: The "sell one" and "sell all" for buyables, respectively. The argument is the id of the buyable.

`,9),l=[n];function o(h,p,r,u,k,d){return i(),a("div",null,l)}const g=s(e,[["render",o]]);export{c as __pageData,g as default}; diff --git a/assets/public_kronos_docs_custom-tab-layouts.md.C9uDrIM0.lean.js b/assets/public_kronos_docs_custom-tab-layouts.md.C9uDrIM0.lean.js deleted file mode 100644 index cab752e3..00000000 --- a/assets/public_kronos_docs_custom-tab-layouts.md.C9uDrIM0.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as a,o as i,a5 as t}from"./chunks/framework.CK8QU5WH.js";const c=JSON.parse('{"title":"Custom tab layouts","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/custom-tab-layouts.md","filePath":"public/kronos/docs/custom-tab-layouts.md"}'),e={name:"public/kronos/docs/custom-tab-layouts.md"},n=t("",9),l=[n];function o(h,p,r,u,k,d){return i(),a("div",null,l)}const g=s(e,[["render",o]]);export{c as __pageData,g as default}; diff --git a/assets/public_kronos_docs_getting-started.md.mdR9VU7R.js b/assets/public_kronos_docs_getting-started.md.mdR9VU7R.js deleted file mode 100644 index b2e9b3ad..00000000 --- a/assets/public_kronos_docs_getting-started.md.mdR9VU7R.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o,a5 as i}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Getting started","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/getting-started.md","filePath":"public/kronos/docs/getting-started.md"}'),a={name:"public/kronos/docs/getting-started.md"},n=i('

Getting started ​

Welcome to The Modding Tree!

Using the Modding Tree, at its simplest level, just requires getting a copy of it onto your computer. However, if you do it the right way, it will help in many ways.

Don't let the word "Github" scare you away. It's actually much easier to use than most people think, especially because most people use it the hard way. The key is Github Desktop, which lets you do everything you need to, without even touching the command line.

The benefits of using Github:

  • It makes it much, much easier to update The Modding Tree.
  • You can share your work without any extra effort using githack, or with a bit more effort, set up a github.io site.
  • It lets you undo changes to your code, and to have multiple versions of it.
  • It lets you collaborate with other people, if you want to.

Getting set up with Github Desktop, Visual Studio Code, and The Modding Tree: ​

  1. Install Github Desktop and Visual Studio Code.

  2. Make a Github account. You can handle this on your own.

  3. Log in on your browser, and go back to The Modding Tree page. At the top right, there should be a button that says "fork". Click on it, and then on your username. You now have your own fork, or copy, of The Modding Tree.

  4. Open Github Desktop and log in. Ignore everything else and choose "clone a repository". A "repository" is basically a "Github project", like The Modding Tree. "Cloning" is downloading a copy of the repository to your computer.

  5. Look for The Modding Tree in the list of repositiories (it should be the only one) and click "clone".

  6. Select that you're using it for your own purposes, and click continue. It will download the files and handle everything.

Using your repository ​

  1. Click on "show in explorer/finder" to the right, and then open the index.html file in the folder. The page should open up on your browser. This will let you view and test your project locally!

  2. To edit your project, click "open in VSCode" in Github Desktop.

  3. Open mod.js in VSCode, and look at the top part where it has a "modInfo" object. Fill in your mod's name to whatever you want, and change the id as well. (It can be any string value, and it's used to determine where the savefile is. Make it something that's probably unique, and don't change it again later or else it'll effectively wipe existing saves)

  4. Save mod.js, and then reload index.html in your browser. The title on the tab, as well as on the info page, will now be updated! You can reload the page every time you change the code to test it quickly and easily.

  5. Go back to Github Desktop. It's time to save your changes into the git system by making a "commit". This basically saves your work and creates a snapshot of what your code looks like at this moment, allowing you to look back at it later.

  6. At the bottom right corner, add a summary of your changes, and then click "commit to master".

  7. Finally, at the top middle, click "push origin" to push your changes out onto the online repository.

  8. You can view your project on line, or share it with others, by going to https://raw.githack.com/[YOUR-GITHUB-USERNAME]/The-Modding-Tree/master/index.html

And now, you have successfully used Github! You can look at the documentation to see how The Modding Tree's system works and to make your mod a reality.

',11),r=[n];function s(l,h,u,d,p,c){return o(),t("div",null,r)}const m=e(a,[["render",s]]);export{y as __pageData,m as default}; diff --git a/assets/public_kronos_docs_getting-started.md.mdR9VU7R.lean.js b/assets/public_kronos_docs_getting-started.md.mdR9VU7R.lean.js deleted file mode 100644 index 87e5df28..00000000 --- a/assets/public_kronos_docs_getting-started.md.mdR9VU7R.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o,a5 as i}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Getting started","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/getting-started.md","filePath":"public/kronos/docs/getting-started.md"}'),a={name:"public/kronos/docs/getting-started.md"},n=i("",11),r=[n];function s(l,h,u,d,p,c){return o(),t("div",null,r)}const m=e(a,[["render",s]]);export{y as __pageData,m as default}; diff --git a/assets/public_kronos_docs_grids.md.BeCPe1VG.js b/assets/public_kronos_docs_grids.md.BeCPe1VG.js deleted file mode 100644 index 10942928..00000000 --- a/assets/public_kronos_docs_grids.md.BeCPe1VG.js +++ /dev/null @@ -1,21 +0,0 @@ -import{_ as s,c as i,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Grids","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/grids.md","filePath":"public/kronos/docs/grids.md"}'),e={name:"public/kronos/docs/grids.md"},n=t(`

Grids ​

Grids are an easier way of making a group of similar clickables. They all have the same behavior, but are different based on their data.

NOTE: Gridables are similar to clickables in some respects, but are fundamentally different from normal TMT components in quite a few ways. Be sure to keep these in mind:

  • Gridable ids use base 100 instead of base 10, so you can have more than 10 tiles in a row. This means that a grid might look like this: 101 102 201 202
  • Individual gridables are not defined individually. All properties go directly into the "grid" object. Functions are called with arguments for the id of the gridables and its associated data, so you can give them the appropriate appearance and properties based on that.
  • If you need two unrelated grids in a layer, you'll need to use a layer proxy component.

Useful functions for dealing with grids:

  • getGridData(layer, id): get the data for the chosen gridable
  • setGridData(layer, id, state): set the data for the chosen gridable
  • gridEffect(layer, id): get the effect for the chosen gridable

The grid should be formatted like this:

js
grid: {
-    rows: 4, // If these are dynamic make sure to have a max value as well!
-    cols: 5,
-    getStartData(id) {
-        return 0
-    },
-    getUnlocked(id) { // Default
-        return true
-    },
-    getCanClick(data, id) {
-        return true
-    },
-    onClick(data, id) { 
-        player[this.layer].grid[id]++
-    },
-    getDisplay(data, id) {
-        return data 
-    },
-
-    etc
-}

Features:

  • rows, cols: The amount of rows and columns of gridable to display.

  • maxRows, maxCols: sometimes needed. If rows or cols are dynamic, you need to define the maximum amount that there can be (you can increase it when you update the game though). These CANNOT be dynamic.

  • getStartData(id): Creates the default data for the gridable at this position. This can be an object, or a regular value.

  • getUnlocked(id): optional. Returns true if the gridable at this position should be visible.

  • getTitle(data, id): optional. Returns text that should displayed at the top in a larger font, based on the position and data of the gridable.

  • getDisplay(data, id): optional. Returns everything that should be displayed on the gridable after the title, based on the position and data of the gridable.

  • getStyle(data, id): optional. Returns CSS to apply to this gridable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • getCanClick(data, id): optional. A function returning a bool to determine if you can click a gridable, based on its data and position. If absent, you can always click it.

  • onClick(data, id): A function that implements clicking on the gridable, based on its position and data.

  • onHold(data, id): optional A function that is called 20x/sec when the button is held for at least 0.25 seconds.

  • getEffect(data, id): optional. A function that calculates and returns a gridable's effect, based on its position and data. (Whatever that means for a gridable)

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

`,10),l=[n];function r(h,p,o,d,k,g){return a(),i("div",null,l)}const y=s(e,[["render",r]]);export{u as __pageData,y as default}; diff --git a/assets/public_kronos_docs_grids.md.BeCPe1VG.lean.js b/assets/public_kronos_docs_grids.md.BeCPe1VG.lean.js deleted file mode 100644 index 09147169..00000000 --- a/assets/public_kronos_docs_grids.md.BeCPe1VG.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as i,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Grids","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/grids.md","filePath":"public/kronos/docs/grids.md"}'),e={name:"public/kronos/docs/grids.md"},n=t("",10),l=[n];function r(h,p,o,d,k,g){return a(),i("div",null,l)}const y=s(e,[["render",r]]);export{u as __pageData,y as default}; diff --git a/assets/public_kronos_docs_infoboxes.md.cE2lKUcU.js b/assets/public_kronos_docs_infoboxes.md.cE2lKUcU.js deleted file mode 100644 index d579781a..00000000 --- a/assets/public_kronos_docs_infoboxes.md.cE2lKUcU.js +++ /dev/null @@ -1,8 +0,0 @@ -import{_ as s,c as i,o as e,a5 as a}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Infoboxes","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/infoboxes.md","filePath":"public/kronos/docs/infoboxes.md"}'),t={name:"public/kronos/docs/infoboxes.md"},n=a(`

Infoboxes ​

Infoboxes are good for displaying "lore", or story elements, as well as for explaining complicated things.

In the default tab layout, the first infobox will be displayed at the very top of the tab.

Infoboxes are defined like other Big Features:

js
infoboxes: {
-    lore: {
-        title: "foo",
-        body() { return "bar" },
-        etc
-    },
-    etc
-}

Features:

  • title: The text displayed above the main box. Can be a function to be dynamic, and can use basic HTML.

  • body: The text displayed inside the box. Can be a function to be dynamic, and can use basic HTML.

  • style, titleStyle, bodyStyle: optional. Apply CSS to the infobox, or to the title button or body of the infobox, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • unlocked(): optional. A function returning a bool to determine if the infobox is visible or not. Default is unlocked.

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: assigned automagically. It's the "key" which the bar was stored under, for convenient access. The infobox in the example's id is "lore".

`,7),o=[n];function l(p,h,r,d,c,k){return e(),i("div",null,o)}const y=s(t,[["render",l]]);export{u as __pageData,y as default}; diff --git a/assets/public_kronos_docs_infoboxes.md.cE2lKUcU.lean.js b/assets/public_kronos_docs_infoboxes.md.cE2lKUcU.lean.js deleted file mode 100644 index 37d39085..00000000 --- a/assets/public_kronos_docs_infoboxes.md.cE2lKUcU.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as i,o as e,a5 as a}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Infoboxes","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/infoboxes.md","filePath":"public/kronos/docs/infoboxes.md"}'),t={name:"public/kronos/docs/infoboxes.md"},n=a("",7),o=[n];function l(p,h,r,d,c,k){return e(),i("div",null,o)}const y=s(t,[["render",l]]);export{u as __pageData,y as default}; diff --git a/assets/public_kronos_docs_layer-features.md.sKwRGXXx.js b/assets/public_kronos_docs_layer-features.md.sKwRGXXx.js deleted file mode 100644 index ca28a74e..00000000 --- a/assets/public_kronos_docs_layer-features.md.sKwRGXXx.js +++ /dev/null @@ -1,11 +0,0 @@ -import{_ as e,c as t,o as a,a5 as s}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Layer Features","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/layer-features.md","filePath":"public/kronos/docs/layer-features.md"}'),i={name:"public/kronos/docs/layer-features.md"},o=s(`

Layer Features ​

This is a more comprehensive list of established features to add to layers. You can add more freely, if you want to have other functions or values associated with your layer. These have special functionality, though.

You can make almost any value dynamic by using a function in its place, including all display strings and styling/color features.

Layer Definition features ​

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar to access the saved value. It makes copying code to new layers easier. It is also assigned to all upgrades and buyables and such.

  • name: optional. used in reset confirmations (and the default infobox title). If absent, it just uses the layer's id.

  • startData(): A function to return the default save data for this layer. Add any variables you have to it. Make sure to use Decimal values rather than normal numbers.

    Standard values: - Required: - unlocked: a bool determining if this layer is unlocked or not - points: a Decimal, the main currency for the layer - Optional: - total: A Decimal, tracks total amount of main prestige currency. Always tracked, but only shown if you add it here. - best: A Decimal, tracks highest amount of main prestige currency. Always tracked, but only shown if you add it here. - unlockOrder: used to keep track of relevant layers unlocked before this one. - resetTime: A number, time since this layer was last prestiged (or reset by another layer)

  • color: A color associated with this layer, used in many places. (A string in hex format with a #)

  • row: The row of the layer, starting at 0. This affects where the node appears on the standard tree, and which resets affect the layer.

    Using "side" instead of a number will cause the layer to appear off to the side as a smaller node (useful for achievements and statistics). Side layers are not affected by resets unless you add a doReset to them.

  • displayRow: OVERRIDE Changes where the layer node appears without changing where it is in the reset order.

  • resource: Name of the main currency you gain by resetting on this layer.

  • effect(): optional. A function that calculates and returns the current values of any bonuses inherent to the main currency. Can return a value or an object containing multiple values. You will also have to implement the effect where it is applied.

  • effectDescription: optional. A function that returns a description of this effect. If the text stays constant, it can just be a string.

  • layerShown(): optional, A function returning a bool which determines if this layer's node should be visible on the tree. It can also return "ghost", which will hide the layer, but its node will still take up space in the tree. Defaults to true.

  • hotkeys: optional. An array containing information on any hotkeys associated with this layer:

    js
    hotkeys: [
-    {
-        key: "p", // What the hotkey button is. Use uppercase if it's combined with shift, or "ctrl+x" for holding down ctrl.
-        description: "p: reset your points for prestige points", // The description of the hotkey that is displayed in the game's How To Play tab
-        onPress() { if (player.p.unlocked) doReset("p") },
-        unlocked() {return hasMilestone('p', 3)} // Determines if you can use the hotkey, optional
-    }
-]

  • style: optional. a "CSS object" where the keys are CSS attributes, containing any CSS that should affect this layer's entire tab.

  • tabFormat: optional. use this if you want to add extra things to your tab or change the layout. See here for more info.

  • midsection: optional, an alternative to tabFormat, which is inserted in between Milestones and Buyables in the standard tab layout. (cannot do subtabs)

Big features (all optional) ​

  • upgrades: A set of one-time purchases which can have unique upgrade conditions, currency costs, and bonuses. See here for more info.

  • milestones: A list of bonuses gained upon reaching certain thresholds of a resource. Often used for automation/QOL. See here for more info.

  • challenges: The player can enter challenges, which make the game harder. If they reach a goal and beat the challenge, they recieve a bonus. See here for more info.

  • buyables: Effectively upgrades that can be bought multiple times, and are optionally respeccable. Many uses. See here for more info.

  • clickables: Extremely versatile and generalized buttons which can only be clicked sometimes. See here for more info.

  • microtabs: An area that functions like a set of subtabs, with buttons at the top changing the content within. (Advanced) See here for more info.

  • bars: Display some information as a progress bar, gague, or similar. They are highly customizable, and can be vertical as well. See here for more info.

  • achievements: Kind of like milestones, but with a different display style and some other differences. Extra features are on the way at a later date! See here for more info.

  • achievementPopups, milestonePopups: optional, If false, disables popup message when you get the achievement/milestone. True by default.

  • infoboxes: Displays some text in a box that can be shown or hidden. See here for more info.

  • grid: A grid of buttons that behave the same, but have their own data.See here for more info.

Prestige formula features ​

  • type: optional. Determines which prestige formula you use. Defaults to "none".

    • "normal": The amount of currency you gain is independent of its current amount (like Prestige). The formula before bonuses is based on baseResource^exponent
    • "static": The cost is dependent on your total after reset. The formula before bonuses is based on base^(x^exponent)
    • "custom": You can define everything, from the calculations to the text on the button, yourself. (See more at the bottom)
    • "none": This layer does not prestige, and therefore does not need any of the other features in this section.

  • baseResource: The name of the resource that determines how much of the main currency you gain on reset.

  • baseAmount(): A function that gets the current value of the base resource.

  • requires: A Decimal, the amount of the base needed to gain 1 of the prestige currency. Also the amount required to unlock the layer. You can instead make this a function, to make it harder if another layer was unlocked first (based on unlockOrder).

  • exponent: Used as described above.

  • base: sometimes required. required for "static" layers, used as described above. If absent, defaults to 2. Must be greater than 1.

  • roundUpCost: optional. a bool, which is true if the resource cost needs to be rounded up. (use if the base resource is a "static" currency.)

  • gainMult(), gainExp(): optional. For normal layers, these functions calculate the multiplier and exponent on resource gain from upgrades and boosts and such. Plug in most bonuses here. For static layers, they instead divide and root the cost of the resource.

  • directMult(): optional. Directly multiplies the resource gain, after exponents and softcaps. For static layers, actually multiplies resource gain instead of reducing the cost.

  • softcap, softcapPower: optional. For normal layers, gain beyond [softcap] points is put to the [softcapPower]th power Default for softcap is e1e7, and for power is 0.5.

  • canBuyMax(): sometimes required. required for static layers, function used to determine if buying max is permitted.

  • onPrestige(gain): optional. A function that triggers when this layer prestiges, just before you gain the currency. Can be used to have secondary resource gain on prestige, or to recalculate things or whatnot.

  • resetDescription: optional. Use this to replace "Reset for " on the Prestige button with something else.

  • prestigeButtonText(): sometimes required. Use this to make the entirety of the text a Prestige button contains. Only required for custom layers, but usable by all types.

  • passiveGeneration(): optional, returns a regular number. You automatically generate your gain times this number every second (does nothing if absent) This is good for automating Normal layers.

  • autoPrestige(): optional, returns a boolean, if true, the layer will always automatically do a prestige if it can. This is good for automating Static layers.

Tree/node features ​

  • symbol: optional. The text that appears on this layer's node. Default is the layer id with the first letter capitalized.

  • image: override. The url (local or global) of an image that goes on the node. (Overrides symbol)

  • position: optional. Determines the horizontal position of the layer in its row in a standard tree. By default, it uses the layer id, and layers are sorted in alphabetical order.

  • branches: optional. An array of layer/node ids. On a tree, a line will appear from this layer to all of the layers in the list. Alternatively, an entry in the array can be a 2-element array consisting of the layer id and a color value. The color value can either be a string with a hex color code, or a number from 1-3 (theme-affected colors).

  • nodeStyle: optional. A CSS object, where the keys are CSS attributes, which styles this layer's node on the tree.

  • tooltip() / tooltipLocked(): optional. Functions that return text, which is the tooltip for the node when the layer is unlocked or locked, respectively. By default the tooltips behave the same as in the original Prestige Tree. If the value is "", the tooltip will be disabled.

  • marked: optional Adds a mark to the corner of the node. If it's "true" it will be a star, but it can also be an image URL.

Other features ​

  • doReset(resettingLayer): optional. Is triggered when a layer on a row greater than or equal to this one does a reset. The default behavior is to reset everything on the row, but only if it was triggered by a layer in a higher row. doReset is always called for side layers, but for these the default behavior is to reset nothing.

    If you want to keep things, determine what to keep based on resettingLayer, milestones, and such, then call layerDataReset(layer, keep), where layer is this layer, and keep is an array of the names of things to keep. It can include things like "points", "best", "total" (for this layer's prestige currency), "upgrades", any unique variables like "generatorPower", etc. If you want to only keep specific upgrades or something like that, save them in a separate variable, then call layerDataReset, and then set player[this.layer].upgrades to the saved upgrades.

  • update(diff): optional. This function is called every game tick. Use it for any passive resource production or time-based things. diff is the time since the last tick.

  • autoUpgrade: optional, a boolean value, if true, the game will attempt to buy this layer's upgrades every tick. Defaults to false.

  • automate(): optional. This function is called every game tick, after production. Use it to activate automation things that aren't otherwise supported.

  • resetsNothing: optional. Returns true if this layer shouldn't trigger any resets when you prestige.

  • increaseUnlockOrder: optional. An array of layer ids. When this layer is unlocked for the first time, the unlockOrder value for any not-yet-unlocked layers in this list increases. This can be used to make them harder to unlock.

  • shouldNotify: optional. A function to return true if this layer should be highlighted in the tree. The layer will automatically be highlighted if you can buy an upgrade whether you have this or not.

  • glowColor: optional. The color that this layer will be highlighted if it should notify. The default is red. You can use this if you want several different notification types!

  • componentStyles: optional. An object that contains a set of functions returning CSS objects. Each of these will be applied to any components on the layer with the type of its id. Example:

js
componentStyles: {
-    "challenge"() { return {'height': '200px'} },
-    "prestige-button"() { return {'color': '#AA66AA'} }
-}
  • deactivated: optional, if this is true, hasUpgrade, hasChallenge, hasAchievement, and hasMilestone will return false for things in the layer, and you will be unable to buy or click things on the layer. You will have to disable effects of buyables, the innate layer effect, and possibly other things yourself.

Custom Prestige type ​

(All of these can also be used by other prestige types)

  • getResetGain(): mostly for custom prestige type. Returns how many points you should get if you reset now. You can call getResetGain(this.layer, useType = "static") or similar to calculate what your gain would be under another prestige type (provided you have all of the required features in the layer).

  • getNextAt(canMax=false): mostly for custom prestige type. Returns how many of the base currency you need to get to the next point. canMax is an optional variable used with Static-ish layers to differentiate between if it's looking for the first point you can reset at, or the requirement for any gain at all (Supporting both is good). You can also call getNextAt(this.layer, canMax=false, useType = "static") or similar to calculate what your next at would be under another prestige type (provided you have all of the required features in the layer).

  • canReset(): mostly for custom prestige type. Return true only if you have the resources required to do a prestige here.

  • prestigeNotify(): mostly for custom prestige types, returns true if this layer should be subtly highlighted to indicate you can prestige for a meaningful gain.

`,20),r=[o];function n(l,h,p,u,d,c){return a(),t("div",null,r)}const f=e(i,[["render",n]]);export{y as __pageData,f as default}; diff --git a/assets/public_kronos_docs_layer-features.md.sKwRGXXx.lean.js b/assets/public_kronos_docs_layer-features.md.sKwRGXXx.lean.js deleted file mode 100644 index e027b7d5..00000000 --- a/assets/public_kronos_docs_layer-features.md.sKwRGXXx.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as s}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Layer Features","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/layer-features.md","filePath":"public/kronos/docs/layer-features.md"}'),i={name:"public/kronos/docs/layer-features.md"},o=s("",20),r=[o];function n(l,h,p,u,d,c){return a(),t("div",null,r)}const f=e(i,[["render",n]]);export{y as __pageData,f as default}; diff --git a/assets/public_kronos_docs_main-mod-info.md.CV8Og8jf.js b/assets/public_kronos_docs_main-mod-info.md.CV8Og8jf.js deleted file mode 100644 index 40c13ef7..00000000 --- a/assets/public_kronos_docs_main-mod-info.md.CV8Og8jf.js +++ /dev/null @@ -1,5 +0,0 @@ -import{_ as i,c as e,o as t,a5 as s}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"mod.js","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/main-mod-info.md","filePath":"public/kronos/docs/main-mod-info.md"}'),a={name:"public/kronos/docs/main-mod-info.md"},n=s(`

mod.js ​

Most of the non-layer code and data that you're likely to edit is here in mod.js. Everything in mod.js will not be altered by updates, besides the addition of new things.

Here's a breakdown of what's in it:

  • modInfo is where most of the basic configuration for the mod is. It contains:

    • name: The name of your mod. (a string)

    • id: The id for your mod, a unique string that is used to determine savefile location. Be sure to set it when you start making a mod, and don't change it later because it will erase all saves.

    • author: The name of the author, displayed in the info tab.

    • pointsName: This changes what is displayed instead of "points" for the main currency. (It does not affect it in the code.)

    • discordName, discordLink: If you have a Discord server or other discussion place, you can add a link to it.

      "discordName" is the text on the link, and "discordLink" is the url of an invite. If you're using a Discord invite, please make sure it's set to never expire.

    • offlineLimit: The maximum amount of offline time that the player can accumulate, in hours. Any extra time is lost. (a number)

      This is useful because most of these mods are fast-paced enough that too much offline time ruins the balance, such as the time in between updates. That is why I suggest developers disable offline time on their own savefile.

    • initialStartPoints: A Decimal for the amount of points a new player should start with.

  • VERSION is used to describe the current version of your mod. It contains:

    • num: The mod's version number, displayed at the top right of the tree tab.
    • name: The version's name, displayed alongside the number in the info tab.

  • changelog is the HTML displayed in the changelog tab. If this gets particularly long, it might be good to put in a separate file (be sure to add the file to index.html)

  • doNotCallTheseFunctionsEveryTick is very important, if you are adding non-standard functions. TMT calls every function anywhere in "layers" every tick to store the result, unless specifically told not to. Functions that have are used to do an action need to be identified. "Official" functions (those in the documentation) are all fine, but if you make any new ones, add their names to this array.

js
// (The ones here are examples, all official functions are already taken care of)
-var doNotCallTheseFunctionsEveryTick = ["doReset", "buy", "onPurchase", "blowUpEverything"]

  • getStartPoints(): A function to determine the amount of points the player starts with after a reset. (returns a Decimal value)

  • canGenPoints(): A function returning a boolean for if points should be generated. Use this if you want an upgrade to unlock generating points.

  • getPointGen(): A function that calculates your points per second. Anything that affects your point gain should go into the calculation here.

  • addedPlayerData(): A function that returns any non-layer-related data that you want to be added to the save data and "player" object.

js
function addedPlayerData() { return {
-	weather: "Yes",
-	happiness: new Decimal(72),
-}}

  • displayThings: An array of functions used to display extra things at the top of the tree tab. Each function returns a string, which is a line to display (with basic HTML support). If a function returns nothing, nothing is displayed (and it doesn't take up a line).

  • isEndgame(): A function to determine if the player has reached the end of the game, at which point the "you win!" screen appears.

Less important things beyond this point!

  • maxTickLength(): Returns the maximum tick length, in milliseconds. Only really useful if you have something that reduces over time, which long ticks mess up (usually a challenge).

  • fixOldSave(): Can be used to modify a save file when loading into a new version of the game. Use this to undo inflation, never forcibly hard reset your players.

`,10),o=[n];function l(h,r,p,d,u,c){return t(),e("div",null,o)}const y=i(a,[["render",l]]);export{f as __pageData,y as default}; diff --git a/assets/public_kronos_docs_main-mod-info.md.CV8Og8jf.lean.js b/assets/public_kronos_docs_main-mod-info.md.CV8Og8jf.lean.js deleted file mode 100644 index a7a79ebe..00000000 --- a/assets/public_kronos_docs_main-mod-info.md.CV8Og8jf.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as i,c as e,o as t,a5 as s}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"mod.js","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/main-mod-info.md","filePath":"public/kronos/docs/main-mod-info.md"}'),a={name:"public/kronos/docs/main-mod-info.md"},n=s("",10),o=[n];function l(h,r,p,d,u,c){return t(),e("div",null,o)}const y=i(a,[["render",l]]);export{f as __pageData,y as default}; diff --git a/assets/public_kronos_docs_milestones.md.DTJttUg9.js b/assets/public_kronos_docs_milestones.md.DTJttUg9.js deleted file mode 100644 index 7ef29a32..00000000 --- a/assets/public_kronos_docs_milestones.md.DTJttUg9.js +++ /dev/null @@ -1,8 +0,0 @@ -import{_ as e,c as s,o as i,a5 as t}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Milestones","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/milestones.md","filePath":"public/kronos/docs/milestones.md"}'),a={name:"public/kronos/docs/milestones.md"},n=t(`

Milestones ​

Milestones are awarded to the player when they meet a certain goal, and give some benefit. Milestones should be formatted like this:

js
milestones: {
-    0: {
-        requirementDescription: "123 waffles",
-        effectDescription: "blah",
-        done() { return player.w.points.gte(123) }
-    }
-    etc
-}

You can use hasMilestone(layer, id) to determine if the player has a given milestone

Milestone features:

  • requirementDescription: A string describing the requirement for unlocking this milestone. Suggestion: Use a "total". It can also be a function that returns updating text. Can use basic HTML.

  • effectDescription: A string describing the reward for having the milestone. You will have to implement the reward elsewhere. It can also be a function that returns updating text. Can use basic HTML.

  • done(): A function returning a boolean to determine if the milestone should be awarded.

  • toggles: optional. Creates toggle buttons that appear on the milestone when it is unlocked. The toggles can toggle a given boolean value in a layer. It is defined as an array of paired items, one pair per toggle. The first is the internal name of the layer the value being toggled is stored in, and the second is the internal name of the variable to toggle. (e.g. [["b", "auto"], ["g", "auto"])

    Tip: Toggles are not de-set if the milestone becomes locked! In this case, you should also check if the player has the milestone.

  • style: optional. Applies CSS to this milestone, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • unlocked(): optional. A function returning a boolean to determine if the milestone should be shown. If absent, it is always shown.

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

  • id: assigned automagically. It's the "key" which the milestone was stored under, for convenient access. The milestone in the example's id is 0.

Disaable milestone popups by adding milestonePopups: false to the layer.

`,7),o=[n];function l(h,r,p,d,c,g){return i(),s("div",null,o)}const m=e(a,[["render",l]]);export{u as __pageData,m as default}; diff --git a/assets/public_kronos_docs_milestones.md.DTJttUg9.lean.js b/assets/public_kronos_docs_milestones.md.DTJttUg9.lean.js deleted file mode 100644 index 567f84c1..00000000 --- a/assets/public_kronos_docs_milestones.md.DTJttUg9.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as s,o as i,a5 as t}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Milestones","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/milestones.md","filePath":"public/kronos/docs/milestones.md"}'),a={name:"public/kronos/docs/milestones.md"},n=t("",7),o=[n];function l(h,r,p,d,c,g){return i(),s("div",null,o)}const m=e(a,[["render",l]]);export{u as __pageData,m as default}; diff --git a/assets/public_kronos_docs_particles.md.acAe5suw.js b/assets/public_kronos_docs_particles.md.acAe5suw.js deleted file mode 100644 index b4cf92a7..00000000 --- a/assets/public_kronos_docs_particles.md.acAe5suw.js +++ /dev/null @@ -1,11 +0,0 @@ -import{_ as e,c as i,o as s,a5 as a}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Particles","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/particles.md","filePath":"public/kronos/docs/particles.md"}'),t={name:"public/kronos/docs/particles.md"},l=a(`

Particles ​

Particles are free-floating elements that can move and have many different behaviors. They can also interact with the mouse.

To make particles, use makeParticles(particle, amount). particle is a particle-defining object, with features as explained below. There is also makeShinies, which uses different defaults and creates stationary particles at a random location. There are also a few other useful things listed at the end.

js

-const myParticle {
-    image:"options_wheel.png",
-    spread: 20,
-    gravity: 2,
-    time: 3,
-    speed() { // Randomize speed a bit
-        return (Math.random() + 1.2) * 8 
-    },
-    etc...
-}

Features can be functions or constant. These features will be called when each particle is made, with an id argument, which is assigned based on which of the amount particles being spawned this is. All of these are optional, with a default value.

All distances are in pixels and angles are in degrees, with 0 being up and going clockwise.

  • time: The amount of time, in seconds, that the particle will last. Default is 3.

  • fadeOutTime: The amount of seconds that fading out at the end should take (part of the total lifetime). Default is 1.

  • fadeInTime: The amount of seconds that fading in should take (part of the total lifetime). Default is 0.

  • image: The image the particle should display. "" will display no image. Default is a generic particle.

  • text: Displays text on the particle. Can use basic HTML.

  • style: Lets you apply other CSS styling to the particle.

  • width, height: The dimensions of the particle. Default is 35 and 35.

  • color: Sets the color of the image to this color.

  • angle: The angle that the particle should face. Default is 0.

  • dir: The initial angle that the particles should move in, before spread is factored in. Default is whatever angle is.

  • spread: If there are several particles, they will be spread out by this many degrees, centered on dir. Default is 30.

  • rotation: The amount that the (visual) angle of the particle should change by. Default is 0.

  • speed: The starting speed of the particle. Default is 15.

  • gravity: The amount the particle should accelerate downwards. Default is 0.

  • x, y: The starting coordinates of the particle. Default is at the mouse position.

  • offset: How far from the start each particle should appear. Default is 10.

  • xVel, yVel: Set initially based on other properties, then used to update movement.

  • layer: When changing tabs, if leaving the layer tab, this particle will be erased.

  • You can add other features to particles, but you must impliment their effects yourself.

Function features: These stay as functions and are for more advanced things. They are optional.

  • update(): Called each tick. Lets you do more advanced visual and movement behaviors by changing other properties.
  • onClick(), onMouseOver(), onMouseLeave(): Called when the particle is interacted with.

Other useful things that are not features of the particle object:

  • setDir(particle, dir), setSpeed(particle, speed): Set the speed/direction on a particle.
  • clearParticles(check): Function to delete particles. With no check, it deletes all particles. Check is a function that takes a particle, and returns true if that particle should be deleted.
  • You can use Vue.delete(particles, this.id) to make a particle delete itself.
  • mouseX and mouseY are variables that track the mouse position.
  • sin(x), cos(x), tan(x): functions that do these operations, with x in degrees. (Instead of radians).
  • asin(x), acos(x), atan(x): functions that do these operations, with the returned value in degrees. (instead of radians).
`,11),n=[l];function h(p,r,o,d,c,k){return s(),i("div",null,n)}const f=e(t,[["render",h]]);export{g as __pageData,f as default}; diff --git a/assets/public_kronos_docs_particles.md.acAe5suw.lean.js b/assets/public_kronos_docs_particles.md.acAe5suw.lean.js deleted file mode 100644 index dd825440..00000000 --- a/assets/public_kronos_docs_particles.md.acAe5suw.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as i,o as s,a5 as a}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Particles","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/particles.md","filePath":"public/kronos/docs/particles.md"}'),t={name:"public/kronos/docs/particles.md"},l=a("",11),n=[l];function h(p,r,o,d,c,k){return s(),i("div",null,n)}const f=e(t,[["render",h]]);export{g as __pageData,f as default}; diff --git a/assets/public_kronos_docs_subtabs-and-microtabs.md.CAfP6QpE.js b/assets/public_kronos_docs_subtabs-and-microtabs.md.CAfP6QpE.js deleted file mode 100644 index e1aca458..00000000 --- a/assets/public_kronos_docs_subtabs-and-microtabs.md.CAfP6QpE.js +++ /dev/null @@ -1,25 +0,0 @@ -import{_ as s,c as a,o as t,a5 as i}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Subtabs and Microtabs","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/subtabs-and-microtabs.md","filePath":"public/kronos/docs/subtabs-and-microtabs.md"}'),n={name:"public/kronos/docs/subtabs-and-microtabs.md"},e=i(`

Subtabs and Microtabs ​

Subtabs are separate sections of a tab that you can view by selecting one at the top of the tab. Microtabs are smaller areas that function in much the same way. You can also embed layers inside of subtabs/microtabs.

Subtabs are defined by using the tab format like this, where each element of tabFormat is given the name of that subtab:

js
tabFormat: {
-    "Main tab": {
-        content: [tab format things],
-        *subtab features*
-    },
-    "Other tab": {
-        content: [tab format things],
-        *subtab features*
-    },
-    etc
-}

Microtabs are defined similarly, and use the same features, but are defined in the "microtabs" feature. Each entry is a group of tabs which will appear in a microtabs component. The first set, "stuff", has 2 tabs, and the second, "otherStuff", has none.

js
microtabs: {
-    stuff: {
-        first: {
-            content: [tab format things],
-            *subtab features*
-        },
-        second: {
-            content: [tab format things],
-            *subtab features*
-        }
-    },
-    otherStuff: {
-        // There could be another set of microtabs here
-    }
-}

Normal subtabs and microtab subtabs both use the same features:

Features: ​

  • content: The tab layout code for the subtab, in the tab layout format.

  • style: optional. Applies CSS to the whole subtab when switched to, in the form of an "CSS Object", where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • buttonStyle: optional. A CSS object, which affects the appearance of the button for that subtab.

  • unlocked(): optional. a function to determine if the button for this subtab should be visible. By default, a subtab is always unlocked. You can't use the "this" keyword in this function.

  • shouldNotify()/prestigeNotify(): optional, if true, the tab button will be highlighted to notify the player that there is something there.

  • glowColor: optional, specifies the color that the subtab glows. If this subtab is causing the main layer to node glow (and it would't otherwise) the node also glows this color. Is NOT overridden by embedding a layer.

  • embedLayer: SIGNIFICANT, the id of another layer. If you have this, it will override "content", "style" and "shouldNotify", instead displaying the entire layer in the subtab.

`,9),l=[e];function h(o,p,r,k,d,b){return t(),a("div",null,l)}const E=s(n,[["render",h]]);export{u as __pageData,E as default}; diff --git a/assets/public_kronos_docs_subtabs-and-microtabs.md.CAfP6QpE.lean.js b/assets/public_kronos_docs_subtabs-and-microtabs.md.CAfP6QpE.lean.js deleted file mode 100644 index 9b834753..00000000 --- a/assets/public_kronos_docs_subtabs-and-microtabs.md.CAfP6QpE.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as a,o as t,a5 as i}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Subtabs and Microtabs","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/subtabs-and-microtabs.md","filePath":"public/kronos/docs/subtabs-and-microtabs.md"}'),n={name:"public/kronos/docs/subtabs-and-microtabs.md"},e=i("",9),l=[e];function h(o,p,r,k,d,b){return t(),a("div",null,l)}const E=s(n,[["render",h]]);export{u as __pageData,E as default}; diff --git a/assets/public_kronos_docs_trees-and-tree-customization.md.D0rBQwbs.js b/assets/public_kronos_docs_trees-and-tree-customization.md.D0rBQwbs.js deleted file mode 100644 index 49d38e1c..00000000 --- a/assets/public_kronos_docs_trees-and-tree-customization.md.D0rBQwbs.js +++ /dev/null @@ -1,3 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Trees and tree customization","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/trees-and-tree-customization.md","filePath":"public/kronos/docs/trees-and-tree-customization.md"}'),s={name:"public/kronos/docs/trees-and-tree-customization.md"},o=i(`

Trees and tree customization ​

If you want to have something beyond the standard tree on the left tab, you can do that in tree.js. You can change the layout of the tree, including making non-layer nodes, change it into something other than a tree, or hide the left tab altogether. This also introduces the "tree" component, which can be used in your layers as well.

layoutInfo ​

The most important part is layoutInfo, containing:

  • startTab: The id of the default tab to show on the left at the start.
  • showTree: True if the tree tab should be shown at the start of the game. (The other tab will fill the whole page)
  • treeLayout: If present, overrides the tree layout and places nodes as you describe instead (explained in the next section).

Additionally, if you want the main layout to not be a tree, you can edit the "tree-tab" layer at the bottom of tree.js to modify it just like a normal layer's tab. You can even switch between left tabs, using showNavTab(layer) to make that layer appear on the left.

Trees ​

The tree component is defined as an array of arrays of names of layers or nodes to show in the tree. They work just like layers/ nodes in the main tree (but branches between nodes will only work on the first node if you have duplicates.)

Here is an example tree:

js
[["p"],
- ["left", "blank", "right", "blank"]
- ["a", "b", "blank", "c", "weirdButton"]]

Nodes ​

Nodes are non-layer buttons that can go in trees. They are defined similarly to layers, but with addNode instead of addLayer.

Features:

  • color: optional, The node's color. (A string in hex format with a #)

  • symbol: optional The text on the button (The id capitalized by default)

  • canClick(): Returns true if the player can click the node. ()

  • onClick(): The function called when the node is clicked.

  • layerShown(): optional, A function returning a bool which determines if this node should be visible. It can also return "ghost", which will hide the layer, but its node will still take up space in its tree.

  • branches: optional. An array of layer/node ids. On a tree, a line will appear from this node to all of the nodes in the list. Alternatively, an entry in the array can be a 2-element array consisting of the id and a color value. The color value can either be a string with a hex color code, or a number from 1-3 (theme-affected colors).

  • nodeStyle: optional. A CSS object, where the keys are CSS attributes, which styles this node on the tree.

  • tooltip() / tooltipLocked(): optional. Functions that return text, which is the tooltip for the node when the layer is unlocked or locked, respectively. By default the tooltips behave the same as in the original Prestige Tree.

  • row: optional, the row that this node appears in (for the default tree).

  • position: optional, Determines the horizontal position of the layer in its row in a default tree. By default, it uses the id, and layers/nodes are sorted in alphabetical order.

`,14),n=[o];function l(r,h,d,p,u,c){return a(),t("div",null,n)}const g=e(s,[["render",l]]);export{y as __pageData,g as default}; diff --git a/assets/public_kronos_docs_trees-and-tree-customization.md.D0rBQwbs.lean.js b/assets/public_kronos_docs_trees-and-tree-customization.md.D0rBQwbs.lean.js deleted file mode 100644 index b44519d8..00000000 --- a/assets/public_kronos_docs_trees-and-tree-customization.md.D0rBQwbs.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as i}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Trees and tree customization","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/trees-and-tree-customization.md","filePath":"public/kronos/docs/trees-and-tree-customization.md"}'),s={name:"public/kronos/docs/trees-and-tree-customization.md"},o=i("",14),n=[o];function l(r,h,d,p,u,c){return a(),t("div",null,n)}const g=e(s,[["render",l]]);export{y as __pageData,g as default}; diff --git a/assets/public_kronos_docs_updating-tmt.md._8lPgb0z.js b/assets/public_kronos_docs_updating-tmt.md._8lPgb0z.js deleted file mode 100644 index 5e6545fc..00000000 --- a/assets/public_kronos_docs_updating-tmt.md._8lPgb0z.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as t,c as e,o,a5 as a}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Updating The Modding Tree","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/updating-tmt.md","filePath":"public/kronos/docs/updating-tmt.md"}'),i={name:"public/kronos/docs/updating-tmt.md"},n=a('

Updating The Modding Tree ​

This tutorial assumes that you have used the Getting Started Tutorial, and are using Github Desktop and VSCode for your mod.

Here's what you have to do when there's a TMT update:

  1. Look at the changelog. It will warn you if the update will break anything or require any changes. Decide if you want to try to update.

  2. Open Github Desktop, and at the top middle, click "fetch origin". This will make Github Desktop get information about the update.

  3. Click where it says "current branch: master" at the top middle, and at the bottom of the thing that appears, click "choose a branch to merge into master".

  4. Select upstream/master. It will likely say there are conflicts, but you have tools to resolve them. Click "Merge upstream/master into master".

  5. A conflict happens when the things you're trying to merge have both made changes in the same place. Click "open in Visual Studio Code" next to the first file.

  6. Scroll down through the file, and look for the parts highlighted in red and green. One of these is your code, and the other is some code that will be modified by the update. Do your best to try to edit things to keep the updated changes, but keep your content.

  7. Continue to do this for all remaining changes.

  8. Do any other changes required by the update, run the game, fix issues, etc.

',4),r=[n];function h(s,d,l,p,u,c){return o(),e("div",null,r)}const _=t(i,[["render",h]]);export{m as __pageData,_ as default}; diff --git a/assets/public_kronos_docs_updating-tmt.md._8lPgb0z.lean.js b/assets/public_kronos_docs_updating-tmt.md._8lPgb0z.lean.js deleted file mode 100644 index 5a095e3e..00000000 --- a/assets/public_kronos_docs_updating-tmt.md._8lPgb0z.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as t,c as e,o,a5 as a}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Updating The Modding Tree","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/updating-tmt.md","filePath":"public/kronos/docs/updating-tmt.md"}'),i={name:"public/kronos/docs/updating-tmt.md"},n=a("",4),r=[n];function h(s,d,l,p,u,c){return o(),e("div",null,r)}const _=t(i,[["render",h]]);export{m as __pageData,_ as default}; diff --git a/assets/public_kronos_docs_upgrades.md.CTKgTXEi.js b/assets/public_kronos_docs_upgrades.md.CTKgTXEi.js deleted file mode 100644 index 2c585a0f..00000000 --- a/assets/public_kronos_docs_upgrades.md.CTKgTXEi.js +++ /dev/null @@ -1,8 +0,0 @@ -import{_ as e,c as t,o as s,a5 as a}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Upgrades","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/upgrades.md","filePath":"public/kronos/docs/upgrades.md"}'),i={name:"public/kronos/docs/upgrades.md"},n=a(`

Upgrades ​

Useful functions for dealing with Upgrades and implementing their effects:

  • hasUpgrade(layer, id): determine if the player has the upgrade
  • upgradeEffect(layer, id): Returns the current effects of the upgrade, if any
  • buyUpgrade(layer, id): Buys an upgrade directly (if affordable)

Hint: Basic point gain is calculated in mod.js's "getPointGen" function.

Upgrades are stored in the following format:

js
upgrades: {
-    11: {
-        description: "Blah",
-        cost: new Decimal(100),
-        etc
-    },
-    etc
-}

Usually, upgrades should have an id where the first digit is the row and the second digit is the column.

Individual upgrades can have these features:

  • title: optional. Displayed at the top in a larger font. It can also be a function that returns updating text. Can use basic HTML.

  • description: A description of the upgrade's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

  • effect(): optional. A function that calculates and returns the current values of any bonuses from the upgrade. Can return a value or an object containing multiple values.

  • effectDisplay(): optional. A function that returns a display of the current effects of the upgrade with formatting. Default displays nothing. Can use basic HTML.

  • fullDisplay(): OVERRIDE. Overrides the other displays and descriptions, and lets you set the full text for the upgrade. Can use basic HTML.

  • cost: A Decimal for the cost of the upgrade. By default, upgrades cost the main prestige currency for the layer.

  • unlocked(): optional. A function returning a bool to determine if the upgrade is visible or not. Default is unlocked.

  • onPurchase(): optional. This function will be called when the upgrade is purchased. Good for upgrades like "makes this layer act like it was unlocked first".

  • style: optional. Applies CSS to this upgrade, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

  • id: assigned automagically. It's the "key" which the upgrade was stored under, for convenient access. The upgrade in the example's id is 11.

By default, upgrades use the main prestige currency for the layer. You can include these to change them (but it needs to be a Decimal):

  • currencyDisplayName: optional. The name to display for the currency for the upgrade.

  • currencyInternalName: optional. The internal name for that currency.

  • currencyLayer: optional. The internal name of the layer that currency is stored in. If it's not in a layer (like Points), omit. If it's not stored directly in a layer, instead use the next feature.

  • currencyLocation: optional. If your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

If you want to do something more complicated like upgrades that cost two currencies, you can override the purchase system with these (and you need to use fullDisplay as well)

  • canAfford(): OVERRIDE, a function determining if you are able to buy the upgrade

  • pay(): OVERRIDE, a function that reduces your currencies when you buy the upgrade

`,13),r=[n];function l(o,p,h,u,c,d){return s(),t("div",null,r)}const y=e(i,[["render",l]]);export{f as __pageData,y as default}; diff --git a/assets/public_kronos_docs_upgrades.md.CTKgTXEi.lean.js b/assets/public_kronos_docs_upgrades.md.CTKgTXEi.lean.js deleted file mode 100644 index f1897ded..00000000 --- a/assets/public_kronos_docs_upgrades.md.CTKgTXEi.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as s,a5 as a}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Upgrades","description":"","frontmatter":{},"headers":[],"relativePath":"public/kronos/docs/upgrades.md","filePath":"public/kronos/docs/upgrades.md"}'),i={name:"public/kronos/docs/upgrades.md"},n=a("",13),r=[n];function l(o,p,h,u,c,d){return s(),t("div",null,r)}const y=e(i,[["render",l]]);export{f as __pageData,y as default}; diff --git a/assets/public_lit_Old Things_2.0-format-changes.md.BUbI7CBx.js b/assets/public_lit_Old Things_2.0-format-changes.md.BUbI7CBx.js deleted file mode 100644 index aa95f544..00000000 --- a/assets/public_lit_Old Things_2.0-format-changes.md.BUbI7CBx.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as i}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"2.0 format changes","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/Old Things/2.0-format-changes.md","filePath":"public/lit/Old Things/2.0-format-changes.md"}'),l={name:"public/lit/Old Things/2.0-format-changes.md"},n=i('

2.0 format changes ​

  • Temp format is changed from temp.something[layer] to temp[layer].something, for consistency
  • Challenges are now saved as an object with the amount of completions in each spot. (This will break saves.)
  • effectDisplay in Challenges and Upgrades no longer takes an argument, and neither does effect for Buyables
  • Buyable cost can take an argument for amount of buyables, but it needs to function if no argument is supplied (it should do the cost for the next purchase).
  • Generation of Points now happens in the main game loop (not in a layer update function), enabled by canGenPoints in game.js.
  • Changed fullLayerReset to layerDataReset, which takes an array of names of values to keep

In addition, many names were changed, mostly expanding abbreviations:

All instances of:

  • chall -> challenge
  • unl -> unlocked
  • upg -> upgrade (besides CSS)
  • amt -> amount
  • desc -> description
  • resCeil -> roundUpCost
  • order -> unlockOrder
  • incr_order -> increaseUnlockOrder

Challenges:

  • desc -> challengeDescription
  • reward -> rewardDescription
  • effect -> rewardEffect
  • effectDisplay -> rewardDisplay
  • active -> challengeActive
',7),o=[n];function s(c,r,d,h,g,f){return t(),a("div",null,o)}const u=e(l,[["render",s]]);export{m as __pageData,u as default}; diff --git a/assets/public_lit_Old Things_2.0-format-changes.md.BUbI7CBx.lean.js b/assets/public_lit_Old Things_2.0-format-changes.md.BUbI7CBx.lean.js deleted file mode 100644 index cc2a9f42..00000000 --- a/assets/public_lit_Old Things_2.0-format-changes.md.BUbI7CBx.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as i}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"2.0 format changes","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/Old Things/2.0-format-changes.md","filePath":"public/lit/Old Things/2.0-format-changes.md"}'),l={name:"public/lit/Old Things/2.0-format-changes.md"},n=i("",7),o=[n];function s(c,r,d,h,g,f){return t(),a("div",null,o)}const u=e(l,[["render",s]]);export{m as __pageData,u as default}; diff --git a/assets/public_lit_README.md.C6r_DD7H.js b/assets/public_lit_README.md.C6r_DD7H.js deleted file mode 100644 index 40d2ef9f..00000000 --- a/assets/public_lit_README.md.C6r_DD7H.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o,a5 as a}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Kronos","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/README.md","filePath":"public/lit/README.md"}'),r={name:"public/lit/README.md"},i=a('

Kronos ​

Play here.

Updating the website:

  • git submodule update --remote
  • git add -A
  • git commit -m "Updated kronos"
  • git push
',4),l=[i];function s(c,d,n,_,p,u){return o(),t("div",null,l)}const f=e(r,[["render",s]]);export{m as __pageData,f as default}; diff --git a/assets/public_lit_README.md.C6r_DD7H.lean.js b/assets/public_lit_README.md.C6r_DD7H.lean.js deleted file mode 100644 index f4f2de94..00000000 --- a/assets/public_lit_README.md.C6r_DD7H.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o,a5 as a}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Kronos","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/README.md","filePath":"public/lit/README.md"}'),r={name:"public/lit/README.md"},i=a("",4),l=[i];function s(c,d,n,_,p,u){return o(),t("div",null,l)}const f=e(r,[["render",s]]);export{m as __pageData,f as default}; diff --git a/assets/public_lit_changelog.md.CG6hOolt.js b/assets/public_lit_changelog.md.CG6hOolt.js deleted file mode 100644 index 5e2afb71..00000000 --- a/assets/public_lit_changelog.md.CG6hOolt.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as i,o as a,a5 as l}from"./chunks/framework.CK8QU5WH.js";const b=JSON.parse('{"title":"The Modding Tree changelog:","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/changelog.md","filePath":"public/lit/changelog.md"}'),t={name:"public/lit/changelog.md"},o=l('

The Modding Tree changelog: ​

v2.π: Incrementally Updated - 2/5/21 ​

  • Performance improvements.
  • Fixed tooltips overlapping with the top display.
  • Clicking a popup dismisses it immediately.
  • Added support for bulk challenge completions.
  • "Best" is updated automatically.
  • Fixed keeping Decimal values on reset.
  • Code reorganization and style improvements by fudo.

v2.3.5 - 12/21/20 ​

  • Added resetTime, which tracks the time since a layer prestiged or was reset.
  • A layer node will be highlighted red if one of its subtabs is highlighted red.
  • Fixed issues with keeping challenges, buyables, and clickables on reset.
  • Improved the unlocking of custom layers.
  • Other minor fixes.

v2.3.4 - 12/16/20 ​

  • Added a node image feature.
  • Resource display now always shows the amount of the currency the layer's gain is based on.
  • Added spacing between tree nodes.
  • Another attempt to fix tooltip flickering.

v2.3.3 - 12/13/20 ​

  • Fixed the first node in a row always taking up space.
  • layerShown is now optional.
  • All prestige types can now use features for custom prestige types.

v2.3.2 - 12/13/20 ​

  • Fixed achievement/milestone popups.

v2.3.1 - 12/12/20 ​

  • Another attempt to fix flickering tooltips.
  • The "this" keyword should work everywhere except tabFormat arrays (although I may have missed some things).
  • Fixed tree branches not updating when scrolling on the right-side tab.
  • Fixed a spacing issue when a node's symbol is ""
  • Removed some old, unneeded files.

v2.3: Cooler and Newer Edition - 12/10/20 ​

  • Added achievement/milestone popups (thank you to Jacorb for this contribution!)
  • The changelog tab is back, and can be set in mod.js.
  • Layer nodes and respec buttons will not be clicked by pressing "enter".
  • Possible fix for flickering tooltips and strange transitions.
  • The victory screen text is configurable.
  • Added image and textStyle features to achievements.
  • Added an argument to use specific rows in an "upgrades" component.
  • Fixed the comma appearing in the main display when there was no effectDescription
  • Added the ability to easily make a tab that is a collection of layers in subtabs.
  • Improved spacing for embedding layers with subtabs into subtabs.

v2.2.8 - 12/03/20 ​

  • Double-clicking a layer node brings you to the main subtab for that layer.
  • Attempted to fix challenges visually updating a different way.
  • Added a softcap function for use in formulas.
  • Added displayRow feature, which lets layers be shown somewhere separate from where they are in the reset order (e.g. side layers)
  • Fixed autoupgrade issue.

v2.2.7 - 11/30/20 ​

  • Added autoUpgrade feature.
  • resource-display now shows resource gain per second if passiveGain is active.
  • Fixed formatting issues on some large numbers.
  • Better support for using classed objects in player and in layers/tmp.
  • Made hard resetting more effective.
  • Removed Herobrine from getStartClickables.

v2.2.6 - 11/30/20 ​

  • Added goalDescription for challenges and made the new "canComplete" system the standard.
  • Another attempt to fix challenges not visually updating.
  • Fixed side layers not appearing.
  • Fixed getStartClickables again.

v2.2.5 - 11/29/20 ​

  • Added features for overriding the displays and costs/goals of upgrades and challenges to make them fully custom.
  • best, total, and unlocked are always automatically added to layerData (but best and total will only display if you add them yourself).
  • Fixed getStartClickables.

v2.2.4 - 11/28/20 ​

  • Added softcap and softcapPower features (for Normal layers)
  • Offline time limit and default max tick length were fixed (previously the limits were 1000x too large)
  • Added fixOldSaves.
  • You can use HTML in main-display.
  • Fixed a number of minor oddities.

v2.2.3 - 11/28/20 ​

  • Layers will be highlighted if you can finish a challenge.
  • The "can complete challenge" color now overrides the "already completed" color.
  • Button nodes now work as side "layers".
  • Setting a tooltip to "" hides it entirely.

v2.2.2 - 11/22/20 ​

  • Fixed right half of the screen being unclickable in some circumstances.
  • Fixed tree branches being offset.
  • Fix to lastSafeTab.

v2.2.1 - 11/7/20 ​

  • Added a small highlight to layers you can meaningfully prestige on.
  • Added passiveGeneration and autoPrestige features to standardize prestige automation. (The old ways still work, but the new ones work better with other things)
  • Improved milestones visually a bit.
  • "best" and "total" are now only displayed if present in startData.
  • Fixed issues with things not updating visually. (Thank you to to Jacorb!)
  • Side layers and button nodes can now be highlighted.
  • Updated docs on the new tree-related features.

v2.2: Uprooted - 11/7/20 ​

  • You can now embed a layer inside of a subtab or microtab!
  • Added support for hiding or reformatting the tree tab
  • Added non-layer button nodes
  • Added shouldNotify to subtab/microtab buttons. (You can make them highlighted)
  • Added commas to large exponents.
  • Upgrades now only show "currently" if they have an effectDisplay (so not for constant effects).
  • Achievements are part of the default tab format.
  • NaN is now handled more intelligently.
  • Renamed files, and moved less relevant ones to another folder.
  • The "hide completed challenges" setting now only hides challenges at max completions.
  • Thank you to thepaperpilot for fixing errors in docs and improving the infobox appearance!
  • Many other minor fixes.

v2.1.4 - 10/25/20 ​

  • Added an infobox component. Thank you to thepaperpilot for this contribution!
  • Layer type is now optional, and defaults to "none".
  • Improved the look of bars and tab buttons.
  • Improved spacing between layer nodes (also thanks to thepaperpilot!)
  • Fixed the "blank" component breaking if only specifying the height.
  • Fixed some numbers not displaying with enough digits.
  • Made a few more things able to be functions.
  • A few other minor fixes.

v2.1.3.1 - 10/21/20 ​

  • Fixed the update function.

v2.1.3 - 10/21/20 ​

  • gainMult and gainExp are now optional.
  • Layer unlocking is now kept on reset.
  • Game should start up faster.
  • Layer updates now have a determined order and starts with earlier-rowed layers.
  • Automation now has a determined order and starts with later-rowed layers.
  • Fixed issues with resetting clickables and challenges.
  • Commas should no longer appear in the decimal places of a number.
  • Fixed potential issue in displaying the tree.

v2.1.2 - 10/19/20 ​

  • Added buyUpgrade function (buyUpg still works though)
  • Added author name to modInfo.
  • Fix to crash caused when the name of a subtab or microtab is changed.
  • Fixes to outdated information in docs.
  • Improvements to Discord links.
  • Thank you to thepaperpilot for contributing to this update!

v2.1.1 - 10/17/20 ​

  • Added resource-display component, which displays the base currency for the prestige layer, as well as the best and/or total of this layer's prestige currency.
  • Fixed the value for the base currency not updating in resource-display.

v2.1: We should have thought of this sooner! - 10/17/20 ​

  • Moved most of the code users will want to edit to mod.js, added documentation for it.
    • Specifically, modInfo, VERSION, canGenPoints, getPointGen, and maxTickLength
  • Added getStartPoints()
  • Added the ability to store non-layer-related data
  • Added the ability to display more things at the top of the tree tab below points.
  • Made the endgame condition customizable
  • Added "sell one" and "sell all" buttons for buyables.
  • Moved the old "game" to demo.js, and replaced it with a minimal game that won't cause issues when edited.
  • Fixed issues with version number
  • Fixed number formatting issue making things like "10e9" appear.

v2.0.5 - 10/16/20 ​

  • Made more features (including prestige parameters) able to be dynamic.
  • Layer nodes can be hidden but still take up space with "ghost" visibility
  • Added clickableEffect for real.
  • Fixed some visual issues with bars.
  • A few other minor tweaks and improvements.

v2.0.4 - 10/16/20 ​

  • Fixed HTML on buttons interfering with clicking on them.

v2.0.3 - 10/16/20 ​

  • Fixed hotkeys not displaying in info.
  • Fixed the game supressing all external hotkeys.
  • You can use more things as currencies for upgrade costs and challenge goals using currencyLocation.
  • Added maxTickLength, which can be used to prevent offline time or tab-switching from breaking time-limit based mechanics.
  • Made buyable respec buttons and clickable "master" buttons their own components, and gave them a hide/show feature.
  • Added a general "tooltip" feature for achievements.

v2.0.2 - 10/15/20 ​

  • Branches are now dynamic (they can be functions).
  • Fixed a crash related to offline time.
  • Fixed links being too wide.

v2.0.1 - 10/15/20 ​

  • Fixed side layers appearing multiple times.

v2.0: The Pinnacle of Achievement Mountain - 10/15/20 ​

  • Added progress bars, which are highly customizable and can be horizontal or vertical!
  • Added "side layers", displayed smaller and off to the side, and don't get reset by default. They can be used for global achievements and statistics. Speaking of which...
  • Added achievements!
  • Added clickables, a more generalized variant of buyables.
  • Almost every value in layer data can be either a function or a constant value!
  • Added support for multiple completions of challenges.
  • Added "none" prestige type, which removes the need for any other prestige-related features.
  • The points display and other gui elements stay at the top of the screen when the tree scrolls.
  • Added getter/setter functions for the amounts and effects of most Big Features
  • Moved modInfo to game.js, added a spot in modInfo for a Discord link, changelog link. Also added a separate mod version from the TMT version in VERSION.
  • Tree structure is based on layer data, no index.html editing is needed.
  • Tmp does not need to be manually updated.
  • You don't have to have the same amount of upgrades in every row (and challs and buyables)
  • "unlocked" is optional for all Big Components (defaults to true).
  • All displays will update correctly.
  • Changelog is no longer in index.html at all.
  • Generation of Points now happens in the main game loop
  • Changed the reset functions to make keeping things easier
  • Renamed many things to increase readability (see the list in the link below)
  • Improved documentation based on feedback

v1.3.5: ​

  • Completely automated convertToDecimal, now you never have to worry about it again.
  • Branches can be defined without a color id. But they can also use hex values for color ids!
  • Created a tutorial for getting started with TMT and Github.
  • Page title is now automatically taken from mod name.

v1.3.4 - 10/8/20 ​

  • Added "midsection" feature to add things to a tab's layout while still keeping the standard layout.
  • Fix for being able to buy more buyables than you should.

v1.3.3 - 10/7/20 ​

  • Fix for the "order of operations" issue in temp.

v1.3.1 - 10/7/20 ​

  • Added custom CSS and tooltips for Layer Nodes.
  • Added custom CSS for upgrades, buyables, milestones, and challenges, both individually and layer-wide.
  • You can now use HTML in most display text!
  • You can now make milestones unlockable and not display immediately.
  • Fixed importing saves, and issue with upgrades not appearing, and probably more.
  • Optional "name" layer feature, used in confirmation messages.

v1.3: Tabception... ception! - 10/7/20 ​

  • Added subtabs! And also a Micro-tab component to let you make smaller subtab-esque areas anywhere.
  • Added a "custom" prestige formula type, and a number of features to support it.
  • Added points/sec display (can be disabled).
  • Added h-line, v-line and image-display components, plus components for individual upgrades, challenges, and milestones.
  • Added upgEffect, buyableEffect, and challEffect functions.
  • Added "hide completed challenges" setting.
  • Moved old changelogs to a separate place.
  • Fixed hasMilestone and incr_order.
  • Static layers now show the currency amount needed for the next one if you can buy max.

v1.2.4 - 10/4/20 ​

  • Layers are now highlighted if you can buy an upgrade, and a new feature, shouldNotify, lets you make it highlight other ways.
  • Fixed bugs with hasUpg, hasChall, hasMilestone, and inChallenge.
  • Changed the sample code to use the above functions for convenience.

v1.2.3 - 10/3/20 ​

  • Added a row component, which displays a list of objects in a row.
  • Added a column component, which displays a list of objects in a column (useful within a row).
  • Changed blanks to have a customizable width and height.

v1.2: This Changes Everything! - 10/3/20 ​

  • Many layer features can now be static values or functions. (This made some formats change, which will break old things)
  • You can now use the "this" keyword, to make code easier to transfer when making new layers.
  • Also added "this.layer", which is the current layer's name, and works on existing subfeatures (e.g. individual upgrades) as well! Subfeatures also have "this.id".
  • Fixed a big save issue. If you use a unique mod id, your save will never conflict with other mods.
  • Added a configurable offline time limit in modinfo at the top of index.html. (default 1 hour)
  • Added a few minor features, and updated the docs with new information.

v1.1.1: ​

  • You can define hotkeys directly from layer config.

v1.1: Enhanced Edition ​

  • Added "Buyables", which can function like Space Buildings or Enhancers.
  • Custom CSS can now be used on any component! Make the third argument an object with CSS parameters.
  • Lots of minor good things.

v1.0: ​

  • First release.
',79),n=[o];function s(r,d,h,u,c,m){return a(),i("div",null,n)}const p=e(t,[["render",s]]);export{b as __pageData,p as default}; diff --git a/assets/public_lit_changelog.md.CG6hOolt.lean.js b/assets/public_lit_changelog.md.CG6hOolt.lean.js deleted file mode 100644 index a2675a00..00000000 --- a/assets/public_lit_changelog.md.CG6hOolt.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as i,o as a,a5 as l}from"./chunks/framework.CK8QU5WH.js";const b=JSON.parse('{"title":"The Modding Tree changelog:","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/changelog.md","filePath":"public/lit/changelog.md"}'),t={name:"public/lit/changelog.md"},o=l("",79),n=[o];function s(r,d,h,u,c,m){return a(),i("div",null,n)}const p=e(t,[["render",s]]);export{b as __pageData,p as default}; diff --git a/assets/public_lit_docs_!general-info.md.D6KB8CTG.js b/assets/public_lit_docs_!general-info.md.D6KB8CTG.js deleted file mode 100644 index 571e1e9e..00000000 --- a/assets/public_lit_docs_!general-info.md.D6KB8CTG.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as o}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"The-Modding-Tree","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/!general-info.md","filePath":"public/lit/docs/!general-info.md"}'),n={name:"public/lit/docs/!general-info.md"},r=o('

The-Modding-Tree ​

The main way to add content is through creating layers. You can either add a layer directly in the layers object in layerSupport.js, or declare it in another file and register it by calling addLayer(layername, layerdata). There is an example layer registration in layers.js showing the recommended method. It is just an example and can be freely deleted. You can also use it as a reference or a base for your own layers.

The first thing you need to do is fill out the modInfo object at the top of mod.js to set your mod's name, ID (a string), and other information. A unique modId will prevent your mod's saves from conflicting with other mods. Note that changing this after people have started playing will reset their saves.

Most of the time, you won't need to dive deep into the code to create things, but you still can if you really want to, for example to add new Vue components in v.js.

The Modding Tree uses break_eternity.js to store large values. This means that many numbers are Decimal objects, and must be treated differently. For example, you have to use new Decimal(x) to create a Decimal value instead of a plain number, and perform operations on them by calling functions. e.g, instead of x = x + y, use x = x.add(y). Keep in mind this also applies to comparison operators, which should be replaced with calling the .gt, .gte, .lt, .lte, .eq, and .neq functions. See the break_eternity.js docs for more details on working with Decimal values.

Almost all values can be either a constant value, or a dynamic value. Dynamic values are defined by putting a function that returns what the value should be at any given time.

All display text can use basic HTML elements (But you can't use most Vue features there).

While reading this documentation, the following key will be used when describing features:

  • No label: This is required and the game may crash if it isn't included.
  • sometimes required: This is may be required, depending on other things in the layer.
  • optional: You can leave this out if you don't intend to use that feature for the layer.
  • assigned automagically: This value will be set automatically and override any value you set.
  • deprecated: This feature is not recommended to be used anymore, and may be removed in future versions of TMT.

Table of Contents ​

General ​

  • Getting Started: Getting your own copy of the code set up with Github Desktop.
  • Main mod info: How to set up general things for your mod in mod.js.
  • Basic layer breakdown: Breaking down the components of a layer with minimal features.
  • Layer features: Explanations of all of the different properties that you can give a layer.
  • Custom Tab Layouts: An optional way to give your tabs a different layout. You can even create entirely new components to use.
  • Custom game layouts: You can get rid of the tree tab, add buttons and other things to the tree, or even customize the tab's layout like a layer tab.
  • Updating TMT: Using Github Desktop to update your mod's version of TMT.

Common components ​

  • Upgrades: How to create upgrades for a layer.
  • Milestones: How to create milestones for a layer.
  • Buyables: Create rebuyable upgrades for your layer (with the option to make them respec-able). Can be used to make Enhancers or Space Buildings.
  • Clickables: A more generalized variant of buyables, for any kind of thing that is sometimes clickable. Between these and Buyables, you can do just about anything.

Other components and features ​

  • Challenges: How to create challenges for a layer.
  • Bars: Display some information as a progress bar, gauge, or similar. They are highly customizable, and can be horizontal and vertical as well.
  • Subtabs and Microtabs: Create subtabs for your tabs, as well as "microtab" components that you can put inside the tabs. You can even use them to embed a layer inside another layer!
  • Achievements: How to create achievements for a layer (or for the whole game).
  • Infoboxes: Boxes containing text that can be shown or hidden.
  • Trees: Make your own trees. You can make non-layer button nodes too!
',16),i=[r];function s(l,d,h,c,u,m){return t(),a("div",null,i)}const b=e(n,[["render",s]]);export{y as __pageData,b as default}; diff --git a/assets/public_lit_docs_!general-info.md.D6KB8CTG.lean.js b/assets/public_lit_docs_!general-info.md.D6KB8CTG.lean.js deleted file mode 100644 index d28c0afd..00000000 --- a/assets/public_lit_docs_!general-info.md.D6KB8CTG.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as a,o as t,a5 as o}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"The-Modding-Tree","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/!general-info.md","filePath":"public/lit/docs/!general-info.md"}'),n={name:"public/lit/docs/!general-info.md"},r=o("",16),i=[r];function s(l,d,h,c,u,m){return t(),a("div",null,i)}const b=e(n,[["render",s]]);export{y as __pageData,b as default}; diff --git a/assets/public_lit_docs_achievements.md.DGaaIXhv.js b/assets/public_lit_docs_achievements.md.DGaaIXhv.js deleted file mode 100644 index 6f39e72d..00000000 --- a/assets/public_lit_docs_achievements.md.DGaaIXhv.js +++ /dev/null @@ -1,9 +0,0 @@ -import{_ as e,c as t,o as i,a5 as a}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Achievements","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/achievements.md","filePath":"public/lit/docs/achievements.md"}'),s={name:"public/lit/docs/achievements.md"},n=a(`

Achievements ​

Achievements are awarded to the player when they meet a certain goal, and optionally give some benefit. Currently they are pretty basic, but additional features will be added later to help.

You can make global achievements by putting them in a side layer by making its row equal to "side" instead of a number.

Useful functions for dealing with achievements and implementing their effects:

  • hasAchievement(layer, id): determine if the player has the Achievement.
  • achievementEffect(layer, id): Returns the current effects of the achievement, if any.

Achievements should be formatted like this:

js
achievements: {
-    rows: # of rows,
-    cols: # of columns,
-    11: {
-        name: "Blah",
-        more features
-    },
-    etc
-}

Each achievement should have an id where the first digit is the row and the second digit is the column.

Individual achievement can have these features:

  • name: optional. displayed at the top of the achievement. The only visible text. It can also be a function that returns updating text. Can use basic HTML.

  • done(): A function returning a boolean to determine if the achievement should be awarded.

  • tooltip: Default tooltip for the achievement, appears when it is hovered over. Should convey the goal and any reward for completing the achievement. It can also be a function that returns updating text. Can use basic HTML. Setting this to "" disables the tooltip.

  • effect(): optional. A function that calculates and returns the current values of any bonuses from the achievement. Can return a value or an object containing multiple values.

  • unlocked(): optional. A function returning a bool to determine if the achievement is visible or not. Default is unlocked.

  • onComplete() - optional. this function will be called when the achievement is completed.

  • image: optional, puts the image from the given URL (relative or absolute) in the achievement

  • style: optional. Applies CSS to this achievement, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • textStyle: optional. Applies CSS to the text, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

  • id: assigned automagically. It's the "key" which the achievement was stored under, for convenient access. The achievement in the example's id is 11.

  • goalTooltip: optional, deprecated. Appears when the achievement is hovered over and locked, overrides the basic tooltip. This is to display the goal (or a hint). It can also be a function that returns updating text. Can use basic HTML.

  • doneTooltip: optional, deprecated. Appears when the achievement is hovered over and completed, overrides the basic tooltip. This can display what the player achieved (the goal), and the rewards, if any. It can also be a function that returns updating text. Can use basic HTML.

Disable achievement popups by adding achievementsPopups: false to the layer.

`,11),l=[n];function o(h,p,r,c,d,u){return i(),t("div",null,l)}const k=e(s,[["render",o]]);export{g as __pageData,k as default}; diff --git a/assets/public_lit_docs_achievements.md.DGaaIXhv.lean.js b/assets/public_lit_docs_achievements.md.DGaaIXhv.lean.js deleted file mode 100644 index 406ef140..00000000 --- a/assets/public_lit_docs_achievements.md.DGaaIXhv.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as i,a5 as a}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Achievements","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/achievements.md","filePath":"public/lit/docs/achievements.md"}'),s={name:"public/lit/docs/achievements.md"},n=a("",11),l=[n];function o(h,p,r,c,d,u){return i(),t("div",null,l)}const k=e(s,[["render",o]]);export{g as __pageData,k as default}; diff --git a/assets/public_lit_docs_bars.md.B1h0O1rn.js b/assets/public_lit_docs_bars.md.B1h0O1rn.js deleted file mode 100644 index 7205b12a..00000000 --- a/assets/public_lit_docs_bars.md.B1h0O1rn.js +++ /dev/null @@ -1,10 +0,0 @@ -import{_ as s,c as i,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Bars","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/bars.md","filePath":"public/lit/docs/bars.md"}'),e={name:"public/lit/docs/bars.md"},n=t(`

Bars ​

Bars let you display information in a more direct way. It can be a progress bar, health bar, capacity gauge, or anything else.

Bars are defined like other Big Features:

js
bars: {
-    bigBar: {
-        direction: RIGHT,
-        width: 200,
-        height: 50,
-        progress() { return 0 },
-        etc
-    },
-    etc
-}

Features:

  • direction: UP, DOWN, LEFT, or RIGHT (not strings). Determines the direction that the bar is filled as it progresses. RIGHT means from left to right.

  • width, height: The size in pixels of the bar, but as numbers (no "px" at the end).

  • progress(): A function that returns the portion of the bar that is filled, from "empty" at 0 to "full" at 1, updating automatically. (Nothing bad happens if the value goes out of these bounds, and it can be a number or Decimal)

  • display(): optional. A function that returns text to be displayed on top of the bar, can use HTML.

  • unlocked(): optional. A function returning a bool to determine if the bar is visible or not. Default is unlocked.

  • baseStyle, fillStyle, borderStyle, textStyle: Optional, Apply CSS to the unfilled portion, filled portion, border, and display text on the bar, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

  • id: assigned automagically. It's the "key" which the bar was stored under, for convenient access. The bar in the example's id is "bigBar".

`,6),l=[n];function r(p,h,o,d,k,c){return a(),i("div",null,l)}const E=s(e,[["render",r]]);export{u as __pageData,E as default}; diff --git a/assets/public_lit_docs_bars.md.B1h0O1rn.lean.js b/assets/public_lit_docs_bars.md.B1h0O1rn.lean.js deleted file mode 100644 index e4567a4a..00000000 --- a/assets/public_lit_docs_bars.md.B1h0O1rn.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as i,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Bars","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/bars.md","filePath":"public/lit/docs/bars.md"}'),e={name:"public/lit/docs/bars.md"},n=t("",6),l=[n];function r(p,h,o,d,k,c){return a(),i("div",null,l)}const E=s(e,[["render",r]]);export{u as __pageData,E as default}; diff --git a/assets/public_lit_docs_basic-layer-breakdown.md.Qv71gcDd.js b/assets/public_lit_docs_basic-layer-breakdown.md.Qv71gcDd.js deleted file mode 100644 index 54e361ad..00000000 --- a/assets/public_lit_docs_basic-layer-breakdown.md.Qv71gcDd.js +++ /dev/null @@ -1,28 +0,0 @@ -import{_ as s,c as i,o as a,a5 as n}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Basic layer breakdown","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/basic-layer-breakdown.md","filePath":"public/lit/docs/basic-layer-breakdown.md"}'),t={name:"public/lit/docs/basic-layer-breakdown.md"},e=n(`

Basic layer breakdown ​

This is a very minimal layer with minimal features. Most things will require additional features.

js
addLayer("p", {
-    startData() { return {                  // startData is a function that returns default data for a layer. 
-        unlocked: true,                     // You can add more variables here to add them to your layer.
-        points: new Decimal(0),             // "points" is the internal name for the main resource of the layer.
-    }},
-
-    color: "#4BDC13",                       // The color for this layer, which affects many elements.
-    resource: "prestige points",            // The name of this layer's main prestige resource.
-    row: 0,                                 // The row this layer is on (0 is the first row).
-
-    baseResource: "points",                 // The name of the resource your prestige gain is based on.
-    baseAmount() { return player.points },  // A function to return the current amount of baseResource.
-
-    requires: new Decimal(10),              // The amount of the base needed to  gain 1 of the prestige currency.
-                                            // Also the amount required to unlock the layer.
-
-    type: "normal",                         // Determines the formula used for calculating prestige currency.
-    exponent: 0.5,                          // "normal" prestige gain is (currency^exponent).
-
-    gainMult() {                            // Returns your multiplier to your gain of the prestige resource.
-        return new Decimal(1)               // Factor in any bonuses multiplying gain here.
-    },
-    gainExp() {                             // Returns your exponent to your gain of the prestige resource.
-        return new Decimal(1)
-    },
-
-    layerShown() { return true }            // Returns a bool for if this layer's node should be visible in the tree.
-})
`,3),h=[e];function l(k,p,r,E,d,o){return a(),i("div",null,h)}const c=s(t,[["render",l]]);export{g as __pageData,c as default}; diff --git a/assets/public_lit_docs_basic-layer-breakdown.md.Qv71gcDd.lean.js b/assets/public_lit_docs_basic-layer-breakdown.md.Qv71gcDd.lean.js deleted file mode 100644 index f5ca4150..00000000 --- a/assets/public_lit_docs_basic-layer-breakdown.md.Qv71gcDd.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as i,o as a,a5 as n}from"./chunks/framework.CK8QU5WH.js";const g=JSON.parse('{"title":"Basic layer breakdown","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/basic-layer-breakdown.md","filePath":"public/lit/docs/basic-layer-breakdown.md"}'),t={name:"public/lit/docs/basic-layer-breakdown.md"},e=n("",3),h=[e];function l(k,p,r,E,d,o){return a(),i("div",null,h)}const c=s(t,[["render",l]]);export{g as __pageData,c as default}; diff --git a/assets/public_lit_docs_buyables.md.-Ov6NyGO.js b/assets/public_lit_docs_buyables.md.-Ov6NyGO.js deleted file mode 100644 index ffe808ac..00000000 --- a/assets/public_lit_docs_buyables.md.-Ov6NyGO.js +++ /dev/null @@ -1,15 +0,0 @@ -import{_ as s,c as i,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Buyables","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/buyables.md","filePath":"public/lit/docs/buyables.md"}'),e={name:"public/lit/docs/buyables.md"},l=t(`

Buyables ​

Buyables are usually things that can be bought multiple times with scaling costs. If you set a respec function, the player can reset the purchases to get their currency back.

The amount of a buyable owned is a Decimal.

Useful functions for dealing with buyables and implementing their effects:

  • getBuyableAmount(layer, id): get the amount of the buyable the player has
  • setBuyableAmount(layer, id, amount): set the amount of the buyable the player has
  • buyableEffect(layer, id): Returns the current effects of the buyable, if any.

Buyables should be formatted like this:

js
buyables: {
-    rows: # of rows,
-    cols: # of columns,
-    11: {
-        cost(x) { return new Decimal(1).mul(x || getBuyableAmt(this.layer, this.id)) },
-        display() { return "Blah" },
-        canAfford() { return player[this.layer].points.gte(this.cost()) },
-        buy() {
-            player[this.layer].points = player[this.layer].points.sub(this.cost())
-            setBuyableAmount(this.layer, this.id, getBuyableAmt(this.layer, this.id).add(1))
-        },
-        etc
-    },
-    etc
-}

Features:

  • title: optional. displayed at the top in a larger font. It can also be a function that returns updating text.

  • cost(): cost for buying the next buyable. Can have an optional argument "x" to calculate the cost of the x+1th object, but needs to use "current amount" as a default value for x. (x is a Decimal). Can return an object if there are multiple currencies.

  • effect(): optional. A function that calculates and returns the current values of bonuses of this buyable. Can return a value or an object containing multiple values.

  • display(): A function returning everything that should be displayed on the buyable after the title, likely including the description, amount bought, cost, and current effect. Can use basic HTML.

  • unlocked(): optional. A function returning a bool to determine if the buyable is visible or not. Default is unlocked.

  • canAfford(): A function returning a bool to determine if you can buy one of the buyables.

  • buy(): A function that implements buying one of the buyable, including spending the currency.

  • buyMax(): optional. A function that implements buying as many of the buyable as possible.

  • style: optional. Applies CSS to this buyable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

  • id: assigned automagically. It's the "key" which the buyable was stored under, for convenient access. The buyable in the example's id is 11.

Sell One/Sell All:

Including a sellOne or sellAll function will cause an additional button to appear beneath the buyable. They are functionally identical, but "sell one" appears above "sell all". You can also use them for other things.

  • sellOne/sellAll(): optional. Called when the button is pressed. The standard use would be to decrease/reset the amount of the buyable, and possibly return some currency to the player.

  • canSellOne/canSellAll(): optional. booleans determining whether or not to show the buttons. If "canSellOne/All" is absent but "sellOne/All" is present, the appropriate button will always show.

`,12),n=[l];function h(p,k,r,o,d,E){return a(),i("div",null,n)}const c=s(e,[["render",h]]);export{y as __pageData,c as default}; diff --git a/assets/public_lit_docs_buyables.md.-Ov6NyGO.lean.js b/assets/public_lit_docs_buyables.md.-Ov6NyGO.lean.js deleted file mode 100644 index ceba3f7a..00000000 --- a/assets/public_lit_docs_buyables.md.-Ov6NyGO.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as i,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Buyables","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/buyables.md","filePath":"public/lit/docs/buyables.md"}'),e={name:"public/lit/docs/buyables.md"},l=t("",12),n=[l];function h(p,k,r,o,d,E){return a(),i("div",null,n)}const c=s(e,[["render",h]]);export{y as __pageData,c as default}; diff --git a/assets/public_lit_docs_challenges.md.BoYK1lsk.js b/assets/public_lit_docs_challenges.md.BoYK1lsk.js deleted file mode 100644 index 32a60d78..00000000 --- a/assets/public_lit_docs_challenges.md.BoYK1lsk.js +++ /dev/null @@ -1,11 +0,0 @@ -import{_ as e,c as i,o as s,a5 as a}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Challenges","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/challenges.md","filePath":"public/lit/docs/challenges.md"}'),t={name:"public/lit/docs/challenges.md"},n=a(`

Challenges ​

Challenges can have fully customizable win conditions. Useful functions for dealing with Challenges and implementing their effects:

  • inChallenge(layer, id): determine if the player is in a given challenge (or another challenge on the same layer that counts as this one).
  • hasChallenge(layer, id): determine if the player has completed the challenge.
  • challengeCompletions(layer, id): determine how many times the player completed the challenge.
  • challengeEffect(layer, id): Returns the current effects of the challenge, if any.

Challenges are stored in the following format:

js
challenges: {
-    rows: # of rows,
-    cols: # of columns,
-    11: {
-        name: "Ouch",
-        challengeDescription: "description of ouchie",
-        goal: new Decimal(100),
-        etc
-    },
-    etc
-}

Each challenge should have an id where the first digit is the row and the second digit is the column.

Individual Challenges can have these features:

  • name: Name of the challenge, can be a string or a function. Can use basic HTML.

  • challengeDescription: A description of what makes the challenge a challenge. You will need to implement these elsewhere. It can also be a function that returns updating text. Can use basic HTML.

  • goalDescription: A description of the win condition for the challenge. It can also be a function that returns updating text. Can use basic HTML. (Optional if using the old goal system)

  • canComplete(): A function that returns true if you meet the win condition for the challenge. Returning a number will allow bulk completing the challenge. (Optional if using the old goal system)

  • rewardDescription: A description of the reward's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

  • rewardEffect(): optional. A function that calculates and returns the current values of any bonuses from the reward. Can return a value or an object containing multiple values. Can use basic HTML.

  • rewardDisplay(): optional. A function that returns a display of the current effects of the reward with formatting. Default behavior is to just display the a number appropriately formatted.

  • fullDisplay(): OVERRIDE. Overrides the other displays and descriptions, and lets you set the full text for the challenge. Can use basic HTML.

  • unlocked(): optional. A function returning a bool to determine if the challenge is visible or not. Default is unlocked.

  • onComplete() - optional. this function will be called when the challenge is completed when previously incomplete.

  • countsAs: optional. If a challenge combines the effects of other challenges in this layer, you can use this. An array of challenge ids. The player is effectively in all of those challenges when in the current one.

  • completionLimit: optional. the amount of times you can complete this challenge. Default is 1 completion.

  • style: optional. Applies CSS to this challenge, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: assigned automagically. It's the "key" which the challenge was stored under, for convenient access. The challenge in the example's id is 11.

The old goal system uses these features:

  • goal: deprecated, A Decimal for the amount of currency required to beat the challenge. By default, the goal is in basic Points. The goal can also be a function if its value changes.

  • currencyDisplayName: deprecated. the name to display for the currency for the goal

  • currencyInternalName: deprecated. the internal name for that currency

  • currencyLayer: deprecated. the internal name of the layer that currency is stored in. If it's not in a layer, omit. If it's not stored directly in a layer, instead use the next feature.

  • currencyLocation(): deprecated. if your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

`,10),l=[n];function o(h,r,p,c,g,d){return s(),i("div",null,l)}const k=e(t,[["render",o]]);export{f as __pageData,k as default}; diff --git a/assets/public_lit_docs_challenges.md.BoYK1lsk.lean.js b/assets/public_lit_docs_challenges.md.BoYK1lsk.lean.js deleted file mode 100644 index de42b059..00000000 --- a/assets/public_lit_docs_challenges.md.BoYK1lsk.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as i,o as s,a5 as a}from"./chunks/framework.CK8QU5WH.js";const f=JSON.parse('{"title":"Challenges","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/challenges.md","filePath":"public/lit/docs/challenges.md"}'),t={name:"public/lit/docs/challenges.md"},n=a("",10),l=[n];function o(h,r,p,c,g,d){return s(),i("div",null,l)}const k=e(t,[["render",o]]);export{f as __pageData,k as default}; diff --git a/assets/public_lit_docs_clickables.md.B6OakSbD.js b/assets/public_lit_docs_clickables.md.B6OakSbD.js deleted file mode 100644 index 85be76e2..00000000 --- a/assets/public_lit_docs_clickables.md.B6OakSbD.js +++ /dev/null @@ -1,9 +0,0 @@ -import{_ as e,c as s,o as i,a5 as a}from"./chunks/framework.CK8QU5WH.js";const b=JSON.parse('{"title":"Clickables","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/clickables.md","filePath":"public/lit/docs/clickables.md"}'),t={name:"public/lit/docs/clickables.md"},l=a(`

Clickables ​

Clickables are any kind of thing that you can click for an effect. They're a more generalized version of Buyables.

DO NOT USE THESE TO MAKE THINGS THAT YOU CLICK REPEATEDLY FOR A BONUS BECAUSE THOSE ARE AWFUL.

There are several differences between the two. One is that a buyable's saved data is its amount as a Decimal, while Clickables store a "state" which can be a number or string, but not Decimal, array, or object). Buyables have a number of extra features which you can see on their page. Clickables also have a smaller default size.

Useful functions for dealing with achievements and implementing their effects:

  • getClickableState(layer, id): get the state of the clickable the player has
  • setClickableState(layer, id, state): set the state of the buyable the player has
  • clickableEffect(layer, id): Returns the current effects of the clickable, if any.

Clickables should be formatted like this:

js
clickables: {
-    rows: # of rows,
-    cols: # of columns,
-    11: {
-        display() {return "Blah"},
-        etc
-    }
-    etc
-}

Features:

  • title: optional. displayed at the top in a larger font. It can also be a function that returns updating text.

  • effect(): optional. A function that calculates and returns the current values of bonuses of this clickable. Can return a value or an object containing multiple values.

  • display(): A function returning everything that should be displayed on the clickable after the title, likely changing based on its state. Can use basic HTML.

  • unlocked(): optional. A function returning a bool to determine if the clickable is visible or not. Default is unlocked.

  • canClick(): A function returning a bool to determine if you can click the clickable.

  • onClick(): A function that implements clicking one of the clickable.

  • style: optional. Applies CSS to this clickable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

  • id: assigned automagically. It's the "key" which the clickable was stored under, for convenient access. The clickable in the example's id is 11.

You can also use these features on the clickables object to add a button above all the clickables, for implementing a respec button or similar.

  • masterButtonPress(): optional. If present, an additional button will appear above the clickables. Pressing it will call this function.

  • masterButtonText: optional. Text to display on the Master Button.

  • showMasterButton(): optional. A function determining whether or not to show the button. Defaults to true if absent.

`,12),n=[l];function o(c,r,h,p,k,u){return i(),s("div",null,n)}const g=e(t,[["render",o]]);export{b as __pageData,g as default}; diff --git a/assets/public_lit_docs_clickables.md.B6OakSbD.lean.js b/assets/public_lit_docs_clickables.md.B6OakSbD.lean.js deleted file mode 100644 index dc7ec01e..00000000 --- a/assets/public_lit_docs_clickables.md.B6OakSbD.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as s,o as i,a5 as a}from"./chunks/framework.CK8QU5WH.js";const b=JSON.parse('{"title":"Clickables","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/clickables.md","filePath":"public/lit/docs/clickables.md"}'),t={name:"public/lit/docs/clickables.md"},l=a("",12),n=[l];function o(c,r,h,p,k,u){return i(),s("div",null,n)}const g=e(t,[["render",o]]);export{b as __pageData,g as default}; diff --git a/assets/public_lit_docs_custom-tab-layouts.md.DVTPJ8Y_.js b/assets/public_lit_docs_custom-tab-layouts.md.DVTPJ8Y_.js deleted file mode 100644 index 73a32b51..00000000 --- a/assets/public_lit_docs_custom-tab-layouts.md.DVTPJ8Y_.js +++ /dev/null @@ -1,14 +0,0 @@ -import{_ as s,c as i,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Custom tab layouts","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/custom-tab-layouts.md","filePath":"public/lit/docs/custom-tab-layouts.md"}'),e={name:"public/lit/docs/custom-tab-layouts.md"},n=t(`

Custom tab layouts ​

Note: If you are using subtabs, tabFormat is used differently, but you still use the same format within each subtabs. See here for more on subtabs.

Custom tab layouts can be used to do basically anything in a tab window, especially combined with the "style" layer feature. The tabFormat feature is an array of things, like this:

js
tabFormat: [
-    "main-display",
-    ["prestige-button", function() { return "Melt your points into " }],
-    "blank",
-    ["display-text",
-        function() { return 'I have ' + format(player.points) + ' pointy points!' },
-        { "color": "red", "font-size": "32px", "font-family": "Comic Sans MS" }],
-    "blank",
-    ["toggle", ["c", "beep"]],
-    "milestones",
-    "blank",
-    "blank",
-    "upgrades"
-]

It is a list of components, which can be either just a name, or an array with arguments. If it's an array, the first item is the name of the component, the second is the data passed into it, and the third (optional) applies a CSS style to it with a "CSS object", where the keys are CSS attributes.

These are the existing components, but you can create more in components.js:

  • display-text: Displays some text (can use basic HTML). The argument is the text to display. It can also be a function that returns updating text.

  • raw-html: Displays some basic HTML, can also be a function.

  • blank: Adds empty space. The default dimensions are 8px x 17px. The argument changes the dimensions. If it's a single value (e.g. "20px"), that determines the height. If you have a pair of arguments, the first is width and the second is height.

  • row: Display a list of components horizontally. The argument is an array of components in the tab layout format.

  • column: Display a list of components vertically. The argument is an array of components in the tab layout format. This is useful to display columns within a row.

  • main-display: The text that displays the main currency for the layer and its effects.

  • resource-display: The text that displays the currency that this layer is based on, as well as the best and/or total values for this layer's prestige currency (if they are put in startData for this layer).

  • prestige-button: The argument is a string that the prestige button should say before the amount of currency you will gain. It can also be a function that returns updating text.

  • upgrades: The layer's upgrades. The argument is optional, and is a the list of rows this component should include, if it doesn't have all of them.

  • milestones, challenges, achievements: Display the upgrades, milestones, and challenges for a layer, as appropriate.

  • buyables, clickables: Display all of the buyables/clickables for this layer, as appropriate. The argument is optional and is the size of the boxes in pixels.

  • microtabs: Display a set of subtabs for an area. The argument is the name of the set of microtabs in the "microtabs" feature.

  • bar: Display a bar. The argument is the id of the bar to display.

  • infobox: Display an infobox. The argument is the id of the infobox to display.

  • tree: Displays a tree. The argument is an array of arrays containing the names of the nodes in the tree (first by row, then by column) See here for more information on tree layouts and nodes!

  • toggle: A toggle button that toggles a bool value. The data is a pair that identifies what bool to toggle, e.g. [layer, id]

The rest of the components are sub-components. They can be used just like other components, but are typically part of another component.

  • upgrade, milestone, challenge, buyable, clickable, achievement: An individual upgrade, challenge, etc. The argument is the id. This can be used if you want to have upgrades split up across multiple subtabs, for example.

  • respec-button, master-button: The respec and master buttons for buyables and clickables, respectively.

  • sell-one, sell-all: The "sell one" and "sell all" for buyables, respectively. The argument is the id of the buyable.

`,9),l=[n];function h(o,p,r,u,k,d){return a(),i("div",null,l)}const E=s(e,[["render",h]]);export{y as __pageData,E as default}; diff --git a/assets/public_lit_docs_custom-tab-layouts.md.DVTPJ8Y_.lean.js b/assets/public_lit_docs_custom-tab-layouts.md.DVTPJ8Y_.lean.js deleted file mode 100644 index c7240915..00000000 --- a/assets/public_lit_docs_custom-tab-layouts.md.DVTPJ8Y_.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as i,o as a,a5 as t}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Custom tab layouts","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/custom-tab-layouts.md","filePath":"public/lit/docs/custom-tab-layouts.md"}'),e={name:"public/lit/docs/custom-tab-layouts.md"},n=t("",9),l=[n];function h(o,p,r,u,k,d){return a(),i("div",null,l)}const E=s(e,[["render",h]]);export{y as __pageData,E as default}; diff --git a/assets/public_lit_docs_getting-started.md.CsxQcaII.js b/assets/public_lit_docs_getting-started.md.CsxQcaII.js deleted file mode 100644 index 04f5973a..00000000 --- a/assets/public_lit_docs_getting-started.md.CsxQcaII.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o,a5 as i}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Getting started","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/getting-started.md","filePath":"public/lit/docs/getting-started.md"}'),a={name:"public/lit/docs/getting-started.md"},n=i('

Getting started ​

Welcome to The Modding Tree!

Using the Modding Tree, at its simplest level, just requires getting a copy of it onto your computer. However, if you do it the right way, it will help in many ways.

Don't let the word "Github" scare you away. It's actually much easier to use than most people think, especially because most people use it the hard way. The key is Github Desktop, which lets you do everything you need to, without even touching the command line.

The benefits of using Github:

  • It makes it much, much easier to update The Modding Tree.
  • You can share your work without any extra effort using githack, or with a bit more effort, set up a github.io site.
  • It lets you undo changes to your code, and to have multiple versions of it.
  • It lets you collaborate with other people, if you want to.

Getting set up with Github Desktop, Visual Studio Code, and The Modding Tree: ​

  1. Install Github Desktop and Visual Studio Code.

  2. Make a Github account. You can handle this on your own.

  3. Log in on your browser, and go back to The Modding Tree page. At the top right, there should be a button that says "fork". Click on it, and then on your username. You now have your own fork, or copy, of The Modding Tree.

  4. Open Github Desktop and log in. Ignore everything else and choose "clone a repository". A "repository" is basically a "Github project", like The Modding Tree. "Cloning" is downloading a copy of the repository to your computer.

  5. Look for The Modding Tree in the list of repositiories (it should be the only one) and click "clone".

  6. Select that you're using it for your own purposes, and click continue. It will download the files and handle everything.

Using your repository ​

  1. Click on "show in explorer/finder" to the right, and then open the index.html file in the folder. The page should open up on your browser. This will let you view and test your project locally!

  2. To edit your project, click "open in VSCode" in Github Desktop.

  3. Open mod.js in VSCode, and look at the top part where it has a "modInfo" object. Fill in your mod's name to whatever you want, and change the id as well. (It can be any string value, and it's used to determine where the savefile is. Make it something that's probably unique, and don't change it again later or else it'll effectively wipe existing saves)

  4. Save mod.js, and then reload index.html in your browser. The title on the tab, as well as on the info page, will now be updated! You can reload the page every time you change the code to test it quickly and easily.

  5. Go back to Github Desktop. It's time to save your changes into the git system by making a "commit". This basically saves your work and creates a snapshot of what your code looks like at this moment, allowing you to look back at it later.

  6. At the bottom right corner, add a summary of your changes, and then click "commit to master".

  7. Finally, at the top middle, click "push origin" to push your changes out onto the online repository.

  8. You can view your project on line, or share it with others, by going to https://raw.githack.com/[YOUR-GITHUB-USERNAME]/The-Modding-Tree/master/index.html

And now, you have successfully used Github! You can look at the documentation to see how The Modding Tree's system works and to make your mod a reality.

',11),r=[n];function s(l,h,u,d,p,c){return o(),t("div",null,r)}const m=e(a,[["render",s]]);export{y as __pageData,m as default}; diff --git a/assets/public_lit_docs_getting-started.md.CsxQcaII.lean.js b/assets/public_lit_docs_getting-started.md.CsxQcaII.lean.js deleted file mode 100644 index 5843f7ba..00000000 --- a/assets/public_lit_docs_getting-started.md.CsxQcaII.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o,a5 as i}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Getting started","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/getting-started.md","filePath":"public/lit/docs/getting-started.md"}'),a={name:"public/lit/docs/getting-started.md"},n=i("",11),r=[n];function s(l,h,u,d,p,c){return o(),t("div",null,r)}const m=e(a,[["render",s]]);export{y as __pageData,m as default}; diff --git a/assets/public_lit_docs_infoboxes.md.BuPTImhx.js b/assets/public_lit_docs_infoboxes.md.BuPTImhx.js deleted file mode 100644 index af561081..00000000 --- a/assets/public_lit_docs_infoboxes.md.BuPTImhx.js +++ /dev/null @@ -1,8 +0,0 @@ -import{_ as s,c as i,o as e,a5 as t}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Infoboxes","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/infoboxes.md","filePath":"public/lit/docs/infoboxes.md"}'),a={name:"public/lit/docs/infoboxes.md"},n=t(`

Infoboxes ​

Infoboxes are good for displaying "lore", or story elements, as well as for explaining complicated things.

In the default tab layout, the first infobox will be displayed at the very top of the tab.

Infoboxes are defined like other Big Features:

js
infoboxes: {
-    lore: {
-        title: "foo",
-        body() { return "bar" },
-        etc
-    },
-    etc
-}

Features:

  • title: The text displayed above the main box. Can be a function to be dynamic, and can use basic HTML.

  • body: The text displayed inside the box. Can be a function to be dynamic, and can use basic HTML.

  • style, titleStyle, bodyStyle: optional. Apply CSS to the infobox, or to the title button or body of the infobox, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • unlocked(): optional. A function returning a bool to determine if the infobox is visible or not. Default is unlocked.

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: assigned automagically. It's the "key" which the bar was stored under, for convenient access. The infobox in the example's id is "lore".

`,7),o=[n];function l(p,h,r,d,c,k){return e(),i("div",null,o)}const y=s(a,[["render",l]]);export{u as __pageData,y as default}; diff --git a/assets/public_lit_docs_infoboxes.md.BuPTImhx.lean.js b/assets/public_lit_docs_infoboxes.md.BuPTImhx.lean.js deleted file mode 100644 index 10de8b7c..00000000 --- a/assets/public_lit_docs_infoboxes.md.BuPTImhx.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as i,o as e,a5 as t}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Infoboxes","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/infoboxes.md","filePath":"public/lit/docs/infoboxes.md"}'),a={name:"public/lit/docs/infoboxes.md"},n=t("",7),o=[n];function l(p,h,r,d,c,k){return e(),i("div",null,o)}const y=s(a,[["render",l]]);export{u as __pageData,y as default}; diff --git a/assets/public_lit_docs_layer-features.md.sExHYK2Z.js b/assets/public_lit_docs_layer-features.md.sExHYK2Z.js deleted file mode 100644 index 7f55cd83..00000000 --- a/assets/public_lit_docs_layer-features.md.sExHYK2Z.js +++ /dev/null @@ -1,10 +0,0 @@ -import{_ as e,c as t,o as a,a5 as s}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Layer Features","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/layer-features.md","filePath":"public/lit/docs/layer-features.md"}'),i={name:"public/lit/docs/layer-features.md"},o=s(`

Layer Features ​

This is a more comprehensive list of established features to add to layers. You can add more freely, if you want to have other functions or values associated with your layer. These have special functionality, though.

You can make almost any value dynamic by using a function in its place, including all display strings and styling/color features.

Layer Definition features ​

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar to access the saved value. It makes copying code to new layers easier. It is also assigned to all upgrades and buyables and such.

  • name: optional. used in reset confirmations (and the default infobox title). If absent, it just uses the layer's id.

  • startData(): A function to return the default save data for this layer. Add any variables you have to it. Make sure to use Decimal values rather than normal numbers.

    Standard values: - Required: - unlocked: a bool determining if this layer is unlocked or not - points: a Decimal, the main currency for the layer - Optional: - total: A Decimal, tracks total amount of main prestige currency. Always tracked, but only shown if you add it here. - best: A Decimal, tracks highest amount of main prestige currency. Always tracked, but only shown if you add it here. - unlockOrder: used to keep track of relevant layers unlocked before this one. - resetTime: A number, time since this layer was last prestiged (or reset by another layer)

  • color: A color associated with this layer, used in many places. (A string in hex format with a #)

  • row: The row of the layer, starting at 0. This affects where the node appears on the standard tree, and which resets affect the layer.

    Using "side" instead of a number will cause the layer to appear off to the side as a smaller node (useful for achievements and statistics). Side layers are not affected by resets unless you add a doReset to them.

  • displayRow: OVERRIDE Changes where the layer node appears without changing where it is in the reset order.

  • resource: Name of the main currency you gain by resetting on this layer.

  • effect(): optional. A function that calculates and returns the current values of any bonuses inherent to the main currency. Can return a value or an object containing multiple values. You will also have to implement the effect where it is applied.

  • effectDescription: optional. A function that returns a description of this effect. If the text stays constant, it can just be a string.

  • layerShown(): optional, A function returning a bool which determines if this layer's node should be visible on the tree. It can also return "ghost", which will hide the layer, but its node will still take up space in the tree. Defaults to true.

  • hotkeys: optional. An array containing information on any hotkeys associated with this layer:

    js
    hotkeys: [
-    {
-        key: "p", // What the hotkey button is. Use uppercase if it's combined with shift, or "ctrl+x" for holding down ctrl.
-        description: "p: reset your points for prestige points", // The description of the hotkey that is displayed in the game's How To Play tab
-        onPress() { if (player.p.unlocked) doReset("p") }
-    }
-]

  • style: optional. a "CSS object" where the keys are CSS attributes, containing any CSS that should affect this layer's entire tab.

  • tabFormat: optional. use this if you want to add extra things to your tab or change the layout. See here for more info.

  • midsection: optional, an alternative to tabFormat, which is inserted in between Milestones and Buyables in the standard tab layout. (cannot do subtabs)

Big features (all optional) ​

  • upgrades: A grid of one-time purchases which can have unique upgrade conditions, currency costs, and bonuses. See here for more info.

  • milestones: A list of bonuses gained upon reaching certain thresholds of a resource. Often used for automation/QOL. See here for more info.

  • challenges: The player can enter challenges, which make the game harder. If they reach a goal and beat the challenge, they recieve a bonus. See here for more info.

  • buyables: Effectively upgrades that can be bought multiple times, and are optionally respeccable. Many uses. See here for more info.

  • clickables: Extremely versatile and generalized buttons which can only be clicked sometimes. See here for more info.

  • microtabs: An area that functions like a set of subtabs, with buttons at the top changing the content within. (Advanced) See here for more info.

  • bars: Display some information as a progress bar, gague, or similar. They are highly customizable, and can be vertical as well. See here for more info.

  • achievements: Kind of like milestones, but with a different display style and some other differences. Extra features are on the way at a later date! See here for more info.

  • infoboxes: Displays some text in a box that can be shown or hidden. See here for more info.

  • achievementPopups, milestonePopups: optional, If false, disables popup message when you get the achievement/milestone. True by default.

Prestige formula features ​

  • type: optional. Determines which prestige formula you use. Defaults to "none".

    • "normal": The amount of currency you gain is independent of its current amount (like Prestige). The formula before bonuses is based on baseResource^exponent
    • "static": The cost is dependent on your total after reset. The formula before bonuses is based on base^(x^exponent)
    • "custom": You can define everything, from the calculations to the text on the button, yourself. (See more at the bottom)
    • "none": This layer does not prestige, and therefore does not need any of the other features in this section.

  • baseResource: The name of the resource that determines how much of the main currency you gain on reset.

  • baseAmount(): A function that gets the current value of the base resource.

  • requires: A Decimal, the amount of the base needed to gain 1 of the prestige currency. Also the amount required to unlock the layer. You can instead make this a function, to make it harder if another layer was unlocked first (based on unlockOrder).

  • exponent: Used as described above.

  • base: sometimes required. required for "static" layers, used as described above. If absent, defaults to 2. Must be greater than 1.

  • roundUpCost: optional. a bool, which is true if the resource cost needs to be rounded up. (use if the base resource is a "static" currency.)

  • gainMult(), gainExp(): optional. Functions that calculate the multiplier and exponent on resource gain from upgrades and boosts and such. Plug in any bonuses here.

  • softcap, softcapPower: optional. For normal layers, gain beyond [softcap] points is put to the [softcapPower]th power Default for softcap is e1e7, and for power is 0.5.

  • canBuyMax(): sometimes required. required for static layers, function used to determine if buying max is permitted.

  • onPrestige(gain): optional. A function that triggers when this layer prestiges, just before you gain the currency. Can be used to have secondary resource gain on prestige, or to recalculate things or whatnot.

  • resetDescription: optional. Use this to replace "Reset for " on the Prestige button with something else.

  • prestigeButtonText(): sometimes required. Use this to make the entirety of the text a Prestige button contains. Only required for custom layers, but usable by all types.

  • passiveGeneration(): optional, returns a regular number. You automatically generate your gain times this number every second (does nothing if absent) This is good for automating Normal layers.

  • autoPrestige(): optional, returns a boolean, if true, the layer will always automatically do a prestige if it can. This is good for automating Static layers.

Tree/node features ​

  • symbol: optional. The text that appears on this layer's node. Default is the layer id with the first letter capitalized.

  • image: override. The url (local or global) of an image that goes on the node. (Overrides symbol)

  • position: optional. Determines the horizontal position of the layer in its row in a standard tree. By default, it uses the layer id, and layers are sorted in alphabetical order.

  • branches: optional. An array of layer/node ids. On a tree, a line will appear from this layer to all of the layers in the list. Alternatively, an entry in the array can be a 2-element array consisting of the layer id and a color value. The color value can either be a string with a hex color code, or a number from 1-3 (theme-affected colors).

  • nodeStyle: optional. A CSS object, where the keys are CSS attributes, which styles this layer's node on the tree.

  • tooltip() / tooltipLocked(): optional. Functions that return text, which is the tooltip for the node when the layer is unlocked or locked, respectively. By default the tooltips behave the same as in the original Prestige Tree. If the value is "", the tooltip will be disabled.

Other features ​

  • doReset(resettingLayer): optional. Is triggered when a layer on a row greater than or equal to this one does a reset. The default behavior is to reset everything on the row, but only if it was triggered by a layer in a higher row. doReset is always called for side layers, but for these the default behavior is to reset nothing.

    If you want to keep things, determine what to keep based on resettingLayer, milestones, and such, then call layerDataReset(layer, keep), where layer is this layer, and keep is an array of the names of things to keep. It can include things like "points", "best", "total" (for this layer's prestige currency), "upgrades", any unique variables like "generatorPower", etc. If you want to only keep specific upgrades or something like that, save them in a separate variable, then call layerDataReset, and then set player[this.layer].upgrades to the saved upgrades.

  • update(diff): optional. This function is called every game tick. Use it for any passive resource production or time-based things. diff is the time since the last tick.

  • autoUpgrade: optional, a boolean value, if true, the game will attempt to buy this layer's upgrades every tick. Defaults to false.

  • automate(): optional. This function is called every game tick, after production. Use it to activate automation things that aren't otherwise supported.

  • resetsNothing: optional. Returns true if this layer shouldn't trigger any resets when you prestige.

  • increaseUnlockOrder: optional. An array of layer ids. When this layer is unlocked for the first time, the unlockOrder value for any not-yet-unlocked layers in this list increases. This can be used to make them harder to unlock.

  • shouldNotify: optional. A function to return true if this layer should be highlighted in the tree. The layer will automatically be highlighted if you can buy an upgrade whether you have this or not.

  • componentStyles: optional. An object that contains a set of functions returning CSS objects. Each of these will be applied to any components on the layer with the type of its id. Example:

js
componentStyles: {
-    "challenge"() { return {'height': '200px'} },
-    "prestige-button"() { return {'color': '#AA66AA'} }
-}

Custom Prestige type ​

(All of these can also be used by other prestige types)

  • getResetGain(): mostly for custom prestige type. Returns how many points you should get if you reset now. You can call getResetGain(this.layer, useType = "static") or similar to calculate what your gain would be under another prestige type (provided you have all of the required features in the layer).

  • getNextAt(canMax=false): mostly for custom prestige type. Returns how many of the base currency you need to get to the next point. canMax is an optional variable used with Static-ish layers to differentiate between if it's looking for the first point you can reset at, or the requirement for any gain at all (Supporting both is good). You can also call getNextAt(this.layer, canMax=false, useType = "static") or similar to calculate what your next at would be under another prestige type (provided you have all of the required features in the layer).

  • canReset(): mostly for custom prestige type. Return true only if you have the resources required to do a prestige here.

  • prestigeNotify(): mostly for custom prestige types, returns true if this layer should be subtly highlighted to indicate you can prestige for a meaningful gain.

`,19),r=[o];function n(l,h,u,p,d,c){return a(),t("div",null,r)}const f=e(i,[["render",n]]);export{y as __pageData,f as default}; diff --git a/assets/public_lit_docs_layer-features.md.sExHYK2Z.lean.js b/assets/public_lit_docs_layer-features.md.sExHYK2Z.lean.js deleted file mode 100644 index e437eef5..00000000 --- a/assets/public_lit_docs_layer-features.md.sExHYK2Z.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as a,a5 as s}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Layer Features","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/layer-features.md","filePath":"public/lit/docs/layer-features.md"}'),i={name:"public/lit/docs/layer-features.md"},o=s("",19),r=[o];function n(l,h,u,p,d,c){return a(),t("div",null,r)}const f=e(i,[["render",n]]);export{y as __pageData,f as default}; diff --git a/assets/public_lit_docs_main-mod-info.md.CVm1BK0i.js b/assets/public_lit_docs_main-mod-info.md.CVm1BK0i.js deleted file mode 100644 index c5d26a71..00000000 --- a/assets/public_lit_docs_main-mod-info.md.CVm1BK0i.js +++ /dev/null @@ -1,5 +0,0 @@ -import{_ as i,c as t,o as e,a5 as s}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"mod.js","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/main-mod-info.md","filePath":"public/lit/docs/main-mod-info.md"}'),a={name:"public/lit/docs/main-mod-info.md"},n=s(`

mod.js ​

All of the non-layer code and data that you're likely to edit is here in mod.js! Everything in mod.js will not be altered by updates, besides the addition of new things.

Here's a breakdown of what's in it:

  • modInfo is where most of the basic configuration for the mod is. It contains:

    • name: The name of your mod. (a string)

    • id: The id for your mod, a unique string that is used to determine savefile location. Setting it is important!

    • author: The name of the author, displayed in the info tab.

    • pointsName: This changes what is displayed instead of "points" for the main currency. (It does not affect it in the code.)

    • discordName, discordLink: If you have a Discord server or other discussion place, you can add a link to it.

      "discordName" is the text on the link, and "discordLink" is the url of an invite. If you're using a Discord invite, please make sure it's set to never expire.

    • offlineLimit: The maximum amount of offline time that the player can accumulate, in hours. Any extra time is lost. (a number)

      This is useful because most of these mods are fast-paced enough that too much offline time ruins the balance, such as the time in between updates. That is why I suggest developers disable offline time on their own savefile.

    • initialStartPoints: A Decimal for the amount of points a new player should start with.

  • VERSION is used to describe the current version of your mod. It contains:

    • num: The mod's version number, displayed at the top right of the tree tab.
    • name: The version's name, displayed alongside the number in the info tab.

  • changelog is the HTML displayed in the changelog tab.

  • doNotCallTheseFunctionsEveryTick is very important. TMT calls every function anywhere in "layers" every tick to store the result, unless specifically told not to. Functions that have are used to do an action need to be identified. "Official" functions (those in the documentation) are all fine, but if you make any new ones, add their names to this array.

js
// (The ones here are examples, all official functions are already taken care of)
-var doNotCallTheseFunctionsEveryTick = ["doReset", "buy", "onPurchase", "blowUpEverything"]

  • getStartPoints(): A function to determine the amount of points the player starts with after a reset. (returns a Decimal value)

  • canGenPoints(): A function returning a boolean for if points should be generated. Use this if you want an upgrade to unlock generating points.

  • getPointGen(): A function that calculates your points per second. Anything that affects your point gain should go into the calculation here.

  • addedPlayerData(): A function that returns any non-layer-related data that you want to be added to the save data and "player" object.

js
function addedPlayerData() { return {
-	weather: "Yes",
-	happiness: new Decimal(72),
-}}

  • displayThings: An array of functions used to display extra things at the top of the tree tab. Each function returns a string, which is a line to display (with basic HTML support). If a function returns nothing, nothing is displayed (and it doesn't take up a line).

  • isEndgame(): A function to determine if the player has reached the end of the game, at which point the "you win!" screen appears.

Less important things beyond this point!

  • maxTickLength(): Returns the maximum tick length, in milliseconds. Only really useful if you have something that reduces over time, which long ticks mess up (usually a challenge).
`,10),o=[n];function l(h,p,r,d,u,c){return e(),t("div",null,o)}const y=i(a,[["render",l]]);export{m as __pageData,y as default}; diff --git a/assets/public_lit_docs_main-mod-info.md.CVm1BK0i.lean.js b/assets/public_lit_docs_main-mod-info.md.CVm1BK0i.lean.js deleted file mode 100644 index 1f743fa8..00000000 --- a/assets/public_lit_docs_main-mod-info.md.CVm1BK0i.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as i,c as t,o as e,a5 as s}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"mod.js","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/main-mod-info.md","filePath":"public/lit/docs/main-mod-info.md"}'),a={name:"public/lit/docs/main-mod-info.md"},n=s("",10),o=[n];function l(h,p,r,d,u,c){return e(),t("div",null,o)}const y=i(a,[["render",l]]);export{m as __pageData,y as default}; diff --git a/assets/public_lit_docs_milestones.md.Cf2Qcvln.js b/assets/public_lit_docs_milestones.md.Cf2Qcvln.js deleted file mode 100644 index febc8f83..00000000 --- a/assets/public_lit_docs_milestones.md.Cf2Qcvln.js +++ /dev/null @@ -1,8 +0,0 @@ -import{_ as e,c as s,o as i,a5 as t}from"./chunks/framework.CK8QU5WH.js";const k=JSON.parse('{"title":"Milestones","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/milestones.md","filePath":"public/lit/docs/milestones.md"}'),a={name:"public/lit/docs/milestones.md"},n=t(`

Milestones ​

Milestones are awarded to the player when they meet a certain goal, and give some benefit. Milestones should be formatted like this:

js
milestones: {
-    0: {
-        requirementDescription: "123 waffles",
-        effectDescription: "blah",
-        done() { return player.w.points.gte(123) }
-    }
-    etc
-}

You can use hasMilestone(layer, id) to determine if the player has a given milestone

Milestone features:

  • requirementDescription: A string describing the requirement for unlocking this milestone. Suggestion: Use a "total". It can also be a function that returns updating text. Can use basic HTML.

  • effectDescription: A string describing the reward for having the milestone. You will have to implement the reward elsewhere. It can also be a function that returns updating text. Can use basic HTML.

  • done(): A function returning a boolean to determine if the milestone should be awarded.

  • toggles: optional. Creates toggle buttons that appear on the milestone when it is unlocked. The toggles can toggle a given boolean value in a layer. It is defined as an array of paired items, one pair per toggle. The first is the internal name of the layer the value being toggled is stored in, and the second is the internal name of the variable to toggle. (e.g. [["b", "auto"], ["g", "auto"])

    Tip: Toggles are not de-set if the milestone becomes locked! In this case, you should also check if the player has the milestone.

  • style: optional. Applies CSS to this milestone, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • unlocked(): optional. A function returning a boolean to determine if the milestone should be shown. If absent, it is always shown.

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

  • id: assigned automagically. It's the "key" which the milestone was stored under, for convenient access. The milestone in the example's id is 0.

Disaable milestone popups by adding milestonePopups: false to the layer.

`,7),l=[n];function o(h,p,r,d,c,g){return i(),s("div",null,l)}const m=e(a,[["render",o]]);export{k as __pageData,m as default}; diff --git a/assets/public_lit_docs_milestones.md.Cf2Qcvln.lean.js b/assets/public_lit_docs_milestones.md.Cf2Qcvln.lean.js deleted file mode 100644 index fec28e38..00000000 --- a/assets/public_lit_docs_milestones.md.Cf2Qcvln.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as s,o as i,a5 as t}from"./chunks/framework.CK8QU5WH.js";const k=JSON.parse('{"title":"Milestones","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/milestones.md","filePath":"public/lit/docs/milestones.md"}'),a={name:"public/lit/docs/milestones.md"},n=t("",7),l=[n];function o(h,p,r,d,c,g){return i(),s("div",null,l)}const m=e(a,[["render",o]]);export{k as __pageData,m as default}; diff --git a/assets/public_lit_docs_subtabs-and-microtabs.md.DhbrQf33.js b/assets/public_lit_docs_subtabs-and-microtabs.md.DhbrQf33.js deleted file mode 100644 index 1cc608a4..00000000 --- a/assets/public_lit_docs_subtabs-and-microtabs.md.DhbrQf33.js +++ /dev/null @@ -1,25 +0,0 @@ -import{_ as s,c as a,o as t,a5 as i}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Subtabs and Microtabs","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/subtabs-and-microtabs.md","filePath":"public/lit/docs/subtabs-and-microtabs.md"}'),n={name:"public/lit/docs/subtabs-and-microtabs.md"},e=i(`

Subtabs and Microtabs ​

Subtabs are separate sections of a tab that you can view by selecting one at the top of the tab. Microtabs are smaller areas that function in much the same way. You can also embed layers inside of subtabs/microtabs.

Subtabs are defined by using the tab format like this, where each element of tabFormat is given the name of that subtab:

js
tabFormat: {
-    "Main tab": {
-        content: [tab format things],
-        *subtab features*
-    },
-    "Other tab": {
-        content: [tab format things],
-        *subtab features*
-    },
-    etc
-}

Microtabs are defined similarly, and use the same features, but are defined in the "microtabs" feature. Each entry is a group of tabs which will appear in a microtabs component. The first set, "stuff", has 2 tabs, and the second, "otherStuff", has none.

js
microtabs: {
-    stuff: {
-        first: {
-            content: [tab format things],
-            *subtab features*
-        },
-        second: {
-            content: [tab format things],
-            *subtab features*
-        }
-    },
-    otherStuff: {
-        // There could be another set of microtabs here
-    }
-}

Normal subtabs and microtab subtabs both use the same features:

Features: ​

  • content: The tab layout code for the subtab, in the tab layout format.

  • style: optional. Applies CSS to the whole subtab when switched to, in the form of an "CSS Object", where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • buttonStyle: optional. A CSS object, which affects the appearance of the button for that subtab.

  • unlocked(): optional. a function to determine if the button for this subtab should be visible. By default, a subtab is always unlocked. You can't use the "this" keyword in this function.

  • shouldNotify(): optional, if true, the tab button will be highlighted to notify the player that there is something there.

  • embedLayer: SIGNIFICANT, the id of another layer. If you have this, it will override "content", "style" and "shouldNotify", instead displaying the entire layer in the subtab.

`,9),l=[e];function h(p,o,r,k,c,d){return t(),a("div",null,l)}const E=s(n,[["render",h]]);export{u as __pageData,E as default}; diff --git a/assets/public_lit_docs_subtabs-and-microtabs.md.DhbrQf33.lean.js b/assets/public_lit_docs_subtabs-and-microtabs.md.DhbrQf33.lean.js deleted file mode 100644 index 02df5093..00000000 --- a/assets/public_lit_docs_subtabs-and-microtabs.md.DhbrQf33.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as s,c as a,o as t,a5 as i}from"./chunks/framework.CK8QU5WH.js";const u=JSON.parse('{"title":"Subtabs and Microtabs","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/subtabs-and-microtabs.md","filePath":"public/lit/docs/subtabs-and-microtabs.md"}'),n={name:"public/lit/docs/subtabs-and-microtabs.md"},e=i("",9),l=[e];function h(p,o,r,k,c,d){return t(),a("div",null,l)}const E=s(n,[["render",h]]);export{u as __pageData,E as default}; diff --git a/assets/public_lit_docs_trees-and-tree-customization.md.DpLqj7LC.js b/assets/public_lit_docs_trees-and-tree-customization.md.DpLqj7LC.js deleted file mode 100644 index 8ac8fb94..00000000 --- a/assets/public_lit_docs_trees-and-tree-customization.md.DpLqj7LC.js +++ /dev/null @@ -1,3 +0,0 @@ -import{_ as e,c as t,o as i,a5 as a}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Trees and tree customization","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/trees-and-tree-customization.md","filePath":"public/lit/docs/trees-and-tree-customization.md"}'),s={name:"public/lit/docs/trees-and-tree-customization.md"},o=a(`

Trees and tree customization ​

If you want to have something beyond the standard tree on the left tab, you can do that in tree.js. You can change the layout of the tree, including making non-layer nodes, change it into something other than a tree, or hide the left tab altogether. This also introduces the "tree" component, which can be used in your layers as well.

layoutInfo ​

The most important part is layoutInfo, containing:

  • startTab: The id of the default tab to show on the left at the start.
  • showTree: True if the tree tab should be shown at the start of the game. (The other tab will fill the whole page)
  • treeLayout: If present, overrides the tree layout and places nodes as you describe instead (explained in the next section).

Additionally, if you want the main layout to not be a tree, you can edit the "tree-tab" layer at the bottom of tree.js to modify it just like a normal layer's tab. You can even switch between left tabs, using showNavTab(layer) to make that layer appear on the left.

Trees ​

The tree component is defined as an array of arrays of names of layers or nodes to show in the tree. They work just like layers/ nodes in the main tree (but branches between nodes will only work on the first node if you have duplicates.)

Here is an example tree:

js
[["p"],
- ["left", "blank", "right", "blank"]
- ["a", "b", "blank", "c", "weirdButton"]]

Nodes ​

Nodes are non-layer buttons that can go in trees. They are defined similarly to layers, but with addNode instead of addLayer.

Features:

  • color: optional, The node's color. (A string in hex format with a #)

  • symbol: optional The text on the button (The id capitalized by default)

  • canClick(): Returns true if the player can click the node. ()

  • onClick(): The function called when the node is clicked.

  • layerShown(): optional, A function returning a bool which determines if this node should be visible. It can also return "ghost", which will hide the layer, but its node will still take up space in its tree.

  • branches: optional. An array of layer/node ids. On a tree, a line will appear from this node to all of the nodes in the list. Alternatively, an entry in the array can be a 2-element array consisting of the id and a color value. The color value can either be a string with a hex color code, or a number from 1-3 (theme-affected colors).

  • nodeStyle: optional. A CSS object, where the keys are CSS attributes, which styles this node on the tree.

  • tooltip() / tooltipLocked(): optional. Functions that return text, which is the tooltip for the node when the layer is unlocked or locked, respectively. By default the tooltips behave the same as in the original Prestige Tree.

  • row: optional, the row that this node appears in (for the default tree).

  • position: optional, Determines the horizontal position of the layer in its row in a default tree. By default, it uses the id, and layers/nodes are sorted in alphabetical order.

`,14),n=[o];function l(r,h,d,p,u,c){return i(),t("div",null,n)}const g=e(s,[["render",l]]);export{y as __pageData,g as default}; diff --git a/assets/public_lit_docs_trees-and-tree-customization.md.DpLqj7LC.lean.js b/assets/public_lit_docs_trees-and-tree-customization.md.DpLqj7LC.lean.js deleted file mode 100644 index 088a7baf..00000000 --- a/assets/public_lit_docs_trees-and-tree-customization.md.DpLqj7LC.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as t,o as i,a5 as a}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Trees and tree customization","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/trees-and-tree-customization.md","filePath":"public/lit/docs/trees-and-tree-customization.md"}'),s={name:"public/lit/docs/trees-and-tree-customization.md"},o=a("",14),n=[o];function l(r,h,d,p,u,c){return i(),t("div",null,n)}const g=e(s,[["render",l]]);export{y as __pageData,g as default}; diff --git a/assets/public_lit_docs_updating-tmt.md.C2pGYz0K.js b/assets/public_lit_docs_updating-tmt.md.C2pGYz0K.js deleted file mode 100644 index abd096c7..00000000 --- a/assets/public_lit_docs_updating-tmt.md.C2pGYz0K.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as t,c as e,o,a5 as a}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Updating The Modding Tree","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/updating-tmt.md","filePath":"public/lit/docs/updating-tmt.md"}'),i={name:"public/lit/docs/updating-tmt.md"},n=a('

Updating The Modding Tree ​

This tutorial assumes that you have used the Getting Started Tutorial, and are using Github Desktop and VSCode for your mod.

Here's what you have to do when there's a TMT update:

  1. Look at the changelog. It will warn you if the update will break anything or require any changes. Decide if you want to try to update.

  2. Open Github Desktop, and at the top middle, click "fetch origin". This will make Github Desktop get information about the update.

  3. Click where it says "current branch: master" at the top middle, and at the bottom of the thing that appears, click "choose a branch to merge into master".

  4. Select upstream/master. It will likely say there are conflicts, but you have tools to resolve them. Click "Merge upstream/master into master".

  5. A conflict happens when the things you're trying to merge have both made changes in the same place. Click "open in Visual Studio Code" next to the first file.

  6. Scroll down through the file, and look for the parts highlighted in red and green. One of these is your code, and the other is some code that will be modified by the update. Do your best to try to edit things to keep the updated changes, but keep your content.

  7. Continue to do this for all remaining changes.

  8. Do any other changes required by the update, run the game, fix issues, etc.

',4),r=[n];function h(d,s,l,p,u,c){return o(),e("div",null,r)}const _=t(i,[["render",h]]);export{m as __pageData,_ as default}; diff --git a/assets/public_lit_docs_updating-tmt.md.C2pGYz0K.lean.js b/assets/public_lit_docs_updating-tmt.md.C2pGYz0K.lean.js deleted file mode 100644 index 3792b9eb..00000000 --- a/assets/public_lit_docs_updating-tmt.md.C2pGYz0K.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as t,c as e,o,a5 as a}from"./chunks/framework.CK8QU5WH.js";const m=JSON.parse('{"title":"Updating The Modding Tree","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/updating-tmt.md","filePath":"public/lit/docs/updating-tmt.md"}'),i={name:"public/lit/docs/updating-tmt.md"},n=a("",4),r=[n];function h(d,s,l,p,u,c){return o(),e("div",null,r)}const _=t(i,[["render",h]]);export{m as __pageData,_ as default}; diff --git a/assets/public_lit_docs_upgrades.md.BttvCS4L.js b/assets/public_lit_docs_upgrades.md.BttvCS4L.js deleted file mode 100644 index 3be333fa..00000000 --- a/assets/public_lit_docs_upgrades.md.BttvCS4L.js +++ /dev/null @@ -1,10 +0,0 @@ -import{_ as e,c as s,o as i,a5 as a}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Upgrades","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/upgrades.md","filePath":"public/lit/docs/upgrades.md"}'),t={name:"public/lit/docs/upgrades.md"},n=a(`

Upgrades ​

Useful functions for dealing with Upgrades and implementing their effects:

  • hasUpgrade(layer, id): determine if the player has the upgrade
  • upgradeEffect(layer, id): Returns the current effects of the upgrade, if any
  • buyUpgrade(layer, id): Buys an upgrade directly (if affordable)

Hint: Basic point gain is calculated in mod.js's "getPointGen" function.

Upgrades are stored in the following format:

js
upgrades: {
-    rows: # of rows,
-    cols: # of columns,
-    11: {
-        description: "Blah",
-        cost: new Decimal(100),
-        etc
-    },
-    etc
-}

Each upgrade should have an id where the first digit is the row and the second digit is the column.

Individual upgrades can have these features:

  • title: optional. Displayed at the top in a larger font. It can also be a function that returns updating text. Can use basic HTML.

  • description: A description of the upgrade's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

  • effect(): optional. A function that calculates and returns the current values of any bonuses from the upgrade. Can return a value or an object containing multiple values.

  • effectDisplay(): optional. A function that returns a display of the current effects of the upgrade with formatting. Default displays nothing. Can use basic HTML.

  • fullDisplay(): OVERRIDE. Overrides the other displays and descriptions, and lets you set the full text for the upgrade. Can use basic HTML.

  • cost: A Decimal for the cost of the upgrade. By default, upgrades cost the main prestige currency for the layer.

  • unlocked(): optional. A function returning a bool to determine if the upgrade is visible or not. Default is unlocked.

  • onPurchase(): optional. This function will be called when the upgrade is purchased. Good for upgrades like "makes this layer act like it was unlocked first".

  • style: optional. Applies CSS to this upgrade, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

  • id: assigned automagically. It's the "key" which the upgrade was stored under, for convenient access. The upgrade in the example's id is 11.

By default, upgrades use the main prestige currency for the layer. You can include these to change them (but it needs to be a Decimal):

  • currencyDisplayName: optional. The name to display for the currency for the upgrade.

  • currencyInternalName: optional. The internal name for that currency.

  • currencyLayer: optional. The internal name of the layer that currency is stored in. If it's not in a layer (like Points), omit. If it's not stored directly in a layer, instead use the next feature.

  • currencyLocation: optional. If your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

If you want to do something more complicated like upgrades that cost two currencies, you can override the purchase system with these (and you need to use fullDisplay as well)

  • canAfford(): OVERRIDE, a function determining if you are able to buy the upgrade

  • pay(): OVERRIDE, a function that reduces your currencies when you buy the upgrade

`,13),l=[n];function r(o,p,h,u,d,c){return i(),s("div",null,l)}const k=e(t,[["render",r]]);export{y as __pageData,k as default}; diff --git a/assets/public_lit_docs_upgrades.md.BttvCS4L.lean.js b/assets/public_lit_docs_upgrades.md.BttvCS4L.lean.js deleted file mode 100644 index 403f3216..00000000 --- a/assets/public_lit_docs_upgrades.md.BttvCS4L.lean.js +++ /dev/null @@ -1 +0,0 @@ -import{_ as e,c as s,o as i,a5 as a}from"./chunks/framework.CK8QU5WH.js";const y=JSON.parse('{"title":"Upgrades","description":"","frontmatter":{},"headers":[],"relativePath":"public/lit/docs/upgrades.md","filePath":"public/lit/docs/upgrades.md"}'),t={name:"public/lit/docs/upgrades.md"},n=a("",13),l=[n];function r(o,p,h,u,d,c){return i(),s("div",null,l)}const k=e(t,[["render",r]]);export{y as __pageData,k as default}; diff --git a/changelog/atom b/changelog/atom index 66c943ec..29b9a617 100644 --- a/changelog/atom +++ b/changelog/atom @@ -2,7 +2,7 @@ https://www.thepaperpilot.org/changelog/ The Paper Pilot's Digital Garden Changelog - 2024-06-15T16:11:34.306Z + 2024-06-15T16:19:05.196Z https://github.com/jpmonette/feed The Paper Pilot @@ -169,70 +169,6 @@ incremental-social2 +- the-small-web2 +- -]]> - - - <![CDATA[ 47 files changed, 124 insertions(+), 13 deletions(-)]]> - https://code.incremental.social/thepaperpilot/pages/commit/91e757f7ccbeb570d900aaa5b49e6e4874d19b2f - - 2024-06-05T00:00:00.000Z - - - - -Page -Changes - - - -activitypub2 ++ -advent-incremental2 ++ -atproto2 ++ -babble-buds2 ++ -capture-the-citadel2 ++ -chat-glue2 ++ -chronological2 ++ -cinny2 ++ -commune2 ++ -decentralized2 ++ -dice-armor2 ++ -digital-gardens2 ++ -federated-identity2 ++ -fedi-v230 +++++++++++++++++----- -fediverse2 ++ -forgejo2 ++ -freeform-vs-chronological-dichotomy2 ++ -freeform2 ++ -game-dev-tree2 ++ -garden-rss4 ++- -.../appeal-to-developers2 ++ -guide-to-incrementals/appeal-to-players6 +++-- -guide-to-incrementals/defining-the-genre6 +++-- -guide-to-incrementals2 ++ -.../navigating-criticism2 ++ -guide-to-incrementals/what-is-content4 ++- -incremental-social2 ++ -kronos2 ++ -logseq2 ++ -matrix2 ++ -mbin2 ++ -my-personal-website2 ++ -my-projects2 ++ -nostr2 ++ -open-source2 ++ -opti-speech2 ++ -planar-pioneers2 ++ -profectus4 ++- -social-media2 ++ -synapse2 ++ -the-cozy-web2 ++ -the-small-web2 ++ -this-knowledge-hub3 +++ -v-ecs2 ++ -vitepress2 ++ -webrings2 ++ -weird2 ++ - ]]> @@ -297,6 +233,70 @@ webrings25 ++++ weird12 ++ +]]> + + + <![CDATA[ 47 files changed, 124 insertions(+), 13 deletions(-)]]> + https://code.incremental.social/thepaperpilot/pages/commit/91e757f7ccbeb570d900aaa5b49e6e4874d19b2f + + 2024-06-05T00:00:00.000Z + + + + +Page +Changes + + + +activitypub2 ++ +advent-incremental2 ++ +atproto2 ++ +babble-buds2 ++ +capture-the-citadel2 ++ +chat-glue2 ++ +chronological2 ++ +cinny2 ++ +commune2 ++ +decentralized2 ++ +dice-armor2 ++ +digital-gardens2 ++ +federated-identity2 ++ +fedi-v230 +++++++++++++++++----- +fediverse2 ++ +forgejo2 ++ +freeform-vs-chronological-dichotomy2 ++ +freeform2 ++ +game-dev-tree2 ++ +garden-rss4 ++- +.../appeal-to-developers2 ++ +guide-to-incrementals/appeal-to-players6 +++-- +guide-to-incrementals/defining-the-genre6 +++-- +guide-to-incrementals2 ++ +.../navigating-criticism2 ++ +guide-to-incrementals/what-is-content4 ++- +incremental-social2 ++ +kronos2 ++ +logseq2 ++ +matrix2 ++ +mbin2 ++ +my-personal-website2 ++ +my-projects2 ++ +nostr2 ++ +open-source2 ++ +opti-speech2 ++ +planar-pioneers2 ++ +profectus4 ++- +social-media2 ++ +synapse2 ++ +the-cozy-web2 ++ +the-small-web2 ++ +this-knowledge-hub3 +++ +v-ecs2 ++ +vitepress2 ++ +webrings2 ++ +weird2 ++ + ]]> \ No newline at end of file diff --git a/changelog/index.html b/changelog/index.html index 37e1f5ab..f384d822 100644 --- a/changelog/index.html +++ b/changelog/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
The Paper Pilot

Appearance

Changelog

This feed starts when I formatted the site to be a Digital Garden. If you'd like to look further into this site's history, check here!

20 files changed, 274 insertions(+), 16 deletions(-)

Pushed on
PageChanges
artificial-intelligence28 ++++++++++++++++
command-palettes25 ++++++++++++++
fedi-v215 +++++----
fediverse2 +-
guide-to-incrementals2 ++
incremental-social2 +-
life-is-strange60 ++++++++++++++++++++++++++++++++++
logseq2 +-
mtx13 ++++++++
my-personal-website2 +-
my-projects2 ++
pre-order-bonuses28 ++++++++++++++++
premium-currency19 +++++++++++
social-media2 +-
the-beginner-s-guide2 +-
the-indieweb/amplification14 ++++++++
the-indieweb/signature-blocks10 ++++++
the-small-web8 +++--
video-game-monetization43 ++++++++++++++++++++++++
weird11 +++++--

47 files changed, 124 insertions(+), 13 deletions(-)

Pushed on
PageChanges
activitypub2 ++
advent-incremental2 ++
atproto2 ++
babble-buds2 ++
capture-the-citadel2 ++
chat-glue2 ++
chronological2 ++
cinny2 ++
commune2 ++
decentralized2 ++
dice-armor2 ++
digital-gardens2 ++
federated-identity2 ++
fedi-v230 +++++++++++++++++-----
fediverse2 ++
forgejo2 ++
freeform-vs-chronological-dichotomy2 ++
freeform2 ++
game-dev-tree2 ++
garden-rss4 ++-
.../appeal-to-developers2 ++
guide-to-incrementals/appeal-to-players6 +++--
guide-to-incrementals/defining-the-genre6 +++--
guide-to-incrementals2 ++
.../navigating-criticism2 ++
guide-to-incrementals/what-is-content4 ++-
incremental-social2 ++
kronos2 ++
logseq2 ++
matrix2 ++
mbin2 ++
my-personal-website2 ++
my-projects2 ++
nostr2 ++
open-source2 ++
opti-speech2 ++
planar-pioneers2 ++
profectus4 ++-
social-media2 ++
synapse2 ++
the-cozy-web2 ++
the-small-web2 ++
this-knowledge-hub3 +++
v-ecs2 ++
vitepress2 ++
webrings2 ++
weird2 ++

47 files changed, 1226 insertions(+)

Pushed on
PageChanges
activitypub13 ++
advent-incremental21 +++
atproto18 +++
babble-buds22 ++++
capture-the-citadel15 +++
chat-glue12 ++
chronological21 +++
cinny10 ++
commune33 +++++
decentralized28 ++++
dice-armor55 ++++++++
digital-gardens20 +++
federated-identity23 ++++
fedi-v295 ++++++++++++++
fediverse21 +++
forgejo10 ++
freeform-vs-chronological-dichotomy10 ++
freeform17 +++
game-dev-tree17 +++
garden-rss22 ++++
.../appeal-to-developers30 +++++
guide-to-incrementals/appeal-to-players60 +++++++++
guide-to-incrementals/defining-the-genre141 +++++++++++++++++++++
guide-to-incrementals27 ++++
.../navigating-criticism26 ++++
guide-to-incrementals/what-is-content52 ++++++++
incremental-social16 +++
kronos18 +++
logseq10 ++
matrix10 ++
mbin12 ++
my-personal-website10 ++
my-projects27 ++++
nostr13 ++
open-source12 ++
opti-speech37 ++++++
planar-pioneers15 +++
profectus24 ++++
social-media25 ++++
synapse10 ++
the-cozy-web16 +++
the-small-web58 +++++++++
this-knowledge-hub22 ++++
v-ecs25 ++++
vitepress10 ++
webrings25 ++++
weird12 ++

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +
The Paper Pilot

Appearance

Changelog

This feed starts when I formatted the site to be a Digital Garden. If you'd like to look further into this site's history, check here!

20 files changed, 274 insertions(+), 16 deletions(-)

Pushed on
PageChanges
artificial-intelligence28 ++++++++++++++++
command-palettes25 ++++++++++++++
fedi-v215 +++++----
fediverse2 +-
guide-to-incrementals2 ++
incremental-social2 +-
life-is-strange60 ++++++++++++++++++++++++++++++++++
logseq2 +-
mtx13 ++++++++
my-personal-website2 +-
my-projects2 ++
pre-order-bonuses28 ++++++++++++++++
premium-currency19 +++++++++++
social-media2 +-
the-beginner-s-guide2 +-
the-indieweb/amplification14 ++++++++
the-indieweb/signature-blocks10 ++++++
the-small-web8 +++--
video-game-monetization43 ++++++++++++++++++++++++
weird11 +++++--

47 files changed, 124 insertions(+), 13 deletions(-)

Pushed on
PageChanges
activitypub2 ++
advent-incremental2 ++
atproto2 ++
babble-buds2 ++
capture-the-citadel2 ++
chat-glue2 ++
chronological2 ++
cinny2 ++
commune2 ++
decentralized2 ++
dice-armor2 ++
digital-gardens2 ++
federated-identity2 ++
fedi-v230 +++++++++++++++++-----
fediverse2 ++
forgejo2 ++
freeform-vs-chronological-dichotomy2 ++
freeform2 ++
game-dev-tree2 ++
garden-rss4 ++-
.../appeal-to-developers2 ++
guide-to-incrementals/appeal-to-players6 +++--
guide-to-incrementals/defining-the-genre6 +++--
guide-to-incrementals2 ++
.../navigating-criticism2 ++
guide-to-incrementals/what-is-content4 ++-
incremental-social2 ++
kronos2 ++
logseq2 ++
matrix2 ++
mbin2 ++
my-personal-website2 ++
my-projects2 ++
nostr2 ++
open-source2 ++
opti-speech2 ++
planar-pioneers2 ++
profectus4 ++-
social-media2 ++
synapse2 ++
the-cozy-web2 ++
the-small-web2 ++
this-knowledge-hub3 +++
v-ecs2 ++
vitepress2 ++
webrings2 ++
weird2 ++

47 files changed, 1226 insertions(+)

Pushed on
PageChanges
activitypub13 ++
advent-incremental21 +++
atproto18 +++
babble-buds22 ++++
capture-the-citadel15 +++
chat-glue12 ++
chronological21 +++
cinny10 ++
commune33 +++++
decentralized28 ++++
dice-armor55 ++++++++
digital-gardens20 +++
federated-identity23 ++++
fedi-v295 ++++++++++++++
fediverse21 +++
forgejo10 ++
freeform-vs-chronological-dichotomy10 ++
freeform17 +++
game-dev-tree17 +++
garden-rss22 ++++
.../appeal-to-developers30 +++++
guide-to-incrementals/appeal-to-players60 +++++++++
guide-to-incrementals/defining-the-genre141 +++++++++++++++++++++
guide-to-incrementals27 ++++
.../navigating-criticism26 ++++
guide-to-incrementals/what-is-content52 ++++++++
incremental-social16 +++
kronos18 +++
logseq10 ++
matrix10 ++
mbin12 ++
my-personal-website10 ++
my-projects27 ++++
nostr13 ++
open-source12 ++
opti-speech37 ++++++
planar-pioneers15 +++
profectus24 ++++
social-media25 ++++
synapse10 ++
the-cozy-web16 +++
the-small-web58 +++++++++
this-knowledge-hub22 ++++
v-ecs25 ++++
vitepress10 ++
webrings25 ++++
weird12 ++

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/changelog/json b/changelog/json index 786453aa..a65a5771 100644 --- a/changelog/json +++ b/changelog/json @@ -65,14 +65,6 @@ "summary": " 3 files changed, 3 insertions(+), 3 deletions(-)", "date_modified": "2024-06-15T00:00:00.000Z" }, - { - "id": "https://code.incremental.social/thepaperpilot/pages/commit/91e757f7ccbeb570d900aaa5b49e6e4874d19b2f", - "content_html": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
PageChanges
activitypub2 ++
advent-incremental2 ++
atproto2 ++
babble-buds2 ++
capture-the-citadel2 ++
chat-glue2 ++
chronological2 ++
cinny2 ++
commune2 ++
decentralized2 ++
dice-armor2 ++
digital-gardens2 ++
federated-identity2 ++
fedi-v230 +++++++++++++++++-----
fediverse2 ++
forgejo2 ++
freeform-vs-chronological-dichotomy2 ++
freeform2 ++
game-dev-tree2 ++
garden-rss4 ++-
.../appeal-to-developers2 ++
guide-to-incrementals/appeal-to-players6 +++--
guide-to-incrementals/defining-the-genre6 +++--
guide-to-incrementals2 ++
.../navigating-criticism2 ++
guide-to-incrementals/what-is-content4 ++-
incremental-social2 ++
kronos2 ++
logseq2 ++
matrix2 ++
mbin2 ++
my-personal-website2 ++
my-projects2 ++
nostr2 ++
open-source2 ++
opti-speech2 ++
planar-pioneers2 ++
profectus4 ++-
social-media2 ++
synapse2 ++
the-cozy-web2 ++
the-small-web2 ++
this-knowledge-hub3 +++
v-ecs2 ++
vitepress2 ++
webrings2 ++
weird2 ++
", - "url": "https://code.incremental.social/thepaperpilot/pages/commit/91e757f7ccbeb570d900aaa5b49e6e4874d19b2f", - "title": " 47 files changed, 124 insertions(+), 13 deletions(-)", - "summary": " 47 files changed, 124 insertions(+), 13 deletions(-)", - "date_modified": "2024-06-05T00:00:00.000Z" - }, { "id": "https://code.incremental.social/thepaperpilot/pages/commit/fe175090d3fc0cfa81754ec5b19a184005e31d8c", "content_html": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
PageChanges
activitypub13 ++
advent-incremental21 +++
atproto18 +++
babble-buds22 ++++
capture-the-citadel15 +++
chat-glue12 ++
chronological21 +++
cinny10 ++
commune33 +++++
decentralized28 ++++
dice-armor55 ++++++++
digital-gardens20 +++
federated-identity23 ++++
fedi-v295 ++++++++++++++
fediverse21 +++
forgejo10 ++
freeform-vs-chronological-dichotomy10 ++
freeform17 +++
game-dev-tree17 +++
garden-rss22 ++++
.../appeal-to-developers30 +++++
guide-to-incrementals/appeal-to-players60 +++++++++
guide-to-incrementals/defining-the-genre141 +++++++++++++++++++++
guide-to-incrementals27 ++++
.../navigating-criticism26 ++++
guide-to-incrementals/what-is-content52 ++++++++
incremental-social16 +++
kronos18 +++
logseq10 ++
matrix10 ++
mbin12 ++
my-personal-website10 ++
my-projects27 ++++
nostr13 ++
open-source12 ++
opti-speech37 ++++++
planar-pioneers15 +++
profectus24 ++++
social-media25 ++++
synapse10 ++
the-cozy-web16 +++
the-small-web58 +++++++++
this-knowledge-hub22 ++++
v-ecs25 ++++
vitepress10 ++
webrings25 ++++
weird12 ++
", @@ -80,6 +72,14 @@ "title": " 47 files changed, 1226 insertions(+)", "summary": " 47 files changed, 1226 insertions(+)", "date_modified": "2024-06-03T00:00:00.000Z" + }, + { + "id": "https://code.incremental.social/thepaperpilot/pages/commit/91e757f7ccbeb570d900aaa5b49e6e4874d19b2f", + "content_html": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
PageChanges
activitypub2 ++
advent-incremental2 ++
atproto2 ++
babble-buds2 ++
capture-the-citadel2 ++
chat-glue2 ++
chronological2 ++
cinny2 ++
commune2 ++
decentralized2 ++
dice-armor2 ++
digital-gardens2 ++
federated-identity2 ++
fedi-v230 +++++++++++++++++-----
fediverse2 ++
forgejo2 ++
freeform-vs-chronological-dichotomy2 ++
freeform2 ++
game-dev-tree2 ++
garden-rss4 ++-
.../appeal-to-developers2 ++
guide-to-incrementals/appeal-to-players6 +++--
guide-to-incrementals/defining-the-genre6 +++--
guide-to-incrementals2 ++
.../navigating-criticism2 ++
guide-to-incrementals/what-is-content4 ++-
incremental-social2 ++
kronos2 ++
logseq2 ++
matrix2 ++
mbin2 ++
my-personal-website2 ++
my-projects2 ++
nostr2 ++
open-source2 ++
opti-speech2 ++
planar-pioneers2 ++
profectus4 ++-
social-media2 ++
synapse2 ++
the-cozy-web2 ++
the-small-web2 ++
this-knowledge-hub3 +++
v-ecs2 ++
vitepress2 ++
webrings2 ++
weird2 ++
", + "url": "https://code.incremental.social/thepaperpilot/pages/commit/91e757f7ccbeb570d900aaa5b49e6e4874d19b2f", + "title": " 47 files changed, 124 insertions(+), 13 deletions(-)", + "summary": " 47 files changed, 124 insertions(+), 13 deletions(-)", + "date_modified": "2024-06-05T00:00:00.000Z" } ] } \ No newline at end of file diff --git a/changelog/rss b/changelog/rss index dfbf8aa6..d0ba224d 100644 --- a/changelog/rss +++ b/changelog/rss @@ -4,7 +4,7 @@ The Paper Pilot's Digital Garden Changelog https://www.thepaperpilot.org/changelog/ A feed of updates made to my digital garden! - Sat, 15 Jun 2024 16:11:34 GMT + Sat, 15 Jun 2024 16:19:05 GMT https://validator.w3.org/feed/docs/rss2.html https://github.com/jpmonette/feed en @@ -166,70 +166,6 @@ incremental-social2 +- the-small-web2 +- -]]> - - - <![CDATA[ 47 files changed, 124 insertions(+), 13 deletions(-)]]> - https://code.incremental.social/thepaperpilot/pages/commit/91e757f7ccbeb570d900aaa5b49e6e4874d19b2f - https://code.incremental.social/thepaperpilot/pages/commit/91e757f7ccbeb570d900aaa5b49e6e4874d19b2f - Wed, 05 Jun 2024 00:00:00 GMT - - - - -Page -Changes - - - -activitypub2 ++ -advent-incremental2 ++ -atproto2 ++ -babble-buds2 ++ -capture-the-citadel2 ++ -chat-glue2 ++ -chronological2 ++ -cinny2 ++ -commune2 ++ -decentralized2 ++ -dice-armor2 ++ -digital-gardens2 ++ -federated-identity2 ++ -fedi-v230 +++++++++++++++++----- -fediverse2 ++ -forgejo2 ++ -freeform-vs-chronological-dichotomy2 ++ -freeform2 ++ -game-dev-tree2 ++ -garden-rss4 ++- -.../appeal-to-developers2 ++ -guide-to-incrementals/appeal-to-players6 +++-- -guide-to-incrementals/defining-the-genre6 +++-- -guide-to-incrementals2 ++ -.../navigating-criticism2 ++ -guide-to-incrementals/what-is-content4 ++- -incremental-social2 ++ -kronos2 ++ -logseq2 ++ -matrix2 ++ -mbin2 ++ -my-personal-website2 ++ -my-projects2 ++ -nostr2 ++ -open-source2 ++ -opti-speech2 ++ -planar-pioneers2 ++ -profectus4 ++- -social-media2 ++ -synapse2 ++ -the-cozy-web2 ++ -the-small-web2 ++ -this-knowledge-hub3 +++ -v-ecs2 ++ -vitepress2 ++ -webrings2 ++ -weird2 ++ - ]]> @@ -294,6 +230,70 @@ webrings25 ++++ weird12 ++ +]]> + + + <![CDATA[ 47 files changed, 124 insertions(+), 13 deletions(-)]]> + https://code.incremental.social/thepaperpilot/pages/commit/91e757f7ccbeb570d900aaa5b49e6e4874d19b2f + https://code.incremental.social/thepaperpilot/pages/commit/91e757f7ccbeb570d900aaa5b49e6e4874d19b2f + Wed, 05 Jun 2024 00:00:00 GMT + + + + +Page +Changes + + + +activitypub2 ++ +advent-incremental2 ++ +atproto2 ++ +babble-buds2 ++ +capture-the-citadel2 ++ +chat-glue2 ++ +chronological2 ++ +cinny2 ++ +commune2 ++ +decentralized2 ++ +dice-armor2 ++ +digital-gardens2 ++ +federated-identity2 ++ +fedi-v230 +++++++++++++++++----- +fediverse2 ++ +forgejo2 ++ +freeform-vs-chronological-dichotomy2 ++ +freeform2 ++ +game-dev-tree2 ++ +garden-rss4 ++- +.../appeal-to-developers2 ++ +guide-to-incrementals/appeal-to-players6 +++-- +guide-to-incrementals/defining-the-genre6 +++-- +guide-to-incrementals2 ++ +.../navigating-criticism2 ++ +guide-to-incrementals/what-is-content4 ++- +incremental-social2 ++ +kronos2 ++ +logseq2 ++ +matrix2 ++ +mbin2 ++ +my-personal-website2 ++ +my-projects2 ++ +nostr2 ++ +open-source2 ++ +opti-speech2 ++ +planar-pioneers2 ++ +profectus4 ++- +social-media2 ++ +synapse2 ++ +the-cozy-web2 ++ +the-small-web2 ++ +this-knowledge-hub3 +++ +v-ecs2 ++ +vitepress2 ++ +webrings2 ++ +weird2 ++ + ]]> diff --git a/garden/activitypub/index.html b/garden/activitypub/index.html index af8d5dcb..b78700db 100644 --- a/garden/activitypub/index.html +++ b/garden/activitypub/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Fediverse

Tags: Decentralized

ActivityPub is a protocol for Federated Social Media

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/advent-incremental/index.html b/garden/advent-incremental/index.html index 1de9e076..aae8af9c 100644 --- a/garden/advent-incremental/index.html +++ b/garden/advent-incremental/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Advent Incremental ​

203 words, ~1 minute read. Planted . Last tended to -.

Tags: My Projects, Profectus

Play it here!

An Open Source game made in Profectus over the course of 1 month by myself and other devs I know in the Incremental Games community!

I had the idea of an advent-style game that unlocked new pieces of content every real-life day a couple days before December started.

This was one of the most hectic months of my life!

I'm super happy with how it turned out. It ended up being way more ambitious than I anticipated but the end result is super large and awesome!

The TV Tropes page on this game mentions some of the cool things about this game

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Tags: My Projects, Profectus

Play it here!

An Open Source game made in Profectus over the course of 1 month by myself and other devs I know in the Incremental Games community!

I had the idea of an advent-style game that unlocked new pieces of content every real-life day a couple days before December started.

This was one of the most hectic months of my life!

I'm super happy with how it turned out. It ended up being way more ambitious than I anticipated but the end result is super large and awesome!

The TV Tropes page on this game mentions some of the cool things about this game

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/artificial-intelligence/index.html b/garden/artificial-intelligence/index.html index 1ef9ce40..176bd524 100644 --- a/garden/artificial-intelligence/index.html +++ b/garden/artificial-intelligence/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,8 +22,8 @@
The Paper Pilot

Appearance

Artificial Intelligence ​

201 words, ~1 minute read. Planted -.

Referenced by: Command Palettes

Catch all term that refers to many different things

Generative AI

  • Models trained on large amounts of existing human made content in order to produce more of that content
  • Copyright concerns over how training data is obtained
  • Common Examples

Human + AI cooperation

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Command Palettes

Catch all term that refers to many different things

Generative AI

  • Models trained on large amounts of existing human made content in order to produce more of that content
  • Copyright concerns over how training data is obtained
  • Common Examples

Human + AI cooperation

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/atproto/index.html b/garden/atproto/index.html index 5a42a232..11c2bcfd 100644 --- a/garden/atproto/index.html +++ b/garden/atproto/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Fediverse

Tags: Decentralized

The AT Protocol is a protocol for Federated Social Media

Currently only used by Bluesky

In comparison to other Fediverse protocols, ATProto is designed for a small number of large instances

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/babble-buds/index.html b/garden/babble-buds/index.html index c12eddd5..792aa079 100644 --- a/garden/babble-buds/index.html +++ b/garden/babble-buds/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Babble Buds ​

207 words, ~1 minute read. Planted . Last tended to -.

Tags: My Projects

Babble Buds is a tool for creating puppets and interacting with puppets controlled by others on a shared stage

Note: I need to move the website off replit because of their monetization strategy changing. In the meantime, you can check it out from its github repository

Inspired by Puppet Pals by Robert Moran

Intended for use in RPG Campaigns

The renderer was separated into its own project, babble.js, so it could be used for stuff like cutscenes

I ported the engine to C# and used it for the cutscenes in Dice Armor

  • I don't believe I ever separated it out into its own project, but you can find the code here
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Tags: My Projects

Babble Buds is a tool for creating puppets and interacting with puppets controlled by others on a shared stage

Note: I need to move the website off replit because of their monetization strategy changing. In the meantime, you can check it out from its github repository

Inspired by Puppet Pals by Robert Moran

Intended for use in RPG Campaigns

The renderer was separated into its own project, babble.js, so it could be used for stuff like cutscenes

I ported the engine to C# and used it for the cutscenes in Dice Armor

  • I don't believe I ever separated it out into its own project, but you can find the code here
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/capture-the-citadel/index.html b/garden/capture-the-citadel/index.html index 0c60fb22..90fbb8ed 100644 --- a/garden/capture-the-citadel/index.html +++ b/garden/capture-the-citadel/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Capture the Citadel ​

132 words, ~1 minute read. Planted . Last tended to -.

Tags: My Projects

A 3D VR re-envisioning of a Slay the Spire-style game by Anthony Lawn and Grant Barbee for their VR class in college's final project.

For more details, visit Grant's page on the game.

screenshot.png

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Tags: My Projects

A 3D VR re-envisioning of a Slay the Spire-style game by Anthony Lawn and Grant Barbee for their VR class in college's final project.

For more details, visit Grant's page on the game.

screenshot.png

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/chat-glue/index.html b/garden/chat-glue/index.html index e85cd469..4135d3ed 100644 --- a/garden/chat-glue/index.html +++ b/garden/chat-glue/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,9 +22,9 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +. Last tended to +.

Referenced by: Commune, The Small Web

A theoretical chat system designed to solve the problems of transcribing branching conversations into linear timelines.

Defined by the Chatting with Glue comic.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/chronological/index.html b/garden/chronological/index.html index 3d8adfa2..a376a90b 100644 --- a/garden/chronological/index.html +++ b/garden/chronological/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Chronological ​

174 words, ~1 minute read. Planted . Last tended to -.

Referenced by: Digital Gardens, Freeform vs Chronological Dichotomy, The Small Web

A collection of information that is tied to its creation or edit date

Part of the Freeform vs Chronological Dichotomy

Anything with a "timeline" or "feed" is considered chronological

  • Even if there's algorithmic sortings that take things other than creation or edit date into account!

Chronological displays are less suitable as stores of knowledge (Digital Gardens)

Social media overuses timelines and feeds

RSS feeds work really well with this form of content

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Digital Gardens, Freeform vs Chronological Dichotomy, The Small Web

A collection of information that is tied to its creation or edit date

Part of the Freeform vs Chronological Dichotomy

Anything with a "timeline" or "feed" is considered chronological

  • Even if there's algorithmic sortings that take things other than creation or edit date into account!

Chronological displays are less suitable as stores of knowledge (Digital Gardens)

Social media overuses timelines and feeds

RSS feeds work really well with this form of content

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/cinny/index.html b/garden/cinny/index.html index c1b310de..9c627e4d 100644 --- a/garden/cinny/index.html +++ b/garden/cinny/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Incremental Social

Cinny is an Open Source web client for the Matrix messaging protocol

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/command-palettes/index.html b/garden/command-palettes/index.html index 2479cdb4..14d505ba 100644 --- a/garden/command-palettes/index.html +++ b/garden/command-palettes/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,8 +22,8 @@
The Paper Pilot

Appearance

Command Palettes ​

208 words, ~1 minute read. Planted -.

Command palettes are a design pattern where apps expose functionality through a search bar

Typing what you want is almost certainly easier and faster than finding the action in some submenu or remembering an arcane hotkey

  • Especially with fuzzy search that also looks through descriptions of actions
  • Command palettes scale very well with large amounts of actions

Artificial Intelligence will make command palettes increasingly powerful

  • Eventually these may become conversational interfaces

Maggie Appleton discusses this pattern in her article on Command K Bars

  • The name comes from the fact many apps use the ctrl/cmd k shortcut to open the command palette

Many softwares I use have some form of command palette

  • Linear
  • Logseq
  • Visual Studio Code
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Command palettes are a design pattern where apps expose functionality through a search bar

Typing what you want is almost certainly easier and faster than finding the action in some submenu or remembering an arcane hotkey

  • Especially with fuzzy search that also looks through descriptions of actions
  • Command palettes scale very well with large amounts of actions

Artificial Intelligence will make command palettes increasingly powerful

  • Eventually these may become conversational interfaces

Maggie Appleton discusses this pattern in her article on Command K Bars

  • The name comes from the fact many apps use the ctrl/cmd k shortcut to open the command palette

Many softwares I use have some form of command palette

  • Linear
  • Logseq
  • Visual Studio Code
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/commune/index.html b/garden/commune/index.html index dbe032ca..3868be81 100644 --- a/garden/commune/index.html +++ b/garden/commune/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,9 +22,9 @@
The Paper Pilot

Appearance

Commune ​

275 words, ~2 minute read. Planted -. Last tended to -.

Referenced by: Federated Identity, Fedi v2, /now, Webrings, Weird

An Open Source Matrix web client built to be better for communities than anything else out there

  • Currently in development
  • Exposes certain channels such that they are web indexable
  • Will include features like Chat Glue and communal Digital Gardens

Created by Erlend Sogge Heggen, a ex-employee from Discourse

  • Maintains the Commune Blog with great write ups on the issues of the modern web, social media, etc. and how they can be improved (by Commune or related projects)
  • Also maintains a Personal Blog about similar topics

The Commune community is very interested in various topics and how they can relate together:

Related projects:

  • @laxla@tech.lgbt is creating Gimli, a federated discord alternative
    • Built on ActivityPub
    • "Guild-based" in ways matrix is not?
    • Will integrate with F3 as well
    • Wants to handle blogging as well
    • Certainly seems similar to Commune's message gardening concept
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +. Last tended to +.

Referenced by: Federated Identity, Fedi v2, /now, Webrings, Weird

An Open Source Matrix web client built to be better for communities than anything else out there

  • Currently in development
  • Exposes certain channels such that they are web indexable
  • Will include features like Chat Glue and communal Digital Gardens

Created by Erlend Sogge Heggen, a ex-employee from Discourse

  • Maintains the Commune Blog with great write ups on the issues of the modern web, social media, etc. and how they can be improved (by Commune or related projects)
  • Also maintains a Personal Blog about similar topics

The Commune community is very interested in various topics and how they can relate together:

Related projects:

  • @laxla@tech.lgbt is creating Gimli, a federated discord alternative
    • Built on ActivityPub
    • "Guild-based" in ways matrix is not?
    • Will integrate with F3 as well
    • Wants to handle blogging as well
    • Certainly seems similar to Commune's message gardening concept
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/davey-wreden/index.html b/garden/davey-wreden/index.html index 113367bf..8bd16fa9 100644 --- a/garden/davey-wreden/index.html +++ b/garden/davey-wreden/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,8 +22,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Ivy Road, The Beginner's Guide

Tagged by: Ivy Road, The Beginner's Guide, Wanderstop

Projects:

Talks and Interviews:

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/decentralized/index.html b/garden/decentralized/index.html index 8c9a00c5..f759e265 100644 --- a/garden/decentralized/index.html +++ b/garden/decentralized/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Decentralized ​

186 words, ~1 minute read. Planted . Last tended to -.

Referenced by: Commune, Fedi v2, Matrix, Social Media

Tagged by: ATProto, ActivityPub, Federated Identity, Fediverse, Nostr

Something with no central source of authority

Common examples:

In practice, the "pick a server" problem causes email and the fediverse to trend towards a handful of large servers that still suffer from some of the issues of centralization

Advantages over centralization:

  • Data ownership
  • Increased privacy
  • No rules to follow
  • Can fully customize your experience
  • No single entity can make the experience worse for everyone
  • Anyone and everyone can try their hand at improving the ecosystem
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Commune, Fedi v2, Matrix, Social Media

Tagged by: ATProto, ActivityPub, Federated Identity, Fediverse, Nostr

Something with no central source of authority

Common examples:

In practice, the "pick a server" problem causes email and the fediverse to trend towards a handful of large servers that still suffer from some of the issues of centralization

Advantages over centralization:

  • Data ownership
  • Increased privacy
  • No rules to follow
  • Can fully customize your experience
  • No single entity can make the experience worse for everyone
  • Anyone and everyone can try their hand at improving the ecosystem
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/dice-armor/index.html b/garden/dice-armor/index.html index 95f312d3..aaf7933b 100644 --- a/garden/dice-armor/index.html +++ b/garden/dice-armor/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Dice Armor ​

1052 words, ~6 minute read. Planted . Last tended to -.

Referenced by: Babble Buds

Tags: My Projects

Download it here

Dice Armor is a game that started development as a semester-long project by a team of nine: a producer, a creative director, a narrative writer, an artist, two programmers, and 3 game designers. The information here is about my contributions as the lead programmer over the semester because I can show off stuff like the editor scripts I wrote. I was doing everything from interface coding, editor scripts, integrating Babble Buds, and of course, everything related to the gameplay itself. To date I'm still the lead programmer for the game; for more up-to-date information on the current state of the game please visit the official site.

The build available here was created for showing off at the end of the semester, and as such has some buttons present to make the game easier to skip parts of the game to see all the content: You start with all the dice in the game already in the shop, there's a button to give yourself free money to buy these dice with, and in the duel, there are buttons to force a win or a loss, which can be used to skip the tutorial (not recommended for first-time players).

Tutorial

Dice Armor is a dice dueling game. Players can use abilities, flip dice, and attack each other to win in a dice game that puts chance into the hands of the players. This is what the dueling scene looks like, with a tutorial cutscene happening on top to guide the player through the basics. Also, all the dice are constructed dynamically, using quaternion math to figure out the placement of each component relative to the face it is going on. The die in the middle has one of the player' and opponents' portraits on each of its sides.

Editors

For many of the objects I've created, I've made scriptable objects so that game designers can add and modify them easily. Additionally, I would create custom inspectors for the objects to help make them as easy to understand and edit as possible. The opponent's artificial intelligence is made up of many strategies, in a prioritized list. When it is the opponents' turn they go through each strategy and check if they can be run, and if so then the opponent performs the strategy and starts back over at the top of the list of strategies. The + sign under the list of strategies opens an organized dropdown of all the various strategies.

Simulator

In addition to custom inspector code, I've created new tools for the editor for our game designers to use. This is a duel simulator that will take two opponents and simulate an arbitrary number of duels between them, and output the results and summarize them for you, much much quicker than manually going through the duels, even with an absurdly high timeScale. This will become incredibly useful in making balance changes and testing new dice against existing sets. This is a screenshot of it in edit mode, but in play mode it removes the "Dueling Managers" field and will use whatever the current duel balance settings are, allowing for the GDs to test freely in play mode without worrying about undoing all their changes afterward.

da1.png

I created the Babble Buds puppet editor and ported the rendering library I wrote for it to C# so it could be used in Unity. Dice Armor has a full campaign using cutscenes made using the Babble Buds cutscene editor, taking advantage of its support for custom commands and fields to control things like talking, giving the player dice and money, starting duels, and controlling player progression through the story.

Action Wheel

When a cutscene ends, its final command is to either start a duel or set the next cutscene in the story. In the latter case, there is an additional field for what to call the next cutscene, and what location it takes place. The cutscene is then added to the player's save file, and when they visit the city locations are greyed out until they have at least one action to do there. Each location has a dynamically populated action wheel with a custom range of acceptable angles.

Shop

The dice shop is dynamically populated by a list of dice available to the player, which can be changed during cutscenes, and is checked against the dice owned by the player to generate sold-out indicators. On the left, the player can choose to filter the options down to a single dice effect, which also updates the "Buy All" button to buy only all the dice in the current filter.

Inventory

The inventory works most the same as the shop, but for equipping dice. It also allows you to drag individual dice or entire sets to the equipped dice glyph. While dragging it will highlight all the slots the new dice will be equipped into.

Dice Rolling

The dice rolling uses the physics engine and detects once the dice have stopped moving, then determines which side is face up based on which of the normals is closest to straight up. It flags the die as cocked if that smallest angle is above a threshold. The dice sink into the table when not rolling to not interfere with any dice that are rolling.

Missile Storm

During certain events like winning the game or having the face of a die broken, the players' portraits will flash an emotion for a second. After winning, a random living die from the winning player is chosen to play their "finisher move", a flashy and dramatic effect to end the game. Shown is the arcane mechana's finisher, "Missile Storm".

After development stopped, the project became Open Source - check it out here

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Babble Buds

Tags: My Projects

Download it here

Dice Armor is a game that started development as a semester-long project by a team of nine: a producer, a creative director, a narrative writer, an artist, two programmers, and 3 game designers. The information here is about my contributions as the lead programmer over the semester because I can show off stuff like the editor scripts I wrote. I was doing everything from interface coding, editor scripts, integrating Babble Buds, and of course, everything related to the gameplay itself. To date I'm still the lead programmer for the game; for more up-to-date information on the current state of the game please visit the official site.

The build available here was created for showing off at the end of the semester, and as such has some buttons present to make the game easier to skip parts of the game to see all the content: You start with all the dice in the game already in the shop, there's a button to give yourself free money to buy these dice with, and in the duel, there are buttons to force a win or a loss, which can be used to skip the tutorial (not recommended for first-time players).

Tutorial

Dice Armor is a dice dueling game. Players can use abilities, flip dice, and attack each other to win in a dice game that puts chance into the hands of the players. This is what the dueling scene looks like, with a tutorial cutscene happening on top to guide the player through the basics. Also, all the dice are constructed dynamically, using quaternion math to figure out the placement of each component relative to the face it is going on. The die in the middle has one of the player' and opponents' portraits on each of its sides.

Editors

For many of the objects I've created, I've made scriptable objects so that game designers can add and modify them easily. Additionally, I would create custom inspectors for the objects to help make them as easy to understand and edit as possible. The opponent's artificial intelligence is made up of many strategies, in a prioritized list. When it is the opponents' turn they go through each strategy and check if they can be run, and if so then the opponent performs the strategy and starts back over at the top of the list of strategies. The + sign under the list of strategies opens an organized dropdown of all the various strategies.

Simulator

In addition to custom inspector code, I've created new tools for the editor for our game designers to use. This is a duel simulator that will take two opponents and simulate an arbitrary number of duels between them, and output the results and summarize them for you, much much quicker than manually going through the duels, even with an absurdly high timeScale. This will become incredibly useful in making balance changes and testing new dice against existing sets. This is a screenshot of it in edit mode, but in play mode it removes the "Dueling Managers" field and will use whatever the current duel balance settings are, allowing for the GDs to test freely in play mode without worrying about undoing all their changes afterward.

da1.png

I created the Babble Buds puppet editor and ported the rendering library I wrote for it to C# so it could be used in Unity. Dice Armor has a full campaign using cutscenes made using the Babble Buds cutscene editor, taking advantage of its support for custom commands and fields to control things like talking, giving the player dice and money, starting duels, and controlling player progression through the story.

Action Wheel

When a cutscene ends, its final command is to either start a duel or set the next cutscene in the story. In the latter case, there is an additional field for what to call the next cutscene, and what location it takes place. The cutscene is then added to the player's save file, and when they visit the city locations are greyed out until they have at least one action to do there. Each location has a dynamically populated action wheel with a custom range of acceptable angles.

Shop

The dice shop is dynamically populated by a list of dice available to the player, which can be changed during cutscenes, and is checked against the dice owned by the player to generate sold-out indicators. On the left, the player can choose to filter the options down to a single dice effect, which also updates the "Buy All" button to buy only all the dice in the current filter.

Inventory

The inventory works most the same as the shop, but for equipping dice. It also allows you to drag individual dice or entire sets to the equipped dice glyph. While dragging it will highlight all the slots the new dice will be equipped into.

Dice Rolling

The dice rolling uses the physics engine and detects once the dice have stopped moving, then determines which side is face up based on which of the normals is closest to straight up. It flags the die as cocked if that smallest angle is above a threshold. The dice sink into the table when not rolling to not interfere with any dice that are rolling.

Missile Storm

During certain events like winning the game or having the face of a die broken, the players' portraits will flash an emotion for a second. After winning, a random living die from the winning player is chosen to play their "finisher move", a flashy and dramatic effect to end the game. Shown is the arcane mechana's finisher, "Missile Storm".

After development stopped, the project became Open Source - check it out here

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/digital-gardens/index.html b/garden/digital-gardens/index.html index 6b54d6bf..ff46d323 100644 --- a/garden/digital-gardens/index.html +++ b/garden/digital-gardens/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Digital Gardens ​

166 words, ~1 minute read. Planted . Last tended to -.

Referenced by: Chronological, Commune, Garden-RSS, The Cozy Web, The Small Web

Digital Gardens are Freeform collections of information made by an individual or community

This Knowledge Hub

Collections of digital gardens and resources for creating them:

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Chronological, Commune, Garden-RSS, The Cozy Web, The Small Web

Digital Gardens are Freeform collections of information made by an individual or community

This Knowledge Hub

Collections of digital gardens and resources for creating them:

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/federated-identity/index.html b/garden/federated-identity/index.html index 5954be99..dfba0923 100644 --- a/garden/federated-identity/index.html +++ b/garden/federated-identity/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Federated Identity ​

170 words, ~1 minute read. Planted . Last tended to -.

Referenced by: Commune, Fedi v2, Weird

Tags: Decentralized

Allow for validating one's identity without relying on a specific centralized server

Implementations:

Self hosted identity providers are NOT enough to be considered federated identity

  • OIDC and OAuth require the service owner to have pre-configured with explicitly allowed identity providers

Incremental Social uses Zitadel which does NOT support IndieAuth and probably won't

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Commune, Fedi v2, Weird

Tags: Decentralized

Allow for validating one's identity without relying on a specific centralized server

Implementations:

Self hosted identity providers are NOT enough to be considered federated identity

  • OIDC and OAuth require the service owner to have pre-configured with explicitly allowed identity providers

Incremental Social uses Zitadel which does NOT support IndieAuth and probably won't

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/fedi-v2/index.html b/garden/fedi-v2/index.html index ae8db0ae..fd8ecd92 100644 --- a/garden/fedi-v2/index.html +++ b/garden/fedi-v2/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,9 +22,9 @@
The Paper Pilot

Appearance

Fedi v2 ​

1370 words, ~7 minute read. Planted -. Last tended to -.

Referenced by: Social Media, Weird

A placeholder name for a theoretical new federated network that is client-centric, in contrast to the server-centric Fediverse

There are further discussions about actually implementing all this within the Weird community

Inspiration ​

  • A Plan for Social Media - Rethinking Federation
    • This article doesn't address many implementation details:
      • If the server is a relay, can content not be viewed anonymously?
      • How to handle storing large amounts of data on every client?
      • Don't you still need to associate with a server for people to direct their messages to?
  • Single-user Mastodon Instance is a Bad Idea
    • Focuses on the non-feasibility of self hosting, contributing to Federated Social Media not actually having all the upsides it should theoretically have by virtue of being Decentralized
  • The Commune community
  • Existing protocols:
    • Nostr
      • Currently suffers a culture problem by being associated with alt right and crypto users, making broad adoption more difficult
    • ATProto
      • Focused on a few large instances, to be run by large corporations. Still requires associating your identity with a server you don't own
  • A lot of these ideas are learned lessons from the usenet days

Identity ​

  • Federated Identity
  • Private and public keys anyone can create and store how they want
    • Fully free to create and store with no server dependencies
  • Profile information
    • Sent as a signed message through all the relays
    • How would you trust a username?
      • Petnames could be used to display human readable names via contacts or decentralized "naming hubs"
      • In most conversations online, you can trust their display name and add them as a contact as that display name
        • You only need to verify they are the same person you interacted with previously
        • You only need to trust people you want to send money to or otherwise "important identities"
        • For important identities, you can trust your contacts forming a chain of trust, or a authoritative naming hub
          • E.g. a white house ran naming hub that verifies the identities of the president and people of Congress
          • People typically wouldn't reach out to a naming hub, as it's not typically necessary
        • Contacts supercede naming hubs, so if a naming hub is breached, anyone I've previously added as a contact is still the source of truth
          • This only fails if the private key itself was breached
        • I'm just thepaperpilot, my display name. For most online communication, this is sufficient
          • My website can have a nameserver saying this publickey is the same as the site owner
          • If I write a paper at a scientific journal, they can say the author of x paper is my publickey
  • How to handle losing your private key
    • If you do have a naming hub you can verify with, they can say the identity has a new publickey
    • Contacts can "vouch" for a identity having a new publickey
    • Clients can decide to trust the new publickey based on contacts and naming hubs saying to
    • Also applies to stolen or compromised keys

Servers ​

  • Act as relays, merely storing messages and sending them to any clients or servers that have subscribed
  • May decide to publicly display messages its received
    • These servers are how discovery would work
    • Different servers may offer unique displays, filters, etc.
  • Users can send their content to any server - no authentication or account required, as the identity suffices
    • Even replies can work this way - no need to know from where a given message originated
  • Private servers could require some password when sending messages or subscribing to things
    • Useful for a school or other entity that wants an internal social network
  • Different ways to subscribe to a server's messages
    • All messages the relay hears about (new relays essentially subscribe like this to some existing relay)
    • All messages from a specific poster ID
    • Any replies to a message created with a specific poster ID
    • Shallow subscriptions, to lighten the load when subscribing to communities

Content ​

  • Protocol should dictate how to convey text, image, audio, video, and binary content
  • Protocol should include reacting to content with arbitrary text, including a URL
    • Upvotes and downvotes are implemented with this system
  • Each message contains fields for the poster's ID (public key) and a signature that verifies the content was made by that poster
    • That signature serves as an ID for the message itself
      • Anything can be replied to using the ID as the "parent" property in a new post
  • Edits are handled as replies with some flag to indicate it's updating the parent messages' content
    • Naturally, this reply would only be respected if it matches the same creator ID
    • Servers should replace the original message entirely with this one and indicate its an edited message
      • Some servers will inevitably keep a full history though
  • Groups/communities are just specially flagged messages
    • Posting to a community is just replying to that message
    • Subscribing to a community is just subscribing to that message
    • The original message creator effectively owns the group
  • IndieWeb pages could publish these messages as well, effectively serving as clients within the network
    • Perhaps use a bit to actually send those messages to other relays within the network

Moderation ​

  • In general, edits and delete requests are made by replying with a specially flagged message
  • Edit and deletion messages are ignored unless they have the correct public key and signature
    • Parent messages form a hierarchy of permission - if someone replies to your message, you can send a delete request for that message
    • Relay owners cannot fully delete messages, but can choose to stop relaying replies etc. of messages as the server owner wishes
  • Posts can be publicly reported with a specially flagged reply
    • How to make anonymous reports?
  • Users can send deletion or edit messages even without a matching public key, and clients (or relays) can choose to respect those messages if that public key is whitelisted as a moderator
    • Messages (and by extension, groups) can have replies granting or removing permission to other public IDs at that hierarchy level
    • People can setup accounts with their desired heuristic for sending delete messages, such as looking at public reports or analyzing the content with AI
      • This way clients can effectively customize their preferred moderation
  • Clients can also choose to add additional rules for hiding content, such as any reports by followed users
  • Perhaps delete messages pull double duty as public reports in and of themselves?

Problems to solve ​

  • No anonymity
    • All upvotes, downvotes, etc. are linked to your public key
    • Perhaps a client could generate new keypairs for every action for anonymity, but then it'd be hard to determine if such an account and action was a genuine user or a bot
  • Servers could probably determine the identity of clients sending their messages to them
    • A client that only ever sends messages with a specific public key is unlikely to be a server
    • A client that doesn't subscribe to all messages is unlikely to be a server
    • Perhaps clients and servers can be identified as such, and subscribing to new messages is something you only do to servers, not clients
  • Illegal material will likely be placed on the hard drive at least temporarily
    • Messages will be downloaded and, even if you follow a moderator bot that looks for illegal material, there's likely to be a delay between receiving the initial message and receiving the bots delete message
  • You have to download all spam messages
    • For redundancy, you'd likely subscribe to multiple relay servers
    • You cannot trust several relay servers to have identical rules on not relaying messages that don't pass whatever moderation heuristic
    • Therefore, the filtering out of spam has to be done by the client, after downloading it all
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +. Last tended to +.

Referenced by: Social Media, Weird

A placeholder name for a theoretical new federated network that is client-centric, in contrast to the server-centric Fediverse

There are further discussions about actually implementing all this within the Weird community

Inspiration ​

  • A Plan for Social Media - Rethinking Federation
    • This article doesn't address many implementation details:
      • If the server is a relay, can content not be viewed anonymously?
      • How to handle storing large amounts of data on every client?
      • Don't you still need to associate with a server for people to direct their messages to?
  • Single-user Mastodon Instance is a Bad Idea
    • Focuses on the non-feasibility of self hosting, contributing to Federated Social Media not actually having all the upsides it should theoretically have by virtue of being Decentralized
  • The Commune community
  • Existing protocols:
    • Nostr
      • Currently suffers a culture problem by being associated with alt right and crypto users, making broad adoption more difficult
    • ATProto
      • Focused on a few large instances, to be run by large corporations. Still requires associating your identity with a server you don't own
  • A lot of these ideas are learned lessons from the usenet days

Identity ​

  • Federated Identity
  • Private and public keys anyone can create and store how they want
    • Fully free to create and store with no server dependencies
  • Profile information
    • Sent as a signed message through all the relays
    • How would you trust a username?
      • Petnames could be used to display human readable names via contacts or decentralized "naming hubs"
      • In most conversations online, you can trust their display name and add them as a contact as that display name
        • You only need to verify they are the same person you interacted with previously
        • You only need to trust people you want to send money to or otherwise "important identities"
        • For important identities, you can trust your contacts forming a chain of trust, or a authoritative naming hub
          • E.g. a white house ran naming hub that verifies the identities of the president and people of Congress
          • People typically wouldn't reach out to a naming hub, as it's not typically necessary
        • Contacts supercede naming hubs, so if a naming hub is breached, anyone I've previously added as a contact is still the source of truth
          • This only fails if the private key itself was breached
        • I'm just thepaperpilot, my display name. For most online communication, this is sufficient
          • My website can have a nameserver saying this publickey is the same as the site owner
          • If I write a paper at a scientific journal, they can say the author of x paper is my publickey
  • How to handle losing your private key
    • If you do have a naming hub you can verify with, they can say the identity has a new publickey
    • Contacts can "vouch" for a identity having a new publickey
    • Clients can decide to trust the new publickey based on contacts and naming hubs saying to
    • Also applies to stolen or compromised keys

Servers ​

  • Act as relays, merely storing messages and sending them to any clients or servers that have subscribed
  • May decide to publicly display messages its received
    • These servers are how discovery would work
    • Different servers may offer unique displays, filters, etc.
  • Users can send their content to any server - no authentication or account required, as the identity suffices
    • Even replies can work this way - no need to know from where a given message originated
  • Private servers could require some password when sending messages or subscribing to things
    • Useful for a school or other entity that wants an internal social network
  • Different ways to subscribe to a server's messages
    • All messages the relay hears about (new relays essentially subscribe like this to some existing relay)
    • All messages from a specific poster ID
    • Any replies to a message created with a specific poster ID
    • Shallow subscriptions, to lighten the load when subscribing to communities

Content ​

  • Protocol should dictate how to convey text, image, audio, video, and binary content
  • Protocol should include reacting to content with arbitrary text, including a URL
    • Upvotes and downvotes are implemented with this system
  • Each message contains fields for the poster's ID (public key) and a signature that verifies the content was made by that poster
    • That signature serves as an ID for the message itself
      • Anything can be replied to using the ID as the "parent" property in a new post
  • Edits are handled as replies with some flag to indicate it's updating the parent messages' content
    • Naturally, this reply would only be respected if it matches the same creator ID
    • Servers should replace the original message entirely with this one and indicate its an edited message
      • Some servers will inevitably keep a full history though
  • Groups/communities are just specially flagged messages
    • Posting to a community is just replying to that message
    • Subscribing to a community is just subscribing to that message
    • The original message creator effectively owns the group
  • IndieWeb pages could publish these messages as well, effectively serving as clients within the network
    • Perhaps use a bit to actually send those messages to other relays within the network

Moderation ​

  • In general, edits and delete requests are made by replying with a specially flagged message
  • Edit and deletion messages are ignored unless they have the correct public key and signature
    • Parent messages form a hierarchy of permission - if someone replies to your message, you can send a delete request for that message
    • Relay owners cannot fully delete messages, but can choose to stop relaying replies etc. of messages as the server owner wishes
  • Posts can be publicly reported with a specially flagged reply
    • How to make anonymous reports?
  • Users can send deletion or edit messages even without a matching public key, and clients (or relays) can choose to respect those messages if that public key is whitelisted as a moderator
    • Messages (and by extension, groups) can have replies granting or removing permission to other public IDs at that hierarchy level
    • People can setup accounts with their desired heuristic for sending delete messages, such as looking at public reports or analyzing the content with AI
      • This way clients can effectively customize their preferred moderation
  • Clients can also choose to add additional rules for hiding content, such as any reports by followed users
  • Perhaps delete messages pull double duty as public reports in and of themselves?

Problems to solve ​

  • No anonymity
    • All upvotes, downvotes, etc. are linked to your public key
    • Perhaps a client could generate new keypairs for every action for anonymity, but then it'd be hard to determine if such an account and action was a genuine user or a bot
  • Servers could probably determine the identity of clients sending their messages to them
    • A client that only ever sends messages with a specific public key is unlikely to be a server
    • A client that doesn't subscribe to all messages is unlikely to be a server
    • Perhaps clients and servers can be identified as such, and subscribing to new messages is something you only do to servers, not clients
  • Illegal material will likely be placed on the hard drive at least temporarily
    • Messages will be downloaded and, even if you follow a moderator bot that looks for illegal material, there's likely to be a delay between receiving the initial message and receiving the bots delete message
  • You have to download all spam messages
    • For redundancy, you'd likely subscribe to multiple relay servers
    • You cannot trust several relay servers to have identical rules on not relaying messages that don't pass whatever moderation heuristic
    • Therefore, the filtering out of spam has to be done by the client, after downloading it all
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/fediverse/index.html b/garden/fediverse/index.html index 6e2915ab..39d1d90d 100644 --- a/garden/fediverse/index.html +++ b/garden/fediverse/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: ATProto, Decentralized, Fedi v2, Incremental Social, Mbin, Weird

Tags: Decentralized

A collection of Social Media websites that can all talk to each other by virtue of a shared protocol

Typically refers to sites implementing ActivityPub

Implementations:

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/forgejo/index.html b/garden/forgejo/index.html index 0c3514fe..e9127b16 100644 --- a/garden/forgejo/index.html +++ b/garden/forgejo/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Incremental Social

Forgejo is an Open Source code repository hosting software

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/freeform-vs-chronological-dichotomy/index.html b/garden/freeform-vs-chronological-dichotomy/index.html index 2602788c..668b63e1 100644 --- a/garden/freeform-vs-chronological-dichotomy/index.html +++ b/garden/freeform-vs-chronological-dichotomy/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Chronological, Freeform

Describes a dichotomy between displaying information in a Freeform vs Chronological manner

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/freeform/index.html b/garden/freeform/index.html index a033b005..198c1bfc 100644 --- a/garden/freeform/index.html +++ b/garden/freeform/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Commune, Digital Gardens, Freeform vs Chronological Dichotomy, Garden-RSS, The Small Web

A collection of information that is not tied to when it was created or edited

Part of the Freeform vs Chronological Dichotomy

Anything wiki-style is considered freeform

  • A collection of living documents

Garden-RSS, a theoretical alternative to RSS that's better for freeform content

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/game-dev-tree/index.html b/garden/game-dev-tree/index.html index 2dfb2b79..bff51932 100644 --- a/garden/game-dev-tree/index.html +++ b/garden/game-dev-tree/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Tags: My Projects

Play it here!

My first (good) incremental game! (My actual first was Shape Tycoon - I don't recommend it!)

It's Open Source!

The TV Tropes page on this game mentions some of the cool things about this game

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/garden-rss/index.html b/garden/garden-rss/index.html index d74af024..fb71b048 100644 --- a/garden/garden-rss/index.html +++ b/garden/garden-rss/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Garden-RSS ​

164 words, ~1 minute read. Planted . Last tended to -.

Referenced by: Freeform, The Small Web, This Knowledge Hub

A theoretical alternative to RSS that's better for Freeform websites (and Digital Gardens specifically )

Why is it useful?

How should it work?

  • Could display changes similar to git diffs

Existing Work

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Freeform, The Small Web, This Knowledge Hub

A theoretical alternative to RSS that's better for Freeform websites (and Digital Gardens specifically )

Why is it useful?

How should it work?

  • Could display changes similar to git diffs

Existing Work

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/guide-to-incrementals/appeal-to-developers/index.html b/garden/guide-to-incrementals/appeal-to-developers/index.html index 78047c45..72f95ffb 100644 --- a/garden/guide-to-incrementals/appeal-to-developers/index.html +++ b/garden/guide-to-incrementals/appeal-to-developers/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Guide to Incrementals/Appeal to Developers ​

731 words, ~4 minute read. Planted . Last tended to -.

There are a lot of developers in the incremental games community - the genre seems to draw them in, and convert a lot of players into developers. Let's explore the reasons why this genre appeals to developers.

Incrementals are Easy to Make ​

Compared to other genres, incrementals have quite low expectations. You don't need to make fancy art, or music, or lay things out nicely. If you can make a button and learn the few lines of code necessary to make a number go up, you can make an incremental. This low threshold makes the genre perfect for those who are actively learning to code and haven't developed any gamedev-related skills yet.

Additionally, unlike other genres incrementals are uniquely easy to implement in a normal web page - no need to worry about rendering sprites, moving them around, implementing physics, etc. New developers can just use HTML to add a button, and the game is now available in your browser. You don't need to choose an engine, have admin privileges, or hell for the dedicated you don't even need a computer - there are tools for web development that run in the browser itself, so you can technically use your phone if that's all you have.

Javascript is a perfectly viable language for making web games, whereas other genres are typically going to require using other more difficult languages to learn. There are countless javascript tutorials that start from 0 knowledge of programming, making it incredibly accessible to beginners.

Players are Easy to Find ​

Once you've finished your game and uploaded it on github pages or itch or just copied the link if you're using glitch or replit (all of which are easy to do), anyone can now play the game in their browser. This low barrier to entry has shown tremendous success in getting completely unknown developers to have thousands of plays.

The incremental games community, which mostly centers around r/incremental_games, is always looking for new games and tends to flood any new ones posted with initial players.

Having your games be played can be incredibly motivating, and the community makes it quite clear that you can expect players to play your game. These communities - both for incremental games in general as well as game-specific communities - tend to be very developer friendly as well. A lot of the developers know each other, and welcome new developers with open arms, often with dedicated channels for programming help and discussions.

Monetization ​

I'd like to clarify that everything I've said above mainly applies to web-based incrementals. Incremental games are also incredibly popular on mobile, but with a much different culture and community. Many mobile gamers will still participate in the web-focused community for the culture. This web-focused community has a culture that has been criticized for being "anti-monetization". Ads, IAPs, and similar forms of monetization are often criticized, mainly due to the abundance of completely non-monetized games available from hobbyist developers. There are exceptions, like paid games often being considered fine, like Increlution or Stuck in Time, or donation ware games like kittens game, but even popular games that have IAP see some level of regular criticism, like NGU Idle, Idle Skilling, or Idle Pins. A large part of this can be explained by the community being hyper-aware of the addictive) nature of this genre and its susceptibility to exploiting players.

On mobile, however, monetization is the norm and expected. If an incremental game is available on mobile, it almost certainly will be monetized, and mobile players are aware and accepting of that. Mobile incremental games, due to their addictive nature, tend to make a lot of money. It's very lucrative, and therefore these games are quite abundant on mobile storefronts.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

There are a lot of developers in the incremental games community - the genre seems to draw them in, and convert a lot of players into developers. Let's explore the reasons why this genre appeals to developers.

Incrementals are Easy to Make ​

Compared to other genres, incrementals have quite low expectations. You don't need to make fancy art, or music, or lay things out nicely. If you can make a button and learn the few lines of code necessary to make a number go up, you can make an incremental. This low threshold makes the genre perfect for those who are actively learning to code and haven't developed any gamedev-related skills yet.

Additionally, unlike other genres incrementals are uniquely easy to implement in a normal web page - no need to worry about rendering sprites, moving them around, implementing physics, etc. New developers can just use HTML to add a button, and the game is now available in your browser. You don't need to choose an engine, have admin privileges, or hell for the dedicated you don't even need a computer - there are tools for web development that run in the browser itself, so you can technically use your phone if that's all you have.

Javascript is a perfectly viable language for making web games, whereas other genres are typically going to require using other more difficult languages to learn. There are countless javascript tutorials that start from 0 knowledge of programming, making it incredibly accessible to beginners.

Players are Easy to Find ​

Once you've finished your game and uploaded it on github pages or itch or just copied the link if you're using glitch or replit (all of which are easy to do), anyone can now play the game in their browser. This low barrier to entry has shown tremendous success in getting completely unknown developers to have thousands of plays.

The incremental games community, which mostly centers around r/incremental_games, is always looking for new games and tends to flood any new ones posted with initial players.

Having your games be played can be incredibly motivating, and the community makes it quite clear that you can expect players to play your game. These communities - both for incremental games in general as well as game-specific communities - tend to be very developer friendly as well. A lot of the developers know each other, and welcome new developers with open arms, often with dedicated channels for programming help and discussions.

Monetization ​

I'd like to clarify that everything I've said above mainly applies to web-based incrementals. Incremental games are also incredibly popular on mobile, but with a much different culture and community. Many mobile gamers will still participate in the web-focused community for the culture. This web-focused community has a culture that has been criticized for being "anti-monetization". Ads, IAPs, and similar forms of monetization are often criticized, mainly due to the abundance of completely non-monetized games available from hobbyist developers. There are exceptions, like paid games often being considered fine, like Increlution or Stuck in Time, or donation ware games like kittens game, but even popular games that have IAP see some level of regular criticism, like NGU Idle, Idle Skilling, or Idle Pins. A large part of this can be explained by the community being hyper-aware of the addictive) nature of this genre and its susceptibility to exploiting players.

On mobile, however, monetization is the norm and expected. If an incremental game is available on mobile, it almost certainly will be monetized, and mobile players are aware and accepting of that. Mobile incremental games, due to their addictive nature, tend to make a lot of money. It's very lucrative, and therefore these games are quite abundant on mobile storefronts.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/guide-to-incrementals/appeal-to-players/index.html b/garden/guide-to-incrementals/appeal-to-players/index.html index d2fc54d0..83e677a8 100644 --- a/garden/guide-to-incrementals/appeal-to-players/index.html +++ b/garden/guide-to-incrementals/appeal-to-players/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Guide to Incrementals/Appeal to Players ​

2526 words, ~14 minute read. Planted . Last tended to -.

This is something that has been discussed and analyzed by many people, and to some extent, I feel like everything that can be said on the topic already has. However, a lot of these analyses are from the perspective of those with not as much experience and involvement within the genre as I'd argue would be necessary for a fully contextualized answer. I recently watched a video about Vampire Survivors, which has since been taken down due to drawing negative attention, which made me think about some interesting arguments about what games are, and what makes them good. The video's argument that "Vampire Survivors is not a video game" mirrors a claim by the developer of Cookie Clicker that his games are "non-games". Using Vampire Survivors and the video made on it as a framework, I'll be answering why incremental games appeal to players. Since the video has been taken down, I'll do my best to contextualize and generalize the arguments of the video without requiring the reader to watch it. For what it's worth, while I disagreed with the video I actually liked a lot of the way it went about thinking about games, and I consider this a continuation of that discussion.

Numbers Going Up ​

This is a very common response to why people enjoy incremental games, although it's not one I find compels me personally, and I suspect it might be a stand-in for progression) or Guide to Incrementals/What is Content?. But reportedly, some people do just like seeing big numbers. I must reiterate I suspect the actual cause is seeing big numbers in context though - if you start at 1e1000 of a currency and get to 1e1001, that isn't going to feel as satisfying as going from 1e10 to 1e100, and in any case, I don't think a button that just adds a zero to your number will feel quite satisfying - I believe its the sense of having made progress, and comparing where you are to where you started and feeling like you've earned your way here that is enjoyable.

Progression

Vampire Survivors can be argued to have a comparatively low depth to its combat compared to many other games. I'd argue it has sufficient depth and more than someone might expect who has only played the game for a short while, but it still definitely gets beat out by many other combat-focused games. Instead, a lot of the progression in Vampire Survivors comes from a meta-progression system by which base stats are increased by spending a currency that persists between runs. While it is technically possible to win without this meta-progression system, and indeed in many roguelikes players like to challenge themselves by beating the game without any meta-progression, the criticism can be made that meta-progression de-emphasizes player skill by making it less important to have to beat the game. Certainly, in incremental games, it is often literally impossible to complete a game without taking advantage of the meta-progression systems. I'd argue this does not detract from the game, however, and is actually a part of what makes incremental games, and roguelikes, enjoyable to many players: meta-progression augments the increases in skill the player is naturally gaining as they play. In effect, it's not replacing the skill increase, but exaggerating it to make it feel more real to the player.

Note: There is also a lot of progression from exploring the mechanics and discovering synergies, unlocking new weapons or playable characters, etc. That just isn't as relevant to this discussion, but it does make up a lot of the appeal of the game.

Effortlessness ​

Incremental games are so easy, a lot of them even have you progress while you're not playing! Part of the appeal is being able to feel like you're making progress while doing something actually productive - multitasking, in a way. In this sense, the game is more of a fidget toy - not something to think hard about and play actively, but something to click a few buttons every so often while you're paying attention to a lecture or studying or working. Of course, not all incremental games lend themselves to being played this way - it's specifically "idle" games that work like this. These are games that take an incredibly long amount of time to see all the content, stretching it as thin as possible, but they aren't expecting you to be sitting at your device playing it the entire time. They expect you to leave and come back later to make a bit of progress and repeat the cycle.

If you look at the higher-level play of most games, you'll see them perform difficult feats with ease and speed. They'll achieve a "flow state" that takes all their knowledge and experience of the game and uses it to play the game as instinctively as possible. It's incredible to watch things like Slay the Spire speed runs or competitive DDR-likes. I'd argue the goal of a lot of games with a competitive scene is to get so good that the game becomes effortless. In that sense, a game that allows you to reach that point earlier isn't any less legitimate, but rather lowers the barrier to entry by allowing more people to get "really good" at the game. And to be clear, Vampire Survivors and (most) incremental games aren't trivially easy - they, and to an extent, every game will have some level of learning and improvement over time.

Addiction

A lot of these reasons for why incremental games appeal may have reminded you of why gambling appeals to people, particularly those prone to addiction. Indeed, incremental games are quite often criticized for their similarity to a skinner box. Some have gone as far as to say incremental games as a genre are commenting that all games are skinner boxes). The argument goes that some games are not fun, but rather condition players into continuing to play without actually getting anything from the experience. When tied to real-world money this is seen as predatory, and to a lesser extent, even free games may be feeding the addictive sides of people and making them more prone to seek out gambling or micro-transaction heavy games.

While incremental games can be fun and even healthy in certain contexts, they can exacerbate video game addiction more than other genres. If you feel like playing incremental games is taking priority over other things in your life, or manipulating your sleep schedule, it may be prudent to seek help. See r/StopGaming for resources.

Since incremental games are often built on extrinsic motivations in the form of progression systems, it's hard to argue whether players continue to play because they are enjoying the gameplay, or if they are just conditioned to keep doing it because the game keeps rewarding them. Unfortunately, it can often feel like it's the latter, as there isn't typically anything compelling about the "gameplay" of clicking a button and waiting. There may be a significant overlap between those who enjoy incremental games and those who are most prone to addiction, and there are often posts on r/incremental_games about someone either struggling with or overcoming video game addiction.

Strategy ​

Incremental games could be considered a subset of strategy games), and inherit the appeals of strategy games. This includes the appeal of feeling like you've found a good solution to a puzzle, or that you're learning more about the game and are improving at making decisions within it. This applies to Vampire Survivors specifically, where you're learning about evolutions and synergies and what kinds of enemies can spawn under what conditions, and how best to handle them.

Note that strategy games are not all the same difficulty, as well. Vampire Survivors is still easier to play than Starcraft 2, and Cookie Clicker is probably somewhere in between (once you progress sufficiently). Vampire Survivors being so successful may indicate that "easier" strategies may have their separate appeal to harder strategy games - players like to feel smart and that they figured the game out and have optimized or mastered it, and the game being easier doesn't detract from that sense of accomplishment as much as it allows more and more users to be able to reach the point where they gain that sense.

Avoiding Staleness ​

Incremental games tend to have "paradigm shifts", where the gameplay changes in a meaningful way at various times throughout the progression of the game. These upset and change the gameplay loop, which helps keep them from stagnating. This constant "freshness" to the gameplay can keep players engaged for longer, compared to a game with a repetitive and static gameplay loop.

Good Game Design ​

Incremental games tend to show their game design "plainly", so it's more readily apparent if a game has good game design while playing, even if you're not looking for it. While different players have different preferences and might enjoy different types of games more than others, there are underlying good and bad game design principles that players will notice the effects of. To be clear, this isn't talking about stuff like big numbers being enjoyable, where I can comfortably agree to disagree with other players. They don't intrinsically make my experience better, but I'm aware of those for whom it does and I won't argue against their feelings. However, the game designer in me does feel like there are some extremely clear-cut examples of good and bad game design philosophies.

Let's start by giving an example of a mechanic I think can be easily and strongly argued is good game design. There are of course many examples, but a personal favorite of mine is how DOOM encourages aggressive gameplay by linking health drops to melee attacks. It has an intended experience it's trying to give the player - immersing themselves as DOOM guy, who would not hide behind cover when low on health - and this mechanic does a great job at encouraging and effectively teaching players to behave properly. This is in sharp contrast to shooters like Call of Duty, which have you regen health passively, encouraging players to hide behind cover and wait after getting hit. Note that I'm not arguing CoD is poorly designed, as the games have different intended experiences. I'm specifically praising DOOM for having a mechanic that does a good job at ensuring the player has that intended experience.

To contrast with an example I think is bad game design, let's talk about shields in souls-likes. This is a bit of a famous example, and I highly recommend this video essay which spends quite a good bit of time on this topic. Essentially, the argument boils down to players of earlier games in the souls games using shields too much - playing slowly, conservatively, and ultimately having less fun. Players wanted to feel safe, so they ended up playing in a way that ruined the experience for them. The developers solved this by removing shields, apart from an intentionally bad one effectively mocking the playstyle, and it did its job at getting players to play more aggressively, and often have more fun.

To bring the conversation back to incrementals, I'm incredibly opinionated on what makes a good incremental game, which I'll discuss in the game design section. Suffice it to say, incremental games rely more on good game design than other genres, due to not having much to distract from bad game design. This helps (although imperfectly - gamers are a bit too tolerant of bad game design!) well-designed games rise to the top within the genre.

Artistic Merit ​

The Vampire Survivors video made me think back to the old arguments about whether games are art, and whether they ought to be. The video seems preoccupied with attaching value to games solely based on their mechanics and the depth thereof, to the point of arguing Vampire Survivors is a waste of time due to its lack of depth. However, even setting aside the fact that if players are having fun then it's not time wasted, I think games can have artistic merit that supersedes the necessity of having (any / engaging / "deep") gameplay. I think the consensus online is that games are definitively art, although I could see the argument that some genres, like incremental games, might be a bit in a grey area. Let's talk about Vampire Survivors first though - It has a story to tell, with lore and many characters, that drive the player and encourage them to continue exploring the game and discovering things within it. Like any walking simulator, it is no less legitimate of a game or the "art" label because of any lack perceived lack of depth. For what it's worth, most art can be consumed with more ease than VS - any painting, movie, sculpture, etc.

A lot of incrementals have a narrative context that can similarly qualify them as art. Cookie Clicker is, as has been pointed out numerous times before, commenting on excess and increasing production beyond any reasonable limits - devolving into increasing production for its own sake. Indeed, a lot of incremental games are written to comment upon various concepts like capitalism or tropes in games, as discussed when defining Incrementals). However, I'd like to argue most incremental games are still art, even without any narrative context. "Art" as a concept is pretty nebulous already, but I personally like those who define it as an act of expression more than any physical result. The creator and the context within which they created the art, and any meaning they put into it, are all relevant and a part of the art itself. Most incremental games have artistic merit from things like why the creator made it, why they chose to make it an incremental game, and why they made any particular design decision. Hell, even if you play through an entire incremental game without a single thought or feeling, that very fact it elicited nothing can itself be artistic merit!

I'm not an art major, and I may be taking a somewhat extreme take on what is art and what has artistic merit, but I'd argue the overall point stands that games, and incremental games specifically, can have artistic merit, which appeals to many gamers.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

This is something that has been discussed and analyzed by many people, and to some extent, I feel like everything that can be said on the topic already has. However, a lot of these analyses are from the perspective of those with not as much experience and involvement within the genre as I'd argue would be necessary for a fully contextualized answer. I recently watched a video about Vampire Survivors, which has since been taken down due to drawing negative attention, which made me think about some interesting arguments about what games are, and what makes them good. The video's argument that "Vampire Survivors is not a video game" mirrors a claim by the developer of Cookie Clicker that his games are "non-games". Using Vampire Survivors and the video made on it as a framework, I'll be answering why incremental games appeal to players. Since the video has been taken down, I'll do my best to contextualize and generalize the arguments of the video without requiring the reader to watch it. For what it's worth, while I disagreed with the video I actually liked a lot of the way it went about thinking about games, and I consider this a continuation of that discussion.

Numbers Going Up ​

This is a very common response to why people enjoy incremental games, although it's not one I find compels me personally, and I suspect it might be a stand-in for progression) or Guide to Incrementals/What is Content?. But reportedly, some people do just like seeing big numbers. I must reiterate I suspect the actual cause is seeing big numbers in context though - if you start at 1e1000 of a currency and get to 1e1001, that isn't going to feel as satisfying as going from 1e10 to 1e100, and in any case, I don't think a button that just adds a zero to your number will feel quite satisfying - I believe its the sense of having made progress, and comparing where you are to where you started and feeling like you've earned your way here that is enjoyable.

Progression

Vampire Survivors can be argued to have a comparatively low depth to its combat compared to many other games. I'd argue it has sufficient depth and more than someone might expect who has only played the game for a short while, but it still definitely gets beat out by many other combat-focused games. Instead, a lot of the progression in Vampire Survivors comes from a meta-progression system by which base stats are increased by spending a currency that persists between runs. While it is technically possible to win without this meta-progression system, and indeed in many roguelikes players like to challenge themselves by beating the game without any meta-progression, the criticism can be made that meta-progression de-emphasizes player skill by making it less important to have to beat the game. Certainly, in incremental games, it is often literally impossible to complete a game without taking advantage of the meta-progression systems. I'd argue this does not detract from the game, however, and is actually a part of what makes incremental games, and roguelikes, enjoyable to many players: meta-progression augments the increases in skill the player is naturally gaining as they play. In effect, it's not replacing the skill increase, but exaggerating it to make it feel more real to the player.

Note: There is also a lot of progression from exploring the mechanics and discovering synergies, unlocking new weapons or playable characters, etc. That just isn't as relevant to this discussion, but it does make up a lot of the appeal of the game.

Effortlessness ​

Incremental games are so easy, a lot of them even have you progress while you're not playing! Part of the appeal is being able to feel like you're making progress while doing something actually productive - multitasking, in a way. In this sense, the game is more of a fidget toy - not something to think hard about and play actively, but something to click a few buttons every so often while you're paying attention to a lecture or studying or working. Of course, not all incremental games lend themselves to being played this way - it's specifically "idle" games that work like this. These are games that take an incredibly long amount of time to see all the content, stretching it as thin as possible, but they aren't expecting you to be sitting at your device playing it the entire time. They expect you to leave and come back later to make a bit of progress and repeat the cycle.

If you look at the higher-level play of most games, you'll see them perform difficult feats with ease and speed. They'll achieve a "flow state" that takes all their knowledge and experience of the game and uses it to play the game as instinctively as possible. It's incredible to watch things like Slay the Spire speed runs or competitive DDR-likes. I'd argue the goal of a lot of games with a competitive scene is to get so good that the game becomes effortless. In that sense, a game that allows you to reach that point earlier isn't any less legitimate, but rather lowers the barrier to entry by allowing more people to get "really good" at the game. And to be clear, Vampire Survivors and (most) incremental games aren't trivially easy - they, and to an extent, every game will have some level of learning and improvement over time.

Addiction

A lot of these reasons for why incremental games appeal may have reminded you of why gambling appeals to people, particularly those prone to addiction. Indeed, incremental games are quite often criticized for their similarity to a skinner box. Some have gone as far as to say incremental games as a genre are commenting that all games are skinner boxes). The argument goes that some games are not fun, but rather condition players into continuing to play without actually getting anything from the experience. When tied to real-world money this is seen as predatory, and to a lesser extent, even free games may be feeding the addictive sides of people and making them more prone to seek out gambling or micro-transaction heavy games.

While incremental games can be fun and even healthy in certain contexts, they can exacerbate video game addiction more than other genres. If you feel like playing incremental games is taking priority over other things in your life, or manipulating your sleep schedule, it may be prudent to seek help. See r/StopGaming for resources.

Since incremental games are often built on extrinsic motivations in the form of progression systems, it's hard to argue whether players continue to play because they are enjoying the gameplay, or if they are just conditioned to keep doing it because the game keeps rewarding them. Unfortunately, it can often feel like it's the latter, as there isn't typically anything compelling about the "gameplay" of clicking a button and waiting. There may be a significant overlap between those who enjoy incremental games and those who are most prone to addiction, and there are often posts on r/incremental_games about someone either struggling with or overcoming video game addiction.

Strategy ​

Incremental games could be considered a subset of strategy games), and inherit the appeals of strategy games. This includes the appeal of feeling like you've found a good solution to a puzzle, or that you're learning more about the game and are improving at making decisions within it. This applies to Vampire Survivors specifically, where you're learning about evolutions and synergies and what kinds of enemies can spawn under what conditions, and how best to handle them.

Note that strategy games are not all the same difficulty, as well. Vampire Survivors is still easier to play than Starcraft 2, and Cookie Clicker is probably somewhere in between (once you progress sufficiently). Vampire Survivors being so successful may indicate that "easier" strategies may have their separate appeal to harder strategy games - players like to feel smart and that they figured the game out and have optimized or mastered it, and the game being easier doesn't detract from that sense of accomplishment as much as it allows more and more users to be able to reach the point where they gain that sense.

Avoiding Staleness ​

Incremental games tend to have "paradigm shifts", where the gameplay changes in a meaningful way at various times throughout the progression of the game. These upset and change the gameplay loop, which helps keep them from stagnating. This constant "freshness" to the gameplay can keep players engaged for longer, compared to a game with a repetitive and static gameplay loop.

Good Game Design ​

Incremental games tend to show their game design "plainly", so it's more readily apparent if a game has good game design while playing, even if you're not looking for it. While different players have different preferences and might enjoy different types of games more than others, there are underlying good and bad game design principles that players will notice the effects of. To be clear, this isn't talking about stuff like big numbers being enjoyable, where I can comfortably agree to disagree with other players. They don't intrinsically make my experience better, but I'm aware of those for whom it does and I won't argue against their feelings. However, the game designer in me does feel like there are some extremely clear-cut examples of good and bad game design philosophies.

Let's start by giving an example of a mechanic I think can be easily and strongly argued is good game design. There are of course many examples, but a personal favorite of mine is how DOOM encourages aggressive gameplay by linking health drops to melee attacks. It has an intended experience it's trying to give the player - immersing themselves as DOOM guy, who would not hide behind cover when low on health - and this mechanic does a great job at encouraging and effectively teaching players to behave properly. This is in sharp contrast to shooters like Call of Duty, which have you regen health passively, encouraging players to hide behind cover and wait after getting hit. Note that I'm not arguing CoD is poorly designed, as the games have different intended experiences. I'm specifically praising DOOM for having a mechanic that does a good job at ensuring the player has that intended experience.

To contrast with an example I think is bad game design, let's talk about shields in souls-likes. This is a bit of a famous example, and I highly recommend this video essay which spends quite a good bit of time on this topic. Essentially, the argument boils down to players of earlier games in the souls games using shields too much - playing slowly, conservatively, and ultimately having less fun. Players wanted to feel safe, so they ended up playing in a way that ruined the experience for them. The developers solved this by removing shields, apart from an intentionally bad one effectively mocking the playstyle, and it did its job at getting players to play more aggressively, and often have more fun.

To bring the conversation back to incrementals, I'm incredibly opinionated on what makes a good incremental game, which I'll discuss in the game design section. Suffice it to say, incremental games rely more on good game design than other genres, due to not having much to distract from bad game design. This helps (although imperfectly - gamers are a bit too tolerant of bad game design!) well-designed games rise to the top within the genre.

Artistic Merit ​

The Vampire Survivors video made me think back to the old arguments about whether games are art, and whether they ought to be. The video seems preoccupied with attaching value to games solely based on their mechanics and the depth thereof, to the point of arguing Vampire Survivors is a waste of time due to its lack of depth. However, even setting aside the fact that if players are having fun then it's not time wasted, I think games can have artistic merit that supersedes the necessity of having (any / engaging / "deep") gameplay. I think the consensus online is that games are definitively art, although I could see the argument that some genres, like incremental games, might be a bit in a grey area. Let's talk about Vampire Survivors first though - It has a story to tell, with lore and many characters, that drive the player and encourage them to continue exploring the game and discovering things within it. Like any walking simulator, it is no less legitimate of a game or the "art" label because of any lack perceived lack of depth. For what it's worth, most art can be consumed with more ease than VS - any painting, movie, sculpture, etc.

A lot of incrementals have a narrative context that can similarly qualify them as art. Cookie Clicker is, as has been pointed out numerous times before, commenting on excess and increasing production beyond any reasonable limits - devolving into increasing production for its own sake. Indeed, a lot of incremental games are written to comment upon various concepts like capitalism or tropes in games, as discussed when defining Incrementals). However, I'd like to argue most incremental games are still art, even without any narrative context. "Art" as a concept is pretty nebulous already, but I personally like those who define it as an act of expression more than any physical result. The creator and the context within which they created the art, and any meaning they put into it, are all relevant and a part of the art itself. Most incremental games have artistic merit from things like why the creator made it, why they chose to make it an incremental game, and why they made any particular design decision. Hell, even if you play through an entire incremental game without a single thought or feeling, that very fact it elicited nothing can itself be artistic merit!

I'm not an art major, and I may be taking a somewhat extreme take on what is art and what has artistic merit, but I'd argue the overall point stands that games, and incremental games specifically, can have artistic merit, which appeals to many gamers.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/guide-to-incrementals/defining-the-genre/index.html b/garden/guide-to-incrementals/defining-the-genre/index.html index 7f8f3965..25e6e0d9 100644 --- a/garden/guide-to-incrementals/defining-the-genre/index.html +++ b/garden/guide-to-incrementals/defining-the-genre/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Guide to Incrementals/Defining the Genre ​

3595 words, ~20 minute read. Planted . Last tended to -.

Video games are placed into genres for a variety of reasons. They can give a mental shorthand to set the player's expectations up, they can help a game market itself by its similarities to other, already popular games, and honestly, people just love categorization for its own sake. For this guide, it's important to define the genre so it is clear what games it's even talking about.

This poses a problem. "Incremental" is a horribly vague way to define games. Most games have numbers going up in some form or another. We need a more specific definition - similar to how "strategy" can't just mean any game with any amount of strategy because that would be most games. What specifically differentiates incremental games from the rest?

"Incremental" implies it's a genre defined by a game mechanic, but all those game mechanics it could imply exist in many other games. Having a skill tree or upgrades doesn't make you incremental, and if a reset mechanic is all it takes then every roguelite would be an incremental as well. So clearly there's more to it than that - what makes an incremental an incremental?

I'd like to go over a couple of popular suggestions I've seen on defining the genre here. I have my personal preferences and will state them here, but I don't think there's a truly perfect answer here.

Disclaimer: I mostly play incremental games on my computer, and my definitions will be heavily biased towards the games I'm familiar with.

Incrementals vs Idlers vs Clickers ​

Oftentimes people refer to this genre as idle games and/or clicker games. You'll even find a trend of oxymoronic game titles that contain both terms. "Incremental games" is the umbrella term both those terms fall under. However, I'd like to argue that not only is it better to just use the term "incremental games", but calling them "idle games" or "clicker games" is wrong. Almost universally, these terms are used interchangeably to refer to the same kind of game, where you start the game click spamming and eventually automate the process. Frankly, that kind of game deserves neither title, and the genre of incremental games has trended away from ever requiring click spamming, as it's a bad mechanic, anyways.

While these games do span a spectrum of how active it requires you to be, and sorting games by that metric can be useful for those looking for a particular experience, the borders of when an incremental game counts as an "idler" is too blurry for the term to be useful. "Incremental games" may not be a great descriptive term for the genre (hence this many thousands of words long page on defining what the genre even is), but it's strictly better than calling them "idler" or "clicker" games. This guide will always use the term "incremental games" unless quoting someone else, as it is the term you typically see on all modern games in the genre.

Incrementals as Parodies

Let's start with one of the most interesting definitions of incremental games. Incremental games appear to be distilled versions of games or genres, "revealing" the naked game design at the core of these games or genres not unlike how parodies comment upon their source material.

To understand what that means, think of how a casino uses skinner boxes to emotionally manipulate its customers to keep playing, but "dressing" up the skinner box with tons of stimuli to hide that ultimately the goal is to condition you into coming back compulsively. The idea that incremental games are parodies means taking the stance that at some level all games are similarly manipulating you, giving dopamine rewards in a way that manipulates you to keep playing while not necessarily giving you any value or fulfillment. Incremental games, then, are any games that plainly display the skinner box, and the manipulative core of the game, at the forefront of the experience.

While incremental games can be fun and even healthy in certain contexts, they can exacerbate video game addiction more than other genres. If you feel like playing incremental games is taking priority over other things in your life, or manipulating your sleep schedule, it may be prudent to seek help. See r/StopGaming for resources.

This "undressing" tends to go hand in hand with a reduced focus on aesthetics, often just printing the game state directly to the screen as text. This makes incremental games much easier to develop, particularly for those with programming skills but not art skills, but that's a tangent for why Incremental Games Guide to Incrementals/Appeal to Developers.

Before I continue, I'd like to make my stance clear that I love games and incremental games, and do not think they should be considered inherently bad or manipulative with the above logic. Skinner boxes are just a way of manipulating behavior via rewards. The games are still fun - that's the reward! I'd believe the real criticism here is that it is "empty fun", or "empty dopamine", that doesn't offer any additional value or sense of fulfillment. I don't think that's inherently bad in moderation, although it can become a problem if the game is manipulating you for profit-seeking, or if you play the game to the detriment of the other parts of your life.

Another interpretation of incremental games as parodies comes from several mainstream incremental games that are also parodies of capitalism, such as cookie clicker and adventure capitalist. It's a very common framework for incremental games to portray the ever-increasing numbers as an insatiable hunger for resources, like the ones observed within capitalism. Therefore, these games are used as evidence that the genre as a whole is about parody and commentary.

Popular videos on incremental games that portray the genre as parodies are Why Idle games make good satire, and how it was ruined. and Bad Game Design - Clicker Games. You may also be interested in this response to the latter video from a fan of incremental games: BadGood Game Design - Clicker Games.

I think that this definition ultimately ascribes a motive to the genre as a whole that only happens to apply to some of the more mainstream titles. There certainly are incremental games commenting on different things, including the genre itself as in the case of The Prestige Tree Classic, The Ascension Tree, or Omega Layers, but certainly not all. And of course, not all games that comment on something or parody something are incremental games! Additionally, a very large majority of incremental games are mobile games using these manipulative strategies to get players to spend as much money as possible - hell, Adventure Capitalist is ostensibly a critique on capitalism but features microtransactions and gameplay that manipulates you into buying them! These profit-seeking incremental games certainly belong within the genre but are hardly parodies when they too use manipulation to serve their interests. Also, from my own anecdotal experience, those who use this definition seem to do so from a fairly surface-level familiarity with the genre, and often in the context of criticizing the genre or the fans thereof.

Incrementals as NGU ​

Another broad definition often used is that incremental games are games where the focus of the game is "numbers going up". This definition proposes that other genres simply use increasing numbers as a means to an end, but incremental games uniquely only care about the numbers themselves going up. Put another way, it implies there should be no narrative justification for the numbers going up other than "why shouldn't they be going up?"

While this definition is common because it feels easy to understand, it is difficult to formally define. Often phrases are used to describe games using this framework, such as having an "exaggerated sense of progression" or "big" numbers. These terms are vague and don't demonstrate an actual threshold between non-incrementals and incrementals. Most games have a sense of progression, so when is it "exaggerated"? How big are "big" numbers? Most notably, RPGs that are typically not considered incrementals will often pass this definition.

Additionally, a lot of incrementals tend to have some theme guiding the gameplay, or at least the names of mechanics. This makes the line blurred between when numbers are going up for their own sake versus for a contextual reason. I believe this point is best illustrated that, while most RPGs are not considered incremental games, there is a sub-genre of "incremental RPGs" that typically relates to RPGs that perform combat automatically. This definition of incremental games does not support RPGs and "incremental RPGs" being on distinct sides of the line if the only difference between them is manual vs automatic combat.

Incrementals as Strategies

This is a rarer interpretation, but there are similarities between incremental games and strategy games, implying incrementals might just be a sub-genre of strategy games. By this approach, incremental games would be defined by their relation to strategy games, and how they involve player strategy. Incremental games are often large optimization problems - above all else, the actual gameplay the player is performing is deciding what to do next. The consequences of wrong decisions are typically more lenient in incremental games - such as just not making optimal progress - but they certainly get complex.

So if we accept the premise that incrementals could fall under strategy, we still need to define what makes a strategy game an incremental versus some other strategy sub-genre. This is a bit tricky due to one particular sub-genre of strategy games: Factory Builders.

Factory builders, such as Factorio or Satisfactory, are games about gaining ever increasing resources, optimizing production, and expanding more and more. That... sounds pretty similar, doesn't it? In fact, there's been some debate on whether factory builders would fall under the "incremental" umbrella. I think it's safe to say the two are certainly related, and probably have quite a bit of overlap in playerbase.

Roguelites as Incrementals? ​

Earlier on, I mentioned reset mechanics shouldn't be used in the definition because that could make all roguelites incrementals... But what if it does? A lot of incrementals can be described as games with a strong sense of progression, often with layers of meta-progression. Roguelites fit that bill to a T. What would make roguelites not incremental? I honestly don't think there's a good explanation here, but many fans of incremental games will state they do believe the two genres to be unrelated, even if there's a significant overlap between their player bases due to having similar appealing traits.

At this point, it'd be appropriate to consider what part of the definition of roguelites precludes them from also being incrementals, but that reveals a new problem: What are roguelites? They're usually defined as rogue_likes with meta-progression, but that just pushes the problem back a step: Incrementals aren't the only genre to have difficulties defining themselves, it seems! Roguelikes are another genre where the community argues over the formal definition of their genre, although that means we can borrow from their process of coming to a consensus, and maybe come across a viable definition for incremental games.

The Berlin Interpretation ​

By far the most popular way of defining roguelikes is the "Berlin Interpretation", which acknowledged the diversity of games within the genre and argued the definition should not be based on any ideals about what the genre ought to be, but rather defined by "its canon". They argued there are a handful of games that can be used to define the canon for roguelikes, and from those games, a list of factors can be derived to determine a game's "roguelikeness". The more factors a game has, the more of a roguelike it is. This strategy is very lenient, allowing a game to not present any specific factor so long as it shows enough, and accounts for the blurriness of any genre definition by not explicitly stating how many factors a game must have to qualify as a definite roguelike.

I believe this strategy for defining genres can be applied to other genres as well. A handful of games can be argued to be the incremental games canon, and a list of factors derived from them can be used to judge any game based on its "incrementalness". I'll propose such a canon and list of factors here, but by no means should it be considered the end-all-be-all.

Note: The "Temple of the roguelike", an authority within the genre, has since replaced the Berlin Interpretation with a new set of factors here: https://blog.roguetemple.com/what-is-a-traditional-roguelike/

The Incremental Games Canon ​

Alright, time to get controversial. Up til now, I've been trying my best to stay objective and analytical, but now it's time to start making some opinionated decisions. Here is a list of games I think could justifiably make up an Incremental Games Canon:

I chose a variety of games here, biasing towards newer games, purposefully to avoid making a narrow or "traditional" definition. The genre is growing and shouldn't be constrained by the traits of the early popular titles. A lot of these could easily be replaced with other games that are mechanically congruent, so ultimately I'm sure if you asked 10 people for their canon list you'd just get 10 different answers, but I think this should sufficiently allow us to determine what factors make a game have higher "incrementalness".

The Paradigm Shift ​

The Paradigm Shift is probably the highest possible value factor for an incremental. It's so common that for a while people referred to incrementals that exhibit this trait as "unfolding" games, to the point of trying to replace the term incremental due to their popularity. Paradigm shifts refer to when the gameplay significantly changes. There are too many examples to list here, but notably, every single reset mechanic is typically going to be a paradigm shift. Examples of games with paradigm shifts that aren't tied to reset mechanics include Universal Paperclips and A Dark Room.

There are many reasons for the appeal of paradigm shifts. Oftentimes each mechanic builds on top of the existing mechanics, increasing the complexity of the game in steps so the player can follow along. They provide a sense of mystery, with the player anticipating what will happen next. They shake up the gameplay before it gets too stale - allowing the game to entertain for longer before the sense of Guide to Incrementals/What is Content? dissipates. Of the canon games selected above, I would argue every single one contains a paradigm shift (although I could see someone disagreeing with that statement wrt Increlution).

I should take a moment to say that while I'm hyping up this specific factor, we cannot just reduce the genre definition to "does it have paradigm shifts". Many games have paradigm shifts that are not incremental, so it's just an indicator of incrementalness. Additionally, it can become quite hard to determine how large of a shift is a "paradigm" shift. Take, for example, any game with a skill tree. In some games, each skill node might have a large impact on how you play with the game, and qualify as a paradigm shift for some players. In other games, each skill node might just be a small percentage modifier on some stat that doesn't really impact much more than a slight bias towards an already established mechanic that's newly buffed. Every single canon game may show that it's common amongst incremental games, but could just as easily indicate that they're common in games in general.

High-Value Factors ​

I won't take as long to discuss the high and low-value factors, as you've already seen most of them brought up earlier on this page. As a reminder, a game does NOT need all of these to be an incremental game, but these are factors that each indicate a strong possibility the game is an incremental, so having several of these means they probably are. These factors apply to most of the canon incremental games.

"Pure UI" Display. Incrementals typically have a textual presentation of the game state - there isn't a visual representation of the entities within the game. The interface is closer to what would be just the UI of a game in another genre or the control panel of a plane. If there is a visual representation, the player is often still interacting with non-diegetic game elements.

Reduced Consequences. Incrementals tend to have reduced repurcussions for misplaying. They very rarely have fail states, where often the largest consequence is simply not progressing - never losing progress.

Optimization Problems. The predominant gameplay of incrementals is typically solving optimization problems, from deciding which purchase to save up for to reasoning and deciding between different mutually exclusive options the game presents.

Resource Management. Incrementals tend to have a lot of resources within the game to keep track of.

Low-Value Factors ​

These are low-value factors, meaning they aren't as strongly correlated with incremental games. Incremental games may have none of these, and non-incrementals may have several of these - if a game only has low-value factors, they're probably not an incremental.

Fast Numeric Growth. Numbers in incremental games tend to grow faster than in other genres. There are more instances of superlinear growth. The larger the numbers get, the stronger of a signal this factor is.

Automation. As an incremental game progresses, the player often no longer has to deal with earlier mechanics, by having them either happen automatically or otherwise be replaced with an alternative that requires less player interaction.

Goal-Oriented. Incrementals are often heavily reliant on extrinsic motivation to guide the player. Typically this is through some sort of in-game goal to work towards, such as a certain amount of a resource being required to unlock or purchase something new.

Waiting is a Mechanic. In incremental games, the player may come across times where there is no action they can take, and the game will progress automatically instead. The player must wait for some amount of this automatic progress to occur before they can resume interaction with the game.

Are Roguelites Incrementals? ​

Having made our variation of the Berlin Interpretation for incremental games, we can compare it to the Berlin Interpretation to determine if there's enough overlap that any game that "passes" the Berlin Interpretation would also pass the incremental variant. That is to say, whether any roguelite would also be considered an incremental game.

The meta-progression of an incremental game could arguably be considered a paradigm shift, and certainly adds some resource management. Goal-oriented would probably also apply. I think anything other than those would be a stretch, and in my opinion that just isn't enough to qualify. To be totally honest, I was never expecting to conclude otherwise though 😉

Sub-Genres ​

There are some trends in incremental games that go beyond just being a commonly used mechanic, such that they deeply affect the rest of the game design. These trends can be used to determine sub-genres within the incremental games umbrella:

Loops games are a sub-genre defined by having a core mechanic related to a loop, where the player is deciding the actions taken per loop. Notable examples include Idle Loops, Stuck in Time, Cavernous II, and Increlution. You may also argue Groundhog Life and Progress Knight fall into this sub-genre.

ITRTG-like games are a sub-genre defined by having a core mechanic based on clearing increasingly difficult battles and often tend to have a lot of different mechanics to become progressively stronger. Notable examples include Idling to Rule the Gods, NGU Idle, and Wizard and Minion Idle.

Polynomial Growth games are a sub-genre defined by having a core mechanic related to a higher degree polynomial. Notable examples include the base layer of Antimatter Dimensions and Swarm Simulator.

Upgrades Games is a category popular on flash games websites that featured games focused on buying upgrades that would allow you to attain more currency in some sort of minigame that would earn you more money to buy more upgrades, which I'd argue now belong under the fold of incremental games. Notable examples include the Learn to Fly series and Upgrade Complete.

Cultivation RPGs are a genre of games, books, and anime popular in China that center around being in a fantasy world with characters getting stronger over time. While few of them get translated into English, a fan of incremental games may find the available games interesting.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Video games are placed into genres for a variety of reasons. They can give a mental shorthand to set the player's expectations up, they can help a game market itself by its similarities to other, already popular games, and honestly, people just love categorization for its own sake. For this guide, it's important to define the genre so it is clear what games it's even talking about.

This poses a problem. "Incremental" is a horribly vague way to define games. Most games have numbers going up in some form or another. We need a more specific definition - similar to how "strategy" can't just mean any game with any amount of strategy because that would be most games. What specifically differentiates incremental games from the rest?

"Incremental" implies it's a genre defined by a game mechanic, but all those game mechanics it could imply exist in many other games. Having a skill tree or upgrades doesn't make you incremental, and if a reset mechanic is all it takes then every roguelite would be an incremental as well. So clearly there's more to it than that - what makes an incremental an incremental?

I'd like to go over a couple of popular suggestions I've seen on defining the genre here. I have my personal preferences and will state them here, but I don't think there's a truly perfect answer here.

Disclaimer: I mostly play incremental games on my computer, and my definitions will be heavily biased towards the games I'm familiar with.

Incrementals vs Idlers vs Clickers ​

Oftentimes people refer to this genre as idle games and/or clicker games. You'll even find a trend of oxymoronic game titles that contain both terms. "Incremental games" is the umbrella term both those terms fall under. However, I'd like to argue that not only is it better to just use the term "incremental games", but calling them "idle games" or "clicker games" is wrong. Almost universally, these terms are used interchangeably to refer to the same kind of game, where you start the game click spamming and eventually automate the process. Frankly, that kind of game deserves neither title, and the genre of incremental games has trended away from ever requiring click spamming, as it's a bad mechanic, anyways.

While these games do span a spectrum of how active it requires you to be, and sorting games by that metric can be useful for those looking for a particular experience, the borders of when an incremental game counts as an "idler" is too blurry for the term to be useful. "Incremental games" may not be a great descriptive term for the genre (hence this many thousands of words long page on defining what the genre even is), but it's strictly better than calling them "idler" or "clicker" games. This guide will always use the term "incremental games" unless quoting someone else, as it is the term you typically see on all modern games in the genre.

Incrementals as Parodies

Let's start with one of the most interesting definitions of incremental games. Incremental games appear to be distilled versions of games or genres, "revealing" the naked game design at the core of these games or genres not unlike how parodies comment upon their source material.

To understand what that means, think of how a casino uses skinner boxes to emotionally manipulate its customers to keep playing, but "dressing" up the skinner box with tons of stimuli to hide that ultimately the goal is to condition you into coming back compulsively. The idea that incremental games are parodies means taking the stance that at some level all games are similarly manipulating you, giving dopamine rewards in a way that manipulates you to keep playing while not necessarily giving you any value or fulfillment. Incremental games, then, are any games that plainly display the skinner box, and the manipulative core of the game, at the forefront of the experience.

While incremental games can be fun and even healthy in certain contexts, they can exacerbate video game addiction more than other genres. If you feel like playing incremental games is taking priority over other things in your life, or manipulating your sleep schedule, it may be prudent to seek help. See r/StopGaming for resources.

This "undressing" tends to go hand in hand with a reduced focus on aesthetics, often just printing the game state directly to the screen as text. This makes incremental games much easier to develop, particularly for those with programming skills but not art skills, but that's a tangent for why Incremental Games Guide to Incrementals/Appeal to Developers.

Before I continue, I'd like to make my stance clear that I love games and incremental games, and do not think they should be considered inherently bad or manipulative with the above logic. Skinner boxes are just a way of manipulating behavior via rewards. The games are still fun - that's the reward! I'd believe the real criticism here is that it is "empty fun", or "empty dopamine", that doesn't offer any additional value or sense of fulfillment. I don't think that's inherently bad in moderation, although it can become a problem if the game is manipulating you for profit-seeking, or if you play the game to the detriment of the other parts of your life.

Another interpretation of incremental games as parodies comes from several mainstream incremental games that are also parodies of capitalism, such as cookie clicker and adventure capitalist. It's a very common framework for incremental games to portray the ever-increasing numbers as an insatiable hunger for resources, like the ones observed within capitalism. Therefore, these games are used as evidence that the genre as a whole is about parody and commentary.

Popular videos on incremental games that portray the genre as parodies are Why Idle games make good satire, and how it was ruined. and Bad Game Design - Clicker Games. You may also be interested in this response to the latter video from a fan of incremental games: BadGood Game Design - Clicker Games.

I think that this definition ultimately ascribes a motive to the genre as a whole that only happens to apply to some of the more mainstream titles. There certainly are incremental games commenting on different things, including the genre itself as in the case of The Prestige Tree Classic, The Ascension Tree, or Omega Layers, but certainly not all. And of course, not all games that comment on something or parody something are incremental games! Additionally, a very large majority of incremental games are mobile games using these manipulative strategies to get players to spend as much money as possible - hell, Adventure Capitalist is ostensibly a critique on capitalism but features microtransactions and gameplay that manipulates you into buying them! These profit-seeking incremental games certainly belong within the genre but are hardly parodies when they too use manipulation to serve their interests. Also, from my own anecdotal experience, those who use this definition seem to do so from a fairly surface-level familiarity with the genre, and often in the context of criticizing the genre or the fans thereof.

Incrementals as NGU ​

Another broad definition often used is that incremental games are games where the focus of the game is "numbers going up". This definition proposes that other genres simply use increasing numbers as a means to an end, but incremental games uniquely only care about the numbers themselves going up. Put another way, it implies there should be no narrative justification for the numbers going up other than "why shouldn't they be going up?"

While this definition is common because it feels easy to understand, it is difficult to formally define. Often phrases are used to describe games using this framework, such as having an "exaggerated sense of progression" or "big" numbers. These terms are vague and don't demonstrate an actual threshold between non-incrementals and incrementals. Most games have a sense of progression, so when is it "exaggerated"? How big are "big" numbers? Most notably, RPGs that are typically not considered incrementals will often pass this definition.

Additionally, a lot of incrementals tend to have some theme guiding the gameplay, or at least the names of mechanics. This makes the line blurred between when numbers are going up for their own sake versus for a contextual reason. I believe this point is best illustrated that, while most RPGs are not considered incremental games, there is a sub-genre of "incremental RPGs" that typically relates to RPGs that perform combat automatically. This definition of incremental games does not support RPGs and "incremental RPGs" being on distinct sides of the line if the only difference between them is manual vs automatic combat.

Incrementals as Strategies

This is a rarer interpretation, but there are similarities between incremental games and strategy games, implying incrementals might just be a sub-genre of strategy games. By this approach, incremental games would be defined by their relation to strategy games, and how they involve player strategy. Incremental games are often large optimization problems - above all else, the actual gameplay the player is performing is deciding what to do next. The consequences of wrong decisions are typically more lenient in incremental games - such as just not making optimal progress - but they certainly get complex.

So if we accept the premise that incrementals could fall under strategy, we still need to define what makes a strategy game an incremental versus some other strategy sub-genre. This is a bit tricky due to one particular sub-genre of strategy games: Factory Builders.

Factory builders, such as Factorio or Satisfactory, are games about gaining ever increasing resources, optimizing production, and expanding more and more. That... sounds pretty similar, doesn't it? In fact, there's been some debate on whether factory builders would fall under the "incremental" umbrella. I think it's safe to say the two are certainly related, and probably have quite a bit of overlap in playerbase.

Roguelites as Incrementals? ​

Earlier on, I mentioned reset mechanics shouldn't be used in the definition because that could make all roguelites incrementals... But what if it does? A lot of incrementals can be described as games with a strong sense of progression, often with layers of meta-progression. Roguelites fit that bill to a T. What would make roguelites not incremental? I honestly don't think there's a good explanation here, but many fans of incremental games will state they do believe the two genres to be unrelated, even if there's a significant overlap between their player bases due to having similar appealing traits.

At this point, it'd be appropriate to consider what part of the definition of roguelites precludes them from also being incrementals, but that reveals a new problem: What are roguelites? They're usually defined as rogue_likes with meta-progression, but that just pushes the problem back a step: Incrementals aren't the only genre to have difficulties defining themselves, it seems! Roguelikes are another genre where the community argues over the formal definition of their genre, although that means we can borrow from their process of coming to a consensus, and maybe come across a viable definition for incremental games.

The Berlin Interpretation ​

By far the most popular way of defining roguelikes is the "Berlin Interpretation", which acknowledged the diversity of games within the genre and argued the definition should not be based on any ideals about what the genre ought to be, but rather defined by "its canon". They argued there are a handful of games that can be used to define the canon for roguelikes, and from those games, a list of factors can be derived to determine a game's "roguelikeness". The more factors a game has, the more of a roguelike it is. This strategy is very lenient, allowing a game to not present any specific factor so long as it shows enough, and accounts for the blurriness of any genre definition by not explicitly stating how many factors a game must have to qualify as a definite roguelike.

I believe this strategy for defining genres can be applied to other genres as well. A handful of games can be argued to be the incremental games canon, and a list of factors derived from them can be used to judge any game based on its "incrementalness". I'll propose such a canon and list of factors here, but by no means should it be considered the end-all-be-all.

Note: The "Temple of the roguelike", an authority within the genre, has since replaced the Berlin Interpretation with a new set of factors here: https://blog.roguetemple.com/what-is-a-traditional-roguelike/

The Incremental Games Canon ​

Alright, time to get controversial. Up til now, I've been trying my best to stay objective and analytical, but now it's time to start making some opinionated decisions. Here is a list of games I think could justifiably make up an Incremental Games Canon:

I chose a variety of games here, biasing towards newer games, purposefully to avoid making a narrow or "traditional" definition. The genre is growing and shouldn't be constrained by the traits of the early popular titles. A lot of these could easily be replaced with other games that are mechanically congruent, so ultimately I'm sure if you asked 10 people for their canon list you'd just get 10 different answers, but I think this should sufficiently allow us to determine what factors make a game have higher "incrementalness".

The Paradigm Shift ​

The Paradigm Shift is probably the highest possible value factor for an incremental. It's so common that for a while people referred to incrementals that exhibit this trait as "unfolding" games, to the point of trying to replace the term incremental due to their popularity. Paradigm shifts refer to when the gameplay significantly changes. There are too many examples to list here, but notably, every single reset mechanic is typically going to be a paradigm shift. Examples of games with paradigm shifts that aren't tied to reset mechanics include Universal Paperclips and A Dark Room.

There are many reasons for the appeal of paradigm shifts. Oftentimes each mechanic builds on top of the existing mechanics, increasing the complexity of the game in steps so the player can follow along. They provide a sense of mystery, with the player anticipating what will happen next. They shake up the gameplay before it gets too stale - allowing the game to entertain for longer before the sense of Guide to Incrementals/What is Content? dissipates. Of the canon games selected above, I would argue every single one contains a paradigm shift (although I could see someone disagreeing with that statement wrt Increlution).

I should take a moment to say that while I'm hyping up this specific factor, we cannot just reduce the genre definition to "does it have paradigm shifts". Many games have paradigm shifts that are not incremental, so it's just an indicator of incrementalness. Additionally, it can become quite hard to determine how large of a shift is a "paradigm" shift. Take, for example, any game with a skill tree. In some games, each skill node might have a large impact on how you play with the game, and qualify as a paradigm shift for some players. In other games, each skill node might just be a small percentage modifier on some stat that doesn't really impact much more than a slight bias towards an already established mechanic that's newly buffed. Every single canon game may show that it's common amongst incremental games, but could just as easily indicate that they're common in games in general.

High-Value Factors ​

I won't take as long to discuss the high and low-value factors, as you've already seen most of them brought up earlier on this page. As a reminder, a game does NOT need all of these to be an incremental game, but these are factors that each indicate a strong possibility the game is an incremental, so having several of these means they probably are. These factors apply to most of the canon incremental games.

"Pure UI" Display. Incrementals typically have a textual presentation of the game state - there isn't a visual representation of the entities within the game. The interface is closer to what would be just the UI of a game in another genre or the control panel of a plane. If there is a visual representation, the player is often still interacting with non-diegetic game elements.

Reduced Consequences. Incrementals tend to have reduced repurcussions for misplaying. They very rarely have fail states, where often the largest consequence is simply not progressing - never losing progress.

Optimization Problems. The predominant gameplay of incrementals is typically solving optimization problems, from deciding which purchase to save up for to reasoning and deciding between different mutually exclusive options the game presents.

Resource Management. Incrementals tend to have a lot of resources within the game to keep track of.

Low-Value Factors ​

These are low-value factors, meaning they aren't as strongly correlated with incremental games. Incremental games may have none of these, and non-incrementals may have several of these - if a game only has low-value factors, they're probably not an incremental.

Fast Numeric Growth. Numbers in incremental games tend to grow faster than in other genres. There are more instances of superlinear growth. The larger the numbers get, the stronger of a signal this factor is.

Automation. As an incremental game progresses, the player often no longer has to deal with earlier mechanics, by having them either happen automatically or otherwise be replaced with an alternative that requires less player interaction.

Goal-Oriented. Incrementals are often heavily reliant on extrinsic motivation to guide the player. Typically this is through some sort of in-game goal to work towards, such as a certain amount of a resource being required to unlock or purchase something new.

Waiting is a Mechanic. In incremental games, the player may come across times where there is no action they can take, and the game will progress automatically instead. The player must wait for some amount of this automatic progress to occur before they can resume interaction with the game.

Are Roguelites Incrementals? ​

Having made our variation of the Berlin Interpretation for incremental games, we can compare it to the Berlin Interpretation to determine if there's enough overlap that any game that "passes" the Berlin Interpretation would also pass the incremental variant. That is to say, whether any roguelite would also be considered an incremental game.

The meta-progression of an incremental game could arguably be considered a paradigm shift, and certainly adds some resource management. Goal-oriented would probably also apply. I think anything other than those would be a stretch, and in my opinion that just isn't enough to qualify. To be totally honest, I was never expecting to conclude otherwise though 😉

Sub-Genres ​

There are some trends in incremental games that go beyond just being a commonly used mechanic, such that they deeply affect the rest of the game design. These trends can be used to determine sub-genres within the incremental games umbrella:

Loops games are a sub-genre defined by having a core mechanic related to a loop, where the player is deciding the actions taken per loop. Notable examples include Idle Loops, Stuck in Time, Cavernous II, and Increlution. You may also argue Groundhog Life and Progress Knight fall into this sub-genre.

ITRTG-like games are a sub-genre defined by having a core mechanic based on clearing increasingly difficult battles and often tend to have a lot of different mechanics to become progressively stronger. Notable examples include Idling to Rule the Gods, NGU Idle, and Wizard and Minion Idle.

Polynomial Growth games are a sub-genre defined by having a core mechanic related to a higher degree polynomial. Notable examples include the base layer of Antimatter Dimensions and Swarm Simulator.

Upgrades Games is a category popular on flash games websites that featured games focused on buying upgrades that would allow you to attain more currency in some sort of minigame that would earn you more money to buy more upgrades, which I'd argue now belong under the fold of incremental games. Notable examples include the Learn to Fly series and Upgrade Complete.

Cultivation RPGs are a genre of games, books, and anime popular in China that center around being in a fantasy world with characters getting stronger over time. While few of them get translated into English, a fan of incremental games may find the available games interesting.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/guide-to-incrementals/index.html b/garden/guide-to-incrementals/index.html index 6cf6bbd5..a58ad4d4 100644 --- a/garden/guide-to-incrementals/index.html +++ b/garden/guide-to-incrementals/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,9 +22,9 @@
The Paper Pilot

Appearance

Guide to Incrementals ​

343 words, ~2 minute read. Planted -. Last tended to -.

This is a comprehensive guide to Incremental Games, a genre of video games. It will explore defining the genre, why it's appealing, and how to design and build your own incremental game. Along the way will be interactive examples, snippets from other creators, and relevant material to contextualize everything.

Note: This is an incomplete document. I want to keep adding opinions and opposing views from other incremental games developers, and add interactive examples to illustrate various points regarding game design and balancing. Consider this a living document - and see the changelog at the end.

Note: This was made before my switch to a digital garden, and is written as prose. Hope you don't mind!

Why am I making this? ​

That's a good question! What authority do I have to be making this guide? I haven't made the best incremental games, nor the most incremental games, certainly not the most popular ones either. But I do have some formal education in game development, know a lot of incremental game devs (as well as other game devs), and have a passionate interest in ludology, classifying genres, etc. I've also made a couple of incremental games) myself.

If you have any additional questions about my credentials or anything on this site, feel free to reach out!

Ludology ​

Making an Incremental ​

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +. Last tended to +.

This is a comprehensive guide to Incremental Games, a genre of video games. It will explore defining the genre, why it's appealing, and how to design and build your own incremental game. Along the way will be interactive examples, snippets from other creators, and relevant material to contextualize everything.

Note: This is an incomplete document. I want to keep adding opinions and opposing views from other incremental games developers, and add interactive examples to illustrate various points regarding game design and balancing. Consider this a living document - and see the changelog at the end.

Note: This was made before my switch to a digital garden, and is written as prose. Hope you don't mind!

Why am I making this? ​

That's a good question! What authority do I have to be making this guide? I haven't made the best incremental games, nor the most incremental games, certainly not the most popular ones either. But I do have some formal education in game development, know a lot of incremental game devs (as well as other game devs), and have a passionate interest in ludology, classifying genres, etc. I've also made a couple of incremental games) myself.

If you have any additional questions about my credentials or anything on this site, feel free to reach out!

Ludology ​

Making an Incremental ​

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/guide-to-incrementals/navigating-criticism/index.html b/garden/guide-to-incrementals/navigating-criticism/index.html index c3a6b3ef..9857b54c 100644 --- a/garden/guide-to-incrementals/navigating-criticism/index.html +++ b/garden/guide-to-incrementals/navigating-criticism/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Guide to Incrementals/Navigating Criticism ​

841 words, ~5 minute read. Planted . Last tended to -.

Developing games is fun and exciting and teaches a lot of wonderful skills - I enthusiastically encourage anyone with an interest in game development to try it out - and incremental games are a wonderful way to get started. However, there are many challenges young and inexperienced developers have to face, and I think the hardest one - harder than coding, debugging, balancing, etc. - is handling criticism. When you put your heart and soul into a game it is natural to feel very vulnerable. While I think there's a lot communities can do to ensure they're welcoming, positive and constructive with their criticisms, inevitably you will eventually read some, and potentially a lot, of comments that can deeply affect you. No one is immune to this, from young incremental game developers to the largest content creators you can think of. That's why it's important to be able to process and navigate criticism, because ultimately collecting feedback is essential to the journey to becoming a better developer. On this page, we'll explore how to embrace criticism, grow from it, and continue to post your games publicly with confidence.

Reading Feedback ​

Game development is a skill that takes time and practice to get truly great at. Criticism and other constructive feedback are vital to continually improving. It's useful to look at the criticism as solely a tool for improving this game and future games - that is to say, it should never be used against you as a person. Insults towards the developer(s) themselves are never okay and should not be allowed within whatever community you're sharing your works in. If you do come across a comment you interpret as an attack upon your person, you should report it. For other negative comments, try not to internalize them; instead, focus on improving the game. By distancing your own identity from your work emotionally, you can better analyze the game and use the feedback to your advantage.

Not all feedback is made equal, and you don't need to feel compelled to read and obey every piece of feedback you receive. Learn to distinguish between constructive feedback and unhelpful comments. Constructive feedback typically offers specific suggestions for improvement, while unhelpful comments are often vague or hurtful. Prioritize the former and disregard the latter. That said, most feedback you get will not be from game developers, so take specific suggestions with a grain of salt. Determine the actual problem they're experiencing, and design what you believe the best solution to that problem would be, regardless if that's the specific solution the player asked for. And keep in mind, due to different player preferences you'll never satisfy everyone, and you don't need to. Ultimately if even just you find the game fun, then that's a success.

Seeking Feedback ​

When deciding where to share your game, consider the type of players you anticipate getting, and the kind of feedback you can anticipate receiving. Different communities will have different levels of support for learning developers, and certain communities may prefer certain types of games or mechanics. It's important to get a diverse set of feedback focused on players you think will enjoy the specific game you're making.

Collecting feedback from other game developers is incredibly helpful. They've trained themselves to recognize good and bad game design and how to articulate the differences, and from my experience are much more likely to leave positive and constructive comments since they've been in your shoes before! They understand the struggles and can offer guidance and emotional support.

Responding to Feedback ​

Negative feedback can naturally feel like an attack, and it's okay to get angry. However, lashing back is never the appropriate response. It's best to cool off IRL, and keep in mind all the positive comments you've received. There's a concept in Psychology called negative bias that explains how negative feedback tends to stick with us much more prominently than positive feedback, so it's useful to regularly remind yourself of all the positive feedback you've received. Celebrate your successes, no matter how small they may seem - getting a game to a state you can publicly share it with people is an accomplishment in and of itself!

Remember your passion and your initial reasons for getting into game development. The journey will have its ups and downs, but staying true to your vision and passion will keep you motivated.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Developing games is fun and exciting and teaches a lot of wonderful skills - I enthusiastically encourage anyone with an interest in game development to try it out - and incremental games are a wonderful way to get started. However, there are many challenges young and inexperienced developers have to face, and I think the hardest one - harder than coding, debugging, balancing, etc. - is handling criticism. When you put your heart and soul into a game it is natural to feel very vulnerable. While I think there's a lot communities can do to ensure they're welcoming, positive and constructive with their criticisms, inevitably you will eventually read some, and potentially a lot, of comments that can deeply affect you. No one is immune to this, from young incremental game developers to the largest content creators you can think of. That's why it's important to be able to process and navigate criticism, because ultimately collecting feedback is essential to the journey to becoming a better developer. On this page, we'll explore how to embrace criticism, grow from it, and continue to post your games publicly with confidence.

Reading Feedback ​

Game development is a skill that takes time and practice to get truly great at. Criticism and other constructive feedback are vital to continually improving. It's useful to look at the criticism as solely a tool for improving this game and future games - that is to say, it should never be used against you as a person. Insults towards the developer(s) themselves are never okay and should not be allowed within whatever community you're sharing your works in. If you do come across a comment you interpret as an attack upon your person, you should report it. For other negative comments, try not to internalize them; instead, focus on improving the game. By distancing your own identity from your work emotionally, you can better analyze the game and use the feedback to your advantage.

Not all feedback is made equal, and you don't need to feel compelled to read and obey every piece of feedback you receive. Learn to distinguish between constructive feedback and unhelpful comments. Constructive feedback typically offers specific suggestions for improvement, while unhelpful comments are often vague or hurtful. Prioritize the former and disregard the latter. That said, most feedback you get will not be from game developers, so take specific suggestions with a grain of salt. Determine the actual problem they're experiencing, and design what you believe the best solution to that problem would be, regardless if that's the specific solution the player asked for. And keep in mind, due to different player preferences you'll never satisfy everyone, and you don't need to. Ultimately if even just you find the game fun, then that's a success.

Seeking Feedback ​

When deciding where to share your game, consider the type of players you anticipate getting, and the kind of feedback you can anticipate receiving. Different communities will have different levels of support for learning developers, and certain communities may prefer certain types of games or mechanics. It's important to get a diverse set of feedback focused on players you think will enjoy the specific game you're making.

Collecting feedback from other game developers is incredibly helpful. They've trained themselves to recognize good and bad game design and how to articulate the differences, and from my experience are much more likely to leave positive and constructive comments since they've been in your shoes before! They understand the struggles and can offer guidance and emotional support.

Responding to Feedback ​

Negative feedback can naturally feel like an attack, and it's okay to get angry. However, lashing back is never the appropriate response. It's best to cool off IRL, and keep in mind all the positive comments you've received. There's a concept in Psychology called negative bias that explains how negative feedback tends to stick with us much more prominently than positive feedback, so it's useful to regularly remind yourself of all the positive feedback you've received. Celebrate your successes, no matter how small they may seem - getting a game to a state you can publicly share it with people is an accomplishment in and of itself!

Remember your passion and your initial reasons for getting into game development. The journey will have its ups and downs, but staying true to your vision and passion will keep you motivated.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/guide-to-incrementals/what-is-content/index.html b/garden/guide-to-incrementals/what-is-content/index.html index aa3adc1f..fc334656 100644 --- a/garden/guide-to-incrementals/what-is-content/index.html +++ b/garden/guide-to-incrementals/what-is-content/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Guide to Incrementals/What is Content? ​

2356 words, ~13 minute read. Planted . Last tended to -.

If you've been in the incremental games community for any amount of time, you'll quickly find the number one thing players want is content. They want as much of it as possible! The most popular incremental games have tons of content, so they just keep stretching on and on and on, introducing mechanic after mechanic, and players love it. In fact, players seem to value the amount of content over the quality of any specific content. However, there's a bit of a lack of understanding concerning what content is, and I'd like to explore what counts as content, and how we measure it. As a baseline definition, I think "content" can just be described as the parts of the game that engage the player, but to truly understand it we need to contextualize what that means and how it affects the gameplay experience.

To clarify the purpose of this page, my goal is not to get (too) nitpicky or to attack games with "low content". There's nothing wrong with short / low-content games - I'm quite a big fan of those games myself! This is mostly targeted toward those who ask for content and settle for "long" games, and those who want to provide content but want to make sure they're not just artificially inflating the game. Ultimately, I suppose the goal is to just reduce the amount of artificially inflated content for the sake of having a "longer" game.

Interaction ​

I think it should be a fairly non-controversial opinion that time spent solely waiting should not count towards content. That is not including the time reading various effects or making decisions in your head, but rather time spent waiting for a condition to be met so you can re-engage with the game.

That is not to say games should necessarily try to minimize this time. Plenty of games lead towards more infrequent interaction and still get popular. In fact, these games appeal to many gamers who want to have something to check up on in between bursts of working on some other activity. These games seem to have fallen slightly out of fashion amongst modern incremental games, but they're still fully valid. The point I'm trying to make here is just that this time is not content. As an extreme example, a game with no interactions and just a counter that goes up every second could safely be said to have 0 content beyond the time it takes to understand what's going on. If it has a list of "goals" to hit, then the time understanding those goals and a short time after achieving each one could be considered content, but not the idle times in between.

Let's take a look at the opposite end of the spectrum - interaction that is so frequent as to become mindless. This is any mechanic where you need to spam-click something to progress. This may be a more controversial take, but I do not believe this constitutes content either. It does not engage the player, because each consecutive click blends together and they do not individually change the gameplay experience. That is to say, a single click and 100 clicks are not meaningfully different in terms of engaging the player. I'd go as far as to say clicking 100 times would be actively worse, as it's artificially delaying the next piece of actual content, alongside the issues of accessibility and potentially causing RSI.

Repeatable Purchases ​

Imagine an entity in a game that you can purchase multiple times, each time it performs the same thing but for a higher cost. These are incredibly common, from the buildings in cookie clicker to the units in swarm sim to the IP and EP multipliers in antimatter dimensions. However, how much content is each specific purchase? Is it content beyond the first purchase? Does it have diminishing returns? What if you are oscillating between two different repeatable purchases? How much content is lost when you automate) away a repeatable purchase?

I don't want to take too harsh a stance against repeatable purchases. They're useful tools and can be used in a myriad of interesting ways. I feel they do become "stale" or less meaningful content over time, and this happens exponentially quickly the more frequently it can be purchased. A classic example that I believe goes too far is the IP/EP multipliers in Antimatter Dimensions. I would go as far as to say they are a chore and do not provide any meaningful content after you've bought them a couple of times. It's a method for inflating numbers (effectively making every OOM a 5x step instead of 10x), that punishes the player progression-wise whenever they forget to max it again, and eventually gets automated away as a reward to the player for making enough progress.

Just to voice the other side of this argument, Acamaeda defended the IP multiplier as giving the player a "good" upgrade every OOM. I can understand that to a point and need to clarify I'm mainly criticizing IP/EP multipliers after they've been introduced for a while. In fact, I would defend the multipliers for a short while after they're introduced using the same logic I would use to defend normal dimensions as repeatable purchases, at least pre-infinity. There's "content" to be had in looking at what dimensions will become affordable next, and then choosing which to buy amongst those. The IP/EP multipliers, early into infinity or eternity respectively, provide another option that gets put into that mental queue of things to buy with each OOM reached - although the optimal order is often quite trivial and not particularly engaging.

The IP/EP multipliers are not the only repeatable purchase in antimatter dimensions I take offense to. The time dimensions are also a series of repeatable purchases, that are all so similar and static that it doesn't take long before you never need to put any thought into buying them, how much you're buying at once, or the order you buy them in - you just press max all and move on. The entire tab could've been just the max all button and it would not have made a difference beyond the start of the eternity layer. The normal dimensions technically have this problem as well, but since you're constantly getting antimatter the order feels like it has a larger impact and it's more meaningful content, right up until they're automated away. Infinity dimensions are a compromise between the two, so I'm highlighting time dimensions here as the most egregious.

Following Instructions ​

We're getting more and more controversial as we go along! Let's talk about how linear content is not content now (in some circumstances). A trend in incremental games is adding difficulty by adding a web of effects that abstract the true change you can expect from any specific purchase or decision you make. If a game is both linear and sufficiently abstracts the effect of player decisions, then the player will no longer be engaging with the content - they'll simply be clicking on things as they become available. This isn't necessarily a bad thing, as plenty of players don't mind this style of gameplay, but I'd argue once you reach a point where players don't bother reading the effects, those interactions are no longer truly content. Note that unlike the previous qualifiers mentioned, this qualifier is based on the player, and therefore subjective. In effect, it's a spectrum where the more complicated the web of effects becomes, the more likely it is to disengage the player.

This over-complicatedness leading to disengaging the player can also happen from non-linear gameplay. If the web of effects becomes sufficiently complicated and finding the optimal progression route too time-consuming to discover, players will seek out guides from other players who've completed the game. The second they do this, the game effectively becomes linearly following the instructions of the guide and all the above criticisms apply. Similarly to as before, though, this is a spectrum and not everyone will seek out a guide at the same level of difficulty.

Automation

Automation is a staple of the genre, but it has certain implications for the design of the game. Why, when new content is introduced, must the older content be automated away - why is it a chore and it feels rewarding to not have to do it again? Why does the new mechanic have such appeal if we know it too will just be automated away later on, and we'll be happy when that happens? It honestly begs the question of why this framework of introducing content and automating the old content is even enjoyable - and nearly nonexistent in other genres. You're not going to reach a point in a platformer game where they just automate the jumping part - that's the core mechanic! Instead, platformers either add new mechanics that build on the core mechanic or at least re-contextualize the core mechanic. However, in incremental games new content very frequently means replacing older content, as opposed to augmenting it.

Admittedly, the above paragraph ignores the obvious answer that separates incremental games in this regard. These mechanics become chores as their frequency increases. The frequency increases to give a sense of progression, and automation is seen as a reward because it now manages what was becoming unmanageable. The new content then comes in and continues the loop to give a stronger sense of progression. That's all good and a fine justification for automating content instead of building upon the base mechanic. It's also much easier to design, as each layer essentially lets you start over instead of needing to think of ideas that conform to the original core mechanic.

So, what's the problem? Even if this trend is justified and easy to implement, there are some other effects it has on the game design. First off, and this is probably a neutral point, incremental games with this cycle of replacing old mechanics with new ones trend towards more and more abstract and further away from any narrative throughline as they add layers. There are only so many justifications for resetting progress, so if a game wants to have several of these layers they're inevitably going to become generic or increasingly loosely associated with the original content. It's most unfortunate, in my opinion when an interesting or innovative core mechanic gets fully automated once a generic "prestige" layer is unlocked.

A recent example is Really Grass Cutting Incremental, an incremental game about cutting grass (although I'm really criticizing the Roblox game it's based on). Except, it doesn't continue to be about cutting grass. After you buy enough upgrades to increase your grass cutting and level up sufficiently you "prestige", an abstract term that in this case means you reset all your progress to get some currency to buy upgrades that do the same things as the original upgrades, but these won't reset on future prestiges. You'll eventually be able to "crystallize", which means you reset all your progress to get some currency to buy upgrades that do the same things as the original upgrades (and a couple of new ones) and won't reset on future crystallizes. Fine. You'll progress a bit, complete some challenges, and finally get to... grasshop? Grasshopping is this mechanic where you reset all your progress to get some resource that isn't for buying upgrades - this time you just unlock different modifiers on everything based on their amount. You may have gotten the point by now, but there are also "steelie" resets which give you steel for some reason, before unlocking a factory with various machines - none of which are directly tied to cutting grass, and start gathering things like oil and reset for rocket parts and reset to go to space and so on and so on. Throughout all of this there is absolutely no narrative justification or throughline for the direction the game is going, or why cutting grass is still relevant when we're collecting things like rocket parts. I may be going a little hard on GCI, but it is far from alone.

Tips for Developers ​

If you're a developer, by this point you should have a pretty decent idea of how to create "true" content in your game. Here are some other specific tips I'd suggest:

An upgrade that simply unlocks another upgrade trivially isn't content. However, many games have an upgrade that just unlocks a feature, which then has a wait or other requirements before it can be used. Try to make sure when you unlock a feature, there is immediately something to do with the feature - for example, perhaps give them a small amount of the new currency it unlocks, if applicable.

If you don't have a large web of effects, and can definitively say the impact of a purchase is to multiply the gain of the cost currency by N, and the next purchase costs N times the amount of that same currency, then this purchase effectively made no difference and it may have made more sense to just go directly to the next upgrade. That said, having effects based on things like the number of purchases made will quickly invalidate this tip.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

If you've been in the incremental games community for any amount of time, you'll quickly find the number one thing players want is content. They want as much of it as possible! The most popular incremental games have tons of content, so they just keep stretching on and on and on, introducing mechanic after mechanic, and players love it. In fact, players seem to value the amount of content over the quality of any specific content. However, there's a bit of a lack of understanding concerning what content is, and I'd like to explore what counts as content, and how we measure it. As a baseline definition, I think "content" can just be described as the parts of the game that engage the player, but to truly understand it we need to contextualize what that means and how it affects the gameplay experience.

To clarify the purpose of this page, my goal is not to get (too) nitpicky or to attack games with "low content". There's nothing wrong with short / low-content games - I'm quite a big fan of those games myself! This is mostly targeted toward those who ask for content and settle for "long" games, and those who want to provide content but want to make sure they're not just artificially inflating the game. Ultimately, I suppose the goal is to just reduce the amount of artificially inflated content for the sake of having a "longer" game.

Interaction ​

I think it should be a fairly non-controversial opinion that time spent solely waiting should not count towards content. That is not including the time reading various effects or making decisions in your head, but rather time spent waiting for a condition to be met so you can re-engage with the game.

That is not to say games should necessarily try to minimize this time. Plenty of games lead towards more infrequent interaction and still get popular. In fact, these games appeal to many gamers who want to have something to check up on in between bursts of working on some other activity. These games seem to have fallen slightly out of fashion amongst modern incremental games, but they're still fully valid. The point I'm trying to make here is just that this time is not content. As an extreme example, a game with no interactions and just a counter that goes up every second could safely be said to have 0 content beyond the time it takes to understand what's going on. If it has a list of "goals" to hit, then the time understanding those goals and a short time after achieving each one could be considered content, but not the idle times in between.

Let's take a look at the opposite end of the spectrum - interaction that is so frequent as to become mindless. This is any mechanic where you need to spam-click something to progress. This may be a more controversial take, but I do not believe this constitutes content either. It does not engage the player, because each consecutive click blends together and they do not individually change the gameplay experience. That is to say, a single click and 100 clicks are not meaningfully different in terms of engaging the player. I'd go as far as to say clicking 100 times would be actively worse, as it's artificially delaying the next piece of actual content, alongside the issues of accessibility and potentially causing RSI.

Repeatable Purchases ​

Imagine an entity in a game that you can purchase multiple times, each time it performs the same thing but for a higher cost. These are incredibly common, from the buildings in cookie clicker to the units in swarm sim to the IP and EP multipliers in antimatter dimensions. However, how much content is each specific purchase? Is it content beyond the first purchase? Does it have diminishing returns? What if you are oscillating between two different repeatable purchases? How much content is lost when you automate) away a repeatable purchase?

I don't want to take too harsh a stance against repeatable purchases. They're useful tools and can be used in a myriad of interesting ways. I feel they do become "stale" or less meaningful content over time, and this happens exponentially quickly the more frequently it can be purchased. A classic example that I believe goes too far is the IP/EP multipliers in Antimatter Dimensions. I would go as far as to say they are a chore and do not provide any meaningful content after you've bought them a couple of times. It's a method for inflating numbers (effectively making every OOM a 5x step instead of 10x), that punishes the player progression-wise whenever they forget to max it again, and eventually gets automated away as a reward to the player for making enough progress.

Just to voice the other side of this argument, Acamaeda defended the IP multiplier as giving the player a "good" upgrade every OOM. I can understand that to a point and need to clarify I'm mainly criticizing IP/EP multipliers after they've been introduced for a while. In fact, I would defend the multipliers for a short while after they're introduced using the same logic I would use to defend normal dimensions as repeatable purchases, at least pre-infinity. There's "content" to be had in looking at what dimensions will become affordable next, and then choosing which to buy amongst those. The IP/EP multipliers, early into infinity or eternity respectively, provide another option that gets put into that mental queue of things to buy with each OOM reached - although the optimal order is often quite trivial and not particularly engaging.

The IP/EP multipliers are not the only repeatable purchase in antimatter dimensions I take offense to. The time dimensions are also a series of repeatable purchases, that are all so similar and static that it doesn't take long before you never need to put any thought into buying them, how much you're buying at once, or the order you buy them in - you just press max all and move on. The entire tab could've been just the max all button and it would not have made a difference beyond the start of the eternity layer. The normal dimensions technically have this problem as well, but since you're constantly getting antimatter the order feels like it has a larger impact and it's more meaningful content, right up until they're automated away. Infinity dimensions are a compromise between the two, so I'm highlighting time dimensions here as the most egregious.

Following Instructions ​

We're getting more and more controversial as we go along! Let's talk about how linear content is not content now (in some circumstances). A trend in incremental games is adding difficulty by adding a web of effects that abstract the true change you can expect from any specific purchase or decision you make. If a game is both linear and sufficiently abstracts the effect of player decisions, then the player will no longer be engaging with the content - they'll simply be clicking on things as they become available. This isn't necessarily a bad thing, as plenty of players don't mind this style of gameplay, but I'd argue once you reach a point where players don't bother reading the effects, those interactions are no longer truly content. Note that unlike the previous qualifiers mentioned, this qualifier is based on the player, and therefore subjective. In effect, it's a spectrum where the more complicated the web of effects becomes, the more likely it is to disengage the player.

This over-complicatedness leading to disengaging the player can also happen from non-linear gameplay. If the web of effects becomes sufficiently complicated and finding the optimal progression route too time-consuming to discover, players will seek out guides from other players who've completed the game. The second they do this, the game effectively becomes linearly following the instructions of the guide and all the above criticisms apply. Similarly to as before, though, this is a spectrum and not everyone will seek out a guide at the same level of difficulty.

Automation

Automation is a staple of the genre, but it has certain implications for the design of the game. Why, when new content is introduced, must the older content be automated away - why is it a chore and it feels rewarding to not have to do it again? Why does the new mechanic have such appeal if we know it too will just be automated away later on, and we'll be happy when that happens? It honestly begs the question of why this framework of introducing content and automating the old content is even enjoyable - and nearly nonexistent in other genres. You're not going to reach a point in a platformer game where they just automate the jumping part - that's the core mechanic! Instead, platformers either add new mechanics that build on the core mechanic or at least re-contextualize the core mechanic. However, in incremental games new content very frequently means replacing older content, as opposed to augmenting it.

Admittedly, the above paragraph ignores the obvious answer that separates incremental games in this regard. These mechanics become chores as their frequency increases. The frequency increases to give a sense of progression, and automation is seen as a reward because it now manages what was becoming unmanageable. The new content then comes in and continues the loop to give a stronger sense of progression. That's all good and a fine justification for automating content instead of building upon the base mechanic. It's also much easier to design, as each layer essentially lets you start over instead of needing to think of ideas that conform to the original core mechanic.

So, what's the problem? Even if this trend is justified and easy to implement, there are some other effects it has on the game design. First off, and this is probably a neutral point, incremental games with this cycle of replacing old mechanics with new ones trend towards more and more abstract and further away from any narrative throughline as they add layers. There are only so many justifications for resetting progress, so if a game wants to have several of these layers they're inevitably going to become generic or increasingly loosely associated with the original content. It's most unfortunate, in my opinion when an interesting or innovative core mechanic gets fully automated once a generic "prestige" layer is unlocked.

A recent example is Really Grass Cutting Incremental, an incremental game about cutting grass (although I'm really criticizing the Roblox game it's based on). Except, it doesn't continue to be about cutting grass. After you buy enough upgrades to increase your grass cutting and level up sufficiently you "prestige", an abstract term that in this case means you reset all your progress to get some currency to buy upgrades that do the same things as the original upgrades, but these won't reset on future prestiges. You'll eventually be able to "crystallize", which means you reset all your progress to get some currency to buy upgrades that do the same things as the original upgrades (and a couple of new ones) and won't reset on future crystallizes. Fine. You'll progress a bit, complete some challenges, and finally get to... grasshop? Grasshopping is this mechanic where you reset all your progress to get some resource that isn't for buying upgrades - this time you just unlock different modifiers on everything based on their amount. You may have gotten the point by now, but there are also "steelie" resets which give you steel for some reason, before unlocking a factory with various machines - none of which are directly tied to cutting grass, and start gathering things like oil and reset for rocket parts and reset to go to space and so on and so on. Throughout all of this there is absolutely no narrative justification or throughline for the direction the game is going, or why cutting grass is still relevant when we're collecting things like rocket parts. I may be going a little hard on GCI, but it is far from alone.

Tips for Developers ​

If you're a developer, by this point you should have a pretty decent idea of how to create "true" content in your game. Here are some other specific tips I'd suggest:

An upgrade that simply unlocks another upgrade trivially isn't content. However, many games have an upgrade that just unlocks a feature, which then has a wait or other requirements before it can be used. Try to make sure when you unlock a feature, there is immediately something to do with the feature - for example, perhaps give them a small amount of the new currency it unlocks, if applicable.

If you don't have a large web of effects, and can definitively say the impact of a purchase is to multiply the gain of the cost currency by N, and the next purchase costs N times the amount of that same currency, then this purchase effectively made no difference and it may have made more sense to just go directly to the next upgrade. That said, having effects based on things like the number of purchases made will quickly invalidate this tip.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/incremental-social/index.html b/garden/incremental-social/index.html index 76a1267a..82d515a2 100644 --- a/garden/incremental-social/index.html +++ b/garden/incremental-social/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,9 +22,9 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +. Last tended to +.

Referenced by: Federated Identity, /now, Webrings

Tags: My Projects

Incremental Social is a Fediverse website hosted by me!

Made explicitly for the incremental games community

Most notably hosts an instance of Mbin, Forgejo, and Synapse (and Cinny)

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/ivy-road/index.html b/garden/ivy-road/index.html index 1577fba8..1bce8d3c 100644 --- a/garden/ivy-road/index.html +++ b/garden/ivy-road/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,8 +22,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Davey Wreden, Wanderstop

Tags: Davey Wreden

Ivy Road is a indie game studio created by Davey Wreden, Karla Kimonja, and C418

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/kronos/index.html b/garden/kronos/index.html index 5fa4ac83..ce95019a 100644 --- a/garden/kronos/index.html +++ b/garden/kronos/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Kronos ​

158 words, ~1 minute read. Planted . Last tended to -.

Referenced by: V-ecs

Tags: My Projects, Profectus

My largest and most ambitious incremental game I've ever made

  • A magnum opus, of sorts ;P

Still in development, and will be for a long time. I have full intention of completing it, however

An older version, that is built in The Modding Tree, only has the gameplay, and only goes up to Chapter 2, can be played here

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: V-ecs

Tags: My Projects, Profectus

My largest and most ambitious incremental game I've ever made

  • A magnum opus, of sorts ;P

Still in development, and will be for a long time. I have full intention of completing it, however

An older version, that is built in The Modding Tree, only has the gameplay, and only goes up to Chapter 2, can be played here

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/life-is-strange/index.html b/garden/life-is-strange/index.html index cc3b758b..0b711c37 100644 --- a/garden/life-is-strange/index.html +++ b/garden/life-is-strange/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Life is Strange ​

734 words, ~4 minute read. Planted . Last tended to -.

A series of narrative driven video games with a focus on player choices

I really enjoyed the first game and engaged with the community a lot. I would get very emotional playing through the later chapters, and it became one of my favorite games.

Playthroughs I enjoyed:

Around the start of Haley and I's relationship, we'd play through LiS1 on projectors in our's classrooms

The ending ​

I was not a huge fan of the ending of Life is Strange. Of the two endings, one very clearly got a lot more resources spent on it, but I think Max's story has a better conclusion under the other.

In my mind, Max's arc (and major themes of the last chapter) was about learning not to rely on her powers, and to learn to live with the consequences of her actions. To that end, having the game end with her taking responsibility and living with the consequences of such a major event is a fitting thematic conclusion to the game and her character arc. In contrast, the other ending shows Max relying on her powers once again and, in my opinion, portrays Max as having not grown nor learned any lessons throughout the entire series. I think its a disservice this ending got so much more attention, with unique outfits and a song dedicated to it.

Life is Strange: Before the Storm ​

I really enjoyed this story. I didn't get quite as invested, perhaps due to it being a condensed 3 chapters rather than 5, but the characters will still just as amazing, which is what makes LiS so good. The ending didn't have as much of a punch as LiS1 - in fact, the entire back half of episode 3 didn't quite meet the bar in my eyes. At the time, I enjoyed these threads discussing criticisms levied at that part of the game:

Deadbones played through the game here

The Awesome Adventures of Captain Spirit ​

I enjoyed the demo, and it certainly got me hyped for LiS2 (although I would've been regardless). Switching to UE seemed like a really good move, and the comic theme fits the aesthetic of the series well.

Life is Strange 2 ​

Unfortunately, I've only played the first chapter of this game. I wanted to play through it with Haley, but we haven't found time to do so.

LATER Skip the rest of LiS1 and play LiS2 with Haley

Life is Strange: True Colors ​

This game seems interesting, although the power does seem a little funnily close to "has empathy". I haven't had time to play it, but would like to.

Life is Strange: Double Exposure ​

I'm very excited for this game! Returning to Max's story sounds awesome. Although I will say, from the trailer alone it's incredibly obvious what one of the story beats will be: Revealing that the two timelines follow the two disparate endings from LiS1.

This game was announced to come with premium editions that get access to the game earlier

  • I think this is a horrible anti-consumer practice
  • Since this game is narratively driven, it is prone to spoilers
  • They're getting more money from their biggest fans without providing any tangible value to them, other than making the experience worse for everyone who plays but doesn't cough up that money
  • I hope other narratively driven games find other ways to do Video Game Monetization
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

A series of narrative driven video games with a focus on player choices

I really enjoyed the first game and engaged with the community a lot. I would get very emotional playing through the later chapters, and it became one of my favorite games.

Playthroughs I enjoyed:

Around the start of Haley and I's relationship, we'd play through LiS1 on projectors in our's classrooms

The ending ​

I was not a huge fan of the ending of Life is Strange. Of the two endings, one very clearly got a lot more resources spent on it, but I think Max's story has a better conclusion under the other.

In my mind, Max's arc (and major themes of the last chapter) was about learning not to rely on her powers, and to learn to live with the consequences of her actions. To that end, having the game end with her taking responsibility and living with the consequences of such a major event is a fitting thematic conclusion to the game and her character arc. In contrast, the other ending shows Max relying on her powers once again and, in my opinion, portrays Max as having not grown nor learned any lessons throughout the entire series. I think its a disservice this ending got so much more attention, with unique outfits and a song dedicated to it.

Life is Strange: Before the Storm ​

I really enjoyed this story. I didn't get quite as invested, perhaps due to it being a condensed 3 chapters rather than 5, but the characters will still just as amazing, which is what makes LiS so good. The ending didn't have as much of a punch as LiS1 - in fact, the entire back half of episode 3 didn't quite meet the bar in my eyes. At the time, I enjoyed these threads discussing criticisms levied at that part of the game:

Deadbones played through the game here

The Awesome Adventures of Captain Spirit ​

I enjoyed the demo, and it certainly got me hyped for LiS2 (although I would've been regardless). Switching to UE seemed like a really good move, and the comic theme fits the aesthetic of the series well.

Life is Strange 2 ​

Unfortunately, I've only played the first chapter of this game. I wanted to play through it with Haley, but we haven't found time to do so.

LATER Skip the rest of LiS1 and play LiS2 with Haley

Life is Strange: True Colors ​

This game seems interesting, although the power does seem a little funnily close to "has empathy". I haven't had time to play it, but would like to.

Life is Strange: Double Exposure ​

I'm very excited for this game! Returning to Max's story sounds awesome. Although I will say, from the trailer alone it's incredibly obvious what one of the story beats will be: Revealing that the two timelines follow the two disparate endings from LiS1.

This game was announced to come with premium editions that get access to the game earlier

  • I think this is a horrible anti-consumer practice
  • Since this game is narratively driven, it is prone to spoilers
  • They're getting more money from their biggest fans without providing any tangible value to them, other than making the experience worse for everyone who plays but doesn't cough up that money
  • I hope other narratively driven games find other ways to do Video Game Monetization
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/logseq/index.html b/garden/logseq/index.html index 3c803114..17a62600 100644 --- a/garden/logseq/index.html +++ b/garden/logseq/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Command Palettes, This Knowledge Hub

Logseq is an Open Source outlining software

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/matrix/index.html b/garden/matrix/index.html index 51fa0868..4bd38af8 100644 --- a/garden/matrix/index.html +++ b/garden/matrix/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Cinny, Commune, Synapse

Matrix is a protocol for Decentralized messaging

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/mbin/index.html b/garden/mbin/index.html index e36eafd9..7f0d31da 100644 --- a/garden/mbin/index.html +++ b/garden/mbin/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Incremental Social

Mbin is an Open Source Fediverse software

Can show both twitter-style posts and reddit-style threads

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/mtx/index.html b/garden/mtx/index.html index c1a02ae7..0c822fc5 100644 --- a/garden/mtx/index.html +++ b/garden/mtx/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,8 +22,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Premium Currency, Video Game Monetization

Purchaseable items in video games that cost real life currencies

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/my-personal-website/index.html b/garden/my-personal-website/index.html index a904334d..26a18711 100644 --- a/garden/my-personal-website/index.html +++ b/garden/my-personal-website/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,9 +22,9 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +. Last tended to +.

Referenced by: The Small Web

A Personal Websites for myself, available at https://thepaperpilot.org

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/my-projects/index.html b/garden/my-projects/index.html index 8193179e..fca56fce 100644 --- a/garden/my-projects/index.html +++ b/garden/my-projects/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,9 +22,9 @@
The Paper Pilot

Appearance

My Projects ​

190 words, ~1 minute read. Planted -. Last tended to -.

Tagged by: Advent Incremental, Babble Buds, Capture the Citadel, Dice Armor, Game Dev Tree, Incremental Social, Kronos, Opti-Speech, Planar Pioneers, Profectus, V-ecs

I like making games and tools!

Games ​

Tools (and other non-games) ​

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +. Last tended to +.

Tagged by: Advent Incremental, Babble Buds, Capture the Citadel, Dice Armor, Game Dev Tree, Incremental Social, Kronos, Opti-Speech, Planar Pioneers, Profectus, V-ecs

I like making games and tools!

Games ​

Tools (and other non-games) ​

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/nostr/index.html b/garden/nostr/index.html index 0febae85..ee42db7b 100644 --- a/garden/nostr/index.html +++ b/garden/nostr/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Fediverse

Tags: Decentralized

Nostr is a protocol for Federated Social Media

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/open-source/index.html b/garden/open-source/index.html index d5958f53..1aa96077 100644 --- a/garden/open-source/index.html +++ b/garden/open-source/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Advent Incremental, Cinny, Commune, Dice Armor, Forgejo, Game Dev Tree, Logseq, Mbin, Planar Pioneers, Profectus, Synapse, Vitepress, Weird

Projects with the source code publicly accessible

Typically also grants users the right to modify the code and redistribute those changes, depending on the license

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/opti-speech/index.html b/garden/opti-speech/index.html index 799dece7..fa82ab17 100644 --- a/garden/opti-speech/index.html +++ b/garden/opti-speech/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Opti-Speech ​

331 words, ~2 minute read. Planted . Last tended to -.

Tags: My Projects

In college I continued development on the Opti-Speech project, originally built alongside the scientific paper Opti-speech: a real-time, 3d visual feedback system for speech training

The Original Project ​

The Optispeech project involves designing and testing a real-time tongue model that can be viewed in a transparent head while a subject talks — for the purposes of treating speech errors and teaching foreign language sounds. This work has been conducted in partnership with Vulintus and with support from the National Institutes of Health (NIH).

system-architecture-600.jpg

This video shows a talker with WAVE sensors placed on the tongue hitting a virtual target sphere located at the alveolar ridge. When an alveolar consonant is hit (e.g., /s/, /n/, /d/) the sphere changes color from red to green.

This video shows an American talker learning a novel sound not found in English. When the post-alveolar consonant is hit, the target sphere changes color from red to green. Here, the NDI WAVE system serves as input.

My Work ​

As the sole programmer at UT Dallas Speech Production Lab at the time, my changes involved updating to a more modern version of Unity, improving the interface, in general cleaning up tech debt so it can more easily support new features, and added support for additional EMA systems, namely the Carstens AG501.

new-interface.png

In addition, the program now includes documentation and unit tests to improve program stability and maintainability going forward.

documentation.png

unittests.png

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Tags: My Projects

In college I continued development on the Opti-Speech project, originally built alongside the scientific paper Opti-speech: a real-time, 3d visual feedback system for speech training

The Original Project ​

The Optispeech project involves designing and testing a real-time tongue model that can be viewed in a transparent head while a subject talks — for the purposes of treating speech errors and teaching foreign language sounds. This work has been conducted in partnership with Vulintus and with support from the National Institutes of Health (NIH).

system-architecture-600.jpg

This video shows a talker with WAVE sensors placed on the tongue hitting a virtual target sphere located at the alveolar ridge. When an alveolar consonant is hit (e.g., /s/, /n/, /d/) the sphere changes color from red to green.

This video shows an American talker learning a novel sound not found in English. When the post-alveolar consonant is hit, the target sphere changes color from red to green. Here, the NDI WAVE system serves as input.

My Work ​

As the sole programmer at UT Dallas Speech Production Lab at the time, my changes involved updating to a more modern version of Unity, improving the interface, in general cleaning up tech debt so it can more easily support new features, and added support for additional EMA systems, namely the Carstens AG501.

new-interface.png

In addition, the program now includes documentation and unit tests to improve program stability and maintainability going forward.

documentation.png

unittests.png

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/planar-pioneers/index.html b/garden/planar-pioneers/index.html index 5d4452d1..66a13a1d 100644 --- a/garden/planar-pioneers/index.html +++ b/garden/planar-pioneers/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Tags: My Projects, Profectus

Play it here!

An Open Source game designed to show off Profectus' dynamic layer system!

The TV Tropes page on this game mentions some of the cool things about this game

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/pre-order-bonuses/index.html b/garden/pre-order-bonuses/index.html index 67a27f83..7878e367 100644 --- a/garden/pre-order-bonuses/index.html +++ b/garden/pre-order-bonuses/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,8 +22,8 @@
The Paper Pilot

Appearance

Pre-Order Bonuses ​

195 words, ~1 minute read. Planted -.

Referenced by: Video Game Monetization

Pre-order bonuses are benefits given to players who buy a game before it comes out

They primarily serve to benefit the company

  • People commit to buying before the embargo date passes
  • Heuristic of how well it'll sell after launch
  • Slight lead on return on investment
    • More significantly impacts indie studios, who will likely have less cash on hand
  • Companies make deals with storefronts to have exclusive bonuses, to drive customers to said storefronts

Common bonuses:

  • Digital goods:
  • Physical goods:
    • Typically pins, keychains, etc.
    • Typically only included in physical editions of the game
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Video Game Monetization

Pre-order bonuses are benefits given to players who buy a game before it comes out

They primarily serve to benefit the company

  • People commit to buying before the embargo date passes
  • Heuristic of how well it'll sell after launch
  • Slight lead on return on investment
    • More significantly impacts indie studios, who will likely have less cash on hand
  • Companies make deals with storefronts to have exclusive bonuses, to drive customers to said storefronts

Common bonuses:

  • Digital goods:
  • Physical goods:
    • Typically pins, keychains, etc.
    • Typically only included in physical editions of the game
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/premium-currency/index.html b/garden/premium-currency/index.html index 5accf111..d4d85d16 100644 --- a/garden/premium-currency/index.html +++ b/garden/premium-currency/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,8 +22,8 @@
The Paper Pilot

Appearance

Premium Currency ​

167 words, ~1 minute read. Planted -.

Referenced by: Pre-Order Bonuses

A popular form of MTX where instead of receiving a useful item or effect directly, you receive a currency that is then spent on an in game store

Reasons companies use them

  • Abstracts the real world price of items
    • No strict conversion ratio
    • Discounts for bulk purchasing
    • Small amounts given for free based on story progression or watching ads
  • Consolidates smaller purchases into a larger one (decreasing friction of individual purchases)
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Pre-Order Bonuses

A popular form of MTX where instead of receiving a useful item or effect directly, you receive a currency that is then spent on an in game store

Reasons companies use them

  • Abstracts the real world price of items
    • No strict conversion ratio
    • Discounts for bulk purchasing
    • Small amounts given for free based on story progression or watching ads
  • Consolidates smaller purchases into a larger one (decreasing friction of individual purchases)
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/profectus/index.html b/garden/profectus/index.html index 50510c26..7eabe4b5 100644 --- a/garden/profectus/index.html +++ b/garden/profectus/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Profectus ​

183 words, ~1 minute read. Planted . Last tended to -.

Referenced by: Advent Incremental, Planar Pioneers

Tagged by: Advent Incremental, Kronos, Planar Pioneers

Tags: My Projects

Profectus is an Open Source game engine I made, loosely based on The Modding Tree by Acamaeda

Technically it's more of a template for making web games

It centers around using Vue's reactivity and is designed with the intent to not restrain developers into making games that only look or behave "one way"

Games made with Profectus:

  • Everything in this garden tagged with this page!
  • The entries to the Profectus Creation Jam
  • Primordia by Jacorb
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Advent Incremental, Planar Pioneers

Tagged by: Advent Incremental, Kronos, Planar Pioneers

Tags: My Projects

Profectus is an Open Source game engine I made, loosely based on The Modding Tree by Acamaeda

Technically it's more of a template for making web games

It centers around using Vue's reactivity and is designed with the intent to not restrain developers into making games that only look or behave "one way"

Games made with Profectus:

  • Everything in this garden tagged with this page!
  • The entries to the Profectus Creation Jam
  • Primordia by Jacorb
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/social-media/index.html b/garden/social-media/index.html index 5813a6dd..77e42aa0 100644 --- a/garden/social-media/index.html +++ b/garden/social-media/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Social Media ​

193 words, ~1 minute read. Planted . Last tended to -.

Referenced by: Commune, Fediverse

Traditional social media

  • Not Decentralized
    • Can't choose your own rules, sorting methods, data queries, etc.
  • Overrun by scams and ads and influencers

Federated Social Media

  • Partially Decentralized
    • Self hosting is too hard for everyone to do
    • Still subject to instance's moderation, limitations, etc.
  • Users need to pick an instance, associating their identity with one specific group
    • People belong to many groups
    • The person is permanently associated with that one group
    • You have to pick before getting a "trial period" to ensure you actually like that group/instance

My take on an ideal social media Fedi v2

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Commune, Fediverse

Traditional social media

  • Not Decentralized
    • Can't choose your own rules, sorting methods, data queries, etc.
  • Overrun by scams and ads and influencers

Federated Social Media

  • Partially Decentralized
    • Self hosting is too hard for everyone to do
    • Still subject to instance's moderation, limitations, etc.
  • Users need to pick an instance, associating their identity with one specific group
    • People belong to many groups
    • The person is permanently associated with that one group
    • You have to pick before getting a "trial period" to ensure you actually like that group/instance

My take on an ideal social media Fedi v2

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/synapse/index.html b/garden/synapse/index.html index 0a488bf4..7d566897 100644 --- a/garden/synapse/index.html +++ b/garden/synapse/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Incremental Social

Synapse is an Open Source server software for the Matrix protocol

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/the-beginner-s-guide/index.html b/garden/the-beginner-s-guide/index.html index 7d87e6c5..c17479de 100644 --- a/garden/the-beginner-s-guide/index.html +++ b/garden/the-beginner-s-guide/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

The Beginner's Guide ​

162 words, ~1 minute read. Planted . Last tended to -.

Tags: Davey Wreden

My favorite video game of all time, bar none. Created by Davey Wreden

The game broadly comments on the relationship between creators and consumers, and it can apply to all forms of art

  • Perhaps also an important commentary on parasocial relationships

Important analyses:

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Tags: Davey Wreden

My favorite video game of all time, bar none. Created by Davey Wreden

The game broadly comments on the relationship between creators and consumers, and it can apply to all forms of art

  • Perhaps also an important commentary on parasocial relationships

Important analyses:

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/the-cozy-web/index.html b/garden/the-cozy-web/index.html index c0c88936..e7789284 100644 --- a/garden/the-cozy-web/index.html +++ b/garden/the-cozy-web/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

The Cozy Web ​

157 words, ~1 minute read. Planted . Last tended to -.

Referenced by: Digital Gardens, The Small Web

The Cozy Web is an extension of the dark forest theory of the Internet

It refers to the part of the web that is not web indexable

This part of the web is known for not typically having ads or marketers

Popularized by this article written by Maggie Appleton, who has also written a lot about Digital Gardens

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Digital Gardens, The Small Web

The Cozy Web is an extension of the dark forest theory of the Internet

It refers to the part of the web that is not web indexable

This part of the web is known for not typically having ads or marketers

Popularized by this article written by Maggie Appleton, who has also written a lot about Digital Gardens

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/the-indieweb/amplification/index.html b/garden/the-indieweb/amplification/index.html index 19b878d5..e6b6115f 100644 --- a/garden/the-indieweb/amplification/index.html +++ b/garden/the-indieweb/amplification/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,8 +22,8 @@
The Paper Pilot

Appearance

The IndieWeb/Amplification ​

149 words, ~1 minute read. Planted -.

Refers to reblogging (and re-hosting, sometimes) of someone else's content on your own site

The Internet is a series of webs discusses some ideas and best practices for amplification

To ensure the rehosted content actually came from the claimed author and was not tampered with, all content should be signed using The IndieWeb/Signature Blocks

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Refers to reblogging (and re-hosting, sometimes) of someone else's content on your own site

The Internet is a series of webs discusses some ideas and best practices for amplification

To ensure the rehosted content actually came from the claimed author and was not tampered with, all content should be signed using The IndieWeb/Signature Blocks

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/the-indieweb/signature-blocks/index.html b/garden/the-indieweb/signature-blocks/index.html index 286d6066..ab603e40 100644 --- a/garden/the-indieweb/signature-blocks/index.html +++ b/garden/the-indieweb/signature-blocks/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,8 +22,8 @@
The Paper Pilot

Appearance

The IndieWeb/Signature Blocks ​

107 words, ~1 minute read. Planted -.

A proposal I want to write for posting signed content on your IndieWeb website

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

A proposal I want to write for posting signed content on your IndieWeb website

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/the-small-web/index.html b/garden/the-small-web/index.html index 38bc1e02..58e5582b 100644 --- a/garden/the-small-web/index.html +++ b/garden/the-small-web/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,9 +22,9 @@
The Paper Pilot

Appearance

The Small Web ​

553 words, ~3 minute read. Planted -. Last tended to -.

Referenced by: /now, This Knowledge Hub

Small personal websites created by individuals

  • My Personal Website
  • A callback to how the web was before social media, which homogenized content
  • These pages are diverse and typically won't have ads or marketers

The small web as a whole is Freeform

  • Individual sites may be Chronological still
  • Individual sites link between each other in ways similar to wikis

Browsing the small web ​

  • Follow Webrings or other links from known small websites
  • Marginalia is a search engine for non-commercial content with a "random" button and filters for the small web explicitly (amongst other useful filters!)

Building personal websites ​

IndieWeb contains various resources

  • Their building blocks are standards people can use to help the small web connect with each other consistently
  • They discourage the use of site builders or templates that end up making sites look too homogenized

Free hosting for static websites:

Streams ​

Microsub is a proposed protocol to support this

  • That way, people could use microsub clients to subscribe to multiple streams and get them in one feed
  • Effectively a Federated Social Media that works through personal websites
  • Announce new posts using WebSub

This also allows your personal website to be the one source of truth for your posted content

Multiple streams can be hosted by one site/person so people can subscribe to the kind of content they're interested in

How viable would it be to include chat messages in a stream as well?

  • Perhaps with Chat Glue you could link to specific branches I chatted in

Digital Gardens ​

These sites may be useful to occasionally check up on rather than get notifications from on every post/change

  • Although Garden-RSS could allow those who want to receive notifications to do so

The future ​

The Internet is a series of webs talks about transitioning from our current consolidated web back to the indie web

Why people want the small web ​

There are tools these days that make making websites incredibly easy

  • Back in the day geocities was pretty complicated but a lot of people managed to make pages there
  • Neocities has an extensive page on Learn How to Make Websites!

Hosting can be expensive, but static websites are cheap

  • There are plenty of free options out there for hosting static websites
    • Ideally you'd use some sort of system that is easily transferrable to other servers, and possibly even supports nomadic identities
    • Free hosting for static websites:
    • People are creative and love creating things
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +. Last tended to +.

Referenced by: /now, This Knowledge Hub

Small personal websites created by individuals

  • My Personal Website
  • A callback to how the web was before social media, which homogenized content
  • These pages are diverse and typically won't have ads or marketers

The small web as a whole is Freeform

  • Individual sites may be Chronological still
  • Individual sites link between each other in ways similar to wikis

Browsing the small web ​

  • Follow Webrings or other links from known small websites
  • Marginalia is a search engine for non-commercial content with a "random" button and filters for the small web explicitly (amongst other useful filters!)

Building personal websites ​

IndieWeb contains various resources

  • Their building blocks are standards people can use to help the small web connect with each other consistently
  • They discourage the use of site builders or templates that end up making sites look too homogenized

Free hosting for static websites:

Streams ​

Microsub is a proposed protocol to support this

  • That way, people could use microsub clients to subscribe to multiple streams and get them in one feed
  • Effectively a Federated Social Media that works through personal websites
  • Announce new posts using WebSub

This also allows your personal website to be the one source of truth for your posted content

Multiple streams can be hosted by one site/person so people can subscribe to the kind of content they're interested in

How viable would it be to include chat messages in a stream as well?

  • Perhaps with Chat Glue you could link to specific branches I chatted in

Digital Gardens ​

These sites may be useful to occasionally check up on rather than get notifications from on every post/change

  • Although Garden-RSS could allow those who want to receive notifications to do so

The future ​

The Internet is a series of webs talks about transitioning from our current consolidated web back to the indie web

Why people want the small web ​

There are tools these days that make making websites incredibly easy

  • Back in the day geocities was pretty complicated but a lot of people managed to make pages there
  • Neocities has an extensive page on Learn How to Make Websites!

Hosting can be expensive, but static websites are cheap

  • There are plenty of free options out there for hosting static websites
    • Ideally you'd use some sort of system that is easily transferrable to other servers, and possibly even supports nomadic identities
    • Free hosting for static websites:
    • People are creative and love creating things
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/this-knowledge-hub/index.html b/garden/this-knowledge-hub/index.html index 828e1763..2f99a03e 100644 --- a/garden/this-knowledge-hub/index.html +++ b/garden/this-knowledge-hub/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

This Knowledge Hub ​

226 words, ~1 minute read. Planted . Last tended to -.

Referenced by: Digital Gardens

This is my knowledge hub!

  • It's a Digital Garden collecting my thoughts in varying levels of completeness on basically anything I have interest in

This is not Wikipedia. My thoughts are biased and argumentative, but to the best of my ability based on fact and expertise

I'm writing on something essentially every day

  • Most of my pages are private, especially the journal pages
  • I'll only push updates to this site every so often (not an automatic process)
  • Until something like Garden-RSS exists, we'll have to make do with /changelog which gives a git diff summary for every pushed change, in the form of a The IndieWeb stream as well as an RSS feed

Written in Logseq and rendered with Vitepress

Suggested pages:

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Digital Gardens

This is my knowledge hub!

  • It's a Digital Garden collecting my thoughts in varying levels of completeness on basically anything I have interest in

This is not Wikipedia. My thoughts are biased and argumentative, but to the best of my ability based on fact and expertise

I'm writing on something essentially every day

  • Most of my pages are private, especially the journal pages
  • I'll only push updates to this site every so often (not an automatic process)
  • Until something like Garden-RSS exists, we'll have to make do with /changelog which gives a git diff summary for every pushed change, in the form of a The IndieWeb stream as well as an RSS feed

Written in Logseq and rendered with Vitepress

Suggested pages:

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/v-ecs/index.html b/garden/v-ecs/index.html index c12288a5..13403c23 100644 --- a/garden/v-ecs/index.html +++ b/garden/v-ecs/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

V-ecs ​

297 words, ~2 minute read. Planted . Last tended to -.

Tags: My Projects

screenshot.png

V-ecs (pronounced "Vex") is a Vulkan-based engine I made for making highly moddable games and tools in Lua centered around the ECS design pattern and a work-stealing job system.

The engine works with "worlds", which are collections of systems and renderers. The engine comes with several worlds using systems and renderers I made, including a voxel world, an incremental game, and some test scenes. All of these include systems to render the fps as well as show a debug console by typing the grave key (`). The default world is a title screen that detects any worlds in the "worlds" folder and displays a button for each of them.

debug.png

The original plans were to eventually put it on the steam workshop so people could more easily share their creations amongst each other, but I never became happy enough with the performance of the engine - the parallelization of the lua code involved a lot of overhead that severely limited performance.

Instead, I made a couple of worlds by myself - an infinite procedurally generated voxel world, a simple incremental game, and a more complex incremental game I call "Sands of Time".

sandsoftime.png

The gameplay of Sands of Time was replicated in Kronos Chapter 2!

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Tags: My Projects

screenshot.png

V-ecs (pronounced "Vex") is a Vulkan-based engine I made for making highly moddable games and tools in Lua centered around the ECS design pattern and a work-stealing job system.

The engine works with "worlds", which are collections of systems and renderers. The engine comes with several worlds using systems and renderers I made, including a voxel world, an incremental game, and some test scenes. All of these include systems to render the fps as well as show a debug console by typing the grave key (`). The default world is a title screen that detects any worlds in the "worlds" folder and displays a button for each of them.

debug.png

The original plans were to eventually put it on the steam workshop so people could more easily share their creations amongst each other, but I never became happy enough with the performance of the engine - the parallelization of the lua code involved a lot of overhead that severely limited performance.

Instead, I made a couple of worlds by myself - an infinite procedurally generated voxel world, a simple incremental game, and a more complex incremental game I call "Sands of Time".

sandsoftime.png

The gameplay of Sands of Time was replicated in Kronos Chapter 2!

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/video-game-monetization/index.html b/garden/video-game-monetization/index.html index 09ea9c44..c57dae06 100644 --- a/garden/video-game-monetization/index.html +++ b/garden/video-game-monetization/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,8 +22,8 @@
The Paper Pilot

Appearance

Video Game Monetization ​

220 words, ~1 minute read. Planted -.

Referenced by: Life is Strange

AAA games ​

Cost a lot of money to make, mostly due to the graphics arms race

The price required to make games that expensive earn the cost back would be much higher than the current price of AAA games

Graphics would not justify those higher prices, and AAA studios know this

Techniques AAA games use to make more money without raising the base price:

Free-to-play games ​

Typically utilize MTX and ads in order to profit

Indie developers ​

Trying to make a sustainable living is hard

The industry is packed with lots of competition

I don't blame them for their monetization

Ethical game monetization ​

Requirements:

  • Free demo
  • Paid base game
  • No MTX
  • Paid content expansions
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Life is Strange

AAA games ​

Cost a lot of money to make, mostly due to the graphics arms race

The price required to make games that expensive earn the cost back would be much higher than the current price of AAA games

Graphics would not justify those higher prices, and AAA studios know this

Techniques AAA games use to make more money without raising the base price:

Free-to-play games ​

Typically utilize MTX and ads in order to profit

Indie developers ​

Trying to make a sustainable living is hard

The industry is packed with lots of competition

I don't blame them for their monetization

Ethical game monetization ​

Requirements:

  • Free demo
  • Paid base game
  • No MTX
  • Paid content expansions
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/vitepress/index.html b/garden/vitepress/index.html index 2957ce96..38bf7f0e 100644 --- a/garden/vitepress/index.html +++ b/garden/vitepress/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: This Knowledge Hub

Vitepress is an Open Source static site generator

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/wanderstop/index.html b/garden/wanderstop/index.html index a4b5ebd6..2d20fb1f 100644 --- a/garden/wanderstop/index.html +++ b/garden/wanderstop/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -26,8 +22,8 @@
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Tags: Davey Wreden

Wanderstop is the first game by Ivy Road. It's a narrative focused cozy game

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/webrings/index.html b/garden/webrings/index.html index a63a4efc..fc233966 100644 --- a/garden/webrings/index.html +++ b/garden/webrings/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Webrings ​

234 words, ~1 minute read. Planted . Last tended to -.

Referenced by: The Small Web

A collection of Personal Websites that link to each other

  • These websites are all endorsing each other
  • They form a network of related sites readers might be interested in
  • Built on human trust rather than algorithms

Commune has a vision for modern webrings

  • Have communities set up matrix spaces for chatting
  • Multiple spaces can contain the same room
  • Related communities can share a room about a relevant topic
    • e.g. a bunch of game development libraries shared a "Game Design" room
  • This allows smaller communities to grow from cross-pollinating with other related communities
  • Could Incremental Social host a shared "Incremental Games" room?
    • How to bridge one channel to multiple discord servers, since that's where most incremental games communities are
    • Would this be appealing to already large communities?
    • Would this be overwhelming to smaller communities?
    • Who would moderate?
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: The Small Web

A collection of Personal Websites that link to each other

  • These websites are all endorsing each other
  • They form a network of related sites readers might be interested in
  • Built on human trust rather than algorithms

Commune has a vision for modern webrings

  • Have communities set up matrix spaces for chatting
  • Multiple spaces can contain the same room
  • Related communities can share a room about a relevant topic
    • e.g. a bunch of game development libraries shared a "Game Design" room
  • This allows smaller communities to grow from cross-pollinating with other related communities
  • Could Incremental Social host a shared "Incremental Games" room?
    • How to bridge one channel to multiple discord servers, since that's where most incremental games communities are
    • Would this be appealing to already large communities?
    • Would this be overwhelming to smaller communities?
    • Who would moderate?
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/garden/weird/index.html b/garden/weird/index.html index 3d64cdbc..563d0471 100644 --- a/garden/weird/index.html +++ b/garden/weird/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
The Paper Pilot

Appearance

Weird ​

220 words, ~1 minute read. Planted . Last tended to -.

Referenced by: Commune, Fedi v2, The Small Web

Weird is an Open Source project by the Commune team currently in development

Aims to make creating Personal Websites with Federated Identity available to everyone

  • Also plans on having paid tiers for giving people access to single user instances of various Fediverse tools

Long term, Weird wants to build a new better fediverse

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

Referenced by: Commune, Fedi v2, The Small Web

Weird is an Open Source project by the Commune team currently in development

Aims to make creating Personal Websites with Federated Identity available to everyone

  • Also plans on having paid tiers for giving people access to single user instances of various Fediverse tools

Long term, Weird wants to build a new better fediverse

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/guide-to-incrementals/design/criticism/index.html b/guide-to-incrementals/design/criticism/index.html index 41070ec7..e893d489 100644 --- a/guide-to-incrementals/design/criticism/index.html +++ b/guide-to-incrementals/design/criticism/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
The Paper Pilot

Appearance

Guide to Incrementals/Navigating Criticism ​

Developing games is fun and exciting and teaches a lot of wonderful skills - I enthusiastically encourage anyone with an interest in game development to try it out - and incremental games are a wonderful way to get started. However, there are many challenges young and inexperienced developers have to face, and I think the hardest one - harder than coding, debugging, balancing, etc. - is handling criticism. When you put your heart and soul into a game it is natural to feel very vulnerable. While I think there's a lot communities can do to ensure they're welcoming, positive and constructive with their criticisms, inevitably you will eventually read some, and potentially a lot, of comments that can deeply affect you. No one is immune to this, from young incremental game developers to the largest content creators you can think of. That's why it's important to be able to process and navigate criticism, because ultimately collecting feedback is essential to the journey to becoming a better developer. On this page, we'll explore how to embrace criticism, grow from it, and continue to post your games publicly with confidence.

Reading Feedback ​

Game development is a skill that takes time and practice to get truly great at. Criticism and other constructive feedback are vital to continually improving. It's useful to look at the criticism as solely a tool for improving this game and future games - that is to say, it should never be used against you as a person. Insults towards the developer(s) themselves are never okay and should not be allowed within whatever community you're sharing your works in. If you do come across a comment you interpret as an attack upon your person, you should report it. For other negative comments, try not to internalize them; instead, focus on improving the game. By distancing your own identity from your work emotionally, you can better analyze the game and use the feedback to your advantage.

Not all feedback is made equal, and you don't need to feel compelled to read and obey every piece of feedback you receive. Learn to distinguish between constructive feedback and unhelpful comments. Constructive feedback typically offers specific suggestions for improvement, while unhelpful comments are often vague or hurtful. Prioritize the former and disregard the latter. That said, most feedback you get will not be from game developers, so take specific suggestions with a grain of salt. Determine the actual problem they're experiencing, and design what you believe the best solution to that problem would be, regardless if that's the specific solution the player asked for. And keep in mind, due to different player preferences you'll never satisfy everyone, and you don't need to. Ultimately if even just you find the game fun, then that's a success.

Seeking Feedback ​

When deciding where to share your game, consider the type of players you anticipate getting, and the kind of feedback you can anticipate receiving. Different communities will have different levels of support for learning developers, and certain communities may prefer certain types of games or mechanics. It's important to get a diverse set of feedback focused on players you think will enjoy the specific game you're making.

Collecting feedback from other game developers is incredibly helpful. They've trained themselves to recognize good and bad game design and how to articulate the differences, and from my experience are much more likely to leave positive and constructive comments since they've been in your shoes before! They understand the struggles and can offer guidance and emotional support.

Responding to Feedback ​

Negative feedback can naturally feel like an attack, and it's okay to get angry. However, lashing back is never the appropriate response. It's best to cool off IRL, and keep in mind all the positive comments you've received. There's a concept in Psychology called negative bias that explains how negative feedback tends to stick with us much more prominently than positive feedback, so it's useful to regularly remind yourself of all the positive feedback you've received. Celebrate your successes, no matter how small they may seem - getting a game to a state you can publicly share it with people is an accomplishment in and of itself!

Remember your passion and your initial reasons for getting into game development. The journey will have its ups and downs, but staying true to your vision and passion will keep you motivated.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +
The Paper Pilot

Appearance

Guide to Incrementals/Navigating Criticism ​

Developing games is fun and exciting and teaches a lot of wonderful skills - I enthusiastically encourage anyone with an interest in game development to try it out - and incremental games are a wonderful way to get started. However, there are many challenges young and inexperienced developers have to face, and I think the hardest one - harder than coding, debugging, balancing, etc. - is handling criticism. When you put your heart and soul into a game it is natural to feel very vulnerable. While I think there's a lot communities can do to ensure they're welcoming, positive and constructive with their criticisms, inevitably you will eventually read some, and potentially a lot, of comments that can deeply affect you. No one is immune to this, from young incremental game developers to the largest content creators you can think of. That's why it's important to be able to process and navigate criticism, because ultimately collecting feedback is essential to the journey to becoming a better developer. On this page, we'll explore how to embrace criticism, grow from it, and continue to post your games publicly with confidence.

Reading Feedback ​

Game development is a skill that takes time and practice to get truly great at. Criticism and other constructive feedback are vital to continually improving. It's useful to look at the criticism as solely a tool for improving this game and future games - that is to say, it should never be used against you as a person. Insults towards the developer(s) themselves are never okay and should not be allowed within whatever community you're sharing your works in. If you do come across a comment you interpret as an attack upon your person, you should report it. For other negative comments, try not to internalize them; instead, focus on improving the game. By distancing your own identity from your work emotionally, you can better analyze the game and use the feedback to your advantage.

Not all feedback is made equal, and you don't need to feel compelled to read and obey every piece of feedback you receive. Learn to distinguish between constructive feedback and unhelpful comments. Constructive feedback typically offers specific suggestions for improvement, while unhelpful comments are often vague or hurtful. Prioritize the former and disregard the latter. That said, most feedback you get will not be from game developers, so take specific suggestions with a grain of salt. Determine the actual problem they're experiencing, and design what you believe the best solution to that problem would be, regardless if that's the specific solution the player asked for. And keep in mind, due to different player preferences you'll never satisfy everyone, and you don't need to. Ultimately if even just you find the game fun, then that's a success.

Seeking Feedback ​

When deciding where to share your game, consider the type of players you anticipate getting, and the kind of feedback you can anticipate receiving. Different communities will have different levels of support for learning developers, and certain communities may prefer certain types of games or mechanics. It's important to get a diverse set of feedback focused on players you think will enjoy the specific game you're making.

Collecting feedback from other game developers is incredibly helpful. They've trained themselves to recognize good and bad game design and how to articulate the differences, and from my experience are much more likely to leave positive and constructive comments since they've been in your shoes before! They understand the struggles and can offer guidance and emotional support.

Responding to Feedback ​

Negative feedback can naturally feel like an attack, and it's okay to get angry. However, lashing back is never the appropriate response. It's best to cool off IRL, and keep in mind all the positive comments you've received. There's a concept in Psychology called negative bias that explains how negative feedback tends to stick with us much more prominently than positive feedback, so it's useful to regularly remind yourself of all the positive feedback you've received. Celebrate your successes, no matter how small they may seem - getting a game to a state you can publicly share it with people is an accomplishment in and of itself!

Remember your passion and your initial reasons for getting into game development. The journey will have its ups and downs, but staying true to your vision and passion will keep you motivated.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/guide-to-incrementals/index.html b/guide-to-incrementals/index.html index 3c6871c1..483f9c24 100644 --- a/guide-to-incrementals/index.html +++ b/guide-to-incrementals/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
The Paper Pilot

Appearance

Guide to Incrementals ​

This is a comprehensive guide to Incremental Games, a genre of video games. It will explore defining the genre, why it's appealing, and how to design and build your own incremental game. Along the way will be interactive examples, snippets from other creators, and relevant material to contextualize everything.

Note: This is an incomplete document. I want to keep adding opinions and opposing views from other incremental games developers, and add interactive examples to illustrate various points regarding game design and balancing. Consider this a living document - and see the changelog at the end.

Note: This was made before my switch to a digital garden, and is written as prose. Hope you don't mind!

Why am I making this? ​

That's a good question! What authority do I have to be making this guide? I haven't made the best incremental games, nor the most incremental games, certainly not the most popular ones either. But I do have some formal education in game development, know a lot of incremental game devs (as well as other game devs), and have a passionate interest in ludology, classifying genres, etc. I've also made a couple of incremental games) myself.

If you have any additional questions about my credentials or anything on this site, feel free to reach out!

Ludology ​

Making an Incremental ​

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +
The Paper Pilot

Appearance

Guide to Incrementals ​

This is a comprehensive guide to Incremental Games, a genre of video games. It will explore defining the genre, why it's appealing, and how to design and build your own incremental game. Along the way will be interactive examples, snippets from other creators, and relevant material to contextualize everything.

Note: This is an incomplete document. I want to keep adding opinions and opposing views from other incremental games developers, and add interactive examples to illustrate various points regarding game design and balancing. Consider this a living document - and see the changelog at the end.

Note: This was made before my switch to a digital garden, and is written as prose. Hope you don't mind!

Why am I making this? ​

That's a good question! What authority do I have to be making this guide? I haven't made the best incremental games, nor the most incremental games, certainly not the most popular ones either. But I do have some formal education in game development, know a lot of incremental game devs (as well as other game devs), and have a passionate interest in ludology, classifying genres, etc. I've also made a couple of incremental games) myself.

If you have any additional questions about my credentials or anything on this site, feel free to reach out!

Ludology ​

Making an Incremental ​

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/guide-to-incrementals/ludology/appeal-developers/index.html b/guide-to-incrementals/ludology/appeal-developers/index.html index a26c5b06..fe4629e4 100644 --- a/guide-to-incrementals/ludology/appeal-developers/index.html +++ b/guide-to-incrementals/ludology/appeal-developers/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
The Paper Pilot

Appearance

Guide to Incrementals/Appeal to Developers ​

There are a lot of developers in the incremental games community - the genre seems to draw them in, and convert a lot of players into developers. Let's explore the reasons why this genre appeals to developers.

Incrementals are Easy to Make ​

Compared to other genres, incrementals have quite low expectations. You don't need to make fancy art, or music, or lay things out nicely. If you can make a button and learn the few lines of code necessary to make a number go up, you can make an incremental. This low threshold makes the genre perfect for those who are actively learning to code and haven't developed any gamedev-related skills yet.

Additionally, unlike other genres incrementals are uniquely easy to implement in a normal web page - no need to worry about rendering sprites, moving them around, implementing physics, etc. New developers can just use HTML to add a button, and the game is now available in your browser. You don't need to choose an engine, have admin privileges, or hell for the dedicated you don't even need a computer - there are tools for web development that run in the browser itself, so you can technically use your phone if that's all you have.

Javascript is a perfectly viable language for making web games, whereas other genres are typically going to require using other more difficult languages to learn. There are countless javascript tutorials that start from 0 knowledge of programming, making it incredibly accessible to beginners.

Players are Easy to Find ​

Once you've finished your game and uploaded it on github pages or itch or just copied the link if you're using glitch or replit (all of which are easy to do), anyone can now play the game in their browser. This low barrier to entry has shown tremendous success in getting completely unknown developers to have thousands of plays.

The incremental games community, which mostly centers around r/incremental_games, is always looking for new games and tends to flood any new ones posted with initial players.

Having your games be played can be incredibly motivating, and the community makes it quite clear that you can expect players to play your game. These communities - both for incremental games in general as well as game-specific communities - tend to be very developer friendly as well. A lot of the developers know each other, and welcome new developers with open arms, often with dedicated channels for programming help and discussions.

Monetization ​

I'd like to clarify that everything I've said above mainly applies to web-based incrementals. Incremental games are also incredibly popular on mobile, but with a much different culture and community. Many mobile gamers will still participate in the web-focused community for the culture. This web-focused community has a culture that has been criticized for being "anti-monetization". Ads, IAPs, and similar forms of monetization are often criticized, mainly due to the abundance of completely non-monetized games available from hobbyist developers. There are exceptions, like paid games often being considered fine, like Increlution or Stuck in Time, or donation ware games like kittens game, but even popular games that have IAP see some level of regular criticism, like NGU Idle, Idle Skilling, or Idle Pins. A large part of this can be explained by the community being hyper-aware of the addictive) nature of this genre and its susceptibility to exploiting players.

On mobile, however, monetization is the norm and expected. If an incremental game is available on mobile, it almost certainly will be monetized, and mobile players are aware and accepting of that. Mobile incremental games, due to their addictive nature, tend to make a lot of money. It's very lucrative, and therefore these games are quite abundant on mobile storefronts.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +
The Paper Pilot

Appearance

Guide to Incrementals/Appeal to Developers ​

There are a lot of developers in the incremental games community - the genre seems to draw them in, and convert a lot of players into developers. Let's explore the reasons why this genre appeals to developers.

Incrementals are Easy to Make ​

Compared to other genres, incrementals have quite low expectations. You don't need to make fancy art, or music, or lay things out nicely. If you can make a button and learn the few lines of code necessary to make a number go up, you can make an incremental. This low threshold makes the genre perfect for those who are actively learning to code and haven't developed any gamedev-related skills yet.

Additionally, unlike other genres incrementals are uniquely easy to implement in a normal web page - no need to worry about rendering sprites, moving them around, implementing physics, etc. New developers can just use HTML to add a button, and the game is now available in your browser. You don't need to choose an engine, have admin privileges, or hell for the dedicated you don't even need a computer - there are tools for web development that run in the browser itself, so you can technically use your phone if that's all you have.

Javascript is a perfectly viable language for making web games, whereas other genres are typically going to require using other more difficult languages to learn. There are countless javascript tutorials that start from 0 knowledge of programming, making it incredibly accessible to beginners.

Players are Easy to Find ​

Once you've finished your game and uploaded it on github pages or itch or just copied the link if you're using glitch or replit (all of which are easy to do), anyone can now play the game in their browser. This low barrier to entry has shown tremendous success in getting completely unknown developers to have thousands of plays.

The incremental games community, which mostly centers around r/incremental_games, is always looking for new games and tends to flood any new ones posted with initial players.

Having your games be played can be incredibly motivating, and the community makes it quite clear that you can expect players to play your game. These communities - both for incremental games in general as well as game-specific communities - tend to be very developer friendly as well. A lot of the developers know each other, and welcome new developers with open arms, often with dedicated channels for programming help and discussions.

Monetization ​

I'd like to clarify that everything I've said above mainly applies to web-based incrementals. Incremental games are also incredibly popular on mobile, but with a much different culture and community. Many mobile gamers will still participate in the web-focused community for the culture. This web-focused community has a culture that has been criticized for being "anti-monetization". Ads, IAPs, and similar forms of monetization are often criticized, mainly due to the abundance of completely non-monetized games available from hobbyist developers. There are exceptions, like paid games often being considered fine, like Increlution or Stuck in Time, or donation ware games like kittens game, but even popular games that have IAP see some level of regular criticism, like NGU Idle, Idle Skilling, or Idle Pins. A large part of this can be explained by the community being hyper-aware of the addictive) nature of this genre and its susceptibility to exploiting players.

On mobile, however, monetization is the norm and expected. If an incremental game is available on mobile, it almost certainly will be monetized, and mobile players are aware and accepting of that. Mobile incremental games, due to their addictive nature, tend to make a lot of money. It's very lucrative, and therefore these games are quite abundant on mobile storefronts.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/guide-to-incrementals/ludology/appeal-gamers/index.html b/guide-to-incrementals/ludology/appeal-gamers/index.html index fd93f057..3f67041f 100644 --- a/guide-to-incrementals/ludology/appeal-gamers/index.html +++ b/guide-to-incrementals/ludology/appeal-gamers/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
The Paper Pilot

Appearance

Guide to Incrementals/Appeal to Players ​

This is something that has been discussed and analyzed by many people, and to some extent, I feel like everything that can be said on the topic already has. However, a lot of these analyses are from the perspective of those with not as much experience and involvement within the genre as I'd argue would be necessary for a fully contextualized answer. I recently watched a video about Vampire Survivors, which has since been taken down due to drawing negative attention, which made me think about some interesting arguments about what games are, and what makes them good. The video's argument that "Vampire Survivors is not a video game" mirrors a claim by the developer of Cookie Clicker that his games are "non-games". Using Vampire Survivors and the video made on it as a framework, I'll be answering why incremental games appeal to players. Since the video has been taken down, I'll do my best to contextualize and generalize the arguments of the video without requiring the reader to watch it. For what it's worth, while I disagreed with the video I actually liked a lot of the way it went about thinking about games, and I consider this a continuation of that discussion.

Numbers Going Up ​

This is a very common response to why people enjoy incremental games, although it's not one I find compels me personally, and I suspect it might be a stand-in for progression) or Guide to Incrementals/What is Content?. But reportedly, some people do just like seeing big numbers. I must reiterate I suspect the actual cause is seeing big numbers in context though - if you start at 1e1000 of a currency and get to 1e1001, that isn't going to feel as satisfying as going from 1e10 to 1e100, and in any case, I don't think a button that just adds a zero to your number will feel quite satisfying - I believe its the sense of having made progress, and comparing where you are to where you started and feeling like you've earned your way here that is enjoyable.

Progression

Vampire Survivors can be argued to have a comparatively low depth to its combat compared to many other games. I'd argue it has sufficient depth and more than someone might expect who has only played the game for a short while, but it still definitely gets beat out by many other combat-focused games. Instead, a lot of the progression in Vampire Survivors comes from a meta-progression system by which base stats are increased by spending a currency that persists between runs. While it is technically possible to win without this meta-progression system, and indeed in many roguelikes players like to challenge themselves by beating the game without any meta-progression, the criticism can be made that meta-progression de-emphasizes player skill by making it less important to have to beat the game. Certainly, in incremental games, it is often literally impossible to complete a game without taking advantage of the meta-progression systems. I'd argue this does not detract from the game, however, and is actually a part of what makes incremental games, and roguelikes, enjoyable to many players: meta-progression augments the increases in skill the player is naturally gaining as they play. In effect, it's not replacing the skill increase, but exaggerating it to make it feel more real to the player.

Note: There is also a lot of progression from exploring the mechanics and discovering synergies, unlocking new weapons or playable characters, etc. That just isn't as relevant to this discussion, but it does make up a lot of the appeal of the game.

Effortlessness ​

Incremental games are so easy, a lot of them even have you progress while you're not playing! Part of the appeal is being able to feel like you're making progress while doing something actually productive - multitasking, in a way. In this sense, the game is more of a fidget toy - not something to think hard about and play actively, but something to click a few buttons every so often while you're paying attention to a lecture or studying or working. Of course, not all incremental games lend themselves to being played this way - it's specifically "idle" games that work like this. These are games that take an incredibly long amount of time to see all the content, stretching it as thin as possible, but they aren't expecting you to be sitting at your device playing it the entire time. They expect you to leave and come back later to make a bit of progress and repeat the cycle.

If you look at the higher-level play of most games, you'll see them perform difficult feats with ease and speed. They'll achieve a "flow state" that takes all their knowledge and experience of the game and uses it to play the game as instinctively as possible. It's incredible to watch things like Slay the Spire speed runs or competitive DDR-likes. I'd argue the goal of a lot of games with a competitive scene is to get so good that the game becomes effortless. In that sense, a game that allows you to reach that point earlier isn't any less legitimate, but rather lowers the barrier to entry by allowing more people to get "really good" at the game. And to be clear, Vampire Survivors and (most) incremental games aren't trivially easy - they, and to an extent, every game will have some level of learning and improvement over time.

Addiction

A lot of these reasons for why incremental games appeal may have reminded you of why gambling appeals to people, particularly those prone to addiction. Indeed, incremental games are quite often criticized for their similarity to a skinner box. Some have gone as far as to say incremental games as a genre are commenting that all games are skinner boxes). The argument goes that some games are not fun, but rather condition players into continuing to play without actually getting anything from the experience. When tied to real-world money this is seen as predatory, and to a lesser extent, even free games may be feeding the addictive sides of people and making them more prone to seek out gambling or micro-transaction heavy games.

While incremental games can be fun and even healthy in certain contexts, they can exacerbate video game addiction more than other genres. If you feel like playing incremental games is taking priority over other things in your life, or manipulating your sleep schedule, it may be prudent to seek help. See r/StopGaming for resources.

Since incremental games are often built on extrinsic motivations in the form of progression systems, it's hard to argue whether players continue to play because they are enjoying the gameplay, or if they are just conditioned to keep doing it because the game keeps rewarding them. Unfortunately, it can often feel like it's the latter, as there isn't typically anything compelling about the "gameplay" of clicking a button and waiting. There may be a significant overlap between those who enjoy incremental games and those who are most prone to addiction, and there are often posts on r/incremental_games about someone either struggling with or overcoming video game addiction.

Strategy ​

Incremental games could be considered a subset of strategy games), and inherit the appeals of strategy games. This includes the appeal of feeling like you've found a good solution to a puzzle, or that you're learning more about the game and are improving at making decisions within it. This applies to Vampire Survivors specifically, where you're learning about evolutions and synergies and what kinds of enemies can spawn under what conditions, and how best to handle them.

Note that strategy games are not all the same difficulty, as well. Vampire Survivors is still easier to play than Starcraft 2, and Cookie Clicker is probably somewhere in between (once you progress sufficiently). Vampire Survivors being so successful may indicate that "easier" strategies may have their separate appeal to harder strategy games - players like to feel smart and that they figured the game out and have optimized or mastered it, and the game being easier doesn't detract from that sense of accomplishment as much as it allows more and more users to be able to reach the point where they gain that sense.

Avoiding Staleness ​

Incremental games tend to have "paradigm shifts", where the gameplay changes in a meaningful way at various times throughout the progression of the game. These upset and change the gameplay loop, which helps keep them from stagnating. This constant "freshness" to the gameplay can keep players engaged for longer, compared to a game with a repetitive and static gameplay loop.

Good Game Design ​

Incremental games tend to show their game design "plainly", so it's more readily apparent if a game has good game design while playing, even if you're not looking for it. While different players have different preferences and might enjoy different types of games more than others, there are underlying good and bad game design principles that players will notice the effects of. To be clear, this isn't talking about stuff like big numbers being enjoyable, where I can comfortably agree to disagree with other players. They don't intrinsically make my experience better, but I'm aware of those for whom it does and I won't argue against their feelings. However, the game designer in me does feel like there are some extremely clear-cut examples of good and bad game design philosophies.

Let's start by giving an example of a mechanic I think can be easily and strongly argued is good game design. There are of course many examples, but a personal favorite of mine is how DOOM encourages aggressive gameplay by linking health drops to melee attacks. It has an intended experience it's trying to give the player - immersing themselves as DOOM guy, who would not hide behind cover when low on health - and this mechanic does a great job at encouraging and effectively teaching players to behave properly. This is in sharp contrast to shooters like Call of Duty, which have you regen health passively, encouraging players to hide behind cover and wait after getting hit. Note that I'm not arguing CoD is poorly designed, as the games have different intended experiences. I'm specifically praising DOOM for having a mechanic that does a good job at ensuring the player has that intended experience.

To contrast with an example I think is bad game design, let's talk about shields in souls-likes. This is a bit of a famous example, and I highly recommend this video essay which spends quite a good bit of time on this topic. Essentially, the argument boils down to players of earlier games in the souls games using shields too much - playing slowly, conservatively, and ultimately having less fun. Players wanted to feel safe, so they ended up playing in a way that ruined the experience for them. The developers solved this by removing shields, apart from an intentionally bad one effectively mocking the playstyle, and it did its job at getting players to play more aggressively, and often have more fun.

To bring the conversation back to incrementals, I'm incredibly opinionated on what makes a good incremental game, which I'll discuss in the game design section. Suffice it to say, incremental games rely more on good game design than other genres, due to not having much to distract from bad game design. This helps (although imperfectly - gamers are a bit too tolerant of bad game design!) well-designed games rise to the top within the genre.

Artistic Merit ​

The Vampire Survivors video made me think back to the old arguments about whether games are art, and whether they ought to be. The video seems preoccupied with attaching value to games solely based on their mechanics and the depth thereof, to the point of arguing Vampire Survivors is a waste of time due to its lack of depth. However, even setting aside the fact that if players are having fun then it's not time wasted, I think games can have artistic merit that supersedes the necessity of having (any / engaging / "deep") gameplay. I think the consensus online is that games are definitively art, although I could see the argument that some genres, like incremental games, might be a bit in a grey area. Let's talk about Vampire Survivors first though - It has a story to tell, with lore and many characters, that drive the player and encourage them to continue exploring the game and discovering things within it. Like any walking simulator, it is no less legitimate of a game or the "art" label because of any lack perceived lack of depth. For what it's worth, most art can be consumed with more ease than VS - any painting, movie, sculpture, etc.

A lot of incrementals have a narrative context that can similarly qualify them as art. Cookie Clicker is, as has been pointed out numerous times before, commenting on excess and increasing production beyond any reasonable limits - devolving into increasing production for its own sake. Indeed, a lot of incremental games are written to comment upon various concepts like capitalism or tropes in games, as discussed when defining Incrementals). However, I'd like to argue most incremental games are still art, even without any narrative context. "Art" as a concept is pretty nebulous already, but I personally like those who define it as an act of expression more than any physical result. The creator and the context within which they created the art, and any meaning they put into it, are all relevant and a part of the art itself. Most incremental games have artistic merit from things like why the creator made it, why they chose to make it an incremental game, and why they made any particular design decision. Hell, even if you play through an entire incremental game without a single thought or feeling, that very fact it elicited nothing can itself be artistic merit!

I'm not an art major, and I may be taking a somewhat extreme take on what is art and what has artistic merit, but I'd argue the overall point stands that games, and incremental games specifically, can have artistic merit, which appeals to many gamers.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +
The Paper Pilot

Appearance

Guide to Incrementals/Appeal to Players ​

This is something that has been discussed and analyzed by many people, and to some extent, I feel like everything that can be said on the topic already has. However, a lot of these analyses are from the perspective of those with not as much experience and involvement within the genre as I'd argue would be necessary for a fully contextualized answer. I recently watched a video about Vampire Survivors, which has since been taken down due to drawing negative attention, which made me think about some interesting arguments about what games are, and what makes them good. The video's argument that "Vampire Survivors is not a video game" mirrors a claim by the developer of Cookie Clicker that his games are "non-games". Using Vampire Survivors and the video made on it as a framework, I'll be answering why incremental games appeal to players. Since the video has been taken down, I'll do my best to contextualize and generalize the arguments of the video without requiring the reader to watch it. For what it's worth, while I disagreed with the video I actually liked a lot of the way it went about thinking about games, and I consider this a continuation of that discussion.

Numbers Going Up ​

This is a very common response to why people enjoy incremental games, although it's not one I find compels me personally, and I suspect it might be a stand-in for progression) or Guide to Incrementals/What is Content?. But reportedly, some people do just like seeing big numbers. I must reiterate I suspect the actual cause is seeing big numbers in context though - if you start at 1e1000 of a currency and get to 1e1001, that isn't going to feel as satisfying as going from 1e10 to 1e100, and in any case, I don't think a button that just adds a zero to your number will feel quite satisfying - I believe its the sense of having made progress, and comparing where you are to where you started and feeling like you've earned your way here that is enjoyable.

Progression

Vampire Survivors can be argued to have a comparatively low depth to its combat compared to many other games. I'd argue it has sufficient depth and more than someone might expect who has only played the game for a short while, but it still definitely gets beat out by many other combat-focused games. Instead, a lot of the progression in Vampire Survivors comes from a meta-progression system by which base stats are increased by spending a currency that persists between runs. While it is technically possible to win without this meta-progression system, and indeed in many roguelikes players like to challenge themselves by beating the game without any meta-progression, the criticism can be made that meta-progression de-emphasizes player skill by making it less important to have to beat the game. Certainly, in incremental games, it is often literally impossible to complete a game without taking advantage of the meta-progression systems. I'd argue this does not detract from the game, however, and is actually a part of what makes incremental games, and roguelikes, enjoyable to many players: meta-progression augments the increases in skill the player is naturally gaining as they play. In effect, it's not replacing the skill increase, but exaggerating it to make it feel more real to the player.

Note: There is also a lot of progression from exploring the mechanics and discovering synergies, unlocking new weapons or playable characters, etc. That just isn't as relevant to this discussion, but it does make up a lot of the appeal of the game.

Effortlessness ​

Incremental games are so easy, a lot of them even have you progress while you're not playing! Part of the appeal is being able to feel like you're making progress while doing something actually productive - multitasking, in a way. In this sense, the game is more of a fidget toy - not something to think hard about and play actively, but something to click a few buttons every so often while you're paying attention to a lecture or studying or working. Of course, not all incremental games lend themselves to being played this way - it's specifically "idle" games that work like this. These are games that take an incredibly long amount of time to see all the content, stretching it as thin as possible, but they aren't expecting you to be sitting at your device playing it the entire time. They expect you to leave and come back later to make a bit of progress and repeat the cycle.

If you look at the higher-level play of most games, you'll see them perform difficult feats with ease and speed. They'll achieve a "flow state" that takes all their knowledge and experience of the game and uses it to play the game as instinctively as possible. It's incredible to watch things like Slay the Spire speed runs or competitive DDR-likes. I'd argue the goal of a lot of games with a competitive scene is to get so good that the game becomes effortless. In that sense, a game that allows you to reach that point earlier isn't any less legitimate, but rather lowers the barrier to entry by allowing more people to get "really good" at the game. And to be clear, Vampire Survivors and (most) incremental games aren't trivially easy - they, and to an extent, every game will have some level of learning and improvement over time.

Addiction

A lot of these reasons for why incremental games appeal may have reminded you of why gambling appeals to people, particularly those prone to addiction. Indeed, incremental games are quite often criticized for their similarity to a skinner box. Some have gone as far as to say incremental games as a genre are commenting that all games are skinner boxes). The argument goes that some games are not fun, but rather condition players into continuing to play without actually getting anything from the experience. When tied to real-world money this is seen as predatory, and to a lesser extent, even free games may be feeding the addictive sides of people and making them more prone to seek out gambling or micro-transaction heavy games.

While incremental games can be fun and even healthy in certain contexts, they can exacerbate video game addiction more than other genres. If you feel like playing incremental games is taking priority over other things in your life, or manipulating your sleep schedule, it may be prudent to seek help. See r/StopGaming for resources.

Since incremental games are often built on extrinsic motivations in the form of progression systems, it's hard to argue whether players continue to play because they are enjoying the gameplay, or if they are just conditioned to keep doing it because the game keeps rewarding them. Unfortunately, it can often feel like it's the latter, as there isn't typically anything compelling about the "gameplay" of clicking a button and waiting. There may be a significant overlap between those who enjoy incremental games and those who are most prone to addiction, and there are often posts on r/incremental_games about someone either struggling with or overcoming video game addiction.

Strategy ​

Incremental games could be considered a subset of strategy games), and inherit the appeals of strategy games. This includes the appeal of feeling like you've found a good solution to a puzzle, or that you're learning more about the game and are improving at making decisions within it. This applies to Vampire Survivors specifically, where you're learning about evolutions and synergies and what kinds of enemies can spawn under what conditions, and how best to handle them.

Note that strategy games are not all the same difficulty, as well. Vampire Survivors is still easier to play than Starcraft 2, and Cookie Clicker is probably somewhere in between (once you progress sufficiently). Vampire Survivors being so successful may indicate that "easier" strategies may have their separate appeal to harder strategy games - players like to feel smart and that they figured the game out and have optimized or mastered it, and the game being easier doesn't detract from that sense of accomplishment as much as it allows more and more users to be able to reach the point where they gain that sense.

Avoiding Staleness ​

Incremental games tend to have "paradigm shifts", where the gameplay changes in a meaningful way at various times throughout the progression of the game. These upset and change the gameplay loop, which helps keep them from stagnating. This constant "freshness" to the gameplay can keep players engaged for longer, compared to a game with a repetitive and static gameplay loop.

Good Game Design ​

Incremental games tend to show their game design "plainly", so it's more readily apparent if a game has good game design while playing, even if you're not looking for it. While different players have different preferences and might enjoy different types of games more than others, there are underlying good and bad game design principles that players will notice the effects of. To be clear, this isn't talking about stuff like big numbers being enjoyable, where I can comfortably agree to disagree with other players. They don't intrinsically make my experience better, but I'm aware of those for whom it does and I won't argue against their feelings. However, the game designer in me does feel like there are some extremely clear-cut examples of good and bad game design philosophies.

Let's start by giving an example of a mechanic I think can be easily and strongly argued is good game design. There are of course many examples, but a personal favorite of mine is how DOOM encourages aggressive gameplay by linking health drops to melee attacks. It has an intended experience it's trying to give the player - immersing themselves as DOOM guy, who would not hide behind cover when low on health - and this mechanic does a great job at encouraging and effectively teaching players to behave properly. This is in sharp contrast to shooters like Call of Duty, which have you regen health passively, encouraging players to hide behind cover and wait after getting hit. Note that I'm not arguing CoD is poorly designed, as the games have different intended experiences. I'm specifically praising DOOM for having a mechanic that does a good job at ensuring the player has that intended experience.

To contrast with an example I think is bad game design, let's talk about shields in souls-likes. This is a bit of a famous example, and I highly recommend this video essay which spends quite a good bit of time on this topic. Essentially, the argument boils down to players of earlier games in the souls games using shields too much - playing slowly, conservatively, and ultimately having less fun. Players wanted to feel safe, so they ended up playing in a way that ruined the experience for them. The developers solved this by removing shields, apart from an intentionally bad one effectively mocking the playstyle, and it did its job at getting players to play more aggressively, and often have more fun.

To bring the conversation back to incrementals, I'm incredibly opinionated on what makes a good incremental game, which I'll discuss in the game design section. Suffice it to say, incremental games rely more on good game design than other genres, due to not having much to distract from bad game design. This helps (although imperfectly - gamers are a bit too tolerant of bad game design!) well-designed games rise to the top within the genre.

Artistic Merit ​

The Vampire Survivors video made me think back to the old arguments about whether games are art, and whether they ought to be. The video seems preoccupied with attaching value to games solely based on their mechanics and the depth thereof, to the point of arguing Vampire Survivors is a waste of time due to its lack of depth. However, even setting aside the fact that if players are having fun then it's not time wasted, I think games can have artistic merit that supersedes the necessity of having (any / engaging / "deep") gameplay. I think the consensus online is that games are definitively art, although I could see the argument that some genres, like incremental games, might be a bit in a grey area. Let's talk about Vampire Survivors first though - It has a story to tell, with lore and many characters, that drive the player and encourage them to continue exploring the game and discovering things within it. Like any walking simulator, it is no less legitimate of a game or the "art" label because of any lack perceived lack of depth. For what it's worth, most art can be consumed with more ease than VS - any painting, movie, sculpture, etc.

A lot of incrementals have a narrative context that can similarly qualify them as art. Cookie Clicker is, as has been pointed out numerous times before, commenting on excess and increasing production beyond any reasonable limits - devolving into increasing production for its own sake. Indeed, a lot of incremental games are written to comment upon various concepts like capitalism or tropes in games, as discussed when defining Incrementals). However, I'd like to argue most incremental games are still art, even without any narrative context. "Art" as a concept is pretty nebulous already, but I personally like those who define it as an act of expression more than any physical result. The creator and the context within which they created the art, and any meaning they put into it, are all relevant and a part of the art itself. Most incremental games have artistic merit from things like why the creator made it, why they chose to make it an incremental game, and why they made any particular design decision. Hell, even if you play through an entire incremental game without a single thought or feeling, that very fact it elicited nothing can itself be artistic merit!

I'm not an art major, and I may be taking a somewhat extreme take on what is art and what has artistic merit, but I'd argue the overall point stands that games, and incremental games specifically, can have artistic merit, which appeals to many gamers.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/guide-to-incrementals/ludology/content/index.html b/guide-to-incrementals/ludology/content/index.html index ff43f690..d7ccf06b 100644 --- a/guide-to-incrementals/ludology/content/index.html +++ b/guide-to-incrementals/ludology/content/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
The Paper Pilot

Appearance

Guide to Incrementals/What is Content? ​

If you've been in the incremental games community for any amount of time, you'll quickly find the number one thing players want is content. They want as much of it as possible! The most popular incremental games have tons of content, so they just keep stretching on and on and on, introducing mechanic after mechanic, and players love it. In fact, players seem to value the amount of content over the quality of any specific content. However, there's a bit of a lack of understanding concerning what content is, and I'd like to explore what counts as content, and how we measure it. As a baseline definition, I think "content" can just be described as the parts of the game that engage the player, but to truly understand it we need to contextualize what that means and how it affects the gameplay experience.

To clarify the purpose of this page, my goal is not to get (too) nitpicky or to attack games with "low content". There's nothing wrong with short / low-content games - I'm quite a big fan of those games myself! This is mostly targeted toward those who ask for content and settle for "long" games, and those who want to provide content but want to make sure they're not just artificially inflating the game. Ultimately, I suppose the goal is to just reduce the amount of artificially inflated content for the sake of having a "longer" game.

Interaction ​

I think it should be a fairly non-controversial opinion that time spent solely waiting should not count towards content. That is not including the time reading various effects or making decisions in your head, but rather time spent waiting for a condition to be met so you can re-engage with the game.

That is not to say games should necessarily try to minimize this time. Plenty of games lead towards more infrequent interaction and still get popular. In fact, these games appeal to many gamers who want to have something to check up on in between bursts of working on some other activity. These games seem to have fallen slightly out of fashion amongst modern incremental games, but they're still fully valid. The point I'm trying to make here is just that this time is not content. As an extreme example, a game with no interactions and just a counter that goes up every second could safely be said to have 0 content beyond the time it takes to understand what's going on. If it has a list of "goals" to hit, then the time understanding those goals and a short time after achieving each one could be considered content, but not the idle times in between.

Let's take a look at the opposite end of the spectrum - interaction that is so frequent as to become mindless. This is any mechanic where you need to spam-click something to progress. This may be a more controversial take, but I do not believe this constitutes content either. It does not engage the player, because each consecutive click blends together and they do not individually change the gameplay experience. That is to say, a single click and 100 clicks are not meaningfully different in terms of engaging the player. I'd go as far as to say clicking 100 times would be actively worse, as it's artificially delaying the next piece of actual content, alongside the issues of accessibility and potentially causing RSI.

Repeatable Purchases ​

Imagine an entity in a game that you can purchase multiple times, each time it performs the same thing but for a higher cost. These are incredibly common, from the buildings in cookie clicker to the units in swarm sim to the IP and EP multipliers in antimatter dimensions. However, how much content is each specific purchase? Is it content beyond the first purchase? Does it have diminishing returns? What if you are oscillating between two different repeatable purchases? How much content is lost when you automate) away a repeatable purchase?

I don't want to take too harsh a stance against repeatable purchases. They're useful tools and can be used in a myriad of interesting ways. I feel they do become "stale" or less meaningful content over time, and this happens exponentially quickly the more frequently it can be purchased. A classic example that I believe goes too far is the IP/EP multipliers in Antimatter Dimensions. I would go as far as to say they are a chore and do not provide any meaningful content after you've bought them a couple of times. It's a method for inflating numbers (effectively making every OOM a 5x step instead of 10x), that punishes the player progression-wise whenever they forget to max it again, and eventually gets automated away as a reward to the player for making enough progress.

Just to voice the other side of this argument, Acamaeda defended the IP multiplier as giving the player a "good" upgrade every OOM. I can understand that to a point and need to clarify I'm mainly criticizing IP/EP multipliers after they've been introduced for a while. In fact, I would defend the multipliers for a short while after they're introduced using the same logic I would use to defend normal dimensions as repeatable purchases, at least pre-infinity. There's "content" to be had in looking at what dimensions will become affordable next, and then choosing which to buy amongst those. The IP/EP multipliers, early into infinity or eternity respectively, provide another option that gets put into that mental queue of things to buy with each OOM reached - although the optimal order is often quite trivial and not particularly engaging.

The IP/EP multipliers are not the only repeatable purchase in antimatter dimensions I take offense to. The time dimensions are also a series of repeatable purchases, that are all so similar and static that it doesn't take long before you never need to put any thought into buying them, how much you're buying at once, or the order you buy them in - you just press max all and move on. The entire tab could've been just the max all button and it would not have made a difference beyond the start of the eternity layer. The normal dimensions technically have this problem as well, but since you're constantly getting antimatter the order feels like it has a larger impact and it's more meaningful content, right up until they're automated away. Infinity dimensions are a compromise between the two, so I'm highlighting time dimensions here as the most egregious.

Following Instructions ​

We're getting more and more controversial as we go along! Let's talk about how linear content is not content now (in some circumstances). A trend in incremental games is adding difficulty by adding a web of effects that abstract the true change you can expect from any specific purchase or decision you make. If a game is both linear and sufficiently abstracts the effect of player decisions, then the player will no longer be engaging with the content - they'll simply be clicking on things as they become available. This isn't necessarily a bad thing, as plenty of players don't mind this style of gameplay, but I'd argue once you reach a point where players don't bother reading the effects, those interactions are no longer truly content. Note that unlike the previous qualifiers mentioned, this qualifier is based on the player, and therefore subjective. In effect, it's a spectrum where the more complicated the web of effects becomes, the more likely it is to disengage the player.

This over-complicatedness leading to disengaging the player can also happen from non-linear gameplay. If the web of effects becomes sufficiently complicated and finding the optimal progression route too time-consuming to discover, players will seek out guides from other players who've completed the game. The second they do this, the game effectively becomes linearly following the instructions of the guide and all the above criticisms apply. Similarly to as before, though, this is a spectrum and not everyone will seek out a guide at the same level of difficulty.

Automation

Automation is a staple of the genre, but it has certain implications for the design of the game. Why, when new content is introduced, must the older content be automated away - why is it a chore and it feels rewarding to not have to do it again? Why does the new mechanic have such appeal if we know it too will just be automated away later on, and we'll be happy when that happens? It honestly begs the question of why this framework of introducing content and automating the old content is even enjoyable - and nearly nonexistent in other genres. You're not going to reach a point in a platformer game where they just automate the jumping part - that's the core mechanic! Instead, platformers either add new mechanics that build on the core mechanic or at least re-contextualize the core mechanic. However, in incremental games new content very frequently means replacing older content, as opposed to augmenting it.

Admittedly, the above paragraph ignores the obvious answer that separates incremental games in this regard. These mechanics become chores as their frequency increases. The frequency increases to give a sense of progression, and automation is seen as a reward because it now manages what was becoming unmanageable. The new content then comes in and continues the loop to give a stronger sense of progression. That's all good and a fine justification for automating content instead of building upon the base mechanic. It's also much easier to design, as each layer essentially lets you start over instead of needing to think of ideas that conform to the original core mechanic.

So, what's the problem? Even if this trend is justified and easy to implement, there are some other effects it has on the game design. First off, and this is probably a neutral point, incremental games with this cycle of replacing old mechanics with new ones trend towards more and more abstract and further away from any narrative throughline as they add layers. There are only so many justifications for resetting progress, so if a game wants to have several of these layers they're inevitably going to become generic or increasingly loosely associated with the original content. It's most unfortunate, in my opinion when an interesting or innovative core mechanic gets fully automated once a generic "prestige" layer is unlocked.

A recent example is Really Grass Cutting Incremental, an incremental game about cutting grass (although I'm really criticizing the Roblox game it's based on). Except, it doesn't continue to be about cutting grass. After you buy enough upgrades to increase your grass cutting and level up sufficiently you "prestige", an abstract term that in this case means you reset all your progress to get some currency to buy upgrades that do the same things as the original upgrades, but these won't reset on future prestiges. You'll eventually be able to "crystallize", which means you reset all your progress to get some currency to buy upgrades that do the same things as the original upgrades (and a couple of new ones) and won't reset on future crystallizes. Fine. You'll progress a bit, complete some challenges, and finally get to... grasshop? Grasshopping is this mechanic where you reset all your progress to get some resource that isn't for buying upgrades - this time you just unlock different modifiers on everything based on their amount. You may have gotten the point by now, but there are also "steelie" resets which give you steel for some reason, before unlocking a factory with various machines - none of which are directly tied to cutting grass, and start gathering things like oil and reset for rocket parts and reset to go to space and so on and so on. Throughout all of this there is absolutely no narrative justification or throughline for the direction the game is going, or why cutting grass is still relevant when we're collecting things like rocket parts. I may be going a little hard on GCI, but it is far from alone.

Tips for Developers ​

If you're a developer, by this point you should have a pretty decent idea of how to create "true" content in your game. Here are some other specific tips I'd suggest:

An upgrade that simply unlocks another upgrade trivially isn't content. However, many games have an upgrade that just unlocks a feature, which then has a wait or other requirements before it can be used. Try to make sure when you unlock a feature, there is immediately something to do with the feature - for example, perhaps give them a small amount of the new currency it unlocks, if applicable.

If you don't have a large web of effects, and can definitively say the impact of a purchase is to multiply the gain of the cost currency by N, and the next purchase costs N times the amount of that same currency, then this purchase effectively made no difference and it may have made more sense to just go directly to the next upgrade. That said, having effects based on things like the number of purchases made will quickly invalidate this tip.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +
The Paper Pilot

Appearance

Guide to Incrementals/What is Content? ​

If you've been in the incremental games community for any amount of time, you'll quickly find the number one thing players want is content. They want as much of it as possible! The most popular incremental games have tons of content, so they just keep stretching on and on and on, introducing mechanic after mechanic, and players love it. In fact, players seem to value the amount of content over the quality of any specific content. However, there's a bit of a lack of understanding concerning what content is, and I'd like to explore what counts as content, and how we measure it. As a baseline definition, I think "content" can just be described as the parts of the game that engage the player, but to truly understand it we need to contextualize what that means and how it affects the gameplay experience.

To clarify the purpose of this page, my goal is not to get (too) nitpicky or to attack games with "low content". There's nothing wrong with short / low-content games - I'm quite a big fan of those games myself! This is mostly targeted toward those who ask for content and settle for "long" games, and those who want to provide content but want to make sure they're not just artificially inflating the game. Ultimately, I suppose the goal is to just reduce the amount of artificially inflated content for the sake of having a "longer" game.

Interaction ​

I think it should be a fairly non-controversial opinion that time spent solely waiting should not count towards content. That is not including the time reading various effects or making decisions in your head, but rather time spent waiting for a condition to be met so you can re-engage with the game.

That is not to say games should necessarily try to minimize this time. Plenty of games lead towards more infrequent interaction and still get popular. In fact, these games appeal to many gamers who want to have something to check up on in between bursts of working on some other activity. These games seem to have fallen slightly out of fashion amongst modern incremental games, but they're still fully valid. The point I'm trying to make here is just that this time is not content. As an extreme example, a game with no interactions and just a counter that goes up every second could safely be said to have 0 content beyond the time it takes to understand what's going on. If it has a list of "goals" to hit, then the time understanding those goals and a short time after achieving each one could be considered content, but not the idle times in between.

Let's take a look at the opposite end of the spectrum - interaction that is so frequent as to become mindless. This is any mechanic where you need to spam-click something to progress. This may be a more controversial take, but I do not believe this constitutes content either. It does not engage the player, because each consecutive click blends together and they do not individually change the gameplay experience. That is to say, a single click and 100 clicks are not meaningfully different in terms of engaging the player. I'd go as far as to say clicking 100 times would be actively worse, as it's artificially delaying the next piece of actual content, alongside the issues of accessibility and potentially causing RSI.

Repeatable Purchases ​

Imagine an entity in a game that you can purchase multiple times, each time it performs the same thing but for a higher cost. These are incredibly common, from the buildings in cookie clicker to the units in swarm sim to the IP and EP multipliers in antimatter dimensions. However, how much content is each specific purchase? Is it content beyond the first purchase? Does it have diminishing returns? What if you are oscillating between two different repeatable purchases? How much content is lost when you automate) away a repeatable purchase?

I don't want to take too harsh a stance against repeatable purchases. They're useful tools and can be used in a myriad of interesting ways. I feel they do become "stale" or less meaningful content over time, and this happens exponentially quickly the more frequently it can be purchased. A classic example that I believe goes too far is the IP/EP multipliers in Antimatter Dimensions. I would go as far as to say they are a chore and do not provide any meaningful content after you've bought them a couple of times. It's a method for inflating numbers (effectively making every OOM a 5x step instead of 10x), that punishes the player progression-wise whenever they forget to max it again, and eventually gets automated away as a reward to the player for making enough progress.

Just to voice the other side of this argument, Acamaeda defended the IP multiplier as giving the player a "good" upgrade every OOM. I can understand that to a point and need to clarify I'm mainly criticizing IP/EP multipliers after they've been introduced for a while. In fact, I would defend the multipliers for a short while after they're introduced using the same logic I would use to defend normal dimensions as repeatable purchases, at least pre-infinity. There's "content" to be had in looking at what dimensions will become affordable next, and then choosing which to buy amongst those. The IP/EP multipliers, early into infinity or eternity respectively, provide another option that gets put into that mental queue of things to buy with each OOM reached - although the optimal order is often quite trivial and not particularly engaging.

The IP/EP multipliers are not the only repeatable purchase in antimatter dimensions I take offense to. The time dimensions are also a series of repeatable purchases, that are all so similar and static that it doesn't take long before you never need to put any thought into buying them, how much you're buying at once, or the order you buy them in - you just press max all and move on. The entire tab could've been just the max all button and it would not have made a difference beyond the start of the eternity layer. The normal dimensions technically have this problem as well, but since you're constantly getting antimatter the order feels like it has a larger impact and it's more meaningful content, right up until they're automated away. Infinity dimensions are a compromise between the two, so I'm highlighting time dimensions here as the most egregious.

Following Instructions ​

We're getting more and more controversial as we go along! Let's talk about how linear content is not content now (in some circumstances). A trend in incremental games is adding difficulty by adding a web of effects that abstract the true change you can expect from any specific purchase or decision you make. If a game is both linear and sufficiently abstracts the effect of player decisions, then the player will no longer be engaging with the content - they'll simply be clicking on things as they become available. This isn't necessarily a bad thing, as plenty of players don't mind this style of gameplay, but I'd argue once you reach a point where players don't bother reading the effects, those interactions are no longer truly content. Note that unlike the previous qualifiers mentioned, this qualifier is based on the player, and therefore subjective. In effect, it's a spectrum where the more complicated the web of effects becomes, the more likely it is to disengage the player.

This over-complicatedness leading to disengaging the player can also happen from non-linear gameplay. If the web of effects becomes sufficiently complicated and finding the optimal progression route too time-consuming to discover, players will seek out guides from other players who've completed the game. The second they do this, the game effectively becomes linearly following the instructions of the guide and all the above criticisms apply. Similarly to as before, though, this is a spectrum and not everyone will seek out a guide at the same level of difficulty.

Automation

Automation is a staple of the genre, but it has certain implications for the design of the game. Why, when new content is introduced, must the older content be automated away - why is it a chore and it feels rewarding to not have to do it again? Why does the new mechanic have such appeal if we know it too will just be automated away later on, and we'll be happy when that happens? It honestly begs the question of why this framework of introducing content and automating the old content is even enjoyable - and nearly nonexistent in other genres. You're not going to reach a point in a platformer game where they just automate the jumping part - that's the core mechanic! Instead, platformers either add new mechanics that build on the core mechanic or at least re-contextualize the core mechanic. However, in incremental games new content very frequently means replacing older content, as opposed to augmenting it.

Admittedly, the above paragraph ignores the obvious answer that separates incremental games in this regard. These mechanics become chores as their frequency increases. The frequency increases to give a sense of progression, and automation is seen as a reward because it now manages what was becoming unmanageable. The new content then comes in and continues the loop to give a stronger sense of progression. That's all good and a fine justification for automating content instead of building upon the base mechanic. It's also much easier to design, as each layer essentially lets you start over instead of needing to think of ideas that conform to the original core mechanic.

So, what's the problem? Even if this trend is justified and easy to implement, there are some other effects it has on the game design. First off, and this is probably a neutral point, incremental games with this cycle of replacing old mechanics with new ones trend towards more and more abstract and further away from any narrative throughline as they add layers. There are only so many justifications for resetting progress, so if a game wants to have several of these layers they're inevitably going to become generic or increasingly loosely associated with the original content. It's most unfortunate, in my opinion when an interesting or innovative core mechanic gets fully automated once a generic "prestige" layer is unlocked.

A recent example is Really Grass Cutting Incremental, an incremental game about cutting grass (although I'm really criticizing the Roblox game it's based on). Except, it doesn't continue to be about cutting grass. After you buy enough upgrades to increase your grass cutting and level up sufficiently you "prestige", an abstract term that in this case means you reset all your progress to get some currency to buy upgrades that do the same things as the original upgrades, but these won't reset on future prestiges. You'll eventually be able to "crystallize", which means you reset all your progress to get some currency to buy upgrades that do the same things as the original upgrades (and a couple of new ones) and won't reset on future crystallizes. Fine. You'll progress a bit, complete some challenges, and finally get to... grasshop? Grasshopping is this mechanic where you reset all your progress to get some resource that isn't for buying upgrades - this time you just unlock different modifiers on everything based on their amount. You may have gotten the point by now, but there are also "steelie" resets which give you steel for some reason, before unlocking a factory with various machines - none of which are directly tied to cutting grass, and start gathering things like oil and reset for rocket parts and reset to go to space and so on and so on. Throughout all of this there is absolutely no narrative justification or throughline for the direction the game is going, or why cutting grass is still relevant when we're collecting things like rocket parts. I may be going a little hard on GCI, but it is far from alone.

Tips for Developers ​

If you're a developer, by this point you should have a pretty decent idea of how to create "true" content in your game. Here are some other specific tips I'd suggest:

An upgrade that simply unlocks another upgrade trivially isn't content. However, many games have an upgrade that just unlocks a feature, which then has a wait or other requirements before it can be used. Try to make sure when you unlock a feature, there is immediately something to do with the feature - for example, perhaps give them a small amount of the new currency it unlocks, if applicable.

If you don't have a large web of effects, and can definitively say the impact of a purchase is to multiply the gain of the cost currency by N, and the next purchase costs N times the amount of that same currency, then this purchase effectively made no difference and it may have made more sense to just go directly to the next upgrade. That said, having effects based on things like the number of purchases made will quickly invalidate this tip.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/guide-to-incrementals/ludology/definition/index.html b/guide-to-incrementals/ludology/definition/index.html index a78b769f..285b0153 100644 --- a/guide-to-incrementals/ludology/definition/index.html +++ b/guide-to-incrementals/ludology/definition/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
The Paper Pilot

Appearance

Guide to Incrementals/Defining the Genre ​

Video games are placed into genres for a variety of reasons. They can give a mental shorthand to set the player's expectations up, they can help a game market itself by its similarities to other, already popular games, and honestly, people just love categorization for its own sake. For this guide, it's important to define the genre so it is clear what games it's even talking about.

This poses a problem. "Incremental" is a horribly vague way to define games. Most games have numbers going up in some form or another. We need a more specific definition - similar to how "strategy" can't just mean any game with any amount of strategy because that would be most games. What specifically differentiates incremental games from the rest?

"Incremental" implies it's a genre defined by a game mechanic, but all those game mechanics it could imply exist in many other games. Having a skill tree or upgrades doesn't make you incremental, and if a reset mechanic is all it takes then every roguelite would be an incremental as well. So clearly there's more to it than that - what makes an incremental an incremental?

I'd like to go over a couple of popular suggestions I've seen on defining the genre here. I have my personal preferences and will state them here, but I don't think there's a truly perfect answer here.

Disclaimer: I mostly play incremental games on my computer, and my definitions will be heavily biased towards the games I'm familiar with.

Incrementals vs Idlers vs Clickers ​

Oftentimes people refer to this genre as idle games and/or clicker games. You'll even find a trend of oxymoronic game titles that contain both terms. "Incremental games" is the umbrella term both those terms fall under. However, I'd like to argue that not only is it better to just use the term "incremental games", but calling them "idle games" or "clicker games" is wrong. Almost universally, these terms are used interchangeably to refer to the same kind of game, where you start the game click spamming and eventually automate the process. Frankly, that kind of game deserves neither title, and the genre of incremental games has trended away from ever requiring click spamming, as it's a bad mechanic, anyways.

While these games do span a spectrum of how active it requires you to be, and sorting games by that metric can be useful for those looking for a particular experience, the borders of when an incremental game counts as an "idler" is too blurry for the term to be useful. "Incremental games" may not be a great descriptive term for the genre (hence this many thousands of words long page on defining what the genre even is), but it's strictly better than calling them "idler" or "clicker" games. This guide will always use the term "incremental games" unless quoting someone else, as it is the term you typically see on all modern games in the genre.

Incrementals as Parodies

Let's start with one of the most interesting definitions of incremental games. Incremental games appear to be distilled versions of games or genres, "revealing" the naked game design at the core of these games or genres not unlike how parodies comment upon their source material.

To understand what that means, think of how a casino uses skinner boxes to emotionally manipulate its customers to keep playing, but "dressing" up the skinner box with tons of stimuli to hide that ultimately the goal is to condition you into coming back compulsively. The idea that incremental games are parodies means taking the stance that at some level all games are similarly manipulating you, giving dopamine rewards in a way that manipulates you to keep playing while not necessarily giving you any value or fulfillment. Incremental games, then, are any games that plainly display the skinner box, and the manipulative core of the game, at the forefront of the experience.

While incremental games can be fun and even healthy in certain contexts, they can exacerbate video game addiction more than other genres. If you feel like playing incremental games is taking priority over other things in your life, or manipulating your sleep schedule, it may be prudent to seek help. See r/StopGaming for resources.

This "undressing" tends to go hand in hand with a reduced focus on aesthetics, often just printing the game state directly to the screen as text. This makes incremental games much easier to develop, particularly for those with programming skills but not art skills, but that's a tangent for why Incremental Games Guide to Incrementals/Appeal to Developers.

Before I continue, I'd like to make my stance clear that I love games and incremental games, and do not think they should be considered inherently bad or manipulative with the above logic. Skinner boxes are just a way of manipulating behavior via rewards. The games are still fun - that's the reward! I'd believe the real criticism here is that it is "empty fun", or "empty dopamine", that doesn't offer any additional value or sense of fulfillment. I don't think that's inherently bad in moderation, although it can become a problem if the game is manipulating you for profit-seeking, or if you play the game to the detriment of the other parts of your life.

Another interpretation of incremental games as parodies comes from several mainstream incremental games that are also parodies of capitalism, such as cookie clicker and adventure capitalist. It's a very common framework for incremental games to portray the ever-increasing numbers as an insatiable hunger for resources, like the ones observed within capitalism. Therefore, these games are used as evidence that the genre as a whole is about parody and commentary.

Popular videos on incremental games that portray the genre as parodies are Why Idle games make good satire, and how it was ruined. and Bad Game Design - Clicker Games. You may also be interested in this response to the latter video from a fan of incremental games: BadGood Game Design - Clicker Games.

I think that this definition ultimately ascribes a motive to the genre as a whole that only happens to apply to some of the more mainstream titles. There certainly are incremental games commenting on different things, including the genre itself as in the case of The Prestige Tree Classic, The Ascension Tree, or Omega Layers, but certainly not all. And of course, not all games that comment on something or parody something are incremental games! Additionally, a very large majority of incremental games are mobile games using these manipulative strategies to get players to spend as much money as possible - hell, Adventure Capitalist is ostensibly a critique on capitalism but features microtransactions and gameplay that manipulates you into buying them! These profit-seeking incremental games certainly belong within the genre but are hardly parodies when they too use manipulation to serve their interests. Also, from my own anecdotal experience, those who use this definition seem to do so from a fairly surface-level familiarity with the genre, and often in the context of criticizing the genre or the fans thereof.

Incrementals as NGU ​

Another broad definition often used is that incremental games are games where the focus of the game is "numbers going up". This definition proposes that other genres simply use increasing numbers as a means to an end, but incremental games uniquely only care about the numbers themselves going up. Put another way, it implies there should be no narrative justification for the numbers going up other than "why shouldn't they be going up?"

While this definition is common because it feels easy to understand, it is difficult to formally define. Often phrases are used to describe games using this framework, such as having an "exaggerated sense of progression" or "big" numbers. These terms are vague and don't demonstrate an actual threshold between non-incrementals and incrementals. Most games have a sense of progression, so when is it "exaggerated"? How big are "big" numbers? Most notably, RPGs that are typically not considered incrementals will often pass this definition.

Additionally, a lot of incrementals tend to have some theme guiding the gameplay, or at least the names of mechanics. This makes the line blurred between when numbers are going up for their own sake versus for a contextual reason. I believe this point is best illustrated that, while most RPGs are not considered incremental games, there is a sub-genre of "incremental RPGs" that typically relates to RPGs that perform combat automatically. This definition of incremental games does not support RPGs and "incremental RPGs" being on distinct sides of the line if the only difference between them is manual vs automatic combat.

Incrementals as Strategies

This is a rarer interpretation, but there are similarities between incremental games and strategy games, implying incrementals might just be a sub-genre of strategy games. By this approach, incremental games would be defined by their relation to strategy games, and how they involve player strategy. Incremental games are often large optimization problems - above all else, the actual gameplay the player is performing is deciding what to do next. The consequences of wrong decisions are typically more lenient in incremental games - such as just not making optimal progress - but they certainly get complex.

So if we accept the premise that incrementals could fall under strategy, we still need to define what makes a strategy game an incremental versus some other strategy sub-genre. This is a bit tricky due to one particular sub-genre of strategy games: Factory Builders.

Factory builders, such as Factorio or Satisfactory, are games about gaining ever increasing resources, optimizing production, and expanding more and more. That... sounds pretty similar, doesn't it? In fact, there's been some debate on whether factory builders would fall under the "incremental" umbrella. I think it's safe to say the two are certainly related, and probably have quite a bit of overlap in playerbase.

Roguelites as Incrementals? ​

Earlier on, I mentioned reset mechanics shouldn't be used in the definition because that could make all roguelites incrementals... But what if it does? A lot of incrementals can be described as games with a strong sense of progression, often with layers of meta-progression. Roguelites fit that bill to a T. What would make roguelites not incremental? I honestly don't think there's a good explanation here, but many fans of incremental games will state they do believe the two genres to be unrelated, even if there's a significant overlap between their player bases due to having similar appealing traits.

At this point, it'd be appropriate to consider what part of the definition of roguelites precludes them from also being incrementals, but that reveals a new problem: What are roguelites? They're usually defined as rogue_likes with meta-progression, but that just pushes the problem back a step: Incrementals aren't the only genre to have difficulties defining themselves, it seems! Roguelikes are another genre where the community argues over the formal definition of their genre, although that means we can borrow from their process of coming to a consensus, and maybe come across a viable definition for incremental games.

The Berlin Interpretation ​

By far the most popular way of defining roguelikes is the "Berlin Interpretation", which acknowledged the diversity of games within the genre and argued the definition should not be based on any ideals about what the genre ought to be, but rather defined by "its canon". They argued there are a handful of games that can be used to define the canon for roguelikes, and from those games, a list of factors can be derived to determine a game's "roguelikeness". The more factors a game has, the more of a roguelike it is. This strategy is very lenient, allowing a game to not present any specific factor so long as it shows enough, and accounts for the blurriness of any genre definition by not explicitly stating how many factors a game must have to qualify as a definite roguelike.

I believe this strategy for defining genres can be applied to other genres as well. A handful of games can be argued to be the incremental games canon, and a list of factors derived from them can be used to judge any game based on its "incrementalness". I'll propose such a canon and list of factors here, but by no means should it be considered the end-all-be-all.

Note: The "Temple of the roguelike", an authority within the genre, has since replaced the Berlin Interpretation with a new set of factors here: https://blog.roguetemple.com/what-is-a-traditional-roguelike/

The Incremental Games Canon ​

Alright, time to get controversial. Up til now, I've been trying my best to stay objective and analytical, but now it's time to start making some opinionated decisions. Here is a list of games I think could justifiably make up an Incremental Games Canon:

I chose a variety of games here, biasing towards newer games, purposefully to avoid making a narrow or "traditional" definition. The genre is growing and shouldn't be constrained by the traits of the early popular titles. A lot of these could easily be replaced with other games that are mechanically congruent, so ultimately I'm sure if you asked 10 people for their canon list you'd just get 10 different answers, but I think this should sufficiently allow us to determine what factors make a game have higher "incrementalness".

The Paradigm Shift ​

The Paradigm Shift is probably the highest possible value factor for an incremental. It's so common that for a while people referred to incrementals that exhibit this trait as "unfolding" games, to the point of trying to replace the term incremental due to their popularity. Paradigm shifts refer to when the gameplay significantly changes. There are too many examples to list here, but notably, every single reset mechanic is typically going to be a paradigm shift. Examples of games with paradigm shifts that aren't tied to reset mechanics include Universal Paperclips and A Dark Room.

There are many reasons for the appeal of paradigm shifts. Oftentimes each mechanic builds on top of the existing mechanics, increasing the complexity of the game in steps so the player can follow along. They provide a sense of mystery, with the player anticipating what will happen next. They shake up the gameplay before it gets too stale - allowing the game to entertain for longer before the sense of Guide to Incrementals/What is Content? dissipates. Of the canon games selected above, I would argue every single one contains a paradigm shift (although I could see someone disagreeing with that statement wrt Increlution).

I should take a moment to say that while I'm hyping up this specific factor, we cannot just reduce the genre definition to "does it have paradigm shifts". Many games have paradigm shifts that are not incremental, so it's just an indicator of incrementalness. Additionally, it can become quite hard to determine how large of a shift is a "paradigm" shift. Take, for example, any game with a skill tree. In some games, each skill node might have a large impact on how you play with the game, and qualify as a paradigm shift for some players. In other games, each skill node might just be a small percentage modifier on some stat that doesn't really impact much more than a slight bias towards an already established mechanic that's newly buffed. Every single canon game may show that it's common amongst incremental games, but could just as easily indicate that they're common in games in general.

High-Value Factors ​

I won't take as long to discuss the high and low-value factors, as you've already seen most of them brought up earlier on this page. As a reminder, a game does NOT need all of these to be an incremental game, but these are factors that each indicate a strong possibility the game is an incremental, so having several of these means they probably are. These factors apply to most of the canon incremental games.

"Pure UI" Display. Incrementals typically have a textual presentation of the game state - there isn't a visual representation of the entities within the game. The interface is closer to what would be just the UI of a game in another genre or the control panel of a plane. If there is a visual representation, the player is often still interacting with non-diegetic game elements.

Reduced Consequences. Incrementals tend to have reduced repurcussions for misplaying. They very rarely have fail states, where often the largest consequence is simply not progressing - never losing progress.

Optimization Problems. The predominant gameplay of incrementals is typically solving optimization problems, from deciding which purchase to save up for to reasoning and deciding between different mutually exclusive options the game presents.

Resource Management. Incrementals tend to have a lot of resources within the game to keep track of.

Low-Value Factors ​

These are low-value factors, meaning they aren't as strongly correlated with incremental games. Incremental games may have none of these, and non-incrementals may have several of these - if a game only has low-value factors, they're probably not an incremental.

Fast Numeric Growth. Numbers in incremental games tend to grow faster than in other genres. There are more instances of superlinear growth. The larger the numbers get, the stronger of a signal this factor is.

Automation. As an incremental game progresses, the player often no longer has to deal with earlier mechanics, by having them either happen automatically or otherwise be replaced with an alternative that requires less player interaction.

Goal-Oriented. Incrementals are often heavily reliant on extrinsic motivation to guide the player. Typically this is through some sort of in-game goal to work towards, such as a certain amount of a resource being required to unlock or purchase something new.

Waiting is a Mechanic. In incremental games, the player may come across times where there is no action they can take, and the game will progress automatically instead. The player must wait for some amount of this automatic progress to occur before they can resume interaction with the game.

Are Roguelites Incrementals? ​

Having made our variation of the Berlin Interpretation for incremental games, we can compare it to the Berlin Interpretation to determine if there's enough overlap that any game that "passes" the Berlin Interpretation would also pass the incremental variant. That is to say, whether any roguelite would also be considered an incremental game.

The meta-progression of an incremental game could arguably be considered a paradigm shift, and certainly adds some resource management. Goal-oriented would probably also apply. I think anything other than those would be a stretch, and in my opinion that just isn't enough to qualify. To be totally honest, I was never expecting to conclude otherwise though 😉

Sub-Genres ​

There are some trends in incremental games that go beyond just being a commonly used mechanic, such that they deeply affect the rest of the game design. These trends can be used to determine sub-genres within the incremental games umbrella:

Loops games are a sub-genre defined by having a core mechanic related to a loop, where the player is deciding the actions taken per loop. Notable examples include Idle Loops, Stuck in Time, Cavernous II, and Increlution. You may also argue Groundhog Life and Progress Knight fall into this sub-genre.

ITRTG-like games are a sub-genre defined by having a core mechanic based on clearing increasingly difficult battles and often tend to have a lot of different mechanics to become progressively stronger. Notable examples include Idling to Rule the Gods, NGU Idle, and Wizard and Minion Idle.

Polynomial Growth games are a sub-genre defined by having a core mechanic related to a higher degree polynomial. Notable examples include the base layer of Antimatter Dimensions and Swarm Simulator.

Upgrades Games is a category popular on flash games websites that featured games focused on buying upgrades that would allow you to attain more currency in some sort of minigame that would earn you more money to buy more upgrades, which I'd argue now belong under the fold of incremental games. Notable examples include the Learn to Fly series and Upgrade Complete.

Cultivation RPGs are a genre of games, books, and anime popular in China that center around being in a fantasy world with characters getting stronger over time. While few of them get translated into English, a fan of incremental games may find the available games interesting.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +
The Paper Pilot

Appearance

Guide to Incrementals/Defining the Genre ​

Video games are placed into genres for a variety of reasons. They can give a mental shorthand to set the player's expectations up, they can help a game market itself by its similarities to other, already popular games, and honestly, people just love categorization for its own sake. For this guide, it's important to define the genre so it is clear what games it's even talking about.

This poses a problem. "Incremental" is a horribly vague way to define games. Most games have numbers going up in some form or another. We need a more specific definition - similar to how "strategy" can't just mean any game with any amount of strategy because that would be most games. What specifically differentiates incremental games from the rest?

"Incremental" implies it's a genre defined by a game mechanic, but all those game mechanics it could imply exist in many other games. Having a skill tree or upgrades doesn't make you incremental, and if a reset mechanic is all it takes then every roguelite would be an incremental as well. So clearly there's more to it than that - what makes an incremental an incremental?

I'd like to go over a couple of popular suggestions I've seen on defining the genre here. I have my personal preferences and will state them here, but I don't think there's a truly perfect answer here.

Disclaimer: I mostly play incremental games on my computer, and my definitions will be heavily biased towards the games I'm familiar with.

Incrementals vs Idlers vs Clickers ​

Oftentimes people refer to this genre as idle games and/or clicker games. You'll even find a trend of oxymoronic game titles that contain both terms. "Incremental games" is the umbrella term both those terms fall under. However, I'd like to argue that not only is it better to just use the term "incremental games", but calling them "idle games" or "clicker games" is wrong. Almost universally, these terms are used interchangeably to refer to the same kind of game, where you start the game click spamming and eventually automate the process. Frankly, that kind of game deserves neither title, and the genre of incremental games has trended away from ever requiring click spamming, as it's a bad mechanic, anyways.

While these games do span a spectrum of how active it requires you to be, and sorting games by that metric can be useful for those looking for a particular experience, the borders of when an incremental game counts as an "idler" is too blurry for the term to be useful. "Incremental games" may not be a great descriptive term for the genre (hence this many thousands of words long page on defining what the genre even is), but it's strictly better than calling them "idler" or "clicker" games. This guide will always use the term "incremental games" unless quoting someone else, as it is the term you typically see on all modern games in the genre.

Incrementals as Parodies

Let's start with one of the most interesting definitions of incremental games. Incremental games appear to be distilled versions of games or genres, "revealing" the naked game design at the core of these games or genres not unlike how parodies comment upon their source material.

To understand what that means, think of how a casino uses skinner boxes to emotionally manipulate its customers to keep playing, but "dressing" up the skinner box with tons of stimuli to hide that ultimately the goal is to condition you into coming back compulsively. The idea that incremental games are parodies means taking the stance that at some level all games are similarly manipulating you, giving dopamine rewards in a way that manipulates you to keep playing while not necessarily giving you any value or fulfillment. Incremental games, then, are any games that plainly display the skinner box, and the manipulative core of the game, at the forefront of the experience.

While incremental games can be fun and even healthy in certain contexts, they can exacerbate video game addiction more than other genres. If you feel like playing incremental games is taking priority over other things in your life, or manipulating your sleep schedule, it may be prudent to seek help. See r/StopGaming for resources.

This "undressing" tends to go hand in hand with a reduced focus on aesthetics, often just printing the game state directly to the screen as text. This makes incremental games much easier to develop, particularly for those with programming skills but not art skills, but that's a tangent for why Incremental Games Guide to Incrementals/Appeal to Developers.

Before I continue, I'd like to make my stance clear that I love games and incremental games, and do not think they should be considered inherently bad or manipulative with the above logic. Skinner boxes are just a way of manipulating behavior via rewards. The games are still fun - that's the reward! I'd believe the real criticism here is that it is "empty fun", or "empty dopamine", that doesn't offer any additional value or sense of fulfillment. I don't think that's inherently bad in moderation, although it can become a problem if the game is manipulating you for profit-seeking, or if you play the game to the detriment of the other parts of your life.

Another interpretation of incremental games as parodies comes from several mainstream incremental games that are also parodies of capitalism, such as cookie clicker and adventure capitalist. It's a very common framework for incremental games to portray the ever-increasing numbers as an insatiable hunger for resources, like the ones observed within capitalism. Therefore, these games are used as evidence that the genre as a whole is about parody and commentary.

Popular videos on incremental games that portray the genre as parodies are Why Idle games make good satire, and how it was ruined. and Bad Game Design - Clicker Games. You may also be interested in this response to the latter video from a fan of incremental games: BadGood Game Design - Clicker Games.

I think that this definition ultimately ascribes a motive to the genre as a whole that only happens to apply to some of the more mainstream titles. There certainly are incremental games commenting on different things, including the genre itself as in the case of The Prestige Tree Classic, The Ascension Tree, or Omega Layers, but certainly not all. And of course, not all games that comment on something or parody something are incremental games! Additionally, a very large majority of incremental games are mobile games using these manipulative strategies to get players to spend as much money as possible - hell, Adventure Capitalist is ostensibly a critique on capitalism but features microtransactions and gameplay that manipulates you into buying them! These profit-seeking incremental games certainly belong within the genre but are hardly parodies when they too use manipulation to serve their interests. Also, from my own anecdotal experience, those who use this definition seem to do so from a fairly surface-level familiarity with the genre, and often in the context of criticizing the genre or the fans thereof.

Incrementals as NGU ​

Another broad definition often used is that incremental games are games where the focus of the game is "numbers going up". This definition proposes that other genres simply use increasing numbers as a means to an end, but incremental games uniquely only care about the numbers themselves going up. Put another way, it implies there should be no narrative justification for the numbers going up other than "why shouldn't they be going up?"

While this definition is common because it feels easy to understand, it is difficult to formally define. Often phrases are used to describe games using this framework, such as having an "exaggerated sense of progression" or "big" numbers. These terms are vague and don't demonstrate an actual threshold between non-incrementals and incrementals. Most games have a sense of progression, so when is it "exaggerated"? How big are "big" numbers? Most notably, RPGs that are typically not considered incrementals will often pass this definition.

Additionally, a lot of incrementals tend to have some theme guiding the gameplay, or at least the names of mechanics. This makes the line blurred between when numbers are going up for their own sake versus for a contextual reason. I believe this point is best illustrated that, while most RPGs are not considered incremental games, there is a sub-genre of "incremental RPGs" that typically relates to RPGs that perform combat automatically. This definition of incremental games does not support RPGs and "incremental RPGs" being on distinct sides of the line if the only difference between them is manual vs automatic combat.

Incrementals as Strategies

This is a rarer interpretation, but there are similarities between incremental games and strategy games, implying incrementals might just be a sub-genre of strategy games. By this approach, incremental games would be defined by their relation to strategy games, and how they involve player strategy. Incremental games are often large optimization problems - above all else, the actual gameplay the player is performing is deciding what to do next. The consequences of wrong decisions are typically more lenient in incremental games - such as just not making optimal progress - but they certainly get complex.

So if we accept the premise that incrementals could fall under strategy, we still need to define what makes a strategy game an incremental versus some other strategy sub-genre. This is a bit tricky due to one particular sub-genre of strategy games: Factory Builders.

Factory builders, such as Factorio or Satisfactory, are games about gaining ever increasing resources, optimizing production, and expanding more and more. That... sounds pretty similar, doesn't it? In fact, there's been some debate on whether factory builders would fall under the "incremental" umbrella. I think it's safe to say the two are certainly related, and probably have quite a bit of overlap in playerbase.

Roguelites as Incrementals? ​

Earlier on, I mentioned reset mechanics shouldn't be used in the definition because that could make all roguelites incrementals... But what if it does? A lot of incrementals can be described as games with a strong sense of progression, often with layers of meta-progression. Roguelites fit that bill to a T. What would make roguelites not incremental? I honestly don't think there's a good explanation here, but many fans of incremental games will state they do believe the two genres to be unrelated, even if there's a significant overlap between their player bases due to having similar appealing traits.

At this point, it'd be appropriate to consider what part of the definition of roguelites precludes them from also being incrementals, but that reveals a new problem: What are roguelites? They're usually defined as rogue_likes with meta-progression, but that just pushes the problem back a step: Incrementals aren't the only genre to have difficulties defining themselves, it seems! Roguelikes are another genre where the community argues over the formal definition of their genre, although that means we can borrow from their process of coming to a consensus, and maybe come across a viable definition for incremental games.

The Berlin Interpretation ​

By far the most popular way of defining roguelikes is the "Berlin Interpretation", which acknowledged the diversity of games within the genre and argued the definition should not be based on any ideals about what the genre ought to be, but rather defined by "its canon". They argued there are a handful of games that can be used to define the canon for roguelikes, and from those games, a list of factors can be derived to determine a game's "roguelikeness". The more factors a game has, the more of a roguelike it is. This strategy is very lenient, allowing a game to not present any specific factor so long as it shows enough, and accounts for the blurriness of any genre definition by not explicitly stating how many factors a game must have to qualify as a definite roguelike.

I believe this strategy for defining genres can be applied to other genres as well. A handful of games can be argued to be the incremental games canon, and a list of factors derived from them can be used to judge any game based on its "incrementalness". I'll propose such a canon and list of factors here, but by no means should it be considered the end-all-be-all.

Note: The "Temple of the roguelike", an authority within the genre, has since replaced the Berlin Interpretation with a new set of factors here: https://blog.roguetemple.com/what-is-a-traditional-roguelike/

The Incremental Games Canon ​

Alright, time to get controversial. Up til now, I've been trying my best to stay objective and analytical, but now it's time to start making some opinionated decisions. Here is a list of games I think could justifiably make up an Incremental Games Canon:

I chose a variety of games here, biasing towards newer games, purposefully to avoid making a narrow or "traditional" definition. The genre is growing and shouldn't be constrained by the traits of the early popular titles. A lot of these could easily be replaced with other games that are mechanically congruent, so ultimately I'm sure if you asked 10 people for their canon list you'd just get 10 different answers, but I think this should sufficiently allow us to determine what factors make a game have higher "incrementalness".

The Paradigm Shift ​

The Paradigm Shift is probably the highest possible value factor for an incremental. It's so common that for a while people referred to incrementals that exhibit this trait as "unfolding" games, to the point of trying to replace the term incremental due to their popularity. Paradigm shifts refer to when the gameplay significantly changes. There are too many examples to list here, but notably, every single reset mechanic is typically going to be a paradigm shift. Examples of games with paradigm shifts that aren't tied to reset mechanics include Universal Paperclips and A Dark Room.

There are many reasons for the appeal of paradigm shifts. Oftentimes each mechanic builds on top of the existing mechanics, increasing the complexity of the game in steps so the player can follow along. They provide a sense of mystery, with the player anticipating what will happen next. They shake up the gameplay before it gets too stale - allowing the game to entertain for longer before the sense of Guide to Incrementals/What is Content? dissipates. Of the canon games selected above, I would argue every single one contains a paradigm shift (although I could see someone disagreeing with that statement wrt Increlution).

I should take a moment to say that while I'm hyping up this specific factor, we cannot just reduce the genre definition to "does it have paradigm shifts". Many games have paradigm shifts that are not incremental, so it's just an indicator of incrementalness. Additionally, it can become quite hard to determine how large of a shift is a "paradigm" shift. Take, for example, any game with a skill tree. In some games, each skill node might have a large impact on how you play with the game, and qualify as a paradigm shift for some players. In other games, each skill node might just be a small percentage modifier on some stat that doesn't really impact much more than a slight bias towards an already established mechanic that's newly buffed. Every single canon game may show that it's common amongst incremental games, but could just as easily indicate that they're common in games in general.

High-Value Factors ​

I won't take as long to discuss the high and low-value factors, as you've already seen most of them brought up earlier on this page. As a reminder, a game does NOT need all of these to be an incremental game, but these are factors that each indicate a strong possibility the game is an incremental, so having several of these means they probably are. These factors apply to most of the canon incremental games.

"Pure UI" Display. Incrementals typically have a textual presentation of the game state - there isn't a visual representation of the entities within the game. The interface is closer to what would be just the UI of a game in another genre or the control panel of a plane. If there is a visual representation, the player is often still interacting with non-diegetic game elements.

Reduced Consequences. Incrementals tend to have reduced repurcussions for misplaying. They very rarely have fail states, where often the largest consequence is simply not progressing - never losing progress.

Optimization Problems. The predominant gameplay of incrementals is typically solving optimization problems, from deciding which purchase to save up for to reasoning and deciding between different mutually exclusive options the game presents.

Resource Management. Incrementals tend to have a lot of resources within the game to keep track of.

Low-Value Factors ​

These are low-value factors, meaning they aren't as strongly correlated with incremental games. Incremental games may have none of these, and non-incrementals may have several of these - if a game only has low-value factors, they're probably not an incremental.

Fast Numeric Growth. Numbers in incremental games tend to grow faster than in other genres. There are more instances of superlinear growth. The larger the numbers get, the stronger of a signal this factor is.

Automation. As an incremental game progresses, the player often no longer has to deal with earlier mechanics, by having them either happen automatically or otherwise be replaced with an alternative that requires less player interaction.

Goal-Oriented. Incrementals are often heavily reliant on extrinsic motivation to guide the player. Typically this is through some sort of in-game goal to work towards, such as a certain amount of a resource being required to unlock or purchase something new.

Waiting is a Mechanic. In incremental games, the player may come across times where there is no action they can take, and the game will progress automatically instead. The player must wait for some amount of this automatic progress to occur before they can resume interaction with the game.

Are Roguelites Incrementals? ​

Having made our variation of the Berlin Interpretation for incremental games, we can compare it to the Berlin Interpretation to determine if there's enough overlap that any game that "passes" the Berlin Interpretation would also pass the incremental variant. That is to say, whether any roguelite would also be considered an incremental game.

The meta-progression of an incremental game could arguably be considered a paradigm shift, and certainly adds some resource management. Goal-oriented would probably also apply. I think anything other than those would be a stretch, and in my opinion that just isn't enough to qualify. To be totally honest, I was never expecting to conclude otherwise though 😉

Sub-Genres ​

There are some trends in incremental games that go beyond just being a commonly used mechanic, such that they deeply affect the rest of the game design. These trends can be used to determine sub-genres within the incremental games umbrella:

Loops games are a sub-genre defined by having a core mechanic related to a loop, where the player is deciding the actions taken per loop. Notable examples include Idle Loops, Stuck in Time, Cavernous II, and Increlution. You may also argue Groundhog Life and Progress Knight fall into this sub-genre.

ITRTG-like games are a sub-genre defined by having a core mechanic based on clearing increasingly difficult battles and often tend to have a lot of different mechanics to become progressively stronger. Notable examples include Idling to Rule the Gods, NGU Idle, and Wizard and Minion Idle.

Polynomial Growth games are a sub-genre defined by having a core mechanic related to a higher degree polynomial. Notable examples include the base layer of Antimatter Dimensions and Swarm Simulator.

Upgrades Games is a category popular on flash games websites that featured games focused on buying upgrades that would allow you to attain more currency in some sort of minigame that would earn you more money to buy more upgrades, which I'd argue now belong under the fold of incremental games. Notable examples include the Learn to Fly series and Upgrade Complete.

Cultivation RPGs are a genre of games, books, and anime popular in China that center around being in a fantasy world with characters getting stronger over time. While few of them get translated into English, a fan of incremental games may find the available games interesting.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/hashmap.json b/hashmap.json index 9bcbd483..0967ef42 100644 --- a/hashmap.json +++ b/hashmap.json @@ -1 +1 @@ -{"garden_kronos_index.md":"iUhWCop9","garden_guide-to-incrementals_appeal-to-developers_index.md":"Diny6WsX","garden_mtx_index.md":"BRzkTeai","garden_my-projects_index.md":"Cznm6ckc","public_gamedevtree_changelog.md":"DGS-7PiF","public_gamedevtree_docs_bars.md":"CxNndqIx","public_gamedevtree_docs_buyables.md":"DlXMZmV4","public_gamedevtree_docs_challenges.md":"DEdsv7kR","public_gamedevtree_docs_getting-started.md":"DzfYHbWF","public_gamedevtree_docs_basic-layer-breakdown.md":"rhKMtsLX","public_gamedevtree_docs_milestones.md":"DiBU9uxR","garden_chronological_index.md":"CQEy-T7E","garden_mbin_index.md":"BHK-Iuf3","guide-to-incrementals_index.md":"Q8NHkbU9","garden_vitepress_index.md":"CDGDOV5f","garden_fediverse_index.md":"C7LEB0uc","garden_this-knowledge-hub_index.md":"CUdFhZdq","garden_social-media_index.md":"BbHjayFv","guide-to-incrementals_ludology_appeal-gamers_index.md":"B6xF3S0w","guide-to-incrementals_ludology_appeal-developers_index.md":"Cm_ScJQR","public_gamedevtree_readme.md":"C_ZitREW","public_gamedevtree_docs_subtabs-and-microtabs.md":"C75eZZin","garden_premium-currency_index.md":"CYRzDOj_","garden_ivy-road_index.md":"I5lUYnjM","garden_webrings_index.md":"DVn_-9-u","public_gamedevtree_docs_infoboxes.md":"9a47XYCg","garden_atproto_index.md":"DbIIfL4R","garden_activitypub_index.md":"CicDcQ2_","garden_advent-incremental_index.md":"C8yXdubg","garden_dice-armor_index.md":"CHYRQr4z","garden_nostr_index.md":"CgleUUbP","garden_the-small-web_index.md":"DB8s7zLZ","garden_weird_index.md":"5UcMgku5","guide-to-incrementals_design_criticism_index.md":"DIKhcyDO","public_kronos_docs_custom-tab-layouts.md":"C9uDrIM0","public_kronos_docs_clickables.md":"BvrZ942x","public_gamedevtree_docs_upgrades.md":"Msxg1C07","public_lit_docs_infoboxes.md":"BuPTImhx","public_lit_docs_subtabs-and-microtabs.md":"DhbrQf33","now_index.md":"Bc55FAwk","garden_artificial-intelligence_index.md":"DHIZV-Nf","garden_guide-to-incrementals_navigating-criticism_index.md":"FUIN6tkG","garden_my-personal-website_index.md":"DwfKlijC","guide-to-incrementals_ludology_definition_index.md":"D2MCMru0","garden_digital-gardens_index.md":"-_Ah0Mkb","garden_guide-to-incrementals_what-is-content_index.md":"BMETYiAP","garden_incremental-social_index.md":"D80WDhip","garden_planar-pioneers_index.md":"C66vsCjv","garden_matrix_index.md":"CeSXZSDm","garden_life-is-strange_index.md":"tdVgcS32","garden_opti-speech_index.md":"fV3laAf8","garden_logseq_index.md":"BiLoV0bt","garden_open-source_index.md":"CrbIsKOD","garden_the-beginner-s-guide_index.md":"BdmIJg3j","index.md":"DsTbDkfQ","garden_the-cozy-web_index.md":"BEzt5FqQ","garden_profectus_index.md":"ykiRoiHE","garden_the-indieweb_signature-blocks_index.md":"BSUq9f2h","garden_freeform-vs-chronological-dichotomy_index.md":"CC0rVLI6","garden_forgejo_index.md":"2k8RiG3S","garden_v-ecs_index.md":"DJKtb91L","public_gamedevtree_docs_clickables.md":"Cyab8uw5","public_gamedevtree_2.0-format-changes.md":"3MaMo5-m","changelog_index.md":"gjqAjJbE","public_gamedevtree_docs_updating-tmt.md":"37YMR_q4","garden_command-palettes_index.md":"aFoJwvWM","garden_video-game-monetization_index.md":"eY03jnxc","garden_capture-the-citadel_index.md":"CzfQmks-","garden_guide-to-incrementals_appeal-to-players_index.md":"CRDB23Hr","garden_garden-rss_index.md":"CeZWgVca","garden_federated-identity_index.md":"DXhML-Yi","garden_pre-order-bonuses_index.md":"C0-qMrbr","garden_freeform_index.md":"CvO7JCJh","garden_fedi-v2_index.md":"CtSaZdaZ","garden_the-indieweb_amplification_index.md":"DT2TYsGY","garden_commune_index.md":"DRJ4sRzw","garden_chat-glue_index.md":"BTV2mQC1","garden_cinny_index.md":"6lP2Zwso","garden_decentralized_index.md":"Cbrt43lP","garden_synapse_index.md":"C51ajr4V","garden_babble-buds_index.md":"D3H2b176","garden_davey-wreden_index.md":"DUU5axE-","garden_game-dev-tree_index.md":"CXDRxuvP","public_gamedevtree_docs_achievements.md":"DrDgZswR","public_gamedevtree_docs_!general-info.md":"BwFSZwbZ","public_gamedevtree_docs_main-mod-info.md":"DYvAg_3w","garden_wanderstop_index.md":"BTJMeiHB","public_kronos_readme.md":"CgBYWZCx","public_kronos_old things_2.0-format-changes.md":"CuPSOvPY","guide-to-incrementals_ludology_content_index.md":"DktkMXz1","public_kronos_docs_getting-started.md":"mdR9VU7R","public_kronos_docs_infoboxes.md":"cE2lKUcU","public_lit_docs_buyables.md":"-Ov6NyGO","public_kronos_docs_grids.md":"BeCPe1VG","public_kronos_docs_layer-features.md":"sKwRGXXx","public_kronos_docs_particles.md":"acAe5suw","public_kronos_docs_main-mod-info.md":"CV8Og8jf","public_kronos_docs_subtabs-and-microtabs.md":"CAfP6QpE","public_kronos_docs_updating-tmt.md":"_8lPgb0z","public_kronos_docs_trees-and-tree-customization.md":"D0rBQwbs","public_lit_old things_2.0-format-changes.md":"BUbI7CBx","public_kronos_docs_upgrades.md":"CTKgTXEi","public_lit_docs_trees-and-tree-customization.md":"DpLqj7LC","public_lit_readme.md":"C6r_DD7H","public_lit_docs_challenges.md":"BoYK1lsk","public_lit_changelog.md":"CG6hOolt","public_lit_docs_custom-tab-layouts.md":"DVTPJ8Y_","public_lit_docs_!general-info.md":"D6KB8CTG","public_lit_docs_getting-started.md":"CsxQcaII","public_lit_docs_bars.md":"B1h0O1rn","public_lit_docs_layer-features.md":"sExHYK2Z","public_lit_docs_upgrades.md":"BttvCS4L","public_lit_docs_updating-tmt.md":"C2pGYz0K","public_kronos_docs_achievements.md":"DH7Fd1ef","public_kronos_changelog.md":"CfILpf_9","public_kronos_docs_bars.md":"C-Hikk54","public_kronos_docs_!general-info.md":"h8u1FelN","public_kronos_docs_milestones.md":"DTJttUg9","public_kronos_docs_basic-layer-breakdown.md":"Zf7IGRAq","garden_guide-to-incrementals_index.md":"BojXmdru","public_lit_docs_clickables.md":"B6OakSbD","garden_guide-to-incrementals_defining-the-genre_index.md":"DC5Wks2J","public_lit_docs_basic-layer-breakdown.md":"Qv71gcDd","public_gamedevtree_docs_layer-features.md":"y6Ef1VMc","public_lit_docs_milestones.md":"Cf2Qcvln","public_kronos_docs_buyables.md":"DaAxmRa3","public_gamedevtree_docs_custom-tab-layouts.md":"DO3JHVjV","public_lit_docs_achievements.md":"DGaaIXhv","public_lit_docs_main-mod-info.md":"CVm1BK0i","public_kronos_docs_challenges.md":"DjtWlrsA"} +{} diff --git a/index.html b/index.html index 23a885bb..9a292f03 100644 --- a/index.html +++ b/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +
The Paper Pilot

Appearance

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/now/index.html b/now/index.html index 2951fd3f..eacfcd37 100644 --- a/now/index.html +++ b/now/index.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
The Paper Pilot

Appearance

/now ​

This "now page" offers a big picture glimpse into what I’m focused on at this point in my life. What is a now page?

Life ​

I'm living in DFW with my wife and baby son. I work at Topaz Labs LLC as a software developer, where I develop their flagship product Topaz Photo AI.

IndieWeb ​

I've been learning a lot about The Small Web (or the various other names it goes by). I've been working on this website and implementing the various IndieWeb building blocks

I'm also working on a proposal for adding The IndieWeb/Signature Blocks to your notes

Commune ​

While I'm not contributing to the project directly, I'm following along and participating with the discussions and designs of Commune.

I'm working on a mockup of what an app could look like that treats incoming messages, emails, etc. differently based on user defined rules, with a focus on moving them into personal or communal digital gardens.

Incremental Social ​

I'm running and improving the social media site Incremental Social, along with CardboardEmpress.

Chromatic Lattice ​

I'm working on a multiplayer incremental game. That's all that's known publicly for now 😜.

Kronos ​

I'm working on a long single player narratively driven incremental game. This is a very long-term project.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +
The Paper Pilot

Appearance

/now ​

This "now page" offers a big picture glimpse into what I’m focused on at this point in my life. What is a now page?

Life ​

I'm living in DFW with my wife and baby son. I work at Topaz Labs LLC as a software developer, where I develop their flagship product Topaz Photo AI.

IndieWeb ​

I've been learning a lot about The Small Web (or the various other names it goes by). I've been working on this website and implementing the various IndieWeb building blocks

I'm also working on a proposal for adding The IndieWeb/Signature Blocks to your notes

Commune ​

While I'm not contributing to the project directly, I'm following along and participating with the discussions and designs of Commune.

I'm working on a mockup of what an app could look like that treats incoming messages, emails, etc. differently based on user defined rules, with a focus on moving them into personal or communal digital gardens.

Incremental Social ​

I'm running and improving the social media site Incremental Social, along with CardboardEmpress.

Chromatic Lattice ​

I'm working on a multiplayer incremental game. That's all that's known publicly for now 😜.

Kronos ​

I'm working on a long single player narratively driven incremental game. This is a very long-term project.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/package.json b/package.json new file mode 100644 index 00000000..25d9dcff --- /dev/null +++ b/package.json @@ -0,0 +1 @@ +{ "private": true, "type": "module" } \ No newline at end of file diff --git a/public/gamedevtree/2.0-format-changes.html b/public/gamedevtree/2.0-format-changes.html index d1428fd5..9a103c90 100644 --- a/public/gamedevtree/2.0-format-changes.html +++ b/public/gamedevtree/2.0-format-changes.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
The Paper Pilot

Appearance

2.0 format changes ​

  • Temp format is changed from temp.something[layer] to temp[layer].something, for consistency
  • Challenges are now saved as an object with the amount of completions in each spot. (This will break saves.)
  • effectDisplay in Challenges and Upgrades no longer takes an argument, and neither does effect for Buyables
  • Buyable cost can take an argument for amount of buyables, but it needs to function if no argument is supplied (it should do the cost for the next purchase).
  • Generation of Points now happens in the main game loop (not in a layer update function), enabled by canGenPoints in game.js.
  • Changed fullLayerReset to layerDataReset, which takes an array of names of values to keep

In addition, many names were changed, mostly expanding abbreviations:

All instances of:

  • chall -> challenge
  • unl -> unlocked
  • upg -> upgrade (besides CSS)
  • amt -> amount
  • desc -> description
  • resCeil -> roundUpCost
  • order -> unlockOrder
  • incr_order -> increaseUnlockOrder

Challenges:

  • desc -> challengeDescription
  • reward -> rewardDescription
  • effect -> rewardEffect
  • effectDisplay -> rewardDisplay
  • active -> challengeActive
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +
The Paper Pilot

Appearance

2.0 format changes ​

  • Temp format is changed from temp.something[layer] to temp[layer].something, for consistency
  • Challenges are now saved as an object with the amount of completions in each spot. (This will break saves.)
  • effectDisplay in Challenges and Upgrades no longer takes an argument, and neither does effect for Buyables
  • Buyable cost can take an argument for amount of buyables, but it needs to function if no argument is supplied (it should do the cost for the next purchase).
  • Generation of Points now happens in the main game loop (not in a layer update function), enabled by canGenPoints in game.js.
  • Changed fullLayerReset to layerDataReset, which takes an array of names of values to keep

In addition, many names were changed, mostly expanding abbreviations:

All instances of:

  • chall -> challenge
  • unl -> unlocked
  • upg -> upgrade (besides CSS)
  • amt -> amount
  • desc -> description
  • resCeil -> roundUpCost
  • order -> unlockOrder
  • incr_order -> increaseUnlockOrder

Challenges:

  • desc -> challengeDescription
  • reward -> rewardDescription
  • effect -> rewardEffect
  • effectDisplay -> rewardDisplay
  • active -> challengeActive
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/public/gamedevtree/README.html b/public/gamedevtree/README.html index e8edf2e7..74a03e62 100644 --- a/public/gamedevtree/README.html +++ b/public/gamedevtree/README.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
The Paper Pilot

Appearance

The-Modding-Tree ​

A modified version of The Prestige Tree that is much easier to mod. It still requires programming knowledge, but it's mostly pretty easy things and copy/pasting.

Look here for a tutorial on getting started with modding with TMT

You can look in the documentation for more information on how it all works, or look at the code in layers.js to see what it all looks like.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +
The Paper Pilot

Appearance

The-Modding-Tree ​

A modified version of The Prestige Tree that is much easier to mod. It still requires programming knowledge, but it's mostly pretty easy things and copy/pasting.

Look here for a tutorial on getting started with modding with TMT

You can look in the documentation for more information on how it all works, or look at the code in layers.js to see what it all looks like.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/public/gamedevtree/changelog.html b/public/gamedevtree/changelog.html index 3f07530e..c33ae692 100644 --- a/public/gamedevtree/changelog.html +++ b/public/gamedevtree/changelog.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
The Paper Pilot

Appearance

The Game Dev Tree changelog: ​

v1.0.4 Version Bump [rebalanced,debuggedx3] - 2020-11-09 ​

  • Fixed refactorings 2, 3, and 4 not actually affecting productivity

v1.0.3 Version Bump [rebalanced,debuggedx2] - 2020-11-08 ​

  • Fixed API milestone 4 not working

v1.0.2 Version Bump [rebalanced,debugged] - 2020-11-08 ​

  • Fixed tree lines being hidden after hitting "keepGoing" in the victory screen

v1.0.1 Version Bump [rebalanced] - 2020-11-08 ​

  • Buffed several TAs

v1.0 Version Bump - 2020-11-08 ​

  • Finished row 4
  • Added colored text to lore
  • Fixed some visual bugs with milestones
  • Probably other stuff lol its been a week

v0.2.3 Stylish - 2020-10-30 ​

  • Re-styled basically everything
  • Added favicon
  • Added header bar
  • Added changelog

v0.2.2 Row 3 - 2020-10-22 ​

  • Removed debug statement
  • Moved milestones in F layer beneath the buyables

v0.2.1 Row 3 - 2020-10-21 ​

  • Fixed layers hiding
  • Fixed typos/minor issues
  • Fixed S layer being highlighted before you can unlock the layer

v0.2 Row 3 - 2020-10-21 ​

  • Implemented row 3

v0.1.1 Cash Influx [rebalanced] - 2020-10-19 ​

  • Fixed notification issue
  • Rebalanced to make early game faster and late game slower
  • Fixed other minor issues

v0.1 Cash Influx - 2020-10-19 ​

  • Implemented row 2

v0.0 Initial Commit - 2020-10-18 ​

  • Implemented row 1
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +
The Paper Pilot

Appearance

The Game Dev Tree changelog: ​

v1.0.4 Version Bump [rebalanced,debuggedx3] - 2020-11-09 ​

  • Fixed refactorings 2, 3, and 4 not actually affecting productivity

v1.0.3 Version Bump [rebalanced,debuggedx2] - 2020-11-08 ​

  • Fixed API milestone 4 not working

v1.0.2 Version Bump [rebalanced,debugged] - 2020-11-08 ​

  • Fixed tree lines being hidden after hitting "keepGoing" in the victory screen

v1.0.1 Version Bump [rebalanced] - 2020-11-08 ​

  • Buffed several TAs

v1.0 Version Bump - 2020-11-08 ​

  • Finished row 4
  • Added colored text to lore
  • Fixed some visual bugs with milestones
  • Probably other stuff lol its been a week

v0.2.3 Stylish - 2020-10-30 ​

  • Re-styled basically everything
  • Added favicon
  • Added header bar
  • Added changelog

v0.2.2 Row 3 - 2020-10-22 ​

  • Removed debug statement
  • Moved milestones in F layer beneath the buyables

v0.2.1 Row 3 - 2020-10-21 ​

  • Fixed layers hiding
  • Fixed typos/minor issues
  • Fixed S layer being highlighted before you can unlock the layer

v0.2 Row 3 - 2020-10-21 ​

  • Implemented row 3

v0.1.1 Cash Influx [rebalanced] - 2020-10-19 ​

  • Fixed notification issue
  • Rebalanced to make early game faster and late game slower
  • Fixed other minor issues

v0.1 Cash Influx - 2020-10-19 ​

  • Implemented row 2

v0.0 Initial Commit - 2020-10-18 ​

  • Implemented row 1
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/public/gamedevtree/docs/!general-info.html b/public/gamedevtree/docs/!general-info.html index d064871c..f741ae43 100644 --- a/public/gamedevtree/docs/!general-info.html +++ b/public/gamedevtree/docs/!general-info.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
The Paper Pilot

Appearance

The-Modding-Tree ​

The main way to add content is through creating layers. You can either add a layer directly in the layers object in layersSupportjs, or declare it in another file and then do "addLayer(layername, layerdata)" (good for breaking things up into smaller files). The existing layers are just examples and can be freely deleted. You can also use them as references and a base for your own layers.

The first thing you need to do is to edit the modInfo at the top of game.js to set your modID (a string). A unique modId will prevent your mod's saves from conflicting with other mods.

Most of the time, you won't need to dive deep into the code to create things, but you still can if you really want to.

The Modding Tree uses break_eternity.js to store large values. This means that many numbers are Decimal objects, and must be treated differently. For example, you have to use new Decimal(x) to create a Decimal value instead of a plain number, and perform operations on them by calling functions. e.g, instead of x = x + y, use x = x.add(y).

Almost all values can be either a constant value, or a dynamic value. Dynamic values are defined by putting a function that returns what the value should be at any given time.

All display text can be basic HTML instead (But you can't use most Vue features there).

Table of Contents: ​

General: ​

  • Getting Started: Getting your own copy of the code set up with Github Desktop.
  • Main mod info: How to set up general things for your mod in mod.js.
  • Basic layer breakdown: Breaking down the components of a layer with minimal features.
  • Layer features: Explanations of all of the different properties that you can give a layer.
  • Custom Tab Layouts: An optional way to give your tabs a different layout. You can even create entirely new components to use.
  • Updating TMT: Using Github Desktop to update your mod's version of TMT.

Common components ​

  • Upgrades: How to create upgrades for a layer.
  • Milestones: How to create milestones for a layer.
  • Buyables: Create rebuyable upgrades for your layer (with the option to make them respec-able). Can be used to make Enhancers or Space Buildings.
  • Clickables: A more generalized variant of buyables, for any kind of thing that is sometimes clickable. Between these and Buyables, you can do just about anything.

Other components ​

  • Challenges: How to create challenges for a layer.
  • Bars: Display some information as a progress bar, gague, or similar. They are highly customizable, and can be horizontal and vertical as well.
  • Subtabs and Microtabs: Create subtabs for your tabs, as well as "microtab" components that you can put inside the tabs.
  • Achievements: How to create achievements for a layer (or for the whole game).
  • Infoboxes: Boxes containing text that can be shown or hidden.
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +
The Paper Pilot

Appearance

The-Modding-Tree ​

The main way to add content is through creating layers. You can either add a layer directly in the layers object in layersSupportjs, or declare it in another file and then do "addLayer(layername, layerdata)" (good for breaking things up into smaller files). The existing layers are just examples and can be freely deleted. You can also use them as references and a base for your own layers.

The first thing you need to do is to edit the modInfo at the top of game.js to set your modID (a string). A unique modId will prevent your mod's saves from conflicting with other mods.

Most of the time, you won't need to dive deep into the code to create things, but you still can if you really want to.

The Modding Tree uses break_eternity.js to store large values. This means that many numbers are Decimal objects, and must be treated differently. For example, you have to use new Decimal(x) to create a Decimal value instead of a plain number, and perform operations on them by calling functions. e.g, instead of x = x + y, use x = x.add(y).

Almost all values can be either a constant value, or a dynamic value. Dynamic values are defined by putting a function that returns what the value should be at any given time.

All display text can be basic HTML instead (But you can't use most Vue features there).

Table of Contents: ​

General: ​

  • Getting Started: Getting your own copy of the code set up with Github Desktop.
  • Main mod info: How to set up general things for your mod in mod.js.
  • Basic layer breakdown: Breaking down the components of a layer with minimal features.
  • Layer features: Explanations of all of the different properties that you can give a layer.
  • Custom Tab Layouts: An optional way to give your tabs a different layout. You can even create entirely new components to use.
  • Updating TMT: Using Github Desktop to update your mod's version of TMT.

Common components ​

  • Upgrades: How to create upgrades for a layer.
  • Milestones: How to create milestones for a layer.
  • Buyables: Create rebuyable upgrades for your layer (with the option to make them respec-able). Can be used to make Enhancers or Space Buildings.
  • Clickables: A more generalized variant of buyables, for any kind of thing that is sometimes clickable. Between these and Buyables, you can do just about anything.

Other components ​

  • Challenges: How to create challenges for a layer.
  • Bars: Display some information as a progress bar, gague, or similar. They are highly customizable, and can be horizontal and vertical as well.
  • Subtabs and Microtabs: Create subtabs for your tabs, as well as "microtab" components that you can put inside the tabs.
  • Achievements: How to create achievements for a layer (or for the whole game).
  • Infoboxes: Boxes containing text that can be shown or hidden.
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/public/gamedevtree/docs/achievements.html b/public/gamedevtree/docs/achievements.html index 0aa1d1ba..ede18a9a 100644 --- a/public/gamedevtree/docs/achievements.html +++ b/public/gamedevtree/docs/achievements.html @@ -8,11 +8,7 @@ - - - - - + @@ -33,8 +29,8 @@ more features } etc - }

Each achievement should have an id where the first digit is the row and the second digit is the column. Individual achievement can have these features:

  • name: optional, displayed at the top of the achievement. The only visible text. It can also be a function that returns updating text. Can use basic HTML.

  • done(): A function returning a boolean to determine if the achievement should be awarded.

  • tooltip: Default tooltip for the achievement, appears when it is hovered over. Should convey the goal and any reward for completing the achievement. It can also be a function that returns updating text. Can use basic HTML.

  • effect(): optional, A function that calculates and returns the current values of any bonuses from the achievement. Can return a value or an object containing multiple values.

  • unlocked(): optional, A function returning a bool to determine if the achievement is visible or not. Default is unlocked.

  • onComplete() - optional, this function will be called when the achievement is completed.

  • style: Optional, Applies CSS to this achievement, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the achievement was stored under, for convenient access. The achievement in the example's id is 11.

  • goalTooltip: optional, depracated Appears when the achievement is hovered over and locked, overrides the basic tooltip. This is to display the goal (or a hint). It can also be a function that returns updating text. Can use basic HTML.

  • doneTooltip: optional, depracated Appears when the achievement is hovered over and completed, overrides the basic tooltip. This can display what the player achieved (the goal), and the rewards, if any. It can also be a function that returns updating text. Can use basic HTML.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- + }

Each achievement should have an id where the first digit is the row and the second digit is the column. Individual achievement can have these features:

  • name: optional, displayed at the top of the achievement. The only visible text. It can also be a function that returns updating text. Can use basic HTML.

  • done(): A function returning a boolean to determine if the achievement should be awarded.

  • tooltip: Default tooltip for the achievement, appears when it is hovered over. Should convey the goal and any reward for completing the achievement. It can also be a function that returns updating text. Can use basic HTML.

  • effect(): optional, A function that calculates and returns the current values of any bonuses from the achievement. Can return a value or an object containing multiple values.

  • unlocked(): optional, A function returning a bool to determine if the achievement is visible or not. Default is unlocked.

  • onComplete() - optional, this function will be called when the achievement is completed.

  • style: Optional, Applies CSS to this achievement, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the achievement was stored under, for convenient access. The achievement in the example's id is 11.

  • goalTooltip: optional, depracated Appears when the achievement is hovered over and locked, overrides the basic tooltip. This is to display the goal (or a hint). It can also be a function that returns updating text. Can use basic HTML.

  • doneTooltip: optional, depracated Appears when the achievement is hovered over and completed, overrides the basic tooltip. This can display what the player achieved (the goal), and the rewards, if any. It can also be a function that returns updating text. Can use basic HTML.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/public/gamedevtree/docs/bars.html b/public/gamedevtree/docs/bars.html index a68c07f4..944bdf7a 100644 --- a/public/gamedevtree/docs/bars.html +++ b/public/gamedevtree/docs/bars.html @@ -8,11 +8,7 @@ - - - - - + @@ -31,8 +27,8 @@ etc } etc - }

Features:

  • direction: UP, DOWN, LEFT, or RIGHT (not Strings). Determines the direction that the bar is filled as it progresses. RIGHT means from left to right.

  • width, height: The size in pixels of the bar, but as Numbers (no "px" at the end)

  • progress(): A function that returns the portion of the bar that is filled, from "empty" at 0 to "full" at 1. (Nothing bad happens if the value goes out of these bounds, and it can be a number or Decimal).

  • display(): optional, A function that returns text to be displayed on top of the bar, can use HTML.

  • unlocked(): optional, A function returning a bool to determine if the bar is visible or not. Default is unlocked.

  • baseStyle, fillStyle, borderStyle, textStyle: Optional, Apply CSS to the unfilled portion, filled portion, border, and display text on the bar, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the bar was stored under, for convenient access. The bar in the example's id is "bigBar".

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- + }

Features:

  • direction: UP, DOWN, LEFT, or RIGHT (not Strings). Determines the direction that the bar is filled as it progresses. RIGHT means from left to right.

  • width, height: The size in pixels of the bar, but as Numbers (no "px" at the end)

  • progress(): A function that returns the portion of the bar that is filled, from "empty" at 0 to "full" at 1. (Nothing bad happens if the value goes out of these bounds, and it can be a number or Decimal).

  • display(): optional, A function that returns text to be displayed on top of the bar, can use HTML.

  • unlocked(): optional, A function returning a bool to determine if the bar is visible or not. Default is unlocked.

  • baseStyle, fillStyle, borderStyle, textStyle: Optional, Apply CSS to the unfilled portion, filled portion, border, and display text on the bar, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the bar was stored under, for convenient access. The bar in the example's id is "bigBar".

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/public/gamedevtree/docs/basic-layer-breakdown.html b/public/gamedevtree/docs/basic-layer-breakdown.html index 11a74a23..305f12d8 100644 --- a/public/gamedevtree/docs/basic-layer-breakdown.html +++ b/public/gamedevtree/docs/basic-layer-breakdown.html @@ -8,11 +8,7 @@ - - - - - + @@ -52,8 +48,8 @@ }, layerShown() {return true}, // Returns a bool for if this layer's node should be visible in the tree. - },
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- + },
CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/public/gamedevtree/docs/buyables.html b/public/gamedevtree/docs/buyables.html index 005c9a76..837ee21f 100644 --- a/public/gamedevtree/docs/buyables.html +++ b/public/gamedevtree/docs/buyables.html @@ -8,11 +8,7 @@ - - - - - + @@ -38,8 +34,8 @@ etc } etc - }

Features:

  • title: optional, displayed at the top in a larger font It can also be a function that returns updating text.

  • cost(): cost for buying the next buyable. Can have an optional argument "x" to calculate the cost of the x+1th object, but needs to use "current amount" as a default value for x. (x is a Decimal). Can return an object if there are multiple currencies.

  • effect(): optional, A function that calculates and returns the current values of bonuses of this buyable. Can return a value or an object containing multiple values.

  • display(): A function returning everything that should be displayed on the buyable after the title, likely including the description, amount bought, cost, and current effect. Can use basic HTML.

  • unlocked(): optional, A function returning a bool to determine if the buyable is visible or not. Default is unlocked.

  • canAfford(): A function returning a bool to determine if you can buy one of the buyables.

  • buy(): A function that implements buying one of the buyable, including spending the currency.

  • buyMax(): optional, A function that implements buying as many of the buyable as possible.

  • style: Optional, Applies CSS to this buyable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the buyable was stored under, for convenient access. The buyable in the example's id is 11.

Sell One/Sell All:

Including a sellOne or sellAll function will cause an additional button to appear beneath the buyable. They are functionally identical, but "sell one" appears above "sell all". You can also use them for other things.

sellOne/sellAll(): optional, Called when the button is pressed. The standard use would be to decrease/reset the amount of the buyable, And possibly return some currency to the player.

canSellOne/canSellAll(): optional, booleans determining whether or not to show the buttons. If "canSellOne/All" is absent but "sellOne/All" is present, the appropriate button will always show.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- + }

Features:

  • title: optional, displayed at the top in a larger font It can also be a function that returns updating text.

  • cost(): cost for buying the next buyable. Can have an optional argument "x" to calculate the cost of the x+1th object, but needs to use "current amount" as a default value for x. (x is a Decimal). Can return an object if there are multiple currencies.

  • effect(): optional, A function that calculates and returns the current values of bonuses of this buyable. Can return a value or an object containing multiple values.

  • display(): A function returning everything that should be displayed on the buyable after the title, likely including the description, amount bought, cost, and current effect. Can use basic HTML.

  • unlocked(): optional, A function returning a bool to determine if the buyable is visible or not. Default is unlocked.

  • canAfford(): A function returning a bool to determine if you can buy one of the buyables.

  • buy(): A function that implements buying one of the buyable, including spending the currency.

  • buyMax(): optional, A function that implements buying as many of the buyable as possible.

  • style: Optional, Applies CSS to this buyable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the buyable was stored under, for convenient access. The buyable in the example's id is 11.

Sell One/Sell All:

Including a sellOne or sellAll function will cause an additional button to appear beneath the buyable. They are functionally identical, but "sell one" appears above "sell all". You can also use them for other things.

sellOne/sellAll(): optional, Called when the button is pressed. The standard use would be to decrease/reset the amount of the buyable, And possibly return some currency to the player.

canSellOne/canSellAll(): optional, booleans determining whether or not to show the buttons. If "canSellOne/All" is absent but "sellOne/All" is present, the appropriate button will always show.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/public/gamedevtree/docs/challenges.html b/public/gamedevtree/docs/challenges.html index 73fa22c9..dd677cb6 100644 --- a/public/gamedevtree/docs/challenges.html +++ b/public/gamedevtree/docs/challenges.html @@ -8,11 +8,7 @@ - - - - - + @@ -33,8 +29,8 @@ etc } etc - }

Each challenge should have an id where the first digit is the row and the second digit is the column. Individual Challenges can have these features:

  • name: Name of the challenge, can be a string or a function. Can use basic HTML.

  • challengeDescription: A description of what makes the challenge a challenge. You will need to implement these elsewhere It can also be a function that returns updating text. Can use basic HTML.

  • rewardDescription: A description of the reward's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

  • rewardEffect(): optional, A function that calculates and returns the current values of any bonuses from the reward. Can return a value or an object containing multiple values. Can use basic HTML.

  • rewardDisplay(): optional, A function that returns a display of the current effects of the reward with formatting. Default behavior is to just display the a number appropriately formatted.

  • goal: A Decimal for the amount of currency required to beat the challenge. By default, the goal is in basic Points. The goal can also be a function if its value changes.

  • unlocked(): optional, A function returning a bool to determine if the challenge is visible or not. Default is unlocked.

  • onComplete() - optional, this function will be called when the challenge is completed when previously incomplete.

  • countsAs: optional, If a challenge combines the effects of other challenges in this layer, you can use this. An array of challenge ids. The player is effectively in all of those challenges when in the current one.

By default, challenges use basic Points for the goal. You can change that using these features.

  • currencyDisplayName: optional, the name to display for the currency for the goal

  • currencyInternalName: optional, the internal name for that currency

  • currencyLayer: optional, the internal name of the layer that currency is stored in. If it's not in a layer, omit. If it's not stored directly in a layer, instead use the next feature.

  • currencyLocation: optional, if your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

  • completionLimit: optional, the amount of times you can complete this challenge. Default is 1 completion.

  • style: Optional, Applies CSS to this challenge, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the challenge was stored under, for convenient access. The challenge in the example's id is 11.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- + }

Each challenge should have an id where the first digit is the row and the second digit is the column. Individual Challenges can have these features:

  • name: Name of the challenge, can be a string or a function. Can use basic HTML.

  • challengeDescription: A description of what makes the challenge a challenge. You will need to implement these elsewhere It can also be a function that returns updating text. Can use basic HTML.

  • rewardDescription: A description of the reward's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

  • rewardEffect(): optional, A function that calculates and returns the current values of any bonuses from the reward. Can return a value or an object containing multiple values. Can use basic HTML.

  • rewardDisplay(): optional, A function that returns a display of the current effects of the reward with formatting. Default behavior is to just display the a number appropriately formatted.

  • goal: A Decimal for the amount of currency required to beat the challenge. By default, the goal is in basic Points. The goal can also be a function if its value changes.

  • unlocked(): optional, A function returning a bool to determine if the challenge is visible or not. Default is unlocked.

  • onComplete() - optional, this function will be called when the challenge is completed when previously incomplete.

  • countsAs: optional, If a challenge combines the effects of other challenges in this layer, you can use this. An array of challenge ids. The player is effectively in all of those challenges when in the current one.

By default, challenges use basic Points for the goal. You can change that using these features.

  • currencyDisplayName: optional, the name to display for the currency for the goal

  • currencyInternalName: optional, the internal name for that currency

  • currencyLayer: optional, the internal name of the layer that currency is stored in. If it's not in a layer, omit. If it's not stored directly in a layer, instead use the next feature.

  • currencyLocation: optional, if your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

  • completionLimit: optional, the amount of times you can complete this challenge. Default is 1 completion.

  • style: Optional, Applies CSS to this challenge, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the challenge was stored under, for convenient access. The challenge in the example's id is 11.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/public/gamedevtree/docs/clickables.html b/public/gamedevtree/docs/clickables.html index d7cc6032..4a410366 100644 --- a/public/gamedevtree/docs/clickables.html +++ b/public/gamedevtree/docs/clickables.html @@ -8,11 +8,7 @@ - - - - - + @@ -37,8 +33,8 @@ etc } etc - }

Features:

  • title: optional, displayed at the top in a larger font It can also be a function that returns updating text.

  • effect(): optional, A function that calculates and returns the current values of bonuses of this clickable. Can return a value or an object containing multiple values.

  • display(): A function returning everything that should be displayed on the clickable after the title, likely changing based on its state. Can use basic HTML.

  • unlocked(): optional, A function returning a bool to determine if the clickable is visible or not. Default is unlocked.

  • canClick(): A function returning a bool to determine if you can click the clickable.

  • onClick(): A function that implements clicking one of the clickable.

  • style: Optional, Applies CSS to this clickable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

  • id: Assigned automagically. It's the "key" which the clickable was stored under, for convenient access. The clickable in the example's id is 11.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- + }

Features:

  • title: optional, displayed at the top in a larger font It can also be a function that returns updating text.

  • effect(): optional, A function that calculates and returns the current values of bonuses of this clickable. Can return a value or an object containing multiple values.

  • display(): A function returning everything that should be displayed on the clickable after the title, likely changing based on its state. Can use basic HTML.

  • unlocked(): optional, A function returning a bool to determine if the clickable is visible or not. Default is unlocked.

  • canClick(): A function returning a bool to determine if you can click the clickable.

  • onClick(): A function that implements clicking one of the clickable.

  • style: Optional, Applies CSS to this clickable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

  • id: Assigned automagically. It's the "key" which the clickable was stored under, for convenient access. The clickable in the example's id is 11.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/public/gamedevtree/docs/custom-tab-layouts.html b/public/gamedevtree/docs/custom-tab-layouts.html index 79d1ddf0..47103857 100644 --- a/public/gamedevtree/docs/custom-tab-layouts.html +++ b/public/gamedevtree/docs/custom-tab-layouts.html @@ -8,11 +8,7 @@ - - - - - + @@ -33,8 +29,8 @@ {"color": "red", "font-size": "32px", "font-family": "Comic Sans MS"}], "blank", ["toggle", ["c", "beep"]], - "milestones", "blank", "blank", "upgrades"]

It is a list of components, which can be either just a name, or an array with arguments. If it's an array, the first item is the name of the component, the second is the data passed into it, and the third (optional) applies a CSS style to it with a "CSS object", where the keys are CSS attributes.

These are the existing components, but you can create more in v.js:

  • display-text: Displays some text (can use basic HTML). The argument is the text to display. It can also be a function that returns updating text.

  • raw-html: Displays some basic HTML, can also be a function.

  • blank: Adds empty space. The default dimensions are 8px x 17px. The argument changes the dimensions. If it's a single value (e.g. "20px"), that determines the height. If you have a pair of arguments, the first is width and the second is height.

  • row: Display a list of components horizontally. The argument is an array of components in the tab layout format.

  • column: Display a list of components vertically. The argument is an array of components in the tab layout format. This is useful to display columns within a row.

  • main-display: The text that displays the main currency for the layer and its effects.

  • resource-display: The text that displays the currency that this layer is based on, as well as the best and/or total values for this layer's prestige currency (if they are put in startData for this layer)

  • prestige-button: The argument is a string that the prestige button should say before the amount of currency you will gain. It can also be a function that returns updating text.

  • upgrades, milestones, challs, achievements: Display the upgrades, milestones, and challenges for a layer, as appropriate.

  • buyables, clickables: Display all of the buyables/clickables for this layer, as appropriate. The argument optional, and is the size of the boxes in pixels.

  • microtabs: Display a set of subtabs for an area. The argument is the name of the set of microtabs in the "microtabs" feature.

  • bar: Display a bar. The argument is the id of the bar to display.

  • infobox: Display an infobox. The argument is the id of the infobox to display.

  • toggle: A toggle button that toggles a bool value. The data is a pair that identifies what bool to toggle, [layer, id]

The rest of the components are sub-components. They can be used just like other components, but are typically part of another component.

  • upgrade, milestone, chall, buyable, clickable, achievement: An individual upgrade, challenge, etc. The argument is the id. This can be used if you want to have upgrades split up across multiple subtabs, for example.

  • respec-button, master-button: The respec and master buttons for buyables and clickables, respectively.

  • sell-one, sell-all: The "sell one" and "sell all" for buyables, respectively. The argument is the id of the buyable.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- + "milestones", "blank", "blank", "upgrades"]

It is a list of components, which can be either just a name, or an array with arguments. If it's an array, the first item is the name of the component, the second is the data passed into it, and the third (optional) applies a CSS style to it with a "CSS object", where the keys are CSS attributes.

These are the existing components, but you can create more in v.js:

  • display-text: Displays some text (can use basic HTML). The argument is the text to display. It can also be a function that returns updating text.

  • raw-html: Displays some basic HTML, can also be a function.

  • blank: Adds empty space. The default dimensions are 8px x 17px. The argument changes the dimensions. If it's a single value (e.g. "20px"), that determines the height. If you have a pair of arguments, the first is width and the second is height.

  • row: Display a list of components horizontally. The argument is an array of components in the tab layout format.

  • column: Display a list of components vertically. The argument is an array of components in the tab layout format. This is useful to display columns within a row.

  • main-display: The text that displays the main currency for the layer and its effects.

  • resource-display: The text that displays the currency that this layer is based on, as well as the best and/or total values for this layer's prestige currency (if they are put in startData for this layer)

  • prestige-button: The argument is a string that the prestige button should say before the amount of currency you will gain. It can also be a function that returns updating text.

  • upgrades, milestones, challs, achievements: Display the upgrades, milestones, and challenges for a layer, as appropriate.

  • buyables, clickables: Display all of the buyables/clickables for this layer, as appropriate. The argument optional, and is the size of the boxes in pixels.

  • microtabs: Display a set of subtabs for an area. The argument is the name of the set of microtabs in the "microtabs" feature.

  • bar: Display a bar. The argument is the id of the bar to display.

  • infobox: Display an infobox. The argument is the id of the infobox to display.

  • toggle: A toggle button that toggles a bool value. The data is a pair that identifies what bool to toggle, [layer, id]

The rest of the components are sub-components. They can be used just like other components, but are typically part of another component.

  • upgrade, milestone, chall, buyable, clickable, achievement: An individual upgrade, challenge, etc. The argument is the id. This can be used if you want to have upgrades split up across multiple subtabs, for example.

  • respec-button, master-button: The respec and master buttons for buyables and clickables, respectively.

  • sell-one, sell-all: The "sell one" and "sell all" for buyables, respectively. The argument is the id of the buyable.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/public/gamedevtree/docs/getting-started.html b/public/gamedevtree/docs/getting-started.html index e7abb7fb..6eb6016a 100644 --- a/public/gamedevtree/docs/getting-started.html +++ b/public/gamedevtree/docs/getting-started.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
The Paper Pilot

Appearance

Getting started ​

Welcome to The Modding Tree!

Using the Modding Tree, at its simplest level, just requires getting a copy of it onto your computer. However, if you do it the right way, it will help in many ways.

Don't let the word "Github" scare you away. It's actually much easier to use than most people think, especially because most people use it the hard way. The key is Github Desktop, which lets you do everything you need to, without even touching the command line.

The benefits of using Github:

  • It makes it much, much easier to update The Modding Tree.
  • You can share your work without any extra effort using githack, or with a bit more effort, set up a github.io site.
  • It lets you undo changes to your code, and to have multiple versions of it.
  • It lets you collaborate with other people, if you want to.

Getting set up with Github and The Modding Tree: ​

  1. Install Github Desktop and Visual Studio Code.

  2. Make a Github account. You can handle this on your own.

  3. Log in on your browser, and go back to The Modding Tree page. At the top right, there should be a button that says "fork". Click on it, and then on your username. You now have your own fork, or copy, of The Modding Tree.

  4. Open Github Desktop and log in. Ignore everything else and choose "clone a repository". A "repository" is basically a "Github project", like The Modding Tree. "Cloning" is downloading a copy of the repository to your computer.

  5. Look for The Modding Tree in the list of repositiories (it should be the only one) and click "clone".

  6. Select that you're using it for your own purposes, and click continue. It will download the files and handle everything.

Using your repository ​

  1. Click on "show in finder" to the right, and then open index.html. This will let you view and test your project!

  2. To edit your project, click "open in VSCode" in Github Desktop.

  3. Open mod.js in VSCode, and look at the top part where it says "modInfo". On the lines below that, change the mod's name to whatever you want, and change the id as well. (It can be any string value, and it's used to determine where the savefile is. Make it something that's probably unique, and don't change it again later.)

  4. Save game.js, and then reload index.html. The title on the tab, as well as on the info page, will now be the new ones!

  5. Go back to Github Desktop. It's time to save your changes into the git system by making a "commit".

  6. At the bottom right corner, add a summary of your changes, and then click "commit to master".

  7. Finally, at the top middle, click "push origin" to push your changes out onto the online repository.

  8. You can view your project on line, or share it with others, by going to https://raw.githack.com/[YOUR-GITHUB-USERNAME]/The-Modding-Tree/master/index.html

And now, you have successfully used Github! You can look at the documentation to see how The Modding Tree's system works and to make your mod a reality.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +
The Paper Pilot

Appearance

Getting started ​

Welcome to The Modding Tree!

Using the Modding Tree, at its simplest level, just requires getting a copy of it onto your computer. However, if you do it the right way, it will help in many ways.

Don't let the word "Github" scare you away. It's actually much easier to use than most people think, especially because most people use it the hard way. The key is Github Desktop, which lets you do everything you need to, without even touching the command line.

The benefits of using Github:

  • It makes it much, much easier to update The Modding Tree.
  • You can share your work without any extra effort using githack, or with a bit more effort, set up a github.io site.
  • It lets you undo changes to your code, and to have multiple versions of it.
  • It lets you collaborate with other people, if you want to.

Getting set up with Github and The Modding Tree: ​

  1. Install Github Desktop and Visual Studio Code.

  2. Make a Github account. You can handle this on your own.

  3. Log in on your browser, and go back to The Modding Tree page. At the top right, there should be a button that says "fork". Click on it, and then on your username. You now have your own fork, or copy, of The Modding Tree.

  4. Open Github Desktop and log in. Ignore everything else and choose "clone a repository". A "repository" is basically a "Github project", like The Modding Tree. "Cloning" is downloading a copy of the repository to your computer.

  5. Look for The Modding Tree in the list of repositiories (it should be the only one) and click "clone".

  6. Select that you're using it for your own purposes, and click continue. It will download the files and handle everything.

Using your repository ​

  1. Click on "show in finder" to the right, and then open index.html. This will let you view and test your project!

  2. To edit your project, click "open in VSCode" in Github Desktop.

  3. Open mod.js in VSCode, and look at the top part where it says "modInfo". On the lines below that, change the mod's name to whatever you want, and change the id as well. (It can be any string value, and it's used to determine where the savefile is. Make it something that's probably unique, and don't change it again later.)

  4. Save game.js, and then reload index.html. The title on the tab, as well as on the info page, will now be the new ones!

  5. Go back to Github Desktop. It's time to save your changes into the git system by making a "commit".

  6. At the bottom right corner, add a summary of your changes, and then click "commit to master".

  7. Finally, at the top middle, click "push origin" to push your changes out onto the online repository.

  8. You can view your project on line, or share it with others, by going to https://raw.githack.com/[YOUR-GITHUB-USERNAME]/The-Modding-Tree/master/index.html

And now, you have successfully used Github! You can look at the documentation to see how The Modding Tree's system works and to make your mod a reality.

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/public/gamedevtree/docs/infoboxes.html b/public/gamedevtree/docs/infoboxes.html index 9a73b059..ad70232a 100644 --- a/public/gamedevtree/docs/infoboxes.html +++ b/public/gamedevtree/docs/infoboxes.html @@ -8,11 +8,7 @@ - - - - - + @@ -31,8 +27,8 @@ etc } etc - }

Features:

  • title: The text displayed above the main box. Can be a function to be dynamic, and can use basic HTML.

  • body: The text displayed inside the box. Can be a function to be dynamic, and can use basic HTML.

  • style, titleStyle, bodyStyle: Optional, Apply CSS to the infobox, or to the title button or body of the infobox, in the form of an object where the keys are CSS attributes, and the values are the Values for those attributes (both as strings).

  • unlocked(): optional, A function returning a bool to determine if the infobox is visible or not. Default is unlocked.

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the bar was stored under, for convenient access. The bar in the example's id is "bigBar".

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- + }

Features:

  • title: The text displayed above the main box. Can be a function to be dynamic, and can use basic HTML.

  • body: The text displayed inside the box. Can be a function to be dynamic, and can use basic HTML.

  • style, titleStyle, bodyStyle: Optional, Apply CSS to the infobox, or to the title button or body of the infobox, in the form of an object where the keys are CSS attributes, and the values are the Values for those attributes (both as strings).

  • unlocked(): optional, A function returning a bool to determine if the infobox is visible or not. Default is unlocked.

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the bar was stored under, for convenient access. The bar in the example's id is "bigBar".

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
+ \ No newline at end of file diff --git a/public/gamedevtree/docs/layer-features.html b/public/gamedevtree/docs/layer-features.html index af75dd7e..775349cb 100644 --- a/public/gamedevtree/docs/layer-features.html +++ b/public/gamedevtree/docs/layer-features.html @@ -8,11 +8,7 @@ - - - - - + @@ -40,8 +36,8 @@

  • update(diff): optional, this function is called every game tick. Use it for any passive resource production or time-based things. diff is the time since the last tick. Suggestion: use addPoints(layer, gain) when generating points to automatically update the best and total amounts.

  • automate(): optional, this function is called every game tick, after production. Use it to activate any autobuyers or auto-resets or similar on this layer, if appropriate.

  • resetsNothing: optional, returns true if this layer shouldn't trigger any resets when you prestige.

  • increaseUnlockOrder: optional, an array of layer ids. When this layer is unlocked for the first time, the unlockOrder value for any not-yet-unlocked layers in this list increases. This can be used to make them harder to unlock.

  • shouldNotify: optional, a function to return true if this layer should be highlighted in the tree. The layer will automatically be highlighted if you can buy an upgrade whether you have this or not.

  • componentStyles: optional, An object that contains a set of functions returning CSS objects. Each of these will be applied to any components on the layer with the type of its id. Example:

    • js
            componentStyles: {
             "challenge"() {return {'height': '200px'}},
             "prestige-button"() {return {'color': '#AA66AA'}},
-        },

    Custom Prestige type ​

    • getResetGain(): For custom prestige type, Returns how many points you should get if you reset now. You can call getResetGain(this.layer, useType = "static") or similar to calculate what your gain would be under another prestige type (provided you have all of the required features in the layer.)

    • getNextAt(canMax=false): For custom prestige type, Returns how many of the base currency you need to get to the next point. canMax is an optional variable used with Static-ish layers to differentiate between if it's looking for the first point you can reset at, or the requirement for any gain at all. (Supporting both is good). You can also call getNextAt(this.layer, canMax=false, useType = "static") or similar to calculate what your next at would be under another prestige type (provided you have all of the required features in the layer.)

    • canReset(): For custom prestige type, return true only if you have the resources required to do a prestige here.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - + },

    Custom Prestige type ​

    • getResetGain(): For custom prestige type, Returns how many points you should get if you reset now. You can call getResetGain(this.layer, useType = "static") or similar to calculate what your gain would be under another prestige type (provided you have all of the required features in the layer.)

    • getNextAt(canMax=false): For custom prestige type, Returns how many of the base currency you need to get to the next point. canMax is an optional variable used with Static-ish layers to differentiate between if it's looking for the first point you can reset at, or the requirement for any gain at all. (Supporting both is good). You can also call getNextAt(this.layer, canMax=false, useType = "static") or similar to calculate what your next at would be under another prestige type (provided you have all of the required features in the layer.)

    • canReset(): For custom prestige type, return true only if you have the resources required to do a prestige here.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/gamedevtree/docs/main-mod-info.html b/public/gamedevtree/docs/main-mod-info.html index f49887ef..37b807b6 100644 --- a/public/gamedevtree/docs/main-mod-info.html +++ b/public/gamedevtree/docs/main-mod-info.html @@ -8,11 +8,7 @@ - - - - - + @@ -29,8 +25,8 @@ var doNotCallTheseFunctionsEveryTick = ["doReset", "buy", "onPurchase", "blowUpEverything"]

    • getStartPoints(): A function to determine the amount of points the player starts with after a reset. (returns a Decimal value)

    • canGenPoints(): A function returning a boolean for if points should be generated. Use this if you want an upgrade to unlock generating points.

    • getPointGen(): A function that calculates your points per second. Anything that affects your point gain should go into the calculation here.

    • addedPlayerData(): A function that returns any non-layer-related data that you want to be added to the save data and "player" object.

    js
    function addedPlayerData() { return {
 	weather: "Yes",
 	happiness: new Decimal(72),
-}}

    • displayThings: An array of functions used to display extra things at the top of the tree tab. Each function returns a string, which is a line to display (with basic HTML support). If a function returns nothing, nothing is displayed (and it doesn't take up a line).

    • isEndgame(): A function to determine if the player has reached the end of the game, at which point the "you win!" screen appears.

    Less important things beyond this point!

    • maxTickLength(): Returns the maximum tick length, in milliseconds. Only really useful if you have something that reduces over time, which long ticks mess up (usually a challenge).
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}}

    • displayThings: An array of functions used to display extra things at the top of the tree tab. Each function returns a string, which is a line to display (with basic HTML support). If a function returns nothing, nothing is displayed (and it doesn't take up a line).

    • isEndgame(): A function to determine if the player has reached the end of the game, at which point the "you win!" screen appears.

    Less important things beyond this point!

    • maxTickLength(): Returns the maximum tick length, in milliseconds. Only really useful if you have something that reduces over time, which long ticks mess up (usually a challenge).
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/gamedevtree/docs/milestones.html b/public/gamedevtree/docs/milestones.html index 06943b2b..5546e40e 100644 --- a/public/gamedevtree/docs/milestones.html +++ b/public/gamedevtree/docs/milestones.html @@ -8,11 +8,7 @@ - - - - - + @@ -31,8 +27,8 @@ } etc }

    You can use hasMilestone(layer, id) to determine if the player has a given milestone

    Milestone features:

    • requirementDesc: A string describing the requirement for unlocking this milestone. Suggestion: Use a "total". It can also be a function that returns updating text. Can use basic HTML.

    • effectDesc: A string describing the reward for having the milestone. You will have to implement the reward elsewhere. It can also be a function that returns updating text. Can use basic HTML.

    • done(): A function returning a boolean to determine if the milestone should be awarded.

    • toggles: optional, Creates toggle buttons that appear on the milestone when it is unlocked. The toggles can toggle a given boolean value in a layer. It is defined as an array of paired items, one pair per toggle. The first is the internal name of the layer the value being toggled is stored in, and the second is the internal name of the variable to toggle. (e.g. [["b", "auto"], ["g", "auto"])

           **Tip:** Toggles are not de-set if the milestone becomes locked! In this case, you should also check if the player has the milestone.
-

    • style: Optional, Applies CSS to this milestone, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

    • unlocked(): Optional A function returning a boolean to determine if the milestone should be shown. If absent, it is always shown.

    • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

    • id: Assigned automagically. It's the "key" which the milestone was stored under, for convenient access. The milestone in the example's id is 0.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +

  • style: Optional, Applies CSS to this milestone, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

  • unlocked(): Optional A function returning a boolean to determine if the milestone should be shown. If absent, it is always shown.

  • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

  • id: Assigned automagically. It's the "key" which the milestone was stored under, for convenient access. The milestone in the example's id is 0.

    • CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/gamedevtree/docs/subtabs-and-microtabs.html b/public/gamedevtree/docs/subtabs-and-microtabs.html index 1c673908..d1280c39 100644 --- a/public/gamedevtree/docs/subtabs-and-microtabs.html +++ b/public/gamedevtree/docs/subtabs-and-microtabs.html @@ -8,11 +8,7 @@ - - - - - + @@ -47,8 +43,8 @@ otherStuff: { // There could be another set of microtabs here } - },

    Normal subtabs and microtab subtabs both use the same features:

    Features: ​

    • content: The tab layout code for the subtab, in the tab layout format

    • style: Optional, Applies CSS to the whole subtab when switched to, in the form of an "CSS Object", where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

    • buttonStyle: Optional, A CSS object, which affects the appearance of the button for that subtab.

    • unlocked(): Optional, a function to determine if the button for this subtab should be visible. By default, a subtab is always unlocked. (You can't use the "this" keyword in this function.)

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - + },

    Normal subtabs and microtab subtabs both use the same features:

    Features: ​

    • content: The tab layout code for the subtab, in the tab layout format

    • style: Optional, Applies CSS to the whole subtab when switched to, in the form of an "CSS Object", where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

    • buttonStyle: Optional, A CSS object, which affects the appearance of the button for that subtab.

    • unlocked(): Optional, a function to determine if the button for this subtab should be visible. By default, a subtab is always unlocked. (You can't use the "this" keyword in this function.)

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/gamedevtree/docs/updating-tmt.html b/public/gamedevtree/docs/updating-tmt.html index 242575e4..4a3381eb 100644 --- a/public/gamedevtree/docs/updating-tmt.html +++ b/public/gamedevtree/docs/updating-tmt.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
    The Paper Pilot

    Appearance

    Updating The Modding Tree ​

    This tutorial assumes that you have used the Getting Started Tutorial, and are using Github Desktop and VSCode for your mod.

    Here's what you have to do when there's a TMT update:

    1. Look at the changelog. It will warn you if the update will break anything or require any changes. Decide if you want to try to update.

    2. Open Github Desktop, and at the top middle, click "fetch origin". This will make Github Desktop get information about the update.

    3. Click where it says "current branch: master" at the top middle, and at the bottom of the thing that appears, click "choose a branch to merge into master.

    4. Select upstream/master. It will likely say there are conflicts, but you have tools to resolve them. Click "Merge upstream/master into master".

    5. A conflict happens when the things you're trying to merge have both made changes in the same place. Click "open in Visual Studio Code" next to the first file.

    6. Scroll down through the file, and look for the parts highlighted in red and green. One of these is your code, and the other is some code that will be modified by the update. Do your best to try to edit things to keep the updated changes, but keep your content.

    7. Continue to do this for all remaining challenges.

    8. Do any other changes required by the update, run the game, fix issues, etc.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +
    The Paper Pilot

    Appearance

    Updating The Modding Tree ​

    This tutorial assumes that you have used the Getting Started Tutorial, and are using Github Desktop and VSCode for your mod.

    Here's what you have to do when there's a TMT update:

    1. Look at the changelog. It will warn you if the update will break anything or require any changes. Decide if you want to try to update.

    2. Open Github Desktop, and at the top middle, click "fetch origin". This will make Github Desktop get information about the update.

    3. Click where it says "current branch: master" at the top middle, and at the bottom of the thing that appears, click "choose a branch to merge into master.

    4. Select upstream/master. It will likely say there are conflicts, but you have tools to resolve them. Click "Merge upstream/master into master".

    5. A conflict happens when the things you're trying to merge have both made changes in the same place. Click "open in Visual Studio Code" next to the first file.

    6. Scroll down through the file, and look for the parts highlighted in red and green. One of these is your code, and the other is some code that will be modified by the update. Do your best to try to edit things to keep the updated changes, but keep your content.

    7. Continue to do this for all remaining challenges.

    8. Do any other changes required by the update, run the game, fix issues, etc.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/gamedevtree/docs/upgrades.html b/public/gamedevtree/docs/upgrades.html index 1151f063..583c61fa 100644 --- a/public/gamedevtree/docs/upgrades.html +++ b/public/gamedevtree/docs/upgrades.html @@ -8,11 +8,7 @@ - - - - - + @@ -33,8 +29,8 @@ more features } etc - }

    Each upgrade should have an id where the first digit is the row and the second digit is the column. Individual upgrades can have these features:

    • title: optional, displayed at the top in a larger font It can also be a function that returns updating text. Can use basic HTML.

    • description: A description of the upgrade's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

    • effect(): optional, A function that calculates and returns the current values of any bonuses from the upgrade. Can return a value or an object containing multiple values.

    • effectDisplay(): optional, A function that returns a display of the current effects of the upgrade with formatting. Default behavior is to just display the a number appropriately formatted. Can use basic HTML.

    • cost: A Decimal for the cost of the upgrade. By default, upgrades cost the main prestige currency for the layer.

    • unlocked(): optional, A function returning a bool to determine if the upgrade is visible or not. Default is unlocked.

    • onPurchase() - optional, this function will be called when the upgrade is purchased. Good for upgrades like "makes this layer act like it was unlocked first".

    By default, upgrades use the main prestige currency for the layer. You can include these to change them (but it needs to be a Decimal):

    • currencyDisplayName: optional, the name to display for the currency for the upgrade

    • currencyInternalName: optional, the internal name for that currency

    • currencyLayer: optional, the internal name of the layer that currency is stored in. If it's not in a layer (like Points), omit. If it's not stored directly in a layer, instead use the next feature.

    • currencyLocation: optional, if your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

    • style: Optional, Applies CSS to this upgrade, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

    • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

    • id: Assigned automagically. It's the "key" which the upgrade was stored under, for convenient access. The upgrade in the example's id is 11.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - + }

    Each upgrade should have an id where the first digit is the row and the second digit is the column. Individual upgrades can have these features:

    • title: optional, displayed at the top in a larger font It can also be a function that returns updating text. Can use basic HTML.

    • description: A description of the upgrade's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

    • effect(): optional, A function that calculates and returns the current values of any bonuses from the upgrade. Can return a value or an object containing multiple values.

    • effectDisplay(): optional, A function that returns a display of the current effects of the upgrade with formatting. Default behavior is to just display the a number appropriately formatted. Can use basic HTML.

    • cost: A Decimal for the cost of the upgrade. By default, upgrades cost the main prestige currency for the layer.

    • unlocked(): optional, A function returning a bool to determine if the upgrade is visible or not. Default is unlocked.

    • onPurchase() - optional, this function will be called when the upgrade is purchased. Good for upgrades like "makes this layer act like it was unlocked first".

    By default, upgrades use the main prestige currency for the layer. You can include these to change them (but it needs to be a Decimal):

    • currencyDisplayName: optional, the name to display for the currency for the upgrade

    • currencyInternalName: optional, the internal name for that currency

    • currencyLayer: optional, the internal name of the layer that currency is stored in. If it's not in a layer (like Points), omit. If it's not stored directly in a layer, instead use the next feature.

    • currencyLocation: optional, if your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

    • style: Optional, Applies CSS to this upgrade, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings)

    • layer: Assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

    • id: Assigned automagically. It's the "key" which the upgrade was stored under, for convenient access. The upgrade in the example's id is 11.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/Old Things/2.0-format-changes.html b/public/kronos/Old Things/2.0-format-changes.html index e3d165cf..8f23c20b 100644 --- a/public/kronos/Old Things/2.0-format-changes.html +++ b/public/kronos/Old Things/2.0-format-changes.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
    The Paper Pilot

    Appearance

    2.0 format changes ​

    • Temp format is changed from temp.something[layer] to temp[layer].something, for consistency
    • Challenges are now saved as an object with the amount of completions in each spot. (This will break saves.)
    • effectDisplay in Challenges and Upgrades no longer takes an argument, and neither does effect for Buyables
    • Buyable cost can take an argument for amount of buyables, but it needs to function if no argument is supplied (it should do the cost for the next purchase).
    • Generation of Points now happens in the main game loop (not in a layer update function), enabled by canGenPoints in game.js.
    • Changed fullLayerReset to layerDataReset, which takes an array of names of values to keep

    In addition, many names were changed, mostly expanding abbreviations:

    All instances of:

    • chall -> challenge
    • unl -> unlocked
    • upg -> upgrade (besides CSS)
    • amt -> amount
    • desc -> description
    • resCeil -> roundUpCost
    • order -> unlockOrder
    • incr_order -> increaseUnlockOrder

    Challenges:

    • desc -> challengeDescription
    • reward -> rewardDescription
    • effect -> rewardEffect
    • effectDisplay -> rewardDisplay
    • active -> challengeActive
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +
    The Paper Pilot

    Appearance

    2.0 format changes ​

    • Temp format is changed from temp.something[layer] to temp[layer].something, for consistency
    • Challenges are now saved as an object with the amount of completions in each spot. (This will break saves.)
    • effectDisplay in Challenges and Upgrades no longer takes an argument, and neither does effect for Buyables
    • Buyable cost can take an argument for amount of buyables, but it needs to function if no argument is supplied (it should do the cost for the next purchase).
    • Generation of Points now happens in the main game loop (not in a layer update function), enabled by canGenPoints in game.js.
    • Changed fullLayerReset to layerDataReset, which takes an array of names of values to keep

    In addition, many names were changed, mostly expanding abbreviations:

    All instances of:

    • chall -> challenge
    • unl -> unlocked
    • upg -> upgrade (besides CSS)
    • amt -> amount
    • desc -> description
    • resCeil -> roundUpCost
    • order -> unlockOrder
    • incr_order -> increaseUnlockOrder

    Challenges:

    • desc -> challengeDescription
    • reward -> rewardDescription
    • effect -> rewardEffect
    • effectDisplay -> rewardDisplay
    • active -> challengeActive
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/README.html b/public/kronos/README.html index 5711e332..addad34d 100644 --- a/public/kronos/README.html +++ b/public/kronos/README.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
    The Paper Pilot

    Appearance

    Kronos ​

    Play here.

    Updating the website:

    • git submodule update --remote
    • git add -A
    • git commit -m "Updated kronos"
    • git push
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +
    The Paper Pilot

    Appearance

    Kronos ​

    Play here.

    Updating the website:

    • git submodule update --remote
    • git add -A
    • git commit -m "Updated kronos"
    • git push
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/changelog.html b/public/kronos/changelog.html index 68f459ef..92625b17 100644 --- a/public/kronos/changelog.html +++ b/public/kronos/changelog.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
    The Paper Pilot

    Appearance

    The Modding Tree changelog: ​

    v2.5.9.2 - 5/19/21 ​

    • Fixed many issues with things not updating.

    v2.5.9.1 - 5/18/21 ​

    • Made text inputs never give NaNs.

    v2.5.9 - 5/18/21 ​

    • Fixed issue when using text inputs for Numbers.
    • Added particle color feature.
    • Particle speed and dir are updated as it moves.
    • Added setSpeed and setDir for particles.
    • Added more trig functions.

    v2.5.8 - 5/17/21 ​

    • Added makeShinies, which creates a stationary particle in a random spot.
    • Bars will visually update more quickly.
    • Fixed a major particle-related issue.
    • Fixed autoUpgrade.
    • Fixed a minor visual issue with tree nodes.

    v2.5.7 - 5/15/21 ​

    • Added a particle system! Not only can it be used for visual effects, but particles can interact with the mouse. They could be used to create golden cookies or collectables, for example.
    • Added marked feature to buyables, clickables, and challenges. By default, stars multi-completion challenges when maxed.
    • Added 'deactivated' feature to layers, which disables many features.
    • Improved number formatting slightly.

    v2.5.6 - 5/14/21 ​

    • You can now use non-numeric ids for upgrades, buyables, etc.
    • Fixed an exploit that let you buy an extra buyable.
    • Moved basic getter/setter functions to easyAccess.js.

    v2.5.5.2 - 5/12/21 ​

    • Fixed a major issue with buyables.
    • Fixed a variety of tabFormat-related issues.
    • Fixed commas appearing in decimal places (thanks to pg132!)

    v2.5.5.1 - 5/12/21 ​

    • Fixed clickables.

    v2.5.5 - 5/12/21 ​

    • Added grids! They are a grid of buttons which behave the same, but have their own data. Good for inventory grids, map tiles, and more!
    • Added "marked" feature to add a mark to a node. Can be an image instead of a star. (Originally by Jacorb)
    • Added "layer-proxy" component that lets you use components from another layer.
    • Added the ability to display non-whole numbers in main-display.

    v2.5.4 - 5/10/21 ​

    • Added a setting to always use single-tab mode.
    • Added directMult, which multiplies prestige gain after exponents and softcaps. It actually multiplies gain for static layers.
    • Added onEnter and onExit for challenges.
    • Improved displaying numbers between 0.0001 and 0.1.
    • Added documentation on how gainMult/Exp work for static layers.
    • Fixed a visual issue on mobile, thanks to thepaperpilot.
    • Improved documentation in general.

    v2.5.3 - 5/8/21 ​

    • Improved performance of tab formats and bars.
    • Respec confirmation settings are now kept on resets.
    • Improved compatibility with older browsers.
    • Fixed missing pixel on vertical bars.

    v2.5.2.1 - 5/7/21 ​

    • Fixed microtabs making layers highlight incorrectly.

    v2.5.2 - 5/7/21 ​

    • Added glowColor for subtabs.
    • Improved the display for extremely small numbers.
    • Fixed issues in the buyable docs.

    v2.5.1 - 5/7/21 ​

    • Fixed dynamic things in tabFormat not updating.

    v2.5: Dreams Really Do Come True - 5/7/21 ​

    • Optimizations, hopefully a significant amount.
    • Added OOM/s point gen display at high values (thanks to Ducdat!)
    • Only one tab will display if the window is not wide enough (also thanks to Ducdat!)
    • Holding down a buyable's button now buys it continuously.
    • New milestone setting will also show the most recently unlocked milestone. (Also renamed all settings to be clearer)
    • Added an onHold feature for clickables.
    • Layer nodes will be highlighted even if the player is on the same tab.
    • Added customizable node glowColor.
    • Added buyable purchaseLimit.
    • Amount is automatically supplied to buyable cost and effect functions.
    • Locked (not yet visible) milestones no longer take up space. Also fixed hidden milestones taking a tiny bit of space.
    • Re-centered respec buttons.
    • Force-displayed tooltips are not hidden by resets.
    • Added formatting support for very small numbers. Disabled in most places by default because rounding errors might cause issues. Access it with formatSmall, or enable it globally by adding "allowSmall: true" to modInfo.

    v2.4.1 - 4/29/21 ​

    • A number of minor fixes, many thanks to thepaperpilot.
    • The respec confirmation checkbox is now part of the respec-button component. (This also fixes the checkbox appearing when there is no respec button)
    • Added a few undocumented changes to the 2.4 changelog (the two at the bottom)

    v2.4: Rationalized Edition - 4/29/21 ​

    • Completely reworked tooltips. Shift-click a node to force its tooltip to stay displayed. (And hopefully finally fixed flickering!)

    • Added text-input and slider components.

    • Added the ability to toggle respec confirmations.

    • Added custom respec confirmation messages.

    • The red layer highlight will not appear before a layer is unlocked.

    • Added unlocking hotkeys.

    • You no longer need to supply 'rows' and 'cols' for any Big Features.

    • Node symbols can use HTML.

    • Added documentation for the respec button.

    • Added prestigeNotify to subtabs, and prestigeNotify in subtabs also highlights the layer node.

    • The version number no longer contains special characters or irrational numbers.

    • Added ctrlDown and shiftDown variables.

    • Tooltips now use HTML (this means you need to replace any newlines with
      )

    v2.π.1 - 4/7/21 ​

    • Fixed formatting for some larger numbers.
    • Upgrades will expand if there is too much text to display.
    • Fixed styling challenges.
    • No longer attempts to display a base currency when there is none.

    v2.π: Incrementally Updated - 2/5/21 ​

    • Performance improvements.
    • Fixed tooltips overlapping with the top display.
    • Clicking a popup dismisses it immediately.
    • Added support for bulk challenge completions.
    • "Best" is updated automatically.
    • Fixed keeping Decimal values on reset.
    • Code reorganization and style improvements by fudo.

    v2.3.5 - 12/21/20 ​

    • Added resetTime, which tracks the time since a layer prestiged or was reset.
    • A layer node will be highlighted red if one of its subtabs is highlighted red.
    • Fixed issues with keeping challenges, buyables, and clickables on reset.
    • Improved the unlocking of custom layers.
    • Other minor fixes.

    v2.3.4 - 12/16/20 ​

    • Added a node image feature.
    • Resource display now always shows the amount of the currency the layer's gain is based on.
    • Added spacing between tree nodes.
    • Another attempt to fix tooltip flickering.

    v2.3.3 - 12/13/20 ​

    • Fixed the first node in a row always taking up space.
    • layerShown is now optional.
    • All prestige types can now use features for custom prestige types.

    v2.3.2 - 12/13/20 ​

    • Fixed achievement/milestone popups.

    v2.3.1 - 12/12/20 ​

    • Another attempt to fix flickering tooltips.
    • The "this" keyword should work everywhere except tabFormat arrays (although I may have missed some things).
    • Fixed tree branches not updating when scrolling on the right-side tab.
    • Fixed a spacing issue when a node's symbol is ""
    • Removed some old, unneeded files.

    v2.3: Cooler and Newer Edition - 12/10/20 ​

    • Added achievement/milestone popups (thank you to Jacorb for this contribution!)
    • The changelog tab is back, and can be set in mod.js.
    • Layer nodes and respec buttons will not be clicked by pressing "enter".
    • Possible fix for flickering tooltips and strange transitions.
    • The victory screen text is configurable.
    • Added image and textStyle features to achievements.
    • Added an argument to use specific rows in an "upgrades" component.
    • Fixed the comma appearing in the main display when there was no effectDescription
    • Added the ability to easily make a tab that is a collection of layers in subtabs.
    • Improved spacing for embedding layers with subtabs into subtabs.

    v2.2.8 - 12/03/20 ​

    • Double-clicking a layer node brings you to the main subtab for that layer.
    • Attempted to fix challenges visually updating a different way.
    • Added a softcap function for use in formulas.
    • Added displayRow feature, which lets layers be shown somewhere separate from where they are in the reset order (e.g. side layers)
    • Fixed autoupgrade issue.

    v2.2.7 - 11/30/20 ​

    • Added autoUpgrade feature.
    • resource-display now shows resource gain per second if passiveGain is active.
    • Fixed formatting issues on some large numbers.
    • Better support for using classed objects in player and in layers/tmp.
    • Made hard resetting more effective.
    • Removed Herobrine from getStartClickables.

    v2.2.6 - 11/30/20 ​

    • Added goalDescription for challenges and made the new "canComplete" system the standard.
    • Another attempt to fix challenges not visually updating.
    • Fixed side layers not appearing.
    • Fixed getStartClickables again.

    v2.2.5 - 11/29/20 ​

    • Added features for overriding the displays and costs/goals of upgrades and challenges to make them fully custom.
    • best, total, and unlocked are always automatically added to layerData (but best and total will only display if you add them yourself).
    • Fixed getStartClickables.

    v2.2.4 - 11/28/20 ​

    • Added softcap and softcapPower features (for Normal layers)
    • Offline time limit and default max tick length were fixed (previously the limits were 1000x too large)
    • Added fixOldSaves.
    • You can use HTML in main-display.
    • Fixed a number of minor oddities.

    v2.2.3 - 11/28/20 ​

    • Layers will be highlighted if you can finish a challenge.
    • The "can complete challenge" color now overrides the "already completed" color.
    • Button nodes now work as side "layers".
    • Setting a tooltip to "" hides it entirely.

    v2.2.2 - 11/22/20 ​

    • Fixed right half of the screen being unclickable in some circumstances.
    • Fixed tree branches being offset.
    • Fix to lastSafeTab.

    v2.2.1 - 11/7/20 ​

    • Added a small highlight to layers you can meaningfully prestige on.
    • Added passiveGeneration and autoPrestige features to standardize prestige automation. (The old ways still work, but the new ones work better with other things)
    • Improved milestones visually a bit.
    • "best" and "total" are now only displayed if present in startData.
    • Fixed issues with things not updating visually. (Thank you to to Jacorb!)
    • Side layers and button nodes can now be highlighted.
    • Updated docs on the new tree-related features.

    v2.2: Uprooted - 11/7/20 ​

    • You can now embed a layer inside of a subtab or microtab!
    • Added support for hiding or reformatting the tree tab
    • Added non-layer button nodes
    • Added shouldNotify to subtab/microtab buttons. (You can make them highlighted)
    • Added commas to large exponents.
    • Upgrades now only show "currently" if they have an effectDisplay (so not for constant effects).
    • Achievements are part of the default tab format.
    • NaN is now handled more intelligently.
    • Renamed files, and moved less relevant ones to another folder.
    • The "hide completed challenges" setting now only hides challenges at max completions.
    • Thank you to thepaperpilot for fixing errors in docs and improving the infobox appearance!
    • Many other minor fixes.

    v2.1.4 - 10/25/20 ​

    • Added an infobox component. Thank you to thepaperpilot for this contribution!
    • Layer type is now optional, and defaults to "none".
    • Improved the look of bars and tab buttons.
    • Improved spacing between layer nodes (also thanks to thepaperpilot!)
    • Fixed the "blank" component breaking if only specifying the height.
    • Fixed some numbers not displaying with enough digits.
    • Made a few more things able to be functions.
    • A few other minor fixes.

    v2.1.3.1 - 10/21/20 ​

    • Fixed the update function.

    v2.1.3 - 10/21/20 ​

    • gainMult and gainExp are now optional.
    • Layer unlocking is now kept on reset.
    • Game should start up faster.
    • Layer updates now have a determined order and starts with earlier-rowed layers.
    • Automation now has a determined order and starts with later-rowed layers.
    • Fixed issues with resetting clickables and challenges.
    • Commas should no longer appear in the decimal places of a number.
    • Fixed potential issue in displaying the tree.

    v2.1.2 - 10/19/20 ​

    • Added buyUpgrade function (buyUpg still works though)
    • Added author name to modInfo.
    • Fix to crash caused when the name of a subtab or microtab is changed.
    • Fixes to outdated information in docs.
    • Improvements to Discord links.
    • Thank you to thepaperpilot for contributing to this update!

    v2.1.1 - 10/17/20 ​

    • Added resource-display component, which displays the base currency for the prestige layer, as well as the best and/or total of this layer's prestige currency.
    • Fixed the value for the base currency not updating in resource-display.

    v2.1: We should have thought of this sooner! - 10/17/20 ​

    • Moved most of the code users will want to edit to mod.js, added documentation for it.
      • Specifically, modInfo, VERSION, canGenPoints, getPointGen, and maxTickLength
    • Added getStartPoints()
    • Added the ability to store non-layer-related data
    • Added the ability to display more things at the top of the tree tab below points.
    • Made the endgame condition customizable
    • Added "sell one" and "sell all" buttons for buyables.
    • Moved the old "game" to demo.js, and replaced it with a minimal game that won't cause issues when edited.
    • Fixed issues with version number
    • Fixed number formatting issue making things like "10e9" appear.

    v2.0.5 - 10/16/20 ​

    • Made more features (including prestige parameters) able to be dynamic.
    • Layer nodes can be hidden but still take up space with "ghost" visibility
    • Added clickableEffect for real.
    • Fixed some visual issues with bars.
    • A few other minor tweaks and improvements.

    v2.0.4 - 10/16/20 ​

    • Fixed HTML on buttons interfering with clicking on them.

    v2.0.3 - 10/16/20 ​

    • Fixed hotkeys not displaying in info.
    • Fixed the game supressing all external hotkeys.
    • You can use more things as currencies for upgrade costs and challenge goals using currencyLocation.
    • Added maxTickLength, which can be used to prevent offline time or tab-switching from breaking time-limit based mechanics.
    • Made buyable respec buttons and clickable "master" buttons their own components, and gave them a hide/show feature.
    • Added a general "tooltip" feature for achievements.

    v2.0.2 - 10/15/20 ​

    • Branches are now dynamic (they can be functions).
    • Fixed a crash related to offline time.
    • Fixed links being too wide.

    v2.0.1 - 10/15/20 ​

    • Fixed side layers appearing multiple times.

    v2.0: The Pinnacle of Achievement Mountain - 10/15/20 ​

    • Added progress bars, which are highly customizable and can be horizontal or vertical!
    • Added "side layers", displayed smaller and off to the side, and don't get reset by default. They can be used for global achievements and statistics. Speaking of which...
    • Added achievements!
    • Added clickables, a more generalized variant of buyables.
    • Almost every value in layer data can be either a function or a constant value!
    • Added support for multiple completions of challenges.
    • Added "none" prestige type, which removes the need for any other prestige-related features.
    • The points display and other gui elements stay at the top of the screen when the tree scrolls.
    • Added getter/setter functions for the amounts and effects of most Big Features
    • Moved modInfo to game.js, added a spot in modInfo for a Discord link, changelog link. Also added a separate mod version from the TMT version in VERSION.
    • Tree structure is based on layer data, no index.html editing is needed.
    • Tmp does not need to be manually updated.
    • You don't have to have the same amount of upgrades in every row (and challs and buyables)
    • "unlocked" is optional for all Big Components (defaults to true).
    • All displays will update correctly.
    • Changelog is no longer in index.html at all.
    • Generation of Points now happens in the main game loop
    • Changed the reset functions to make keeping things easier
    • Renamed many things to increase readability (see the list in the link below)
    • Improved documentation based on feedback

    v1.3.5: ​

    • Completely automated convertToDecimal, now you never have to worry about it again.
    • Branches can be defined without a color id. But they can also use hex values for color ids!
    • Created a tutorial for getting started with TMT and Github.
    • Page title is now automatically taken from mod name.

    v1.3.4 - 10/8/20 ​

    • Added "midsection" feature to add things to a tab's layout while still keeping the standard layout.
    • Fix for being able to buy more buyables than you should.

    v1.3.3 - 10/7/20 ​

    • Fix for the "order of operations" issue in temp.

    v1.3.1 - 10/7/20 ​

    • Added custom CSS and tooltips for Layer Nodes.
    • Added custom CSS for upgrades, buyables, milestones, and challenges, both individually and layer-wide.
    • You can now use HTML in most display text!
    • You can now make milestones unlockable and not display immediately.
    • Fixed importing saves, and issue with upgrades not appearing, and probably more.
    • Optional "name" layer feature, used in confirmation messages.

    v1.3: Tabception... ception! - 10/7/20 ​

    • Added subtabs! And also a Micro-tab component to let you make smaller subtab-esque areas anywhere.
    • Added a "custom" prestige formula type, and a number of features to support it.
    • Added points/sec display (can be disabled).
    • Added h-line, v-line and image-display components, plus components for individual upgrades, challenges, and milestones.
    • Added upgEffect, buyableEffect, and challEffect functions.
    • Added "hide completed challenges" setting.
    • Moved old changelogs to a separate place.
    • Fixed hasMilestone and incr_order.
    • Static layers now show the currency amount needed for the next one if you can buy max.

    v1.2.4 - 10/4/20 ​

    • Layers are now highlighted if you can buy an upgrade, and a new feature, shouldNotify, lets you make it highlight other ways.
    • Fixed bugs with hasUpg, hasChall, hasMilestone, and inChallenge.
    • Changed the sample code to use the above functions for convenience.

    v1.2.3 - 10/3/20 ​

    • Added a row component, which displays a list of objects in a row.
    • Added a column component, which displays a list of objects in a column (useful within a row).
    • Changed blanks to have a customizable width and height.

    v1.2: This Changes Everything! - 10/3/20 ​

    • Many layer features can now be static values or functions. (This made some formats change, which will break old things)
    • You can now use the "this" keyword, to make code easier to transfer when making new layers.
    • Also added "this.layer", which is the current layer's name, and works on existing subfeatures (e.g. individual upgrades) as well! Subfeatures also have "this.id".
    • Fixed a big save issue. If you use a unique mod id, your save will never conflict with other mods.
    • Added a configurable offline time limit in modinfo at the top of index.html. (default 1 hour)
    • Added a few minor features, and updated the docs with new information.

    v1.1.1 - 9/30/20 ​

    • You can define hotkeys directly from layer config.

    v1.1: Enhanced Edition - 9/30/20 ​

    • Added "Buyables", which can function like Space Buildings or Enhancers.
    • Custom CSS can now be used on any component! Make the third argument an object with CSS parameters.
    • Lots of minor good things.

    v1.0 - 9/27/20 ​

    • First release.
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +
    The Paper Pilot

    Appearance

    The Modding Tree changelog: ​

    v2.5.9.2 - 5/19/21 ​

    • Fixed many issues with things not updating.

    v2.5.9.1 - 5/18/21 ​

    • Made text inputs never give NaNs.

    v2.5.9 - 5/18/21 ​

    • Fixed issue when using text inputs for Numbers.
    • Added particle color feature.
    • Particle speed and dir are updated as it moves.
    • Added setSpeed and setDir for particles.
    • Added more trig functions.

    v2.5.8 - 5/17/21 ​

    • Added makeShinies, which creates a stationary particle in a random spot.
    • Bars will visually update more quickly.
    • Fixed a major particle-related issue.
    • Fixed autoUpgrade.
    • Fixed a minor visual issue with tree nodes.

    v2.5.7 - 5/15/21 ​

    • Added a particle system! Not only can it be used for visual effects, but particles can interact with the mouse. They could be used to create golden cookies or collectables, for example.
    • Added marked feature to buyables, clickables, and challenges. By default, stars multi-completion challenges when maxed.
    • Added 'deactivated' feature to layers, which disables many features.
    • Improved number formatting slightly.

    v2.5.6 - 5/14/21 ​

    • You can now use non-numeric ids for upgrades, buyables, etc.
    • Fixed an exploit that let you buy an extra buyable.
    • Moved basic getter/setter functions to easyAccess.js.

    v2.5.5.2 - 5/12/21 ​

    • Fixed a major issue with buyables.
    • Fixed a variety of tabFormat-related issues.
    • Fixed commas appearing in decimal places (thanks to pg132!)

    v2.5.5.1 - 5/12/21 ​

    • Fixed clickables.

    v2.5.5 - 5/12/21 ​

    • Added grids! They are a grid of buttons which behave the same, but have their own data. Good for inventory grids, map tiles, and more!
    • Added "marked" feature to add a mark to a node. Can be an image instead of a star. (Originally by Jacorb)
    • Added "layer-proxy" component that lets you use components from another layer.
    • Added the ability to display non-whole numbers in main-display.

    v2.5.4 - 5/10/21 ​

    • Added a setting to always use single-tab mode.
    • Added directMult, which multiplies prestige gain after exponents and softcaps. It actually multiplies gain for static layers.
    • Added onEnter and onExit for challenges.
    • Improved displaying numbers between 0.0001 and 0.1.
    • Added documentation on how gainMult/Exp work for static layers.
    • Fixed a visual issue on mobile, thanks to thepaperpilot.
    • Improved documentation in general.

    v2.5.3 - 5/8/21 ​

    • Improved performance of tab formats and bars.
    • Respec confirmation settings are now kept on resets.
    • Improved compatibility with older browsers.
    • Fixed missing pixel on vertical bars.

    v2.5.2.1 - 5/7/21 ​

    • Fixed microtabs making layers highlight incorrectly.

    v2.5.2 - 5/7/21 ​

    • Added glowColor for subtabs.
    • Improved the display for extremely small numbers.
    • Fixed issues in the buyable docs.

    v2.5.1 - 5/7/21 ​

    • Fixed dynamic things in tabFormat not updating.

    v2.5: Dreams Really Do Come True - 5/7/21 ​

    • Optimizations, hopefully a significant amount.
    • Added OOM/s point gen display at high values (thanks to Ducdat!)
    • Only one tab will display if the window is not wide enough (also thanks to Ducdat!)
    • Holding down a buyable's button now buys it continuously.
    • New milestone setting will also show the most recently unlocked milestone. (Also renamed all settings to be clearer)
    • Added an onHold feature for clickables.
    • Layer nodes will be highlighted even if the player is on the same tab.
    • Added customizable node glowColor.
    • Added buyable purchaseLimit.
    • Amount is automatically supplied to buyable cost and effect functions.
    • Locked (not yet visible) milestones no longer take up space. Also fixed hidden milestones taking a tiny bit of space.
    • Re-centered respec buttons.
    • Force-displayed tooltips are not hidden by resets.
    • Added formatting support for very small numbers. Disabled in most places by default because rounding errors might cause issues. Access it with formatSmall, or enable it globally by adding "allowSmall: true" to modInfo.

    v2.4.1 - 4/29/21 ​

    • A number of minor fixes, many thanks to thepaperpilot.
    • The respec confirmation checkbox is now part of the respec-button component. (This also fixes the checkbox appearing when there is no respec button)
    • Added a few undocumented changes to the 2.4 changelog (the two at the bottom)

    v2.4: Rationalized Edition - 4/29/21 ​

    • Completely reworked tooltips. Shift-click a node to force its tooltip to stay displayed. (And hopefully finally fixed flickering!)

    • Added text-input and slider components.

    • Added the ability to toggle respec confirmations.

    • Added custom respec confirmation messages.

    • The red layer highlight will not appear before a layer is unlocked.

    • Added unlocking hotkeys.

    • You no longer need to supply 'rows' and 'cols' for any Big Features.

    • Node symbols can use HTML.

    • Added documentation for the respec button.

    • Added prestigeNotify to subtabs, and prestigeNotify in subtabs also highlights the layer node.

    • The version number no longer contains special characters or irrational numbers.

    • Added ctrlDown and shiftDown variables.

    • Tooltips now use HTML (this means you need to replace any newlines with
      )

    v2.π.1 - 4/7/21 ​

    • Fixed formatting for some larger numbers.
    • Upgrades will expand if there is too much text to display.
    • Fixed styling challenges.
    • No longer attempts to display a base currency when there is none.

    v2.π: Incrementally Updated - 2/5/21 ​

    • Performance improvements.
    • Fixed tooltips overlapping with the top display.
    • Clicking a popup dismisses it immediately.
    • Added support for bulk challenge completions.
    • "Best" is updated automatically.
    • Fixed keeping Decimal values on reset.
    • Code reorganization and style improvements by fudo.

    v2.3.5 - 12/21/20 ​

    • Added resetTime, which tracks the time since a layer prestiged or was reset.
    • A layer node will be highlighted red if one of its subtabs is highlighted red.
    • Fixed issues with keeping challenges, buyables, and clickables on reset.
    • Improved the unlocking of custom layers.
    • Other minor fixes.

    v2.3.4 - 12/16/20 ​

    • Added a node image feature.
    • Resource display now always shows the amount of the currency the layer's gain is based on.
    • Added spacing between tree nodes.
    • Another attempt to fix tooltip flickering.

    v2.3.3 - 12/13/20 ​

    • Fixed the first node in a row always taking up space.
    • layerShown is now optional.
    • All prestige types can now use features for custom prestige types.

    v2.3.2 - 12/13/20 ​

    • Fixed achievement/milestone popups.

    v2.3.1 - 12/12/20 ​

    • Another attempt to fix flickering tooltips.
    • The "this" keyword should work everywhere except tabFormat arrays (although I may have missed some things).
    • Fixed tree branches not updating when scrolling on the right-side tab.
    • Fixed a spacing issue when a node's symbol is ""
    • Removed some old, unneeded files.

    v2.3: Cooler and Newer Edition - 12/10/20 ​

    • Added achievement/milestone popups (thank you to Jacorb for this contribution!)
    • The changelog tab is back, and can be set in mod.js.
    • Layer nodes and respec buttons will not be clicked by pressing "enter".
    • Possible fix for flickering tooltips and strange transitions.
    • The victory screen text is configurable.
    • Added image and textStyle features to achievements.
    • Added an argument to use specific rows in an "upgrades" component.
    • Fixed the comma appearing in the main display when there was no effectDescription
    • Added the ability to easily make a tab that is a collection of layers in subtabs.
    • Improved spacing for embedding layers with subtabs into subtabs.

    v2.2.8 - 12/03/20 ​

    • Double-clicking a layer node brings you to the main subtab for that layer.
    • Attempted to fix challenges visually updating a different way.
    • Added a softcap function for use in formulas.
    • Added displayRow feature, which lets layers be shown somewhere separate from where they are in the reset order (e.g. side layers)
    • Fixed autoupgrade issue.

    v2.2.7 - 11/30/20 ​

    • Added autoUpgrade feature.
    • resource-display now shows resource gain per second if passiveGain is active.
    • Fixed formatting issues on some large numbers.
    • Better support for using classed objects in player and in layers/tmp.
    • Made hard resetting more effective.
    • Removed Herobrine from getStartClickables.

    v2.2.6 - 11/30/20 ​

    • Added goalDescription for challenges and made the new "canComplete" system the standard.
    • Another attempt to fix challenges not visually updating.
    • Fixed side layers not appearing.
    • Fixed getStartClickables again.

    v2.2.5 - 11/29/20 ​

    • Added features for overriding the displays and costs/goals of upgrades and challenges to make them fully custom.
    • best, total, and unlocked are always automatically added to layerData (but best and total will only display if you add them yourself).
    • Fixed getStartClickables.

    v2.2.4 - 11/28/20 ​

    • Added softcap and softcapPower features (for Normal layers)
    • Offline time limit and default max tick length were fixed (previously the limits were 1000x too large)
    • Added fixOldSaves.
    • You can use HTML in main-display.
    • Fixed a number of minor oddities.

    v2.2.3 - 11/28/20 ​

    • Layers will be highlighted if you can finish a challenge.
    • The "can complete challenge" color now overrides the "already completed" color.
    • Button nodes now work as side "layers".
    • Setting a tooltip to "" hides it entirely.

    v2.2.2 - 11/22/20 ​

    • Fixed right half of the screen being unclickable in some circumstances.
    • Fixed tree branches being offset.
    • Fix to lastSafeTab.

    v2.2.1 - 11/7/20 ​

    • Added a small highlight to layers you can meaningfully prestige on.
    • Added passiveGeneration and autoPrestige features to standardize prestige automation. (The old ways still work, but the new ones work better with other things)
    • Improved milestones visually a bit.
    • "best" and "total" are now only displayed if present in startData.
    • Fixed issues with things not updating visually. (Thank you to to Jacorb!)
    • Side layers and button nodes can now be highlighted.
    • Updated docs on the new tree-related features.

    v2.2: Uprooted - 11/7/20 ​

    • You can now embed a layer inside of a subtab or microtab!
    • Added support for hiding or reformatting the tree tab
    • Added non-layer button nodes
    • Added shouldNotify to subtab/microtab buttons. (You can make them highlighted)
    • Added commas to large exponents.
    • Upgrades now only show "currently" if they have an effectDisplay (so not for constant effects).
    • Achievements are part of the default tab format.
    • NaN is now handled more intelligently.
    • Renamed files, and moved less relevant ones to another folder.
    • The "hide completed challenges" setting now only hides challenges at max completions.
    • Thank you to thepaperpilot for fixing errors in docs and improving the infobox appearance!
    • Many other minor fixes.

    v2.1.4 - 10/25/20 ​

    • Added an infobox component. Thank you to thepaperpilot for this contribution!
    • Layer type is now optional, and defaults to "none".
    • Improved the look of bars and tab buttons.
    • Improved spacing between layer nodes (also thanks to thepaperpilot!)
    • Fixed the "blank" component breaking if only specifying the height.
    • Fixed some numbers not displaying with enough digits.
    • Made a few more things able to be functions.
    • A few other minor fixes.

    v2.1.3.1 - 10/21/20 ​

    • Fixed the update function.

    v2.1.3 - 10/21/20 ​

    • gainMult and gainExp are now optional.
    • Layer unlocking is now kept on reset.
    • Game should start up faster.
    • Layer updates now have a determined order and starts with earlier-rowed layers.
    • Automation now has a determined order and starts with later-rowed layers.
    • Fixed issues with resetting clickables and challenges.
    • Commas should no longer appear in the decimal places of a number.
    • Fixed potential issue in displaying the tree.

    v2.1.2 - 10/19/20 ​

    • Added buyUpgrade function (buyUpg still works though)
    • Added author name to modInfo.
    • Fix to crash caused when the name of a subtab or microtab is changed.
    • Fixes to outdated information in docs.
    • Improvements to Discord links.
    • Thank you to thepaperpilot for contributing to this update!

    v2.1.1 - 10/17/20 ​

    • Added resource-display component, which displays the base currency for the prestige layer, as well as the best and/or total of this layer's prestige currency.
    • Fixed the value for the base currency not updating in resource-display.

    v2.1: We should have thought of this sooner! - 10/17/20 ​

    • Moved most of the code users will want to edit to mod.js, added documentation for it.
      • Specifically, modInfo, VERSION, canGenPoints, getPointGen, and maxTickLength
    • Added getStartPoints()
    • Added the ability to store non-layer-related data
    • Added the ability to display more things at the top of the tree tab below points.
    • Made the endgame condition customizable
    • Added "sell one" and "sell all" buttons for buyables.
    • Moved the old "game" to demo.js, and replaced it with a minimal game that won't cause issues when edited.
    • Fixed issues with version number
    • Fixed number formatting issue making things like "10e9" appear.

    v2.0.5 - 10/16/20 ​

    • Made more features (including prestige parameters) able to be dynamic.
    • Layer nodes can be hidden but still take up space with "ghost" visibility
    • Added clickableEffect for real.
    • Fixed some visual issues with bars.
    • A few other minor tweaks and improvements.

    v2.0.4 - 10/16/20 ​

    • Fixed HTML on buttons interfering with clicking on them.

    v2.0.3 - 10/16/20 ​

    • Fixed hotkeys not displaying in info.
    • Fixed the game supressing all external hotkeys.
    • You can use more things as currencies for upgrade costs and challenge goals using currencyLocation.
    • Added maxTickLength, which can be used to prevent offline time or tab-switching from breaking time-limit based mechanics.
    • Made buyable respec buttons and clickable "master" buttons their own components, and gave them a hide/show feature.
    • Added a general "tooltip" feature for achievements.

    v2.0.2 - 10/15/20 ​

    • Branches are now dynamic (they can be functions).
    • Fixed a crash related to offline time.
    • Fixed links being too wide.

    v2.0.1 - 10/15/20 ​

    • Fixed side layers appearing multiple times.

    v2.0: The Pinnacle of Achievement Mountain - 10/15/20 ​

    • Added progress bars, which are highly customizable and can be horizontal or vertical!
    • Added "side layers", displayed smaller and off to the side, and don't get reset by default. They can be used for global achievements and statistics. Speaking of which...
    • Added achievements!
    • Added clickables, a more generalized variant of buyables.
    • Almost every value in layer data can be either a function or a constant value!
    • Added support for multiple completions of challenges.
    • Added "none" prestige type, which removes the need for any other prestige-related features.
    • The points display and other gui elements stay at the top of the screen when the tree scrolls.
    • Added getter/setter functions for the amounts and effects of most Big Features
    • Moved modInfo to game.js, added a spot in modInfo for a Discord link, changelog link. Also added a separate mod version from the TMT version in VERSION.
    • Tree structure is based on layer data, no index.html editing is needed.
    • Tmp does not need to be manually updated.
    • You don't have to have the same amount of upgrades in every row (and challs and buyables)
    • "unlocked" is optional for all Big Components (defaults to true).
    • All displays will update correctly.
    • Changelog is no longer in index.html at all.
    • Generation of Points now happens in the main game loop
    • Changed the reset functions to make keeping things easier
    • Renamed many things to increase readability (see the list in the link below)
    • Improved documentation based on feedback

    v1.3.5: ​

    • Completely automated convertToDecimal, now you never have to worry about it again.
    • Branches can be defined without a color id. But they can also use hex values for color ids!
    • Created a tutorial for getting started with TMT and Github.
    • Page title is now automatically taken from mod name.

    v1.3.4 - 10/8/20 ​

    • Added "midsection" feature to add things to a tab's layout while still keeping the standard layout.
    • Fix for being able to buy more buyables than you should.

    v1.3.3 - 10/7/20 ​

    • Fix for the "order of operations" issue in temp.

    v1.3.1 - 10/7/20 ​

    • Added custom CSS and tooltips for Layer Nodes.
    • Added custom CSS for upgrades, buyables, milestones, and challenges, both individually and layer-wide.
    • You can now use HTML in most display text!
    • You can now make milestones unlockable and not display immediately.
    • Fixed importing saves, and issue with upgrades not appearing, and probably more.
    • Optional "name" layer feature, used in confirmation messages.

    v1.3: Tabception... ception! - 10/7/20 ​

    • Added subtabs! And also a Micro-tab component to let you make smaller subtab-esque areas anywhere.
    • Added a "custom" prestige formula type, and a number of features to support it.
    • Added points/sec display (can be disabled).
    • Added h-line, v-line and image-display components, plus components for individual upgrades, challenges, and milestones.
    • Added upgEffect, buyableEffect, and challEffect functions.
    • Added "hide completed challenges" setting.
    • Moved old changelogs to a separate place.
    • Fixed hasMilestone and incr_order.
    • Static layers now show the currency amount needed for the next one if you can buy max.

    v1.2.4 - 10/4/20 ​

    • Layers are now highlighted if you can buy an upgrade, and a new feature, shouldNotify, lets you make it highlight other ways.
    • Fixed bugs with hasUpg, hasChall, hasMilestone, and inChallenge.
    • Changed the sample code to use the above functions for convenience.

    v1.2.3 - 10/3/20 ​

    • Added a row component, which displays a list of objects in a row.
    • Added a column component, which displays a list of objects in a column (useful within a row).
    • Changed blanks to have a customizable width and height.

    v1.2: This Changes Everything! - 10/3/20 ​

    • Many layer features can now be static values or functions. (This made some formats change, which will break old things)
    • You can now use the "this" keyword, to make code easier to transfer when making new layers.
    • Also added "this.layer", which is the current layer's name, and works on existing subfeatures (e.g. individual upgrades) as well! Subfeatures also have "this.id".
    • Fixed a big save issue. If you use a unique mod id, your save will never conflict with other mods.
    • Added a configurable offline time limit in modinfo at the top of index.html. (default 1 hour)
    • Added a few minor features, and updated the docs with new information.

    v1.1.1 - 9/30/20 ​

    • You can define hotkeys directly from layer config.

    v1.1: Enhanced Edition - 9/30/20 ​

    • Added "Buyables", which can function like Space Buildings or Enhancers.
    • Custom CSS can now be used on any component! Make the third argument an object with CSS parameters.
    • Lots of minor good things.

    v1.0 - 9/27/20 ​

    • First release.
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/!general-info.html b/public/kronos/docs/!general-info.html index a15c42d7..1a9a998d 100644 --- a/public/kronos/docs/!general-info.html +++ b/public/kronos/docs/!general-info.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
    The Paper Pilot

    Appearance

    The-Modding-Tree ​

    Making a game in The Modding Tree mostly involves defining parameters or functions on objects. If you aren't following the getting started guide, you should start by setting up your basic mod info in mod.js. It's important to set a mod id to ensure saving works properly.

    Beyond that, the main way to add content is through creating layers, often in layers.js. You can add new layers by calling addLayer(layername, layerdata). There is an example of a basic layer in layers.js showing the recommended method. It is just an example and can be freely deleted. You can also use it as a reference or a base for your own layers.

    Most of the time, you won't need to dive deep into the code to create things, but you still can if you really want to, for example to add new Vue components in components.js.

    The Modding Tree uses break_eternity.js to store large values. This means that many numbers are Decimal objects, and must be treated differently. For example, you have to use new Decimal(x) to create a Decimal value instead of a plain number, and perform operations on them by calling functions. e.g, instead of x = x + y, use x = x.add(y). Keep in mind this also applies to comparison operators, which should be replaced with calling the .gt, .gte, .lt, .lte, .eq, and .neq functions. See the break_eternity.js docs for more details on working with Decimal values.

    Almost all values can be either a constant value, or a dynamic value. Dynamic values are defined by putting a function that returns what the value should be at any given time.

    All display text can use basic HTML elements (But you can't use most Vue features there).

    While reading this documentation, the following key will be used when describing features:

    • No label: This is required and the game may crash if it isn't included.
    • sometimes required: This is may be required, depending on other things in the layer.
    • optional: You can leave this out if you don't intend to use that feature for the layer.
    • assigned automagically: This value will be set automatically and override any value you set.
    • deprecated: This feature is not recommended to be used, because newer features are able to achieve the same thing in a better, easier way.

    Table of Contents ​

    General ​

    • Getting Started: Getting your own copy of the code set up with Github Desktop.
    • Main mod info: How to set up general things for your mod in mod.js.
    • Basic layer breakdown: Breaking down the components of a layer with minimal features.
    • Layer features: Explanations of all of the different properties that you can give a layer.
    • Custom Tab Layouts: An optional way to give your tabs a different layout. You can even create entirely new components to use.
    • Custom game layouts: You can get rid of the tree tab, add buttons and other things to the tree, or even customize the tab's layout like a layer tab.
    • Updating TMT: Using Github Desktop to update your mod's version of TMT.

    Common components ​

    • Upgrades: How to create upgrades for a layer.
    • Milestones: How to create milestones for a layer.
    • Buyables: Create rebuyable upgrades for your layer (with the option to make them respec-able). Can be used to make Enhancers or Space Buildings, for example.
    • Clickables: A more generalized variant of buyables, for any kind of thing that is sometimes clickable. Between these and Buyables, you can do just about anything.
    • Achievements: How to create achievements for a layer (or for the whole game).

    Other components and features ​

    • Challenges: How to create challenges for a layer.
    • Bars: Display some information as a progress bar, gauge, or similar. They are highly customizable, and can be horizontal and vertical as well.
    • Subtabs and Microtabs: Create subtabs for your tabs, as well as "microtab" components that you can put inside the tabs. You can even use them to embed a layer inside another layer!
    • [Grids][grids.md]: Create a group buttons that behave the same, but have their own data. Good for map tiles, an inventory grid, and more!
    • Infoboxes: Boxes containing text that can be shown or hidden.
    • Trees: Make your own trees. You can make non-layer button nodes too!
    • Particle system: Can be used to create particles for visual effects, but also interactable things like golden cookies or collectables.
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +
    The Paper Pilot

    Appearance

    The-Modding-Tree ​

    Making a game in The Modding Tree mostly involves defining parameters or functions on objects. If you aren't following the getting started guide, you should start by setting up your basic mod info in mod.js. It's important to set a mod id to ensure saving works properly.

    Beyond that, the main way to add content is through creating layers, often in layers.js. You can add new layers by calling addLayer(layername, layerdata). There is an example of a basic layer in layers.js showing the recommended method. It is just an example and can be freely deleted. You can also use it as a reference or a base for your own layers.

    Most of the time, you won't need to dive deep into the code to create things, but you still can if you really want to, for example to add new Vue components in components.js.

    The Modding Tree uses break_eternity.js to store large values. This means that many numbers are Decimal objects, and must be treated differently. For example, you have to use new Decimal(x) to create a Decimal value instead of a plain number, and perform operations on them by calling functions. e.g, instead of x = x + y, use x = x.add(y). Keep in mind this also applies to comparison operators, which should be replaced with calling the .gt, .gte, .lt, .lte, .eq, and .neq functions. See the break_eternity.js docs for more details on working with Decimal values.

    Almost all values can be either a constant value, or a dynamic value. Dynamic values are defined by putting a function that returns what the value should be at any given time.

    All display text can use basic HTML elements (But you can't use most Vue features there).

    While reading this documentation, the following key will be used when describing features:

    • No label: This is required and the game may crash if it isn't included.
    • sometimes required: This is may be required, depending on other things in the layer.
    • optional: You can leave this out if you don't intend to use that feature for the layer.
    • assigned automagically: This value will be set automatically and override any value you set.
    • deprecated: This feature is not recommended to be used, because newer features are able to achieve the same thing in a better, easier way.

    Table of Contents ​

    General ​

    • Getting Started: Getting your own copy of the code set up with Github Desktop.
    • Main mod info: How to set up general things for your mod in mod.js.
    • Basic layer breakdown: Breaking down the components of a layer with minimal features.
    • Layer features: Explanations of all of the different properties that you can give a layer.
    • Custom Tab Layouts: An optional way to give your tabs a different layout. You can even create entirely new components to use.
    • Custom game layouts: You can get rid of the tree tab, add buttons and other things to the tree, or even customize the tab's layout like a layer tab.
    • Updating TMT: Using Github Desktop to update your mod's version of TMT.

    Common components ​

    • Upgrades: How to create upgrades for a layer.
    • Milestones: How to create milestones for a layer.
    • Buyables: Create rebuyable upgrades for your layer (with the option to make them respec-able). Can be used to make Enhancers or Space Buildings, for example.
    • Clickables: A more generalized variant of buyables, for any kind of thing that is sometimes clickable. Between these and Buyables, you can do just about anything.
    • Achievements: How to create achievements for a layer (or for the whole game).

    Other components and features ​

    • Challenges: How to create challenges for a layer.
    • Bars: Display some information as a progress bar, gauge, or similar. They are highly customizable, and can be horizontal and vertical as well.
    • Subtabs and Microtabs: Create subtabs for your tabs, as well as "microtab" components that you can put inside the tabs. You can even use them to embed a layer inside another layer!
    • [Grids][grids.md]: Create a group buttons that behave the same, but have their own data. Good for map tiles, an inventory grid, and more!
    • Infoboxes: Boxes containing text that can be shown or hidden.
    • Trees: Make your own trees. You can make non-layer button nodes too!
    • Particle system: Can be used to create particles for visual effects, but also interactable things like golden cookies or collectables.
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/achievements.html b/public/kronos/docs/achievements.html index fd9a1a59..297df997 100644 --- a/public/kronos/docs/achievements.html +++ b/public/kronos/docs/achievements.html @@ -8,11 +8,7 @@ - - - - - + @@ -31,8 +27,8 @@ more features }, etc -}

    Usually, each achievement should have an id where the first digit is the row and the second digit is the column.

    Individual achievement can have these features:

    • name: optional. displayed at the top of the achievement. The only visible text. It can also be a function that returns updating text. Can use basic HTML.

    • done(): A function returning a boolean to determine if the achievement should be awarded.

    • tooltip: Default tooltip for the achievement, appears when it is hovered over. Should convey the goal and any reward for completing the achievement. It can also be a function that returns updating text. Can use basic HTML. Setting this to "" disables the tooltip.

    • effect(): optional. A function that calculates and returns the current values of any bonuses from the achievement. Can return a value or an object containing multiple values.

    • unlocked(): optional. A function returning a bool to determine if the achievement is visible or not. Default is unlocked.

    • onComplete() - optional. this function will be called when the achievement is completed.

    • image: optional, puts the image from the given URL (relative or absolute) in the achievement

    • style: optional. Applies CSS to this achievement, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • textStyle: optional. Applies CSS to the text, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the achievement was stored under, for convenient access. The achievement in the example's id is 11.

    • goalTooltip: optional, deprecated. Appears when the achievement is hovered over and locked, overrides the basic tooltip. This is to display the goal (or a hint). It can also be a function that returns updating text. Can use basic HTML.

    • doneTooltip: optional, deprecated. Appears when the achievement is hovered over and completed, overrides the basic tooltip. This can display what the player achieved (the goal), and the rewards, if any. It can also be a function that returns updating text. Can use basic HTML.

    Disable achievement popups by adding achievementsPopups: false to the layer.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Usually, each achievement should have an id where the first digit is the row and the second digit is the column.

    Individual achievement can have these features:

    • name: optional. displayed at the top of the achievement. The only visible text. It can also be a function that returns updating text. Can use basic HTML.

    • done(): A function returning a boolean to determine if the achievement should be awarded.

    • tooltip: Default tooltip for the achievement, appears when it is hovered over. Should convey the goal and any reward for completing the achievement. It can also be a function that returns updating text. Can use basic HTML. Setting this to "" disables the tooltip.

    • effect(): optional. A function that calculates and returns the current values of any bonuses from the achievement. Can return a value or an object containing multiple values.

    • unlocked(): optional. A function returning a bool to determine if the achievement is visible or not. Default is unlocked.

    • onComplete() - optional. this function will be called when the achievement is completed.

    • image: optional, puts the image from the given URL (relative or absolute) in the achievement

    • style: optional. Applies CSS to this achievement, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • textStyle: optional. Applies CSS to the text, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the achievement was stored under, for convenient access. The achievement in the example's id is 11.

    • goalTooltip: optional, deprecated. Appears when the achievement is hovered over and locked, overrides the basic tooltip. This is to display the goal (or a hint). It can also be a function that returns updating text. Can use basic HTML.

    • doneTooltip: optional, deprecated. Appears when the achievement is hovered over and completed, overrides the basic tooltip. This can display what the player achieved (the goal), and the rewards, if any. It can also be a function that returns updating text. Can use basic HTML.

    Disable achievement popups by adding achievementsPopups: false to the layer.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/bars.html b/public/kronos/docs/bars.html index aa2f506f..b0aa55ea 100644 --- a/public/kronos/docs/bars.html +++ b/public/kronos/docs/bars.html @@ -8,11 +8,7 @@ - - - - - + @@ -34,8 +30,8 @@ etc }, etc -}

    Features:

    • direction: UP, DOWN, LEFT, or RIGHT (not strings). Determines the direction that the bar is filled as it progresses. RIGHT means from left to right.

    • width, height: The size in pixels of the bar, but as numbers (no "px" at the end).

    • progress(): A function that returns the portion of the bar that is filled, from "empty" at 0 to "full" at 1, updating automatically. (Nothing bad happens if the value goes out of these bounds, and it can be a number or Decimal)

    • display(): optional. A function that returns text to be displayed on top of the bar, can use HTML.

    • unlocked(): optional. A function returning a bool to determine if the bar is visible or not. Default is unlocked.

    • baseStyle, fillStyle, borderStyle, textStyle: Optional, Apply CSS to the unfilled portion, filled portion, border, and display text on the bar, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the bar was stored under, for convenient access. The bar in the example's id is "bigBar".

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Features:

    • direction: UP, DOWN, LEFT, or RIGHT (not strings). Determines the direction that the bar is filled as it progresses. RIGHT means from left to right.

    • width, height: The size in pixels of the bar, but as numbers (no "px" at the end).

    • progress(): A function that returns the portion of the bar that is filled, from "empty" at 0 to "full" at 1, updating automatically. (Nothing bad happens if the value goes out of these bounds, and it can be a number or Decimal)

    • display(): optional. A function that returns text to be displayed on top of the bar, can use HTML.

    • unlocked(): optional. A function returning a bool to determine if the bar is visible or not. Default is unlocked.

    • baseStyle, fillStyle, borderStyle, textStyle: Optional, Apply CSS to the unfilled portion, filled portion, border, and display text on the bar, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the bar was stored under, for convenient access. The bar in the example's id is "bigBar".

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/basic-layer-breakdown.html b/public/kronos/docs/basic-layer-breakdown.html index 662b2875..46f239c2 100644 --- a/public/kronos/docs/basic-layer-breakdown.html +++ b/public/kronos/docs/basic-layer-breakdown.html @@ -8,11 +8,7 @@ - - - - - + @@ -56,8 +52,8 @@ upgrades: { // Look in the upgrades docs to see what goes here! }, -})
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +})
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/buyables.html b/public/kronos/docs/buyables.html index b44e1a3c..486774fb 100644 --- a/public/kronos/docs/buyables.html +++ b/public/kronos/docs/buyables.html @@ -8,11 +8,7 @@ - - - - - + @@ -37,8 +33,8 @@ etc }, etc -}

    Features:

    • title: optional. displayed at the top in a larger font. It can also be a function that returns updating text.

    • cost(): cost for buying the next buyable. Can have an optional argument "x" to calculate the cost of the x+1th purchase. (x is a Decimal). Can return an object if there are multiple currencies.

    • effect(): optional. A function that calculates and returns the current values of bonuses of this buyable. Can have an optional argument "x" to calculate the effect of having x of the buyable.. Can return a value or an object containing multiple values.

    • display(): A function returning everything that should be displayed on the buyable after the title, likely including the description, amount bought, cost, and current effect. Can use basic HTML.

    • unlocked(): optional. A function returning a bool to determine if the buyable is visible or not. Default is unlocked.

    • canAfford(): A function returning a bool to determine if you can buy one of the buyables.

    • buy(): A function that implements buying one of the buyable, including spending the currency.

    • buyMax(): optional. A function that implements buying as many of the buyable as possible.

    • style: optional. Applies CSS to this buyable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • purchaseLimit: optional. The limit on how many of the buyable can be bought. The default is no limit.

    • marked: optional Adds a mark to the corner of the buyable. If it's "true" it will be a star, but it can also be an image URL.

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the buyable was stored under, for convenient access. The buyable in the example's id is 11.

    Sell One/Sell All:

    Including a sellOne or sellAll function will cause an additional button to appear beneath the buyable. They are functionally identical, but "sell one" appears above "sell all". You can also use them for other things.

    • sellOne/sellAll(): optional. Called when the button is pressed. The standard use would be to decrease/reset the amount of the buyable, and possibly return some currency to the player.

    • canSellOne/canSellAll(): optional. booleans determining whether or not to show the buttons. If "canSellOne/All" is absent but "sellOne/All" is present, the appropriate button will always show.

    To add a respec button, or something similar, add the respecBuyables function to the main buyables object (not individual buyables). You can use these features along with it:

    • respec(): optional. This is called when the button is pressed (after a toggleable confirmation message).

    • respecText: optional. Text to display on the respec Button.

    • showRespec(): optional. A function determining whether or not to show the button, if respecBuyables is defined. Defaults to true if absent.

    • respecMessage: optional. A custom confirmation message on respec, in place of the default one.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Features:

    • title: optional. displayed at the top in a larger font. It can also be a function that returns updating text.

    • cost(): cost for buying the next buyable. Can have an optional argument "x" to calculate the cost of the x+1th purchase. (x is a Decimal). Can return an object if there are multiple currencies.

    • effect(): optional. A function that calculates and returns the current values of bonuses of this buyable. Can have an optional argument "x" to calculate the effect of having x of the buyable.. Can return a value or an object containing multiple values.

    • display(): A function returning everything that should be displayed on the buyable after the title, likely including the description, amount bought, cost, and current effect. Can use basic HTML.

    • unlocked(): optional. A function returning a bool to determine if the buyable is visible or not. Default is unlocked.

    • canAfford(): A function returning a bool to determine if you can buy one of the buyables.

    • buy(): A function that implements buying one of the buyable, including spending the currency.

    • buyMax(): optional. A function that implements buying as many of the buyable as possible.

    • style: optional. Applies CSS to this buyable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • purchaseLimit: optional. The limit on how many of the buyable can be bought. The default is no limit.

    • marked: optional Adds a mark to the corner of the buyable. If it's "true" it will be a star, but it can also be an image URL.

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the buyable was stored under, for convenient access. The buyable in the example's id is 11.

    Sell One/Sell All:

    Including a sellOne or sellAll function will cause an additional button to appear beneath the buyable. They are functionally identical, but "sell one" appears above "sell all". You can also use them for other things.

    • sellOne/sellAll(): optional. Called when the button is pressed. The standard use would be to decrease/reset the amount of the buyable, and possibly return some currency to the player.

    • canSellOne/canSellAll(): optional. booleans determining whether or not to show the buttons. If "canSellOne/All" is absent but "sellOne/All" is present, the appropriate button will always show.

    To add a respec button, or something similar, add the respecBuyables function to the main buyables object (not individual buyables). You can use these features along with it:

    • respec(): optional. This is called when the button is pressed (after a toggleable confirmation message).

    • respecText: optional. Text to display on the respec Button.

    • showRespec(): optional. A function determining whether or not to show the button, if respecBuyables is defined. Defaults to true if absent.

    • respecMessage: optional. A custom confirmation message on respec, in place of the default one.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/challenges.html b/public/kronos/docs/challenges.html index 69ae4afe..adffc2b1 100644 --- a/public/kronos/docs/challenges.html +++ b/public/kronos/docs/challenges.html @@ -8,11 +8,7 @@ - - - - - + @@ -33,8 +29,8 @@ etc }, etc -}

    Usually, each challenge should have an id where the first digit is the row and the second digit is the column.

    Individual Challenges can have these features:

    • name: Name of the challenge, can be a string or a function. Can use basic HTML.

    • challengeDescription: A description of what makes the challenge a challenge. You will need to implement these elsewhere. It can also be a function that returns updating text. Can use basic HTML.

    • goalDescription: A description of the win condition for the challenge. It can also be a function that returns updating text. Can use basic HTML. (Optional if using the old goal system)

    • canComplete(): A function that returns true if you meet the win condition for the challenge. Returning a number will allow bulk completing the challenge. (Optional if using the old goal system)

    • rewardDescription: A description of the reward's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

    • rewardEffect(): optional. A function that calculates and returns the current values of any bonuses from the reward. Can return a value or an object containing multiple values. Can use basic HTML.

    • rewardDisplay(): optional. A function that returns a display of the current effects of the reward with formatting. Default behavior is to just display the a number appropriately formatted.

    • fullDisplay(): OVERRIDE. Overrides the other displays and descriptions, and lets you set the full text for the challenge. Can use basic HTML.

    • unlocked(): optional. A function returning a bool to determine if the challenge is visible or not. Default is unlocked.

    • onComplete() - optional. this function will be called when the challenge is completed when previously incomplete.

    • onEnter() - optional. this function will be called when entering the challenge

    • onExit() - optional. this function will be called when exiting the challenge in any way

    • countsAs: optional. If a challenge combines the effects of other challenges in this layer, you can use this. An array of challenge ids. The player is effectively in all of those challenges when in the current one.

    • completionLimit: optional. the amount of times you can complete this challenge. Default is 1 completion.

    • style: optional. Applies CSS to this challenge, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • marked: optional Adds a mark to the corner of the challenge. If it's "true" it will be a star, but it can also be an image URL. By default, if the challenge has multiple completions, it will be starred at max completions.

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

    • id: assigned automagically. It's the "key" which the challenge was stored under, for convenient access. The challenge in the example's id is 11.

    The old goal system uses these features:

    • goal: deprecated, A Decimal for the amount of currency required to beat the challenge. By default, the goal is in basic Points. The goal can also be a function if its value changes.

    • currencyDisplayName: deprecated. the name to display for the currency for the goal

    • currencyInternalName: deprecated. the internal name for that currency

    • currencyLayer: deprecated. the internal name of the layer that currency is stored in. If it's not in a layer, omit. If it's not stored directly in a layer, instead use the next feature.

    • currencyLocation(): deprecated. if your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Usually, each challenge should have an id where the first digit is the row and the second digit is the column.

    Individual Challenges can have these features:

    • name: Name of the challenge, can be a string or a function. Can use basic HTML.

    • challengeDescription: A description of what makes the challenge a challenge. You will need to implement these elsewhere. It can also be a function that returns updating text. Can use basic HTML.

    • goalDescription: A description of the win condition for the challenge. It can also be a function that returns updating text. Can use basic HTML. (Optional if using the old goal system)

    • canComplete(): A function that returns true if you meet the win condition for the challenge. Returning a number will allow bulk completing the challenge. (Optional if using the old goal system)

    • rewardDescription: A description of the reward's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

    • rewardEffect(): optional. A function that calculates and returns the current values of any bonuses from the reward. Can return a value or an object containing multiple values. Can use basic HTML.

    • rewardDisplay(): optional. A function that returns a display of the current effects of the reward with formatting. Default behavior is to just display the a number appropriately formatted.

    • fullDisplay(): OVERRIDE. Overrides the other displays and descriptions, and lets you set the full text for the challenge. Can use basic HTML.

    • unlocked(): optional. A function returning a bool to determine if the challenge is visible or not. Default is unlocked.

    • onComplete() - optional. this function will be called when the challenge is completed when previously incomplete.

    • onEnter() - optional. this function will be called when entering the challenge

    • onExit() - optional. this function will be called when exiting the challenge in any way

    • countsAs: optional. If a challenge combines the effects of other challenges in this layer, you can use this. An array of challenge ids. The player is effectively in all of those challenges when in the current one.

    • completionLimit: optional. the amount of times you can complete this challenge. Default is 1 completion.

    • style: optional. Applies CSS to this challenge, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • marked: optional Adds a mark to the corner of the challenge. If it's "true" it will be a star, but it can also be an image URL. By default, if the challenge has multiple completions, it will be starred at max completions.

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

    • id: assigned automagically. It's the "key" which the challenge was stored under, for convenient access. The challenge in the example's id is 11.

    The old goal system uses these features:

    • goal: deprecated, A Decimal for the amount of currency required to beat the challenge. By default, the goal is in basic Points. The goal can also be a function if its value changes.

    • currencyDisplayName: deprecated. the name to display for the currency for the goal

    • currencyInternalName: deprecated. the internal name for that currency

    • currencyLayer: deprecated. the internal name of the layer that currency is stored in. If it's not in a layer, omit. If it's not stored directly in a layer, instead use the next feature.

    • currencyLocation(): deprecated. if your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/clickables.html b/public/kronos/docs/clickables.html index 1a8417b4..182029d4 100644 --- a/public/kronos/docs/clickables.html +++ b/public/kronos/docs/clickables.html @@ -8,11 +8,7 @@ - - - - - + @@ -31,8 +27,8 @@ etc } etc -}

    Features:

    • title: optional. displayed at the top in a larger font. It can also be a function that returns updating text.

    • effect(): optional. A function that calculates and returns the current values of bonuses of this clickable. Can return a value or an object containing multiple values.

    • display(): A function returning everything that should be displayed on the clickable after the title, likely changing based on its state. Can use basic HTML.

    • unlocked(): optional. A function returning a bool to determine if the clickable is visible or not. Default is unlocked.

    • canClick(): A function returning a bool to determine if you can click the clickable.

    • onClick(): A function that implements clicking the clickable.

    • onHold(): optional A function that is called 20x/sec when the button is held for at least 0.25 seconds.

    • style: optional. Applies CSS to this clickable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • marked: optional Adds a mark to the corner of the clickable. If it's "true" it will be a star, but it can also be an image URL.

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the clickable was stored under, for convenient access. The clickable in the example's id is 11.

    You can also use these features on the clickables object to add a button above all the clickables, for implementing a respec button or similar.

    • masterButtonPress(): optional. If present, an additional button will appear above the clickables. Pressing it will call this function.

    • masterButtonText: optional. Text to display on the Master Button.

    • showMasterButton(): optional. A function determining whether or not to show the button, if masterButtonPress is defined. Defaults to true if absent.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Features:

    • title: optional. displayed at the top in a larger font. It can also be a function that returns updating text.

    • effect(): optional. A function that calculates and returns the current values of bonuses of this clickable. Can return a value or an object containing multiple values.

    • display(): A function returning everything that should be displayed on the clickable after the title, likely changing based on its state. Can use basic HTML.

    • unlocked(): optional. A function returning a bool to determine if the clickable is visible or not. Default is unlocked.

    • canClick(): A function returning a bool to determine if you can click the clickable.

    • onClick(): A function that implements clicking the clickable.

    • onHold(): optional A function that is called 20x/sec when the button is held for at least 0.25 seconds.

    • style: optional. Applies CSS to this clickable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • marked: optional Adds a mark to the corner of the clickable. If it's "true" it will be a star, but it can also be an image URL.

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the clickable was stored under, for convenient access. The clickable in the example's id is 11.

    You can also use these features on the clickables object to add a button above all the clickables, for implementing a respec button or similar.

    • masterButtonPress(): optional. If present, an additional button will appear above the clickables. Pressing it will call this function.

    • masterButtonText: optional. Text to display on the Master Button.

    • showMasterButton(): optional. A function determining whether or not to show the button, if masterButtonPress is defined. Defaults to true if absent.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/custom-tab-layouts.html b/public/kronos/docs/custom-tab-layouts.html index 23d0b86e..5b76be53 100644 --- a/public/kronos/docs/custom-tab-layouts.html +++ b/public/kronos/docs/custom-tab-layouts.html @@ -8,11 +8,7 @@ - - - - - + @@ -38,8 +34,8 @@ "blank", "blank", "upgrades" -]

    It is a list of components, which can be either just a name, or an array with arguments. If it's an array, the first item is the name of the component, the second is the data passed into it, and the third (optional) applies a CSS style to it with a "CSS object", where the keys are CSS attributes.

    These are the existing components, but you can create more in components.js:

    • display-text: Displays some text (can use basic HTML). The argument is the text to display. It can also be a function that returns updating text.

    • raw-html: Displays some basic HTML, can also be a function.

    • blank: Adds empty space. The default dimensions are 8px x 17px. The argument changes the dimensions. If it's a single value (e.g. "20px"), that determines the height. If you have a pair of arguments, the first is width and the second is height.

    • row: Display a list of components horizontally. The argument is an array of components in the tab layout format.

    • column: Display a list of components vertically. The argument is an array of components in the tab layout format. This is useful to display columns within a row.

    • main-display: The text that displays the main currency for the layer and its effects. The argument is the amount of precision to use, allowing it to display non-whole numbers.

    • resource-display: The text that displays the currency that this layer is based on, as well as the best and/or total values for this layer's prestige currency (if they are put in startData for this layer).

    • prestige-button: The argument is a string that the prestige button should say before the amount of currency you will gain. It can also be a function that returns updating text.

    • text-input: A text input box. The argument is the name of the variable in player[layer] that the input is for, player[layer][argument] (Works with strings, numbers, and Decimals!)

    • slider: Lets the user input a value with a slider. The argument a 3-element array: [name, min, max]. The name is the name of the variable in player[layer] that the input that the input is for, and min and max are the limits of the slider. (Does not work for Decimal values)

    • upgrades: The layer's upgrades. The argument is optional, and is a the list of rows this component should include, if it doesn't have all of them.

    • milestones, challenges, achievements: Display the upgrades, milestones, and challenges for a layer, as appropriate.

    • buyables, clickables: Display all of the buyables/clickables for this layer, as appropriate. The argument is optional and is the size of the boxes in pixels.

    • microtabs: Display a set of subtabs for an area. The argument is the name of the set of microtabs in the "microtabs" feature.

    • bar: Display a bar. The argument is the id of the bar to display.

    • infobox: Display an infobox. The argument is the id of the infobox to display.

    • tree: Displays a tree. The argument is an array of arrays containing the names of the nodes in the tree (first by row, then by column) See here for more information on tree layouts and nodes!

    • toggle: A toggle button that toggles a bool value. The argument is a pair that identifies the location in player of the bool to toggle, e.g. [layer, id]. 'layer' also affects the color of the toggle.

    • grid: Displays the gridable grid for the layer. If you need more than one grid, use a layer proxy.

    • layer-proxy: Lets you use components from another layer. The argument is a pair, [layer, data], consisting of the id of the layer to proxy from, and the tabFormat for the components to show. (Note: you cannot use a microtab within a layer proxy)

    The rest of the components are sub-components. They can be used just like other components, but are typically part of another component.

    • upgrade, milestone, challenge, buyable, clickable, achievement, gridable: An individual upgrade, challenge, etc. The argument is the id. This can be used if you want to have upgrades split up across multiple subtabs, for example.

    • respec-button, master-button: The respec and master buttons for buyables and clickables, respectively.

    • sell-one, sell-all: The "sell one" and "sell all" for buyables, respectively. The argument is the id of the buyable.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +]

    It is a list of components, which can be either just a name, or an array with arguments. If it's an array, the first item is the name of the component, the second is the data passed into it, and the third (optional) applies a CSS style to it with a "CSS object", where the keys are CSS attributes.

    These are the existing components, but you can create more in components.js:

    • display-text: Displays some text (can use basic HTML). The argument is the text to display. It can also be a function that returns updating text.

    • raw-html: Displays some basic HTML, can also be a function.

    • blank: Adds empty space. The default dimensions are 8px x 17px. The argument changes the dimensions. If it's a single value (e.g. "20px"), that determines the height. If you have a pair of arguments, the first is width and the second is height.

    • row: Display a list of components horizontally. The argument is an array of components in the tab layout format.

    • column: Display a list of components vertically. The argument is an array of components in the tab layout format. This is useful to display columns within a row.

    • main-display: The text that displays the main currency for the layer and its effects. The argument is the amount of precision to use, allowing it to display non-whole numbers.

    • resource-display: The text that displays the currency that this layer is based on, as well as the best and/or total values for this layer's prestige currency (if they are put in startData for this layer).

    • prestige-button: The argument is a string that the prestige button should say before the amount of currency you will gain. It can also be a function that returns updating text.

    • text-input: A text input box. The argument is the name of the variable in player[layer] that the input is for, player[layer][argument] (Works with strings, numbers, and Decimals!)

    • slider: Lets the user input a value with a slider. The argument a 3-element array: [name, min, max]. The name is the name of the variable in player[layer] that the input that the input is for, and min and max are the limits of the slider. (Does not work for Decimal values)

    • upgrades: The layer's upgrades. The argument is optional, and is a the list of rows this component should include, if it doesn't have all of them.

    • milestones, challenges, achievements: Display the upgrades, milestones, and challenges for a layer, as appropriate.

    • buyables, clickables: Display all of the buyables/clickables for this layer, as appropriate. The argument is optional and is the size of the boxes in pixels.

    • microtabs: Display a set of subtabs for an area. The argument is the name of the set of microtabs in the "microtabs" feature.

    • bar: Display a bar. The argument is the id of the bar to display.

    • infobox: Display an infobox. The argument is the id of the infobox to display.

    • tree: Displays a tree. The argument is an array of arrays containing the names of the nodes in the tree (first by row, then by column) See here for more information on tree layouts and nodes!

    • toggle: A toggle button that toggles a bool value. The argument is a pair that identifies the location in player of the bool to toggle, e.g. [layer, id]. 'layer' also affects the color of the toggle.

    • grid: Displays the gridable grid for the layer. If you need more than one grid, use a layer proxy.

    • layer-proxy: Lets you use components from another layer. The argument is a pair, [layer, data], consisting of the id of the layer to proxy from, and the tabFormat for the components to show. (Note: you cannot use a microtab within a layer proxy)

    The rest of the components are sub-components. They can be used just like other components, but are typically part of another component.

    • upgrade, milestone, challenge, buyable, clickable, achievement, gridable: An individual upgrade, challenge, etc. The argument is the id. This can be used if you want to have upgrades split up across multiple subtabs, for example.

    • respec-button, master-button: The respec and master buttons for buyables and clickables, respectively.

    • sell-one, sell-all: The "sell one" and "sell all" for buyables, respectively. The argument is the id of the buyable.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/getting-started.html b/public/kronos/docs/getting-started.html index 0fbc1099..334b67f7 100644 --- a/public/kronos/docs/getting-started.html +++ b/public/kronos/docs/getting-started.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
    The Paper Pilot

    Appearance

    Getting started ​

    Welcome to The Modding Tree!

    Using the Modding Tree, at its simplest level, just requires getting a copy of it onto your computer. However, if you do it the right way, it will help in many ways.

    Don't let the word "Github" scare you away. It's actually much easier to use than most people think, especially because most people use it the hard way. The key is Github Desktop, which lets you do everything you need to, without even touching the command line.

    The benefits of using Github:

    • It makes it much, much easier to update The Modding Tree.
    • You can share your work without any extra effort using githack, or with a bit more effort, set up a github.io site.
    • It lets you undo changes to your code, and to have multiple versions of it.
    • It lets you collaborate with other people, if you want to.

    Getting set up with Github Desktop, Visual Studio Code, and The Modding Tree: ​

    1. Install Github Desktop and Visual Studio Code.

    2. Make a Github account. You can handle this on your own.

    3. Log in on your browser, and go back to The Modding Tree page. At the top right, there should be a button that says "fork". Click on it, and then on your username. You now have your own fork, or copy, of The Modding Tree.

    4. Open Github Desktop and log in. Ignore everything else and choose "clone a repository". A "repository" is basically a "Github project", like The Modding Tree. "Cloning" is downloading a copy of the repository to your computer.

    5. Look for The Modding Tree in the list of repositiories (it should be the only one) and click "clone".

    6. Select that you're using it for your own purposes, and click continue. It will download the files and handle everything.

    Using your repository ​

    1. Click on "show in explorer/finder" to the right, and then open the index.html file in the folder. The page should open up on your browser. This will let you view and test your project locally!

    2. To edit your project, click "open in VSCode" in Github Desktop.

    3. Open mod.js in VSCode, and look at the top part where it has a "modInfo" object. Fill in your mod's name to whatever you want, and change the id as well. (It can be any string value, and it's used to determine where the savefile is. Make it something that's probably unique, and don't change it again later or else it'll effectively wipe existing saves)

    4. Save mod.js, and then reload index.html in your browser. The title on the tab, as well as on the info page, will now be updated! You can reload the page every time you change the code to test it quickly and easily.

    5. Go back to Github Desktop. It's time to save your changes into the git system by making a "commit". This basically saves your work and creates a snapshot of what your code looks like at this moment, allowing you to look back at it later.

    6. At the bottom right corner, add a summary of your changes, and then click "commit to master".

    7. Finally, at the top middle, click "push origin" to push your changes out onto the online repository.

    8. You can view your project on line, or share it with others, by going to https://raw.githack.com/[YOUR-GITHUB-USERNAME]/The-Modding-Tree/master/index.html

    And now, you have successfully used Github! You can look at the documentation to see how The Modding Tree's system works and to make your mod a reality.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +
    The Paper Pilot

    Appearance

    Getting started ​

    Welcome to The Modding Tree!

    Using the Modding Tree, at its simplest level, just requires getting a copy of it onto your computer. However, if you do it the right way, it will help in many ways.

    Don't let the word "Github" scare you away. It's actually much easier to use than most people think, especially because most people use it the hard way. The key is Github Desktop, which lets you do everything you need to, without even touching the command line.

    The benefits of using Github:

    • It makes it much, much easier to update The Modding Tree.
    • You can share your work without any extra effort using githack, or with a bit more effort, set up a github.io site.
    • It lets you undo changes to your code, and to have multiple versions of it.
    • It lets you collaborate with other people, if you want to.

    Getting set up with Github Desktop, Visual Studio Code, and The Modding Tree: ​

    1. Install Github Desktop and Visual Studio Code.

    2. Make a Github account. You can handle this on your own.

    3. Log in on your browser, and go back to The Modding Tree page. At the top right, there should be a button that says "fork". Click on it, and then on your username. You now have your own fork, or copy, of The Modding Tree.

    4. Open Github Desktop and log in. Ignore everything else and choose "clone a repository". A "repository" is basically a "Github project", like The Modding Tree. "Cloning" is downloading a copy of the repository to your computer.

    5. Look for The Modding Tree in the list of repositiories (it should be the only one) and click "clone".

    6. Select that you're using it for your own purposes, and click continue. It will download the files and handle everything.

    Using your repository ​

    1. Click on "show in explorer/finder" to the right, and then open the index.html file in the folder. The page should open up on your browser. This will let you view and test your project locally!

    2. To edit your project, click "open in VSCode" in Github Desktop.

    3. Open mod.js in VSCode, and look at the top part where it has a "modInfo" object. Fill in your mod's name to whatever you want, and change the id as well. (It can be any string value, and it's used to determine where the savefile is. Make it something that's probably unique, and don't change it again later or else it'll effectively wipe existing saves)

    4. Save mod.js, and then reload index.html in your browser. The title on the tab, as well as on the info page, will now be updated! You can reload the page every time you change the code to test it quickly and easily.

    5. Go back to Github Desktop. It's time to save your changes into the git system by making a "commit". This basically saves your work and creates a snapshot of what your code looks like at this moment, allowing you to look back at it later.

    6. At the bottom right corner, add a summary of your changes, and then click "commit to master".

    7. Finally, at the top middle, click "push origin" to push your changes out onto the online repository.

    8. You can view your project on line, or share it with others, by going to https://raw.githack.com/[YOUR-GITHUB-USERNAME]/The-Modding-Tree/master/index.html

    And now, you have successfully used Github! You can look at the documentation to see how The Modding Tree's system works and to make your mod a reality.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/grids.html b/public/kronos/docs/grids.html index ae491420..34983865 100644 --- a/public/kronos/docs/grids.html +++ b/public/kronos/docs/grids.html @@ -8,11 +8,7 @@ - - - - - + @@ -45,8 +41,8 @@ }, etc -}

    Features:

    • rows, cols: The amount of rows and columns of gridable to display.

    • maxRows, maxCols: sometimes needed. If rows or cols are dynamic, you need to define the maximum amount that there can be (you can increase it when you update the game though). These CANNOT be dynamic.

    • getStartData(id): Creates the default data for the gridable at this position. This can be an object, or a regular value.

    • getUnlocked(id): optional. Returns true if the gridable at this position should be visible.

    • getTitle(data, id): optional. Returns text that should displayed at the top in a larger font, based on the position and data of the gridable.

    • getDisplay(data, id): optional. Returns everything that should be displayed on the gridable after the title, based on the position and data of the gridable.

    • getStyle(data, id): optional. Returns CSS to apply to this gridable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • getCanClick(data, id): optional. A function returning a bool to determine if you can click a gridable, based on its data and position. If absent, you can always click it.

    • onClick(data, id): A function that implements clicking on the gridable, based on its position and data.

    • onHold(data, id): optional A function that is called 20x/sec when the button is held for at least 0.25 seconds.

    • getEffect(data, id): optional. A function that calculates and returns a gridable's effect, based on its position and data. (Whatever that means for a gridable)

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Features:

    • rows, cols: The amount of rows and columns of gridable to display.

    • maxRows, maxCols: sometimes needed. If rows or cols are dynamic, you need to define the maximum amount that there can be (you can increase it when you update the game though). These CANNOT be dynamic.

    • getStartData(id): Creates the default data for the gridable at this position. This can be an object, or a regular value.

    • getUnlocked(id): optional. Returns true if the gridable at this position should be visible.

    • getTitle(data, id): optional. Returns text that should displayed at the top in a larger font, based on the position and data of the gridable.

    • getDisplay(data, id): optional. Returns everything that should be displayed on the gridable after the title, based on the position and data of the gridable.

    • getStyle(data, id): optional. Returns CSS to apply to this gridable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • getCanClick(data, id): optional. A function returning a bool to determine if you can click a gridable, based on its data and position. If absent, you can always click it.

    • onClick(data, id): A function that implements clicking on the gridable, based on its position and data.

    • onHold(data, id): optional A function that is called 20x/sec when the button is held for at least 0.25 seconds.

    • getEffect(data, id): optional. A function that calculates and returns a gridable's effect, based on its position and data. (Whatever that means for a gridable)

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/infoboxes.html b/public/kronos/docs/infoboxes.html index f088f920..4847b85a 100644 --- a/public/kronos/docs/infoboxes.html +++ b/public/kronos/docs/infoboxes.html @@ -8,11 +8,7 @@ - - - - - + @@ -32,8 +28,8 @@ etc }, etc -}

    Features:

    • title: The text displayed above the main box. Can be a function to be dynamic, and can use basic HTML.

    • body: The text displayed inside the box. Can be a function to be dynamic, and can use basic HTML.

    • style, titleStyle, bodyStyle: optional. Apply CSS to the infobox, or to the title button or body of the infobox, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • unlocked(): optional. A function returning a bool to determine if the infobox is visible or not. Default is unlocked.

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

    • id: assigned automagically. It's the "key" which the bar was stored under, for convenient access. The infobox in the example's id is "lore".

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Features:

    • title: The text displayed above the main box. Can be a function to be dynamic, and can use basic HTML.

    • body: The text displayed inside the box. Can be a function to be dynamic, and can use basic HTML.

    • style, titleStyle, bodyStyle: optional. Apply CSS to the infobox, or to the title button or body of the infobox, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • unlocked(): optional. A function returning a bool to determine if the infobox is visible or not. Default is unlocked.

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

    • id: assigned automagically. It's the "key" which the bar was stored under, for convenient access. The infobox in the example's id is "lore".

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/layer-features.html b/public/kronos/docs/layer-features.html index 5fd17697..1069574e 100644 --- a/public/kronos/docs/layer-features.html +++ b/public/kronos/docs/layer-features.html @@ -8,11 +8,7 @@ - - - - - + @@ -35,8 +31,8 @@ ]

  • style: optional. a "CSS object" where the keys are CSS attributes, containing any CSS that should affect this layer's entire tab.

  • tabFormat: optional. use this if you want to add extra things to your tab or change the layout. See here for more info.

  • midsection: optional, an alternative to tabFormat, which is inserted in between Milestones and Buyables in the standard tab layout. (cannot do subtabs)

    • Big features (all optional) ​

    • upgrades: A set of one-time purchases which can have unique upgrade conditions, currency costs, and bonuses. See here for more info.

    • milestones: A list of bonuses gained upon reaching certain thresholds of a resource. Often used for automation/QOL. See here for more info.

    • challenges: The player can enter challenges, which make the game harder. If they reach a goal and beat the challenge, they recieve a bonus. See here for more info.

    • buyables: Effectively upgrades that can be bought multiple times, and are optionally respeccable. Many uses. See here for more info.

    • clickables: Extremely versatile and generalized buttons which can only be clicked sometimes. See here for more info.

    • microtabs: An area that functions like a set of subtabs, with buttons at the top changing the content within. (Advanced) See here for more info.

    • bars: Display some information as a progress bar, gague, or similar. They are highly customizable, and can be vertical as well. See here for more info.

    • achievements: Kind of like milestones, but with a different display style and some other differences. Extra features are on the way at a later date! See here for more info.

    • achievementPopups, milestonePopups: optional, If false, disables popup message when you get the achievement/milestone. True by default.

    • infoboxes: Displays some text in a box that can be shown or hidden. See here for more info.

    • grid: A grid of buttons that behave the same, but have their own data.See here for more info.

    Prestige formula features ​

    • type: optional. Determines which prestige formula you use. Defaults to "none".

      • "normal": The amount of currency you gain is independent of its current amount (like Prestige). The formula before bonuses is based on baseResource^exponent
      • "static": The cost is dependent on your total after reset. The formula before bonuses is based on base^(x^exponent)
      • "custom": You can define everything, from the calculations to the text on the button, yourself. (See more at the bottom)
      • "none": This layer does not prestige, and therefore does not need any of the other features in this section.

    • baseResource: The name of the resource that determines how much of the main currency you gain on reset.

    • baseAmount(): A function that gets the current value of the base resource.

    • requires: A Decimal, the amount of the base needed to gain 1 of the prestige currency. Also the amount required to unlock the layer. You can instead make this a function, to make it harder if another layer was unlocked first (based on unlockOrder).

    • exponent: Used as described above.

    • base: sometimes required. required for "static" layers, used as described above. If absent, defaults to 2. Must be greater than 1.

    • roundUpCost: optional. a bool, which is true if the resource cost needs to be rounded up. (use if the base resource is a "static" currency.)

    • gainMult(), gainExp(): optional. For normal layers, these functions calculate the multiplier and exponent on resource gain from upgrades and boosts and such. Plug in most bonuses here. For static layers, they instead divide and root the cost of the resource.

    • directMult(): optional. Directly multiplies the resource gain, after exponents and softcaps. For static layers, actually multiplies resource gain instead of reducing the cost.

    • softcap, softcapPower: optional. For normal layers, gain beyond [softcap] points is put to the [softcapPower]th power Default for softcap is e1e7, and for power is 0.5.

    • canBuyMax(): sometimes required. required for static layers, function used to determine if buying max is permitted.

    • onPrestige(gain): optional. A function that triggers when this layer prestiges, just before you gain the currency. Can be used to have secondary resource gain on prestige, or to recalculate things or whatnot.

    • resetDescription: optional. Use this to replace "Reset for " on the Prestige button with something else.

    • prestigeButtonText(): sometimes required. Use this to make the entirety of the text a Prestige button contains. Only required for custom layers, but usable by all types.

    • passiveGeneration(): optional, returns a regular number. You automatically generate your gain times this number every second (does nothing if absent) This is good for automating Normal layers.

    • autoPrestige(): optional, returns a boolean, if true, the layer will always automatically do a prestige if it can. This is good for automating Static layers.

    Tree/node features ​

    • symbol: optional. The text that appears on this layer's node. Default is the layer id with the first letter capitalized.

    • image: override. The url (local or global) of an image that goes on the node. (Overrides symbol)

    • position: optional. Determines the horizontal position of the layer in its row in a standard tree. By default, it uses the layer id, and layers are sorted in alphabetical order.

    • branches: optional. An array of layer/node ids. On a tree, a line will appear from this layer to all of the layers in the list. Alternatively, an entry in the array can be a 2-element array consisting of the layer id and a color value. The color value can either be a string with a hex color code, or a number from 1-3 (theme-affected colors).

    • nodeStyle: optional. A CSS object, where the keys are CSS attributes, which styles this layer's node on the tree.

    • tooltip() / tooltipLocked(): optional. Functions that return text, which is the tooltip for the node when the layer is unlocked or locked, respectively. By default the tooltips behave the same as in the original Prestige Tree. If the value is "", the tooltip will be disabled.

    • marked: optional Adds a mark to the corner of the node. If it's "true" it will be a star, but it can also be an image URL.

    Other features ​

    • doReset(resettingLayer): optional. Is triggered when a layer on a row greater than or equal to this one does a reset. The default behavior is to reset everything on the row, but only if it was triggered by a layer in a higher row. doReset is always called for side layers, but for these the default behavior is to reset nothing.

      If you want to keep things, determine what to keep based on resettingLayer, milestones, and such, then call layerDataReset(layer, keep), where layer is this layer, and keep is an array of the names of things to keep. It can include things like "points", "best", "total" (for this layer's prestige currency), "upgrades", any unique variables like "generatorPower", etc. If you want to only keep specific upgrades or something like that, save them in a separate variable, then call layerDataReset, and then set player[this.layer].upgrades to the saved upgrades.

    • update(diff): optional. This function is called every game tick. Use it for any passive resource production or time-based things. diff is the time since the last tick.

    • autoUpgrade: optional, a boolean value, if true, the game will attempt to buy this layer's upgrades every tick. Defaults to false.

    • automate(): optional. This function is called every game tick, after production. Use it to activate automation things that aren't otherwise supported.

    • resetsNothing: optional. Returns true if this layer shouldn't trigger any resets when you prestige.

    • increaseUnlockOrder: optional. An array of layer ids. When this layer is unlocked for the first time, the unlockOrder value for any not-yet-unlocked layers in this list increases. This can be used to make them harder to unlock.

    • shouldNotify: optional. A function to return true if this layer should be highlighted in the tree. The layer will automatically be highlighted if you can buy an upgrade whether you have this or not.

    • glowColor: optional. The color that this layer will be highlighted if it should notify. The default is red. You can use this if you want several different notification types!

    • componentStyles: optional. An object that contains a set of functions returning CSS objects. Each of these will be applied to any components on the layer with the type of its id. Example:

    js
    componentStyles: {
     "challenge"() { return {'height': '200px'} },
     "prestige-button"() { return {'color': '#AA66AA'} }
-}
    • deactivated: optional, if this is true, hasUpgrade, hasChallenge, hasAchievement, and hasMilestone will return false for things in the layer, and you will be unable to buy or click things on the layer. You will have to disable effects of buyables, the innate layer effect, and possibly other things yourself.

    Custom Prestige type ​

    (All of these can also be used by other prestige types)

    • getResetGain(): mostly for custom prestige type. Returns how many points you should get if you reset now. You can call getResetGain(this.layer, useType = "static") or similar to calculate what your gain would be under another prestige type (provided you have all of the required features in the layer).

    • getNextAt(canMax=false): mostly for custom prestige type. Returns how many of the base currency you need to get to the next point. canMax is an optional variable used with Static-ish layers to differentiate between if it's looking for the first point you can reset at, or the requirement for any gain at all (Supporting both is good). You can also call getNextAt(this.layer, canMax=false, useType = "static") or similar to calculate what your next at would be under another prestige type (provided you have all of the required features in the layer).

    • canReset(): mostly for custom prestige type. Return true only if you have the resources required to do a prestige here.

    • prestigeNotify(): mostly for custom prestige types, returns true if this layer should be subtly highlighted to indicate you can prestige for a meaningful gain.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}
    • deactivated: optional, if this is true, hasUpgrade, hasChallenge, hasAchievement, and hasMilestone will return false for things in the layer, and you will be unable to buy or click things on the layer. You will have to disable effects of buyables, the innate layer effect, and possibly other things yourself.

    Custom Prestige type ​

    (All of these can also be used by other prestige types)

    • getResetGain(): mostly for custom prestige type. Returns how many points you should get if you reset now. You can call getResetGain(this.layer, useType = "static") or similar to calculate what your gain would be under another prestige type (provided you have all of the required features in the layer).

    • getNextAt(canMax=false): mostly for custom prestige type. Returns how many of the base currency you need to get to the next point. canMax is an optional variable used with Static-ish layers to differentiate between if it's looking for the first point you can reset at, or the requirement for any gain at all (Supporting both is good). You can also call getNextAt(this.layer, canMax=false, useType = "static") or similar to calculate what your next at would be under another prestige type (provided you have all of the required features in the layer).

    • canReset(): mostly for custom prestige type. Return true only if you have the resources required to do a prestige here.

    • prestigeNotify(): mostly for custom prestige types, returns true if this layer should be subtly highlighted to indicate you can prestige for a meaningful gain.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/main-mod-info.html b/public/kronos/docs/main-mod-info.html index cbc09dc9..9d4e9022 100644 --- a/public/kronos/docs/main-mod-info.html +++ b/public/kronos/docs/main-mod-info.html @@ -8,11 +8,7 @@ - - - - - + @@ -29,8 +25,8 @@ var doNotCallTheseFunctionsEveryTick = ["doReset", "buy", "onPurchase", "blowUpEverything"]

    • getStartPoints(): A function to determine the amount of points the player starts with after a reset. (returns a Decimal value)

    • canGenPoints(): A function returning a boolean for if points should be generated. Use this if you want an upgrade to unlock generating points.

    • getPointGen(): A function that calculates your points per second. Anything that affects your point gain should go into the calculation here.

    • addedPlayerData(): A function that returns any non-layer-related data that you want to be added to the save data and "player" object.

    js
    function addedPlayerData() { return {
 	weather: "Yes",
 	happiness: new Decimal(72),
-}}

    • displayThings: An array of functions used to display extra things at the top of the tree tab. Each function returns a string, which is a line to display (with basic HTML support). If a function returns nothing, nothing is displayed (and it doesn't take up a line).

    • isEndgame(): A function to determine if the player has reached the end of the game, at which point the "you win!" screen appears.

    Less important things beyond this point!

    • maxTickLength(): Returns the maximum tick length, in milliseconds. Only really useful if you have something that reduces over time, which long ticks mess up (usually a challenge).

    • fixOldSave(): Can be used to modify a save file when loading into a new version of the game. Use this to undo inflation, never forcibly hard reset your players.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}}

    • displayThings: An array of functions used to display extra things at the top of the tree tab. Each function returns a string, which is a line to display (with basic HTML support). If a function returns nothing, nothing is displayed (and it doesn't take up a line).

    • isEndgame(): A function to determine if the player has reached the end of the game, at which point the "you win!" screen appears.

    Less important things beyond this point!

    • maxTickLength(): Returns the maximum tick length, in milliseconds. Only really useful if you have something that reduces over time, which long ticks mess up (usually a challenge).

    • fixOldSave(): Can be used to modify a save file when loading into a new version of the game. Use this to undo inflation, never forcibly hard reset your players.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/milestones.html b/public/kronos/docs/milestones.html index e3193dfd..a2a858a4 100644 --- a/public/kronos/docs/milestones.html +++ b/public/kronos/docs/milestones.html @@ -8,11 +8,7 @@ - - - - - + @@ -32,8 +28,8 @@ done() { return player.w.points.gte(123) } } etc -}

    You can use hasMilestone(layer, id) to determine if the player has a given milestone

    Milestone features:

    • requirementDescription: A string describing the requirement for unlocking this milestone. Suggestion: Use a "total". It can also be a function that returns updating text. Can use basic HTML.

    • effectDescription: A string describing the reward for having the milestone. You will have to implement the reward elsewhere. It can also be a function that returns updating text. Can use basic HTML.

    • done(): A function returning a boolean to determine if the milestone should be awarded.

    • toggles: optional. Creates toggle buttons that appear on the milestone when it is unlocked. The toggles can toggle a given boolean value in a layer. It is defined as an array of paired items, one pair per toggle. The first is the internal name of the layer the value being toggled is stored in, and the second is the internal name of the variable to toggle. (e.g. [["b", "auto"], ["g", "auto"])

      Tip: Toggles are not de-set if the milestone becomes locked! In this case, you should also check if the player has the milestone.

    • style: optional. Applies CSS to this milestone, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • unlocked(): optional. A function returning a boolean to determine if the milestone should be shown. If absent, it is always shown.

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the milestone was stored under, for convenient access. The milestone in the example's id is 0.

    Disaable milestone popups by adding milestonePopups: false to the layer.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    You can use hasMilestone(layer, id) to determine if the player has a given milestone

    Milestone features:

    • requirementDescription: A string describing the requirement for unlocking this milestone. Suggestion: Use a "total". It can also be a function that returns updating text. Can use basic HTML.

    • effectDescription: A string describing the reward for having the milestone. You will have to implement the reward elsewhere. It can also be a function that returns updating text. Can use basic HTML.

    • done(): A function returning a boolean to determine if the milestone should be awarded.

    • toggles: optional. Creates toggle buttons that appear on the milestone when it is unlocked. The toggles can toggle a given boolean value in a layer. It is defined as an array of paired items, one pair per toggle. The first is the internal name of the layer the value being toggled is stored in, and the second is the internal name of the variable to toggle. (e.g. [["b", "auto"], ["g", "auto"])

      Tip: Toggles are not de-set if the milestone becomes locked! In this case, you should also check if the player has the milestone.

    • style: optional. Applies CSS to this milestone, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • unlocked(): optional. A function returning a boolean to determine if the milestone should be shown. If absent, it is always shown.

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the milestone was stored under, for convenient access. The milestone in the example's id is 0.

    Disaable milestone popups by adding milestonePopups: false to the layer.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/particles.html b/public/kronos/docs/particles.html index f1e84034..2b91ddc6 100644 --- a/public/kronos/docs/particles.html +++ b/public/kronos/docs/particles.html @@ -8,11 +8,7 @@ - - - - - + @@ -35,8 +31,8 @@ return (Math.random() + 1.2) * 8 }, etc... -}

    Features can be functions or constant. These features will be called when each particle is made, with an id argument, which is assigned based on which of the amount particles being spawned this is. All of these are optional, with a default value.

    All distances are in pixels and angles are in degrees, with 0 being up and going clockwise.

    • time: The amount of time, in seconds, that the particle will last. Default is 3.

    • fadeOutTime: The amount of seconds that fading out at the end should take (part of the total lifetime). Default is 1.

    • fadeInTime: The amount of seconds that fading in should take (part of the total lifetime). Default is 0.

    • image: The image the particle should display. "" will display no image. Default is a generic particle.

    • text: Displays text on the particle. Can use basic HTML.

    • style: Lets you apply other CSS styling to the particle.

    • width, height: The dimensions of the particle. Default is 35 and 35.

    • color: Sets the color of the image to this color.

    • angle: The angle that the particle should face. Default is 0.

    • dir: The initial angle that the particles should move in, before spread is factored in. Default is whatever angle is.

    • spread: If there are several particles, they will be spread out by this many degrees, centered on dir. Default is 30.

    • rotation: The amount that the (visual) angle of the particle should change by. Default is 0.

    • speed: The starting speed of the particle. Default is 15.

    • gravity: The amount the particle should accelerate downwards. Default is 0.

    • x, y: The starting coordinates of the particle. Default is at the mouse position.

    • offset: How far from the start each particle should appear. Default is 10.

    • xVel, yVel: Set initially based on other properties, then used to update movement.

    • layer: When changing tabs, if leaving the layer tab, this particle will be erased.

    • You can add other features to particles, but you must impliment their effects yourself.

    Function features: These stay as functions and are for more advanced things. They are optional.

    • update(): Called each tick. Lets you do more advanced visual and movement behaviors by changing other properties.
    • onClick(), onMouseOver(), onMouseLeave(): Called when the particle is interacted with.

    Other useful things that are not features of the particle object:

    • setDir(particle, dir), setSpeed(particle, speed): Set the speed/direction on a particle.
    • clearParticles(check): Function to delete particles. With no check, it deletes all particles. Check is a function that takes a particle, and returns true if that particle should be deleted.
    • You can use Vue.delete(particles, this.id) to make a particle delete itself.
    • mouseX and mouseY are variables that track the mouse position.
    • sin(x), cos(x), tan(x): functions that do these operations, with x in degrees. (Instead of radians).
    • asin(x), acos(x), atan(x): functions that do these operations, with the returned value in degrees. (instead of radians).
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Features can be functions or constant. These features will be called when each particle is made, with an id argument, which is assigned based on which of the amount particles being spawned this is. All of these are optional, with a default value.

    All distances are in pixels and angles are in degrees, with 0 being up and going clockwise.

    • time: The amount of time, in seconds, that the particle will last. Default is 3.

    • fadeOutTime: The amount of seconds that fading out at the end should take (part of the total lifetime). Default is 1.

    • fadeInTime: The amount of seconds that fading in should take (part of the total lifetime). Default is 0.

    • image: The image the particle should display. "" will display no image. Default is a generic particle.

    • text: Displays text on the particle. Can use basic HTML.

    • style: Lets you apply other CSS styling to the particle.

    • width, height: The dimensions of the particle. Default is 35 and 35.

    • color: Sets the color of the image to this color.

    • angle: The angle that the particle should face. Default is 0.

    • dir: The initial angle that the particles should move in, before spread is factored in. Default is whatever angle is.

    • spread: If there are several particles, they will be spread out by this many degrees, centered on dir. Default is 30.

    • rotation: The amount that the (visual) angle of the particle should change by. Default is 0.

    • speed: The starting speed of the particle. Default is 15.

    • gravity: The amount the particle should accelerate downwards. Default is 0.

    • x, y: The starting coordinates of the particle. Default is at the mouse position.

    • offset: How far from the start each particle should appear. Default is 10.

    • xVel, yVel: Set initially based on other properties, then used to update movement.

    • layer: When changing tabs, if leaving the layer tab, this particle will be erased.

    • You can add other features to particles, but you must impliment their effects yourself.

    Function features: These stay as functions and are for more advanced things. They are optional.

    • update(): Called each tick. Lets you do more advanced visual and movement behaviors by changing other properties.
    • onClick(), onMouseOver(), onMouseLeave(): Called when the particle is interacted with.

    Other useful things that are not features of the particle object:

    • setDir(particle, dir), setSpeed(particle, speed): Set the speed/direction on a particle.
    • clearParticles(check): Function to delete particles. With no check, it deletes all particles. Check is a function that takes a particle, and returns true if that particle should be deleted.
    • You can use Vue.delete(particles, this.id) to make a particle delete itself.
    • mouseX and mouseY are variables that track the mouse position.
    • sin(x), cos(x), tan(x): functions that do these operations, with x in degrees. (Instead of radians).
    • asin(x), acos(x), atan(x): functions that do these operations, with the returned value in degrees. (instead of radians).
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/subtabs-and-microtabs.html b/public/kronos/docs/subtabs-and-microtabs.html index 2b668ac1..8d31f5f4 100644 --- a/public/kronos/docs/subtabs-and-microtabs.html +++ b/public/kronos/docs/subtabs-and-microtabs.html @@ -8,11 +8,7 @@ - - - - - + @@ -49,8 +45,8 @@ otherStuff: { // There could be another set of microtabs here } -}

    Normal subtabs and microtab subtabs both use the same features:

    Features: ​

    • content: The tab layout code for the subtab, in the tab layout format.

    • style: optional. Applies CSS to the whole subtab when switched to, in the form of an "CSS Object", where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • buttonStyle: optional. A CSS object, which affects the appearance of the button for that subtab.

    • unlocked(): optional. a function to determine if the button for this subtab should be visible. By default, a subtab is always unlocked. You can't use the "this" keyword in this function.

    • shouldNotify()/prestigeNotify(): optional, if true, the tab button will be highlighted to notify the player that there is something there.

    • glowColor: optional, specifies the color that the subtab glows. If this subtab is causing the main layer to node glow (and it would't otherwise) the node also glows this color. Is NOT overridden by embedding a layer.

    • embedLayer: SIGNIFICANT, the id of another layer. If you have this, it will override "content", "style" and "shouldNotify", instead displaying the entire layer in the subtab.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Normal subtabs and microtab subtabs both use the same features:

    Features: ​

    • content: The tab layout code for the subtab, in the tab layout format.

    • style: optional. Applies CSS to the whole subtab when switched to, in the form of an "CSS Object", where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • buttonStyle: optional. A CSS object, which affects the appearance of the button for that subtab.

    • unlocked(): optional. a function to determine if the button for this subtab should be visible. By default, a subtab is always unlocked. You can't use the "this" keyword in this function.

    • shouldNotify()/prestigeNotify(): optional, if true, the tab button will be highlighted to notify the player that there is something there.

    • glowColor: optional, specifies the color that the subtab glows. If this subtab is causing the main layer to node glow (and it would't otherwise) the node also glows this color. Is NOT overridden by embedding a layer.

    • embedLayer: SIGNIFICANT, the id of another layer. If you have this, it will override "content", "style" and "shouldNotify", instead displaying the entire layer in the subtab.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/trees-and-tree-customization.html b/public/kronos/docs/trees-and-tree-customization.html index 21942613..8ded4506 100644 --- a/public/kronos/docs/trees-and-tree-customization.html +++ b/public/kronos/docs/trees-and-tree-customization.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
    The Paper Pilot

    Appearance

    Trees and tree customization ​

    If you want to have something beyond the standard tree on the left tab, you can do that in tree.js. You can change the layout of the tree, including making non-layer nodes, change it into something other than a tree, or hide the left tab altogether. This also introduces the "tree" component, which can be used in your layers as well.

    layoutInfo ​

    The most important part is layoutInfo, containing:

    • startTab: The id of the default tab to show on the left at the start.
    • showTree: True if the tree tab should be shown at the start of the game. (The other tab will fill the whole page)
    • treeLayout: If present, overrides the tree layout and places nodes as you describe instead (explained in the next section).

    Additionally, if you want the main layout to not be a tree, you can edit the "tree-tab" layer at the bottom of tree.js to modify it just like a normal layer's tab. You can even switch between left tabs, using showNavTab(layer) to make that layer appear on the left.

    Trees ​

    The tree component is defined as an array of arrays of names of layers or nodes to show in the tree. They work just like layers/ nodes in the main tree (but branches between nodes will only work on the first node if you have duplicates.)

    Here is an example tree:

    js
    [["p"],
  ["left", "blank", "right", "blank"]
- ["a", "b", "blank", "c", "weirdButton"]]

    Nodes ​

    Nodes are non-layer buttons that can go in trees. They are defined similarly to layers, but with addNode instead of addLayer.

    Features:

    • color: optional, The node's color. (A string in hex format with a #)

    • symbol: optional The text on the button (The id capitalized by default)

    • canClick(): Returns true if the player can click the node. ()

    • onClick(): The function called when the node is clicked.

    • layerShown(): optional, A function returning a bool which determines if this node should be visible. It can also return "ghost", which will hide the layer, but its node will still take up space in its tree.

    • branches: optional. An array of layer/node ids. On a tree, a line will appear from this node to all of the nodes in the list. Alternatively, an entry in the array can be a 2-element array consisting of the id and a color value. The color value can either be a string with a hex color code, or a number from 1-3 (theme-affected colors).

    • nodeStyle: optional. A CSS object, where the keys are CSS attributes, which styles this node on the tree.

    • tooltip() / tooltipLocked(): optional. Functions that return text, which is the tooltip for the node when the layer is unlocked or locked, respectively. By default the tooltips behave the same as in the original Prestige Tree.

    • row: optional, the row that this node appears in (for the default tree).

    • position: optional, Determines the horizontal position of the layer in its row in a default tree. By default, it uses the id, and layers/nodes are sorted in alphabetical order.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - + ["a", "b", "blank", "c", "weirdButton"]]

    Nodes ​

    Nodes are non-layer buttons that can go in trees. They are defined similarly to layers, but with addNode instead of addLayer.

    Features:

    • color: optional, The node's color. (A string in hex format with a #)

    • symbol: optional The text on the button (The id capitalized by default)

    • canClick(): Returns true if the player can click the node. ()

    • onClick(): The function called when the node is clicked.

    • layerShown(): optional, A function returning a bool which determines if this node should be visible. It can also return "ghost", which will hide the layer, but its node will still take up space in its tree.

    • branches: optional. An array of layer/node ids. On a tree, a line will appear from this node to all of the nodes in the list. Alternatively, an entry in the array can be a 2-element array consisting of the id and a color value. The color value can either be a string with a hex color code, or a number from 1-3 (theme-affected colors).

    • nodeStyle: optional. A CSS object, where the keys are CSS attributes, which styles this node on the tree.

    • tooltip() / tooltipLocked(): optional. Functions that return text, which is the tooltip for the node when the layer is unlocked or locked, respectively. By default the tooltips behave the same as in the original Prestige Tree.

    • row: optional, the row that this node appears in (for the default tree).

    • position: optional, Determines the horizontal position of the layer in its row in a default tree. By default, it uses the id, and layers/nodes are sorted in alphabetical order.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/updating-tmt.html b/public/kronos/docs/updating-tmt.html index 26d300c1..8ac0c847 100644 --- a/public/kronos/docs/updating-tmt.html +++ b/public/kronos/docs/updating-tmt.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
    The Paper Pilot

    Appearance

    Updating The Modding Tree ​

    This tutorial assumes that you have used the Getting Started Tutorial, and are using Github Desktop and VSCode for your mod.

    Here's what you have to do when there's a TMT update:

    1. Look at the changelog. It will warn you if the update will break anything or require any changes. Decide if you want to try to update.

    2. Open Github Desktop, and at the top middle, click "fetch origin". This will make Github Desktop get information about the update.

    3. Click where it says "current branch: master" at the top middle, and at the bottom of the thing that appears, click "choose a branch to merge into master".

    4. Select upstream/master. It will likely say there are conflicts, but you have tools to resolve them. Click "Merge upstream/master into master".

    5. A conflict happens when the things you're trying to merge have both made changes in the same place. Click "open in Visual Studio Code" next to the first file.

    6. Scroll down through the file, and look for the parts highlighted in red and green. One of these is your code, and the other is some code that will be modified by the update. Do your best to try to edit things to keep the updated changes, but keep your content.

    7. Continue to do this for all remaining changes.

    8. Do any other changes required by the update, run the game, fix issues, etc.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +
    The Paper Pilot

    Appearance

    Updating The Modding Tree ​

    This tutorial assumes that you have used the Getting Started Tutorial, and are using Github Desktop and VSCode for your mod.

    Here's what you have to do when there's a TMT update:

    1. Look at the changelog. It will warn you if the update will break anything or require any changes. Decide if you want to try to update.

    2. Open Github Desktop, and at the top middle, click "fetch origin". This will make Github Desktop get information about the update.

    3. Click where it says "current branch: master" at the top middle, and at the bottom of the thing that appears, click "choose a branch to merge into master".

    4. Select upstream/master. It will likely say there are conflicts, but you have tools to resolve them. Click "Merge upstream/master into master".

    5. A conflict happens when the things you're trying to merge have both made changes in the same place. Click "open in Visual Studio Code" next to the first file.

    6. Scroll down through the file, and look for the parts highlighted in red and green. One of these is your code, and the other is some code that will be modified by the update. Do your best to try to edit things to keep the updated changes, but keep your content.

    7. Continue to do this for all remaining changes.

    8. Do any other changes required by the update, run the game, fix issues, etc.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/kronos/docs/upgrades.html b/public/kronos/docs/upgrades.html index e077ec45..96c2a2d4 100644 --- a/public/kronos/docs/upgrades.html +++ b/public/kronos/docs/upgrades.html @@ -8,11 +8,7 @@ - - - - - + @@ -32,8 +28,8 @@ etc }, etc -}

    Usually, upgrades should have an id where the first digit is the row and the second digit is the column.

    Individual upgrades can have these features:

    • title: optional. Displayed at the top in a larger font. It can also be a function that returns updating text. Can use basic HTML.

    • description: A description of the upgrade's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

    • effect(): optional. A function that calculates and returns the current values of any bonuses from the upgrade. Can return a value or an object containing multiple values.

    • effectDisplay(): optional. A function that returns a display of the current effects of the upgrade with formatting. Default displays nothing. Can use basic HTML.

    • fullDisplay(): OVERRIDE. Overrides the other displays and descriptions, and lets you set the full text for the upgrade. Can use basic HTML.

    • cost: A Decimal for the cost of the upgrade. By default, upgrades cost the main prestige currency for the layer.

    • unlocked(): optional. A function returning a bool to determine if the upgrade is visible or not. Default is unlocked.

    • onPurchase(): optional. This function will be called when the upgrade is purchased. Good for upgrades like "makes this layer act like it was unlocked first".

    • style: optional. Applies CSS to this upgrade, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the upgrade was stored under, for convenient access. The upgrade in the example's id is 11.

    By default, upgrades use the main prestige currency for the layer. You can include these to change them (but it needs to be a Decimal):

    • currencyDisplayName: optional. The name to display for the currency for the upgrade.

    • currencyInternalName: optional. The internal name for that currency.

    • currencyLayer: optional. The internal name of the layer that currency is stored in. If it's not in a layer (like Points), omit. If it's not stored directly in a layer, instead use the next feature.

    • currencyLocation: optional. If your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

    If you want to do something more complicated like upgrades that cost two currencies, you can override the purchase system with these (and you need to use fullDisplay as well)

    • canAfford(): OVERRIDE, a function determining if you are able to buy the upgrade

    • pay(): OVERRIDE, a function that reduces your currencies when you buy the upgrade

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Usually, upgrades should have an id where the first digit is the row and the second digit is the column.

    Individual upgrades can have these features:

    • title: optional. Displayed at the top in a larger font. It can also be a function that returns updating text. Can use basic HTML.

    • description: A description of the upgrade's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

    • effect(): optional. A function that calculates and returns the current values of any bonuses from the upgrade. Can return a value or an object containing multiple values.

    • effectDisplay(): optional. A function that returns a display of the current effects of the upgrade with formatting. Default displays nothing. Can use basic HTML.

    • fullDisplay(): OVERRIDE. Overrides the other displays and descriptions, and lets you set the full text for the upgrade. Can use basic HTML.

    • cost: A Decimal for the cost of the upgrade. By default, upgrades cost the main prestige currency for the layer.

    • unlocked(): optional. A function returning a bool to determine if the upgrade is visible or not. Default is unlocked.

    • onPurchase(): optional. This function will be called when the upgrade is purchased. Good for upgrades like "makes this layer act like it was unlocked first".

    • style: optional. Applies CSS to this upgrade, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the upgrade was stored under, for convenient access. The upgrade in the example's id is 11.

    By default, upgrades use the main prestige currency for the layer. You can include these to change them (but it needs to be a Decimal):

    • currencyDisplayName: optional. The name to display for the currency for the upgrade.

    • currencyInternalName: optional. The internal name for that currency.

    • currencyLayer: optional. The internal name of the layer that currency is stored in. If it's not in a layer (like Points), omit. If it's not stored directly in a layer, instead use the next feature.

    • currencyLocation: optional. If your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

    If you want to do something more complicated like upgrades that cost two currencies, you can override the purchase system with these (and you need to use fullDisplay as well)

    • canAfford(): OVERRIDE, a function determining if you are able to buy the upgrade

    • pay(): OVERRIDE, a function that reduces your currencies when you buy the upgrade

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/Old Things/2.0-format-changes.html b/public/lit/Old Things/2.0-format-changes.html index 5d82a4ec..3864141e 100644 --- a/public/lit/Old Things/2.0-format-changes.html +++ b/public/lit/Old Things/2.0-format-changes.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
    The Paper Pilot

    Appearance

    2.0 format changes ​

    • Temp format is changed from temp.something[layer] to temp[layer].something, for consistency
    • Challenges are now saved as an object with the amount of completions in each spot. (This will break saves.)
    • effectDisplay in Challenges and Upgrades no longer takes an argument, and neither does effect for Buyables
    • Buyable cost can take an argument for amount of buyables, but it needs to function if no argument is supplied (it should do the cost for the next purchase).
    • Generation of Points now happens in the main game loop (not in a layer update function), enabled by canGenPoints in game.js.
    • Changed fullLayerReset to layerDataReset, which takes an array of names of values to keep

    In addition, many names were changed, mostly expanding abbreviations:

    All instances of:

    • chall -> challenge
    • unl -> unlocked
    • upg -> upgrade (besides CSS)
    • amt -> amount
    • desc -> description
    • resCeil -> roundUpCost
    • order -> unlockOrder
    • incr_order -> increaseUnlockOrder

    Challenges:

    • desc -> challengeDescription
    • reward -> rewardDescription
    • effect -> rewardEffect
    • effectDisplay -> rewardDisplay
    • active -> challengeActive
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +
    The Paper Pilot

    Appearance

    2.0 format changes ​

    • Temp format is changed from temp.something[layer] to temp[layer].something, for consistency
    • Challenges are now saved as an object with the amount of completions in each spot. (This will break saves.)
    • effectDisplay in Challenges and Upgrades no longer takes an argument, and neither does effect for Buyables
    • Buyable cost can take an argument for amount of buyables, but it needs to function if no argument is supplied (it should do the cost for the next purchase).
    • Generation of Points now happens in the main game loop (not in a layer update function), enabled by canGenPoints in game.js.
    • Changed fullLayerReset to layerDataReset, which takes an array of names of values to keep

    In addition, many names were changed, mostly expanding abbreviations:

    All instances of:

    • chall -> challenge
    • unl -> unlocked
    • upg -> upgrade (besides CSS)
    • amt -> amount
    • desc -> description
    • resCeil -> roundUpCost
    • order -> unlockOrder
    • incr_order -> increaseUnlockOrder

    Challenges:

    • desc -> challengeDescription
    • reward -> rewardDescription
    • effect -> rewardEffect
    • effectDisplay -> rewardDisplay
    • active -> challengeActive
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/README.html b/public/lit/README.html index 6016ba28..9d421231 100644 --- a/public/lit/README.html +++ b/public/lit/README.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
    The Paper Pilot

    Appearance

    Kronos ​

    Play here.

    Updating the website:

    • git submodule update --remote
    • git add -A
    • git commit -m "Updated kronos"
    • git push
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +
    The Paper Pilot

    Appearance

    Kronos ​

    Play here.

    Updating the website:

    • git submodule update --remote
    • git add -A
    • git commit -m "Updated kronos"
    • git push
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/changelog.html b/public/lit/changelog.html index e7af32f6..1276f803 100644 --- a/public/lit/changelog.html +++ b/public/lit/changelog.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
    The Paper Pilot

    Appearance

    The Modding Tree changelog: ​

    v2.π: Incrementally Updated - 2/5/21 ​

    • Performance improvements.
    • Fixed tooltips overlapping with the top display.
    • Clicking a popup dismisses it immediately.
    • Added support for bulk challenge completions.
    • "Best" is updated automatically.
    • Fixed keeping Decimal values on reset.
    • Code reorganization and style improvements by fudo.

    v2.3.5 - 12/21/20 ​

    • Added resetTime, which tracks the time since a layer prestiged or was reset.
    • A layer node will be highlighted red if one of its subtabs is highlighted red.
    • Fixed issues with keeping challenges, buyables, and clickables on reset.
    • Improved the unlocking of custom layers.
    • Other minor fixes.

    v2.3.4 - 12/16/20 ​

    • Added a node image feature.
    • Resource display now always shows the amount of the currency the layer's gain is based on.
    • Added spacing between tree nodes.
    • Another attempt to fix tooltip flickering.

    v2.3.3 - 12/13/20 ​

    • Fixed the first node in a row always taking up space.
    • layerShown is now optional.
    • All prestige types can now use features for custom prestige types.

    v2.3.2 - 12/13/20 ​

    • Fixed achievement/milestone popups.

    v2.3.1 - 12/12/20 ​

    • Another attempt to fix flickering tooltips.
    • The "this" keyword should work everywhere except tabFormat arrays (although I may have missed some things).
    • Fixed tree branches not updating when scrolling on the right-side tab.
    • Fixed a spacing issue when a node's symbol is ""
    • Removed some old, unneeded files.

    v2.3: Cooler and Newer Edition - 12/10/20 ​

    • Added achievement/milestone popups (thank you to Jacorb for this contribution!)
    • The changelog tab is back, and can be set in mod.js.
    • Layer nodes and respec buttons will not be clicked by pressing "enter".
    • Possible fix for flickering tooltips and strange transitions.
    • The victory screen text is configurable.
    • Added image and textStyle features to achievements.
    • Added an argument to use specific rows in an "upgrades" component.
    • Fixed the comma appearing in the main display when there was no effectDescription
    • Added the ability to easily make a tab that is a collection of layers in subtabs.
    • Improved spacing for embedding layers with subtabs into subtabs.

    v2.2.8 - 12/03/20 ​

    • Double-clicking a layer node brings you to the main subtab for that layer.
    • Attempted to fix challenges visually updating a different way.
    • Added a softcap function for use in formulas.
    • Added displayRow feature, which lets layers be shown somewhere separate from where they are in the reset order (e.g. side layers)
    • Fixed autoupgrade issue.

    v2.2.7 - 11/30/20 ​

    • Added autoUpgrade feature.
    • resource-display now shows resource gain per second if passiveGain is active.
    • Fixed formatting issues on some large numbers.
    • Better support for using classed objects in player and in layers/tmp.
    • Made hard resetting more effective.
    • Removed Herobrine from getStartClickables.

    v2.2.6 - 11/30/20 ​

    • Added goalDescription for challenges and made the new "canComplete" system the standard.
    • Another attempt to fix challenges not visually updating.
    • Fixed side layers not appearing.
    • Fixed getStartClickables again.

    v2.2.5 - 11/29/20 ​

    • Added features for overriding the displays and costs/goals of upgrades and challenges to make them fully custom.
    • best, total, and unlocked are always automatically added to layerData (but best and total will only display if you add them yourself).
    • Fixed getStartClickables.

    v2.2.4 - 11/28/20 ​

    • Added softcap and softcapPower features (for Normal layers)
    • Offline time limit and default max tick length were fixed (previously the limits were 1000x too large)
    • Added fixOldSaves.
    • You can use HTML in main-display.
    • Fixed a number of minor oddities.

    v2.2.3 - 11/28/20 ​

    • Layers will be highlighted if you can finish a challenge.
    • The "can complete challenge" color now overrides the "already completed" color.
    • Button nodes now work as side "layers".
    • Setting a tooltip to "" hides it entirely.

    v2.2.2 - 11/22/20 ​

    • Fixed right half of the screen being unclickable in some circumstances.
    • Fixed tree branches being offset.
    • Fix to lastSafeTab.

    v2.2.1 - 11/7/20 ​

    • Added a small highlight to layers you can meaningfully prestige on.
    • Added passiveGeneration and autoPrestige features to standardize prestige automation. (The old ways still work, but the new ones work better with other things)
    • Improved milestones visually a bit.
    • "best" and "total" are now only displayed if present in startData.
    • Fixed issues with things not updating visually. (Thank you to to Jacorb!)
    • Side layers and button nodes can now be highlighted.
    • Updated docs on the new tree-related features.

    v2.2: Uprooted - 11/7/20 ​

    • You can now embed a layer inside of a subtab or microtab!
    • Added support for hiding or reformatting the tree tab
    • Added non-layer button nodes
    • Added shouldNotify to subtab/microtab buttons. (You can make them highlighted)
    • Added commas to large exponents.
    • Upgrades now only show "currently" if they have an effectDisplay (so not for constant effects).
    • Achievements are part of the default tab format.
    • NaN is now handled more intelligently.
    • Renamed files, and moved less relevant ones to another folder.
    • The "hide completed challenges" setting now only hides challenges at max completions.
    • Thank you to thepaperpilot for fixing errors in docs and improving the infobox appearance!
    • Many other minor fixes.

    v2.1.4 - 10/25/20 ​

    • Added an infobox component. Thank you to thepaperpilot for this contribution!
    • Layer type is now optional, and defaults to "none".
    • Improved the look of bars and tab buttons.
    • Improved spacing between layer nodes (also thanks to thepaperpilot!)
    • Fixed the "blank" component breaking if only specifying the height.
    • Fixed some numbers not displaying with enough digits.
    • Made a few more things able to be functions.
    • A few other minor fixes.

    v2.1.3.1 - 10/21/20 ​

    • Fixed the update function.

    v2.1.3 - 10/21/20 ​

    • gainMult and gainExp are now optional.
    • Layer unlocking is now kept on reset.
    • Game should start up faster.
    • Layer updates now have a determined order and starts with earlier-rowed layers.
    • Automation now has a determined order and starts with later-rowed layers.
    • Fixed issues with resetting clickables and challenges.
    • Commas should no longer appear in the decimal places of a number.
    • Fixed potential issue in displaying the tree.

    v2.1.2 - 10/19/20 ​

    • Added buyUpgrade function (buyUpg still works though)
    • Added author name to modInfo.
    • Fix to crash caused when the name of a subtab or microtab is changed.
    • Fixes to outdated information in docs.
    • Improvements to Discord links.
    • Thank you to thepaperpilot for contributing to this update!

    v2.1.1 - 10/17/20 ​

    • Added resource-display component, which displays the base currency for the prestige layer, as well as the best and/or total of this layer's prestige currency.
    • Fixed the value for the base currency not updating in resource-display.

    v2.1: We should have thought of this sooner! - 10/17/20 ​

    • Moved most of the code users will want to edit to mod.js, added documentation for it.
      • Specifically, modInfo, VERSION, canGenPoints, getPointGen, and maxTickLength
    • Added getStartPoints()
    • Added the ability to store non-layer-related data
    • Added the ability to display more things at the top of the tree tab below points.
    • Made the endgame condition customizable
    • Added "sell one" and "sell all" buttons for buyables.
    • Moved the old "game" to demo.js, and replaced it with a minimal game that won't cause issues when edited.
    • Fixed issues with version number
    • Fixed number formatting issue making things like "10e9" appear.

    v2.0.5 - 10/16/20 ​

    • Made more features (including prestige parameters) able to be dynamic.
    • Layer nodes can be hidden but still take up space with "ghost" visibility
    • Added clickableEffect for real.
    • Fixed some visual issues with bars.
    • A few other minor tweaks and improvements.

    v2.0.4 - 10/16/20 ​

    • Fixed HTML on buttons interfering with clicking on them.

    v2.0.3 - 10/16/20 ​

    • Fixed hotkeys not displaying in info.
    • Fixed the game supressing all external hotkeys.
    • You can use more things as currencies for upgrade costs and challenge goals using currencyLocation.
    • Added maxTickLength, which can be used to prevent offline time or tab-switching from breaking time-limit based mechanics.
    • Made buyable respec buttons and clickable "master" buttons their own components, and gave them a hide/show feature.
    • Added a general "tooltip" feature for achievements.

    v2.0.2 - 10/15/20 ​

    • Branches are now dynamic (they can be functions).
    • Fixed a crash related to offline time.
    • Fixed links being too wide.

    v2.0.1 - 10/15/20 ​

    • Fixed side layers appearing multiple times.

    v2.0: The Pinnacle of Achievement Mountain - 10/15/20 ​

    • Added progress bars, which are highly customizable and can be horizontal or vertical!
    • Added "side layers", displayed smaller and off to the side, and don't get reset by default. They can be used for global achievements and statistics. Speaking of which...
    • Added achievements!
    • Added clickables, a more generalized variant of buyables.
    • Almost every value in layer data can be either a function or a constant value!
    • Added support for multiple completions of challenges.
    • Added "none" prestige type, which removes the need for any other prestige-related features.
    • The points display and other gui elements stay at the top of the screen when the tree scrolls.
    • Added getter/setter functions for the amounts and effects of most Big Features
    • Moved modInfo to game.js, added a spot in modInfo for a Discord link, changelog link. Also added a separate mod version from the TMT version in VERSION.
    • Tree structure is based on layer data, no index.html editing is needed.
    • Tmp does not need to be manually updated.
    • You don't have to have the same amount of upgrades in every row (and challs and buyables)
    • "unlocked" is optional for all Big Components (defaults to true).
    • All displays will update correctly.
    • Changelog is no longer in index.html at all.
    • Generation of Points now happens in the main game loop
    • Changed the reset functions to make keeping things easier
    • Renamed many things to increase readability (see the list in the link below)
    • Improved documentation based on feedback

    v1.3.5: ​

    • Completely automated convertToDecimal, now you never have to worry about it again.
    • Branches can be defined without a color id. But they can also use hex values for color ids!
    • Created a tutorial for getting started with TMT and Github.
    • Page title is now automatically taken from mod name.

    v1.3.4 - 10/8/20 ​

    • Added "midsection" feature to add things to a tab's layout while still keeping the standard layout.
    • Fix for being able to buy more buyables than you should.

    v1.3.3 - 10/7/20 ​

    • Fix for the "order of operations" issue in temp.

    v1.3.1 - 10/7/20 ​

    • Added custom CSS and tooltips for Layer Nodes.
    • Added custom CSS for upgrades, buyables, milestones, and challenges, both individually and layer-wide.
    • You can now use HTML in most display text!
    • You can now make milestones unlockable and not display immediately.
    • Fixed importing saves, and issue with upgrades not appearing, and probably more.
    • Optional "name" layer feature, used in confirmation messages.

    v1.3: Tabception... ception! - 10/7/20 ​

    • Added subtabs! And also a Micro-tab component to let you make smaller subtab-esque areas anywhere.
    • Added a "custom" prestige formula type, and a number of features to support it.
    • Added points/sec display (can be disabled).
    • Added h-line, v-line and image-display components, plus components for individual upgrades, challenges, and milestones.
    • Added upgEffect, buyableEffect, and challEffect functions.
    • Added "hide completed challenges" setting.
    • Moved old changelogs to a separate place.
    • Fixed hasMilestone and incr_order.
    • Static layers now show the currency amount needed for the next one if you can buy max.

    v1.2.4 - 10/4/20 ​

    • Layers are now highlighted if you can buy an upgrade, and a new feature, shouldNotify, lets you make it highlight other ways.
    • Fixed bugs with hasUpg, hasChall, hasMilestone, and inChallenge.
    • Changed the sample code to use the above functions for convenience.

    v1.2.3 - 10/3/20 ​

    • Added a row component, which displays a list of objects in a row.
    • Added a column component, which displays a list of objects in a column (useful within a row).
    • Changed blanks to have a customizable width and height.

    v1.2: This Changes Everything! - 10/3/20 ​

    • Many layer features can now be static values or functions. (This made some formats change, which will break old things)
    • You can now use the "this" keyword, to make code easier to transfer when making new layers.
    • Also added "this.layer", which is the current layer's name, and works on existing subfeatures (e.g. individual upgrades) as well! Subfeatures also have "this.id".
    • Fixed a big save issue. If you use a unique mod id, your save will never conflict with other mods.
    • Added a configurable offline time limit in modinfo at the top of index.html. (default 1 hour)
    • Added a few minor features, and updated the docs with new information.

    v1.1.1: ​

    • You can define hotkeys directly from layer config.

    v1.1: Enhanced Edition ​

    • Added "Buyables", which can function like Space Buildings or Enhancers.
    • Custom CSS can now be used on any component! Make the third argument an object with CSS parameters.
    • Lots of minor good things.

    v1.0: ​

    • First release.
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +
    The Paper Pilot

    Appearance

    The Modding Tree changelog: ​

    v2.π: Incrementally Updated - 2/5/21 ​

    • Performance improvements.
    • Fixed tooltips overlapping with the top display.
    • Clicking a popup dismisses it immediately.
    • Added support for bulk challenge completions.
    • "Best" is updated automatically.
    • Fixed keeping Decimal values on reset.
    • Code reorganization and style improvements by fudo.

    v2.3.5 - 12/21/20 ​

    • Added resetTime, which tracks the time since a layer prestiged or was reset.
    • A layer node will be highlighted red if one of its subtabs is highlighted red.
    • Fixed issues with keeping challenges, buyables, and clickables on reset.
    • Improved the unlocking of custom layers.
    • Other minor fixes.

    v2.3.4 - 12/16/20 ​

    • Added a node image feature.
    • Resource display now always shows the amount of the currency the layer's gain is based on.
    • Added spacing between tree nodes.
    • Another attempt to fix tooltip flickering.

    v2.3.3 - 12/13/20 ​

    • Fixed the first node in a row always taking up space.
    • layerShown is now optional.
    • All prestige types can now use features for custom prestige types.

    v2.3.2 - 12/13/20 ​

    • Fixed achievement/milestone popups.

    v2.3.1 - 12/12/20 ​

    • Another attempt to fix flickering tooltips.
    • The "this" keyword should work everywhere except tabFormat arrays (although I may have missed some things).
    • Fixed tree branches not updating when scrolling on the right-side tab.
    • Fixed a spacing issue when a node's symbol is ""
    • Removed some old, unneeded files.

    v2.3: Cooler and Newer Edition - 12/10/20 ​

    • Added achievement/milestone popups (thank you to Jacorb for this contribution!)
    • The changelog tab is back, and can be set in mod.js.
    • Layer nodes and respec buttons will not be clicked by pressing "enter".
    • Possible fix for flickering tooltips and strange transitions.
    • The victory screen text is configurable.
    • Added image and textStyle features to achievements.
    • Added an argument to use specific rows in an "upgrades" component.
    • Fixed the comma appearing in the main display when there was no effectDescription
    • Added the ability to easily make a tab that is a collection of layers in subtabs.
    • Improved spacing for embedding layers with subtabs into subtabs.

    v2.2.8 - 12/03/20 ​

    • Double-clicking a layer node brings you to the main subtab for that layer.
    • Attempted to fix challenges visually updating a different way.
    • Added a softcap function for use in formulas.
    • Added displayRow feature, which lets layers be shown somewhere separate from where they are in the reset order (e.g. side layers)
    • Fixed autoupgrade issue.

    v2.2.7 - 11/30/20 ​

    • Added autoUpgrade feature.
    • resource-display now shows resource gain per second if passiveGain is active.
    • Fixed formatting issues on some large numbers.
    • Better support for using classed objects in player and in layers/tmp.
    • Made hard resetting more effective.
    • Removed Herobrine from getStartClickables.

    v2.2.6 - 11/30/20 ​

    • Added goalDescription for challenges and made the new "canComplete" system the standard.
    • Another attempt to fix challenges not visually updating.
    • Fixed side layers not appearing.
    • Fixed getStartClickables again.

    v2.2.5 - 11/29/20 ​

    • Added features for overriding the displays and costs/goals of upgrades and challenges to make them fully custom.
    • best, total, and unlocked are always automatically added to layerData (but best and total will only display if you add them yourself).
    • Fixed getStartClickables.

    v2.2.4 - 11/28/20 ​

    • Added softcap and softcapPower features (for Normal layers)
    • Offline time limit and default max tick length were fixed (previously the limits were 1000x too large)
    • Added fixOldSaves.
    • You can use HTML in main-display.
    • Fixed a number of minor oddities.

    v2.2.3 - 11/28/20 ​

    • Layers will be highlighted if you can finish a challenge.
    • The "can complete challenge" color now overrides the "already completed" color.
    • Button nodes now work as side "layers".
    • Setting a tooltip to "" hides it entirely.

    v2.2.2 - 11/22/20 ​

    • Fixed right half of the screen being unclickable in some circumstances.
    • Fixed tree branches being offset.
    • Fix to lastSafeTab.

    v2.2.1 - 11/7/20 ​

    • Added a small highlight to layers you can meaningfully prestige on.
    • Added passiveGeneration and autoPrestige features to standardize prestige automation. (The old ways still work, but the new ones work better with other things)
    • Improved milestones visually a bit.
    • "best" and "total" are now only displayed if present in startData.
    • Fixed issues with things not updating visually. (Thank you to to Jacorb!)
    • Side layers and button nodes can now be highlighted.
    • Updated docs on the new tree-related features.

    v2.2: Uprooted - 11/7/20 ​

    • You can now embed a layer inside of a subtab or microtab!
    • Added support for hiding or reformatting the tree tab
    • Added non-layer button nodes
    • Added shouldNotify to subtab/microtab buttons. (You can make them highlighted)
    • Added commas to large exponents.
    • Upgrades now only show "currently" if they have an effectDisplay (so not for constant effects).
    • Achievements are part of the default tab format.
    • NaN is now handled more intelligently.
    • Renamed files, and moved less relevant ones to another folder.
    • The "hide completed challenges" setting now only hides challenges at max completions.
    • Thank you to thepaperpilot for fixing errors in docs and improving the infobox appearance!
    • Many other minor fixes.

    v2.1.4 - 10/25/20 ​

    • Added an infobox component. Thank you to thepaperpilot for this contribution!
    • Layer type is now optional, and defaults to "none".
    • Improved the look of bars and tab buttons.
    • Improved spacing between layer nodes (also thanks to thepaperpilot!)
    • Fixed the "blank" component breaking if only specifying the height.
    • Fixed some numbers not displaying with enough digits.
    • Made a few more things able to be functions.
    • A few other minor fixes.

    v2.1.3.1 - 10/21/20 ​

    • Fixed the update function.

    v2.1.3 - 10/21/20 ​

    • gainMult and gainExp are now optional.
    • Layer unlocking is now kept on reset.
    • Game should start up faster.
    • Layer updates now have a determined order and starts with earlier-rowed layers.
    • Automation now has a determined order and starts with later-rowed layers.
    • Fixed issues with resetting clickables and challenges.
    • Commas should no longer appear in the decimal places of a number.
    • Fixed potential issue in displaying the tree.

    v2.1.2 - 10/19/20 ​

    • Added buyUpgrade function (buyUpg still works though)
    • Added author name to modInfo.
    • Fix to crash caused when the name of a subtab or microtab is changed.
    • Fixes to outdated information in docs.
    • Improvements to Discord links.
    • Thank you to thepaperpilot for contributing to this update!

    v2.1.1 - 10/17/20 ​

    • Added resource-display component, which displays the base currency for the prestige layer, as well as the best and/or total of this layer's prestige currency.
    • Fixed the value for the base currency not updating in resource-display.

    v2.1: We should have thought of this sooner! - 10/17/20 ​

    • Moved most of the code users will want to edit to mod.js, added documentation for it.
      • Specifically, modInfo, VERSION, canGenPoints, getPointGen, and maxTickLength
    • Added getStartPoints()
    • Added the ability to store non-layer-related data
    • Added the ability to display more things at the top of the tree tab below points.
    • Made the endgame condition customizable
    • Added "sell one" and "sell all" buttons for buyables.
    • Moved the old "game" to demo.js, and replaced it with a minimal game that won't cause issues when edited.
    • Fixed issues with version number
    • Fixed number formatting issue making things like "10e9" appear.

    v2.0.5 - 10/16/20 ​

    • Made more features (including prestige parameters) able to be dynamic.
    • Layer nodes can be hidden but still take up space with "ghost" visibility
    • Added clickableEffect for real.
    • Fixed some visual issues with bars.
    • A few other minor tweaks and improvements.

    v2.0.4 - 10/16/20 ​

    • Fixed HTML on buttons interfering with clicking on them.

    v2.0.3 - 10/16/20 ​

    • Fixed hotkeys not displaying in info.
    • Fixed the game supressing all external hotkeys.
    • You can use more things as currencies for upgrade costs and challenge goals using currencyLocation.
    • Added maxTickLength, which can be used to prevent offline time or tab-switching from breaking time-limit based mechanics.
    • Made buyable respec buttons and clickable "master" buttons their own components, and gave them a hide/show feature.
    • Added a general "tooltip" feature for achievements.

    v2.0.2 - 10/15/20 ​

    • Branches are now dynamic (they can be functions).
    • Fixed a crash related to offline time.
    • Fixed links being too wide.

    v2.0.1 - 10/15/20 ​

    • Fixed side layers appearing multiple times.

    v2.0: The Pinnacle of Achievement Mountain - 10/15/20 ​

    • Added progress bars, which are highly customizable and can be horizontal or vertical!
    • Added "side layers", displayed smaller and off to the side, and don't get reset by default. They can be used for global achievements and statistics. Speaking of which...
    • Added achievements!
    • Added clickables, a more generalized variant of buyables.
    • Almost every value in layer data can be either a function or a constant value!
    • Added support for multiple completions of challenges.
    • Added "none" prestige type, which removes the need for any other prestige-related features.
    • The points display and other gui elements stay at the top of the screen when the tree scrolls.
    • Added getter/setter functions for the amounts and effects of most Big Features
    • Moved modInfo to game.js, added a spot in modInfo for a Discord link, changelog link. Also added a separate mod version from the TMT version in VERSION.
    • Tree structure is based on layer data, no index.html editing is needed.
    • Tmp does not need to be manually updated.
    • You don't have to have the same amount of upgrades in every row (and challs and buyables)
    • "unlocked" is optional for all Big Components (defaults to true).
    • All displays will update correctly.
    • Changelog is no longer in index.html at all.
    • Generation of Points now happens in the main game loop
    • Changed the reset functions to make keeping things easier
    • Renamed many things to increase readability (see the list in the link below)
    • Improved documentation based on feedback

    v1.3.5: ​

    • Completely automated convertToDecimal, now you never have to worry about it again.
    • Branches can be defined without a color id. But they can also use hex values for color ids!
    • Created a tutorial for getting started with TMT and Github.
    • Page title is now automatically taken from mod name.

    v1.3.4 - 10/8/20 ​

    • Added "midsection" feature to add things to a tab's layout while still keeping the standard layout.
    • Fix for being able to buy more buyables than you should.

    v1.3.3 - 10/7/20 ​

    • Fix for the "order of operations" issue in temp.

    v1.3.1 - 10/7/20 ​

    • Added custom CSS and tooltips for Layer Nodes.
    • Added custom CSS for upgrades, buyables, milestones, and challenges, both individually and layer-wide.
    • You can now use HTML in most display text!
    • You can now make milestones unlockable and not display immediately.
    • Fixed importing saves, and issue with upgrades not appearing, and probably more.
    • Optional "name" layer feature, used in confirmation messages.

    v1.3: Tabception... ception! - 10/7/20 ​

    • Added subtabs! And also a Micro-tab component to let you make smaller subtab-esque areas anywhere.
    • Added a "custom" prestige formula type, and a number of features to support it.
    • Added points/sec display (can be disabled).
    • Added h-line, v-line and image-display components, plus components for individual upgrades, challenges, and milestones.
    • Added upgEffect, buyableEffect, and challEffect functions.
    • Added "hide completed challenges" setting.
    • Moved old changelogs to a separate place.
    • Fixed hasMilestone and incr_order.
    • Static layers now show the currency amount needed for the next one if you can buy max.

    v1.2.4 - 10/4/20 ​

    • Layers are now highlighted if you can buy an upgrade, and a new feature, shouldNotify, lets you make it highlight other ways.
    • Fixed bugs with hasUpg, hasChall, hasMilestone, and inChallenge.
    • Changed the sample code to use the above functions for convenience.

    v1.2.3 - 10/3/20 ​

    • Added a row component, which displays a list of objects in a row.
    • Added a column component, which displays a list of objects in a column (useful within a row).
    • Changed blanks to have a customizable width and height.

    v1.2: This Changes Everything! - 10/3/20 ​

    • Many layer features can now be static values or functions. (This made some formats change, which will break old things)
    • You can now use the "this" keyword, to make code easier to transfer when making new layers.
    • Also added "this.layer", which is the current layer's name, and works on existing subfeatures (e.g. individual upgrades) as well! Subfeatures also have "this.id".
    • Fixed a big save issue. If you use a unique mod id, your save will never conflict with other mods.
    • Added a configurable offline time limit in modinfo at the top of index.html. (default 1 hour)
    • Added a few minor features, and updated the docs with new information.

    v1.1.1: ​

    • You can define hotkeys directly from layer config.

    v1.1: Enhanced Edition ​

    • Added "Buyables", which can function like Space Buildings or Enhancers.
    • Custom CSS can now be used on any component! Make the third argument an object with CSS parameters.
    • Lots of minor good things.

    v1.0: ​

    • First release.
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/docs/!general-info.html b/public/lit/docs/!general-info.html index 391c581f..0c0efe14 100644 --- a/public/lit/docs/!general-info.html +++ b/public/lit/docs/!general-info.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
    The Paper Pilot

    Appearance

    The-Modding-Tree ​

    The main way to add content is through creating layers. You can either add a layer directly in the layers object in layerSupport.js, or declare it in another file and register it by calling addLayer(layername, layerdata). There is an example layer registration in layers.js showing the recommended method. It is just an example and can be freely deleted. You can also use it as a reference or a base for your own layers.

    The first thing you need to do is fill out the modInfo object at the top of mod.js to set your mod's name, ID (a string), and other information. A unique modId will prevent your mod's saves from conflicting with other mods. Note that changing this after people have started playing will reset their saves.

    Most of the time, you won't need to dive deep into the code to create things, but you still can if you really want to, for example to add new Vue components in v.js.

    The Modding Tree uses break_eternity.js to store large values. This means that many numbers are Decimal objects, and must be treated differently. For example, you have to use new Decimal(x) to create a Decimal value instead of a plain number, and perform operations on them by calling functions. e.g, instead of x = x + y, use x = x.add(y). Keep in mind this also applies to comparison operators, which should be replaced with calling the .gt, .gte, .lt, .lte, .eq, and .neq functions. See the break_eternity.js docs for more details on working with Decimal values.

    Almost all values can be either a constant value, or a dynamic value. Dynamic values are defined by putting a function that returns what the value should be at any given time.

    All display text can use basic HTML elements (But you can't use most Vue features there).

    While reading this documentation, the following key will be used when describing features:

    • No label: This is required and the game may crash if it isn't included.
    • sometimes required: This is may be required, depending on other things in the layer.
    • optional: You can leave this out if you don't intend to use that feature for the layer.
    • assigned automagically: This value will be set automatically and override any value you set.
    • deprecated: This feature is not recommended to be used anymore, and may be removed in future versions of TMT.

    Table of Contents ​

    General ​

    • Getting Started: Getting your own copy of the code set up with Github Desktop.
    • Main mod info: How to set up general things for your mod in mod.js.
    • Basic layer breakdown: Breaking down the components of a layer with minimal features.
    • Layer features: Explanations of all of the different properties that you can give a layer.
    • Custom Tab Layouts: An optional way to give your tabs a different layout. You can even create entirely new components to use.
    • Custom game layouts: You can get rid of the tree tab, add buttons and other things to the tree, or even customize the tab's layout like a layer tab.
    • Updating TMT: Using Github Desktop to update your mod's version of TMT.

    Common components ​

    • Upgrades: How to create upgrades for a layer.
    • Milestones: How to create milestones for a layer.
    • Buyables: Create rebuyable upgrades for your layer (with the option to make them respec-able). Can be used to make Enhancers or Space Buildings.
    • Clickables: A more generalized variant of buyables, for any kind of thing that is sometimes clickable. Between these and Buyables, you can do just about anything.

    Other components and features ​

    • Challenges: How to create challenges for a layer.
    • Bars: Display some information as a progress bar, gauge, or similar. They are highly customizable, and can be horizontal and vertical as well.
    • Subtabs and Microtabs: Create subtabs for your tabs, as well as "microtab" components that you can put inside the tabs. You can even use them to embed a layer inside another layer!
    • Achievements: How to create achievements for a layer (or for the whole game).
    • Infoboxes: Boxes containing text that can be shown or hidden.
    • Trees: Make your own trees. You can make non-layer button nodes too!
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +
    The Paper Pilot

    Appearance

    The-Modding-Tree ​

    The main way to add content is through creating layers. You can either add a layer directly in the layers object in layerSupport.js, or declare it in another file and register it by calling addLayer(layername, layerdata). There is an example layer registration in layers.js showing the recommended method. It is just an example and can be freely deleted. You can also use it as a reference or a base for your own layers.

    The first thing you need to do is fill out the modInfo object at the top of mod.js to set your mod's name, ID (a string), and other information. A unique modId will prevent your mod's saves from conflicting with other mods. Note that changing this after people have started playing will reset their saves.

    Most of the time, you won't need to dive deep into the code to create things, but you still can if you really want to, for example to add new Vue components in v.js.

    The Modding Tree uses break_eternity.js to store large values. This means that many numbers are Decimal objects, and must be treated differently. For example, you have to use new Decimal(x) to create a Decimal value instead of a plain number, and perform operations on them by calling functions. e.g, instead of x = x + y, use x = x.add(y). Keep in mind this also applies to comparison operators, which should be replaced with calling the .gt, .gte, .lt, .lte, .eq, and .neq functions. See the break_eternity.js docs for more details on working with Decimal values.

    Almost all values can be either a constant value, or a dynamic value. Dynamic values are defined by putting a function that returns what the value should be at any given time.

    All display text can use basic HTML elements (But you can't use most Vue features there).

    While reading this documentation, the following key will be used when describing features:

    • No label: This is required and the game may crash if it isn't included.
    • sometimes required: This is may be required, depending on other things in the layer.
    • optional: You can leave this out if you don't intend to use that feature for the layer.
    • assigned automagically: This value will be set automatically and override any value you set.
    • deprecated: This feature is not recommended to be used anymore, and may be removed in future versions of TMT.

    Table of Contents ​

    General ​

    • Getting Started: Getting your own copy of the code set up with Github Desktop.
    • Main mod info: How to set up general things for your mod in mod.js.
    • Basic layer breakdown: Breaking down the components of a layer with minimal features.
    • Layer features: Explanations of all of the different properties that you can give a layer.
    • Custom Tab Layouts: An optional way to give your tabs a different layout. You can even create entirely new components to use.
    • Custom game layouts: You can get rid of the tree tab, add buttons and other things to the tree, or even customize the tab's layout like a layer tab.
    • Updating TMT: Using Github Desktop to update your mod's version of TMT.

    Common components ​

    • Upgrades: How to create upgrades for a layer.
    • Milestones: How to create milestones for a layer.
    • Buyables: Create rebuyable upgrades for your layer (with the option to make them respec-able). Can be used to make Enhancers or Space Buildings.
    • Clickables: A more generalized variant of buyables, for any kind of thing that is sometimes clickable. Between these and Buyables, you can do just about anything.

    Other components and features ​

    • Challenges: How to create challenges for a layer.
    • Bars: Display some information as a progress bar, gauge, or similar. They are highly customizable, and can be horizontal and vertical as well.
    • Subtabs and Microtabs: Create subtabs for your tabs, as well as "microtab" components that you can put inside the tabs. You can even use them to embed a layer inside another layer!
    • Achievements: How to create achievements for a layer (or for the whole game).
    • Infoboxes: Boxes containing text that can be shown or hidden.
    • Trees: Make your own trees. You can make non-layer button nodes too!
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/docs/achievements.html b/public/lit/docs/achievements.html index d8149957..d4f2af42 100644 --- a/public/lit/docs/achievements.html +++ b/public/lit/docs/achievements.html @@ -8,11 +8,7 @@ - - - - - + @@ -33,8 +29,8 @@ more features }, etc -}

    Each achievement should have an id where the first digit is the row and the second digit is the column.

    Individual achievement can have these features:

    • name: optional. displayed at the top of the achievement. The only visible text. It can also be a function that returns updating text. Can use basic HTML.

    • done(): A function returning a boolean to determine if the achievement should be awarded.

    • tooltip: Default tooltip for the achievement, appears when it is hovered over. Should convey the goal and any reward for completing the achievement. It can also be a function that returns updating text. Can use basic HTML. Setting this to "" disables the tooltip.

    • effect(): optional. A function that calculates and returns the current values of any bonuses from the achievement. Can return a value or an object containing multiple values.

    • unlocked(): optional. A function returning a bool to determine if the achievement is visible or not. Default is unlocked.

    • onComplete() - optional. this function will be called when the achievement is completed.

    • image: optional, puts the image from the given URL (relative or absolute) in the achievement

    • style: optional. Applies CSS to this achievement, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • textStyle: optional. Applies CSS to the text, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the achievement was stored under, for convenient access. The achievement in the example's id is 11.

    • goalTooltip: optional, deprecated. Appears when the achievement is hovered over and locked, overrides the basic tooltip. This is to display the goal (or a hint). It can also be a function that returns updating text. Can use basic HTML.

    • doneTooltip: optional, deprecated. Appears when the achievement is hovered over and completed, overrides the basic tooltip. This can display what the player achieved (the goal), and the rewards, if any. It can also be a function that returns updating text. Can use basic HTML.

    Disable achievement popups by adding achievementsPopups: false to the layer.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Each achievement should have an id where the first digit is the row and the second digit is the column.

    Individual achievement can have these features:

    • name: optional. displayed at the top of the achievement. The only visible text. It can also be a function that returns updating text. Can use basic HTML.

    • done(): A function returning a boolean to determine if the achievement should be awarded.

    • tooltip: Default tooltip for the achievement, appears when it is hovered over. Should convey the goal and any reward for completing the achievement. It can also be a function that returns updating text. Can use basic HTML. Setting this to "" disables the tooltip.

    • effect(): optional. A function that calculates and returns the current values of any bonuses from the achievement. Can return a value or an object containing multiple values.

    • unlocked(): optional. A function returning a bool to determine if the achievement is visible or not. Default is unlocked.

    • onComplete() - optional. this function will be called when the achievement is completed.

    • image: optional, puts the image from the given URL (relative or absolute) in the achievement

    • style: optional. Applies CSS to this achievement, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • textStyle: optional. Applies CSS to the text, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the achievement was stored under, for convenient access. The achievement in the example's id is 11.

    • goalTooltip: optional, deprecated. Appears when the achievement is hovered over and locked, overrides the basic tooltip. This is to display the goal (or a hint). It can also be a function that returns updating text. Can use basic HTML.

    • doneTooltip: optional, deprecated. Appears when the achievement is hovered over and completed, overrides the basic tooltip. This can display what the player achieved (the goal), and the rewards, if any. It can also be a function that returns updating text. Can use basic HTML.

    Disable achievement popups by adding achievementsPopups: false to the layer.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/docs/bars.html b/public/lit/docs/bars.html index 129f7a25..17c3a524 100644 --- a/public/lit/docs/bars.html +++ b/public/lit/docs/bars.html @@ -8,11 +8,7 @@ - - - - - + @@ -34,8 +30,8 @@ etc }, etc -}

    Features:

    • direction: UP, DOWN, LEFT, or RIGHT (not strings). Determines the direction that the bar is filled as it progresses. RIGHT means from left to right.

    • width, height: The size in pixels of the bar, but as numbers (no "px" at the end).

    • progress(): A function that returns the portion of the bar that is filled, from "empty" at 0 to "full" at 1, updating automatically. (Nothing bad happens if the value goes out of these bounds, and it can be a number or Decimal)

    • display(): optional. A function that returns text to be displayed on top of the bar, can use HTML.

    • unlocked(): optional. A function returning a bool to determine if the bar is visible or not. Default is unlocked.

    • baseStyle, fillStyle, borderStyle, textStyle: Optional, Apply CSS to the unfilled portion, filled portion, border, and display text on the bar, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the bar was stored under, for convenient access. The bar in the example's id is "bigBar".

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Features:

    • direction: UP, DOWN, LEFT, or RIGHT (not strings). Determines the direction that the bar is filled as it progresses. RIGHT means from left to right.

    • width, height: The size in pixels of the bar, but as numbers (no "px" at the end).

    • progress(): A function that returns the portion of the bar that is filled, from "empty" at 0 to "full" at 1, updating automatically. (Nothing bad happens if the value goes out of these bounds, and it can be a number or Decimal)

    • display(): optional. A function that returns text to be displayed on top of the bar, can use HTML.

    • unlocked(): optional. A function returning a bool to determine if the bar is visible or not. Default is unlocked.

    • baseStyle, fillStyle, borderStyle, textStyle: Optional, Apply CSS to the unfilled portion, filled portion, border, and display text on the bar, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the bar was stored under, for convenient access. The bar in the example's id is "bigBar".

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/docs/basic-layer-breakdown.html b/public/lit/docs/basic-layer-breakdown.html index c4686507..12f3b52f 100644 --- a/public/lit/docs/basic-layer-breakdown.html +++ b/public/lit/docs/basic-layer-breakdown.html @@ -8,11 +8,7 @@ - - - - - + @@ -52,8 +48,8 @@ }, layerShown() { return true } // Returns a bool for if this layer's node should be visible in the tree. -})
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +})
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/docs/buyables.html b/public/lit/docs/buyables.html index 30068eb8..24c35aed 100644 --- a/public/lit/docs/buyables.html +++ b/public/lit/docs/buyables.html @@ -8,11 +8,7 @@ - - - - - + @@ -39,8 +35,8 @@ etc }, etc -}

    Features:

    • title: optional. displayed at the top in a larger font. It can also be a function that returns updating text.

    • cost(): cost for buying the next buyable. Can have an optional argument "x" to calculate the cost of the x+1th object, but needs to use "current amount" as a default value for x. (x is a Decimal). Can return an object if there are multiple currencies.

    • effect(): optional. A function that calculates and returns the current values of bonuses of this buyable. Can return a value or an object containing multiple values.

    • display(): A function returning everything that should be displayed on the buyable after the title, likely including the description, amount bought, cost, and current effect. Can use basic HTML.

    • unlocked(): optional. A function returning a bool to determine if the buyable is visible or not. Default is unlocked.

    • canAfford(): A function returning a bool to determine if you can buy one of the buyables.

    • buy(): A function that implements buying one of the buyable, including spending the currency.

    • buyMax(): optional. A function that implements buying as many of the buyable as possible.

    • style: optional. Applies CSS to this buyable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the buyable was stored under, for convenient access. The buyable in the example's id is 11.

    Sell One/Sell All:

    Including a sellOne or sellAll function will cause an additional button to appear beneath the buyable. They are functionally identical, but "sell one" appears above "sell all". You can also use them for other things.

    • sellOne/sellAll(): optional. Called when the button is pressed. The standard use would be to decrease/reset the amount of the buyable, and possibly return some currency to the player.

    • canSellOne/canSellAll(): optional. booleans determining whether or not to show the buttons. If "canSellOne/All" is absent but "sellOne/All" is present, the appropriate button will always show.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Features:

    • title: optional. displayed at the top in a larger font. It can also be a function that returns updating text.

    • cost(): cost for buying the next buyable. Can have an optional argument "x" to calculate the cost of the x+1th object, but needs to use "current amount" as a default value for x. (x is a Decimal). Can return an object if there are multiple currencies.

    • effect(): optional. A function that calculates and returns the current values of bonuses of this buyable. Can return a value or an object containing multiple values.

    • display(): A function returning everything that should be displayed on the buyable after the title, likely including the description, amount bought, cost, and current effect. Can use basic HTML.

    • unlocked(): optional. A function returning a bool to determine if the buyable is visible or not. Default is unlocked.

    • canAfford(): A function returning a bool to determine if you can buy one of the buyables.

    • buy(): A function that implements buying one of the buyable, including spending the currency.

    • buyMax(): optional. A function that implements buying as many of the buyable as possible.

    • style: optional. Applies CSS to this buyable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the buyable was stored under, for convenient access. The buyable in the example's id is 11.

    Sell One/Sell All:

    Including a sellOne or sellAll function will cause an additional button to appear beneath the buyable. They are functionally identical, but "sell one" appears above "sell all". You can also use them for other things.

    • sellOne/sellAll(): optional. Called when the button is pressed. The standard use would be to decrease/reset the amount of the buyable, and possibly return some currency to the player.

    • canSellOne/canSellAll(): optional. booleans determining whether or not to show the buttons. If "canSellOne/All" is absent but "sellOne/All" is present, the appropriate button will always show.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/docs/challenges.html b/public/lit/docs/challenges.html index dd6aba97..75eaa83a 100644 --- a/public/lit/docs/challenges.html +++ b/public/lit/docs/challenges.html @@ -8,11 +8,7 @@ - - - - - + @@ -35,8 +31,8 @@ etc }, etc -}

    Each challenge should have an id where the first digit is the row and the second digit is the column.

    Individual Challenges can have these features:

    • name: Name of the challenge, can be a string or a function. Can use basic HTML.

    • challengeDescription: A description of what makes the challenge a challenge. You will need to implement these elsewhere. It can also be a function that returns updating text. Can use basic HTML.

    • goalDescription: A description of the win condition for the challenge. It can also be a function that returns updating text. Can use basic HTML. (Optional if using the old goal system)

    • canComplete(): A function that returns true if you meet the win condition for the challenge. Returning a number will allow bulk completing the challenge. (Optional if using the old goal system)

    • rewardDescription: A description of the reward's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

    • rewardEffect(): optional. A function that calculates and returns the current values of any bonuses from the reward. Can return a value or an object containing multiple values. Can use basic HTML.

    • rewardDisplay(): optional. A function that returns a display of the current effects of the reward with formatting. Default behavior is to just display the a number appropriately formatted.

    • fullDisplay(): OVERRIDE. Overrides the other displays and descriptions, and lets you set the full text for the challenge. Can use basic HTML.

    • unlocked(): optional. A function returning a bool to determine if the challenge is visible or not. Default is unlocked.

    • onComplete() - optional. this function will be called when the challenge is completed when previously incomplete.

    • countsAs: optional. If a challenge combines the effects of other challenges in this layer, you can use this. An array of challenge ids. The player is effectively in all of those challenges when in the current one.

    • completionLimit: optional. the amount of times you can complete this challenge. Default is 1 completion.

    • style: optional. Applies CSS to this challenge, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

    • id: assigned automagically. It's the "key" which the challenge was stored under, for convenient access. The challenge in the example's id is 11.

    The old goal system uses these features:

    • goal: deprecated, A Decimal for the amount of currency required to beat the challenge. By default, the goal is in basic Points. The goal can also be a function if its value changes.

    • currencyDisplayName: deprecated. the name to display for the currency for the goal

    • currencyInternalName: deprecated. the internal name for that currency

    • currencyLayer: deprecated. the internal name of the layer that currency is stored in. If it's not in a layer, omit. If it's not stored directly in a layer, instead use the next feature.

    • currencyLocation(): deprecated. if your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Each challenge should have an id where the first digit is the row and the second digit is the column.

    Individual Challenges can have these features:

    • name: Name of the challenge, can be a string or a function. Can use basic HTML.

    • challengeDescription: A description of what makes the challenge a challenge. You will need to implement these elsewhere. It can also be a function that returns updating text. Can use basic HTML.

    • goalDescription: A description of the win condition for the challenge. It can also be a function that returns updating text. Can use basic HTML. (Optional if using the old goal system)

    • canComplete(): A function that returns true if you meet the win condition for the challenge. Returning a number will allow bulk completing the challenge. (Optional if using the old goal system)

    • rewardDescription: A description of the reward's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

    • rewardEffect(): optional. A function that calculates and returns the current values of any bonuses from the reward. Can return a value or an object containing multiple values. Can use basic HTML.

    • rewardDisplay(): optional. A function that returns a display of the current effects of the reward with formatting. Default behavior is to just display the a number appropriately formatted.

    • fullDisplay(): OVERRIDE. Overrides the other displays and descriptions, and lets you set the full text for the challenge. Can use basic HTML.

    • unlocked(): optional. A function returning a bool to determine if the challenge is visible or not. Default is unlocked.

    • onComplete() - optional. this function will be called when the challenge is completed when previously incomplete.

    • countsAs: optional. If a challenge combines the effects of other challenges in this layer, you can use this. An array of challenge ids. The player is effectively in all of those challenges when in the current one.

    • completionLimit: optional. the amount of times you can complete this challenge. Default is 1 completion.

    • style: optional. Applies CSS to this challenge, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

    • id: assigned automagically. It's the "key" which the challenge was stored under, for convenient access. The challenge in the example's id is 11.

    The old goal system uses these features:

    • goal: deprecated, A Decimal for the amount of currency required to beat the challenge. By default, the goal is in basic Points. The goal can also be a function if its value changes.

    • currencyDisplayName: deprecated. the name to display for the currency for the goal

    • currencyInternalName: deprecated. the internal name for that currency

    • currencyLayer: deprecated. the internal name of the layer that currency is stored in. If it's not in a layer, omit. If it's not stored directly in a layer, instead use the next feature.

    • currencyLocation(): deprecated. if your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/docs/clickables.html b/public/lit/docs/clickables.html index 44468caf..839560d4 100644 --- a/public/lit/docs/clickables.html +++ b/public/lit/docs/clickables.html @@ -8,11 +8,7 @@ - - - - - + @@ -33,8 +29,8 @@ etc } etc -}

    Features:

    • title: optional. displayed at the top in a larger font. It can also be a function that returns updating text.

    • effect(): optional. A function that calculates and returns the current values of bonuses of this clickable. Can return a value or an object containing multiple values.

    • display(): A function returning everything that should be displayed on the clickable after the title, likely changing based on its state. Can use basic HTML.

    • unlocked(): optional. A function returning a bool to determine if the clickable is visible or not. Default is unlocked.

    • canClick(): A function returning a bool to determine if you can click the clickable.

    • onClick(): A function that implements clicking one of the clickable.

    • style: optional. Applies CSS to this clickable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the clickable was stored under, for convenient access. The clickable in the example's id is 11.

    You can also use these features on the clickables object to add a button above all the clickables, for implementing a respec button or similar.

    • masterButtonPress(): optional. If present, an additional button will appear above the clickables. Pressing it will call this function.

    • masterButtonText: optional. Text to display on the Master Button.

    • showMasterButton(): optional. A function determining whether or not to show the button. Defaults to true if absent.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Features:

    • title: optional. displayed at the top in a larger font. It can also be a function that returns updating text.

    • effect(): optional. A function that calculates and returns the current values of bonuses of this clickable. Can return a value or an object containing multiple values.

    • display(): A function returning everything that should be displayed on the clickable after the title, likely changing based on its state. Can use basic HTML.

    • unlocked(): optional. A function returning a bool to determine if the clickable is visible or not. Default is unlocked.

    • canClick(): A function returning a bool to determine if you can click the clickable.

    • onClick(): A function that implements clicking one of the clickable.

    • style: optional. Applies CSS to this clickable, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the clickable was stored under, for convenient access. The clickable in the example's id is 11.

    You can also use these features on the clickables object to add a button above all the clickables, for implementing a respec button or similar.

    • masterButtonPress(): optional. If present, an additional button will appear above the clickables. Pressing it will call this function.

    • masterButtonText: optional. Text to display on the Master Button.

    • showMasterButton(): optional. A function determining whether or not to show the button. Defaults to true if absent.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/docs/custom-tab-layouts.html b/public/lit/docs/custom-tab-layouts.html index d8069b20..20ccf810 100644 --- a/public/lit/docs/custom-tab-layouts.html +++ b/public/lit/docs/custom-tab-layouts.html @@ -8,11 +8,7 @@ - - - - - + @@ -38,8 +34,8 @@ "blank", "blank", "upgrades" -]

    It is a list of components, which can be either just a name, or an array with arguments. If it's an array, the first item is the name of the component, the second is the data passed into it, and the third (optional) applies a CSS style to it with a "CSS object", where the keys are CSS attributes.

    These are the existing components, but you can create more in components.js:

    • display-text: Displays some text (can use basic HTML). The argument is the text to display. It can also be a function that returns updating text.

    • raw-html: Displays some basic HTML, can also be a function.

    • blank: Adds empty space. The default dimensions are 8px x 17px. The argument changes the dimensions. If it's a single value (e.g. "20px"), that determines the height. If you have a pair of arguments, the first is width and the second is height.

    • row: Display a list of components horizontally. The argument is an array of components in the tab layout format.

    • column: Display a list of components vertically. The argument is an array of components in the tab layout format. This is useful to display columns within a row.

    • main-display: The text that displays the main currency for the layer and its effects.

    • resource-display: The text that displays the currency that this layer is based on, as well as the best and/or total values for this layer's prestige currency (if they are put in startData for this layer).

    • prestige-button: The argument is a string that the prestige button should say before the amount of currency you will gain. It can also be a function that returns updating text.

    • upgrades: The layer's upgrades. The argument is optional, and is a the list of rows this component should include, if it doesn't have all of them.

    • milestones, challenges, achievements: Display the upgrades, milestones, and challenges for a layer, as appropriate.

    • buyables, clickables: Display all of the buyables/clickables for this layer, as appropriate. The argument is optional and is the size of the boxes in pixels.

    • microtabs: Display a set of subtabs for an area. The argument is the name of the set of microtabs in the "microtabs" feature.

    • bar: Display a bar. The argument is the id of the bar to display.

    • infobox: Display an infobox. The argument is the id of the infobox to display.

    • tree: Displays a tree. The argument is an array of arrays containing the names of the nodes in the tree (first by row, then by column) See here for more information on tree layouts and nodes!

    • toggle: A toggle button that toggles a bool value. The data is a pair that identifies what bool to toggle, e.g. [layer, id]

    The rest of the components are sub-components. They can be used just like other components, but are typically part of another component.

    • upgrade, milestone, challenge, buyable, clickable, achievement: An individual upgrade, challenge, etc. The argument is the id. This can be used if you want to have upgrades split up across multiple subtabs, for example.

    • respec-button, master-button: The respec and master buttons for buyables and clickables, respectively.

    • sell-one, sell-all: The "sell one" and "sell all" for buyables, respectively. The argument is the id of the buyable.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +]

    It is a list of components, which can be either just a name, or an array with arguments. If it's an array, the first item is the name of the component, the second is the data passed into it, and the third (optional) applies a CSS style to it with a "CSS object", where the keys are CSS attributes.

    These are the existing components, but you can create more in components.js:

    • display-text: Displays some text (can use basic HTML). The argument is the text to display. It can also be a function that returns updating text.

    • raw-html: Displays some basic HTML, can also be a function.

    • blank: Adds empty space. The default dimensions are 8px x 17px. The argument changes the dimensions. If it's a single value (e.g. "20px"), that determines the height. If you have a pair of arguments, the first is width and the second is height.

    • row: Display a list of components horizontally. The argument is an array of components in the tab layout format.

    • column: Display a list of components vertically. The argument is an array of components in the tab layout format. This is useful to display columns within a row.

    • main-display: The text that displays the main currency for the layer and its effects.

    • resource-display: The text that displays the currency that this layer is based on, as well as the best and/or total values for this layer's prestige currency (if they are put in startData for this layer).

    • prestige-button: The argument is a string that the prestige button should say before the amount of currency you will gain. It can also be a function that returns updating text.

    • upgrades: The layer's upgrades. The argument is optional, and is a the list of rows this component should include, if it doesn't have all of them.

    • milestones, challenges, achievements: Display the upgrades, milestones, and challenges for a layer, as appropriate.

    • buyables, clickables: Display all of the buyables/clickables for this layer, as appropriate. The argument is optional and is the size of the boxes in pixels.

    • microtabs: Display a set of subtabs for an area. The argument is the name of the set of microtabs in the "microtabs" feature.

    • bar: Display a bar. The argument is the id of the bar to display.

    • infobox: Display an infobox. The argument is the id of the infobox to display.

    • tree: Displays a tree. The argument is an array of arrays containing the names of the nodes in the tree (first by row, then by column) See here for more information on tree layouts and nodes!

    • toggle: A toggle button that toggles a bool value. The data is a pair that identifies what bool to toggle, e.g. [layer, id]

    The rest of the components are sub-components. They can be used just like other components, but are typically part of another component.

    • upgrade, milestone, challenge, buyable, clickable, achievement: An individual upgrade, challenge, etc. The argument is the id. This can be used if you want to have upgrades split up across multiple subtabs, for example.

    • respec-button, master-button: The respec and master buttons for buyables and clickables, respectively.

    • sell-one, sell-all: The "sell one" and "sell all" for buyables, respectively. The argument is the id of the buyable.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/docs/getting-started.html b/public/lit/docs/getting-started.html index 2ae80abf..82553c96 100644 --- a/public/lit/docs/getting-started.html +++ b/public/lit/docs/getting-started.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
    The Paper Pilot

    Appearance

    Getting started ​

    Welcome to The Modding Tree!

    Using the Modding Tree, at its simplest level, just requires getting a copy of it onto your computer. However, if you do it the right way, it will help in many ways.

    Don't let the word "Github" scare you away. It's actually much easier to use than most people think, especially because most people use it the hard way. The key is Github Desktop, which lets you do everything you need to, without even touching the command line.

    The benefits of using Github:

    • It makes it much, much easier to update The Modding Tree.
    • You can share your work without any extra effort using githack, or with a bit more effort, set up a github.io site.
    • It lets you undo changes to your code, and to have multiple versions of it.
    • It lets you collaborate with other people, if you want to.

    Getting set up with Github Desktop, Visual Studio Code, and The Modding Tree: ​

    1. Install Github Desktop and Visual Studio Code.

    2. Make a Github account. You can handle this on your own.

    3. Log in on your browser, and go back to The Modding Tree page. At the top right, there should be a button that says "fork". Click on it, and then on your username. You now have your own fork, or copy, of The Modding Tree.

    4. Open Github Desktop and log in. Ignore everything else and choose "clone a repository". A "repository" is basically a "Github project", like The Modding Tree. "Cloning" is downloading a copy of the repository to your computer.

    5. Look for The Modding Tree in the list of repositiories (it should be the only one) and click "clone".

    6. Select that you're using it for your own purposes, and click continue. It will download the files and handle everything.

    Using your repository ​

    1. Click on "show in explorer/finder" to the right, and then open the index.html file in the folder. The page should open up on your browser. This will let you view and test your project locally!

    2. To edit your project, click "open in VSCode" in Github Desktop.

    3. Open mod.js in VSCode, and look at the top part where it has a "modInfo" object. Fill in your mod's name to whatever you want, and change the id as well. (It can be any string value, and it's used to determine where the savefile is. Make it something that's probably unique, and don't change it again later or else it'll effectively wipe existing saves)

    4. Save mod.js, and then reload index.html in your browser. The title on the tab, as well as on the info page, will now be updated! You can reload the page every time you change the code to test it quickly and easily.

    5. Go back to Github Desktop. It's time to save your changes into the git system by making a "commit". This basically saves your work and creates a snapshot of what your code looks like at this moment, allowing you to look back at it later.

    6. At the bottom right corner, add a summary of your changes, and then click "commit to master".

    7. Finally, at the top middle, click "push origin" to push your changes out onto the online repository.

    8. You can view your project on line, or share it with others, by going to https://raw.githack.com/[YOUR-GITHUB-USERNAME]/The-Modding-Tree/master/index.html

    And now, you have successfully used Github! You can look at the documentation to see how The Modding Tree's system works and to make your mod a reality.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +
    The Paper Pilot

    Appearance

    Getting started ​

    Welcome to The Modding Tree!

    Using the Modding Tree, at its simplest level, just requires getting a copy of it onto your computer. However, if you do it the right way, it will help in many ways.

    Don't let the word "Github" scare you away. It's actually much easier to use than most people think, especially because most people use it the hard way. The key is Github Desktop, which lets you do everything you need to, without even touching the command line.

    The benefits of using Github:

    • It makes it much, much easier to update The Modding Tree.
    • You can share your work without any extra effort using githack, or with a bit more effort, set up a github.io site.
    • It lets you undo changes to your code, and to have multiple versions of it.
    • It lets you collaborate with other people, if you want to.

    Getting set up with Github Desktop, Visual Studio Code, and The Modding Tree: ​

    1. Install Github Desktop and Visual Studio Code.

    2. Make a Github account. You can handle this on your own.

    3. Log in on your browser, and go back to The Modding Tree page. At the top right, there should be a button that says "fork". Click on it, and then on your username. You now have your own fork, or copy, of The Modding Tree.

    4. Open Github Desktop and log in. Ignore everything else and choose "clone a repository". A "repository" is basically a "Github project", like The Modding Tree. "Cloning" is downloading a copy of the repository to your computer.

    5. Look for The Modding Tree in the list of repositiories (it should be the only one) and click "clone".

    6. Select that you're using it for your own purposes, and click continue. It will download the files and handle everything.

    Using your repository ​

    1. Click on "show in explorer/finder" to the right, and then open the index.html file in the folder. The page should open up on your browser. This will let you view and test your project locally!

    2. To edit your project, click "open in VSCode" in Github Desktop.

    3. Open mod.js in VSCode, and look at the top part where it has a "modInfo" object. Fill in your mod's name to whatever you want, and change the id as well. (It can be any string value, and it's used to determine where the savefile is. Make it something that's probably unique, and don't change it again later or else it'll effectively wipe existing saves)

    4. Save mod.js, and then reload index.html in your browser. The title on the tab, as well as on the info page, will now be updated! You can reload the page every time you change the code to test it quickly and easily.

    5. Go back to Github Desktop. It's time to save your changes into the git system by making a "commit". This basically saves your work and creates a snapshot of what your code looks like at this moment, allowing you to look back at it later.

    6. At the bottom right corner, add a summary of your changes, and then click "commit to master".

    7. Finally, at the top middle, click "push origin" to push your changes out onto the online repository.

    8. You can view your project on line, or share it with others, by going to https://raw.githack.com/[YOUR-GITHUB-USERNAME]/The-Modding-Tree/master/index.html

    And now, you have successfully used Github! You can look at the documentation to see how The Modding Tree's system works and to make your mod a reality.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/docs/infoboxes.html b/public/lit/docs/infoboxes.html index 70bc0582..7de87598 100644 --- a/public/lit/docs/infoboxes.html +++ b/public/lit/docs/infoboxes.html @@ -8,11 +8,7 @@ - - - - - + @@ -32,8 +28,8 @@ etc }, etc -}

    Features:

    • title: The text displayed above the main box. Can be a function to be dynamic, and can use basic HTML.

    • body: The text displayed inside the box. Can be a function to be dynamic, and can use basic HTML.

    • style, titleStyle, bodyStyle: optional. Apply CSS to the infobox, or to the title button or body of the infobox, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • unlocked(): optional. A function returning a bool to determine if the infobox is visible or not. Default is unlocked.

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

    • id: assigned automagically. It's the "key" which the bar was stored under, for convenient access. The infobox in the example's id is "lore".

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Features:

    • title: The text displayed above the main box. Can be a function to be dynamic, and can use basic HTML.

    • body: The text displayed inside the box. Can be a function to be dynamic, and can use basic HTML.

    • style, titleStyle, bodyStyle: optional. Apply CSS to the infobox, or to the title button or body of the infobox, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • unlocked(): optional. A function returning a bool to determine if the infobox is visible or not. Default is unlocked.

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar

    • id: assigned automagically. It's the "key" which the bar was stored under, for convenient access. The infobox in the example's id is "lore".

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/docs/layer-features.html b/public/lit/docs/layer-features.html index 006c0189..f49f3916 100644 --- a/public/lit/docs/layer-features.html +++ b/public/lit/docs/layer-features.html @@ -8,11 +8,7 @@ - - - - - + @@ -34,8 +30,8 @@ ]

  • style: optional. a "CSS object" where the keys are CSS attributes, containing any CSS that should affect this layer's entire tab.

  • tabFormat: optional. use this if you want to add extra things to your tab or change the layout. See here for more info.

  • midsection: optional, an alternative to tabFormat, which is inserted in between Milestones and Buyables in the standard tab layout. (cannot do subtabs)

    • Big features (all optional) ​

    • upgrades: A grid of one-time purchases which can have unique upgrade conditions, currency costs, and bonuses. See here for more info.

    • milestones: A list of bonuses gained upon reaching certain thresholds of a resource. Often used for automation/QOL. See here for more info.

    • challenges: The player can enter challenges, which make the game harder. If they reach a goal and beat the challenge, they recieve a bonus. See here for more info.

    • buyables: Effectively upgrades that can be bought multiple times, and are optionally respeccable. Many uses. See here for more info.

    • clickables: Extremely versatile and generalized buttons which can only be clicked sometimes. See here for more info.

    • microtabs: An area that functions like a set of subtabs, with buttons at the top changing the content within. (Advanced) See here for more info.

    • bars: Display some information as a progress bar, gague, or similar. They are highly customizable, and can be vertical as well. See here for more info.

    • achievements: Kind of like milestones, but with a different display style and some other differences. Extra features are on the way at a later date! See here for more info.

    • infoboxes: Displays some text in a box that can be shown or hidden. See here for more info.

    • achievementPopups, milestonePopups: optional, If false, disables popup message when you get the achievement/milestone. True by default.

    Prestige formula features ​

    • type: optional. Determines which prestige formula you use. Defaults to "none".

      • "normal": The amount of currency you gain is independent of its current amount (like Prestige). The formula before bonuses is based on baseResource^exponent
      • "static": The cost is dependent on your total after reset. The formula before bonuses is based on base^(x^exponent)
      • "custom": You can define everything, from the calculations to the text on the button, yourself. (See more at the bottom)
      • "none": This layer does not prestige, and therefore does not need any of the other features in this section.

    • baseResource: The name of the resource that determines how much of the main currency you gain on reset.

    • baseAmount(): A function that gets the current value of the base resource.

    • requires: A Decimal, the amount of the base needed to gain 1 of the prestige currency. Also the amount required to unlock the layer. You can instead make this a function, to make it harder if another layer was unlocked first (based on unlockOrder).

    • exponent: Used as described above.

    • base: sometimes required. required for "static" layers, used as described above. If absent, defaults to 2. Must be greater than 1.

    • roundUpCost: optional. a bool, which is true if the resource cost needs to be rounded up. (use if the base resource is a "static" currency.)

    • gainMult(), gainExp(): optional. Functions that calculate the multiplier and exponent on resource gain from upgrades and boosts and such. Plug in any bonuses here.

    • softcap, softcapPower: optional. For normal layers, gain beyond [softcap] points is put to the [softcapPower]th power Default for softcap is e1e7, and for power is 0.5.

    • canBuyMax(): sometimes required. required for static layers, function used to determine if buying max is permitted.

    • onPrestige(gain): optional. A function that triggers when this layer prestiges, just before you gain the currency. Can be used to have secondary resource gain on prestige, or to recalculate things or whatnot.

    • resetDescription: optional. Use this to replace "Reset for " on the Prestige button with something else.

    • prestigeButtonText(): sometimes required. Use this to make the entirety of the text a Prestige button contains. Only required for custom layers, but usable by all types.

    • passiveGeneration(): optional, returns a regular number. You automatically generate your gain times this number every second (does nothing if absent) This is good for automating Normal layers.

    • autoPrestige(): optional, returns a boolean, if true, the layer will always automatically do a prestige if it can. This is good for automating Static layers.

    Tree/node features ​

    • symbol: optional. The text that appears on this layer's node. Default is the layer id with the first letter capitalized.

    • image: override. The url (local or global) of an image that goes on the node. (Overrides symbol)

    • position: optional. Determines the horizontal position of the layer in its row in a standard tree. By default, it uses the layer id, and layers are sorted in alphabetical order.

    • branches: optional. An array of layer/node ids. On a tree, a line will appear from this layer to all of the layers in the list. Alternatively, an entry in the array can be a 2-element array consisting of the layer id and a color value. The color value can either be a string with a hex color code, or a number from 1-3 (theme-affected colors).

    • nodeStyle: optional. A CSS object, where the keys are CSS attributes, which styles this layer's node on the tree.

    • tooltip() / tooltipLocked(): optional. Functions that return text, which is the tooltip for the node when the layer is unlocked or locked, respectively. By default the tooltips behave the same as in the original Prestige Tree. If the value is "", the tooltip will be disabled.

    Other features ​

    • doReset(resettingLayer): optional. Is triggered when a layer on a row greater than or equal to this one does a reset. The default behavior is to reset everything on the row, but only if it was triggered by a layer in a higher row. doReset is always called for side layers, but for these the default behavior is to reset nothing.

      If you want to keep things, determine what to keep based on resettingLayer, milestones, and such, then call layerDataReset(layer, keep), where layer is this layer, and keep is an array of the names of things to keep. It can include things like "points", "best", "total" (for this layer's prestige currency), "upgrades", any unique variables like "generatorPower", etc. If you want to only keep specific upgrades or something like that, save them in a separate variable, then call layerDataReset, and then set player[this.layer].upgrades to the saved upgrades.

    • update(diff): optional. This function is called every game tick. Use it for any passive resource production or time-based things. diff is the time since the last tick.

    • autoUpgrade: optional, a boolean value, if true, the game will attempt to buy this layer's upgrades every tick. Defaults to false.

    • automate(): optional. This function is called every game tick, after production. Use it to activate automation things that aren't otherwise supported.

    • resetsNothing: optional. Returns true if this layer shouldn't trigger any resets when you prestige.

    • increaseUnlockOrder: optional. An array of layer ids. When this layer is unlocked for the first time, the unlockOrder value for any not-yet-unlocked layers in this list increases. This can be used to make them harder to unlock.

    • shouldNotify: optional. A function to return true if this layer should be highlighted in the tree. The layer will automatically be highlighted if you can buy an upgrade whether you have this or not.

    • componentStyles: optional. An object that contains a set of functions returning CSS objects. Each of these will be applied to any components on the layer with the type of its id. Example:

    js
    componentStyles: {
     "challenge"() { return {'height': '200px'} },
     "prestige-button"() { return {'color': '#AA66AA'} }
-}

    Custom Prestige type ​

    (All of these can also be used by other prestige types)

    • getResetGain(): mostly for custom prestige type. Returns how many points you should get if you reset now. You can call getResetGain(this.layer, useType = "static") or similar to calculate what your gain would be under another prestige type (provided you have all of the required features in the layer).

    • getNextAt(canMax=false): mostly for custom prestige type. Returns how many of the base currency you need to get to the next point. canMax is an optional variable used with Static-ish layers to differentiate between if it's looking for the first point you can reset at, or the requirement for any gain at all (Supporting both is good). You can also call getNextAt(this.layer, canMax=false, useType = "static") or similar to calculate what your next at would be under another prestige type (provided you have all of the required features in the layer).

    • canReset(): mostly for custom prestige type. Return true only if you have the resources required to do a prestige here.

    • prestigeNotify(): mostly for custom prestige types, returns true if this layer should be subtly highlighted to indicate you can prestige for a meaningful gain.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Custom Prestige type ​

    (All of these can also be used by other prestige types)

    • getResetGain(): mostly for custom prestige type. Returns how many points you should get if you reset now. You can call getResetGain(this.layer, useType = "static") or similar to calculate what your gain would be under another prestige type (provided you have all of the required features in the layer).

    • getNextAt(canMax=false): mostly for custom prestige type. Returns how many of the base currency you need to get to the next point. canMax is an optional variable used with Static-ish layers to differentiate between if it's looking for the first point you can reset at, or the requirement for any gain at all (Supporting both is good). You can also call getNextAt(this.layer, canMax=false, useType = "static") or similar to calculate what your next at would be under another prestige type (provided you have all of the required features in the layer).

    • canReset(): mostly for custom prestige type. Return true only if you have the resources required to do a prestige here.

    • prestigeNotify(): mostly for custom prestige types, returns true if this layer should be subtly highlighted to indicate you can prestige for a meaningful gain.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/docs/main-mod-info.html b/public/lit/docs/main-mod-info.html index 39f33126..f865bd25 100644 --- a/public/lit/docs/main-mod-info.html +++ b/public/lit/docs/main-mod-info.html @@ -8,11 +8,7 @@ - - - - - + @@ -29,8 +25,8 @@ var doNotCallTheseFunctionsEveryTick = ["doReset", "buy", "onPurchase", "blowUpEverything"]

    • getStartPoints(): A function to determine the amount of points the player starts with after a reset. (returns a Decimal value)

    • canGenPoints(): A function returning a boolean for if points should be generated. Use this if you want an upgrade to unlock generating points.

    • getPointGen(): A function that calculates your points per second. Anything that affects your point gain should go into the calculation here.

    • addedPlayerData(): A function that returns any non-layer-related data that you want to be added to the save data and "player" object.

    js
    function addedPlayerData() { return {
 	weather: "Yes",
 	happiness: new Decimal(72),
-}}

    • displayThings: An array of functions used to display extra things at the top of the tree tab. Each function returns a string, which is a line to display (with basic HTML support). If a function returns nothing, nothing is displayed (and it doesn't take up a line).

    • isEndgame(): A function to determine if the player has reached the end of the game, at which point the "you win!" screen appears.

    Less important things beyond this point!

    • maxTickLength(): Returns the maximum tick length, in milliseconds. Only really useful if you have something that reduces over time, which long ticks mess up (usually a challenge).
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}}

    • displayThings: An array of functions used to display extra things at the top of the tree tab. Each function returns a string, which is a line to display (with basic HTML support). If a function returns nothing, nothing is displayed (and it doesn't take up a line).

    • isEndgame(): A function to determine if the player has reached the end of the game, at which point the "you win!" screen appears.

    Less important things beyond this point!

    • maxTickLength(): Returns the maximum tick length, in milliseconds. Only really useful if you have something that reduces over time, which long ticks mess up (usually a challenge).
    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/docs/milestones.html b/public/lit/docs/milestones.html index b2334eb4..2cf16c8f 100644 --- a/public/lit/docs/milestones.html +++ b/public/lit/docs/milestones.html @@ -8,11 +8,7 @@ - - - - - + @@ -32,8 +28,8 @@ done() { return player.w.points.gte(123) } } etc -}

    You can use hasMilestone(layer, id) to determine if the player has a given milestone

    Milestone features:

    • requirementDescription: A string describing the requirement for unlocking this milestone. Suggestion: Use a "total". It can also be a function that returns updating text. Can use basic HTML.

    • effectDescription: A string describing the reward for having the milestone. You will have to implement the reward elsewhere. It can also be a function that returns updating text. Can use basic HTML.

    • done(): A function returning a boolean to determine if the milestone should be awarded.

    • toggles: optional. Creates toggle buttons that appear on the milestone when it is unlocked. The toggles can toggle a given boolean value in a layer. It is defined as an array of paired items, one pair per toggle. The first is the internal name of the layer the value being toggled is stored in, and the second is the internal name of the variable to toggle. (e.g. [["b", "auto"], ["g", "auto"])

      Tip: Toggles are not de-set if the milestone becomes locked! In this case, you should also check if the player has the milestone.

    • style: optional. Applies CSS to this milestone, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • unlocked(): optional. A function returning a boolean to determine if the milestone should be shown. If absent, it is always shown.

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the milestone was stored under, for convenient access. The milestone in the example's id is 0.

    Disaable milestone popups by adding milestonePopups: false to the layer.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    You can use hasMilestone(layer, id) to determine if the player has a given milestone

    Milestone features:

    • requirementDescription: A string describing the requirement for unlocking this milestone. Suggestion: Use a "total". It can also be a function that returns updating text. Can use basic HTML.

    • effectDescription: A string describing the reward for having the milestone. You will have to implement the reward elsewhere. It can also be a function that returns updating text. Can use basic HTML.

    • done(): A function returning a boolean to determine if the milestone should be awarded.

    • toggles: optional. Creates toggle buttons that appear on the milestone when it is unlocked. The toggles can toggle a given boolean value in a layer. It is defined as an array of paired items, one pair per toggle. The first is the internal name of the layer the value being toggled is stored in, and the second is the internal name of the variable to toggle. (e.g. [["b", "auto"], ["g", "auto"])

      Tip: Toggles are not de-set if the milestone becomes locked! In this case, you should also check if the player has the milestone.

    • style: optional. Applies CSS to this milestone, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • unlocked(): optional. A function returning a boolean to determine if the milestone should be shown. If absent, it is always shown.

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the milestone was stored under, for convenient access. The milestone in the example's id is 0.

    Disaable milestone popups by adding milestonePopups: false to the layer.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/docs/subtabs-and-microtabs.html b/public/lit/docs/subtabs-and-microtabs.html index 65870d6e..67aaf445 100644 --- a/public/lit/docs/subtabs-and-microtabs.html +++ b/public/lit/docs/subtabs-and-microtabs.html @@ -8,11 +8,7 @@ - - - - - + @@ -49,8 +45,8 @@ otherStuff: { // There could be another set of microtabs here } -}

    Normal subtabs and microtab subtabs both use the same features:

    Features: ​

    • content: The tab layout code for the subtab, in the tab layout format.

    • style: optional. Applies CSS to the whole subtab when switched to, in the form of an "CSS Object", where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • buttonStyle: optional. A CSS object, which affects the appearance of the button for that subtab.

    • unlocked(): optional. a function to determine if the button for this subtab should be visible. By default, a subtab is always unlocked. You can't use the "this" keyword in this function.

    • shouldNotify(): optional, if true, the tab button will be highlighted to notify the player that there is something there.

    • embedLayer: SIGNIFICANT, the id of another layer. If you have this, it will override "content", "style" and "shouldNotify", instead displaying the entire layer in the subtab.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Normal subtabs and microtab subtabs both use the same features:

    Features: ​

    • content: The tab layout code for the subtab, in the tab layout format.

    • style: optional. Applies CSS to the whole subtab when switched to, in the form of an "CSS Object", where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • buttonStyle: optional. A CSS object, which affects the appearance of the button for that subtab.

    • unlocked(): optional. a function to determine if the button for this subtab should be visible. By default, a subtab is always unlocked. You can't use the "this" keyword in this function.

    • shouldNotify(): optional, if true, the tab button will be highlighted to notify the player that there is something there.

    • embedLayer: SIGNIFICANT, the id of another layer. If you have this, it will override "content", "style" and "shouldNotify", instead displaying the entire layer in the subtab.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/docs/trees-and-tree-customization.html b/public/lit/docs/trees-and-tree-customization.html index 2c15b161..2e14f228 100644 --- a/public/lit/docs/trees-and-tree-customization.html +++ b/public/lit/docs/trees-and-tree-customization.html @@ -8,11 +8,7 @@ - - - - - + @@ -27,8 +23,8 @@
    The Paper Pilot

    Appearance

    Trees and tree customization ​

    If you want to have something beyond the standard tree on the left tab, you can do that in tree.js. You can change the layout of the tree, including making non-layer nodes, change it into something other than a tree, or hide the left tab altogether. This also introduces the "tree" component, which can be used in your layers as well.

    layoutInfo ​

    The most important part is layoutInfo, containing:

    • startTab: The id of the default tab to show on the left at the start.
    • showTree: True if the tree tab should be shown at the start of the game. (The other tab will fill the whole page)
    • treeLayout: If present, overrides the tree layout and places nodes as you describe instead (explained in the next section).

    Additionally, if you want the main layout to not be a tree, you can edit the "tree-tab" layer at the bottom of tree.js to modify it just like a normal layer's tab. You can even switch between left tabs, using showNavTab(layer) to make that layer appear on the left.

    Trees ​

    The tree component is defined as an array of arrays of names of layers or nodes to show in the tree. They work just like layers/ nodes in the main tree (but branches between nodes will only work on the first node if you have duplicates.)

    Here is an example tree:

    js
    [["p"],
  ["left", "blank", "right", "blank"]
- ["a", "b", "blank", "c", "weirdButton"]]

    Nodes ​

    Nodes are non-layer buttons that can go in trees. They are defined similarly to layers, but with addNode instead of addLayer.

    Features:

    • color: optional, The node's color. (A string in hex format with a #)

    • symbol: optional The text on the button (The id capitalized by default)

    • canClick(): Returns true if the player can click the node. ()

    • onClick(): The function called when the node is clicked.

    • layerShown(): optional, A function returning a bool which determines if this node should be visible. It can also return "ghost", which will hide the layer, but its node will still take up space in its tree.

    • branches: optional. An array of layer/node ids. On a tree, a line will appear from this node to all of the nodes in the list. Alternatively, an entry in the array can be a 2-element array consisting of the id and a color value. The color value can either be a string with a hex color code, or a number from 1-3 (theme-affected colors).

    • nodeStyle: optional. A CSS object, where the keys are CSS attributes, which styles this node on the tree.

    • tooltip() / tooltipLocked(): optional. Functions that return text, which is the tooltip for the node when the layer is unlocked or locked, respectively. By default the tooltips behave the same as in the original Prestige Tree.

    • row: optional, the row that this node appears in (for the default tree).

    • position: optional, Determines the horizontal position of the layer in its row in a default tree. By default, it uses the id, and layers/nodes are sorted in alphabetical order.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - + ["a", "b", "blank", "c", "weirdButton"]]

    Nodes ​

    Nodes are non-layer buttons that can go in trees. They are defined similarly to layers, but with addNode instead of addLayer.

    Features:

    • color: optional, The node's color. (A string in hex format with a #)

    • symbol: optional The text on the button (The id capitalized by default)

    • canClick(): Returns true if the player can click the node. ()

    • onClick(): The function called when the node is clicked.

    • layerShown(): optional, A function returning a bool which determines if this node should be visible. It can also return "ghost", which will hide the layer, but its node will still take up space in its tree.

    • branches: optional. An array of layer/node ids. On a tree, a line will appear from this node to all of the nodes in the list. Alternatively, an entry in the array can be a 2-element array consisting of the id and a color value. The color value can either be a string with a hex color code, or a number from 1-3 (theme-affected colors).

    • nodeStyle: optional. A CSS object, where the keys are CSS attributes, which styles this node on the tree.

    • tooltip() / tooltipLocked(): optional. Functions that return text, which is the tooltip for the node when the layer is unlocked or locked, respectively. By default the tooltips behave the same as in the original Prestige Tree.

    • row: optional, the row that this node appears in (for the default tree).

    • position: optional, Determines the horizontal position of the layer in its row in a default tree. By default, it uses the id, and layers/nodes are sorted in alphabetical order.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/docs/updating-tmt.html b/public/lit/docs/updating-tmt.html index 42e0c49e..8cedf685 100644 --- a/public/lit/docs/updating-tmt.html +++ b/public/lit/docs/updating-tmt.html @@ -8,11 +8,7 @@ - - - - - + @@ -25,8 +21,8 @@ -
    The Paper Pilot

    Appearance

    Updating The Modding Tree ​

    This tutorial assumes that you have used the Getting Started Tutorial, and are using Github Desktop and VSCode for your mod.

    Here's what you have to do when there's a TMT update:

    1. Look at the changelog. It will warn you if the update will break anything or require any changes. Decide if you want to try to update.

    2. Open Github Desktop, and at the top middle, click "fetch origin". This will make Github Desktop get information about the update.

    3. Click where it says "current branch: master" at the top middle, and at the bottom of the thing that appears, click "choose a branch to merge into master".

    4. Select upstream/master. It will likely say there are conflicts, but you have tools to resolve them. Click "Merge upstream/master into master".

    5. A conflict happens when the things you're trying to merge have both made changes in the same place. Click "open in Visual Studio Code" next to the first file.

    6. Scroll down through the file, and look for the parts highlighted in red and green. One of these is your code, and the other is some code that will be modified by the update. Do your best to try to edit things to keep the updated changes, but keep your content.

    7. Continue to do this for all remaining changes.

    8. Do any other changes required by the update, run the game, fix issues, etc.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +
    The Paper Pilot

    Appearance

    Updating The Modding Tree ​

    This tutorial assumes that you have used the Getting Started Tutorial, and are using Github Desktop and VSCode for your mod.

    Here's what you have to do when there's a TMT update:

    1. Look at the changelog. It will warn you if the update will break anything or require any changes. Decide if you want to try to update.

    2. Open Github Desktop, and at the top middle, click "fetch origin". This will make Github Desktop get information about the update.

    3. Click where it says "current branch: master" at the top middle, and at the bottom of the thing that appears, click "choose a branch to merge into master".

    4. Select upstream/master. It will likely say there are conflicts, but you have tools to resolve them. Click "Merge upstream/master into master".

    5. A conflict happens when the things you're trying to merge have both made changes in the same place. Click "open in Visual Studio Code" next to the first file.

    6. Scroll down through the file, and look for the parts highlighted in red and green. One of these is your code, and the other is some code that will be modified by the update. Do your best to try to edit things to keep the updated changes, but keep your content.

    7. Continue to do this for all remaining changes.

    8. Do any other changes required by the update, run the game, fix issues, etc.

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file diff --git a/public/lit/docs/upgrades.html b/public/lit/docs/upgrades.html index aed2699f..7280db2e 100644 --- a/public/lit/docs/upgrades.html +++ b/public/lit/docs/upgrades.html @@ -8,11 +8,7 @@ - - - - - + @@ -34,8 +30,8 @@ etc }, etc -}

    Each upgrade should have an id where the first digit is the row and the second digit is the column.

    Individual upgrades can have these features:

    • title: optional. Displayed at the top in a larger font. It can also be a function that returns updating text. Can use basic HTML.

    • description: A description of the upgrade's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

    • effect(): optional. A function that calculates and returns the current values of any bonuses from the upgrade. Can return a value or an object containing multiple values.

    • effectDisplay(): optional. A function that returns a display of the current effects of the upgrade with formatting. Default displays nothing. Can use basic HTML.

    • fullDisplay(): OVERRIDE. Overrides the other displays and descriptions, and lets you set the full text for the upgrade. Can use basic HTML.

    • cost: A Decimal for the cost of the upgrade. By default, upgrades cost the main prestige currency for the layer.

    • unlocked(): optional. A function returning a bool to determine if the upgrade is visible or not. Default is unlocked.

    • onPurchase(): optional. This function will be called when the upgrade is purchased. Good for upgrades like "makes this layer act like it was unlocked first".

    • style: optional. Applies CSS to this upgrade, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the upgrade was stored under, for convenient access. The upgrade in the example's id is 11.

    By default, upgrades use the main prestige currency for the layer. You can include these to change them (but it needs to be a Decimal):

    • currencyDisplayName: optional. The name to display for the currency for the upgrade.

    • currencyInternalName: optional. The internal name for that currency.

    • currencyLayer: optional. The internal name of the layer that currency is stored in. If it's not in a layer (like Points), omit. If it's not stored directly in a layer, instead use the next feature.

    • currencyLocation: optional. If your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

    If you want to do something more complicated like upgrades that cost two currencies, you can override the purchase system with these (and you need to use fullDisplay as well)

    • canAfford(): OVERRIDE, a function determining if you are able to buy the upgrade

    • pay(): OVERRIDE, a function that reduces your currencies when you buy the upgrade

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    - +}

    Each upgrade should have an id where the first digit is the row and the second digit is the column.

    Individual upgrades can have these features:

    • title: optional. Displayed at the top in a larger font. It can also be a function that returns updating text. Can use basic HTML.

    • description: A description of the upgrade's effect. You will also have to implement the effect where it is applied. It can also be a function that returns updating text. Can use basic HTML.

    • effect(): optional. A function that calculates and returns the current values of any bonuses from the upgrade. Can return a value or an object containing multiple values.

    • effectDisplay(): optional. A function that returns a display of the current effects of the upgrade with formatting. Default displays nothing. Can use basic HTML.

    • fullDisplay(): OVERRIDE. Overrides the other displays and descriptions, and lets you set the full text for the upgrade. Can use basic HTML.

    • cost: A Decimal for the cost of the upgrade. By default, upgrades cost the main prestige currency for the layer.

    • unlocked(): optional. A function returning a bool to determine if the upgrade is visible or not. Default is unlocked.

    • onPurchase(): optional. This function will be called when the upgrade is purchased. Good for upgrades like "makes this layer act like it was unlocked first".

    • style: optional. Applies CSS to this upgrade, in the form of an object where the keys are CSS attributes, and the values are the values for those attributes (both as strings).

    • layer: assigned automagically. It's the same value as the name of this layer, so you can do player[this.layer].points or similar.

    • id: assigned automagically. It's the "key" which the upgrade was stored under, for convenient access. The upgrade in the example's id is 11.

    By default, upgrades use the main prestige currency for the layer. You can include these to change them (but it needs to be a Decimal):

    • currencyDisplayName: optional. The name to display for the currency for the upgrade.

    • currencyInternalName: optional. The internal name for that currency.

    • currencyLayer: optional. The internal name of the layer that currency is stored in. If it's not in a layer (like Points), omit. If it's not stored directly in a layer, instead use the next feature.

    • currencyLocation: optional. If your currency is stored in something inside a layer (e.g. a buyable's amount), you can access it this way. This is a function returning the object in "player" that contains the value (like player[this.layer].buyables)

    If you want to do something more complicated like upgrades that cost two currencies, you can override the purchase system with these (and you need to use fullDisplay as well)

    • canAfford(): OVERRIDE, a function determining if you are able to buy the upgrade

    • pay(): OVERRIDE, a function that reduces your currencies when you buy the upgrade

    CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    + \ No newline at end of file