diff --git a/404.html b/404.html index 7738ed49..8b062e67 100644 --- a/404.html +++ b/404.html @@ -6,9 +6,9 @@ 404 | The Paper Pilot - + - + @@ -22,7 +22,7 @@
- + \ No newline at end of file diff --git a/about/index.html b/about/index.html index 322e7035..4bf710bf 100644 --- a/about/index.html +++ b/about/index.html @@ -6,13 +6,13 @@ About Me | The Paper Pilot - + - + - - + + @@ -24,8 +24,8 @@ -
The Paper Pilot

About Me ​

I'm a software developer who likes making games and tools! I have a variety of interests, from game development to the fediverse to digital gardens.

I live in Dallas, Texas, USA with my wife and baby son.

I work at Topaz Labs LLC as a Product Engineer. I develop their flagship product Topaz Photo AI.

Reach out to me:

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are 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

About Me ​

I'm a software developer who likes making games and tools! I have a variety of interests, from game development to the fediverse to digital gardens.

I live in Dallas, Texas, USA with my wife and baby son. I work at Topaz Labs LLC as a Product Engineer. I develop their flagship product Topaz Photo AI.

Reach out to me:

CC 2024 The Paper Pilot. CC BY-NC-SA 4.0.
Any and all opinions listed here are 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/assets/about_index.md.BG_5Z8Zw.js b/assets/about_index.md.Bj378-Tn.js similarity index 64% rename from assets/about_index.md.BG_5Z8Zw.js rename to assets/about_index.md.Bj378-Tn.js index a0d14b80..446bbbc1 100644 --- a/assets/about_index.md.BG_5Z8Zw.js +++ b/assets/about_index.md.Bj378-Tn.js @@ -1 +1 @@ -import{_ as a,c as e,o as s,a5 as t,a4 as o}from"./chunks/framework.BIC8H_hJ.js";const f=JSON.parse('{"title":"About Me","description":"","frontmatter":{"title":"About Me","prev":false,"next":false},"headers":[],"relativePath":"about/index.md","filePath":"about/index.md"}'),n={name:"about/index.md"},i=t('

About Me ​

I'm a software developer who likes making games and tools! I have a variety of interests, from game development to the fediverse to digital gardens.

I live in Dallas, Texas, USA with my wife and baby son.

I work at Topaz Labs LLC as a Product Engineer. I develop their flagship product Topaz Photo AI.

Reach out to me:

',2),r=[i];function p(l,c,d,m,_,h){return s(),e("div",null,r)}const g=a(n,[["render",p]]);export{f as __pageData,g as default}; +import{_ as a,c as e,o as s,a5 as t,a4 as o}from"./chunks/framework.BIC8H_hJ.js";const f=JSON.parse('{"title":"About Me","description":"","frontmatter":{"title":"About Me","prev":false,"next":false},"headers":[],"relativePath":"about/index.md","filePath":"about/index.md"}'),n={name:"about/index.md"},i=t('

About Me ​

I'm a software developer who likes making games and tools! I have a variety of interests, from game development to the fediverse to digital gardens.

I live in Dallas, Texas, USA with my wife and baby son. I work at Topaz Labs LLC as a Product Engineer. I develop their flagship product Topaz Photo AI.

Reach out to me:

',2),r=[i];function l(p,c,d,m,_,h){return s(),e("div",null,r)}const g=a(n,[["render",l]]);export{f as __pageData,g as default}; diff --git a/assets/about_index.md.BG_5Z8Zw.lean.js b/assets/about_index.md.Bj378-Tn.lean.js similarity index 73% rename from assets/about_index.md.BG_5Z8Zw.lean.js rename to assets/about_index.md.Bj378-Tn.lean.js index a83683d4..462412d2 100644 --- a/assets/about_index.md.BG_5Z8Zw.lean.js +++ b/assets/about_index.md.Bj378-Tn.lean.js @@ -1 +1 @@ -import{_ as a,c as e,o as s,a5 as t,a4 as o}from"./chunks/framework.BIC8H_hJ.js";const f=JSON.parse('{"title":"About Me","description":"","frontmatter":{"title":"About Me","prev":false,"next":false},"headers":[],"relativePath":"about/index.md","filePath":"about/index.md"}'),n={name:"about/index.md"},i=t("",2),r=[i];function p(l,c,d,m,_,h){return s(),e("div",null,r)}const g=a(n,[["render",p]]);export{f as __pageData,g as default}; +import{_ as a,c as e,o as s,a5 as t,a4 as o}from"./chunks/framework.BIC8H_hJ.js";const f=JSON.parse('{"title":"About Me","description":"","frontmatter":{"title":"About Me","prev":false,"next":false},"headers":[],"relativePath":"about/index.md","filePath":"about/index.md"}'),n={name:"about/index.md"},i=t("",2),r=[i];function l(p,c,d,m,_,h){return s(),e("div",null,r)}const g=a(n,[["render",l]]);export{f as __pageData,g as default}; diff --git a/assets/app.CF4SexEJ.js b/assets/app.BU_mR-Aq.js similarity index 95% rename from assets/app.CF4SexEJ.js rename to assets/app.BU_mR-Aq.js index 4d9d8e0a..68282a3c 100644 --- a/assets/app.CF4SexEJ.js +++ b/assets/app.BU_mR-Aq.js @@ -1 +1 @@ -import{U as o,aq as p,ar as u,as as l,at as c,au as f,av as d,aw as m,ax as h,ay as A,az as g,d as v,u as y,y as P,x as w,aA as C,aB as R,aC as b,aD as E}from"./chunks/framework.BIC8H_hJ.js";import{R as S}from"./chunks/theme.DtwQKu2B.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}; +import{U as o,aq as p,ar as u,as as l,at as c,au as f,av as d,aw as m,ax as h,ay as A,az as g,d as v,u as y,y as P,x as w,aA as C,aB as R,aC as b,aD as E}from"./chunks/framework.BIC8H_hJ.js";import{R as S}from"./chunks/theme.C-h4U6q2.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/chunks/VPLocalSearchBox.CXpTOvCf.js b/assets/chunks/VPLocalSearchBox.D1yhhzqU.js similarity index 99% rename from assets/chunks/VPLocalSearchBox.CXpTOvCf.js rename to assets/chunks/VPLocalSearchBox.D1yhhzqU.js index 83df72be..fc1a9f2c 100644 --- a/assets/chunks/VPLocalSearchBox.CXpTOvCf.js +++ b/assets/chunks/VPLocalSearchBox.D1yhhzqU.js @@ -1,4 +1,4 @@ -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,aE as Dt,aF as kt,d as Ot,G as we,aG as et,h as xe,aH as Rt,aI as _t,x as Mt,aJ as Lt,y as Oe,R as he,Q as Fe,aK as Pt,a3 as zt,Y as Bt,U as Vt,aL as $t,o as X,b as Wt,j as k,a1 as Kt,k as G,aM as Jt,aN as Ut,aO as jt,c as te,n as tt,e as Ee,E as rt,F as at,a as de,t as ve,aP as Gt,p as Qt,l as Ht,aQ as nt,aR as qt,at as Yt,az as Zt,aS as Xt,_ as er}from"./framework.BIC8H_hJ.js";import{u as tr,c as rr}from"./theme.DtwQKu2B.js";const ar={root:()=>It(()=>import("./@localSearchIndexroot.DZ7KDNG6.js"),[])};/*! +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,aE as Dt,aF as kt,d as Ot,G as we,aG as et,h as xe,aH as Rt,aI as _t,x as Mt,aJ as Lt,y as Oe,R as he,Q as Fe,aK as Pt,a3 as zt,Y as Bt,U as Vt,aL as $t,o as X,b as Wt,j as k,a1 as Kt,k as G,aM as Jt,aN as Ut,aO as jt,c as te,n as tt,e as Ee,E as rt,F as at,a as de,t as ve,aP as Gt,p as Qt,l as Ht,aQ as nt,aR as qt,at as Yt,az as Zt,aS as Xt,_ as er}from"./framework.BIC8H_hJ.js";import{u as tr,c as rr}from"./theme.C-h4U6q2.js";const ar={root:()=>It(()=>import("./@localSearchIndexroot.DZ7KDNG6.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)};/*! diff --git a/assets/chunks/git.data.BUKN53Ta.js b/assets/chunks/git.data.pqelWCHe.js similarity index 97% rename from assets/chunks/git.data.BUKN53Ta.js rename to assets/chunks/git.data.pqelWCHe.js index c96a8e25..c211221e 100644 --- a/assets/chunks/git.data.BUKN53Ta.js +++ b/assets/chunks/git.data.pqelWCHe.js @@ -1 +1 @@ -const e=JSON.parse(`{"site/garden/advent-incremental/index.md":"Planted \\n. Last tended to \\n.","site/garden/artificial-intelligence/index.md":"Planted \\n. Last tended to \\n.","site/garden/atproto/index.md":"Planted \\n. Last tended to \\n.","site/garden/babble-buds/index.md":"Planted \\n. Last tended to \\n.","site/garden/capture-the-citadel/index.md":"Planted \\n. Last tended to \\n.","site/garden/chat-glue/index.md":"Planted \\n. Last tended to \\n.","site/garden/chronological/index.md":"Planted \\n. Last tended to \\n.","site/garden/cinny/index.md":"Planted \\n. Last tended to \\n.","site/garden/command-palettes/index.md":"Planted \\n. Last tended to \\n.","site/garden/commune/index.md":"Planted \\n. Last tended to \\n.","site/garden/davey-wreden/index.md":"Planted \\n. Last tended to \\n.","site/garden/decentralized/index.md":"Planted \\n. Last tended to \\n.","site/garden/dice-armor/index.md":"Planted \\n. Last tended to \\n.","site/garden/digital-gardens/index.md":"Planted \\n. Last tended to \\n.","site/garden/federated-identity/index.md":"Planted \\n. Last tended to \\n.","site/garden/fedi-v2/index.md":"Planted \\n. Last tended to \\n.","site/garden/fediverse/index.md":"Planted \\n. Last tended to \\n.","site/garden/forgejo/index.md":"Planted \\n. Last tended to \\n.","site/garden/freeform-vs-chronological-dichotomy/index.md":"Planted \\n. Last tended to \\n.","site/garden/freeform/index.md":"Planted \\n. Last tended to \\n.","site/garden/game-dev-tree/index.md":"Planted \\n. Last tended to \\n.","site/garden/garden-rss/index.md":"Planted \\n. Last tended to \\n.","site/garden/guide-to-incrementals/appeal-to-developers/index.md":"Planted \\n. Last tended to \\n.","site/garden/guide-to-incrementals/appeal-to-players/index.md":"Planted \\n. Last tended to \\n.","site/garden/guide-to-incrementals/defining-the-genre/index.md":"Planted \\n. Last tended to \\n.","site/garden/guide-to-incrementals/index.md":"Planted \\n. Last tended to \\n.","site/garden/guide-to-incrementals/navigating-criticism/index.md":"Planted \\n. Last tended to \\n.","site/garden/guide-to-incrementals/what-is-content/index.md":"Planted \\n. Last tended to \\n.","site/garden/incremental-social/index.md":"Planted \\n. Last tended to \\n.","site/garden/ivy-road/index.md":"Planted \\n. Last tended to \\n.","site/garden/kronos/index.md":"Planted \\n. Last tended to \\n.","site/garden/life-is-strange/index.md":"Planted \\n. Last tended to \\n.","site/garden/logseq/index.md":"Planted \\n. Last tended to \\n.","site/garden/matrix/index.md":"Planted \\n. Last tended to \\n.","site/garden/mbin/index.md":"Planted \\n. Last tended to \\n.","site/garden/mtx/index.md":"Planted \\n. Last tended to \\n.","site/garden/my-personal-website/index.md":"Planted \\n. Last tended to \\n.","site/garden/my-projects/index.md":"Planted \\n. Last tended to \\n.","site/garden/nostr/index.md":"Planted \\n. Last tended to \\n.","site/garden/open-source/index.md":"Planted \\n. Last tended to \\n.","site/garden/opti-speech/index.md":"Planted \\n. Last tended to \\n.","site/garden/planar-pioneers/index.md":"Planted \\n. Last tended to \\n.","site/garden/pre-order-bonuses/index.md":"Planted \\n. Last tended to \\n.","site/garden/premium-currency/index.md":"Planted \\n. Last tended to \\n.","site/garden/profectus/index.md":"Planted \\n. Last tended to \\n.","site/garden/social-media/index.md":"Planted \\n. Last tended to \\n.","site/garden/synapse/index.md":"Planted \\n. Last tended to \\n.","site/garden/the-beginner-s-guide/index.md":"Planted \\n. Last tended to \\n.","site/garden/the-cozy-web/index.md":"Planted \\n. Last tended to \\n.","site/garden/the-indieweb/amplification/index.md":"Planted \\n. Last tended to \\n.","site/garden/the-indieweb/signature-blocks/index.md":"Planted \\n. Last tended to \\n.","site/garden/the-small-web/index.md":"Planted \\n. Last tended to \\n.","site/garden/this-knowledge-hub/index.md":"Planted \\n. Last tended to \\n.","site/garden/v-ecs/index.md":"Planted \\n. Last tended to \\n.","site/garden/video-game-monetization/index.md":"Planted \\n. Last tended to \\n.","site/garden/vitepress/index.md":"Planted \\n. Last tended to \\n.","site/garden/wanderstop/index.md":"Planted \\n. Last tended to \\n.","site/garden/webrings/index.md":"Planted \\n. Last tended to \\n.","site/garden/weird/index.md":"Planted \\n. Last tended to \\n.","site/now/index.md":"Planted \\n. Last tended to \\n.","site/garden/activitypub/index.md":"Planted \\n. Last tended to \\n.","site/guide-to-incrementals/index.md":"Planted \\n. Last tended to \\n.","site/guide-to-incrementals/design/criticism/index.md":"Planted \\n. Last tended to \\n.","site/guide-to-incrementals/ludology/appeal-developers/index.md":"Planted \\n. Last tended to \\n.","site/guide-to-incrementals/ludology/appeal-gamers/index.md":"Planted \\n. Last tended to \\n.","site/guide-to-incrementals/ludology/content/index.md":"Planted \\n. Last tended to \\n.","site/guide-to-incrementals/ludology/definition/index.md":"Planted \\n. Last tended to \\n."}`);export{e as d}; +const e=JSON.parse(`{"site/garden/advent-incremental/index.md":"Planted \\n. Last tended to \\n.","site/garden/artificial-intelligence/index.md":"Planted \\n. Last tended to \\n.","site/garden/atproto/index.md":"Planted \\n. Last tended to \\n.","site/garden/babble-buds/index.md":"Planted \\n. Last tended to \\n.","site/garden/capture-the-citadel/index.md":"Planted \\n. Last tended to \\n.","site/garden/chat-glue/index.md":"Planted \\n. Last tended to \\n.","site/garden/chronological/index.md":"Planted \\n. Last tended to \\n.","site/garden/cinny/index.md":"Planted \\n. Last tended to \\n.","site/garden/command-palettes/index.md":"Planted \\n. Last tended to \\n.","site/garden/commune/index.md":"Planted \\n. Last tended to \\n.","site/garden/davey-wreden/index.md":"Planted \\n. Last tended to \\n.","site/garden/decentralized/index.md":"Planted \\n. Last tended to \\n.","site/garden/dice-armor/index.md":"Planted \\n. Last tended to \\n.","site/garden/digital-gardens/index.md":"Planted \\n. Last tended to \\n.","site/garden/federated-identity/index.md":"Planted \\n. Last tended to \\n.","site/garden/fedi-v2/index.md":"Planted \\n. Last tended to \\n.","site/garden/fediverse/index.md":"Planted \\n. Last tended to \\n.","site/garden/forgejo/index.md":"Planted \\n. Last tended to \\n.","site/garden/freeform-vs-chronological-dichotomy/index.md":"Planted \\n. Last tended to \\n.","site/garden/freeform/index.md":"Planted \\n. Last tended to \\n.","site/garden/game-dev-tree/index.md":"Planted \\n. Last tended to \\n.","site/garden/garden-rss/index.md":"Planted \\n. Last tended to \\n.","site/garden/guide-to-incrementals/appeal-to-developers/index.md":"Planted \\n. Last tended to \\n.","site/garden/guide-to-incrementals/appeal-to-players/index.md":"Planted \\n. Last tended to \\n.","site/garden/guide-to-incrementals/defining-the-genre/index.md":"Planted \\n. Last tended to \\n.","site/garden/guide-to-incrementals/index.md":"Planted \\n. Last tended to \\n.","site/garden/guide-to-incrementals/navigating-criticism/index.md":"Planted \\n. Last tended to \\n.","site/garden/guide-to-incrementals/what-is-content/index.md":"Planted \\n. Last tended to \\n.","site/garden/incremental-social/index.md":"Planted \\n. Last tended to \\n.","site/garden/ivy-road/index.md":"Planted \\n. Last tended to \\n.","site/garden/kronos/index.md":"Planted \\n. Last tended to \\n.","site/garden/life-is-strange/index.md":"Planted \\n. Last tended to \\n.","site/garden/logseq/index.md":"Planted \\n. Last tended to \\n.","site/garden/matrix/index.md":"Planted \\n. Last tended to \\n.","site/garden/mbin/index.md":"Planted \\n. Last tended to \\n.","site/garden/mtx/index.md":"Planted \\n. Last tended to \\n.","site/garden/my-personal-website/index.md":"Planted \\n. Last tended to \\n.","site/garden/my-projects/index.md":"Planted \\n. Last tended to \\n.","site/garden/nostr/index.md":"Planted \\n. Last tended to \\n.","site/garden/open-source/index.md":"Planted \\n. Last tended to \\n.","site/garden/opti-speech/index.md":"Planted \\n. Last tended to \\n.","site/garden/planar-pioneers/index.md":"Planted \\n. Last tended to \\n.","site/garden/pre-order-bonuses/index.md":"Planted \\n. Last tended to \\n.","site/garden/premium-currency/index.md":"Planted \\n. Last tended to \\n.","site/garden/profectus/index.md":"Planted \\n. Last tended to \\n.","site/garden/social-media/index.md":"Planted \\n. Last tended to \\n.","site/garden/synapse/index.md":"Planted \\n. Last tended to \\n.","site/garden/the-beginner-s-guide/index.md":"Planted \\n. Last tended to \\n.","site/garden/the-cozy-web/index.md":"Planted \\n. Last tended to \\n.","site/garden/the-indieweb/amplification/index.md":"Planted \\n. Last tended to \\n.","site/garden/the-indieweb/signature-blocks/index.md":"Planted \\n. Last tended to \\n.","site/garden/the-small-web/index.md":"Planted \\n. Last tended to \\n.","site/garden/this-knowledge-hub/index.md":"Planted \\n. Last tended to \\n.","site/garden/v-ecs/index.md":"Planted \\n. Last tended to \\n.","site/garden/video-game-monetization/index.md":"Planted \\n. Last tended to \\n.","site/garden/vitepress/index.md":"Planted \\n. Last tended to \\n.","site/garden/wanderstop/index.md":"Planted \\n. Last tended to \\n.","site/garden/webrings/index.md":"Planted \\n. Last tended to \\n.","site/garden/weird/index.md":"Planted \\n. Last tended to \\n.","site/garden/activitypub/index.md":"Planted \\n. Last tended to \\n.","site/now/index.md":"Planted \\n. Last tended to \\n.","site/guide-to-incrementals/index.md":"Planted \\n. Last tended to \\n.","site/guide-to-incrementals/design/criticism/index.md":"Planted \\n. Last tended to \\n.","site/guide-to-incrementals/ludology/appeal-developers/index.md":"Planted \\n. Last tended to \\n.","site/guide-to-incrementals/ludology/appeal-gamers/index.md":"Planted \\n. Last tended to \\n.","site/guide-to-incrementals/ludology/content/index.md":"Planted \\n. Last tended to \\n.","site/guide-to-incrementals/ludology/definition/index.md":"Planted \\n. Last tended to \\n."}`);export{e as d}; diff --git a/assets/chunks/theme.DtwQKu2B.js b/assets/chunks/theme.C-h4U6q2.js similarity index 86% rename from assets/chunks/theme.DtwQKu2B.js rename to assets/chunks/theme.C-h4U6q2.js index 408b5780..56cc41c5 100644 --- a/assets/chunks/theme.DtwQKu2B.js +++ b/assets/chunks/theme.C-h4U6q2.js @@ -1,2 +1,2 @@ -const __vite__fileDeps=["assets/chunks/VPLocalSearchBox.CXpTOvCf.js","assets/chunks/framework.BIC8H_hJ.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 w,b as $,w as v,e as f,T as pe,_ as k,u as ze,i as qe,f as Ke,g as he,h as y,j as u,k as r,p as C,l as B,m as z,q as le,s as I,v as O,x as ee,y as q,z as fe,A as Pe,B as Re,C as We,D as K,F as M,E as F,G as Le,H as te,I as m,J as W,K as Ve,L as Y,M as Q,N as oe,O as Ye,P as Se,Q as ce,R as we,S as Te,U as se,V as Je,W as Xe,X as Qe,Y as Ie,Z as Ne,$ as Ze,a0 as xe,a1 as et,a2 as tt,a3 as ot,a4 as st}from"./framework.BIC8H_hJ.js";const nt=_({__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(w(e.text),1)])],2))}}),at={key:0,class:"VPBackdrop"},rt=_({__name:"VPBackdrop",props:{show:{type:Boolean}},setup(o){return(e,t)=>(a(),$(pe,{name:"fade"},{default:v(()=>[e.show?(a(),c("div",at)):f("",!0)]),_:1}))}}),it=k(rt,[["__scopeId","data-v-c79a1216"]]),P=ze;function lt(o,e){let t,n=!1;return()=>{t&&clearTimeout(t),n?t=setTimeout(o,e):(o(),(n=!0)&&setTimeout(()=>n=!1,e))}}function ue(o){return/^\//.test(o)?o:`/${o}`}function _e(o){const{pathname:e,search:t,hash:n,protocol:s}=new URL(o,"http://a.com");if(qe(o)||o.startsWith("#")||!s.startsWith("http")||!Ke(e))return o;const{site:i}=P(),d=e.endsWith("/")||e.endsWith(".html")?o:o.replace(/(?:(^\.+)\/)?.*$/,`$1${e.replace(/(\.md)?$/,i.value.cleanUrls?"":".html")}${t}${n}`);return he(d)}function J({correspondingLink:o=!1}={}){const{site:e,localeIndex:t,page:n,theme:s,hash:i}=P(),d=y(()=>{var p,g;return{label:(p=e.value.locales[t.value])==null?void 0:p.label,link:((g=e.value.locales[t.value])==null?void 0:g.link)||(t.value==="root"?"/":`/${t.value}/`)}});return{localeLinks:y(()=>Object.entries(e.value.locales).flatMap(([p,g])=>d.value.label===g.label?[]:{text:g.label,link:ct(g.link||(p==="root"?"/":`/${p}/`),s.value.i18nRouting!==!1&&o,n.value.relativePath.slice(d.value.link.length-1),!e.value.cleanUrls)+i.value})),currentLang:d}}function ct(o,e,t,n){return e?o.replace(/\/$/,"")+ue(t.replace(/(^|\/)index\.md$/,"$1").replace(/\.md$/,n?".html":"")):o}const ut=o=>(C("data-v-d6be1790"),o=o(),B(),o),dt={class:"NotFound"},vt={class:"code"},pt={class:"title"},ht=ut(()=>u("div",{class:"divider"},null,-1)),ft={class:"quote"},_t={class:"action"},mt=["href","aria-label"],bt=_({__name:"NotFound",setup(o){const{theme:e}=P(),{currentLang:t}=J();return(n,s)=>{var i,d,h,p,g;return a(),c("div",dt,[u("p",vt,w(((i=r(e).notFound)==null?void 0:i.code)??"404"),1),u("h1",pt,w(((d=r(e).notFound)==null?void 0:d.title)??"PAGE NOT FOUND"),1),ht,u("blockquote",ft,w(((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),u("div",_t,[u("a",{class:"link",href:r(he)(r(t).link),"aria-label":((p=r(e).notFound)==null?void 0:p.linkLabel)??"go to home"},w(((g=r(e).notFound)==null?void 0:g.linkText)??"Take me home"),9,mt)])])}}}),kt=k(bt,[["__scopeId","data-v-d6be1790"]]);function Me(o,e){if(Array.isArray(o))return Z(o);if(o==null)return[];e=ue(e);const t=Object.keys(o).sort((s,i)=>i.split("/").length-s.split("/").length).find(s=>e.startsWith(ue(s))),n=t?o[t]:[];return Array.isArray(n)?Z(n):Z(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 gt(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 de(o,e){return Array.isArray(e)?e.some(t=>de(o,t)):z(o,e.link)?!0:e.items?de(o,e.items):!1}function Z(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=Z(n.items,s)),n})}function U(){const{frontmatter:o,page:e,theme:t}=P(),n=le("(min-width: 960px)"),s=I(!1),i=y(()=>{const H=t.value.sidebar,S=e.value.relativePath;return H?Me(H,S):[]}),d=I(i.value);O(i,(H,S)=>{JSON.stringify(H)!==JSON.stringify(S)&&(d.value=i.value)});const h=y(()=>o.value.sidebar!==!1&&d.value.length>0&&o.value.layout!=="home"),p=y(()=>g?o.value.aside==null?t.value.aside==="left":o.value.aside==="left":!1),g=y(()=>o.value.layout==="home"?!1:o.value.aside!=null?!!o.value.aside:t.value.aside!==!1),L=y(()=>h.value&&n.value),b=y(()=>h.value?$t(d.value):[]);function V(){s.value=!0}function T(){s.value=!1}function A(){s.value?T():V()}return{isOpen:s,sidebar:d,sidebarGroups:b,hasSidebar:h,hasAside:g,leftAside:p,isSidebarEnabled:L,open:V,close:T,toggle:A}}function yt(o,e){let t;ee(()=>{t=o.value?document.activeElement:void 0}),q(()=>{window.addEventListener("keyup",n)}),fe(()=>{window.removeEventListener("keyup",n)});function n(s){s.key==="Escape"&&o.value&&(e(),t==null||t.focus())}}function Pt(o){const{page:e,hash:t}=P(),n=I(!1),s=y(()=>o.value.collapsed!=null),i=y(()=>!!o.value.link),d=I(!1),h=()=>{d.value=z(e.value.relativePath,o.value.link)};O([e,o,t],h),q(h);const p=y(()=>d.value?!0:o.value.items?de(e.value.relativePath,o.value.items):!1),g=y(()=>!!(o.value.items&&o.value.items.length));ee(()=>{n.value=!!(s.value&&o.value.collapsed)}),Pe(()=>{(d.value||p.value)&&(n.value=!1)});function L(){s.value&&(n.value=!n.value)}return{collapsed:n,collapsible:s,isLink:i,isActiveLink:d,hasActiveLink:p,hasChildren:g,toggle:L}}function Lt(){const{hasSidebar:o}=U(),e=le("(min-width: 960px)"),t=le("(min-width: 1280px)");return{isAsideEnabled:y(()=>!t.value&&!e.value?!1:o.value?t.value:e.value)}}const ve=[];function Ae(o){return typeof o.outline=="object"&&!Array.isArray(o.outline)&&o.outline.label||o.outlineTitle||"On this page"}function me(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:Vt(t),link:"#"+t.id,level:n}});return St(e,o)}function Vt(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 St(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(d=>d.level>=n&&d.level<=s),ve.length=0;for(const{element:d,link:h}of o)ve.push({element:d,link:h});const i=[];e:for(let d=0;d=0;p--){const g=o[p];if(g.level{requestAnimationFrame(i),window.addEventListener("scroll",n)}),Re(()=>{d(location.hash)}),fe(()=>{window.removeEventListener("scroll",n)});function i(){if(!t.value)return;const h=window.scrollY,p=window.innerHeight,g=document.body.offsetHeight,L=Math.abs(h+p-g)<1,b=ve.map(({element:T,link:A})=>({link:A,top:Tt(T)})).filter(({top:T})=>!Number.isNaN(T)).sort((T,A)=>T.top-A.top);if(!b.length){d(null);return}if(h<1){d(null);return}if(L){d(b[b.length-1].link);return}let V=null;for(const{link:T,top:A}of b){if(A>h+We()+4)break;V=T}d(V)}function d(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 Tt(o){let e=0;for(;o!==document.body;){if(o===null)return NaN;e+=o.offsetTop,o=o.offsetParent}return e}const It=["href","title"],Nt=_({__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:d,title:h})=>(a(),c("li",null,[u("a",{class:"outline-link",href:d,onClick:e,title:h},w(h),9,It),i!=null&&i.length?(a(),$(s,{key:0,headers:i},null,8,["headers"])):f("",!0)]))),256))],2)}}}),He=k(Nt,[["__scopeId","data-v-b933a997"]]),Mt={class:"content"},At={"aria-level":"2",class:"outline-title",id:"doc-outline-aria-label",role:"heading"},Ht=_({__name:"VPDocAsideOutline",setup(o){const{frontmatter:e,theme:t}=P(),n=Le([]);te(()=>{n.value=me(e.value.outline??t.value.outline)});const s=I(),i=I();return wt(s,i),(d,h)=>(a(),c("nav",{"aria-labelledby":"doc-outline-aria-label",class:N(["VPDocAsideOutline",{"has-outline":n.value.length>0}]),ref_key:"container",ref:s},[u("div",Mt,[u("div",{class:"outline-marker",ref_key:"marker",ref:i},null,512),u("div",At,w(r(Ae)(r(t))),1),m(He,{headers:n.value,root:!0},null,8,["headers"])])],2))}}),Ct=k(Ht,[["__scopeId","data-v-a5bbad30"]]),Bt={class:"VPDocAsideCarbonAds"},Et=_({__name:"VPDocAsideCarbonAds",props:{carbonAds:{}},setup(o){const e=()=>null;return(t,n)=>(a(),c("div",Bt,[m(r(e),{"carbon-ads":t.carbonAds},null,8,["carbon-ads"])]))}}),Ft=o=>(C("data-v-3f215769"),o=o(),B(),o),Dt={class:"VPDocAside"},Ot=Ft(()=>u("div",{class:"spacer"},null,-1)),Ut=_({__name:"VPDocAside",setup(o){const{theme:e}=P();return(t,n)=>(a(),c("div",Dt,[l(t.$slots,"aside-top",{},void 0,!0),l(t.$slots,"aside-outline-before",{},void 0,!0),m(Ct),l(t.$slots,"aside-outline-after",{},void 0,!0),Ot,l(t.$slots,"aside-ads-before",{},void 0,!0),r(e).carbonAds?(a(),$(Et,{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)]))}}),Gt=k(Ut,[["__scopeId","data-v-3f215769"]]);function jt(){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 zt(){const{page:o,theme:e,frontmatter:t}=P();return y(()=>{var g,L,b,V,T,A,H,S;const n=Me(e.value.sidebar,o.value.relativePath),s=gt(n),i=qt(s,G=>G.link.replace(/[?#].*$/,"")),d=i.findIndex(G=>z(o.value.relativePath,G.link)),h=((g=e.value.docFooter)==null?void 0:g.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)??((b=i[d-1])==null?void 0:b.docFooterText)??((V=i[d-1])==null?void 0:V.text),link:(typeof t.value.prev=="object"?t.value.prev.link:void 0)??((T=i[d-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[d+1])==null?void 0:A.docFooterText)??((H=i[d+1])==null?void 0:H.text),link:(typeof t.value.next=="object"?t.value.next.link:void 0)??((S=i[d+1])==null?void 0:S.link)}}})}function qt(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&&Ve.test(e.href)||e.target==="_blank");return(s,i)=>(a(),$(W(t.value),{class:N(["VPLink",{link:s.href,"vp-external-link-icon":n.value,"no-icon":s.noIcon}]),href:s.href?r(_e)(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"]))}}),Kt={class:"VPLastUpdated"},Rt=["datetime"],Wt=_({__name:"VPDocFooterLastUpdated",setup(o){const{theme:e,page:t,frontmatter:n,lang:s}=P(),i=y(()=>new Date(n.value.lastUpdated??t.value.lastUpdated)),d=y(()=>i.value.toISOString()),h=I("");return q(()=>{ee(()=>{var p,g,L;h.value=new Intl.DateTimeFormat((g=(p=e.value.lastUpdated)==null?void 0:p.formatOptions)!=null&&g.forceLocale?s.value:void 0,((L=e.value.lastUpdated)==null?void 0:L.formatOptions)??{dateStyle:"short",timeStyle:"short"}).format(i.value)})}),(p,g)=>{var L;return a(),c("p",Kt,[E(w(((L=r(e).lastUpdated)==null?void 0:L.text)||r(e).lastUpdatedText||"Last updated")+": ",1),u("time",{datetime:d.value},w(h.value),9,Rt)])}}}),Yt=k(Wt,[["__scopeId","data-v-7e05ebdb"]]),Ce=o=>(C("data-v-d4a0bba5"),o=o(),B(),o),Jt={key:0,class:"VPDocFooter"},Xt={key:0,class:"edit-info"},Qt={key:0,class:"edit-link"},Zt=Ce(()=>u("span",{class:"vpi-square-pen edit-link-icon"},null,-1)),xt={key:1,class:"last-updated"},eo={key:1,class:"prev-next","aria-labelledby":"doc-footer-aria-label"},to=Ce(()=>u("span",{class:"visually-hidden",id:"doc-footer-aria-label"},"Pager",-1)),oo={class:"pager"},so=["innerHTML"],no=["innerHTML"],ao={class:"pager"},ro=["innerHTML"],io=["innerHTML"],lo=_({__name:"VPDocFooter",setup(o){const{theme:e,page:t,frontmatter:n}=P(),s=jt(),i=zt(),d=y(()=>e.value.editLink&&n.value.editLink!==!1),h=y(()=>t.value.lastUpdated&&n.value.lastUpdated!==!1),p=y(()=>d.value||h.value||i.value.prev||i.value.next);return(g,L)=>{var b,V,T,A;return p.value?(a(),c("footer",Jt,[l(g.$slots,"doc-footer-before",{},void 0,!0),d.value||h.value?(a(),c("div",Xt,[d.value?(a(),c("div",Qt,[m(D,{class:"edit-link-button",href:r(s).url,"no-icon":!0},{default:v(()=>[Zt,E(" "+w(r(s).text),1)]),_:1},8,["href"])])):f("",!0),h.value?(a(),c("div",xt,[m(Yt)])):f("",!0)])):f("",!0),(b=r(i).prev)!=null&&b.link||(V=r(i).next)!=null&&V.link?(a(),c("nav",eo,[to,u("div",oo,[(T=r(i).prev)!=null&&T.link?(a(),$(D,{key:0,class:"pager-link prev",href:r(i).prev.link},{default:v(()=>{var H;return[u("span",{class:"desc",innerHTML:((H=r(e).docFooter)==null?void 0:H.prev)||"Previous page"},null,8,so),u("span",{class:"title",innerHTML:r(i).prev.text},null,8,no)]}),_:1},8,["href"])):f("",!0)]),u("div",ao,[(A=r(i).next)!=null&&A.link?(a(),$(D,{key:0,class:"pager-link next",href:r(i).next.link},{default:v(()=>{var H;return[u("span",{class:"desc",innerHTML:((H=r(e).docFooter)==null?void 0:H.next)||"Next page"},null,8,ro),u("span",{class:"title",innerHTML:r(i).next.text},null,8,io)]}),_:1},8,["href"])):f("",!0)])])):f("",!0)])):f("",!0)}}}),co=k(lo,[["__scopeId","data-v-d4a0bba5"]]),uo=o=>(C("data-v-39a288b8"),o=o(),B(),o),vo={class:"container"},po=uo(()=>u("div",{class:"aside-curtain"},null,-1)),ho={class:"aside-container"},fo={class:"aside-content"},_o={class:"content"},mo={class:"content-container"},bo={class:"main"},ko=_({__name:"VPDoc",setup(o){const{theme:e}=P(),t=Y(),{hasSidebar:n,hasAside:s,leftAside:i}=U(),d=y(()=>t.path.replace(/[./]+/g,"_").replace(/_html$/,""));return(h,p)=>{const g=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),u("div",vo,[r(s)?(a(),c("div",{key:0,class:N(["aside",{"left-aside":r(i)}])},[po,u("div",ho,[u("div",fo,[m(Gt,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),u("div",_o,[u("div",mo,[l(h.$slots,"doc-before",{},void 0,!0),u("main",bo,[m(g,{class:N(["vp-doc",[d.value,r(e).externalLinkIcon&&"external-link-icon-enabled"]])},null,8,["class"])]),m(co,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=k(ko,[["__scopeId","data-v-39a288b8"]]),go=_({__name:"VPButton",props:{tag:{},size:{default:"medium"},theme:{default:"brand"},text:{},href:{},target:{},rel:{}},setup(o){const e=o,t=y(()=>e.href&&Ve.test(e.href)),n=y(()=>e.tag||e.href?"a":"button");return(s,i)=>(a(),$(W(n.value),{class:N(["VPButton",[s.size,s.theme]]),href:s.href?r(_e)(s.href):void 0,target:e.target??(t.value?"_blank":void 0),rel:e.rel??(t.value?"noreferrer":void 0)},{default:v(()=>[E(w(s.text),1)]),_:1},8,["class","href","target","rel"]))}}),yo=k(go,[["__scopeId","data-v-cad61b99"]]),Po=["src","alt"],Lo=_({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",Q({key:0,class:"VPImage"},typeof e.image=="string"?e.$attrs:{...e.image,...e.$attrs},{src:r(he)(typeof e.image=="string"?e.image:e.image.src),alt:e.alt??(typeof e.image=="string"?"":e.image.alt||"")}),null,16,Po)):(a(),c(M,{key:1},[m(n,Q({class:"dark",image:e.image.dark,alt:e.image.alt},e.$attrs),null,16,["image","alt"]),m(n,Q({class:"light",image:e.image.light,alt:e.image.alt},e.$attrs),null,16,["image","alt"])],64))],64)):f("",!0)}}}),x=k(Lo,[["__scopeId","data-v-8426fc1a"]]),Vo=o=>(C("data-v-303bb580"),o=o(),B(),o),So={class:"container"},wo={class:"main"},To={key:0,class:"name"},Io=["innerHTML"],No=["innerHTML"],Mo=["innerHTML"],Ao={key:0,class:"actions"},Ho={key:0,class:"image"},Co={class:"image-container"},Bo=Vo(()=>u("div",{class:"image-bg"},null,-1)),Eo=_({__name:"VPHero",props:{name:{},text:{},tagline:{},image:{},actions:{}},setup(o){const e=oe("hero-image-slot-exists");return(t,n)=>(a(),c("div",{class:N(["VPHero",{"has-image":t.image||r(e)}])},[u("div",So,[u("div",wo,[l(t.$slots,"home-hero-info-before",{},void 0,!0),l(t.$slots,"home-hero-info",{},()=>[t.name?(a(),c("h1",To,[u("span",{innerHTML:t.name,class:"clip"},null,8,Io)])):f("",!0),t.text?(a(),c("p",{key:1,innerHTML:t.text,class:"text"},null,8,No)):f("",!0),t.tagline?(a(),c("p",{key:2,innerHTML:t.tagline,class:"tagline"},null,8,Mo)):f("",!0)],!0),l(t.$slots,"home-hero-info-after",{},void 0,!0),t.actions?(a(),c("div",Ao,[(a(!0),c(M,null,F(t.actions,s=>(a(),c("div",{key:s.link,class:"action"},[m(yo,{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",Ho,[u("div",Co,[Bo,l(t.$slots,"home-hero-image",{},()=>[t.image?(a(),$(x,{key:0,class:"image-src",image:t.image},null,8,["image"])):f("",!0)],!0)])])):f("",!0)])],2))}}),Fo=k(Eo,[["__scopeId","data-v-303bb580"]]),Do=_({__name:"VPHomeHero",setup(o){const{frontmatter:e}=P();return(t,n)=>r(e).hero?(a(),$(Fo,{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)}}),Oo=o=>(C("data-v-a3976bdc"),o=o(),B(),o),Uo={class:"box"},Go={key:0,class:"icon"},jo=["innerHTML"],zo=["innerHTML"],qo=["innerHTML"],Ko={key:4,class:"link-text"},Ro={class:"link-text-value"},Wo=Oo(()=>u("span",{class:"vpi-arrow-right link-text-icon"},null,-1)),Yo=_({__name:"VPFeature",props:{icon:{},title:{},details:{},link:{},linkText:{},rel:{},target:{}},setup(o){return(e,t)=>(a(),$(D,{class:"VPFeature",href:e.link,rel:e.rel,target:e.target,"no-icon":!0,tag:e.link?"a":"div"},{default:v(()=>[u("article",Uo,[typeof e.icon=="object"&&e.icon.wrap?(a(),c("div",Go,[m(x,{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(),$(x,{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,jo)):f("",!0),u("h2",{class:"title",innerHTML:e.title},null,8,zo),e.details?(a(),c("p",{key:3,class:"details",innerHTML:e.details},null,8,qo)):f("",!0),e.linkText?(a(),c("div",Ko,[u("p",Ro,[E(w(e.linkText)+" ",1),Wo])])):f("",!0)])]),_:1},8,["href","rel","target","tag"]))}}),Jo=k(Yo,[["__scopeId","data-v-a3976bdc"]]),Xo={key:0,class:"VPFeatures"},Qo={class:"container"},Zo={class:"items"},xo=_({__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",Xo,[u("div",Qo,[u("div",Zo,[(a(!0),c(M,null,F(n.features,i=>(a(),c("div",{key:i.title,class:N(["item",[t.value]])},[m(Jo,{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)}}),es=k(xo,[["__scopeId","data-v-a6181336"]]),ts=_({__name:"VPHomeFeatures",setup(o){const{frontmatter:e}=P();return(t,n)=>r(e).features?(a(),$(es,{key:0,class:"VPHomeFeatures",features:r(e).features},null,8,["features"])):f("",!0)}}),os=_({__name:"VPHomeContent",setup(o){const{width:e}=Ye({initialWidth:0,includeScrollbar:!1});return(t,n)=>(a(),c("div",{class:"vp-doc container",style:Se(r(e)?{"--vp-offset":`calc(50% - ${r(e)/2}px)`}:{})},[l(t.$slots,"default",{},void 0,!0)],4))}}),ss=k(os,[["__scopeId","data-v-8e2d4988"]]),ns={class:"VPHome"},as=_({__name:"VPHome",setup(o){const{frontmatter:e}=P();return(t,n)=>{const s=K("Content");return a(),c("div",ns,[l(t.$slots,"home-hero-before",{},void 0,!0),m(Do,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(ts),l(t.$slots,"home-features-after",{},void 0,!0),r(e).markdownStyles!==!1?(a(),$(ss,{key:0},{default:v(()=>[m(s)]),_:1})):(a(),$(s,{key:1}))])}}}),rs=k(as,[["__scopeId","data-v-686f80a6"]]),is={},ls={class:"VPPage"};function cs(o,e){const t=K("Content");return a(),c("div",ls,[l(o.$slots,"page-top"),m(t),l(o.$slots,"page-bottom")])}const us=k(is,[["render",cs]]),ds=_({__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(kt)],!0):r(t).layout==="page"?(a(),$(us,{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(),$(rs,{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(),$(W(r(t).layout),{key:3})):(a(),$($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))}}),vs=k(ds,[["__scopeId","data-v-1428d186"]]),ps={class:"container"},hs=["innerHTML"],fs=["innerHTML"],_s=_({__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)}])},[u("div",ps,[r(e).footer.message?(a(),c("p",{key:0,class:"message",innerHTML:r(e).footer.message},null,8,hs)):f("",!0),r(e).footer.copyright?(a(),c("p",{key:1,class:"copyright",innerHTML:r(e).footer.copyright},null,8,fs)):f("",!0)])],2)):f("",!0)}}),ms=k(_s,[["__scopeId","data-v-e315a0ad"]]);function bs(){const{theme:o,frontmatter:e}=P(),t=Le([]),n=y(()=>t.value.length>0);return te(()=>{t.value=me(e.value.outline??o.value.outline)}),{headers:t,hasLocalNav:n}}const ks=o=>(C("data-v-17a5e62e"),o=o(),B(),o),$s={class:"menu-text"},gs=ks(()=>u("span",{class:"vpi-chevron-right icon"},null,-1)),ys={class:"header"},Ps={class:"outline"},Ls=_({__name:"VPLocalNavOutlineDropdown",props:{headers:{},navHeight:{}},setup(o){const e=o,{theme:t}=P(),n=I(!1),s=I(0),i=I(),d=I();function h(b){var V;(V=i.value)!=null&&V.contains(b.target)||(n.value=!1)}O(n,b=>{if(b){document.addEventListener("click",h);return}document.removeEventListener("click",h)}),ce("Escape",()=>{n.value=!1}),te(()=>{n.value=!1});function p(){n.value=!n.value,s.value=window.innerHeight+Math.min(window.scrollY-e.navHeight,0)}function g(b){b.target.classList.contains("outline-link")&&(d.value&&(d.value.style.transition="none"),we(()=>{n.value=!1}))}function L(){n.value=!1,window.scrollTo({top:0,left:0,behavior:"smooth"})}return(b,V)=>(a(),c("div",{class:"VPLocalNavOutlineDropdown",style:Se({"--vp-vh":s.value+"px"}),ref_key:"main",ref:i},[b.headers.length>0?(a(),c("button",{key:0,onClick:p,class:N({open:n.value})},[u("span",$s,w(r(Ae)(r(t))),1),gs],2)):(a(),c("button",{key:1,onClick:L},w(r(t).returnToTopLabel||"Return to top"),1)),m(pe,{name:"flyout"},{default:v(()=>[n.value?(a(),c("div",{key:0,ref_key:"items",ref:d,class:"items",onClick:g},[u("div",ys,[u("a",{class:"top-link",href:"#",onClick:L},w(r(t).returnToTopLabel||"Return to top"),1)]),u("div",Ps,[m(He,{headers:b.headers},null,8,["headers"])])],512)):f("",!0)]),_:1})],4))}}),Vs=k(Ls,[["__scopeId","data-v-17a5e62e"]]),Ss=o=>(C("data-v-a6f0e41e"),o=o(),B(),o),ws={class:"container"},Ts=["aria-expanded"],Is=Ss(()=>u("span",{class:"vpi-align-left menu-icon"},null,-1)),Ns={class:"menu-text"},Ms=_({__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}=Te(),d=I(0);q(()=>{d.value=parseInt(getComputedStyle(document.documentElement).getPropertyValue("--vp-nav-height"))}),te(()=>{s.value=me(t.value.outline??e.value.outline)});const h=y(()=>s.value.length===0),p=y(()=>h.value&&!n.value),g=y(()=>({VPLocalNav:!0,"has-sidebar":n.value,empty:h.value,fixed:p.value}));return(L,b)=>r(t).layout!=="home"&&(!p.value||r(i)>=d.value)?(a(),c("div",{key:0,class:N(g.value)},[u("div",ws,[r(n)?(a(),c("button",{key:0,class:"menu","aria-expanded":L.open,"aria-controls":"VPSidebarNav",onClick:b[0]||(b[0]=V=>L.$emit("open-menu"))},[Is,u("span",Ns,w(r(e).sidebarMenuLabel||"Menu"),1)],8,Ts)):f("",!0),m(Vs,{headers:r(s),navHeight:d.value},null,8,["headers","navHeight"])])],2)):f("",!0)}}),As=k(Ms,[["__scopeId","data-v-a6f0e41e"]]);function Hs(){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 Cs={},Bs={class:"VPSwitch",type:"button",role:"switch"},Es={class:"check"},Fs={key:0,class:"icon"};function Ds(o,e){return a(),c("button",Bs,[u("span",Es,[o.$slots.default?(a(),c("span",Fs,[l(o.$slots,"default",{},void 0,!0)])):f("",!0)])])}const Os=k(Cs,[["render",Ds],["__scopeId","data-v-1d5665e3"]]),Be=o=>(C("data-v-d1f28634"),o=o(),B(),o),Us=Be(()=>u("span",{class:"vpi-sun sun"},null,-1)),Gs=Be(()=>u("span",{class:"vpi-moon moon"},null,-1)),js=_({__name:"VPSwitchAppearance",setup(o){const{isDark:e,theme:t}=P(),n=oe("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,d)=>(a(),$(Os,{title:s.value,class:"VPSwitchAppearance","aria-checked":r(e),onClick:r(n)},{default:v(()=>[Us,Gs]),_:1},8,["title","aria-checked","onClick"]))}}),be=k(js,[["__scopeId","data-v-d1f28634"]]),zs={key:0,class:"VPNavBarAppearance"},qs=_({__name:"VPNavBarAppearance",setup(o){const{site:e}=P();return(t,n)=>r(e).appearance&&r(e).appearance!=="force-dark"?(a(),c("div",zs,[m(be)])):f("",!0)}}),Ks=k(qs,[["__scopeId","data-v-e6aabb21"]]),ke=I();let Ee=!1,ie=0;function Rs(o){const e=I(!1);if(se){!Ee&&Ws(),ie++;const t=O(ke,n=>{var s,i,d;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,(d=o.onBlur)==null||d.call(o))});fe(()=>{t(),ie--,ie||Ys()})}return Je(e)}function Ws(){document.addEventListener("focusin",Fe),Ee=!0,ke.value=document.activeElement}function Ys(){document.removeEventListener("focusin",Fe)}function Fe(){ke.value=document.activeElement}const Js={class:"VPMenuLink"},Xs=_({__name:"VPMenuLink",props:{item:{}},setup(o){const{page:e}=P();return(t,n)=>(a(),c("div",Js,[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(w(t.item.text),1)]),_:1},8,["class","href","target","rel"])]))}}),ne=k(Xs,[["__scopeId","data-v-43f1e123"]]),Qs={class:"VPMenuGroup"},Zs={key:0,class:"title"},xs=_({__name:"VPMenuGroup",props:{text:{},items:{}},setup(o){return(e,t)=>(a(),c("div",Qs,[e.text?(a(),c("p",Zs,w(e.text),1)):f("",!0),(a(!0),c(M,null,F(e.items,n=>(a(),c(M,null,["link"in n?(a(),$(ne,{key:0,item:n},null,8,["item"])):f("",!0)],64))),256))]))}}),en=k(xs,[["__scopeId","data-v-69e747b5"]]),tn={class:"VPMenu"},on={key:0,class:"items"},sn=_({__name:"VPMenu",props:{items:{}},setup(o){return(e,t)=>(a(),c("div",tn,[e.items?(a(),c("div",on,[(a(!0),c(M,null,F(e.items,n=>(a(),c(M,{key:n.text},["link"in n?(a(),$(ne,{key:0,item:n},null,8,["item"])):(a(),$(en,{key:1,text:n.text,items:n.items},null,8,["text","items"]))],64))),128))])):f("",!0),l(e.$slots,"default",{},void 0,!0)]))}}),nn=k(sn,[["__scopeId","data-v-e7ea1737"]]),an=o=>(C("data-v-b6c34ac9"),o=o(),B(),o),rn=["aria-expanded","aria-label"],ln={key:0,class:"text"},cn=["innerHTML"],un=an(()=>u("span",{class:"vpi-chevron-down text-icon"},null,-1)),dn={key:1,class:"vpi-more-horizontal icon"},vn={class:"menu"},pn=_({__name:"VPFlyout",props:{icon:{},button:{},label:{},items:{}},setup(o){const e=I(!1),t=I();Rs({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]=d=>e.value=!0),onMouseleave:i[2]||(i[2]=d=>e.value=!1)},[u("button",{type:"button",class:"button","aria-haspopup":"true","aria-expanded":e.value,"aria-label":s.label,onClick:i[0]||(i[0]=d=>e.value=!e.value)},[s.button||s.icon?(a(),c("span",ln,[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,cn)):f("",!0),un])):(a(),c("span",dn))],8,rn),u("div",vn,[m(nn,{items:s.items},{default:v(()=>[l(s.$slots,"default",{},void 0,!0)]),_:3},8,["items"])])],544))}}),$e=k(pn,[["__scopeId","data-v-b6c34ac9"]]),hn=["href","aria-label","innerHTML"],fn=_({__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,hn))}}),_n=k(fn,[["__scopeId","data-v-eee4e7cb"]]),mn={class:"VPSocialLinks"},bn=_({__name:"VPSocialLinks",props:{links:{}},setup(o){return(e,t)=>(a(),c("div",mn,[(a(!0),c(M,null,F(e.links,({link:n,icon:s,ariaLabel:i})=>(a(),$(_n,{key:n,icon:s,link:n,ariaLabel:i},null,8,["icon","link","ariaLabel"]))),128))]))}}),ge=k(bn,[["__scopeId","data-v-7bc22406"]]),kn={key:0,class:"group translations"},$n={class:"trans-title"},gn={key:1,class:"group"},yn={class:"item appearance"},Pn={class:"label"},Ln={class:"appearance-action"},Vn={key:2,class:"group"},Sn={class:"item social-links"},wn=_({__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(d,h)=>i.value?(a(),$($e,{key:0,class:"VPNavBarExtra",label:"extra navigation"},{default:v(()=>[r(n).length&&r(s).label?(a(),c("div",kn,[u("p",$n,w(r(s).label),1),(a(!0),c(M,null,F(r(n),p=>(a(),$(ne,{key:p.link,item:p},null,8,["item"]))),128))])):f("",!0),r(e).appearance&&r(e).appearance!=="force-dark"?(a(),c("div",gn,[u("div",yn,[u("p",Pn,w(r(t).darkModeSwitchLabel||"Appearance"),1),u("div",Ln,[m(be)])])])):f("",!0),r(t).socialLinks?(a(),c("div",Vn,[u("div",Sn,[m(ge,{class:"social-links-list",links:r(t).socialLinks},null,8,["links"])])])):f("",!0)]),_:1})):f("",!0)}}),Tn=k(wn,[["__scopeId","data-v-d0bd9dde"]]),In=o=>(C("data-v-e5dd9c1c"),o=o(),B(),o),Nn=["aria-expanded"],Mn=In(()=>u("span",{class:"container"},[u("span",{class:"top"}),u("span",{class:"middle"}),u("span",{class:"bottom"})],-1)),An=[Mn],Hn=_({__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"))},An,10,Nn))}}),Cn=k(Hn,[["__scopeId","data-v-e5dd9c1c"]]),Bn=["innerHTML"],En=_({__name:"VPNavBarMenuLink",props:{item:{}},setup(o){const{page:e}=P();return(t,n)=>(a(),$(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(()=>[u("span",{innerHTML:t.item.text},null,8,Bn)]),_:1},8,["class","href","noIcon","target","rel"]))}}),Fn=k(En,[["__scopeId","data-v-9c663999"]]),Dn=_({__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,d)=>(a(),$($e,{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"]))}}),On=o=>(C("data-v-7f418b0f"),o=o(),B(),o),Un={key:0,"aria-labelledby":"main-nav-aria-label",class:"VPNavBarMenu"},Gn=On(()=>u("span",{id:"main-nav-aria-label",class:"visually-hidden"},"Main Navigation",-1)),jn=_({__name:"VPNavBarMenu",setup(o){const{theme:e}=P();return(t,n)=>r(e).nav?(a(),c("nav",Un,[Gn,(a(!0),c(M,null,F(r(e).nav,s=>(a(),c(M,{key:s.text},["link"in s?(a(),$(Fn,{key:0,item:s},null,8,["item"])):(a(),$(Dn,{key:1,item:s},null,8,["item"]))],64))),128))])):f("",!0)}}),zn=k(jn,[["__scopeId","data-v-7f418b0f"]]);function qn(o){const{localeIndex:e,theme:t}=P();function n(s){var A,H,S;const i=s.split("."),d=(A=t.value.search)==null?void 0:A.options,h=d&&typeof d=="object",p=h&&((S=(H=d.locales)==null?void 0:H[e.value])==null?void 0:S.translations)||null,g=h&&d.translations||null;let L=p,b=g,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 ae=b==null?void 0:b[G];ae&&(j=b=ae);const re=L==null?void 0:L[G];re&&(j=L=re),R||(V=j),ae||(b=j),re||(L=j)}return(L==null?void 0:L[T])??(b==null?void 0:b[T])??(V==null?void 0:V[T])??""}return n}const Kn=["aria-label"],Rn={class:"DocSearch-Button-Container"},Wn=u("span",{class:"vp-icon DocSearch-Search-Icon"},null,-1),Yn={class:"DocSearch-Button-Placeholder"},Jn=u("span",{class:"DocSearch-Button-Keys"},[u("kbd",{class:"DocSearch-Button-Key"}),u("kbd",{class:"DocSearch-Button-Key"},"K")],-1),ye=_({__name:"VPNavBarSearchButton",setup(o){const t=qn({button:{buttonText:"Search",buttonAriaLabel:"Search"}});return(n,s)=>(a(),c("button",{type:"button",class:"DocSearch DocSearch-Button","aria-label":r(t)("button.buttonAriaLabel")},[u("span",Rn,[Wn,u("span",Yn,w(r(t)("button.buttonText")),1)]),Jn],8,Kn))}}),Xn={class:"VPNavBarSearch"},Qn={id:"local-search"},Zn={key:1,id:"docsearch"},xn=_({__name:"VPNavBarSearch",setup(o){const e=Xe(()=>Qe(()=>import("./VPLocalSearchBox.CXpTOvCf.js"),__vite__mapDeps([0,1]))),t=()=>null,{theme:n}=P(),s=I(!1),i=I(!1);q(()=>{});function d(){s.value||(s.value=!0,setTimeout(h,16))}function h(){const b=new Event("keydown");b.key="k",b.metaKey=!0,window.dispatchEvent(b),setTimeout(()=>{document.querySelector(".DocSearch-Modal")||h()},16)}function p(b){const V=b.target,T=V.tagName;return V.isContentEditable||T==="INPUT"||T==="SELECT"||T==="TEXTAREA"}const g=I(!1);ce("k",b=>{(b.ctrlKey||b.metaKey)&&(b.preventDefault(),g.value=!0)}),ce("/",b=>{p(b)||(b.preventDefault(),g.value=!0)});const L="local";return(b,V)=>{var T;return a(),c("div",Xn,[r(L)==="local"?(a(),c(M,{key:0},[g.value?(a(),$(r(e),{key:0,onClose:V[0]||(V[0]=A=>g.value=!1)})):f("",!0),u("div",Qn,[m(ye,{onClick:V[1]||(V[1]=A=>g.value=!0)})])],64)):r(L)==="algolia"?(a(),c(M,{key:1},[s.value?(a(),$(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",Zn,[m(ye,{onClick:d})]))],64)):f("",!0)])}}}),ea=_({__name:"VPNavBarSocialLinks",setup(o){const{theme:e}=P();return(t,n)=>r(e).socialLinks?(a(),$(ge,{key:0,class:"VPNavBarSocialLinks",links:r(e).socialLinks},null,8,["links"])):f("",!0)}}),ta=k(ea,[["__scopeId","data-v-0394ad82"]]),oa=["href","rel","target"],sa={key:1},na={key:2},aa=_({__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}),d=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,g)=>(a(),c("div",{class:N(["VPNavBarTitle",{"has-sidebar":r(n)}])},[u("a",{class:"title",href:i.value??r(_e)(r(s).link),rel:d.value,target:h.value},[l(p.$slots,"nav-bar-title-before",{},void 0,!0),r(t).logo?(a(),$(x,{key:0,class:"logo",image:r(t).logo},null,8,["image"])):f("",!0),r(t).siteTitle?(a(),c("span",sa,w(r(t).siteTitle),1)):r(t).siteTitle===void 0?(a(),c("span",na,w(r(e).title),1)):f("",!0),l(p.$slots,"nav-bar-title-after",{},void 0,!0)],8,oa)],2))}}),ra=k(aa,[["__scopeId","data-v-ab179fa1"]]),ia={class:"items"},la={class:"title"},ca=_({__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(),$($e,{key:0,class:"VPNavBarTranslations",icon:"vpi-languages",label:r(e).langMenuLabel||"Change language"},{default:v(()=>[u("div",ia,[u("p",la,w(r(n).label),1),(a(!0),c(M,null,F(r(t),d=>(a(),$(ne,{key:d.link,item:d},null,8,["item"]))),128))])]),_:1},8,["label"])):f("",!0)}}),ua=k(ca,[["__scopeId","data-v-88af2de4"]]),da=o=>(C("data-v-ccf7ddec"),o=o(),B(),o),va={class:"wrapper"},pa={class:"container"},ha={class:"title"},fa={class:"content"},_a={class:"content-body"},ma=da(()=>u("div",{class:"divider"},[u("div",{class:"divider-line"})],-1)),ba=_({__name:"VPNavBar",props:{isScreenOpen:{type:Boolean}},emits:["toggle-screen"],setup(o){const{y:e}=Te(),{hasSidebar:t}=U(),{frontmatter:n}=P(),s=I({});return Pe(()=>{s.value={"has-sidebar":t.value,home:n.value.layout==="home",top:e.value===0}}),(i,d)=>(a(),c("div",{class:N(["VPNavBar",s.value])},[u("div",va,[u("div",pa,[u("div",ha,[m(ra,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})]),u("div",fa,[u("div",_a,[l(i.$slots,"nav-bar-content-before",{},void 0,!0),m(xn,{class:"search"}),m(zn,{class:"menu"}),m(ua,{class:"translations"}),m(Ks,{class:"appearance"}),m(ta,{class:"social-links"}),m(Tn,{class:"extra"}),l(i.$slots,"nav-bar-content-after",{},void 0,!0),m(Cn,{class:"hamburger",active:i.isScreenOpen,onClick:d[0]||(d[0]=h=>i.$emit("toggle-screen"))},null,8,["active"])])])])]),ma],2))}}),ka=k(ba,[["__scopeId","data-v-ccf7ddec"]]),$a={key:0,class:"VPNavScreenAppearance"},ga={class:"text"},ya=_({__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,[u("p",ga,w(r(t).darkModeSwitchLabel||"Appearance"),1),m(be)])):f("",!0)}}),Pa=k(ya,[["__scopeId","data-v-2d7af913"]]),La=_({__name:"VPNavScreenMenuLink",props:{item:{}},setup(o){const e=oe("close-screen");return(t,n)=>(a(),$(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"]))}}),Va=k(La,[["__scopeId","data-v-7f31e1f6"]]),Sa=_({__name:"VPNavScreenMenuGroupLink",props:{item:{}},setup(o){const e=oe("close-screen");return(t,n)=>(a(),$(D,{class:"VPNavScreenMenuGroupLink",href:t.item.link,target:t.item.target,rel:t.item.rel,onClick:r(e)},{default:v(()=>[E(w(t.item.text),1)]),_:1},8,["href","target","rel","onClick"]))}}),De=k(Sa,[["__scopeId","data-v-19976ae1"]]),wa={class:"VPNavScreenMenuGroupSection"},Ta={key:0,class:"title"},Ia=_({__name:"VPNavScreenMenuGroupSection",props:{text:{},items:{}},setup(o){return(e,t)=>(a(),c("div",wa,[e.text?(a(),c("p",Ta,w(e.text),1)):f("",!0),(a(!0),c(M,null,F(e.items,n=>(a(),$(De,{key:n.text,item:n},null,8,["item"]))),128))]))}}),Na=k(Ia,[["__scopeId","data-v-8133b170"]]),Ma=o=>(C("data-v-ff6087d4"),o=o(),B(),o),Aa=["aria-controls","aria-expanded"],Ha=["innerHTML"],Ca=Ma(()=>u("span",{class:"vpi-plus button-icon"},null,-1)),Ba=["id"],Ea={key:1,class:"group"},Fa=_({__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,d)=>(a(),c("div",{class:N(["VPNavScreenMenuGroup",{open:t.value}])},[u("button",{class:"button","aria-controls":n.value,"aria-expanded":t.value,onClick:s},[u("span",{class:"button-text",innerHTML:i.text},null,8,Ha),Ca],8,Aa),u("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(De,{item:h},null,8,["item"])])):(a(),c("div",Ea,[m(Na,{text:h.text,items:h.items},null,8,["text","items"])]))],64))),128))],8,Ba)],2))}}),Da=k(Fa,[["__scopeId","data-v-ff6087d4"]]),Oa={key:0,class:"VPNavScreenMenu"},Ua=_({__name:"VPNavScreenMenu",setup(o){const{theme:e}=P();return(t,n)=>r(e).nav?(a(),c("nav",Oa,[(a(!0),c(M,null,F(r(e).nav,s=>(a(),c(M,{key:s.text},["link"in s?(a(),$(Va,{key:0,item:s},null,8,["item"])):(a(),$(Da,{key:1,text:s.text||"",items:s.items},null,8,["text","items"]))],64))),128))])):f("",!0)}}),Ga=_({__name:"VPNavScreenSocialLinks",setup(o){const{theme:e}=P();return(t,n)=>r(e).socialLinks?(a(),$(ge,{key:0,class:"VPNavScreenSocialLinks",links:r(e).socialLinks},null,8,["links"])):f("",!0)}}),Oe=o=>(C("data-v-858fe1a4"),o=o(),B(),o),ja=Oe(()=>u("span",{class:"vpi-languages icon lang"},null,-1)),za=Oe(()=>u("span",{class:"vpi-chevron-down icon chevron"},null,-1)),qa={class:"list"},Ka=_({__name:"VPNavScreenTranslations",setup(o){const{localeLinks:e,currentLang:t}=J({correspondingLink:!0}),n=I(!1);function s(){n.value=!n.value}return(i,d)=>r(e).length&&r(t).label?(a(),c("div",{key:0,class:N(["VPNavScreenTranslations",{open:n.value}])},[u("button",{class:"title",onClick:s},[ja,E(" "+w(r(t).label)+" ",1),za]),u("ul",qa,[(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(w(h.text),1)]),_:2},1032,["href"])]))),128))])],2)):f("",!0)}}),Ra=k(Ka,[["__scopeId","data-v-858fe1a4"]]),Wa={class:"container"},Ya=_({__name:"VPNavScreen",props:{open:{type:Boolean}},setup(o){const e=I(null),t=Ie(se?document.body:null);return(n,s)=>(a(),$(pe,{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"},[u("div",Wa,[l(n.$slots,"nav-screen-content-before",{},void 0,!0),m(Ua,{class:"menu"}),m(Ra,{class:"translations"}),m(Pa,{class:"appearance"}),m(Ga,{class:"social-links"}),l(n.$slots,"nav-screen-content-after",{},void 0,!0)])],512)):f("",!0)]),_:3}))}}),Ja=k(Ya,[["__scopeId","data-v-cc5739dd"]]),Xa={key:0,class:"VPNav"},Qa=_({__name:"VPNav",setup(o){const{isScreenOpen:e,closeScreen:t,toggleScreen:n}=Hs(),{frontmatter:s}=P(),i=y(()=>s.value.navbar!==!1);return Ne("close-screen",t),ee(()=>{se&&document.documentElement.classList.toggle("hide-nav",!i.value)}),(d,h)=>i.value?(a(),c("header",Xa,[m(ka,{"is-screen-open":r(e),onToggleScreen:r(n)},{"nav-bar-title-before":v(()=>[l(d.$slots,"nav-bar-title-before",{},void 0,!0)]),"nav-bar-title-after":v(()=>[l(d.$slots,"nav-bar-title-after",{},void 0,!0)]),"nav-bar-content-before":v(()=>[l(d.$slots,"nav-bar-content-before",{},void 0,!0)]),"nav-bar-content-after":v(()=>[l(d.$slots,"nav-bar-content-after",{},void 0,!0)]),_:3},8,["is-screen-open","onToggleScreen"]),m(Ja,{open:r(e)},{"nav-screen-content-before":v(()=>[l(d.$slots,"nav-screen-content-before",{},void 0,!0)]),"nav-screen-content-after":v(()=>[l(d.$slots,"nav-screen-content-after",{},void 0,!0)]),_:3},8,["open"])])):f("",!0)}}),Za=k(Qa,[["__scopeId","data-v-ae24b3ad"]]),Ue=o=>(C("data-v-b8d55f3b"),o=o(),B(),o),xa=["role","tabindex"],er=Ue(()=>u("div",{class:"indicator"},null,-1)),tr=["onKeydown"],or=Ue(()=>u("span",{class:"vpi-chevron-right caret-icon"},null,-1)),sr=[or],nr={key:1,class:"items"},ar=_({__name:"VPSidebarItem",props:{item:{},depth:{}},setup(o){const e=o,{collapsed:t,collapsible:n,isLink:s,isActiveLink:i,hasActiveLink:d,hasChildren:h,toggle:p}=Pt(y(()=>e.item)),g=y(()=>h.value?"section":"div"),L=y(()=>s.value?"a":"div"),b=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":d.value}]);function A(S){"key"in S&&S.key!=="Enter"||!e.item.link&&p()}function H(){e.item.link&&p()}return(S,G)=>{const j=K("VPSidebarItem",!0);return a(),$(W(g.value),{class:N(["VPSidebarItem",T.value])},{default:v(()=>[S.item.text?(a(),c("div",Q({key:0,class:"item",role:V.value},xe(S.item.items?{click:A,keydown:A}:{},!0),{tabindex:S.item.items&&0}),[er,S.item.link?(a(),$(D,{key:0,tag:L.value,class:"link",href:S.item.link,rel:S.item.rel,target:S.item.target},{default:v(()=>[(a(),$(W(b.value),{class:"text",innerHTML:S.item.text},null,8,["innerHTML"]))]),_:1},8,["tag","href","rel","target"])):(a(),$(W(b.value),{key:1,class:"text",innerHTML:S.item.text},null,8,["innerHTML"])),S.item.collapsed!=null&&S.item.items&&S.item.items.length?(a(),c("div",{key:2,class:"caret",role:"button","aria-label":"toggle section",onClick:H,onKeydown:Ze(H,["enter"]),tabindex:"0"},sr,40,tr)):f("",!0)],16,xa)):f("",!0),S.item.items&&S.item.items.length?(a(),c("div",nr,[S.depth<5?(a(!0),c(M,{key:0},F(S.item.items,R=>(a(),$(j,{key:R.text,item:R,depth:S.depth+1},null,8,["item","depth"]))),128)):f("",!0)])):f("",!0)]),_:1},8,["class"])}}}),rr=k(ar,[["__scopeId","data-v-b8d55f3b"]]),Ge=o=>(C("data-v-575e6a36"),o=o(),B(),o),ir=Ge(()=>u("div",{class:"curtain"},null,-1)),lr={class:"nav",id:"VPSidebarNav","aria-labelledby":"sidebar-aria-label",tabindex:"-1"},cr=Ge(()=>u("span",{class:"visually-hidden",id:"sidebar-aria-label"}," Sidebar Navigation ",-1)),ur=_({__name:"VPSidebar",props:{open:{type:Boolean}},setup(o){const e=o,{sidebarGroups:t,hasSidebar:n}=U(),s=I(null),i=Ie(se?document.body:null);return O([e,s],()=>{var d;e.open?(i.value=!0,(d=s.value)==null||d.focus()):i.value=!1},{immediate:!0,flush:"post"}),(d,h)=>r(n)?(a(),c("aside",{key:0,class:N(["VPSidebar",{open:d.open}]),ref_key:"navEl",ref:s,onClick:h[0]||(h[0]=et(()=>{},["stop"]))},[ir,u("nav",lr,[cr,l(d.$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(rr,{item:p,depth:0},null,8,["item"])]))),128)),l(d.$slots,"sidebar-nav-after",{},void 0,!0)])],2)):f("",!0)}}),dr=k(ur,[["__scopeId","data-v-575e6a36"]]),vr=_({__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 d=()=>{i.removeAttribute("tabindex"),i.removeEventListener("blur",d)};i.setAttribute("tabindex","-1"),i.addEventListener("blur",d),i.focus(),window.scrollTo(0,0)}}return(s,i)=>(a(),c(M,null,[u("span",{ref_key:"backToTop",ref:t,tabindex:"-1"},null,512),u("a",{href:"#VPContent",class:"VPSkipLink visually-hidden",onClick:n}," Skip to content ")],64))}}),pr=k(vr,[["__scopeId","data-v-0f60ec36"]]),hr=_({__name:"Layout",setup(o){const{isOpen:e,open:t,close:n}=U(),s=Y();O(()=>s.path,n),yt(e,n);const{frontmatter:i}=P(),d=tt(),h=y(()=>!!d["home-hero-image"]);return Ne("hero-image-slot-exists",h),(p,g)=>{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(pr),m(it,{class:"backdrop",show:r(e),onClick:r(n)},null,8,["show","onClick"]),m(Za,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(As,{open:r(e),onOpenMenu:r(t)},null,8,["open","onOpenMenu"]),m(dr,{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(vs,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(ms),l(p.$slots,"layout-bottom",{},void 0,!0)],2)):(a(),$(L,{key:1}))}}}),fr=k(hr,[["__scopeId","data-v-5d98c3a5"]]),je={Layout:fr,enhanceApp:({app:o})=>{o.component("Badge",nt)}},_r=_({__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 we(),e()}),ot("hashchange",e),(n,s)=>l(n.$slots,"default")}}),X=o=>(C("data-v-25629fb0"),o=o(),B(),o),mr={class:"vp-doc"},br=X(()=>u("a",{class:"h-card u-uid",href:"/about"},[u("img",{src:st,alt:""}),E("The Paper Pilot")],-1)),kr=X(()=>u("a",{rel:"license",href:"https://creativecommons.org/licenses/by-nc-sa/4.0/"},"CC BY-NC-SA 4.0",-1)),$r=X(()=>u("div",null,"Any and all opinions listed here are my own and not representative of my employers; future, past and present.",-1)),gr=X(()=>u("div",null,[u("a",{href:"https://resume.incremental.social/thepaperpilot/thepaperpilot"},"Resume"),E(" (not actively seeking new opportunities).")],-1)),yr=X(()=>u("div",null,[E("Site built from "),u("a",{href:"https://code.incremental.social/thepaperpilot/pages/commit/69806655296d142bed214ae0a1af9c5c2c01cefc"},"this commit"),E(" on "),u("time",null,"Tuesday, June 18, 2024 at 12:44:40"),E(".")],-1)),Pr=_({__name:"Layout",setup(o){return(e,t)=>(a(),$(r(je).Layout,null,{"layout-top":v(()=>[m(r(_r))]),"layout-bottom":v(()=>[u("footer",mr,[u("div",null,[E("CC "+w(new Date().getFullYear())+" ",1),br,E(". "),kr,E(".")]),$r,gr,yr])]),_:1}))}}),Lr=k(Pr,[["__scopeId","data-v-25629fb0"]]),Sr={...je,Layout:Lr};export{Sr as R,qn as c,P as u}; +const __vite__fileDeps=["assets/chunks/VPLocalSearchBox.D1yhhzqU.js","assets/chunks/framework.BIC8H_hJ.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 w,b as $,w as v,e as f,T as pe,_ as b,u as ze,i as qe,f as Ke,g as he,h as y,j as u,k as r,p as C,l as B,m as z,q as le,s as I,v as O,x as ee,y as q,z as fe,A as Pe,B as Re,C as We,D as K,F as M,E as F,G as Le,H as te,I as m,J as W,K as Ve,L as Y,M as Q,N as oe,O as Ye,P as Se,Q as ce,R as we,S as Te,U as se,V as Je,W as Xe,X as Qe,Y as Ie,Z as Ne,$ as Ze,a0 as xe,a1 as et,a2 as tt,a3 as ot,a4 as st}from"./framework.BIC8H_hJ.js";const nt=_({__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(w(e.text),1)])],2))}}),at={key:0,class:"VPBackdrop"},rt=_({__name:"VPBackdrop",props:{show:{type:Boolean}},setup(o){return(e,t)=>(a(),$(pe,{name:"fade"},{default:v(()=>[e.show?(a(),c("div",at)):f("",!0)]),_:1}))}}),it=b(rt,[["__scopeId","data-v-c79a1216"]]),P=ze;function lt(o,e){let t,n=!1;return()=>{t&&clearTimeout(t),n?t=setTimeout(o,e):(o(),(n=!0)&&setTimeout(()=>n=!1,e))}}function ue(o){return/^\//.test(o)?o:`/${o}`}function _e(o){const{pathname:e,search:t,hash:n,protocol:s}=new URL(o,"http://a.com");if(qe(o)||o.startsWith("#")||!s.startsWith("http")||!Ke(e))return o;const{site:i}=P(),d=e.endsWith("/")||e.endsWith(".html")?o:o.replace(/(?:(^\.+)\/)?.*$/,`$1${e.replace(/(\.md)?$/,i.value.cleanUrls?"":".html")}${t}${n}`);return he(d)}function J({correspondingLink:o=!1}={}){const{site:e,localeIndex:t,page:n,theme:s,hash:i}=P(),d=y(()=>{var p,g;return{label:(p=e.value.locales[t.value])==null?void 0:p.label,link:((g=e.value.locales[t.value])==null?void 0:g.link)||(t.value==="root"?"/":`/${t.value}/`)}});return{localeLinks:y(()=>Object.entries(e.value.locales).flatMap(([p,g])=>d.value.label===g.label?[]:{text:g.label,link:ct(g.link||(p==="root"?"/":`/${p}/`),s.value.i18nRouting!==!1&&o,n.value.relativePath.slice(d.value.link.length-1),!e.value.cleanUrls)+i.value})),currentLang:d}}function ct(o,e,t,n){return e?o.replace(/\/$/,"")+ue(t.replace(/(^|\/)index\.md$/,"$1").replace(/\.md$/,n?".html":"")):o}const ut=o=>(C("data-v-d6be1790"),o=o(),B(),o),dt={class:"NotFound"},vt={class:"code"},pt={class:"title"},ht=ut(()=>u("div",{class:"divider"},null,-1)),ft={class:"quote"},_t={class:"action"},mt=["href","aria-label"],kt=_({__name:"NotFound",setup(o){const{theme:e}=P(),{currentLang:t}=J();return(n,s)=>{var i,d,h,p,g;return a(),c("div",dt,[u("p",vt,w(((i=r(e).notFound)==null?void 0:i.code)??"404"),1),u("h1",pt,w(((d=r(e).notFound)==null?void 0:d.title)??"PAGE NOT FOUND"),1),ht,u("blockquote",ft,w(((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),u("div",_t,[u("a",{class:"link",href:r(he)(r(t).link),"aria-label":((p=r(e).notFound)==null?void 0:p.linkLabel)??"go to home"},w(((g=r(e).notFound)==null?void 0:g.linkText)??"Take me home"),9,mt)])])}}}),bt=b(kt,[["__scopeId","data-v-d6be1790"]]);function Me(o,e){if(Array.isArray(o))return Z(o);if(o==null)return[];e=ue(e);const t=Object.keys(o).sort((s,i)=>i.split("/").length-s.split("/").length).find(s=>e.startsWith(ue(s))),n=t?o[t]:[];return Array.isArray(n)?Z(n):Z(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 gt(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 de(o,e){return Array.isArray(e)?e.some(t=>de(o,t)):z(o,e.link)?!0:e.items?de(o,e.items):!1}function Z(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=Z(n.items,s)),n})}function U(){const{frontmatter:o,page:e,theme:t}=P(),n=le("(min-width: 960px)"),s=I(!1),i=y(()=>{const H=t.value.sidebar,S=e.value.relativePath;return H?Me(H,S):[]}),d=I(i.value);O(i,(H,S)=>{JSON.stringify(H)!==JSON.stringify(S)&&(d.value=i.value)});const h=y(()=>o.value.sidebar!==!1&&d.value.length>0&&o.value.layout!=="home"),p=y(()=>g?o.value.aside==null?t.value.aside==="left":o.value.aside==="left":!1),g=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(d.value):[]);function V(){s.value=!0}function T(){s.value=!1}function A(){s.value?T():V()}return{isOpen:s,sidebar:d,sidebarGroups:k,hasSidebar:h,hasAside:g,leftAside:p,isSidebarEnabled:L,open:V,close:T,toggle:A}}function yt(o,e){let t;ee(()=>{t=o.value?document.activeElement:void 0}),q(()=>{window.addEventListener("keyup",n)}),fe(()=>{window.removeEventListener("keyup",n)});function n(s){s.key==="Escape"&&o.value&&(e(),t==null||t.focus())}}function Pt(o){const{page:e,hash:t}=P(),n=I(!1),s=y(()=>o.value.collapsed!=null),i=y(()=>!!o.value.link),d=I(!1),h=()=>{d.value=z(e.value.relativePath,o.value.link)};O([e,o,t],h),q(h);const p=y(()=>d.value?!0:o.value.items?de(e.value.relativePath,o.value.items):!1),g=y(()=>!!(o.value.items&&o.value.items.length));ee(()=>{n.value=!!(s.value&&o.value.collapsed)}),Pe(()=>{(d.value||p.value)&&(n.value=!1)});function L(){s.value&&(n.value=!n.value)}return{collapsed:n,collapsible:s,isLink:i,isActiveLink:d,hasActiveLink:p,hasChildren:g,toggle:L}}function Lt(){const{hasSidebar:o}=U(),e=le("(min-width: 960px)"),t=le("(min-width: 1280px)");return{isAsideEnabled:y(()=>!t.value&&!e.value?!1:o.value?t.value:e.value)}}const ve=[];function Ae(o){return typeof o.outline=="object"&&!Array.isArray(o.outline)&&o.outline.label||o.outlineTitle||"On this page"}function me(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:Vt(t),link:"#"+t.id,level:n}});return St(e,o)}function Vt(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 St(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(d=>d.level>=n&&d.level<=s),ve.length=0;for(const{element:d,link:h}of o)ve.push({element:d,link:h});const i=[];e:for(let d=0;d=0;p--){const g=o[p];if(g.level{requestAnimationFrame(i),window.addEventListener("scroll",n)}),Re(()=>{d(location.hash)}),fe(()=>{window.removeEventListener("scroll",n)});function i(){if(!t.value)return;const h=window.scrollY,p=window.innerHeight,g=document.body.offsetHeight,L=Math.abs(h+p-g)<1,k=ve.map(({element:T,link:A})=>({link:A,top:Tt(T)})).filter(({top:T})=>!Number.isNaN(T)).sort((T,A)=>T.top-A.top);if(!k.length){d(null);return}if(h<1){d(null);return}if(L){d(k[k.length-1].link);return}let V=null;for(const{link:T,top:A}of k){if(A>h+We()+4)break;V=T}d(V)}function d(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 Tt(o){let e=0;for(;o!==document.body;){if(o===null)return NaN;e+=o.offsetTop,o=o.offsetParent}return e}const It=["href","title"],Nt=_({__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:d,title:h})=>(a(),c("li",null,[u("a",{class:"outline-link",href:d,onClick:e,title:h},w(h),9,It),i!=null&&i.length?(a(),$(s,{key:0,headers:i},null,8,["headers"])):f("",!0)]))),256))],2)}}}),He=b(Nt,[["__scopeId","data-v-b933a997"]]),Mt={class:"content"},At={"aria-level":"2",class:"outline-title",id:"doc-outline-aria-label",role:"heading"},Ht=_({__name:"VPDocAsideOutline",setup(o){const{frontmatter:e,theme:t}=P(),n=Le([]);te(()=>{n.value=me(e.value.outline??t.value.outline)});const s=I(),i=I();return wt(s,i),(d,h)=>(a(),c("nav",{"aria-labelledby":"doc-outline-aria-label",class:N(["VPDocAsideOutline",{"has-outline":n.value.length>0}]),ref_key:"container",ref:s},[u("div",Mt,[u("div",{class:"outline-marker",ref_key:"marker",ref:i},null,512),u("div",At,w(r(Ae)(r(t))),1),m(He,{headers:n.value,root:!0},null,8,["headers"])])],2))}}),Ct=b(Ht,[["__scopeId","data-v-a5bbad30"]]),Bt={class:"VPDocAsideCarbonAds"},Et=_({__name:"VPDocAsideCarbonAds",props:{carbonAds:{}},setup(o){const e=()=>null;return(t,n)=>(a(),c("div",Bt,[m(r(e),{"carbon-ads":t.carbonAds},null,8,["carbon-ads"])]))}}),Ft=o=>(C("data-v-3f215769"),o=o(),B(),o),Dt={class:"VPDocAside"},Ot=Ft(()=>u("div",{class:"spacer"},null,-1)),Ut=_({__name:"VPDocAside",setup(o){const{theme:e}=P();return(t,n)=>(a(),c("div",Dt,[l(t.$slots,"aside-top",{},void 0,!0),l(t.$slots,"aside-outline-before",{},void 0,!0),m(Ct),l(t.$slots,"aside-outline-after",{},void 0,!0),Ot,l(t.$slots,"aside-ads-before",{},void 0,!0),r(e).carbonAds?(a(),$(Et,{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)]))}}),Gt=b(Ut,[["__scopeId","data-v-3f215769"]]);function jt(){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 zt(){const{page:o,theme:e,frontmatter:t}=P();return y(()=>{var g,L,k,V,T,A,H,S;const n=Me(e.value.sidebar,o.value.relativePath),s=gt(n),i=qt(s,G=>G.link.replace(/[?#].*$/,"")),d=i.findIndex(G=>z(o.value.relativePath,G.link)),h=((g=e.value.docFooter)==null?void 0:g.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[d-1])==null?void 0:k.docFooterText)??((V=i[d-1])==null?void 0:V.text),link:(typeof t.value.prev=="object"?t.value.prev.link:void 0)??((T=i[d-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[d+1])==null?void 0:A.docFooterText)??((H=i[d+1])==null?void 0:H.text),link:(typeof t.value.next=="object"?t.value.next.link:void 0)??((S=i[d+1])==null?void 0:S.link)}}})}function qt(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&&Ve.test(e.href)||e.target==="_blank");return(s,i)=>(a(),$(W(t.value),{class:N(["VPLink",{link:s.href,"vp-external-link-icon":n.value,"no-icon":s.noIcon}]),href:s.href?r(_e)(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"]))}}),Kt={class:"VPLastUpdated"},Rt=["datetime"],Wt=_({__name:"VPDocFooterLastUpdated",setup(o){const{theme:e,page:t,frontmatter:n,lang:s}=P(),i=y(()=>new Date(n.value.lastUpdated??t.value.lastUpdated)),d=y(()=>i.value.toISOString()),h=I("");return q(()=>{ee(()=>{var p,g,L;h.value=new Intl.DateTimeFormat((g=(p=e.value.lastUpdated)==null?void 0:p.formatOptions)!=null&&g.forceLocale?s.value:void 0,((L=e.value.lastUpdated)==null?void 0:L.formatOptions)??{dateStyle:"short",timeStyle:"short"}).format(i.value)})}),(p,g)=>{var L;return a(),c("p",Kt,[E(w(((L=r(e).lastUpdated)==null?void 0:L.text)||r(e).lastUpdatedText||"Last updated")+": ",1),u("time",{datetime:d.value},w(h.value),9,Rt)])}}}),Yt=b(Wt,[["__scopeId","data-v-7e05ebdb"]]),Ce=o=>(C("data-v-d4a0bba5"),o=o(),B(),o),Jt={key:0,class:"VPDocFooter"},Xt={key:0,class:"edit-info"},Qt={key:0,class:"edit-link"},Zt=Ce(()=>u("span",{class:"vpi-square-pen edit-link-icon"},null,-1)),xt={key:1,class:"last-updated"},eo={key:1,class:"prev-next","aria-labelledby":"doc-footer-aria-label"},to=Ce(()=>u("span",{class:"visually-hidden",id:"doc-footer-aria-label"},"Pager",-1)),oo={class:"pager"},so=["innerHTML"],no=["innerHTML"],ao={class:"pager"},ro=["innerHTML"],io=["innerHTML"],lo=_({__name:"VPDocFooter",setup(o){const{theme:e,page:t,frontmatter:n}=P(),s=jt(),i=zt(),d=y(()=>e.value.editLink&&n.value.editLink!==!1),h=y(()=>t.value.lastUpdated&&n.value.lastUpdated!==!1),p=y(()=>d.value||h.value||i.value.prev||i.value.next);return(g,L)=>{var k,V,T,A;return p.value?(a(),c("footer",Jt,[l(g.$slots,"doc-footer-before",{},void 0,!0),d.value||h.value?(a(),c("div",Xt,[d.value?(a(),c("div",Qt,[m(D,{class:"edit-link-button",href:r(s).url,"no-icon":!0},{default:v(()=>[Zt,E(" "+w(r(s).text),1)]),_:1},8,["href"])])):f("",!0),h.value?(a(),c("div",xt,[m(Yt)])):f("",!0)])):f("",!0),(k=r(i).prev)!=null&&k.link||(V=r(i).next)!=null&&V.link?(a(),c("nav",eo,[to,u("div",oo,[(T=r(i).prev)!=null&&T.link?(a(),$(D,{key:0,class:"pager-link prev",href:r(i).prev.link},{default:v(()=>{var H;return[u("span",{class:"desc",innerHTML:((H=r(e).docFooter)==null?void 0:H.prev)||"Previous page"},null,8,so),u("span",{class:"title",innerHTML:r(i).prev.text},null,8,no)]}),_:1},8,["href"])):f("",!0)]),u("div",ao,[(A=r(i).next)!=null&&A.link?(a(),$(D,{key:0,class:"pager-link next",href:r(i).next.link},{default:v(()=>{var H;return[u("span",{class:"desc",innerHTML:((H=r(e).docFooter)==null?void 0:H.next)||"Next page"},null,8,ro),u("span",{class:"title",innerHTML:r(i).next.text},null,8,io)]}),_:1},8,["href"])):f("",!0)])])):f("",!0)])):f("",!0)}}}),co=b(lo,[["__scopeId","data-v-d4a0bba5"]]),uo=o=>(C("data-v-39a288b8"),o=o(),B(),o),vo={class:"container"},po=uo(()=>u("div",{class:"aside-curtain"},null,-1)),ho={class:"aside-container"},fo={class:"aside-content"},_o={class:"content"},mo={class:"content-container"},ko={class:"main"},bo=_({__name:"VPDoc",setup(o){const{theme:e}=P(),t=Y(),{hasSidebar:n,hasAside:s,leftAside:i}=U(),d=y(()=>t.path.replace(/[./]+/g,"_").replace(/_html$/,""));return(h,p)=>{const g=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),u("div",vo,[r(s)?(a(),c("div",{key:0,class:N(["aside",{"left-aside":r(i)}])},[po,u("div",ho,[u("div",fo,[m(Gt,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),u("div",_o,[u("div",mo,[l(h.$slots,"doc-before",{},void 0,!0),u("main",ko,[m(g,{class:N(["vp-doc",[d.value,r(e).externalLinkIcon&&"external-link-icon-enabled"]])},null,8,["class"])]),m(co,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(bo,[["__scopeId","data-v-39a288b8"]]),go=_({__name:"VPButton",props:{tag:{},size:{default:"medium"},theme:{default:"brand"},text:{},href:{},target:{},rel:{}},setup(o){const e=o,t=y(()=>e.href&&Ve.test(e.href)),n=y(()=>e.tag||e.href?"a":"button");return(s,i)=>(a(),$(W(n.value),{class:N(["VPButton",[s.size,s.theme]]),href:s.href?r(_e)(s.href):void 0,target:e.target??(t.value?"_blank":void 0),rel:e.rel??(t.value?"noreferrer":void 0)},{default:v(()=>[E(w(s.text),1)]),_:1},8,["class","href","target","rel"]))}}),yo=b(go,[["__scopeId","data-v-cad61b99"]]),Po=["src","alt"],Lo=_({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",Q({key:0,class:"VPImage"},typeof e.image=="string"?e.$attrs:{...e.image,...e.$attrs},{src:r(he)(typeof e.image=="string"?e.image:e.image.src),alt:e.alt??(typeof e.image=="string"?"":e.image.alt||"")}),null,16,Po)):(a(),c(M,{key:1},[m(n,Q({class:"dark",image:e.image.dark,alt:e.image.alt},e.$attrs),null,16,["image","alt"]),m(n,Q({class:"light",image:e.image.light,alt:e.image.alt},e.$attrs),null,16,["image","alt"])],64))],64)):f("",!0)}}}),x=b(Lo,[["__scopeId","data-v-8426fc1a"]]),Vo=o=>(C("data-v-303bb580"),o=o(),B(),o),So={class:"container"},wo={class:"main"},To={key:0,class:"name"},Io=["innerHTML"],No=["innerHTML"],Mo=["innerHTML"],Ao={key:0,class:"actions"},Ho={key:0,class:"image"},Co={class:"image-container"},Bo=Vo(()=>u("div",{class:"image-bg"},null,-1)),Eo=_({__name:"VPHero",props:{name:{},text:{},tagline:{},image:{},actions:{}},setup(o){const e=oe("hero-image-slot-exists");return(t,n)=>(a(),c("div",{class:N(["VPHero",{"has-image":t.image||r(e)}])},[u("div",So,[u("div",wo,[l(t.$slots,"home-hero-info-before",{},void 0,!0),l(t.$slots,"home-hero-info",{},()=>[t.name?(a(),c("h1",To,[u("span",{innerHTML:t.name,class:"clip"},null,8,Io)])):f("",!0),t.text?(a(),c("p",{key:1,innerHTML:t.text,class:"text"},null,8,No)):f("",!0),t.tagline?(a(),c("p",{key:2,innerHTML:t.tagline,class:"tagline"},null,8,Mo)):f("",!0)],!0),l(t.$slots,"home-hero-info-after",{},void 0,!0),t.actions?(a(),c("div",Ao,[(a(!0),c(M,null,F(t.actions,s=>(a(),c("div",{key:s.link,class:"action"},[m(yo,{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",Ho,[u("div",Co,[Bo,l(t.$slots,"home-hero-image",{},()=>[t.image?(a(),$(x,{key:0,class:"image-src",image:t.image},null,8,["image"])):f("",!0)],!0)])])):f("",!0)])],2))}}),Fo=b(Eo,[["__scopeId","data-v-303bb580"]]),Do=_({__name:"VPHomeHero",setup(o){const{frontmatter:e}=P();return(t,n)=>r(e).hero?(a(),$(Fo,{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)}}),Oo=o=>(C("data-v-a3976bdc"),o=o(),B(),o),Uo={class:"box"},Go={key:0,class:"icon"},jo=["innerHTML"],zo=["innerHTML"],qo=["innerHTML"],Ko={key:4,class:"link-text"},Ro={class:"link-text-value"},Wo=Oo(()=>u("span",{class:"vpi-arrow-right link-text-icon"},null,-1)),Yo=_({__name:"VPFeature",props:{icon:{},title:{},details:{},link:{},linkText:{},rel:{},target:{}},setup(o){return(e,t)=>(a(),$(D,{class:"VPFeature",href:e.link,rel:e.rel,target:e.target,"no-icon":!0,tag:e.link?"a":"div"},{default:v(()=>[u("article",Uo,[typeof e.icon=="object"&&e.icon.wrap?(a(),c("div",Go,[m(x,{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(),$(x,{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,jo)):f("",!0),u("h2",{class:"title",innerHTML:e.title},null,8,zo),e.details?(a(),c("p",{key:3,class:"details",innerHTML:e.details},null,8,qo)):f("",!0),e.linkText?(a(),c("div",Ko,[u("p",Ro,[E(w(e.linkText)+" ",1),Wo])])):f("",!0)])]),_:1},8,["href","rel","target","tag"]))}}),Jo=b(Yo,[["__scopeId","data-v-a3976bdc"]]),Xo={key:0,class:"VPFeatures"},Qo={class:"container"},Zo={class:"items"},xo=_({__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",Xo,[u("div",Qo,[u("div",Zo,[(a(!0),c(M,null,F(n.features,i=>(a(),c("div",{key:i.title,class:N(["item",[t.value]])},[m(Jo,{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)}}),es=b(xo,[["__scopeId","data-v-a6181336"]]),ts=_({__name:"VPHomeFeatures",setup(o){const{frontmatter:e}=P();return(t,n)=>r(e).features?(a(),$(es,{key:0,class:"VPHomeFeatures",features:r(e).features},null,8,["features"])):f("",!0)}}),os=_({__name:"VPHomeContent",setup(o){const{width:e}=Ye({initialWidth:0,includeScrollbar:!1});return(t,n)=>(a(),c("div",{class:"vp-doc container",style:Se(r(e)?{"--vp-offset":`calc(50% - ${r(e)/2}px)`}:{})},[l(t.$slots,"default",{},void 0,!0)],4))}}),ss=b(os,[["__scopeId","data-v-8e2d4988"]]),ns={class:"VPHome"},as=_({__name:"VPHome",setup(o){const{frontmatter:e}=P();return(t,n)=>{const s=K("Content");return a(),c("div",ns,[l(t.$slots,"home-hero-before",{},void 0,!0),m(Do,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(ts),l(t.$slots,"home-features-after",{},void 0,!0),r(e).markdownStyles!==!1?(a(),$(ss,{key:0},{default:v(()=>[m(s)]),_:1})):(a(),$(s,{key:1}))])}}}),rs=b(as,[["__scopeId","data-v-686f80a6"]]),is={},ls={class:"VPPage"};function cs(o,e){const t=K("Content");return a(),c("div",ls,[l(o.$slots,"page-top"),m(t),l(o.$slots,"page-bottom")])}const us=b(is,[["render",cs]]),ds=_({__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(bt)],!0):r(t).layout==="page"?(a(),$(us,{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(),$(rs,{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(),$(W(r(t).layout),{key:3})):(a(),$($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))}}),vs=b(ds,[["__scopeId","data-v-1428d186"]]),ps={class:"container"},hs=["innerHTML"],fs=["innerHTML"],_s=_({__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)}])},[u("div",ps,[r(e).footer.message?(a(),c("p",{key:0,class:"message",innerHTML:r(e).footer.message},null,8,hs)):f("",!0),r(e).footer.copyright?(a(),c("p",{key:1,class:"copyright",innerHTML:r(e).footer.copyright},null,8,fs)):f("",!0)])],2)):f("",!0)}}),ms=b(_s,[["__scopeId","data-v-e315a0ad"]]);function ks(){const{theme:o,frontmatter:e}=P(),t=Le([]),n=y(()=>t.value.length>0);return te(()=>{t.value=me(e.value.outline??o.value.outline)}),{headers:t,hasLocalNav:n}}const bs=o=>(C("data-v-17a5e62e"),o=o(),B(),o),$s={class:"menu-text"},gs=bs(()=>u("span",{class:"vpi-chevron-right icon"},null,-1)),ys={class:"header"},Ps={class:"outline"},Ls=_({__name:"VPLocalNavOutlineDropdown",props:{headers:{},navHeight:{}},setup(o){const e=o,{theme:t}=P(),n=I(!1),s=I(0),i=I(),d=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)}),ce("Escape",()=>{n.value=!1}),te(()=>{n.value=!1});function p(){n.value=!n.value,s.value=window.innerHeight+Math.min(window.scrollY-e.navHeight,0)}function g(k){k.target.classList.contains("outline-link")&&(d.value&&(d.value.style.transition="none"),we(()=>{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:Se({"--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})},[u("span",$s,w(r(Ae)(r(t))),1),gs],2)):(a(),c("button",{key:1,onClick:L},w(r(t).returnToTopLabel||"Return to top"),1)),m(pe,{name:"flyout"},{default:v(()=>[n.value?(a(),c("div",{key:0,ref_key:"items",ref:d,class:"items",onClick:g},[u("div",ys,[u("a",{class:"top-link",href:"#",onClick:L},w(r(t).returnToTopLabel||"Return to top"),1)]),u("div",Ps,[m(He,{headers:k.headers},null,8,["headers"])])],512)):f("",!0)]),_:1})],4))}}),Vs=b(Ls,[["__scopeId","data-v-17a5e62e"]]),Ss=o=>(C("data-v-a6f0e41e"),o=o(),B(),o),ws={class:"container"},Ts=["aria-expanded"],Is=Ss(()=>u("span",{class:"vpi-align-left menu-icon"},null,-1)),Ns={class:"menu-text"},Ms=_({__name:"VPLocalNav",props:{open:{type:Boolean}},emits:["open-menu"],setup(o){const{theme:e,frontmatter:t}=P(),{hasSidebar:n}=U(),{headers:s}=ks(),{y:i}=Te(),d=I(0);q(()=>{d.value=parseInt(getComputedStyle(document.documentElement).getPropertyValue("--vp-nav-height"))}),te(()=>{s.value=me(t.value.outline??e.value.outline)});const h=y(()=>s.value.length===0),p=y(()=>h.value&&!n.value),g=y(()=>({VPLocalNav:!0,"has-sidebar":n.value,empty:h.value,fixed:p.value}));return(L,k)=>r(t).layout!=="home"&&(!p.value||r(i)>=d.value)?(a(),c("div",{key:0,class:N(g.value)},[u("div",ws,[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"))},[Is,u("span",Ns,w(r(e).sidebarMenuLabel||"Menu"),1)],8,Ts)):f("",!0),m(Vs,{headers:r(s),navHeight:d.value},null,8,["headers","navHeight"])])],2)):f("",!0)}}),As=b(Ms,[["__scopeId","data-v-a6f0e41e"]]);function Hs(){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 Cs={},Bs={class:"VPSwitch",type:"button",role:"switch"},Es={class:"check"},Fs={key:0,class:"icon"};function Ds(o,e){return a(),c("button",Bs,[u("span",Es,[o.$slots.default?(a(),c("span",Fs,[l(o.$slots,"default",{},void 0,!0)])):f("",!0)])])}const Os=b(Cs,[["render",Ds],["__scopeId","data-v-1d5665e3"]]),Be=o=>(C("data-v-d1f28634"),o=o(),B(),o),Us=Be(()=>u("span",{class:"vpi-sun sun"},null,-1)),Gs=Be(()=>u("span",{class:"vpi-moon moon"},null,-1)),js=_({__name:"VPSwitchAppearance",setup(o){const{isDark:e,theme:t}=P(),n=oe("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,d)=>(a(),$(Os,{title:s.value,class:"VPSwitchAppearance","aria-checked":r(e),onClick:r(n)},{default:v(()=>[Us,Gs]),_:1},8,["title","aria-checked","onClick"]))}}),ke=b(js,[["__scopeId","data-v-d1f28634"]]),zs={key:0,class:"VPNavBarAppearance"},qs=_({__name:"VPNavBarAppearance",setup(o){const{site:e}=P();return(t,n)=>r(e).appearance&&r(e).appearance!=="force-dark"?(a(),c("div",zs,[m(ke)])):f("",!0)}}),Ks=b(qs,[["__scopeId","data-v-e6aabb21"]]),be=I();let Ee=!1,ie=0;function Rs(o){const e=I(!1);if(se){!Ee&&Ws(),ie++;const t=O(be,n=>{var s,i,d;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,(d=o.onBlur)==null||d.call(o))});fe(()=>{t(),ie--,ie||Ys()})}return Je(e)}function Ws(){document.addEventListener("focusin",Fe),Ee=!0,be.value=document.activeElement}function Ys(){document.removeEventListener("focusin",Fe)}function Fe(){be.value=document.activeElement}const Js={class:"VPMenuLink"},Xs=_({__name:"VPMenuLink",props:{item:{}},setup(o){const{page:e}=P();return(t,n)=>(a(),c("div",Js,[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(w(t.item.text),1)]),_:1},8,["class","href","target","rel"])]))}}),ne=b(Xs,[["__scopeId","data-v-43f1e123"]]),Qs={class:"VPMenuGroup"},Zs={key:0,class:"title"},xs=_({__name:"VPMenuGroup",props:{text:{},items:{}},setup(o){return(e,t)=>(a(),c("div",Qs,[e.text?(a(),c("p",Zs,w(e.text),1)):f("",!0),(a(!0),c(M,null,F(e.items,n=>(a(),c(M,null,["link"in n?(a(),$(ne,{key:0,item:n},null,8,["item"])):f("",!0)],64))),256))]))}}),en=b(xs,[["__scopeId","data-v-69e747b5"]]),tn={class:"VPMenu"},on={key:0,class:"items"},sn=_({__name:"VPMenu",props:{items:{}},setup(o){return(e,t)=>(a(),c("div",tn,[e.items?(a(),c("div",on,[(a(!0),c(M,null,F(e.items,n=>(a(),c(M,{key:n.text},["link"in n?(a(),$(ne,{key:0,item:n},null,8,["item"])):(a(),$(en,{key:1,text:n.text,items:n.items},null,8,["text","items"]))],64))),128))])):f("",!0),l(e.$slots,"default",{},void 0,!0)]))}}),nn=b(sn,[["__scopeId","data-v-e7ea1737"]]),an=o=>(C("data-v-b6c34ac9"),o=o(),B(),o),rn=["aria-expanded","aria-label"],ln={key:0,class:"text"},cn=["innerHTML"],un=an(()=>u("span",{class:"vpi-chevron-down text-icon"},null,-1)),dn={key:1,class:"vpi-more-horizontal icon"},vn={class:"menu"},pn=_({__name:"VPFlyout",props:{icon:{},button:{},label:{},items:{}},setup(o){const e=I(!1),t=I();Rs({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]=d=>e.value=!0),onMouseleave:i[2]||(i[2]=d=>e.value=!1)},[u("button",{type:"button",class:"button","aria-haspopup":"true","aria-expanded":e.value,"aria-label":s.label,onClick:i[0]||(i[0]=d=>e.value=!e.value)},[s.button||s.icon?(a(),c("span",ln,[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,cn)):f("",!0),un])):(a(),c("span",dn))],8,rn),u("div",vn,[m(nn,{items:s.items},{default:v(()=>[l(s.$slots,"default",{},void 0,!0)]),_:3},8,["items"])])],544))}}),$e=b(pn,[["__scopeId","data-v-b6c34ac9"]]),hn=["href","aria-label","innerHTML"],fn=_({__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,hn))}}),_n=b(fn,[["__scopeId","data-v-eee4e7cb"]]),mn={class:"VPSocialLinks"},kn=_({__name:"VPSocialLinks",props:{links:{}},setup(o){return(e,t)=>(a(),c("div",mn,[(a(!0),c(M,null,F(e.links,({link:n,icon:s,ariaLabel:i})=>(a(),$(_n,{key:n,icon:s,link:n,ariaLabel:i},null,8,["icon","link","ariaLabel"]))),128))]))}}),ge=b(kn,[["__scopeId","data-v-7bc22406"]]),bn={key:0,class:"group translations"},$n={class:"trans-title"},gn={key:1,class:"group"},yn={class:"item appearance"},Pn={class:"label"},Ln={class:"appearance-action"},Vn={key:2,class:"group"},Sn={class:"item social-links"},wn=_({__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(d,h)=>i.value?(a(),$($e,{key:0,class:"VPNavBarExtra",label:"extra navigation"},{default:v(()=>[r(n).length&&r(s).label?(a(),c("div",bn,[u("p",$n,w(r(s).label),1),(a(!0),c(M,null,F(r(n),p=>(a(),$(ne,{key:p.link,item:p},null,8,["item"]))),128))])):f("",!0),r(e).appearance&&r(e).appearance!=="force-dark"?(a(),c("div",gn,[u("div",yn,[u("p",Pn,w(r(t).darkModeSwitchLabel||"Appearance"),1),u("div",Ln,[m(ke)])])])):f("",!0),r(t).socialLinks?(a(),c("div",Vn,[u("div",Sn,[m(ge,{class:"social-links-list",links:r(t).socialLinks},null,8,["links"])])])):f("",!0)]),_:1})):f("",!0)}}),Tn=b(wn,[["__scopeId","data-v-d0bd9dde"]]),In=o=>(C("data-v-e5dd9c1c"),o=o(),B(),o),Nn=["aria-expanded"],Mn=In(()=>u("span",{class:"container"},[u("span",{class:"top"}),u("span",{class:"middle"}),u("span",{class:"bottom"})],-1)),An=[Mn],Hn=_({__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"))},An,10,Nn))}}),Cn=b(Hn,[["__scopeId","data-v-e5dd9c1c"]]),Bn=["innerHTML"],En=_({__name:"VPNavBarMenuLink",props:{item:{}},setup(o){const{page:e}=P();return(t,n)=>(a(),$(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(()=>[u("span",{innerHTML:t.item.text},null,8,Bn)]),_:1},8,["class","href","noIcon","target","rel"]))}}),Fn=b(En,[["__scopeId","data-v-9c663999"]]),Dn=_({__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,d)=>(a(),$($e,{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"]))}}),On=o=>(C("data-v-7f418b0f"),o=o(),B(),o),Un={key:0,"aria-labelledby":"main-nav-aria-label",class:"VPNavBarMenu"},Gn=On(()=>u("span",{id:"main-nav-aria-label",class:"visually-hidden"},"Main Navigation",-1)),jn=_({__name:"VPNavBarMenu",setup(o){const{theme:e}=P();return(t,n)=>r(e).nav?(a(),c("nav",Un,[Gn,(a(!0),c(M,null,F(r(e).nav,s=>(a(),c(M,{key:s.text},["link"in s?(a(),$(Fn,{key:0,item:s},null,8,["item"])):(a(),$(Dn,{key:1,item:s},null,8,["item"]))],64))),128))])):f("",!0)}}),zn=b(jn,[["__scopeId","data-v-7f418b0f"]]);function qn(o){const{localeIndex:e,theme:t}=P();function n(s){var A,H,S;const i=s.split("."),d=(A=t.value.search)==null?void 0:A.options,h=d&&typeof d=="object",p=h&&((S=(H=d.locales)==null?void 0:H[e.value])==null?void 0:S.translations)||null,g=h&&d.translations||null;let L=p,k=g,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 ae=k==null?void 0:k[G];ae&&(j=k=ae);const re=L==null?void 0:L[G];re&&(j=L=re),R||(V=j),ae||(k=j),re||(L=j)}return(L==null?void 0:L[T])??(k==null?void 0:k[T])??(V==null?void 0:V[T])??""}return n}const Kn=["aria-label"],Rn={class:"DocSearch-Button-Container"},Wn=u("span",{class:"vp-icon DocSearch-Search-Icon"},null,-1),Yn={class:"DocSearch-Button-Placeholder"},Jn=u("span",{class:"DocSearch-Button-Keys"},[u("kbd",{class:"DocSearch-Button-Key"}),u("kbd",{class:"DocSearch-Button-Key"},"K")],-1),ye=_({__name:"VPNavBarSearchButton",setup(o){const t=qn({button:{buttonText:"Search",buttonAriaLabel:"Search"}});return(n,s)=>(a(),c("button",{type:"button",class:"DocSearch DocSearch-Button","aria-label":r(t)("button.buttonAriaLabel")},[u("span",Rn,[Wn,u("span",Yn,w(r(t)("button.buttonText")),1)]),Jn],8,Kn))}}),Xn={class:"VPNavBarSearch"},Qn={id:"local-search"},Zn={key:1,id:"docsearch"},xn=_({__name:"VPNavBarSearch",setup(o){const e=Xe(()=>Qe(()=>import("./VPLocalSearchBox.D1yhhzqU.js"),__vite__mapDeps([0,1]))),t=()=>null,{theme:n}=P(),s=I(!1),i=I(!1);q(()=>{});function d(){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 g=I(!1);ce("k",k=>{(k.ctrlKey||k.metaKey)&&(k.preventDefault(),g.value=!0)}),ce("/",k=>{p(k)||(k.preventDefault(),g.value=!0)});const L="local";return(k,V)=>{var T;return a(),c("div",Xn,[r(L)==="local"?(a(),c(M,{key:0},[g.value?(a(),$(r(e),{key:0,onClose:V[0]||(V[0]=A=>g.value=!1)})):f("",!0),u("div",Qn,[m(ye,{onClick:V[1]||(V[1]=A=>g.value=!0)})])],64)):r(L)==="algolia"?(a(),c(M,{key:1},[s.value?(a(),$(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",Zn,[m(ye,{onClick:d})]))],64)):f("",!0)])}}}),ea=_({__name:"VPNavBarSocialLinks",setup(o){const{theme:e}=P();return(t,n)=>r(e).socialLinks?(a(),$(ge,{key:0,class:"VPNavBarSocialLinks",links:r(e).socialLinks},null,8,["links"])):f("",!0)}}),ta=b(ea,[["__scopeId","data-v-0394ad82"]]),oa=["href","rel","target"],sa={key:1},na={key:2},aa=_({__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}),d=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,g)=>(a(),c("div",{class:N(["VPNavBarTitle",{"has-sidebar":r(n)}])},[u("a",{class:"title",href:i.value??r(_e)(r(s).link),rel:d.value,target:h.value},[l(p.$slots,"nav-bar-title-before",{},void 0,!0),r(t).logo?(a(),$(x,{key:0,class:"logo",image:r(t).logo},null,8,["image"])):f("",!0),r(t).siteTitle?(a(),c("span",sa,w(r(t).siteTitle),1)):r(t).siteTitle===void 0?(a(),c("span",na,w(r(e).title),1)):f("",!0),l(p.$slots,"nav-bar-title-after",{},void 0,!0)],8,oa)],2))}}),ra=b(aa,[["__scopeId","data-v-ab179fa1"]]),ia={class:"items"},la={class:"title"},ca=_({__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(),$($e,{key:0,class:"VPNavBarTranslations",icon:"vpi-languages",label:r(e).langMenuLabel||"Change language"},{default:v(()=>[u("div",ia,[u("p",la,w(r(n).label),1),(a(!0),c(M,null,F(r(t),d=>(a(),$(ne,{key:d.link,item:d},null,8,["item"]))),128))])]),_:1},8,["label"])):f("",!0)}}),ua=b(ca,[["__scopeId","data-v-88af2de4"]]),da=o=>(C("data-v-ccf7ddec"),o=o(),B(),o),va={class:"wrapper"},pa={class:"container"},ha={class:"title"},fa={class:"content"},_a={class:"content-body"},ma=da(()=>u("div",{class:"divider"},[u("div",{class:"divider-line"})],-1)),ka=_({__name:"VPNavBar",props:{isScreenOpen:{type:Boolean}},emits:["toggle-screen"],setup(o){const{y:e}=Te(),{hasSidebar:t}=U(),{frontmatter:n}=P(),s=I({});return Pe(()=>{s.value={"has-sidebar":t.value,home:n.value.layout==="home",top:e.value===0}}),(i,d)=>(a(),c("div",{class:N(["VPNavBar",s.value])},[u("div",va,[u("div",pa,[u("div",ha,[m(ra,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})]),u("div",fa,[u("div",_a,[l(i.$slots,"nav-bar-content-before",{},void 0,!0),m(xn,{class:"search"}),m(zn,{class:"menu"}),m(ua,{class:"translations"}),m(Ks,{class:"appearance"}),m(ta,{class:"social-links"}),m(Tn,{class:"extra"}),l(i.$slots,"nav-bar-content-after",{},void 0,!0),m(Cn,{class:"hamburger",active:i.isScreenOpen,onClick:d[0]||(d[0]=h=>i.$emit("toggle-screen"))},null,8,["active"])])])])]),ma],2))}}),ba=b(ka,[["__scopeId","data-v-ccf7ddec"]]),$a={key:0,class:"VPNavScreenAppearance"},ga={class:"text"},ya=_({__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,[u("p",ga,w(r(t).darkModeSwitchLabel||"Appearance"),1),m(ke)])):f("",!0)}}),Pa=b(ya,[["__scopeId","data-v-2d7af913"]]),La=_({__name:"VPNavScreenMenuLink",props:{item:{}},setup(o){const e=oe("close-screen");return(t,n)=>(a(),$(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"]))}}),Va=b(La,[["__scopeId","data-v-7f31e1f6"]]),Sa=_({__name:"VPNavScreenMenuGroupLink",props:{item:{}},setup(o){const e=oe("close-screen");return(t,n)=>(a(),$(D,{class:"VPNavScreenMenuGroupLink",href:t.item.link,target:t.item.target,rel:t.item.rel,onClick:r(e)},{default:v(()=>[E(w(t.item.text),1)]),_:1},8,["href","target","rel","onClick"]))}}),De=b(Sa,[["__scopeId","data-v-19976ae1"]]),wa={class:"VPNavScreenMenuGroupSection"},Ta={key:0,class:"title"},Ia=_({__name:"VPNavScreenMenuGroupSection",props:{text:{},items:{}},setup(o){return(e,t)=>(a(),c("div",wa,[e.text?(a(),c("p",Ta,w(e.text),1)):f("",!0),(a(!0),c(M,null,F(e.items,n=>(a(),$(De,{key:n.text,item:n},null,8,["item"]))),128))]))}}),Na=b(Ia,[["__scopeId","data-v-8133b170"]]),Ma=o=>(C("data-v-ff6087d4"),o=o(),B(),o),Aa=["aria-controls","aria-expanded"],Ha=["innerHTML"],Ca=Ma(()=>u("span",{class:"vpi-plus button-icon"},null,-1)),Ba=["id"],Ea={key:1,class:"group"},Fa=_({__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,d)=>(a(),c("div",{class:N(["VPNavScreenMenuGroup",{open:t.value}])},[u("button",{class:"button","aria-controls":n.value,"aria-expanded":t.value,onClick:s},[u("span",{class:"button-text",innerHTML:i.text},null,8,Ha),Ca],8,Aa),u("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(De,{item:h},null,8,["item"])])):(a(),c("div",Ea,[m(Na,{text:h.text,items:h.items},null,8,["text","items"])]))],64))),128))],8,Ba)],2))}}),Da=b(Fa,[["__scopeId","data-v-ff6087d4"]]),Oa={key:0,class:"VPNavScreenMenu"},Ua=_({__name:"VPNavScreenMenu",setup(o){const{theme:e}=P();return(t,n)=>r(e).nav?(a(),c("nav",Oa,[(a(!0),c(M,null,F(r(e).nav,s=>(a(),c(M,{key:s.text},["link"in s?(a(),$(Va,{key:0,item:s},null,8,["item"])):(a(),$(Da,{key:1,text:s.text||"",items:s.items},null,8,["text","items"]))],64))),128))])):f("",!0)}}),Ga=_({__name:"VPNavScreenSocialLinks",setup(o){const{theme:e}=P();return(t,n)=>r(e).socialLinks?(a(),$(ge,{key:0,class:"VPNavScreenSocialLinks",links:r(e).socialLinks},null,8,["links"])):f("",!0)}}),Oe=o=>(C("data-v-858fe1a4"),o=o(),B(),o),ja=Oe(()=>u("span",{class:"vpi-languages icon lang"},null,-1)),za=Oe(()=>u("span",{class:"vpi-chevron-down icon chevron"},null,-1)),qa={class:"list"},Ka=_({__name:"VPNavScreenTranslations",setup(o){const{localeLinks:e,currentLang:t}=J({correspondingLink:!0}),n=I(!1);function s(){n.value=!n.value}return(i,d)=>r(e).length&&r(t).label?(a(),c("div",{key:0,class:N(["VPNavScreenTranslations",{open:n.value}])},[u("button",{class:"title",onClick:s},[ja,E(" "+w(r(t).label)+" ",1),za]),u("ul",qa,[(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(w(h.text),1)]),_:2},1032,["href"])]))),128))])],2)):f("",!0)}}),Ra=b(Ka,[["__scopeId","data-v-858fe1a4"]]),Wa={class:"container"},Ya=_({__name:"VPNavScreen",props:{open:{type:Boolean}},setup(o){const e=I(null),t=Ie(se?document.body:null);return(n,s)=>(a(),$(pe,{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"},[u("div",Wa,[l(n.$slots,"nav-screen-content-before",{},void 0,!0),m(Ua,{class:"menu"}),m(Ra,{class:"translations"}),m(Pa,{class:"appearance"}),m(Ga,{class:"social-links"}),l(n.$slots,"nav-screen-content-after",{},void 0,!0)])],512)):f("",!0)]),_:3}))}}),Ja=b(Ya,[["__scopeId","data-v-cc5739dd"]]),Xa={key:0,class:"VPNav"},Qa=_({__name:"VPNav",setup(o){const{isScreenOpen:e,closeScreen:t,toggleScreen:n}=Hs(),{frontmatter:s}=P(),i=y(()=>s.value.navbar!==!1);return Ne("close-screen",t),ee(()=>{se&&document.documentElement.classList.toggle("hide-nav",!i.value)}),(d,h)=>i.value?(a(),c("header",Xa,[m(ba,{"is-screen-open":r(e),onToggleScreen:r(n)},{"nav-bar-title-before":v(()=>[l(d.$slots,"nav-bar-title-before",{},void 0,!0)]),"nav-bar-title-after":v(()=>[l(d.$slots,"nav-bar-title-after",{},void 0,!0)]),"nav-bar-content-before":v(()=>[l(d.$slots,"nav-bar-content-before",{},void 0,!0)]),"nav-bar-content-after":v(()=>[l(d.$slots,"nav-bar-content-after",{},void 0,!0)]),_:3},8,["is-screen-open","onToggleScreen"]),m(Ja,{open:r(e)},{"nav-screen-content-before":v(()=>[l(d.$slots,"nav-screen-content-before",{},void 0,!0)]),"nav-screen-content-after":v(()=>[l(d.$slots,"nav-screen-content-after",{},void 0,!0)]),_:3},8,["open"])])):f("",!0)}}),Za=b(Qa,[["__scopeId","data-v-ae24b3ad"]]),Ue=o=>(C("data-v-b8d55f3b"),o=o(),B(),o),xa=["role","tabindex"],er=Ue(()=>u("div",{class:"indicator"},null,-1)),tr=["onKeydown"],or=Ue(()=>u("span",{class:"vpi-chevron-right caret-icon"},null,-1)),sr=[or],nr={key:1,class:"items"},ar=_({__name:"VPSidebarItem",props:{item:{},depth:{}},setup(o){const e=o,{collapsed:t,collapsible:n,isLink:s,isActiveLink:i,hasActiveLink:d,hasChildren:h,toggle:p}=Pt(y(()=>e.item)),g=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":d.value}]);function A(S){"key"in S&&S.key!=="Enter"||!e.item.link&&p()}function H(){e.item.link&&p()}return(S,G)=>{const j=K("VPSidebarItem",!0);return a(),$(W(g.value),{class:N(["VPSidebarItem",T.value])},{default:v(()=>[S.item.text?(a(),c("div",Q({key:0,class:"item",role:V.value},xe(S.item.items?{click:A,keydown:A}:{},!0),{tabindex:S.item.items&&0}),[er,S.item.link?(a(),$(D,{key:0,tag:L.value,class:"link",href:S.item.link,rel:S.item.rel,target:S.item.target},{default:v(()=>[(a(),$(W(k.value),{class:"text",innerHTML:S.item.text},null,8,["innerHTML"]))]),_:1},8,["tag","href","rel","target"])):(a(),$(W(k.value),{key:1,class:"text",innerHTML:S.item.text},null,8,["innerHTML"])),S.item.collapsed!=null&&S.item.items&&S.item.items.length?(a(),c("div",{key:2,class:"caret",role:"button","aria-label":"toggle section",onClick:H,onKeydown:Ze(H,["enter"]),tabindex:"0"},sr,40,tr)):f("",!0)],16,xa)):f("",!0),S.item.items&&S.item.items.length?(a(),c("div",nr,[S.depth<5?(a(!0),c(M,{key:0},F(S.item.items,R=>(a(),$(j,{key:R.text,item:R,depth:S.depth+1},null,8,["item","depth"]))),128)):f("",!0)])):f("",!0)]),_:1},8,["class"])}}}),rr=b(ar,[["__scopeId","data-v-b8d55f3b"]]),Ge=o=>(C("data-v-575e6a36"),o=o(),B(),o),ir=Ge(()=>u("div",{class:"curtain"},null,-1)),lr={class:"nav",id:"VPSidebarNav","aria-labelledby":"sidebar-aria-label",tabindex:"-1"},cr=Ge(()=>u("span",{class:"visually-hidden",id:"sidebar-aria-label"}," Sidebar Navigation ",-1)),ur=_({__name:"VPSidebar",props:{open:{type:Boolean}},setup(o){const e=o,{sidebarGroups:t,hasSidebar:n}=U(),s=I(null),i=Ie(se?document.body:null);return O([e,s],()=>{var d;e.open?(i.value=!0,(d=s.value)==null||d.focus()):i.value=!1},{immediate:!0,flush:"post"}),(d,h)=>r(n)?(a(),c("aside",{key:0,class:N(["VPSidebar",{open:d.open}]),ref_key:"navEl",ref:s,onClick:h[0]||(h[0]=et(()=>{},["stop"]))},[ir,u("nav",lr,[cr,l(d.$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(rr,{item:p,depth:0},null,8,["item"])]))),128)),l(d.$slots,"sidebar-nav-after",{},void 0,!0)])],2)):f("",!0)}}),dr=b(ur,[["__scopeId","data-v-575e6a36"]]),vr=_({__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 d=()=>{i.removeAttribute("tabindex"),i.removeEventListener("blur",d)};i.setAttribute("tabindex","-1"),i.addEventListener("blur",d),i.focus(),window.scrollTo(0,0)}}return(s,i)=>(a(),c(M,null,[u("span",{ref_key:"backToTop",ref:t,tabindex:"-1"},null,512),u("a",{href:"#VPContent",class:"VPSkipLink visually-hidden",onClick:n}," Skip to content ")],64))}}),pr=b(vr,[["__scopeId","data-v-0f60ec36"]]),hr=_({__name:"Layout",setup(o){const{isOpen:e,open:t,close:n}=U(),s=Y();O(()=>s.path,n),yt(e,n);const{frontmatter:i}=P(),d=tt(),h=y(()=>!!d["home-hero-image"]);return Ne("hero-image-slot-exists",h),(p,g)=>{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(pr),m(it,{class:"backdrop",show:r(e),onClick:r(n)},null,8,["show","onClick"]),m(Za,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(As,{open:r(e),onOpenMenu:r(t)},null,8,["open","onOpenMenu"]),m(dr,{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(vs,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(ms),l(p.$slots,"layout-bottom",{},void 0,!0)],2)):(a(),$(L,{key:1}))}}}),fr=b(hr,[["__scopeId","data-v-5d98c3a5"]]),je={Layout:fr,enhanceApp:({app:o})=>{o.component("Badge",nt)}},_r=_({__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 we(),e()}),ot("hashchange",e),(n,s)=>l(n.$slots,"default")}}),X=o=>(C("data-v-a3638063"),o=o(),B(),o),mr={class:"vp-doc"},kr=X(()=>u("a",{class:"h-card u-uid",href:"/about"},[u("img",{src:st,alt:""}),E("The Paper Pilot")],-1)),br=X(()=>u("a",{rel:"license",href:"https://creativecommons.org/licenses/by-nc-sa/4.0/"},"CC BY-NC-SA 4.0",-1)),$r=X(()=>u("div",null,"Any and all opinions listed here are my own and not representative of my employers; future, past and present.",-1)),gr=X(()=>u("div",null,[u("a",{href:"https://resume.incremental.social/thepaperpilot/thepaperpilot"},"Resume"),E(" (not actively seeking new opportunities).")],-1)),yr=X(()=>u("div",null,[E("Site built from "),u("a",{href:"https://code.incremental.social/thepaperpilot/pages/commit/02d825340d380a7e08f1650ac0a684985997fea5"},"this commit"),E(" on "),u("time",null,"Tuesday, June 18, 2024 at 12:53:34"),E(".")],-1)),Pr=_({__name:"Layout",setup(o){return(e,t)=>(a(),$(r(je).Layout,null,{"layout-top":v(()=>[m(r(_r))]),"layout-bottom":v(()=>[u("footer",mr,[u("div",null,[E("CC "+w(new Date().getFullYear())+" ",1),kr,E(". "),br,E(".")]),$r,gr,yr])]),_:1}))}}),Lr=b(Pr,[["__scopeId","data-v-a3638063"]]),Sr={...je,Layout:Lr};export{Sr as R,qn as c,P as u}; diff --git a/assets/garden_activitypub_index.md.Dv6GWpX1.js b/assets/garden_activitypub_index.md.mGHaIpWs.js similarity index 94% rename from assets/garden_activitypub_index.md.Dv6GWpX1.js rename to assets/garden_activitypub_index.md.mGHaIpWs.js index 6a50f581..fedeb67d 100644 --- a/assets/garden_activitypub_index.md.Dv6GWpX1.js +++ b/assets/garden_activitypub_index.md.mGHaIpWs.js @@ -1 +1 @@ -import{d as i}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as s,j as e,a as t,k as a,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"ActivityPub",-1),o=["innerHTML"],d=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/fediverse/"},"Fediverse")])],-1),p=e("blockquote",null,[e("p",null,[t("Tags: "),e("a",{href:"/garden/decentralized/"},"Decentralized")])],-1),_=e("p",null,[e("a",{href:"https://activitypub.rocks",target:"_blank",rel:"noreferrer"},"ActivityPub"),t(" is a protocol for "),e("a",{href:"/garden/fediverse/"},"Federated Social Media")],-1),y=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"}'),f={name:"garden/activitypub/index.md"},k=Object.assign(f,{setup(h){const r=n();return(v,b)=>(l(),s("div",null,[c,e("p",null,[t("8 words, ~0 minute read. "),e("span",{innerHTML:a(i)[`site/${a(r).page.value.relativePath}`]},null,8,o)]),d,u,p,_]))}});export{y as __pageData,k as default}; +import{d as i}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as s,j as e,a as t,k as a,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"ActivityPub",-1),o=["innerHTML"],d=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/fediverse/"},"Fediverse")])],-1),p=e("blockquote",null,[e("p",null,[t("Tags: "),e("a",{href:"/garden/decentralized/"},"Decentralized")])],-1),_=e("p",null,[e("a",{href:"https://activitypub.rocks",target:"_blank",rel:"noreferrer"},"ActivityPub"),t(" is a protocol for "),e("a",{href:"/garden/fediverse/"},"Federated Social Media")],-1),y=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"}'),f={name:"garden/activitypub/index.md"},k=Object.assign(f,{setup(h){const r=n();return(v,b)=>(l(),s("div",null,[c,e("p",null,[t("8 words, ~0 minute read. "),e("span",{innerHTML:a(i)[`site/${a(r).page.value.relativePath}`]},null,8,o)]),d,u,p,_]))}});export{y as __pageData,k as default}; diff --git a/assets/garden_activitypub_index.md.Dv6GWpX1.lean.js b/assets/garden_activitypub_index.md.mGHaIpWs.lean.js similarity index 94% rename from assets/garden_activitypub_index.md.Dv6GWpX1.lean.js rename to assets/garden_activitypub_index.md.mGHaIpWs.lean.js index 6a50f581..fedeb67d 100644 --- a/assets/garden_activitypub_index.md.Dv6GWpX1.lean.js +++ b/assets/garden_activitypub_index.md.mGHaIpWs.lean.js @@ -1 +1 @@ -import{d as i}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as s,j as e,a as t,k as a,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"ActivityPub",-1),o=["innerHTML"],d=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/fediverse/"},"Fediverse")])],-1),p=e("blockquote",null,[e("p",null,[t("Tags: "),e("a",{href:"/garden/decentralized/"},"Decentralized")])],-1),_=e("p",null,[e("a",{href:"https://activitypub.rocks",target:"_blank",rel:"noreferrer"},"ActivityPub"),t(" is a protocol for "),e("a",{href:"/garden/fediverse/"},"Federated Social Media")],-1),y=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"}'),f={name:"garden/activitypub/index.md"},k=Object.assign(f,{setup(h){const r=n();return(v,b)=>(l(),s("div",null,[c,e("p",null,[t("8 words, ~0 minute read. "),e("span",{innerHTML:a(i)[`site/${a(r).page.value.relativePath}`]},null,8,o)]),d,u,p,_]))}});export{y as __pageData,k as default}; +import{d as i}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as s,j as e,a as t,k as a,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"ActivityPub",-1),o=["innerHTML"],d=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/fediverse/"},"Fediverse")])],-1),p=e("blockquote",null,[e("p",null,[t("Tags: "),e("a",{href:"/garden/decentralized/"},"Decentralized")])],-1),_=e("p",null,[e("a",{href:"https://activitypub.rocks",target:"_blank",rel:"noreferrer"},"ActivityPub"),t(" is a protocol for "),e("a",{href:"/garden/fediverse/"},"Federated Social Media")],-1),y=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"}'),f={name:"garden/activitypub/index.md"},k=Object.assign(f,{setup(h){const r=n();return(v,b)=>(l(),s("div",null,[c,e("p",null,[t("8 words, ~0 minute read. "),e("span",{innerHTML:a(i)[`site/${a(r).page.value.relativePath}`]},null,8,o)]),d,u,p,_]))}});export{y as __pageData,k as default}; diff --git a/assets/garden_advent-incremental_index.md.BMlqKZHu.js b/assets/garden_advent-incremental_index.md.COneCCEO.js similarity index 96% rename from assets/garden_advent-incremental_index.md.BMlqKZHu.js rename to assets/garden_advent-incremental_index.md.COneCCEO.js index c240528b..42db3722 100644 --- a/assets/garden_advent-incremental_index.md.BMlqKZHu.js +++ b/assets/garden_advent-incremental_index.md.COneCCEO.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as r,c as o,j as e,a as s,k as t,a5 as i,o as p}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Advent Incremental",-1),d=["innerHTML"],l=i('

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),v=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"}'),m={name:"garden/advent-incremental/index.md"},y=Object.assign(m,{setup(h){const a=r();return(u,f)=>(p(),o("div",null,[c,e("p",null,[s("104 words, ~1 minute read. "),e("span",{innerHTML:t(n)[`site/${t(a).page.value.relativePath}`]},null,8,d)]),l]))}});export{v as __pageData,y as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as r,c as o,j as e,a as s,k as t,a5 as i,o as p}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Advent Incremental",-1),d=["innerHTML"],l=i('

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),v=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"}'),m={name:"garden/advent-incremental/index.md"},y=Object.assign(m,{setup(h){const a=r();return(u,f)=>(p(),o("div",null,[c,e("p",null,[s("104 words, ~1 minute read. "),e("span",{innerHTML:t(n)[`site/${t(a).page.value.relativePath}`]},null,8,d)]),l]))}});export{v as __pageData,y as default}; diff --git a/assets/garden_advent-incremental_index.md.BMlqKZHu.lean.js b/assets/garden_advent-incremental_index.md.COneCCEO.lean.js similarity index 92% rename from assets/garden_advent-incremental_index.md.BMlqKZHu.lean.js rename to assets/garden_advent-incremental_index.md.COneCCEO.lean.js index 58cb5653..6e497375 100644 --- a/assets/garden_advent-incremental_index.md.BMlqKZHu.lean.js +++ b/assets/garden_advent-incremental_index.md.COneCCEO.lean.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as r,c as o,j as e,a as s,k as t,a5 as i,o as p}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Advent Incremental",-1),d=["innerHTML"],l=i("",8),v=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"}'),m={name:"garden/advent-incremental/index.md"},y=Object.assign(m,{setup(h){const a=r();return(u,f)=>(p(),o("div",null,[c,e("p",null,[s("104 words, ~1 minute read. "),e("span",{innerHTML:t(n)[`site/${t(a).page.value.relativePath}`]},null,8,d)]),l]))}});export{v as __pageData,y as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as r,c as o,j as e,a as s,k as t,a5 as i,o as p}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Advent Incremental",-1),d=["innerHTML"],l=i("",8),v=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"}'),m={name:"garden/advent-incremental/index.md"},y=Object.assign(m,{setup(h){const a=r();return(u,f)=>(p(),o("div",null,[c,e("p",null,[s("104 words, ~1 minute read. "),e("span",{innerHTML:t(n)[`site/${t(a).page.value.relativePath}`]},null,8,d)]),l]))}});export{v as __pageData,y as default}; diff --git a/assets/garden_artificial-intelligence_index.md.D_IxpRAg.js b/assets/garden_artificial-intelligence_index.md.Bns_28Jh.js similarity index 97% rename from assets/garden_artificial-intelligence_index.md.D_IxpRAg.js rename to assets/garden_artificial-intelligence_index.md.Bns_28Jh.js index f197214a..3e45847b 100644 --- a/assets/garden_artificial-intelligence_index.md.D_IxpRAg.js +++ b/assets/garden_artificial-intelligence_index.md.Bns_28Jh.js @@ -1 +1 @@ -import{d as l}from"./chunks/git.data.BUKN53Ta.js";import{u as r,c as i,j as e,a as o,k as a,a5 as n,o as s}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Artificial Intelligence",-1),p=["innerHTML"],d=n('

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),b=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"}'),u={name:"garden/artificial-intelligence/index.md"},k=Object.assign(u,{setup(h){const t=r();return(m,f)=>(s(),i("div",null,[c,e("p",null,[o("101 words, ~1 minute read. "),e("span",{innerHTML:a(l)[`site/${a(t).page.value.relativePath}`]},null,8,p)]),d]))}});export{b as __pageData,k as default}; +import{d as l}from"./chunks/git.data.pqelWCHe.js";import{u as r,c as i,j as e,a as o,k as a,a5 as n,o as s}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Artificial Intelligence",-1),p=["innerHTML"],d=n('

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),b=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"}'),u={name:"garden/artificial-intelligence/index.md"},k=Object.assign(u,{setup(h){const t=r();return(m,f)=>(s(),i("div",null,[c,e("p",null,[o("101 words, ~1 minute read. "),e("span",{innerHTML:a(l)[`site/${a(t).page.value.relativePath}`]},null,8,p)]),d]))}});export{b as __pageData,k as default}; diff --git a/assets/garden_artificial-intelligence_index.md.D_IxpRAg.lean.js b/assets/garden_artificial-intelligence_index.md.Bns_28Jh.lean.js similarity index 92% rename from assets/garden_artificial-intelligence_index.md.D_IxpRAg.lean.js rename to assets/garden_artificial-intelligence_index.md.Bns_28Jh.lean.js index 1f52f524..8532ce18 100644 --- a/assets/garden_artificial-intelligence_index.md.D_IxpRAg.lean.js +++ b/assets/garden_artificial-intelligence_index.md.Bns_28Jh.lean.js @@ -1 +1 @@ -import{d as l}from"./chunks/git.data.BUKN53Ta.js";import{u as r,c as i,j as e,a as o,k as a,a5 as n,o as s}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Artificial Intelligence",-1),p=["innerHTML"],d=n("",7),b=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"}'),u={name:"garden/artificial-intelligence/index.md"},k=Object.assign(u,{setup(h){const t=r();return(m,f)=>(s(),i("div",null,[c,e("p",null,[o("101 words, ~1 minute read. "),e("span",{innerHTML:a(l)[`site/${a(t).page.value.relativePath}`]},null,8,p)]),d]))}});export{b as __pageData,k as default}; +import{d as l}from"./chunks/git.data.pqelWCHe.js";import{u as r,c as i,j as e,a as o,k as a,a5 as n,o as s}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Artificial Intelligence",-1),p=["innerHTML"],d=n("",7),b=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"}'),u={name:"garden/artificial-intelligence/index.md"},k=Object.assign(u,{setup(h){const t=r();return(m,f)=>(s(),i("div",null,[c,e("p",null,[o("101 words, ~1 minute read. "),e("span",{innerHTML:a(l)[`site/${a(t).page.value.relativePath}`]},null,8,p)]),d]))}});export{b as __pageData,k as default}; diff --git a/assets/garden_atproto_index.md.C4ax3TK3.js b/assets/garden_atproto_index.md.yx1RGhM6.js similarity index 95% rename from assets/garden_atproto_index.md.C4ax3TK3.js rename to assets/garden_atproto_index.md.yx1RGhM6.js index 4a929a80..2b702253 100644 --- a/assets/garden_atproto_index.md.C4ax3TK3.js +++ b/assets/garden_atproto_index.md.yx1RGhM6.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as s,j as e,a as n,k as a,a5 as l,o as d}from"./chunks/framework.BIC8H_hJ.js";const i=e("h1",{class:"p-name"},"ATProto",-1),c=["innerHTML"],p=l('

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),m=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"}'),_={name:"garden/atproto/index.md"},b=Object.assign(_,{setup(f){const t=o();return(u,h)=>(d(),s("div",null,[i,e("p",null,[n("31 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),p]))}});export{m as __pageData,b as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as s,j as e,a as n,k as a,a5 as l,o as d}from"./chunks/framework.BIC8H_hJ.js";const i=e("h1",{class:"p-name"},"ATProto",-1),c=["innerHTML"],p=l('

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),m=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"}'),_={name:"garden/atproto/index.md"},b=Object.assign(_,{setup(f){const t=o();return(u,h)=>(d(),s("div",null,[i,e("p",null,[n("31 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),p]))}});export{m as __pageData,b as default}; diff --git a/assets/garden_atproto_index.md.C4ax3TK3.lean.js b/assets/garden_atproto_index.md.yx1RGhM6.lean.js similarity index 91% rename from assets/garden_atproto_index.md.C4ax3TK3.lean.js rename to assets/garden_atproto_index.md.yx1RGhM6.lean.js index f61def01..20e170f1 100644 --- a/assets/garden_atproto_index.md.C4ax3TK3.lean.js +++ b/assets/garden_atproto_index.md.yx1RGhM6.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as s,j as e,a as n,k as a,a5 as l,o as d}from"./chunks/framework.BIC8H_hJ.js";const i=e("h1",{class:"p-name"},"ATProto",-1),c=["innerHTML"],p=l("",6),m=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"}'),_={name:"garden/atproto/index.md"},b=Object.assign(_,{setup(f){const t=o();return(u,h)=>(d(),s("div",null,[i,e("p",null,[n("31 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),p]))}});export{m as __pageData,b as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as s,j as e,a as n,k as a,a5 as l,o as d}from"./chunks/framework.BIC8H_hJ.js";const i=e("h1",{class:"p-name"},"ATProto",-1),c=["innerHTML"],p=l("",6),m=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"}'),_={name:"garden/atproto/index.md"},b=Object.assign(_,{setup(f){const t=o();return(u,h)=>(d(),s("div",null,[i,e("p",null,[n("31 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),p]))}});export{m as __pageData,b as default}; diff --git a/assets/garden_babble-buds_index.md.C6pXaSnx.js b/assets/garden_babble-buds_index.md.DKuN95VU.js similarity index 96% rename from assets/garden_babble-buds_index.md.C6pXaSnx.js rename to assets/garden_babble-buds_index.md.DKuN95VU.js index a5156a77..f3b1df85 100644 --- a/assets/garden_babble-buds_index.md.C6pXaSnx.js +++ b/assets/garden_babble-buds_index.md.DKuN95VU.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as o,j as e,a as n,k as t,a5 as i,o as b}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Babble Buds",-1),p=["innerHTML"],d=i('

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),m=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"}'),c={name:"garden/babble-buds/index.md"},k=Object.assign(c,{setup(u){const a=s();return(h,_)=>(b(),o("div",null,[l,e("p",null,[n("113 words, ~1 minute read. "),e("span",{innerHTML:t(r)[`site/${t(a).page.value.relativePath}`]},null,8,p)]),d]))}});export{m as __pageData,k as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as o,j as e,a as n,k as t,a5 as i,o as b}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Babble Buds",-1),p=["innerHTML"],d=i('

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),m=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"}'),c={name:"garden/babble-buds/index.md"},k=Object.assign(c,{setup(u){const a=s();return(h,_)=>(b(),o("div",null,[l,e("p",null,[n("113 words, ~1 minute read. "),e("span",{innerHTML:t(r)[`site/${t(a).page.value.relativePath}`]},null,8,p)]),d]))}});export{m as __pageData,k as default}; diff --git a/assets/garden_babble-buds_index.md.C6pXaSnx.lean.js b/assets/garden_babble-buds_index.md.DKuN95VU.lean.js similarity index 91% rename from assets/garden_babble-buds_index.md.C6pXaSnx.lean.js rename to assets/garden_babble-buds_index.md.DKuN95VU.lean.js index 5cf90232..27af9ee3 100644 --- a/assets/garden_babble-buds_index.md.C6pXaSnx.lean.js +++ b/assets/garden_babble-buds_index.md.DKuN95VU.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as o,j as e,a as n,k as t,a5 as i,o as b}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Babble Buds",-1),p=["innerHTML"],d=i("",9),m=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"}'),c={name:"garden/babble-buds/index.md"},k=Object.assign(c,{setup(u){const a=s();return(h,_)=>(b(),o("div",null,[l,e("p",null,[n("113 words, ~1 minute read. "),e("span",{innerHTML:t(r)[`site/${t(a).page.value.relativePath}`]},null,8,p)]),d]))}});export{m as __pageData,k as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as o,j as e,a as n,k as t,a5 as i,o as b}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Babble Buds",-1),p=["innerHTML"],d=i("",9),m=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"}'),c={name:"garden/babble-buds/index.md"},k=Object.assign(c,{setup(u){const a=s();return(h,_)=>(b(),o("div",null,[l,e("p",null,[n("113 words, ~1 minute read. "),e("span",{innerHTML:t(r)[`site/${t(a).page.value.relativePath}`]},null,8,p)]),d]))}});export{m as __pageData,k as default}; diff --git a/assets/garden_capture-the-citadel_index.md.152H3gwW.js b/assets/garden_capture-the-citadel_index.md.CzSxLzbg.js similarity index 95% rename from assets/garden_capture-the-citadel_index.md.152H3gwW.js rename to assets/garden_capture-the-citadel_index.md.CzSxLzbg.js index e5524572..aaca4cc1 100644 --- a/assets/garden_capture-the-citadel_index.md.152H3gwW.js +++ b/assets/garden_capture-the-citadel_index.md.CzSxLzbg.js @@ -1 +1 @@ -import{u as n,c as s,j as e,a as t,k as a,a6 as l,o as i}from"./chunks/framework.BIC8H_hJ.js";import{d as o}from"./chunks/git.data.BUKN53Ta.js";const c=e("h1",{class:"p-name"},"Capture the Citadel",-1),d=["innerHTML"],p=e("hr",null,null,-1),h=e("blockquote",null,[e("p",null,[t("Tags: "),e("a",{href:"/garden/my-projects/"},"My Projects")])],-1),u=e("p",null,"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.",-1),_=e("p",null,[t("For more details, visit "),e("a",{href:"https://grantcbarbee.github.io/conquer-the-citadel.html",target:"_blank",rel:"noreferrer"},"Grant's page on the game"),t(".")],-1),g=e("div",{class:"img-container"},[e("img",{src:l,title:"screenshot.png"})],-1),j=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"}'),m={name:"garden/capture-the-citadel/index.md"},C=Object.assign(m,{setup(f){const r=n();return(b,v)=>(i(),s("div",null,[c,e("p",null,[t("39 words, ~0 minute read. "),e("span",{innerHTML:a(o)[`site/${a(r).page.value.relativePath}`]},null,8,d)]),p,h,u,_,g]))}});export{j as __pageData,C as default}; +import{u as n,c as s,j as e,a as t,k as a,a6 as l,o as i}from"./chunks/framework.BIC8H_hJ.js";import{d as o}from"./chunks/git.data.pqelWCHe.js";const c=e("h1",{class:"p-name"},"Capture the Citadel",-1),d=["innerHTML"],p=e("hr",null,null,-1),h=e("blockquote",null,[e("p",null,[t("Tags: "),e("a",{href:"/garden/my-projects/"},"My Projects")])],-1),u=e("p",null,"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.",-1),_=e("p",null,[t("For more details, visit "),e("a",{href:"https://grantcbarbee.github.io/conquer-the-citadel.html",target:"_blank",rel:"noreferrer"},"Grant's page on the game"),t(".")],-1),g=e("div",{class:"img-container"},[e("img",{src:l,title:"screenshot.png"})],-1),j=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"}'),m={name:"garden/capture-the-citadel/index.md"},C=Object.assign(m,{setup(f){const r=n();return(b,v)=>(i(),s("div",null,[c,e("p",null,[t("39 words, ~0 minute read. "),e("span",{innerHTML:a(o)[`site/${a(r).page.value.relativePath}`]},null,8,d)]),p,h,u,_,g]))}});export{j as __pageData,C as default}; diff --git a/assets/garden_capture-the-citadel_index.md.152H3gwW.lean.js b/assets/garden_capture-the-citadel_index.md.CzSxLzbg.lean.js similarity index 95% rename from assets/garden_capture-the-citadel_index.md.152H3gwW.lean.js rename to assets/garden_capture-the-citadel_index.md.CzSxLzbg.lean.js index e5524572..aaca4cc1 100644 --- a/assets/garden_capture-the-citadel_index.md.152H3gwW.lean.js +++ b/assets/garden_capture-the-citadel_index.md.CzSxLzbg.lean.js @@ -1 +1 @@ -import{u as n,c as s,j as e,a as t,k as a,a6 as l,o as i}from"./chunks/framework.BIC8H_hJ.js";import{d as o}from"./chunks/git.data.BUKN53Ta.js";const c=e("h1",{class:"p-name"},"Capture the Citadel",-1),d=["innerHTML"],p=e("hr",null,null,-1),h=e("blockquote",null,[e("p",null,[t("Tags: "),e("a",{href:"/garden/my-projects/"},"My Projects")])],-1),u=e("p",null,"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.",-1),_=e("p",null,[t("For more details, visit "),e("a",{href:"https://grantcbarbee.github.io/conquer-the-citadel.html",target:"_blank",rel:"noreferrer"},"Grant's page on the game"),t(".")],-1),g=e("div",{class:"img-container"},[e("img",{src:l,title:"screenshot.png"})],-1),j=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"}'),m={name:"garden/capture-the-citadel/index.md"},C=Object.assign(m,{setup(f){const r=n();return(b,v)=>(i(),s("div",null,[c,e("p",null,[t("39 words, ~0 minute read. "),e("span",{innerHTML:a(o)[`site/${a(r).page.value.relativePath}`]},null,8,d)]),p,h,u,_,g]))}});export{j as __pageData,C as default}; +import{u as n,c as s,j as e,a as t,k as a,a6 as l,o as i}from"./chunks/framework.BIC8H_hJ.js";import{d as o}from"./chunks/git.data.pqelWCHe.js";const c=e("h1",{class:"p-name"},"Capture the Citadel",-1),d=["innerHTML"],p=e("hr",null,null,-1),h=e("blockquote",null,[e("p",null,[t("Tags: "),e("a",{href:"/garden/my-projects/"},"My Projects")])],-1),u=e("p",null,"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.",-1),_=e("p",null,[t("For more details, visit "),e("a",{href:"https://grantcbarbee.github.io/conquer-the-citadel.html",target:"_blank",rel:"noreferrer"},"Grant's page on the game"),t(".")],-1),g=e("div",{class:"img-container"},[e("img",{src:l,title:"screenshot.png"})],-1),j=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"}'),m={name:"garden/capture-the-citadel/index.md"},C=Object.assign(m,{setup(f){const r=n();return(b,v)=>(i(),s("div",null,[c,e("p",null,[t("39 words, ~0 minute read. "),e("span",{innerHTML:a(o)[`site/${a(r).page.value.relativePath}`]},null,8,d)]),p,h,u,_,g]))}});export{j as __pageData,C as default}; diff --git a/assets/garden_chat-glue_index.md.CBv9u4YB.js b/assets/garden_chat-glue_index.md.DUkteB-2.js similarity index 94% rename from assets/garden_chat-glue_index.md.CBv9u4YB.js rename to assets/garden_chat-glue_index.md.DUkteB-2.js index 49e6ba61..e564a744 100644 --- a/assets/garden_chat-glue_index.md.CBv9u4YB.js +++ b/assets/garden_chat-glue_index.md.DUkteB-2.js @@ -1 +1 @@ -import{d as l}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as r,j as e,a as t,k as a,o}from"./chunks/framework.BIC8H_hJ.js";const i=e("h1",{class:"p-name"},"Chat Glue",-1),c=["innerHTML"],u=e("hr",null,null,-1),h=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/commune/"},"Commune"),t(", "),e("a",{href:"/garden/the-small-web/"},"The Small Web")])],-1),d=e("p",null,"A theoretical chat system designed to solve the problems of transcribing branching conversations into linear timelines.",-1),_=e("p",null,[t("Defined by the "),e("a",{href:"https://a9.io/glue-comic/",target:"_blank",rel:"noreferrer"},"Chatting with Glue"),t(" comic.")],-1),x=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"}'),m={name:"garden/chat-glue/index.md"},k=Object.assign(m,{setup(p){const n=s();return(g,f)=>(o(),r("div",null,[i,e("p",null,[t("23 words, ~0 minute read. "),e("span",{innerHTML:a(l)[`site/${a(n).page.value.relativePath}`]},null,8,c)]),u,h,d,_]))}});export{x as __pageData,k as default}; +import{d as l}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as r,j as e,a as t,k as a,o}from"./chunks/framework.BIC8H_hJ.js";const i=e("h1",{class:"p-name"},"Chat Glue",-1),c=["innerHTML"],u=e("hr",null,null,-1),h=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/commune/"},"Commune"),t(", "),e("a",{href:"/garden/the-small-web/"},"The Small Web")])],-1),d=e("p",null,"A theoretical chat system designed to solve the problems of transcribing branching conversations into linear timelines.",-1),_=e("p",null,[t("Defined by the "),e("a",{href:"https://a9.io/glue-comic/",target:"_blank",rel:"noreferrer"},"Chatting with Glue"),t(" comic.")],-1),x=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"}'),m={name:"garden/chat-glue/index.md"},k=Object.assign(m,{setup(p){const n=s();return(g,f)=>(o(),r("div",null,[i,e("p",null,[t("23 words, ~0 minute read. "),e("span",{innerHTML:a(l)[`site/${a(n).page.value.relativePath}`]},null,8,c)]),u,h,d,_]))}});export{x as __pageData,k as default}; diff --git a/assets/garden_chat-glue_index.md.CBv9u4YB.lean.js b/assets/garden_chat-glue_index.md.DUkteB-2.lean.js similarity index 94% rename from assets/garden_chat-glue_index.md.CBv9u4YB.lean.js rename to assets/garden_chat-glue_index.md.DUkteB-2.lean.js index 49e6ba61..e564a744 100644 --- a/assets/garden_chat-glue_index.md.CBv9u4YB.lean.js +++ b/assets/garden_chat-glue_index.md.DUkteB-2.lean.js @@ -1 +1 @@ -import{d as l}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as r,j as e,a as t,k as a,o}from"./chunks/framework.BIC8H_hJ.js";const i=e("h1",{class:"p-name"},"Chat Glue",-1),c=["innerHTML"],u=e("hr",null,null,-1),h=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/commune/"},"Commune"),t(", "),e("a",{href:"/garden/the-small-web/"},"The Small Web")])],-1),d=e("p",null,"A theoretical chat system designed to solve the problems of transcribing branching conversations into linear timelines.",-1),_=e("p",null,[t("Defined by the "),e("a",{href:"https://a9.io/glue-comic/",target:"_blank",rel:"noreferrer"},"Chatting with Glue"),t(" comic.")],-1),x=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"}'),m={name:"garden/chat-glue/index.md"},k=Object.assign(m,{setup(p){const n=s();return(g,f)=>(o(),r("div",null,[i,e("p",null,[t("23 words, ~0 minute read. "),e("span",{innerHTML:a(l)[`site/${a(n).page.value.relativePath}`]},null,8,c)]),u,h,d,_]))}});export{x as __pageData,k as default}; +import{d as l}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as r,j as e,a as t,k as a,o}from"./chunks/framework.BIC8H_hJ.js";const i=e("h1",{class:"p-name"},"Chat Glue",-1),c=["innerHTML"],u=e("hr",null,null,-1),h=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/commune/"},"Commune"),t(", "),e("a",{href:"/garden/the-small-web/"},"The Small Web")])],-1),d=e("p",null,"A theoretical chat system designed to solve the problems of transcribing branching conversations into linear timelines.",-1),_=e("p",null,[t("Defined by the "),e("a",{href:"https://a9.io/glue-comic/",target:"_blank",rel:"noreferrer"},"Chatting with Glue"),t(" comic.")],-1),x=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"}'),m={name:"garden/chat-glue/index.md"},k=Object.assign(m,{setup(p){const n=s();return(g,f)=>(o(),r("div",null,[i,e("p",null,[t("23 words, ~0 minute read. "),e("span",{innerHTML:a(l)[`site/${a(n).page.value.relativePath}`]},null,8,c)]),u,h,d,_]))}});export{x as __pageData,k as default}; diff --git a/assets/garden_chronological_index.md.CL1_BH-C.js b/assets/garden_chronological_index.md.BMnS4jcy.js similarity index 96% rename from assets/garden_chronological_index.md.CL1_BH-C.js rename to assets/garden_chronological_index.md.BMnS4jcy.js index 11c4bf40..1ba286ce 100644 --- a/assets/garden_chronological_index.md.CL1_BH-C.js +++ b/assets/garden_chronological_index.md.BMnS4jcy.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as r,c as i,j as e,a as n,k as o,a5 as l,o as s}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Chronological",-1),d=["innerHTML"],h=l('

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),v=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"}'),g={name:"garden/chronological/index.md"},T=Object.assign(g,{setup(f){const a=r();return(p,_)=>(s(),i("div",null,[c,e("p",null,[n("73 words, ~0 minute read. "),e("span",{innerHTML:o(t)[`site/${o(a).page.value.relativePath}`]},null,8,d)]),h]))}});export{v as __pageData,T as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as r,c as i,j as e,a as n,k as o,a5 as l,o as s}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Chronological",-1),d=["innerHTML"],h=l('

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),v=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"}'),g={name:"garden/chronological/index.md"},T=Object.assign(g,{setup(f){const a=r();return(p,_)=>(s(),i("div",null,[c,e("p",null,[n("73 words, ~0 minute read. "),e("span",{innerHTML:o(t)[`site/${o(a).page.value.relativePath}`]},null,8,d)]),h]))}});export{v as __pageData,T as default}; diff --git a/assets/garden_chronological_index.md.CL1_BH-C.lean.js b/assets/garden_chronological_index.md.BMnS4jcy.lean.js similarity index 91% rename from assets/garden_chronological_index.md.CL1_BH-C.lean.js rename to assets/garden_chronological_index.md.BMnS4jcy.lean.js index e81a4dde..6902735d 100644 --- a/assets/garden_chronological_index.md.CL1_BH-C.lean.js +++ b/assets/garden_chronological_index.md.BMnS4jcy.lean.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as r,c as i,j as e,a as n,k as o,a5 as l,o as s}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Chronological",-1),d=["innerHTML"],h=l("",9),v=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"}'),g={name:"garden/chronological/index.md"},T=Object.assign(g,{setup(f){const a=r();return(p,_)=>(s(),i("div",null,[c,e("p",null,[n("73 words, ~0 minute read. "),e("span",{innerHTML:o(t)[`site/${o(a).page.value.relativePath}`]},null,8,d)]),h]))}});export{v as __pageData,T as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as r,c as i,j as e,a as n,k as o,a5 as l,o as s}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Chronological",-1),d=["innerHTML"],h=l("",9),v=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"}'),g={name:"garden/chronological/index.md"},T=Object.assign(g,{setup(f){const a=r();return(p,_)=>(s(),i("div",null,[c,e("p",null,[n("73 words, ~0 minute read. "),e("span",{innerHTML:o(t)[`site/${o(a).page.value.relativePath}`]},null,8,d)]),h]))}});export{v as __pageData,T as default}; diff --git a/assets/garden_cinny_index.md.BWUHPipG.js b/assets/garden_cinny_index.md.BHU0bIv4.js similarity index 94% rename from assets/garden_cinny_index.md.BWUHPipG.js rename to assets/garden_cinny_index.md.BHU0bIv4.js index 0bc053d1..168f809b 100644 --- a/assets/garden_cinny_index.md.BWUHPipG.js +++ b/assets/garden_cinny_index.md.BHU0bIv4.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as i,j as e,a as n,k as a,o as l}from"./chunks/framework.BIC8H_hJ.js";const o=e("h1",{class:"p-name"},"Cinny",-1),c=["innerHTML"],d=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[n("Referenced by: "),e("a",{href:"/garden/incremental-social/"},"Incremental Social")])],-1),p=e("p",null,[e("a",{href:"https://cinny.in",target:"_blank",rel:"noreferrer"},"Cinny"),n(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),n(" web client for the "),e("a",{href:"/garden/matrix/"},"Matrix"),n(" messaging protocol")],-1),x=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"}'),_={name:"garden/cinny/index.md"},b=Object.assign(_,{setup(h){const t=s();return(f,m)=>(l(),i("div",null,[o,e("p",null,[n("3 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),d,u,p]))}});export{x as __pageData,b as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as i,j as e,a as n,k as a,o as l}from"./chunks/framework.BIC8H_hJ.js";const o=e("h1",{class:"p-name"},"Cinny",-1),c=["innerHTML"],d=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[n("Referenced by: "),e("a",{href:"/garden/incremental-social/"},"Incremental Social")])],-1),p=e("p",null,[e("a",{href:"https://cinny.in",target:"_blank",rel:"noreferrer"},"Cinny"),n(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),n(" web client for the "),e("a",{href:"/garden/matrix/"},"Matrix"),n(" messaging protocol")],-1),x=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"}'),_={name:"garden/cinny/index.md"},b=Object.assign(_,{setup(h){const t=s();return(f,m)=>(l(),i("div",null,[o,e("p",null,[n("3 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),d,u,p]))}});export{x as __pageData,b as default}; diff --git a/assets/garden_cinny_index.md.BWUHPipG.lean.js b/assets/garden_cinny_index.md.BHU0bIv4.lean.js similarity index 94% rename from assets/garden_cinny_index.md.BWUHPipG.lean.js rename to assets/garden_cinny_index.md.BHU0bIv4.lean.js index 0bc053d1..168f809b 100644 --- a/assets/garden_cinny_index.md.BWUHPipG.lean.js +++ b/assets/garden_cinny_index.md.BHU0bIv4.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as i,j as e,a as n,k as a,o as l}from"./chunks/framework.BIC8H_hJ.js";const o=e("h1",{class:"p-name"},"Cinny",-1),c=["innerHTML"],d=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[n("Referenced by: "),e("a",{href:"/garden/incremental-social/"},"Incremental Social")])],-1),p=e("p",null,[e("a",{href:"https://cinny.in",target:"_blank",rel:"noreferrer"},"Cinny"),n(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),n(" web client for the "),e("a",{href:"/garden/matrix/"},"Matrix"),n(" messaging protocol")],-1),x=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"}'),_={name:"garden/cinny/index.md"},b=Object.assign(_,{setup(h){const t=s();return(f,m)=>(l(),i("div",null,[o,e("p",null,[n("3 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),d,u,p]))}});export{x as __pageData,b as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as i,j as e,a as n,k as a,o as l}from"./chunks/framework.BIC8H_hJ.js";const o=e("h1",{class:"p-name"},"Cinny",-1),c=["innerHTML"],d=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[n("Referenced by: "),e("a",{href:"/garden/incremental-social/"},"Incremental Social")])],-1),p=e("p",null,[e("a",{href:"https://cinny.in",target:"_blank",rel:"noreferrer"},"Cinny"),n(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),n(" web client for the "),e("a",{href:"/garden/matrix/"},"Matrix"),n(" messaging protocol")],-1),x=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"}'),_={name:"garden/cinny/index.md"},b=Object.assign(_,{setup(h){const t=s();return(f,m)=>(l(),i("div",null,[o,e("p",null,[n("3 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),d,u,p]))}});export{x as __pageData,b as default}; diff --git a/assets/garden_command-palettes_index.md.A3RBTTKb.js b/assets/garden_command-palettes_index.md.COD9mgbL.js similarity index 96% rename from assets/garden_command-palettes_index.md.A3RBTTKb.js rename to assets/garden_command-palettes_index.md.COD9mgbL.js index f1b671b4..d7a8efe1 100644 --- a/assets/garden_command-palettes_index.md.A3RBTTKb.js +++ b/assets/garden_command-palettes_index.md.COD9mgbL.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as l,j as e,a as o,k as a,a5 as i,o as r}from"./chunks/framework.BIC8H_hJ.js";const m=e("h1",{class:"p-name"},"Command Palettes",-1),c=["innerHTML"],p=i('

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),y=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"}'),d={name:"garden/command-palettes/index.md"},T=Object.assign(d,{setup(u){const t=s();return(h,_)=>(r(),l("div",null,[m,e("p",null,[o("117 words, ~1 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),p]))}});export{y as __pageData,T as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as l,j as e,a as o,k as a,a5 as i,o as r}from"./chunks/framework.BIC8H_hJ.js";const m=e("h1",{class:"p-name"},"Command Palettes",-1),c=["innerHTML"],p=i('

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),y=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"}'),d={name:"garden/command-palettes/index.md"},T=Object.assign(d,{setup(u){const t=s();return(h,_)=>(r(),l("div",null,[m,e("p",null,[o("117 words, ~1 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),p]))}});export{y as __pageData,T as default}; diff --git a/assets/garden_command-palettes_index.md.A3RBTTKb.lean.js b/assets/garden_command-palettes_index.md.COD9mgbL.lean.js similarity index 91% rename from assets/garden_command-palettes_index.md.A3RBTTKb.lean.js rename to assets/garden_command-palettes_index.md.COD9mgbL.lean.js index e0e70778..eaaaee69 100644 --- a/assets/garden_command-palettes_index.md.A3RBTTKb.lean.js +++ b/assets/garden_command-palettes_index.md.COD9mgbL.lean.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as l,j as e,a as o,k as a,a5 as i,o as r}from"./chunks/framework.BIC8H_hJ.js";const m=e("h1",{class:"p-name"},"Command Palettes",-1),c=["innerHTML"],p=i("",10),y=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"}'),d={name:"garden/command-palettes/index.md"},T=Object.assign(d,{setup(u){const t=s();return(h,_)=>(r(),l("div",null,[m,e("p",null,[o("117 words, ~1 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),p]))}});export{y as __pageData,T as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as l,j as e,a as o,k as a,a5 as i,o as r}from"./chunks/framework.BIC8H_hJ.js";const m=e("h1",{class:"p-name"},"Command Palettes",-1),c=["innerHTML"],p=i("",10),y=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"}'),d={name:"garden/command-palettes/index.md"},T=Object.assign(d,{setup(u){const t=s();return(h,_)=>(r(),l("div",null,[m,e("p",null,[o("117 words, ~1 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),p]))}});export{y as __pageData,T as default}; diff --git a/assets/garden_commune_index.md.PJf709s_.js b/assets/garden_commune_index.md.ClMeApsd.js similarity index 97% rename from assets/garden_commune_index.md.PJf709s_.js rename to assets/garden_commune_index.md.ClMeApsd.js index ddfbc458..4bab0bf6 100644 --- a/assets/garden_commune_index.md.PJf709s_.js +++ b/assets/garden_commune_index.md.ClMeApsd.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as i,c as n,j as e,a as l,k as a,a5 as o,o as s}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Commune",-1),h=["innerHTML"],c=o('

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),b=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"}'),m={name:"garden/commune/index.md"},w=Object.assign(m,{setup(u){const t=i();return(g,f)=>(s(),n("div",null,[d,e("p",null,[l("144 words, ~1 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,h)]),c]))}});export{b as __pageData,w as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as i,c as n,j as e,a as l,k as a,a5 as o,o as s}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Commune",-1),h=["innerHTML"],c=o('

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),b=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"}'),m={name:"garden/commune/index.md"},w=Object.assign(m,{setup(u){const t=i();return(g,f)=>(s(),n("div",null,[d,e("p",null,[l("144 words, ~1 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,h)]),c]))}});export{b as __pageData,w as default}; diff --git a/assets/garden_commune_index.md.PJf709s_.lean.js b/assets/garden_commune_index.md.ClMeApsd.lean.js similarity index 91% rename from assets/garden_commune_index.md.PJf709s_.lean.js rename to assets/garden_commune_index.md.ClMeApsd.lean.js index 7919b9e0..6100589a 100644 --- a/assets/garden_commune_index.md.PJf709s_.lean.js +++ b/assets/garden_commune_index.md.ClMeApsd.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as i,c as n,j as e,a as l,k as a,a5 as o,o as s}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Commune",-1),h=["innerHTML"],c=o("",10),b=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"}'),m={name:"garden/commune/index.md"},w=Object.assign(m,{setup(u){const t=i();return(g,f)=>(s(),n("div",null,[d,e("p",null,[l("144 words, ~1 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,h)]),c]))}});export{b as __pageData,w as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as i,c as n,j as e,a as l,k as a,a5 as o,o as s}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Commune",-1),h=["innerHTML"],c=o("",10),b=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"}'),m={name:"garden/commune/index.md"},w=Object.assign(m,{setup(u){const t=i();return(g,f)=>(s(),n("div",null,[d,e("p",null,[l("144 words, ~1 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,h)]),c]))}});export{b as __pageData,w as default}; diff --git a/assets/garden_davey-wreden_index.md.aaY4xWmC.js b/assets/garden_davey-wreden_index.md.DagLHB1k.js similarity index 96% rename from assets/garden_davey-wreden_index.md.aaY4xWmC.js rename to assets/garden_davey-wreden_index.md.DagLHB1k.js index 7f69b37f..02fdc07a 100644 --- a/assets/garden_davey-wreden_index.md.aaY4xWmC.js +++ b/assets/garden_davey-wreden_index.md.DagLHB1k.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as d,j as e,a as o,k as a,a5 as i,o as l}from"./chunks/framework.BIC8H_hJ.js";const s=e("h1",{class:"p-name"},"Davey Wreden",-1),h=["innerHTML"],c=i('

Referenced by: Ivy Road, The Beginner's Guide

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

Projects:

Talks and Interviews:

',7),f=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"}'),u={name:"garden/davey-wreden/index.md"},w=Object.assign(u,{setup(g){const r=n();return(_,p)=>(l(),d("div",null,[s,e("p",null,[o("37 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,h)]),c]))}});export{f as __pageData,w as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as d,j as e,a as o,k as a,a5 as i,o as l}from"./chunks/framework.BIC8H_hJ.js";const s=e("h1",{class:"p-name"},"Davey Wreden",-1),h=["innerHTML"],c=i('

Referenced by: Ivy Road, The Beginner's Guide

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

Projects:

Talks and Interviews:

',7),f=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"}'),u={name:"garden/davey-wreden/index.md"},w=Object.assign(u,{setup(g){const r=n();return(_,p)=>(l(),d("div",null,[s,e("p",null,[o("37 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,h)]),c]))}});export{f as __pageData,w as default}; diff --git a/assets/garden_davey-wreden_index.md.aaY4xWmC.lean.js b/assets/garden_davey-wreden_index.md.DagLHB1k.lean.js similarity index 91% rename from assets/garden_davey-wreden_index.md.aaY4xWmC.lean.js rename to assets/garden_davey-wreden_index.md.DagLHB1k.lean.js index cd013534..cd5d9dd9 100644 --- a/assets/garden_davey-wreden_index.md.aaY4xWmC.lean.js +++ b/assets/garden_davey-wreden_index.md.DagLHB1k.lean.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as d,j as e,a as o,k as a,a5 as i,o as l}from"./chunks/framework.BIC8H_hJ.js";const s=e("h1",{class:"p-name"},"Davey Wreden",-1),h=["innerHTML"],c=i("",7),f=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"}'),u={name:"garden/davey-wreden/index.md"},w=Object.assign(u,{setup(g){const r=n();return(_,p)=>(l(),d("div",null,[s,e("p",null,[o("37 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,h)]),c]))}});export{f as __pageData,w as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as d,j as e,a as o,k as a,a5 as i,o as l}from"./chunks/framework.BIC8H_hJ.js";const s=e("h1",{class:"p-name"},"Davey Wreden",-1),h=["innerHTML"],c=i("",7),f=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"}'),u={name:"garden/davey-wreden/index.md"},w=Object.assign(u,{setup(g){const r=n();return(_,p)=>(l(),d("div",null,[s,e("p",null,[o("37 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,h)]),c]))}});export{f as __pageData,w as default}; diff --git a/assets/garden_decentralized_index.md.DMoi2uh1.js b/assets/garden_decentralized_index.md.CjAdL8Q4.js similarity index 96% rename from assets/garden_decentralized_index.md.DMoi2uh1.js rename to assets/garden_decentralized_index.md.CjAdL8Q4.js index 726682d8..b7d96ef2 100644 --- a/assets/garden_decentralized_index.md.DMoi2uh1.js +++ b/assets/garden_decentralized_index.md.CjAdL8Q4.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as i,c as n,j as e,a as o,k as a,a5 as l,o as d}from"./chunks/framework.BIC8H_hJ.js";const s=e("h1",{class:"p-name"},"Decentralized",-1),c=["innerHTML"],p=l('

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),v=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"}'),u={name:"garden/decentralized/index.md"},y=Object.assign(u,{setup(f){const t=i();return(h,m)=>(d(),n("div",null,[s,e("p",null,[o("80 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),p]))}});export{v as __pageData,y as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as i,c as n,j as e,a as o,k as a,a5 as l,o as d}from"./chunks/framework.BIC8H_hJ.js";const s=e("h1",{class:"p-name"},"Decentralized",-1),c=["innerHTML"],p=l('

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),v=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"}'),u={name:"garden/decentralized/index.md"},y=Object.assign(u,{setup(f){const t=i();return(h,m)=>(d(),n("div",null,[s,e("p",null,[o("80 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),p]))}});export{v as __pageData,y as default}; diff --git a/assets/garden_decentralized_index.md.DMoi2uh1.lean.js b/assets/garden_decentralized_index.md.CjAdL8Q4.lean.js similarity index 91% rename from assets/garden_decentralized_index.md.DMoi2uh1.lean.js rename to assets/garden_decentralized_index.md.CjAdL8Q4.lean.js index 8fad49a1..c0db7bc0 100644 --- a/assets/garden_decentralized_index.md.DMoi2uh1.lean.js +++ b/assets/garden_decentralized_index.md.CjAdL8Q4.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as i,c as n,j as e,a as o,k as a,a5 as l,o as d}from"./chunks/framework.BIC8H_hJ.js";const s=e("h1",{class:"p-name"},"Decentralized",-1),c=["innerHTML"],p=l("",9),v=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"}'),u={name:"garden/decentralized/index.md"},y=Object.assign(u,{setup(f){const t=i();return(h,m)=>(d(),n("div",null,[s,e("p",null,[o("80 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),p]))}});export{v as __pageData,y as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as i,c as n,j as e,a as o,k as a,a5 as l,o as d}from"./chunks/framework.BIC8H_hJ.js";const s=e("h1",{class:"p-name"},"Decentralized",-1),c=["innerHTML"],p=l("",9),v=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"}'),u={name:"garden/decentralized/index.md"},y=Object.assign(u,{setup(f){const t=i();return(h,m)=>(d(),n("div",null,[s,e("p",null,[o("80 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),p]))}});export{v as __pageData,y as default}; diff --git a/assets/garden_dice-armor_index.md.DvezVt4e.js b/assets/garden_dice-armor_index.md.DyblR0tT.js similarity index 99% rename from assets/garden_dice-armor_index.md.DvezVt4e.js rename to assets/garden_dice-armor_index.md.DyblR0tT.js index 9cdb39de..411f1935 100644 --- a/assets/garden_dice-armor_index.md.DvezVt4e.js +++ b/assets/garden_dice-armor_index.md.DyblR0tT.js @@ -1 +1 @@ -import{u as i,c as o,j as e,a as s,k as t,a5 as n,o as r,a7 as l,a8 as d,a9 as c,aa as h,ab as p,ac as m,ad as u,ae as g,af as f}from"./chunks/framework.BIC8H_hJ.js";import{d as y}from"./chunks/git.data.BUKN53Ta.js";const b=e("h1",{class:"p-name"},"Dice Armor",-1),v=["innerHTML"],w=n('

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).

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.

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.

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.

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.

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.

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.

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.

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.

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),D=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"}'),_={name:"garden/dice-armor/index.md"},B=Object.assign(_,{setup(k){const a=i();return(T,q)=>(r(),o("div",null,[b,e("p",null,[s("963 words, ~5 minute read. "),e("span",{innerHTML:t(y)[`site/${t(a).page.value.relativePath}`]},null,8,v)]),w]))}});export{D as __pageData,B as default}; +import{u as i,c as o,j as e,a as s,k as t,a5 as n,o as r,a7 as l,a8 as d,a9 as c,aa as h,ab as p,ac as m,ad as u,ae as g,af as f}from"./chunks/framework.BIC8H_hJ.js";import{d as y}from"./chunks/git.data.pqelWCHe.js";const b=e("h1",{class:"p-name"},"Dice Armor",-1),v=["innerHTML"],w=n('

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).

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.

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.

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.

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.

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.

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.

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.

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.

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),D=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"}'),_={name:"garden/dice-armor/index.md"},B=Object.assign(_,{setup(k){const a=i();return(T,q)=>(r(),o("div",null,[b,e("p",null,[s("963 words, ~5 minute read. "),e("span",{innerHTML:t(y)[`site/${t(a).page.value.relativePath}`]},null,8,v)]),w]))}});export{D as __pageData,B as default}; diff --git a/assets/garden_dice-armor_index.md.DvezVt4e.lean.js b/assets/garden_dice-armor_index.md.DyblR0tT.lean.js similarity index 92% rename from assets/garden_dice-armor_index.md.DvezVt4e.lean.js rename to assets/garden_dice-armor_index.md.DyblR0tT.lean.js index 22c0db80..90511982 100644 --- a/assets/garden_dice-armor_index.md.DvezVt4e.lean.js +++ b/assets/garden_dice-armor_index.md.DyblR0tT.lean.js @@ -1 +1 @@ -import{u as i,c as o,j as e,a as s,k as t,a5 as n,o as r,a7 as l,a8 as d,a9 as c,aa as h,ab as p,ac as m,ad as u,ae as g,af as f}from"./chunks/framework.BIC8H_hJ.js";import{d as y}from"./chunks/git.data.BUKN53Ta.js";const b=e("h1",{class:"p-name"},"Dice Armor",-1),v=["innerHTML"],w=n("",25),D=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"}'),_={name:"garden/dice-armor/index.md"},B=Object.assign(_,{setup(k){const a=i();return(T,q)=>(r(),o("div",null,[b,e("p",null,[s("963 words, ~5 minute read. "),e("span",{innerHTML:t(y)[`site/${t(a).page.value.relativePath}`]},null,8,v)]),w]))}});export{D as __pageData,B as default}; +import{u as i,c as o,j as e,a as s,k as t,a5 as n,o as r,a7 as l,a8 as d,a9 as c,aa as h,ab as p,ac as m,ad as u,ae as g,af as f}from"./chunks/framework.BIC8H_hJ.js";import{d as y}from"./chunks/git.data.pqelWCHe.js";const b=e("h1",{class:"p-name"},"Dice Armor",-1),v=["innerHTML"],w=n("",25),D=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"}'),_={name:"garden/dice-armor/index.md"},B=Object.assign(_,{setup(k){const a=i();return(T,q)=>(r(),o("div",null,[b,e("p",null,[s("963 words, ~5 minute read. "),e("span",{innerHTML:t(y)[`site/${t(a).page.value.relativePath}`]},null,8,v)]),w]))}});export{D as __pageData,B as default}; diff --git a/assets/garden_digital-gardens_index.md.CA3uP89H.js b/assets/garden_digital-gardens_index.md.DlYNcbZT.js similarity index 97% rename from assets/garden_digital-gardens_index.md.CA3uP89H.js rename to assets/garden_digital-gardens_index.md.DlYNcbZT.js index f6f3f4db..32d295a4 100644 --- a/assets/garden_digital-gardens_index.md.CA3uP89H.js +++ b/assets/garden_digital-gardens_index.md.DlYNcbZT.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as i,j as e,a as o,k as a,a5 as l,o as s}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Digital Gardens",-1),g=["innerHTML"],c=l('

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),b=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"}'),h={name:"garden/digital-gardens/index.md"},T=Object.assign(h,{setup(p){const r=n();return(u,f)=>(s(),i("div",null,[d,e("p",null,[o("63 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,g)]),c]))}});export{b as __pageData,T as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as i,j as e,a as o,k as a,a5 as l,o as s}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Digital Gardens",-1),g=["innerHTML"],c=l('

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),b=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"}'),h={name:"garden/digital-gardens/index.md"},T=Object.assign(h,{setup(p){const r=n();return(u,f)=>(s(),i("div",null,[d,e("p",null,[o("63 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,g)]),c]))}});export{b as __pageData,T as default}; diff --git a/assets/garden_digital-gardens_index.md.CA3uP89H.lean.js b/assets/garden_digital-gardens_index.md.DlYNcbZT.lean.js similarity index 92% rename from assets/garden_digital-gardens_index.md.CA3uP89H.lean.js rename to assets/garden_digital-gardens_index.md.DlYNcbZT.lean.js index f5eecfe3..50c898da 100644 --- a/assets/garden_digital-gardens_index.md.CA3uP89H.lean.js +++ b/assets/garden_digital-gardens_index.md.DlYNcbZT.lean.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as i,j as e,a as o,k as a,a5 as l,o as s}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Digital Gardens",-1),g=["innerHTML"],c=l("",7),b=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"}'),h={name:"garden/digital-gardens/index.md"},T=Object.assign(h,{setup(p){const r=n();return(u,f)=>(s(),i("div",null,[d,e("p",null,[o("63 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,g)]),c]))}});export{b as __pageData,T as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as i,j as e,a as o,k as a,a5 as l,o as s}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Digital Gardens",-1),g=["innerHTML"],c=l("",7),b=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"}'),h={name:"garden/digital-gardens/index.md"},T=Object.assign(h,{setup(p){const r=n();return(u,f)=>(s(),i("div",null,[d,e("p",null,[o("63 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,g)]),c]))}});export{b as __pageData,T as default}; diff --git a/assets/garden_federated-identity_index.md.30v88T8v.js b/assets/garden_federated-identity_index.md.Bx0G2BEh.js similarity index 96% rename from assets/garden_federated-identity_index.md.30v88T8v.js rename to assets/garden_federated-identity_index.md.Bx0G2BEh.js index 3280c6b3..e1c0b0d9 100644 --- a/assets/garden_federated-identity_index.md.30v88T8v.js +++ b/assets/garden_federated-identity_index.md.Bx0G2BEh.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as i,c as n,j as e,a as d,k as t,a5 as o,o as l}from"./chunks/framework.BIC8H_hJ.js";const s=e("h1",{class:"p-name"},"Federated Identity",-1),c=["innerHTML"],u=o('

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),b=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"}'),p={name:"garden/federated-identity/index.md"},y=Object.assign(p,{setup(h){const a=i();return(f,_)=>(l(),n("div",null,[s,e("p",null,[d("68 words, ~0 minute read. "),e("span",{innerHTML:t(r)[`site/${t(a).page.value.relativePath}`]},null,8,c)]),u]))}});export{b as __pageData,y as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as i,c as n,j as e,a as d,k as t,a5 as o,o as l}from"./chunks/framework.BIC8H_hJ.js";const s=e("h1",{class:"p-name"},"Federated Identity",-1),c=["innerHTML"],u=o('

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),b=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"}'),p={name:"garden/federated-identity/index.md"},y=Object.assign(p,{setup(h){const a=i();return(f,_)=>(l(),n("div",null,[s,e("p",null,[d("68 words, ~0 minute read. "),e("span",{innerHTML:t(r)[`site/${t(a).page.value.relativePath}`]},null,8,c)]),u]))}});export{b as __pageData,y as default}; diff --git a/assets/garden_federated-identity_index.md.30v88T8v.lean.js b/assets/garden_federated-identity_index.md.Bx0G2BEh.lean.js similarity index 92% rename from assets/garden_federated-identity_index.md.30v88T8v.lean.js rename to assets/garden_federated-identity_index.md.Bx0G2BEh.lean.js index 921d2322..7ca5d6ce 100644 --- a/assets/garden_federated-identity_index.md.30v88T8v.lean.js +++ b/assets/garden_federated-identity_index.md.Bx0G2BEh.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as i,c as n,j as e,a as d,k as t,a5 as o,o as l}from"./chunks/framework.BIC8H_hJ.js";const s=e("h1",{class:"p-name"},"Federated Identity",-1),c=["innerHTML"],u=o("",9),b=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"}'),p={name:"garden/federated-identity/index.md"},y=Object.assign(p,{setup(h){const a=i();return(f,_)=>(l(),n("div",null,[s,e("p",null,[d("68 words, ~0 minute read. "),e("span",{innerHTML:t(r)[`site/${t(a).page.value.relativePath}`]},null,8,c)]),u]))}});export{b as __pageData,y as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as i,c as n,j as e,a as d,k as t,a5 as o,o as l}from"./chunks/framework.BIC8H_hJ.js";const s=e("h1",{class:"p-name"},"Federated Identity",-1),c=["innerHTML"],u=o("",9),b=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"}'),p={name:"garden/federated-identity/index.md"},y=Object.assign(p,{setup(h){const a=i();return(f,_)=>(l(),n("div",null,[s,e("p",null,[d("68 words, ~0 minute read. "),e("span",{innerHTML:t(r)[`site/${t(a).page.value.relativePath}`]},null,8,c)]),u]))}});export{b as __pageData,y as default}; diff --git a/assets/garden_fedi-v2_index.md.g4qaD9AG.js b/assets/garden_fedi-v2_index.md.DE3mE6fu.js similarity index 99% rename from assets/garden_fedi-v2_index.md.g4qaD9AG.js rename to assets/garden_fedi-v2_index.md.DE3mE6fu.js index 7cc5b54e..eac1ed4a 100644 --- a/assets/garden_fedi-v2_index.md.g4qaD9AG.js +++ b/assets/garden_fedi-v2_index.md.DE3mE6fu.js @@ -1 +1 @@ -import{d as a}from"./chunks/git.data.BUKN53Ta.js";import{u as l,c as s,j as e,a as o,k as i,a5 as r,o as n}from"./chunks/framework.BIC8H_hJ.js";const u=e("h1",{class:"p-name"},"Fedi v2",-1),d=["innerHTML"],h=r('

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),b=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"}'),c={name:"garden/fedi-v2/index.md"},v=Object.assign(c,{setup(m){const t=l();return(y,p)=>(n(),s("div",null,[u,e("p",null,[o("1274 words, ~7 minute read. "),e("span",{innerHTML:i(a)[`site/${i(t).page.value.relativePath}`]},null,8,d)]),h]))}});export{b as __pageData,v as default}; +import{d as a}from"./chunks/git.data.pqelWCHe.js";import{u as l,c as s,j as e,a as o,k as i,a5 as r,o as n}from"./chunks/framework.BIC8H_hJ.js";const u=e("h1",{class:"p-name"},"Fedi v2",-1),d=["innerHTML"],h=r('

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),b=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"}'),c={name:"garden/fedi-v2/index.md"},v=Object.assign(c,{setup(m){const t=l();return(y,p)=>(n(),s("div",null,[u,e("p",null,[o("1274 words, ~7 minute read. "),e("span",{innerHTML:i(a)[`site/${i(t).page.value.relativePath}`]},null,8,d)]),h]))}});export{b as __pageData,v as default}; diff --git a/assets/garden_fedi-v2_index.md.g4qaD9AG.lean.js b/assets/garden_fedi-v2_index.md.DE3mE6fu.lean.js similarity index 91% rename from assets/garden_fedi-v2_index.md.g4qaD9AG.lean.js rename to assets/garden_fedi-v2_index.md.DE3mE6fu.lean.js index 4bfdab65..cf857d29 100644 --- a/assets/garden_fedi-v2_index.md.g4qaD9AG.lean.js +++ b/assets/garden_fedi-v2_index.md.DE3mE6fu.lean.js @@ -1 +1 @@ -import{d as a}from"./chunks/git.data.BUKN53Ta.js";import{u as l,c as s,j as e,a as o,k as i,a5 as r,o as n}from"./chunks/framework.BIC8H_hJ.js";const u=e("h1",{class:"p-name"},"Fedi v2",-1),d=["innerHTML"],h=r("",16),b=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"}'),c={name:"garden/fedi-v2/index.md"},v=Object.assign(c,{setup(m){const t=l();return(y,p)=>(n(),s("div",null,[u,e("p",null,[o("1274 words, ~7 minute read. "),e("span",{innerHTML:i(a)[`site/${i(t).page.value.relativePath}`]},null,8,d)]),h]))}});export{b as __pageData,v as default}; +import{d as a}from"./chunks/git.data.pqelWCHe.js";import{u as l,c as s,j as e,a as o,k as i,a5 as r,o as n}from"./chunks/framework.BIC8H_hJ.js";const u=e("h1",{class:"p-name"},"Fedi v2",-1),d=["innerHTML"],h=r("",16),b=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"}'),c={name:"garden/fedi-v2/index.md"},v=Object.assign(c,{setup(m){const t=l();return(y,p)=>(n(),s("div",null,[u,e("p",null,[o("1274 words, ~7 minute read. "),e("span",{innerHTML:i(a)[`site/${i(t).page.value.relativePath}`]},null,8,d)]),h]))}});export{b as __pageData,v as default}; diff --git a/assets/garden_fediverse_index.md.Dw1EGARy.js b/assets/garden_fediverse_index.md.p2zOMqpI.js similarity index 96% rename from assets/garden_fediverse_index.md.Dw1EGARy.js rename to assets/garden_fediverse_index.md.p2zOMqpI.js index 79699ec9..04ed8b89 100644 --- a/assets/garden_fediverse_index.md.Dw1EGARy.js +++ b/assets/garden_fediverse_index.md.p2zOMqpI.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as i,c as n,j as e,a as d,k as a,a5 as o,o as s}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Fediverse",-1),c=["innerHTML"],p=o('

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),v=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"}'),f={name:"garden/fediverse/index.md"},b=Object.assign(f,{setup(_){const t=i();return(u,h)=>(s(),n("div",null,[l,e("p",null,[d("29 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),p]))}});export{v as __pageData,b as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as i,c as n,j as e,a as d,k as a,a5 as o,o as s}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Fediverse",-1),c=["innerHTML"],p=o('

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),v=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"}'),f={name:"garden/fediverse/index.md"},b=Object.assign(f,{setup(_){const t=i();return(u,h)=>(s(),n("div",null,[l,e("p",null,[d("29 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),p]))}});export{v as __pageData,b as default}; diff --git a/assets/garden_fediverse_index.md.Dw1EGARy.lean.js b/assets/garden_fediverse_index.md.p2zOMqpI.lean.js similarity index 92% rename from assets/garden_fediverse_index.md.Dw1EGARy.lean.js rename to assets/garden_fediverse_index.md.p2zOMqpI.lean.js index 3b96c930..49343b6c 100644 --- a/assets/garden_fediverse_index.md.Dw1EGARy.lean.js +++ b/assets/garden_fediverse_index.md.p2zOMqpI.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as i,c as n,j as e,a as d,k as a,a5 as o,o as s}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Fediverse",-1),c=["innerHTML"],p=o("",7),v=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"}'),f={name:"garden/fediverse/index.md"},b=Object.assign(f,{setup(_){const t=i();return(u,h)=>(s(),n("div",null,[l,e("p",null,[d("29 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),p]))}});export{v as __pageData,b as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as i,c as n,j as e,a as d,k as a,a5 as o,o as s}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Fediverse",-1),c=["innerHTML"],p=o("",7),v=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"}'),f={name:"garden/fediverse/index.md"},b=Object.assign(f,{setup(_){const t=i();return(u,h)=>(s(),n("div",null,[l,e("p",null,[d("29 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),p]))}});export{v as __pageData,b as default}; diff --git a/assets/garden_forgejo_index.md.DAIAC7z7.js b/assets/garden_forgejo_index.md.DskPgq7f.js similarity index 93% rename from assets/garden_forgejo_index.md.DAIAC7z7.js rename to assets/garden_forgejo_index.md.DskPgq7f.js index 33139683..204213cb 100644 --- a/assets/garden_forgejo_index.md.DAIAC7z7.js +++ b/assets/garden_forgejo_index.md.DskPgq7f.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as s,j as e,a,k as o,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Forgejo",-1),i=["innerHTML"],d=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/incremental-social/"},"Incremental Social")])],-1),p=e("p",null,[e("a",{href:"https://forgejo.org",target:"_blank",rel:"noreferrer"},"Forgejo"),a(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),a(" code repository hosting software")],-1),x=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"}'),_={name:"garden/forgejo/index.md"},b=Object.assign(_,{setup(g){const r=n();return(f,h)=>(l(),s("div",null,[c,e("p",null,[a("5 words, ~0 minute read. "),e("span",{innerHTML:o(t)[`site/${o(r).page.value.relativePath}`]},null,8,i)]),d,u,p]))}});export{x as __pageData,b as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as s,j as e,a,k as o,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Forgejo",-1),i=["innerHTML"],d=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/incremental-social/"},"Incremental Social")])],-1),p=e("p",null,[e("a",{href:"https://forgejo.org",target:"_blank",rel:"noreferrer"},"Forgejo"),a(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),a(" code repository hosting software")],-1),x=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"}'),_={name:"garden/forgejo/index.md"},b=Object.assign(_,{setup(g){const r=n();return(f,h)=>(l(),s("div",null,[c,e("p",null,[a("5 words, ~0 minute read. "),e("span",{innerHTML:o(t)[`site/${o(r).page.value.relativePath}`]},null,8,i)]),d,u,p]))}});export{x as __pageData,b as default}; diff --git a/assets/garden_forgejo_index.md.DAIAC7z7.lean.js b/assets/garden_forgejo_index.md.DskPgq7f.lean.js similarity index 93% rename from assets/garden_forgejo_index.md.DAIAC7z7.lean.js rename to assets/garden_forgejo_index.md.DskPgq7f.lean.js index 33139683..204213cb 100644 --- a/assets/garden_forgejo_index.md.DAIAC7z7.lean.js +++ b/assets/garden_forgejo_index.md.DskPgq7f.lean.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as s,j as e,a,k as o,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Forgejo",-1),i=["innerHTML"],d=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/incremental-social/"},"Incremental Social")])],-1),p=e("p",null,[e("a",{href:"https://forgejo.org",target:"_blank",rel:"noreferrer"},"Forgejo"),a(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),a(" code repository hosting software")],-1),x=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"}'),_={name:"garden/forgejo/index.md"},b=Object.assign(_,{setup(g){const r=n();return(f,h)=>(l(),s("div",null,[c,e("p",null,[a("5 words, ~0 minute read. "),e("span",{innerHTML:o(t)[`site/${o(r).page.value.relativePath}`]},null,8,i)]),d,u,p]))}});export{x as __pageData,b as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as s,j as e,a,k as o,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Forgejo",-1),i=["innerHTML"],d=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/incremental-social/"},"Incremental Social")])],-1),p=e("p",null,[e("a",{href:"https://forgejo.org",target:"_blank",rel:"noreferrer"},"Forgejo"),a(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),a(" code repository hosting software")],-1),x=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"}'),_={name:"garden/forgejo/index.md"},b=Object.assign(_,{setup(g){const r=n();return(f,h)=>(l(),s("div",null,[c,e("p",null,[a("5 words, ~0 minute read. "),e("span",{innerHTML:o(t)[`site/${o(r).page.value.relativePath}`]},null,8,i)]),d,u,p]))}});export{x as __pageData,b as default}; diff --git a/assets/garden_freeform-vs-chronological-dichotomy_index.md.J7Z6S5W3.js b/assets/garden_freeform-vs-chronological-dichotomy_index.md.RXz6V-VC.js similarity index 95% rename from assets/garden_freeform-vs-chronological-dichotomy_index.md.J7Z6S5W3.js rename to assets/garden_freeform-vs-chronological-dichotomy_index.md.RXz6V-VC.js index 750e189c..426d99a3 100644 --- a/assets/garden_freeform-vs-chronological-dichotomy_index.md.J7Z6S5W3.js +++ b/assets/garden_freeform-vs-chronological-dichotomy_index.md.RXz6V-VC.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as t,c as l,j as e,a as o,k as r,o as c}from"./chunks/framework.BIC8H_hJ.js";const s=e("h1",{class:"p-name"},"Freeform vs Chronological Dichotomy",-1),i=["innerHTML"],d=e("hr",null,null,-1),h=e("blockquote",null,[e("p",null,[o("Referenced by: "),e("a",{href:"/garden/chronological/"},"Chronological"),o(", "),e("a",{href:"/garden/freeform/"},"Freeform")])],-1),m=e("p",null,[o("Describes a dichotomy between displaying information in a "),e("a",{href:"/garden/freeform/"},"Freeform"),o(" vs "),e("a",{href:"/garden/chronological/"},"Chronological"),o(" manner")],-1),y=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"}'),f={name:"garden/freeform-vs-chronological-dichotomy/index.md"},x=Object.assign(f,{setup(g){const a=t();return(u,_)=>(c(),l("div",null,[s,e("p",null,[o("10 words, ~0 minute read. "),e("span",{innerHTML:r(n)[`site/${r(a).page.value.relativePath}`]},null,8,i)]),d,h,m]))}});export{y as __pageData,x as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as t,c as l,j as e,a as o,k as r,o as c}from"./chunks/framework.BIC8H_hJ.js";const s=e("h1",{class:"p-name"},"Freeform vs Chronological Dichotomy",-1),i=["innerHTML"],d=e("hr",null,null,-1),h=e("blockquote",null,[e("p",null,[o("Referenced by: "),e("a",{href:"/garden/chronological/"},"Chronological"),o(", "),e("a",{href:"/garden/freeform/"},"Freeform")])],-1),m=e("p",null,[o("Describes a dichotomy between displaying information in a "),e("a",{href:"/garden/freeform/"},"Freeform"),o(" vs "),e("a",{href:"/garden/chronological/"},"Chronological"),o(" manner")],-1),y=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"}'),f={name:"garden/freeform-vs-chronological-dichotomy/index.md"},x=Object.assign(f,{setup(g){const a=t();return(u,_)=>(c(),l("div",null,[s,e("p",null,[o("10 words, ~0 minute read. "),e("span",{innerHTML:r(n)[`site/${r(a).page.value.relativePath}`]},null,8,i)]),d,h,m]))}});export{y as __pageData,x as default}; diff --git a/assets/garden_freeform-vs-chronological-dichotomy_index.md.J7Z6S5W3.lean.js b/assets/garden_freeform-vs-chronological-dichotomy_index.md.RXz6V-VC.lean.js similarity index 95% rename from assets/garden_freeform-vs-chronological-dichotomy_index.md.J7Z6S5W3.lean.js rename to assets/garden_freeform-vs-chronological-dichotomy_index.md.RXz6V-VC.lean.js index 750e189c..426d99a3 100644 --- a/assets/garden_freeform-vs-chronological-dichotomy_index.md.J7Z6S5W3.lean.js +++ b/assets/garden_freeform-vs-chronological-dichotomy_index.md.RXz6V-VC.lean.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as t,c as l,j as e,a as o,k as r,o as c}from"./chunks/framework.BIC8H_hJ.js";const s=e("h1",{class:"p-name"},"Freeform vs Chronological Dichotomy",-1),i=["innerHTML"],d=e("hr",null,null,-1),h=e("blockquote",null,[e("p",null,[o("Referenced by: "),e("a",{href:"/garden/chronological/"},"Chronological"),o(", "),e("a",{href:"/garden/freeform/"},"Freeform")])],-1),m=e("p",null,[o("Describes a dichotomy between displaying information in a "),e("a",{href:"/garden/freeform/"},"Freeform"),o(" vs "),e("a",{href:"/garden/chronological/"},"Chronological"),o(" manner")],-1),y=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"}'),f={name:"garden/freeform-vs-chronological-dichotomy/index.md"},x=Object.assign(f,{setup(g){const a=t();return(u,_)=>(c(),l("div",null,[s,e("p",null,[o("10 words, ~0 minute read. "),e("span",{innerHTML:r(n)[`site/${r(a).page.value.relativePath}`]},null,8,i)]),d,h,m]))}});export{y as __pageData,x as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as t,c as l,j as e,a as o,k as r,o as c}from"./chunks/framework.BIC8H_hJ.js";const s=e("h1",{class:"p-name"},"Freeform vs Chronological Dichotomy",-1),i=["innerHTML"],d=e("hr",null,null,-1),h=e("blockquote",null,[e("p",null,[o("Referenced by: "),e("a",{href:"/garden/chronological/"},"Chronological"),o(", "),e("a",{href:"/garden/freeform/"},"Freeform")])],-1),m=e("p",null,[o("Describes a dichotomy between displaying information in a "),e("a",{href:"/garden/freeform/"},"Freeform"),o(" vs "),e("a",{href:"/garden/chronological/"},"Chronological"),o(" manner")],-1),y=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"}'),f={name:"garden/freeform-vs-chronological-dichotomy/index.md"},x=Object.assign(f,{setup(g){const a=t();return(u,_)=>(c(),l("div",null,[s,e("p",null,[o("10 words, ~0 minute read. "),e("span",{innerHTML:r(n)[`site/${r(a).page.value.relativePath}`]},null,8,i)]),d,h,m]))}});export{y as __pageData,x as default}; diff --git a/assets/garden_freeform_index.md.C7x-jEUs.js b/assets/garden_freeform_index.md.C1K0FSr_.js similarity index 95% rename from assets/garden_freeform_index.md.C7x-jEUs.js rename to assets/garden_freeform_index.md.C1K0FSr_.js index f1835936..fa4b70dc 100644 --- a/assets/garden_freeform_index.md.C7x-jEUs.js +++ b/assets/garden_freeform_index.md.C1K0FSr_.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as n,j as e,a as i,k as a,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Freeform",-1),c=["innerHTML"],f=s('

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),S=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"}'),m={name:"garden/freeform/index.md"},v=Object.assign(m,{setup(h){const r=o();return(_,p)=>(l(),n("div",null,[d,e("p",null,[i("46 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),f]))}});export{S as __pageData,v as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as n,j as e,a as i,k as a,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Freeform",-1),c=["innerHTML"],f=s('

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),S=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"}'),m={name:"garden/freeform/index.md"},v=Object.assign(m,{setup(h){const r=o();return(_,p)=>(l(),n("div",null,[d,e("p",null,[i("46 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),f]))}});export{S as __pageData,v as default}; diff --git a/assets/garden_freeform_index.md.C7x-jEUs.lean.js b/assets/garden_freeform_index.md.C1K0FSr_.lean.js similarity index 91% rename from assets/garden_freeform_index.md.C7x-jEUs.lean.js rename to assets/garden_freeform_index.md.C1K0FSr_.lean.js index 3c58a3df..23d64f39 100644 --- a/assets/garden_freeform_index.md.C7x-jEUs.lean.js +++ b/assets/garden_freeform_index.md.C1K0FSr_.lean.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as n,j as e,a as i,k as a,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Freeform",-1),c=["innerHTML"],f=s("",7),S=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"}'),m={name:"garden/freeform/index.md"},v=Object.assign(m,{setup(h){const r=o();return(_,p)=>(l(),n("div",null,[d,e("p",null,[i("46 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),f]))}});export{S as __pageData,v as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as n,j as e,a as i,k as a,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Freeform",-1),c=["innerHTML"],f=s("",7),S=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"}'),m={name:"garden/freeform/index.md"},v=Object.assign(m,{setup(h){const r=o();return(_,p)=>(l(),n("div",null,[d,e("p",null,[i("46 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),f]))}});export{S as __pageData,v as default}; diff --git a/assets/garden_game-dev-tree_index.md.BHrjr9mU.js b/assets/garden_game-dev-tree_index.md.jNux2X3x.js similarity index 95% rename from assets/garden_game-dev-tree_index.md.BHrjr9mU.js rename to assets/garden_game-dev-tree_index.md.jNux2X3x.js index ef55a0d7..3f30e1b2 100644 --- a/assets/garden_game-dev-tree_index.md.BHrjr9mU.js +++ b/assets/garden_game-dev-tree_index.md.jNux2X3x.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as s,j as e,a as n,k as a,a5 as p,o as i}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Game Dev Tree",-1),l=["innerHTML"],d=p('

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),T=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"}'),m={name:"garden/game-dev-tree/index.md"},v=Object.assign(m,{setup(_){const t=o();return(h,g)=>(i(),s("div",null,[c,e("p",null,[n("34 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,l)]),d]))}});export{T as __pageData,v as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as s,j as e,a as n,k as a,a5 as p,o as i}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Game Dev Tree",-1),l=["innerHTML"],d=p('

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),T=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"}'),m={name:"garden/game-dev-tree/index.md"},v=Object.assign(m,{setup(_){const t=o();return(h,g)=>(i(),s("div",null,[c,e("p",null,[n("34 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,l)]),d]))}});export{T as __pageData,v as default}; diff --git a/assets/garden_game-dev-tree_index.md.BHrjr9mU.lean.js b/assets/garden_game-dev-tree_index.md.jNux2X3x.lean.js similarity index 91% rename from assets/garden_game-dev-tree_index.md.BHrjr9mU.lean.js rename to assets/garden_game-dev-tree_index.md.jNux2X3x.lean.js index 4fbd8559..2398afa6 100644 --- a/assets/garden_game-dev-tree_index.md.BHrjr9mU.lean.js +++ b/assets/garden_game-dev-tree_index.md.jNux2X3x.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as s,j as e,a as n,k as a,a5 as p,o as i}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Game Dev Tree",-1),l=["innerHTML"],d=p("",6),T=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"}'),m={name:"garden/game-dev-tree/index.md"},v=Object.assign(m,{setup(_){const t=o();return(h,g)=>(i(),s("div",null,[c,e("p",null,[n("34 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,l)]),d]))}});export{T as __pageData,v as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as s,j as e,a as n,k as a,a5 as p,o as i}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Game Dev Tree",-1),l=["innerHTML"],d=p("",6),T=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"}'),m={name:"garden/game-dev-tree/index.md"},v=Object.assign(m,{setup(_){const t=o();return(h,g)=>(i(),s("div",null,[c,e("p",null,[n("34 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,l)]),d]))}});export{T as __pageData,v as default}; diff --git a/assets/garden_garden-rss_index.md.MseAvfYU.js b/assets/garden_garden-rss_index.md.DzOOAEz6.js similarity index 96% rename from assets/garden_garden-rss_index.md.MseAvfYU.js rename to assets/garden_garden-rss_index.md.DzOOAEz6.js index e4f940a0..ca215a2d 100644 --- a/assets/garden_garden-rss_index.md.MseAvfYU.js +++ b/assets/garden_garden-rss_index.md.DzOOAEz6.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as i,j as e,a as n,k as a,a5 as l,o}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Garden-RSS",-1),c=["innerHTML"],f=l('

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),S=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"}'),h={name:"garden/garden-rss/index.md"},b=Object.assign(h,{setup(g){const r=s();return(p,u)=>(o(),i("div",null,[d,e("p",null,[n("59 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),f]))}});export{S as __pageData,b as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as i,j as e,a as n,k as a,a5 as l,o}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Garden-RSS",-1),c=["innerHTML"],f=l('

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),S=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"}'),h={name:"garden/garden-rss/index.md"},b=Object.assign(h,{setup(g){const r=s();return(p,u)=>(o(),i("div",null,[d,e("p",null,[n("59 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),f]))}});export{S as __pageData,b as default}; diff --git a/assets/garden_garden-rss_index.md.MseAvfYU.lean.js b/assets/garden_garden-rss_index.md.DzOOAEz6.lean.js similarity index 91% rename from assets/garden_garden-rss_index.md.MseAvfYU.lean.js rename to assets/garden_garden-rss_index.md.DzOOAEz6.lean.js index d73e979f..ad0cb799 100644 --- a/assets/garden_garden-rss_index.md.MseAvfYU.lean.js +++ b/assets/garden_garden-rss_index.md.DzOOAEz6.lean.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as i,j as e,a as n,k as a,a5 as l,o}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Garden-RSS",-1),c=["innerHTML"],f=l("",9),S=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"}'),h={name:"garden/garden-rss/index.md"},b=Object.assign(h,{setup(g){const r=s();return(p,u)=>(o(),i("div",null,[d,e("p",null,[n("59 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),f]))}});export{S as __pageData,b as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as i,j as e,a as n,k as a,a5 as l,o}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Garden-RSS",-1),c=["innerHTML"],f=l("",9),S=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"}'),h={name:"garden/garden-rss/index.md"},b=Object.assign(h,{setup(g){const r=s();return(p,u)=>(o(),i("div",null,[d,e("p",null,[n("59 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),f]))}});export{S as __pageData,b as default}; diff --git a/assets/garden_guide-to-incrementals_appeal-to-developers_index.md.CAI69wax.js b/assets/garden_guide-to-incrementals_appeal-to-developers_index.md.K8NRU4Sg.js similarity index 98% rename from assets/garden_guide-to-incrementals_appeal-to-developers_index.md.CAI69wax.js rename to assets/garden_guide-to-incrementals_appeal-to-developers_index.md.K8NRU4Sg.js index da78bd21..7bc8e7e1 100644 --- a/assets/garden_guide-to-incrementals_appeal-to-developers_index.md.CAI69wax.js +++ b/assets/garden_guide-to-incrementals_appeal-to-developers_index.md.K8NRU4Sg.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as i,j as e,a as r,k as a,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const m=e("h1",{class:"p-name"},"Guide to Incrementals/Appeal to Developers",-1),d=["innerHTML"],c=s('

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),b=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"}'),p={name:"garden/guide-to-incrementals/appeal-to-developers/index.md"},v=Object.assign(p,{setup(h){const t=o();return(u,g)=>(l(),i("div",null,[m,e("p",null,[r("636 words, ~3 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,d)]),c]))}});export{b as __pageData,v as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as i,j as e,a as r,k as a,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const m=e("h1",{class:"p-name"},"Guide to Incrementals/Appeal to Developers",-1),d=["innerHTML"],c=s('

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),b=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"}'),p={name:"garden/guide-to-incrementals/appeal-to-developers/index.md"},v=Object.assign(p,{setup(h){const t=o();return(u,g)=>(l(),i("div",null,[m,e("p",null,[r("636 words, ~3 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,d)]),c]))}});export{b as __pageData,v as default}; diff --git a/assets/garden_guide-to-incrementals_appeal-to-developers_index.md.CAI69wax.lean.js b/assets/garden_guide-to-incrementals_appeal-to-developers_index.md.K8NRU4Sg.lean.js similarity index 93% rename from assets/garden_guide-to-incrementals_appeal-to-developers_index.md.CAI69wax.lean.js rename to assets/garden_guide-to-incrementals_appeal-to-developers_index.md.K8NRU4Sg.lean.js index 992a0f9d..5497f4eb 100644 --- a/assets/garden_guide-to-incrementals_appeal-to-developers_index.md.CAI69wax.lean.js +++ b/assets/garden_guide-to-incrementals_appeal-to-developers_index.md.K8NRU4Sg.lean.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as i,j as e,a as r,k as a,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const m=e("h1",{class:"p-name"},"Guide to Incrementals/Appeal to Developers",-1),d=["innerHTML"],c=s("",13),b=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"}'),p={name:"garden/guide-to-incrementals/appeal-to-developers/index.md"},v=Object.assign(p,{setup(h){const t=o();return(u,g)=>(l(),i("div",null,[m,e("p",null,[r("636 words, ~3 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,d)]),c]))}});export{b as __pageData,v as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as i,j as e,a as r,k as a,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const m=e("h1",{class:"p-name"},"Guide to Incrementals/Appeal to Developers",-1),d=["innerHTML"],c=s("",13),b=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"}'),p={name:"garden/guide-to-incrementals/appeal-to-developers/index.md"},v=Object.assign(p,{setup(h){const t=o();return(u,g)=>(l(),i("div",null,[m,e("p",null,[r("636 words, ~3 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,d)]),c]))}});export{b as __pageData,v as default}; diff --git a/assets/garden_guide-to-incrementals_appeal-to-players_index.md.BVOWwfyv.js b/assets/garden_guide-to-incrementals_appeal-to-players_index.md.BtS-sAfk.js similarity index 99% rename from assets/garden_guide-to-incrementals_appeal-to-players_index.md.BVOWwfyv.js rename to assets/garden_guide-to-incrementals_appeal-to-players_index.md.BtS-sAfk.js index dc3cc233..aa8bc2cb 100644 --- a/assets/garden_guide-to-incrementals_appeal-to-players_index.md.BVOWwfyv.js +++ b/assets/garden_guide-to-incrementals_appeal-to-players_index.md.BtS-sAfk.js @@ -1 +1 @@ -import{d as i}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as o,j as e,a as s,k as t,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"Guide to Incrementals/Appeal to Players",-1),m=["innerHTML"],g=r('

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),b=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"}'),d={name:"garden/guide-to-incrementals/appeal-to-players/index.md"},w=Object.assign(d,{setup(c){const a=n();return(p,u)=>(l(),o("div",null,[h,e("p",null,[s("2400 words, ~13 minute read. "),e("span",{innerHTML:t(i)[`site/${t(a).page.value.relativePath}`]},null,8,m)]),g]))}});export{b as __pageData,w as default}; +import{d as i}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as o,j as e,a as s,k as t,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"Guide to Incrementals/Appeal to Players",-1),m=["innerHTML"],g=r('

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),b=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"}'),d={name:"garden/guide-to-incrementals/appeal-to-players/index.md"},w=Object.assign(d,{setup(c){const a=n();return(p,u)=>(l(),o("div",null,[h,e("p",null,[s("2400 words, ~13 minute read. "),e("span",{innerHTML:t(i)[`site/${t(a).page.value.relativePath}`]},null,8,m)]),g]))}});export{b as __pageData,w as default}; diff --git a/assets/garden_guide-to-incrementals_appeal-to-players_index.md.BVOWwfyv.lean.js b/assets/garden_guide-to-incrementals_appeal-to-players_index.md.BtS-sAfk.lean.js similarity index 93% rename from assets/garden_guide-to-incrementals_appeal-to-players_index.md.BVOWwfyv.lean.js rename to assets/garden_guide-to-incrementals_appeal-to-players_index.md.BtS-sAfk.lean.js index bde44311..f0eecd8a 100644 --- a/assets/garden_guide-to-incrementals_appeal-to-players_index.md.BVOWwfyv.lean.js +++ b/assets/garden_guide-to-incrementals_appeal-to-players_index.md.BtS-sAfk.lean.js @@ -1 +1 @@ -import{d as i}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as o,j as e,a as s,k as t,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"Guide to Incrementals/Appeal to Players",-1),m=["innerHTML"],g=r("",28),b=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"}'),d={name:"garden/guide-to-incrementals/appeal-to-players/index.md"},w=Object.assign(d,{setup(c){const a=n();return(p,u)=>(l(),o("div",null,[h,e("p",null,[s("2400 words, ~13 minute read. "),e("span",{innerHTML:t(i)[`site/${t(a).page.value.relativePath}`]},null,8,m)]),g]))}});export{b as __pageData,w as default}; +import{d as i}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as o,j as e,a as s,k as t,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"Guide to Incrementals/Appeal to Players",-1),m=["innerHTML"],g=r("",28),b=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"}'),d={name:"garden/guide-to-incrementals/appeal-to-players/index.md"},w=Object.assign(d,{setup(c){const a=n();return(p,u)=>(l(),o("div",null,[h,e("p",null,[s("2400 words, ~13 minute read. "),e("span",{innerHTML:t(i)[`site/${t(a).page.value.relativePath}`]},null,8,m)]),g]))}});export{b as __pageData,w as default}; diff --git a/assets/garden_guide-to-incrementals_defining-the-genre_index.md.DnJeFnvy.js b/assets/garden_guide-to-incrementals_defining-the-genre_index.md.BHfFhLBp.js similarity index 99% rename from assets/garden_guide-to-incrementals_defining-the-genre_index.md.DnJeFnvy.js rename to assets/garden_guide-to-incrementals_defining-the-genre_index.md.BHfFhLBp.js index 8914c876..f516f1b7 100644 --- a/assets/garden_guide-to-incrementals_defining-the-genre_index.md.DnJeFnvy.js +++ b/assets/garden_guide-to-incrementals_defining-the-genre_index.md.BHfFhLBp.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as o,j as e,a as i,k as t,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"Guide to Incrementals/Defining the Genre",-1),m=["innerHTML"],g=s('

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),y=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"}'),c={name:"garden/guide-to-incrementals/defining-the-genre/index.md"},w=Object.assign(c,{setup(u){const a=n();return(d,p)=>(l(),o("div",null,[h,e("p",null,[i("3429 words, ~19 minute read. "),e("span",{innerHTML:t(r)[`site/${t(a).page.value.relativePath}`]},null,8,m)]),g]))}});export{y as __pageData,w as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as o,j as e,a as i,k as t,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"Guide to Incrementals/Defining the Genre",-1),m=["innerHTML"],g=s('

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),y=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"}'),c={name:"garden/guide-to-incrementals/defining-the-genre/index.md"},w=Object.assign(c,{setup(u){const a=n();return(d,p)=>(l(),o("div",null,[h,e("p",null,[i("3429 words, ~19 minute read. "),e("span",{innerHTML:t(r)[`site/${t(a).page.value.relativePath}`]},null,8,m)]),g]))}});export{y as __pageData,w as default}; diff --git a/assets/garden_guide-to-incrementals_defining-the-genre_index.md.DnJeFnvy.lean.js b/assets/garden_guide-to-incrementals_defining-the-genre_index.md.BHfFhLBp.lean.js similarity index 93% rename from assets/garden_guide-to-incrementals_defining-the-genre_index.md.DnJeFnvy.lean.js rename to assets/garden_guide-to-incrementals_defining-the-genre_index.md.BHfFhLBp.lean.js index 8484e468..500dc372 100644 --- a/assets/garden_guide-to-incrementals_defining-the-genre_index.md.DnJeFnvy.lean.js +++ b/assets/garden_guide-to-incrementals_defining-the-genre_index.md.BHfFhLBp.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as o,j as e,a as i,k as t,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"Guide to Incrementals/Defining the Genre",-1),m=["innerHTML"],g=s("",64),y=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"}'),c={name:"garden/guide-to-incrementals/defining-the-genre/index.md"},w=Object.assign(c,{setup(u){const a=n();return(d,p)=>(l(),o("div",null,[h,e("p",null,[i("3429 words, ~19 minute read. "),e("span",{innerHTML:t(r)[`site/${t(a).page.value.relativePath}`]},null,8,m)]),g]))}});export{y as __pageData,w as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as o,j as e,a as i,k as t,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"Guide to Incrementals/Defining the Genre",-1),m=["innerHTML"],g=s("",64),y=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"}'),c={name:"garden/guide-to-incrementals/defining-the-genre/index.md"},w=Object.assign(c,{setup(u){const a=n();return(d,p)=>(l(),o("div",null,[h,e("p",null,[i("3429 words, ~19 minute read. "),e("span",{innerHTML:t(r)[`site/${t(a).page.value.relativePath}`]},null,8,m)]),g]))}});export{y as __pageData,w as default}; diff --git a/assets/garden_guide-to-incrementals_index.md.ELvcPBGG.js b/assets/garden_guide-to-incrementals_index.md.dW5Hwzwj.js similarity index 98% rename from assets/garden_guide-to-incrementals_index.md.ELvcPBGG.js rename to assets/garden_guide-to-incrementals_index.md.dW5Hwzwj.js index d6359293..fc2eed69 100644 --- a/assets/garden_guide-to-incrementals_index.md.ELvcPBGG.js +++ b/assets/garden_guide-to-incrementals_index.md.dW5Hwzwj.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as i,c as o,j as e,a as r,k as a,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Guide to Incrementals",-1),m=["innerHTML"],c=s('

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),v=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"}'),g={name:"garden/guide-to-incrementals/index.md"},y=Object.assign(g,{setup(h){const t=i();return(u,p)=>(l(),o("div",null,[d,e("p",null,[r("251 words, ~1 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,m)]),c]))}});export{v as __pageData,y as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as i,c as o,j as e,a as r,k as a,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Guide to Incrementals",-1),m=["innerHTML"],c=s('

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),v=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"}'),g={name:"garden/guide-to-incrementals/index.md"},y=Object.assign(g,{setup(h){const t=i();return(u,p)=>(l(),o("div",null,[d,e("p",null,[r("251 words, ~1 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,m)]),c]))}});export{v as __pageData,y as default}; diff --git a/assets/garden_guide-to-incrementals_index.md.ELvcPBGG.lean.js b/assets/garden_guide-to-incrementals_index.md.dW5Hwzwj.lean.js similarity index 92% rename from assets/garden_guide-to-incrementals_index.md.ELvcPBGG.lean.js rename to assets/garden_guide-to-incrementals_index.md.dW5Hwzwj.lean.js index 96c5031c..d24c85bd 100644 --- a/assets/garden_guide-to-incrementals_index.md.ELvcPBGG.lean.js +++ b/assets/garden_guide-to-incrementals_index.md.dW5Hwzwj.lean.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as i,c as o,j as e,a as r,k as a,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Guide to Incrementals",-1),m=["innerHTML"],c=s("",11),v=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"}'),g={name:"garden/guide-to-incrementals/index.md"},y=Object.assign(g,{setup(h){const t=i();return(u,p)=>(l(),o("div",null,[d,e("p",null,[r("251 words, ~1 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,m)]),c]))}});export{v as __pageData,y as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as i,c as o,j as e,a as r,k as a,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Guide to Incrementals",-1),m=["innerHTML"],c=s("",11),v=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"}'),g={name:"garden/guide-to-incrementals/index.md"},y=Object.assign(g,{setup(h){const t=i();return(u,p)=>(l(),o("div",null,[d,e("p",null,[r("251 words, ~1 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,m)]),c]))}});export{v as __pageData,y as default}; diff --git a/assets/garden_guide-to-incrementals_navigating-criticism_index.md.Dl7LDZ8M.js b/assets/garden_guide-to-incrementals_navigating-criticism_index.md.NsATwqk1.js similarity index 98% rename from assets/garden_guide-to-incrementals_navigating-criticism_index.md.Dl7LDZ8M.js rename to assets/garden_guide-to-incrementals_navigating-criticism_index.md.NsATwqk1.js index d17db620..5626e034 100644 --- a/assets/garden_guide-to-incrementals_navigating-criticism_index.md.Dl7LDZ8M.js +++ b/assets/garden_guide-to-incrementals_navigating-criticism_index.md.NsATwqk1.js @@ -1 +1 @@ -import{d as i}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as o,j as e,a as s,k as t,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Guide to Incrementals/Navigating Criticism",-1),d=["innerHTML"],u=r('

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),v=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"}'),m={name:"garden/guide-to-incrementals/navigating-criticism/index.md"},b=Object.assign(m,{setup(h){const a=n();return(g,p)=>(l(),o("div",null,[c,e("p",null,[s("747 words, ~4 minute read. "),e("span",{innerHTML:t(i)[`site/${t(a).page.value.relativePath}`]},null,8,d)]),u]))}});export{v as __pageData,b as default}; +import{d as i}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as o,j as e,a as s,k as t,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Guide to Incrementals/Navigating Criticism",-1),d=["innerHTML"],u=r('

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),v=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"}'),m={name:"garden/guide-to-incrementals/navigating-criticism/index.md"},b=Object.assign(m,{setup(h){const a=n();return(g,p)=>(l(),o("div",null,[c,e("p",null,[s("747 words, ~4 minute read. "),e("span",{innerHTML:t(i)[`site/${t(a).page.value.relativePath}`]},null,8,d)]),u]))}});export{v as __pageData,b as default}; diff --git a/assets/garden_guide-to-incrementals_navigating-criticism_index.md.Dl7LDZ8M.lean.js b/assets/garden_guide-to-incrementals_navigating-criticism_index.md.NsATwqk1.lean.js similarity index 93% rename from assets/garden_guide-to-incrementals_navigating-criticism_index.md.Dl7LDZ8M.lean.js rename to assets/garden_guide-to-incrementals_navigating-criticism_index.md.NsATwqk1.lean.js index 3abc3928..3ea047c2 100644 --- a/assets/garden_guide-to-incrementals_navigating-criticism_index.md.Dl7LDZ8M.lean.js +++ b/assets/garden_guide-to-incrementals_navigating-criticism_index.md.NsATwqk1.lean.js @@ -1 +1 @@ -import{d as i}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as o,j as e,a as s,k as t,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Guide to Incrementals/Navigating Criticism",-1),d=["innerHTML"],u=r("",11),v=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"}'),m={name:"garden/guide-to-incrementals/navigating-criticism/index.md"},b=Object.assign(m,{setup(h){const a=n();return(g,p)=>(l(),o("div",null,[c,e("p",null,[s("747 words, ~4 minute read. "),e("span",{innerHTML:t(i)[`site/${t(a).page.value.relativePath}`]},null,8,d)]),u]))}});export{v as __pageData,b as default}; +import{d as i}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as o,j as e,a as s,k as t,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Guide to Incrementals/Navigating Criticism",-1),d=["innerHTML"],u=r("",11),v=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"}'),m={name:"garden/guide-to-incrementals/navigating-criticism/index.md"},b=Object.assign(m,{setup(h){const a=n();return(g,p)=>(l(),o("div",null,[c,e("p",null,[s("747 words, ~4 minute read. "),e("span",{innerHTML:t(i)[`site/${t(a).page.value.relativePath}`]},null,8,d)]),u]))}});export{v as __pageData,b as default}; diff --git a/assets/garden_guide-to-incrementals_what-is-content_index.md.CwKYJWZw.js b/assets/garden_guide-to-incrementals_what-is-content_index.md.DH0-e6tX.js similarity index 99% rename from assets/garden_guide-to-incrementals_what-is-content_index.md.CwKYJWZw.js rename to assets/garden_guide-to-incrementals_what-is-content_index.md.DH0-e6tX.js index 989a0efb..be7e2a20 100644 --- a/assets/garden_guide-to-incrementals_what-is-content_index.md.CwKYJWZw.js +++ b/assets/garden_guide-to-incrementals_what-is-content_index.md.DH0-e6tX.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as i,j as e,a as s,k as t,a5 as r,o as h}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Guide to Incrementals/What is Content?",-1),c=["innerHTML"],u=r('

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),b=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"}'),m={name:"garden/guide-to-incrementals/what-is-content/index.md"},w=Object.assign(m,{setup(d){const a=o();return(g,p)=>(h(),i("div",null,[l,e("p",null,[s("2092 words, ~11 minute read. "),e("span",{innerHTML:t(n)[`site/${t(a).page.value.relativePath}`]},null,8,c)]),u]))}});export{b as __pageData,w as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as i,j as e,a as s,k as t,a5 as r,o as h}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Guide to Incrementals/What is Content?",-1),c=["innerHTML"],u=r('

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),b=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"}'),m={name:"garden/guide-to-incrementals/what-is-content/index.md"},w=Object.assign(m,{setup(d){const a=o();return(g,p)=>(h(),i("div",null,[l,e("p",null,[s("2092 words, ~11 minute read. "),e("span",{innerHTML:t(n)[`site/${t(a).page.value.relativePath}`]},null,8,c)]),u]))}});export{b as __pageData,w as default}; diff --git a/assets/garden_guide-to-incrementals_what-is-content_index.md.CwKYJWZw.lean.js b/assets/garden_guide-to-incrementals_what-is-content_index.md.DH0-e6tX.lean.js similarity index 93% rename from assets/garden_guide-to-incrementals_what-is-content_index.md.CwKYJWZw.lean.js rename to assets/garden_guide-to-incrementals_what-is-content_index.md.DH0-e6tX.lean.js index d3565bf6..2b867b1f 100644 --- a/assets/garden_guide-to-incrementals_what-is-content_index.md.CwKYJWZw.lean.js +++ b/assets/garden_guide-to-incrementals_what-is-content_index.md.DH0-e6tX.lean.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as i,j as e,a as s,k as t,a5 as r,o as h}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Guide to Incrementals/What is Content?",-1),c=["innerHTML"],u=r("",24),b=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"}'),m={name:"garden/guide-to-incrementals/what-is-content/index.md"},w=Object.assign(m,{setup(d){const a=o();return(g,p)=>(h(),i("div",null,[l,e("p",null,[s("2092 words, ~11 minute read. "),e("span",{innerHTML:t(n)[`site/${t(a).page.value.relativePath}`]},null,8,c)]),u]))}});export{b as __pageData,w as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as i,j as e,a as s,k as t,a5 as r,o as h}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Guide to Incrementals/What is Content?",-1),c=["innerHTML"],u=r("",24),b=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"}'),m={name:"garden/guide-to-incrementals/what-is-content/index.md"},w=Object.assign(m,{setup(d){const a=o();return(g,p)=>(h(),i("div",null,[l,e("p",null,[s("2092 words, ~11 minute read. "),e("span",{innerHTML:t(n)[`site/${t(a).page.value.relativePath}`]},null,8,c)]),u]))}});export{b as __pageData,w as default}; diff --git a/assets/garden_incremental-social_index.md.DbJXv224.js b/assets/garden_incremental-social_index.md.DaKqcO1b.js similarity index 95% rename from assets/garden_incremental-social_index.md.DbJXv224.js rename to assets/garden_incremental-social_index.md.DaKqcO1b.js index b89b4c4e..98f978c0 100644 --- a/assets/garden_incremental-social_index.md.DbJXv224.js +++ b/assets/garden_incremental-social_index.md.DaKqcO1b.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as r,c as s,j as e,a as o,k as a,a5 as i,o as c}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Incremental Social",-1),d=["innerHTML"],p=i('

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),b=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"}'),_={name:"garden/incremental-social/index.md"},y=Object.assign(_,{setup(m){const n=r();return(f,g)=>(c(),s("div",null,[l,e("p",null,[o("20 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(n).page.value.relativePath}`]},null,8,d)]),p]))}});export{b as __pageData,y as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as r,c as s,j as e,a as o,k as a,a5 as i,o as c}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Incremental Social",-1),d=["innerHTML"],p=i('

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),b=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"}'),_={name:"garden/incremental-social/index.md"},y=Object.assign(_,{setup(m){const n=r();return(f,g)=>(c(),s("div",null,[l,e("p",null,[o("20 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(n).page.value.relativePath}`]},null,8,d)]),p]))}});export{b as __pageData,y as default}; diff --git a/assets/garden_incremental-social_index.md.DbJXv224.lean.js b/assets/garden_incremental-social_index.md.DaKqcO1b.lean.js similarity index 92% rename from assets/garden_incremental-social_index.md.DbJXv224.lean.js rename to assets/garden_incremental-social_index.md.DaKqcO1b.lean.js index 43c6804a..f7b7b4bf 100644 --- a/assets/garden_incremental-social_index.md.DbJXv224.lean.js +++ b/assets/garden_incremental-social_index.md.DaKqcO1b.lean.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as r,c as s,j as e,a as o,k as a,a5 as i,o as c}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Incremental Social",-1),d=["innerHTML"],p=i("",6),b=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"}'),_={name:"garden/incremental-social/index.md"},y=Object.assign(_,{setup(m){const n=r();return(f,g)=>(c(),s("div",null,[l,e("p",null,[o("20 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(n).page.value.relativePath}`]},null,8,d)]),p]))}});export{b as __pageData,y as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as r,c as s,j as e,a as o,k as a,a5 as i,o as c}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Incremental Social",-1),d=["innerHTML"],p=i("",6),b=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"}'),_={name:"garden/incremental-social/index.md"},y=Object.assign(_,{setup(m){const n=r();return(f,g)=>(c(),s("div",null,[l,e("p",null,[o("20 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(n).page.value.relativePath}`]},null,8,d)]),p]))}});export{b as __pageData,y as default}; diff --git a/assets/garden_ivy-road_index.md.p78T1xXN.js b/assets/garden_ivy-road_index.md.DEYj6m9c.js similarity index 94% rename from assets/garden_ivy-road_index.md.p78T1xXN.js rename to assets/garden_ivy-road_index.md.DEYj6m9c.js index 73be1362..2b71a436 100644 --- a/assets/garden_ivy-road_index.md.p78T1xXN.js +++ b/assets/garden_ivy-road_index.md.DEYj6m9c.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as d,c as n,j as e,a as o,k as a,a5 as s,o as i}from"./chunks/framework.BIC8H_hJ.js";const _=e("h1",{class:"p-name"},"Ivy Road",-1),c=["innerHTML"],l=s('

Referenced by: Davey Wreden, Wanderstop

Tags: Davey Wreden

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

',4),h=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"}'),p={name:"garden/ivy-road/index.md"},m=Object.assign(p,{setup(u){const r=d();return(v,f)=>(i(),n("div",null,[_,e("p",null,[o("6 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),l]))}});export{h as __pageData,m as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as d,c as n,j as e,a as o,k as a,a5 as s,o as i}from"./chunks/framework.BIC8H_hJ.js";const _=e("h1",{class:"p-name"},"Ivy Road",-1),c=["innerHTML"],l=s('

Referenced by: Davey Wreden, Wanderstop

Tags: Davey Wreden

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

',4),h=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"}'),p={name:"garden/ivy-road/index.md"},m=Object.assign(p,{setup(u){const r=d();return(v,f)=>(i(),n("div",null,[_,e("p",null,[o("6 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),l]))}});export{h as __pageData,m as default}; diff --git a/assets/garden_ivy-road_index.md.p78T1xXN.lean.js b/assets/garden_ivy-road_index.md.DEYj6m9c.lean.js similarity index 91% rename from assets/garden_ivy-road_index.md.p78T1xXN.lean.js rename to assets/garden_ivy-road_index.md.DEYj6m9c.lean.js index a3cd0c1d..fe3dd4a5 100644 --- a/assets/garden_ivy-road_index.md.p78T1xXN.lean.js +++ b/assets/garden_ivy-road_index.md.DEYj6m9c.lean.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as d,c as n,j as e,a as o,k as a,a5 as s,o as i}from"./chunks/framework.BIC8H_hJ.js";const _=e("h1",{class:"p-name"},"Ivy Road",-1),c=["innerHTML"],l=s("",4),h=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"}'),p={name:"garden/ivy-road/index.md"},m=Object.assign(p,{setup(u){const r=d();return(v,f)=>(i(),n("div",null,[_,e("p",null,[o("6 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),l]))}});export{h as __pageData,m as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as d,c as n,j as e,a as o,k as a,a5 as s,o as i}from"./chunks/framework.BIC8H_hJ.js";const _=e("h1",{class:"p-name"},"Ivy Road",-1),c=["innerHTML"],l=s("",4),h=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"}'),p={name:"garden/ivy-road/index.md"},m=Object.assign(p,{setup(u){const r=d();return(v,f)=>(i(),n("div",null,[_,e("p",null,[o("6 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),l]))}});export{h as __pageData,m as default}; diff --git a/assets/garden_kronos_index.md.BPoR1tPW.js b/assets/garden_kronos_index.md.fo69wtFv.js similarity index 95% rename from assets/garden_kronos_index.md.BPoR1tPW.js rename to assets/garden_kronos_index.md.fo69wtFv.js index 9961a507..2c702a43 100644 --- a/assets/garden_kronos_index.md.BPoR1tPW.js +++ b/assets/garden_kronos_index.md.fo69wtFv.js @@ -1 +1 @@ -import{d as o}from"./chunks/git.data.BUKN53Ta.js";import{u as r,c as n,j as e,a as s,k as a,a5 as l,o as i}from"./chunks/framework.BIC8H_hJ.js";const p=e("h1",{class:"p-name"},"Kronos",-1),c=["innerHTML"],d=l('

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),k=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"}'),u={name:"garden/kronos/index.md"},b=Object.assign(u,{setup(_){const t=r();return(m,h)=>(i(),n("div",null,[p,e("p",null,[s("60 words, ~0 minute read. "),e("span",{innerHTML:a(o)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),d]))}});export{k as __pageData,b as default}; +import{d as o}from"./chunks/git.data.pqelWCHe.js";import{u as r,c as n,j as e,a as s,k as a,a5 as l,o as i}from"./chunks/framework.BIC8H_hJ.js";const p=e("h1",{class:"p-name"},"Kronos",-1),c=["innerHTML"],d=l('

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),k=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"}'),u={name:"garden/kronos/index.md"},b=Object.assign(u,{setup(_){const t=r();return(m,h)=>(i(),n("div",null,[p,e("p",null,[s("60 words, ~0 minute read. "),e("span",{innerHTML:a(o)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),d]))}});export{k as __pageData,b as default}; diff --git a/assets/garden_kronos_index.md.BPoR1tPW.lean.js b/assets/garden_kronos_index.md.fo69wtFv.lean.js similarity index 91% rename from assets/garden_kronos_index.md.BPoR1tPW.lean.js rename to assets/garden_kronos_index.md.fo69wtFv.lean.js index 63d1c9f1..cbf5a434 100644 --- a/assets/garden_kronos_index.md.BPoR1tPW.lean.js +++ b/assets/garden_kronos_index.md.fo69wtFv.lean.js @@ -1 +1 @@ -import{d as o}from"./chunks/git.data.BUKN53Ta.js";import{u as r,c as n,j as e,a as s,k as a,a5 as l,o as i}from"./chunks/framework.BIC8H_hJ.js";const p=e("h1",{class:"p-name"},"Kronos",-1),c=["innerHTML"],d=l("",7),k=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"}'),u={name:"garden/kronos/index.md"},b=Object.assign(u,{setup(_){const t=r();return(m,h)=>(i(),n("div",null,[p,e("p",null,[s("60 words, ~0 minute read. "),e("span",{innerHTML:a(o)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),d]))}});export{k as __pageData,b as default}; +import{d as o}from"./chunks/git.data.pqelWCHe.js";import{u as r,c as n,j as e,a as s,k as a,a5 as l,o as i}from"./chunks/framework.BIC8H_hJ.js";const p=e("h1",{class:"p-name"},"Kronos",-1),c=["innerHTML"],d=l("",7),k=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"}'),u={name:"garden/kronos/index.md"},b=Object.assign(u,{setup(_){const t=r();return(m,h)=>(i(),n("div",null,[p,e("p",null,[s("60 words, ~0 minute read. "),e("span",{innerHTML:a(o)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),d]))}});export{k as __pageData,b as default}; diff --git a/assets/garden_life-is-strange_index.md.BihXPWLv.js b/assets/garden_life-is-strange_index.md.CYMELw9c.js similarity index 99% rename from assets/garden_life-is-strange_index.md.BihXPWLv.js rename to assets/garden_life-is-strange_index.md.CYMELw9c.js index 833ac923..315ec9b4 100644 --- a/assets/garden_life-is-strange_index.md.BihXPWLv.js +++ b/assets/garden_life-is-strange_index.md.CYMELw9c.js @@ -1 +1 @@ -import{u as i,c as r,j as e,a as s,k as t,a5 as o,o as n,ag as l,ah as h}from"./chunks/framework.BIC8H_hJ.js";import{d}from"./chunks/git.data.BUKN53Ta.js";const g=e("h1",{class:"p-name"},"Life is Strange",-1),c=["innerHTML"],m=o('

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),b=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"}'),u={name:"garden/life-is-strange/index.md"},v=Object.assign(u,{setup(f){const a=i();return(p,w)=>(n(),r("div",null,[g,e("p",null,[s("654 words, ~4 minute read. "),e("span",{innerHTML:t(d)[`site/${t(a).page.value.relativePath}`]},null,8,c)]),m]))}});export{b as __pageData,v as default}; +import{u as i,c as r,j as e,a as s,k as t,a5 as o,o as n,ag as l,ah as h}from"./chunks/framework.BIC8H_hJ.js";import{d}from"./chunks/git.data.pqelWCHe.js";const g=e("h1",{class:"p-name"},"Life is Strange",-1),c=["innerHTML"],m=o('

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),b=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"}'),u={name:"garden/life-is-strange/index.md"},v=Object.assign(u,{setup(f){const a=i();return(p,w)=>(n(),r("div",null,[g,e("p",null,[s("654 words, ~4 minute read. "),e("span",{innerHTML:t(d)[`site/${t(a).page.value.relativePath}`]},null,8,c)]),m]))}});export{b as __pageData,v as default}; diff --git a/assets/garden_life-is-strange_index.md.BihXPWLv.lean.js b/assets/garden_life-is-strange_index.md.CYMELw9c.lean.js similarity index 91% rename from assets/garden_life-is-strange_index.md.BihXPWLv.lean.js rename to assets/garden_life-is-strange_index.md.CYMELw9c.lean.js index 45b68a25..eb169e6a 100644 --- a/assets/garden_life-is-strange_index.md.BihXPWLv.lean.js +++ b/assets/garden_life-is-strange_index.md.CYMELw9c.lean.js @@ -1 +1 @@ -import{u as i,c as r,j as e,a as s,k as t,a5 as o,o as n,ag as l,ah as h}from"./chunks/framework.BIC8H_hJ.js";import{d}from"./chunks/git.data.BUKN53Ta.js";const g=e("h1",{class:"p-name"},"Life is Strange",-1),c=["innerHTML"],m=o("",25),b=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"}'),u={name:"garden/life-is-strange/index.md"},v=Object.assign(u,{setup(f){const a=i();return(p,w)=>(n(),r("div",null,[g,e("p",null,[s("654 words, ~4 minute read. "),e("span",{innerHTML:t(d)[`site/${t(a).page.value.relativePath}`]},null,8,c)]),m]))}});export{b as __pageData,v as default}; +import{u as i,c as r,j as e,a as s,k as t,a5 as o,o as n,ag as l,ah as h}from"./chunks/framework.BIC8H_hJ.js";import{d}from"./chunks/git.data.pqelWCHe.js";const g=e("h1",{class:"p-name"},"Life is Strange",-1),c=["innerHTML"],m=o("",25),b=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"}'),u={name:"garden/life-is-strange/index.md"},v=Object.assign(u,{setup(f){const a=i();return(p,w)=>(n(),r("div",null,[g,e("p",null,[s("654 words, ~4 minute read. "),e("span",{innerHTML:t(d)[`site/${t(a).page.value.relativePath}`]},null,8,c)]),m]))}});export{b as __pageData,v as default}; diff --git a/assets/garden_logseq_index.md.B3Y44Cac.js b/assets/garden_logseq_index.md.DPP8FcR8.js similarity index 94% rename from assets/garden_logseq_index.md.B3Y44Cac.js rename to assets/garden_logseq_index.md.DPP8FcR8.js index 8efb60e3..63df5c5c 100644 --- a/assets/garden_logseq_index.md.B3Y44Cac.js +++ b/assets/garden_logseq_index.md.DPP8FcR8.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as r,j as e,a,k as t,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Logseq",-1),i=["innerHTML"],c=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/command-palettes/"},"Command Palettes"),a(", "),e("a",{href:"/garden/this-knowledge-hub/"},"This Knowledge Hub")])],-1),g=e("p",null,[e("a",{href:"https://logseq.com",target:"_blank",rel:"noreferrer"},"Logseq"),a(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),a(" outlining software")],-1),b=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"}'),p={name:"garden/logseq/index.md"},x=Object.assign(p,{setup(_){const s=o();return(h,m)=>(l(),r("div",null,[d,e("p",null,[a("3 words, ~0 minute read. "),e("span",{innerHTML:t(n)[`site/${t(s).page.value.relativePath}`]},null,8,i)]),c,u,g]))}});export{b as __pageData,x as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as r,j as e,a,k as t,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Logseq",-1),i=["innerHTML"],c=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/command-palettes/"},"Command Palettes"),a(", "),e("a",{href:"/garden/this-knowledge-hub/"},"This Knowledge Hub")])],-1),g=e("p",null,[e("a",{href:"https://logseq.com",target:"_blank",rel:"noreferrer"},"Logseq"),a(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),a(" outlining software")],-1),b=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"}'),p={name:"garden/logseq/index.md"},x=Object.assign(p,{setup(_){const s=o();return(h,m)=>(l(),r("div",null,[d,e("p",null,[a("3 words, ~0 minute read. "),e("span",{innerHTML:t(n)[`site/${t(s).page.value.relativePath}`]},null,8,i)]),c,u,g]))}});export{b as __pageData,x as default}; diff --git a/assets/garden_logseq_index.md.B3Y44Cac.lean.js b/assets/garden_logseq_index.md.DPP8FcR8.lean.js similarity index 94% rename from assets/garden_logseq_index.md.B3Y44Cac.lean.js rename to assets/garden_logseq_index.md.DPP8FcR8.lean.js index 8efb60e3..63df5c5c 100644 --- a/assets/garden_logseq_index.md.B3Y44Cac.lean.js +++ b/assets/garden_logseq_index.md.DPP8FcR8.lean.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as r,j as e,a,k as t,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Logseq",-1),i=["innerHTML"],c=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/command-palettes/"},"Command Palettes"),a(", "),e("a",{href:"/garden/this-knowledge-hub/"},"This Knowledge Hub")])],-1),g=e("p",null,[e("a",{href:"https://logseq.com",target:"_blank",rel:"noreferrer"},"Logseq"),a(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),a(" outlining software")],-1),b=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"}'),p={name:"garden/logseq/index.md"},x=Object.assign(p,{setup(_){const s=o();return(h,m)=>(l(),r("div",null,[d,e("p",null,[a("3 words, ~0 minute read. "),e("span",{innerHTML:t(n)[`site/${t(s).page.value.relativePath}`]},null,8,i)]),c,u,g]))}});export{b as __pageData,x as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as r,j as e,a,k as t,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Logseq",-1),i=["innerHTML"],c=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/command-palettes/"},"Command Palettes"),a(", "),e("a",{href:"/garden/this-knowledge-hub/"},"This Knowledge Hub")])],-1),g=e("p",null,[e("a",{href:"https://logseq.com",target:"_blank",rel:"noreferrer"},"Logseq"),a(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),a(" outlining software")],-1),b=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"}'),p={name:"garden/logseq/index.md"},x=Object.assign(p,{setup(_){const s=o();return(h,m)=>(l(),r("div",null,[d,e("p",null,[a("3 words, ~0 minute read. "),e("span",{innerHTML:t(n)[`site/${t(s).page.value.relativePath}`]},null,8,i)]),c,u,g]))}});export{b as __pageData,x as default}; diff --git a/assets/garden_matrix_index.md.BEX0nAgV.js b/assets/garden_matrix_index.md.DuLU0VEp.js similarity index 93% rename from assets/garden_matrix_index.md.BEX0nAgV.js rename to assets/garden_matrix_index.md.DuLU0VEp.js index c77e9508..2899ffcc 100644 --- a/assets/garden_matrix_index.md.BEX0nAgV.js +++ b/assets/garden_matrix_index.md.DuLU0VEp.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as s,j as e,a as i,k as a,a5 as o,o as d}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Matrix",-1),_=["innerHTML"],l=o('

Referenced by: Cinny, Commune, Synapse

Matrix is a protocol for Decentralized messaging

',3),x=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"}'),p={name:"garden/matrix/index.md"},T=Object.assign(p,{setup(m){const t=n();return(u,f)=>(d(),s("div",null,[c,e("p",null,[i("2 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,_)]),l]))}});export{x as __pageData,T as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as s,j as e,a as i,k as a,a5 as o,o as d}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Matrix",-1),_=["innerHTML"],l=o('

Referenced by: Cinny, Commune, Synapse

Matrix is a protocol for Decentralized messaging

',3),x=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"}'),p={name:"garden/matrix/index.md"},T=Object.assign(p,{setup(m){const t=n();return(u,f)=>(d(),s("div",null,[c,e("p",null,[i("2 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,_)]),l]))}});export{x as __pageData,T as default}; diff --git a/assets/garden_matrix_index.md.BEX0nAgV.lean.js b/assets/garden_matrix_index.md.DuLU0VEp.lean.js similarity index 91% rename from assets/garden_matrix_index.md.BEX0nAgV.lean.js rename to assets/garden_matrix_index.md.DuLU0VEp.lean.js index 4a16cfa4..a0c322a7 100644 --- a/assets/garden_matrix_index.md.BEX0nAgV.lean.js +++ b/assets/garden_matrix_index.md.DuLU0VEp.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as s,j as e,a as i,k as a,a5 as o,o as d}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Matrix",-1),_=["innerHTML"],l=o("",3),x=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"}'),p={name:"garden/matrix/index.md"},T=Object.assign(p,{setup(m){const t=n();return(u,f)=>(d(),s("div",null,[c,e("p",null,[i("2 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,_)]),l]))}});export{x as __pageData,T as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as s,j as e,a as i,k as a,a5 as o,o as d}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Matrix",-1),_=["innerHTML"],l=o("",3),x=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"}'),p={name:"garden/matrix/index.md"},T=Object.assign(p,{setup(m){const t=n();return(u,f)=>(d(),s("div",null,[c,e("p",null,[i("2 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,_)]),l]))}});export{x as __pageData,T as default}; diff --git a/assets/garden_mbin_index.md.LX2QNMDg.js b/assets/garden_mbin_index.md.ZZDbXLwf.js similarity index 94% rename from assets/garden_mbin_index.md.LX2QNMDg.js rename to assets/garden_mbin_index.md.ZZDbXLwf.js index fc2aa2d2..1fdff8be 100644 --- a/assets/garden_mbin_index.md.LX2QNMDg.js +++ b/assets/garden_mbin_index.md.ZZDbXLwf.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as i,j as e,a as t,k as n,o}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Mbin",-1),d=["innerHTML"],c=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/incremental-social/"},"Incremental Social")])],-1),_=e("p",null,[e("a",{href:"https://github.com/MbinOrg/mbin",target:"_blank",rel:"noreferrer"},"Mbin"),t(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),t(),e("a",{href:"/garden/fediverse/"},"Fediverse"),t(" software")],-1),p=e("p",null,"Can show both twitter-style posts and reddit-style threads",-1),x=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"}'),h={name:"garden/mbin/index.md"},M=Object.assign(h,{setup(m){const a=s();return(f,b)=>(o(),i("div",null,[l,e("p",null,[t("12 words, ~0 minute read. "),e("span",{innerHTML:n(r)[`site/${n(a).page.value.relativePath}`]},null,8,d)]),c,u,_,p]))}});export{x as __pageData,M as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as i,j as e,a as t,k as n,o}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Mbin",-1),d=["innerHTML"],c=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/incremental-social/"},"Incremental Social")])],-1),_=e("p",null,[e("a",{href:"https://github.com/MbinOrg/mbin",target:"_blank",rel:"noreferrer"},"Mbin"),t(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),t(),e("a",{href:"/garden/fediverse/"},"Fediverse"),t(" software")],-1),p=e("p",null,"Can show both twitter-style posts and reddit-style threads",-1),x=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"}'),h={name:"garden/mbin/index.md"},M=Object.assign(h,{setup(m){const a=s();return(f,b)=>(o(),i("div",null,[l,e("p",null,[t("12 words, ~0 minute read. "),e("span",{innerHTML:n(r)[`site/${n(a).page.value.relativePath}`]},null,8,d)]),c,u,_,p]))}});export{x as __pageData,M as default}; diff --git a/assets/garden_mbin_index.md.LX2QNMDg.lean.js b/assets/garden_mbin_index.md.ZZDbXLwf.lean.js similarity index 94% rename from assets/garden_mbin_index.md.LX2QNMDg.lean.js rename to assets/garden_mbin_index.md.ZZDbXLwf.lean.js index fc2aa2d2..1fdff8be 100644 --- a/assets/garden_mbin_index.md.LX2QNMDg.lean.js +++ b/assets/garden_mbin_index.md.ZZDbXLwf.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as i,j as e,a as t,k as n,o}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Mbin",-1),d=["innerHTML"],c=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/incremental-social/"},"Incremental Social")])],-1),_=e("p",null,[e("a",{href:"https://github.com/MbinOrg/mbin",target:"_blank",rel:"noreferrer"},"Mbin"),t(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),t(),e("a",{href:"/garden/fediverse/"},"Fediverse"),t(" software")],-1),p=e("p",null,"Can show both twitter-style posts and reddit-style threads",-1),x=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"}'),h={name:"garden/mbin/index.md"},M=Object.assign(h,{setup(m){const a=s();return(f,b)=>(o(),i("div",null,[l,e("p",null,[t("12 words, ~0 minute read. "),e("span",{innerHTML:n(r)[`site/${n(a).page.value.relativePath}`]},null,8,d)]),c,u,_,p]))}});export{x as __pageData,M as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as i,j as e,a as t,k as n,o}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Mbin",-1),d=["innerHTML"],c=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/incremental-social/"},"Incremental Social")])],-1),_=e("p",null,[e("a",{href:"https://github.com/MbinOrg/mbin",target:"_blank",rel:"noreferrer"},"Mbin"),t(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),t(),e("a",{href:"/garden/fediverse/"},"Fediverse"),t(" software")],-1),p=e("p",null,"Can show both twitter-style posts and reddit-style threads",-1),x=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"}'),h={name:"garden/mbin/index.md"},M=Object.assign(h,{setup(m){const a=s();return(f,b)=>(o(),i("div",null,[l,e("p",null,[t("12 words, ~0 minute read. "),e("span",{innerHTML:n(r)[`site/${n(a).page.value.relativePath}`]},null,8,d)]),c,u,_,p]))}});export{x as __pageData,M as default}; diff --git a/assets/garden_mtx_index.md.8LNgjod3.js b/assets/garden_mtx_index.md.CH_HN224.js similarity index 93% rename from assets/garden_mtx_index.md.8LNgjod3.js rename to assets/garden_mtx_index.md.CH_HN224.js index f91d216d..7678a1e9 100644 --- a/assets/garden_mtx_index.md.8LNgjod3.js +++ b/assets/garden_mtx_index.md.CH_HN224.js @@ -1 +1 @@ -import{d as s}from"./chunks/git.data.BUKN53Ta.js";import{u as r,c as i,j as e,a,k as t,o}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"MTX",-1),c=["innerHTML"],d=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/premium-currency/"},"Premium Currency"),a(", "),e("a",{href:"/garden/video-game-monetization/"},"Video Game Monetization")])],-1),m=e("p",null,"Purchaseable items in video games that cost real life currencies",-1),v=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"}'),p={name:"garden/mtx/index.md"},M=Object.assign(p,{setup(_){const n=r();return(h,f)=>(o(),i("div",null,[l,e("p",null,[a("10 words, ~0 minute read. "),e("span",{innerHTML:t(s)[`site/${t(n).page.value.relativePath}`]},null,8,c)]),d,u,m]))}});export{v as __pageData,M as default}; +import{d as s}from"./chunks/git.data.pqelWCHe.js";import{u as r,c as i,j as e,a,k as t,o}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"MTX",-1),c=["innerHTML"],d=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/premium-currency/"},"Premium Currency"),a(", "),e("a",{href:"/garden/video-game-monetization/"},"Video Game Monetization")])],-1),m=e("p",null,"Purchaseable items in video games that cost real life currencies",-1),v=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"}'),p={name:"garden/mtx/index.md"},M=Object.assign(p,{setup(_){const n=r();return(h,f)=>(o(),i("div",null,[l,e("p",null,[a("10 words, ~0 minute read. "),e("span",{innerHTML:t(s)[`site/${t(n).page.value.relativePath}`]},null,8,c)]),d,u,m]))}});export{v as __pageData,M as default}; diff --git a/assets/garden_mtx_index.md.8LNgjod3.lean.js b/assets/garden_mtx_index.md.CH_HN224.lean.js similarity index 93% rename from assets/garden_mtx_index.md.8LNgjod3.lean.js rename to assets/garden_mtx_index.md.CH_HN224.lean.js index f91d216d..7678a1e9 100644 --- a/assets/garden_mtx_index.md.8LNgjod3.lean.js +++ b/assets/garden_mtx_index.md.CH_HN224.lean.js @@ -1 +1 @@ -import{d as s}from"./chunks/git.data.BUKN53Ta.js";import{u as r,c as i,j as e,a,k as t,o}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"MTX",-1),c=["innerHTML"],d=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/premium-currency/"},"Premium Currency"),a(", "),e("a",{href:"/garden/video-game-monetization/"},"Video Game Monetization")])],-1),m=e("p",null,"Purchaseable items in video games that cost real life currencies",-1),v=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"}'),p={name:"garden/mtx/index.md"},M=Object.assign(p,{setup(_){const n=r();return(h,f)=>(o(),i("div",null,[l,e("p",null,[a("10 words, ~0 minute read. "),e("span",{innerHTML:t(s)[`site/${t(n).page.value.relativePath}`]},null,8,c)]),d,u,m]))}});export{v as __pageData,M as default}; +import{d as s}from"./chunks/git.data.pqelWCHe.js";import{u as r,c as i,j as e,a,k as t,o}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"MTX",-1),c=["innerHTML"],d=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/premium-currency/"},"Premium Currency"),a(", "),e("a",{href:"/garden/video-game-monetization/"},"Video Game Monetization")])],-1),m=e("p",null,"Purchaseable items in video games that cost real life currencies",-1),v=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"}'),p={name:"garden/mtx/index.md"},M=Object.assign(p,{setup(_){const n=r();return(h,f)=>(o(),i("div",null,[l,e("p",null,[a("10 words, ~0 minute read. "),e("span",{innerHTML:t(s)[`site/${t(n).page.value.relativePath}`]},null,8,c)]),d,u,m]))}});export{v as __pageData,M as default}; diff --git a/assets/garden_my-personal-website_index.md.DyFNC0MU.js b/assets/garden_my-personal-website_index.md.DM_scmXw.js similarity index 94% rename from assets/garden_my-personal-website_index.md.DyFNC0MU.js rename to assets/garden_my-personal-website_index.md.DM_scmXw.js index ce2f02a6..4eb7a225 100644 --- a/assets/garden_my-personal-website_index.md.DyFNC0MU.js +++ b/assets/garden_my-personal-website_index.md.DM_scmXw.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as l,c as n,j as e,a,k as t,o}from"./chunks/framework.BIC8H_hJ.js";const i=e("h1",{class:"p-name"},"My Personal Website",-1),p=["innerHTML"],d=e("hr",null,null,-1),c=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/the-small-web/"},"The Small Web")])],-1),_=e("p",null,[a("A "),e("a",{href:"/garden/the-small-web/"},"Personal Websites"),a(" for myself, available at "),e("a",{href:"https://thepaperpilot.org",target:"_blank",rel:"noreferrer"},"https://thepaperpilot.org")],-1),y=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"}'),h={name:"garden/my-personal-website/index.md"},w=Object.assign(h,{setup(u){const s=l();return(m,b)=>(o(),n("div",null,[i,e("p",null,[a("10 words, ~0 minute read. "),e("span",{innerHTML:t(r)[`site/${t(s).page.value.relativePath}`]},null,8,p)]),d,c,_]))}});export{y as __pageData,w as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as l,c as n,j as e,a,k as t,o}from"./chunks/framework.BIC8H_hJ.js";const i=e("h1",{class:"p-name"},"My Personal Website",-1),p=["innerHTML"],d=e("hr",null,null,-1),c=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/the-small-web/"},"The Small Web")])],-1),_=e("p",null,[a("A "),e("a",{href:"/garden/the-small-web/"},"Personal Websites"),a(" for myself, available at "),e("a",{href:"https://thepaperpilot.org",target:"_blank",rel:"noreferrer"},"https://thepaperpilot.org")],-1),y=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"}'),h={name:"garden/my-personal-website/index.md"},w=Object.assign(h,{setup(u){const s=l();return(m,b)=>(o(),n("div",null,[i,e("p",null,[a("10 words, ~0 minute read. "),e("span",{innerHTML:t(r)[`site/${t(s).page.value.relativePath}`]},null,8,p)]),d,c,_]))}});export{y as __pageData,w as default}; diff --git a/assets/garden_my-personal-website_index.md.DyFNC0MU.lean.js b/assets/garden_my-personal-website_index.md.DM_scmXw.lean.js similarity index 94% rename from assets/garden_my-personal-website_index.md.DyFNC0MU.lean.js rename to assets/garden_my-personal-website_index.md.DM_scmXw.lean.js index ce2f02a6..4eb7a225 100644 --- a/assets/garden_my-personal-website_index.md.DyFNC0MU.lean.js +++ b/assets/garden_my-personal-website_index.md.DM_scmXw.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as l,c as n,j as e,a,k as t,o}from"./chunks/framework.BIC8H_hJ.js";const i=e("h1",{class:"p-name"},"My Personal Website",-1),p=["innerHTML"],d=e("hr",null,null,-1),c=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/the-small-web/"},"The Small Web")])],-1),_=e("p",null,[a("A "),e("a",{href:"/garden/the-small-web/"},"Personal Websites"),a(" for myself, available at "),e("a",{href:"https://thepaperpilot.org",target:"_blank",rel:"noreferrer"},"https://thepaperpilot.org")],-1),y=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"}'),h={name:"garden/my-personal-website/index.md"},w=Object.assign(h,{setup(u){const s=l();return(m,b)=>(o(),n("div",null,[i,e("p",null,[a("10 words, ~0 minute read. "),e("span",{innerHTML:t(r)[`site/${t(s).page.value.relativePath}`]},null,8,p)]),d,c,_]))}});export{y as __pageData,w as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as l,c as n,j as e,a,k as t,o}from"./chunks/framework.BIC8H_hJ.js";const i=e("h1",{class:"p-name"},"My Personal Website",-1),p=["innerHTML"],d=e("hr",null,null,-1),c=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/the-small-web/"},"The Small Web")])],-1),_=e("p",null,[a("A "),e("a",{href:"/garden/the-small-web/"},"Personal Websites"),a(" for myself, available at "),e("a",{href:"https://thepaperpilot.org",target:"_blank",rel:"noreferrer"},"https://thepaperpilot.org")],-1),y=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"}'),h={name:"garden/my-personal-website/index.md"},w=Object.assign(h,{setup(u){const s=l();return(m,b)=>(o(),n("div",null,[i,e("p",null,[a("10 words, ~0 minute read. "),e("span",{innerHTML:t(r)[`site/${t(s).page.value.relativePath}`]},null,8,p)]),d,c,_]))}});export{y as __pageData,w as default}; diff --git a/assets/garden_my-projects_index.md.WruDkTLa.js b/assets/garden_my-projects_index.md.PcKN-fzF.js similarity index 97% rename from assets/garden_my-projects_index.md.WruDkTLa.js rename to assets/garden_my-projects_index.md.PcKN-fzF.js index 47812fa8..1849a5e4 100644 --- a/assets/garden_my-projects_index.md.WruDkTLa.js +++ b/assets/garden_my-projects_index.md.PcKN-fzF.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as o,j as e,a as l,k as a,a5 as i,o as s}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"My Projects",-1),c=["innerHTML"],h=i('

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),b=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"}'),p={name:"garden/my-projects/index.md"},v=Object.assign(p,{setup(g){const r=n();return(m,f)=>(s(),o("div",null,[d,e("p",null,[l("72 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),h]))}});export{b as __pageData,v as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as o,j as e,a as l,k as a,a5 as i,o as s}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"My Projects",-1),c=["innerHTML"],h=i('

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),b=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"}'),p={name:"garden/my-projects/index.md"},v=Object.assign(p,{setup(g){const r=n();return(m,f)=>(s(),o("div",null,[d,e("p",null,[l("72 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),h]))}});export{b as __pageData,v as default}; diff --git a/assets/garden_my-projects_index.md.WruDkTLa.lean.js b/assets/garden_my-projects_index.md.PcKN-fzF.lean.js similarity index 91% rename from assets/garden_my-projects_index.md.WruDkTLa.lean.js rename to assets/garden_my-projects_index.md.PcKN-fzF.lean.js index d804ac46..7831cfe4 100644 --- a/assets/garden_my-projects_index.md.WruDkTLa.lean.js +++ b/assets/garden_my-projects_index.md.PcKN-fzF.lean.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as o,j as e,a as l,k as a,a5 as i,o as s}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"My Projects",-1),c=["innerHTML"],h=i("",7),b=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"}'),p={name:"garden/my-projects/index.md"},v=Object.assign(p,{setup(g){const r=n();return(m,f)=>(s(),o("div",null,[d,e("p",null,[l("72 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),h]))}});export{b as __pageData,v as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as o,j as e,a as l,k as a,a5 as i,o as s}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"My Projects",-1),c=["innerHTML"],h=i("",7),b=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"}'),p={name:"garden/my-projects/index.md"},v=Object.assign(p,{setup(g){const r=n();return(m,f)=>(s(),o("div",null,[d,e("p",null,[l("72 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),h]))}});export{b as __pageData,v as default}; diff --git a/assets/garden_nostr_index.md.DeFQ_p4c.js b/assets/garden_nostr_index.md.CSTpQOla.js similarity index 94% rename from assets/garden_nostr_index.md.DeFQ_p4c.js rename to assets/garden_nostr_index.md.CSTpQOla.js index f6940b53..43d94f99 100644 --- a/assets/garden_nostr_index.md.DeFQ_p4c.js +++ b/assets/garden_nostr_index.md.CSTpQOla.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as o,j as e,a as t,k as a,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Nostr",-1),i=["innerHTML"],c=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/fediverse/"},"Fediverse")])],-1),_=e("blockquote",null,[e("p",null,[t("Tags: "),e("a",{href:"/garden/decentralized/"},"Decentralized")])],-1),p=e("p",null,[e("a",{href:"https://nostr.com",target:"_blank",rel:"noreferrer"},"Nostr"),t(" is a protocol for "),e("a",{href:"/garden/fediverse/"},"Federated Social Media")],-1),N=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"}'),f={name:"garden/nostr/index.md"},b=Object.assign(f,{setup(h){const r=s();return(g,m)=>(l(),o("div",null,[d,e("p",null,[t("8 words, ~0 minute read. "),e("span",{innerHTML:a(n)[`site/${a(r).page.value.relativePath}`]},null,8,i)]),c,u,_,p]))}});export{N as __pageData,b as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as o,j as e,a as t,k as a,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Nostr",-1),i=["innerHTML"],c=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/fediverse/"},"Fediverse")])],-1),_=e("blockquote",null,[e("p",null,[t("Tags: "),e("a",{href:"/garden/decentralized/"},"Decentralized")])],-1),p=e("p",null,[e("a",{href:"https://nostr.com",target:"_blank",rel:"noreferrer"},"Nostr"),t(" is a protocol for "),e("a",{href:"/garden/fediverse/"},"Federated Social Media")],-1),N=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"}'),f={name:"garden/nostr/index.md"},b=Object.assign(f,{setup(h){const r=s();return(g,m)=>(l(),o("div",null,[d,e("p",null,[t("8 words, ~0 minute read. "),e("span",{innerHTML:a(n)[`site/${a(r).page.value.relativePath}`]},null,8,i)]),c,u,_,p]))}});export{N as __pageData,b as default}; diff --git a/assets/garden_nostr_index.md.DeFQ_p4c.lean.js b/assets/garden_nostr_index.md.CSTpQOla.lean.js similarity index 94% rename from assets/garden_nostr_index.md.DeFQ_p4c.lean.js rename to assets/garden_nostr_index.md.CSTpQOla.lean.js index f6940b53..43d94f99 100644 --- a/assets/garden_nostr_index.md.DeFQ_p4c.lean.js +++ b/assets/garden_nostr_index.md.CSTpQOla.lean.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as o,j as e,a as t,k as a,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Nostr",-1),i=["innerHTML"],c=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/fediverse/"},"Fediverse")])],-1),_=e("blockquote",null,[e("p",null,[t("Tags: "),e("a",{href:"/garden/decentralized/"},"Decentralized")])],-1),p=e("p",null,[e("a",{href:"https://nostr.com",target:"_blank",rel:"noreferrer"},"Nostr"),t(" is a protocol for "),e("a",{href:"/garden/fediverse/"},"Federated Social Media")],-1),N=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"}'),f={name:"garden/nostr/index.md"},b=Object.assign(f,{setup(h){const r=s();return(g,m)=>(l(),o("div",null,[d,e("p",null,[t("8 words, ~0 minute read. "),e("span",{innerHTML:a(n)[`site/${a(r).page.value.relativePath}`]},null,8,i)]),c,u,_,p]))}});export{N as __pageData,b as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as o,j as e,a as t,k as a,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Nostr",-1),i=["innerHTML"],c=e("hr",null,null,-1),u=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/fediverse/"},"Fediverse")])],-1),_=e("blockquote",null,[e("p",null,[t("Tags: "),e("a",{href:"/garden/decentralized/"},"Decentralized")])],-1),p=e("p",null,[e("a",{href:"https://nostr.com",target:"_blank",rel:"noreferrer"},"Nostr"),t(" is a protocol for "),e("a",{href:"/garden/fediverse/"},"Federated Social Media")],-1),N=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"}'),f={name:"garden/nostr/index.md"},b=Object.assign(f,{setup(h){const r=s();return(g,m)=>(l(),o("div",null,[d,e("p",null,[t("8 words, ~0 minute read. "),e("span",{innerHTML:a(n)[`site/${a(r).page.value.relativePath}`]},null,8,i)]),c,u,_,p]))}});export{N as __pageData,b as default}; diff --git a/assets/garden_open-source_index.md.C491r43H.js b/assets/garden_open-source_index.md.DuvAPmO4.js similarity index 95% rename from assets/garden_open-source_index.md.C491r43H.js rename to assets/garden_open-source_index.md.DuvAPmO4.js index cf3d15a4..3d35cfa9 100644 --- a/assets/garden_open-source_index.md.C491r43H.js +++ b/assets/garden_open-source_index.md.DuvAPmO4.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as t,c as s,j as e,a as o,k as a,a5 as c,o as d}from"./chunks/framework.BIC8H_hJ.js";const i=e("h1",{class:"p-name"},"Open Source",-1),p=["innerHTML"],l=c('

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),T=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"}'),u={name:"garden/open-source/index.md"},b=Object.assign(u,{setup(h){const r=t();return(g,_)=>(d(),s("div",null,[i,e("p",null,[o("25 words, ~0 minute read. "),e("span",{innerHTML:a(n)[`site/${a(r).page.value.relativePath}`]},null,8,p)]),l]))}});export{T as __pageData,b as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as t,c as s,j as e,a as o,k as a,a5 as c,o as d}from"./chunks/framework.BIC8H_hJ.js";const i=e("h1",{class:"p-name"},"Open Source",-1),p=["innerHTML"],l=c('

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),T=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"}'),u={name:"garden/open-source/index.md"},b=Object.assign(u,{setup(h){const r=t();return(g,_)=>(d(),s("div",null,[i,e("p",null,[o("25 words, ~0 minute read. "),e("span",{innerHTML:a(n)[`site/${a(r).page.value.relativePath}`]},null,8,p)]),l]))}});export{T as __pageData,b as default}; diff --git a/assets/garden_open-source_index.md.C491r43H.lean.js b/assets/garden_open-source_index.md.DuvAPmO4.lean.js similarity index 91% rename from assets/garden_open-source_index.md.C491r43H.lean.js rename to assets/garden_open-source_index.md.DuvAPmO4.lean.js index 9eaa0edd..25e17185 100644 --- a/assets/garden_open-source_index.md.C491r43H.lean.js +++ b/assets/garden_open-source_index.md.DuvAPmO4.lean.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as t,c as s,j as e,a as o,k as a,a5 as c,o as d}from"./chunks/framework.BIC8H_hJ.js";const i=e("h1",{class:"p-name"},"Open Source",-1),p=["innerHTML"],l=c("",4),T=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"}'),u={name:"garden/open-source/index.md"},b=Object.assign(u,{setup(h){const r=t();return(g,_)=>(d(),s("div",null,[i,e("p",null,[o("25 words, ~0 minute read. "),e("span",{innerHTML:a(n)[`site/${a(r).page.value.relativePath}`]},null,8,p)]),l]))}});export{T as __pageData,b as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as t,c as s,j as e,a as o,k as a,a5 as c,o as d}from"./chunks/framework.BIC8H_hJ.js";const i=e("h1",{class:"p-name"},"Open Source",-1),p=["innerHTML"],l=c("",4),T=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"}'),u={name:"garden/open-source/index.md"},b=Object.assign(u,{setup(h){const r=t();return(g,_)=>(d(),s("div",null,[i,e("p",null,[o("25 words, ~0 minute read. "),e("span",{innerHTML:a(n)[`site/${a(r).page.value.relativePath}`]},null,8,p)]),l]))}});export{T as __pageData,b as default}; diff --git a/assets/garden_opti-speech_index.md.DN4EnHzm.js b/assets/garden_opti-speech_index.md.B-Gx7i7-.js similarity index 98% rename from assets/garden_opti-speech_index.md.DN4EnHzm.js rename to assets/garden_opti-speech_index.md.B-Gx7i7-.js index 50200aa7..c532ba52 100644 --- a/assets/garden_opti-speech_index.md.DN4EnHzm.js +++ b/assets/garden_opti-speech_index.md.B-Gx7i7-.js @@ -1 +1 @@ -import{u as r,c as o,j as e,a as s,k as t,a5 as a,o as n,ai as l,aj as c,ak as p,al as d}from"./chunks/framework.BIC8H_hJ.js";import{d as h}from"./chunks/git.data.BUKN53Ta.js";const m=e("h1",{class:"p-name"},"Opti-Speech",-1),u=["innerHTML"],g=a('

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).

',6),_=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),f=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),v=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),b=a('

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.

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

',7),O=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"}'),w={name:"garden/opti-speech/index.md"},S=Object.assign(w,{setup(y){const i=r();return(T,k)=>(n(),o("div",null,[m,e("p",null,[s("312 words, ~2 minute read. "),e("span",{innerHTML:t(h)[`site/${t(i).page.value.relativePath}`]},null,8,u)]),g,_,f,v,b]))}});export{O as __pageData,S as default}; +import{u as r,c as o,j as e,a as s,k as t,a5 as a,o as n,ai as l,aj as c,ak as p,al as d}from"./chunks/framework.BIC8H_hJ.js";import{d as h}from"./chunks/git.data.pqelWCHe.js";const m=e("h1",{class:"p-name"},"Opti-Speech",-1),u=["innerHTML"],g=a('

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).

',6),_=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),f=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),v=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),b=a('

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.

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

',7),O=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"}'),w={name:"garden/opti-speech/index.md"},S=Object.assign(w,{setup(y){const i=r();return(T,k)=>(n(),o("div",null,[m,e("p",null,[s("312 words, ~2 minute read. "),e("span",{innerHTML:t(h)[`site/${t(i).page.value.relativePath}`]},null,8,u)]),g,_,f,v,b]))}});export{O as __pageData,S as default}; diff --git a/assets/garden_opti-speech_index.md.DN4EnHzm.lean.js b/assets/garden_opti-speech_index.md.B-Gx7i7-.lean.js similarity index 96% rename from assets/garden_opti-speech_index.md.DN4EnHzm.lean.js rename to assets/garden_opti-speech_index.md.B-Gx7i7-.lean.js index 1973320b..cfde706e 100644 --- a/assets/garden_opti-speech_index.md.DN4EnHzm.lean.js +++ b/assets/garden_opti-speech_index.md.B-Gx7i7-.lean.js @@ -1 +1 @@ -import{u as r,c as o,j as e,a as s,k as t,a5 as a,o as n,ai as l,aj as c,ak as p,al as d}from"./chunks/framework.BIC8H_hJ.js";import{d as h}from"./chunks/git.data.BUKN53Ta.js";const m=e("h1",{class:"p-name"},"Opti-Speech",-1),u=["innerHTML"],g=a("",6),_=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),f=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),v=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),b=a("",7),O=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"}'),w={name:"garden/opti-speech/index.md"},S=Object.assign(w,{setup(y){const i=r();return(T,k)=>(n(),o("div",null,[m,e("p",null,[s("312 words, ~2 minute read. "),e("span",{innerHTML:t(h)[`site/${t(i).page.value.relativePath}`]},null,8,u)]),g,_,f,v,b]))}});export{O as __pageData,S as default}; +import{u as r,c as o,j as e,a as s,k as t,a5 as a,o as n,ai as l,aj as c,ak as p,al as d}from"./chunks/framework.BIC8H_hJ.js";import{d as h}from"./chunks/git.data.pqelWCHe.js";const m=e("h1",{class:"p-name"},"Opti-Speech",-1),u=["innerHTML"],g=a("",6),_=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),f=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),v=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),b=a("",7),O=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"}'),w={name:"garden/opti-speech/index.md"},S=Object.assign(w,{setup(y){const i=r();return(T,k)=>(n(),o("div",null,[m,e("p",null,[s("312 words, ~2 minute read. "),e("span",{innerHTML:t(h)[`site/${t(i).page.value.relativePath}`]},null,8,u)]),g,_,f,v,b]))}});export{O as __pageData,S as default}; diff --git a/assets/garden_planar-pioneers_index.md.CMufsH2U.js b/assets/garden_planar-pioneers_index.md.Bxqtb01r.js similarity index 95% rename from assets/garden_planar-pioneers_index.md.CMufsH2U.js rename to assets/garden_planar-pioneers_index.md.Bxqtb01r.js index b1ce4bca..5467e31c 100644 --- a/assets/garden_planar-pioneers_index.md.CMufsH2U.js +++ b/assets/garden_planar-pioneers_index.md.Bxqtb01r.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as n,j as e,a as o,k as a,a5 as p,o as i}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Planar Pioneers",-1),c=["innerHTML"],d=p('

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),P=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"}'),_={name:"garden/planar-pioneers/index.md"},T=Object.assign(_,{setup(h){const r=s();return(f,u)=>(i(),n("div",null,[l,e("p",null,[o("25 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),d]))}});export{P as __pageData,T as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as n,j as e,a as o,k as a,a5 as p,o as i}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Planar Pioneers",-1),c=["innerHTML"],d=p('

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),P=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"}'),_={name:"garden/planar-pioneers/index.md"},T=Object.assign(_,{setup(h){const r=s();return(f,u)=>(i(),n("div",null,[l,e("p",null,[o("25 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),d]))}});export{P as __pageData,T as default}; diff --git a/assets/garden_planar-pioneers_index.md.CMufsH2U.lean.js b/assets/garden_planar-pioneers_index.md.Bxqtb01r.lean.js similarity index 92% rename from assets/garden_planar-pioneers_index.md.CMufsH2U.lean.js rename to assets/garden_planar-pioneers_index.md.Bxqtb01r.lean.js index 37f80b15..9bfdfd69 100644 --- a/assets/garden_planar-pioneers_index.md.CMufsH2U.lean.js +++ b/assets/garden_planar-pioneers_index.md.Bxqtb01r.lean.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as n,j as e,a as o,k as a,a5 as p,o as i}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Planar Pioneers",-1),c=["innerHTML"],d=p("",5),P=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"}'),_={name:"garden/planar-pioneers/index.md"},T=Object.assign(_,{setup(h){const r=s();return(f,u)=>(i(),n("div",null,[l,e("p",null,[o("25 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),d]))}});export{P as __pageData,T as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as n,j as e,a as o,k as a,a5 as p,o as i}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Planar Pioneers",-1),c=["innerHTML"],d=p("",5),P=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"}'),_={name:"garden/planar-pioneers/index.md"},T=Object.assign(_,{setup(h){const r=s();return(f,u)=>(i(),n("div",null,[l,e("p",null,[o("25 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),d]))}});export{P as __pageData,T as default}; diff --git a/assets/garden_pre-order-bonuses_index.md.CNCIw0CK.js b/assets/garden_pre-order-bonuses_index.md.C4h9RmIa.js similarity index 96% rename from assets/garden_pre-order-bonuses_index.md.CNCIw0CK.js rename to assets/garden_pre-order-bonuses_index.md.C4h9RmIa.js index 8ae49938..b26830cd 100644 --- a/assets/garden_pre-order-bonuses_index.md.CNCIw0CK.js +++ b/assets/garden_pre-order-bonuses_index.md.C4h9RmIa.js @@ -1 +1 @@ -import{d as a}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as t,j as e,a as l,k as i,a5 as r,o as n}from"./chunks/framework.BIC8H_hJ.js";const u=e("h1",{class:"p-name"},"Pre-Order Bonuses",-1),d=["innerHTML"],c=r('

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),b=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"}'),p={name:"garden/pre-order-bonuses/index.md"},y=Object.assign(p,{setup(m){const s=o();return(_,h)=>(n(),t("div",null,[u,e("p",null,[l("98 words, ~1 minute read. "),e("span",{innerHTML:i(a)[`site/${i(s).page.value.relativePath}`]},null,8,d)]),c]))}});export{b as __pageData,y as default}; +import{d as a}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as t,j as e,a as l,k as i,a5 as r,o as n}from"./chunks/framework.BIC8H_hJ.js";const u=e("h1",{class:"p-name"},"Pre-Order Bonuses",-1),d=["innerHTML"],c=r('

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),b=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"}'),p={name:"garden/pre-order-bonuses/index.md"},y=Object.assign(p,{setup(m){const s=o();return(_,h)=>(n(),t("div",null,[u,e("p",null,[l("98 words, ~1 minute read. "),e("span",{innerHTML:i(a)[`site/${i(s).page.value.relativePath}`]},null,8,d)]),c]))}});export{b as __pageData,y as default}; diff --git a/assets/garden_pre-order-bonuses_index.md.CNCIw0CK.lean.js b/assets/garden_pre-order-bonuses_index.md.C4h9RmIa.lean.js similarity index 92% rename from assets/garden_pre-order-bonuses_index.md.CNCIw0CK.lean.js rename to assets/garden_pre-order-bonuses_index.md.C4h9RmIa.lean.js index 863c256c..21b24899 100644 --- a/assets/garden_pre-order-bonuses_index.md.CNCIw0CK.lean.js +++ b/assets/garden_pre-order-bonuses_index.md.C4h9RmIa.lean.js @@ -1 +1 @@ -import{d as a}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as t,j as e,a as l,k as i,a5 as r,o as n}from"./chunks/framework.BIC8H_hJ.js";const u=e("h1",{class:"p-name"},"Pre-Order Bonuses",-1),d=["innerHTML"],c=r("",7),b=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"}'),p={name:"garden/pre-order-bonuses/index.md"},y=Object.assign(p,{setup(m){const s=o();return(_,h)=>(n(),t("div",null,[u,e("p",null,[l("98 words, ~1 minute read. "),e("span",{innerHTML:i(a)[`site/${i(s).page.value.relativePath}`]},null,8,d)]),c]))}});export{b as __pageData,y as default}; +import{d as a}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as t,j as e,a as l,k as i,a5 as r,o as n}from"./chunks/framework.BIC8H_hJ.js";const u=e("h1",{class:"p-name"},"Pre-Order Bonuses",-1),d=["innerHTML"],c=r("",7),b=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"}'),p={name:"garden/pre-order-bonuses/index.md"},y=Object.assign(p,{setup(m){const s=o();return(_,h)=>(n(),t("div",null,[u,e("p",null,[l("98 words, ~1 minute read. "),e("span",{innerHTML:i(a)[`site/${i(s).page.value.relativePath}`]},null,8,d)]),c]))}});export{b as __pageData,y as default}; diff --git a/assets/garden_premium-currency_index.md.CdZaDSOd.js b/assets/garden_premium-currency_index.md.Dx5rwYTw.js similarity index 95% rename from assets/garden_premium-currency_index.md.CdZaDSOd.js rename to assets/garden_premium-currency_index.md.Dx5rwYTw.js index d1a15378..20ec8a3c 100644 --- a/assets/garden_premium-currency_index.md.CdZaDSOd.js +++ b/assets/garden_premium-currency_index.md.Dx5rwYTw.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as n,j as e,a as i,k as r,a5 as o,o as c}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Premium Currency",-1),u=["innerHTML"],d=o('

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),y=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"}'),m={name:"garden/premium-currency/index.md"},v=Object.assign(m,{setup(p){const a=s();return(_,f)=>(c(),n("div",null,[l,e("p",null,[i("71 words, ~0 minute read. "),e("span",{innerHTML:r(t)[`site/${r(a).page.value.relativePath}`]},null,8,u)]),d]))}});export{y as __pageData,v as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as n,j as e,a as i,k as r,a5 as o,o as c}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Premium Currency",-1),u=["innerHTML"],d=o('

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),y=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"}'),m={name:"garden/premium-currency/index.md"},v=Object.assign(m,{setup(p){const a=s();return(_,f)=>(c(),n("div",null,[l,e("p",null,[i("71 words, ~0 minute read. "),e("span",{innerHTML:r(t)[`site/${r(a).page.value.relativePath}`]},null,8,u)]),d]))}});export{y as __pageData,v as default}; diff --git a/assets/garden_premium-currency_index.md.CdZaDSOd.lean.js b/assets/garden_premium-currency_index.md.Dx5rwYTw.lean.js similarity index 91% rename from assets/garden_premium-currency_index.md.CdZaDSOd.lean.js rename to assets/garden_premium-currency_index.md.Dx5rwYTw.lean.js index 6bf34599..6a9dd51a 100644 --- a/assets/garden_premium-currency_index.md.CdZaDSOd.lean.js +++ b/assets/garden_premium-currency_index.md.Dx5rwYTw.lean.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as n,j as e,a as i,k as r,a5 as o,o as c}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Premium Currency",-1),u=["innerHTML"],d=o("",5),y=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"}'),m={name:"garden/premium-currency/index.md"},v=Object.assign(m,{setup(p){const a=s();return(_,f)=>(c(),n("div",null,[l,e("p",null,[i("71 words, ~0 minute read. "),e("span",{innerHTML:r(t)[`site/${r(a).page.value.relativePath}`]},null,8,u)]),d]))}});export{y as __pageData,v as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as n,j as e,a as i,k as r,a5 as o,o as c}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Premium Currency",-1),u=["innerHTML"],d=o("",5),y=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"}'),m={name:"garden/premium-currency/index.md"},v=Object.assign(m,{setup(p){const a=s();return(_,f)=>(c(),n("div",null,[l,e("p",null,[i("71 words, ~0 minute read. "),e("span",{innerHTML:r(t)[`site/${r(a).page.value.relativePath}`]},null,8,u)]),d]))}});export{y as __pageData,v as default}; diff --git a/assets/garden_profectus_index.md.BC07-N6d.js b/assets/garden_profectus_index.md.zl6sD7ik.js similarity index 96% rename from assets/garden_profectus_index.md.BC07-N6d.js rename to assets/garden_profectus_index.md.zl6sD7ik.js index a1def40e..cb8be8d1 100644 --- a/assets/garden_profectus_index.md.BC07-N6d.js +++ b/assets/garden_profectus_index.md.zl6sD7ik.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as o,j as e,a as s,k as a,a5 as i,o as c}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Profectus",-1),d=["innerHTML"],p=i('

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),b=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"}'),u={name:"garden/profectus/index.md"},P=Object.assign(u,{setup(f){const t=n();return(g,h)=>(c(),o("div",null,[l,e("p",null,[s("73 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,d)]),p]))}});export{b as __pageData,P as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as o,j as e,a as s,k as a,a5 as i,o as c}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Profectus",-1),d=["innerHTML"],p=i('

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),b=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"}'),u={name:"garden/profectus/index.md"},P=Object.assign(u,{setup(f){const t=n();return(g,h)=>(c(),o("div",null,[l,e("p",null,[s("73 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,d)]),p]))}});export{b as __pageData,P as default}; diff --git a/assets/garden_profectus_index.md.BC07-N6d.lean.js b/assets/garden_profectus_index.md.zl6sD7ik.lean.js similarity index 91% rename from assets/garden_profectus_index.md.BC07-N6d.lean.js rename to assets/garden_profectus_index.md.zl6sD7ik.lean.js index 5950950d..d079475b 100644 --- a/assets/garden_profectus_index.md.BC07-N6d.lean.js +++ b/assets/garden_profectus_index.md.zl6sD7ik.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as o,j as e,a as s,k as a,a5 as i,o as c}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Profectus",-1),d=["innerHTML"],p=i("",9),b=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"}'),u={name:"garden/profectus/index.md"},P=Object.assign(u,{setup(f){const t=n();return(g,h)=>(c(),o("div",null,[l,e("p",null,[s("73 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,d)]),p]))}});export{b as __pageData,P as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as o,j as e,a as s,k as a,a5 as i,o as c}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Profectus",-1),d=["innerHTML"],p=i("",9),b=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"}'),u={name:"garden/profectus/index.md"},P=Object.assign(u,{setup(f){const t=n();return(g,h)=>(c(),o("div",null,[l,e("p",null,[s("73 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,d)]),p]))}});export{b as __pageData,P as default}; diff --git a/assets/garden_social-media_index.md.BklGV2fi.js b/assets/garden_social-media_index.md.Bc71elCV.js similarity index 96% rename from assets/garden_social-media_index.md.BklGV2fi.js rename to assets/garden_social-media_index.md.Bc71elCV.js index a237afd7..190bd65c 100644 --- a/assets/garden_social-media_index.md.BklGV2fi.js +++ b/assets/garden_social-media_index.md.Bc71elCV.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as l,c as o,j as e,a as n,k as a,a5 as r,o as s}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Social Media",-1),c=["innerHTML"],u=r('

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),v=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"}'),p={name:"garden/social-media/index.md"},S=Object.assign(p,{setup(_){const i=l();return(m,h)=>(s(),o("div",null,[d,e("p",null,[n("98 words, ~1 minute read. "),e("span",{innerHTML:a(t)[`site/${a(i).page.value.relativePath}`]},null,8,c)]),u]))}});export{v as __pageData,S as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as l,c as o,j as e,a as n,k as a,a5 as r,o as s}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Social Media",-1),c=["innerHTML"],u=r('

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),v=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"}'),p={name:"garden/social-media/index.md"},S=Object.assign(p,{setup(_){const i=l();return(m,h)=>(s(),o("div",null,[d,e("p",null,[n("98 words, ~1 minute read. "),e("span",{innerHTML:a(t)[`site/${a(i).page.value.relativePath}`]},null,8,c)]),u]))}});export{v as __pageData,S as default}; diff --git a/assets/garden_social-media_index.md.BklGV2fi.lean.js b/assets/garden_social-media_index.md.Bc71elCV.lean.js similarity index 91% rename from assets/garden_social-media_index.md.BklGV2fi.lean.js rename to assets/garden_social-media_index.md.Bc71elCV.lean.js index ee058d37..c13d1c04 100644 --- a/assets/garden_social-media_index.md.BklGV2fi.lean.js +++ b/assets/garden_social-media_index.md.Bc71elCV.lean.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as l,c as o,j as e,a as n,k as a,a5 as r,o as s}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Social Media",-1),c=["innerHTML"],u=r("",7),v=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"}'),p={name:"garden/social-media/index.md"},S=Object.assign(p,{setup(_){const i=l();return(m,h)=>(s(),o("div",null,[d,e("p",null,[n("98 words, ~1 minute read. "),e("span",{innerHTML:a(t)[`site/${a(i).page.value.relativePath}`]},null,8,c)]),u]))}});export{v as __pageData,S as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as l,c as o,j as e,a as n,k as a,a5 as r,o as s}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Social Media",-1),c=["innerHTML"],u=r("",7),v=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"}'),p={name:"garden/social-media/index.md"},S=Object.assign(p,{setup(_){const i=l();return(m,h)=>(s(),o("div",null,[d,e("p",null,[n("98 words, ~1 minute read. "),e("span",{innerHTML:a(t)[`site/${a(i).page.value.relativePath}`]},null,8,c)]),u]))}});export{v as __pageData,S as default}; diff --git a/assets/garden_synapse_index.md.B9mv0QMw.js b/assets/garden_synapse_index.md.CSt75VkQ.js similarity index 94% rename from assets/garden_synapse_index.md.B9mv0QMw.js rename to assets/garden_synapse_index.md.CSt75VkQ.js index 7e3a9157..7125a178 100644 --- a/assets/garden_synapse_index.md.B9mv0QMw.js +++ b/assets/garden_synapse_index.md.CSt75VkQ.js @@ -1 +1 @@ -import{d as s}from"./chunks/git.data.BUKN53Ta.js";import{u as r,c as o,j as e,a,k as n,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Synapse",-1),i=["innerHTML"],p=e("hr",null,null,-1),d=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/incremental-social/"},"Incremental Social")])],-1),u=e("p",null,[e("a",{href:"https://github.com/element-hq/synapse",target:"_blank",rel:"noreferrer"},"Synapse"),a(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),a(" server software for the "),e("a",{href:"/garden/matrix/"},"Matrix"),a(" protocol")],-1),x=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"}'),_={name:"garden/synapse/index.md"},S=Object.assign(_,{setup(h){const t=r();return(f,m)=>(l(),o("div",null,[c,e("p",null,[a("2 words, ~0 minute read. "),e("span",{innerHTML:n(s)[`site/${n(t).page.value.relativePath}`]},null,8,i)]),p,d,u]))}});export{x as __pageData,S as default}; +import{d as s}from"./chunks/git.data.pqelWCHe.js";import{u as r,c as o,j as e,a,k as n,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Synapse",-1),i=["innerHTML"],p=e("hr",null,null,-1),d=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/incremental-social/"},"Incremental Social")])],-1),u=e("p",null,[e("a",{href:"https://github.com/element-hq/synapse",target:"_blank",rel:"noreferrer"},"Synapse"),a(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),a(" server software for the "),e("a",{href:"/garden/matrix/"},"Matrix"),a(" protocol")],-1),x=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"}'),_={name:"garden/synapse/index.md"},S=Object.assign(_,{setup(h){const t=r();return(f,m)=>(l(),o("div",null,[c,e("p",null,[a("2 words, ~0 minute read. "),e("span",{innerHTML:n(s)[`site/${n(t).page.value.relativePath}`]},null,8,i)]),p,d,u]))}});export{x as __pageData,S as default}; diff --git a/assets/garden_synapse_index.md.B9mv0QMw.lean.js b/assets/garden_synapse_index.md.CSt75VkQ.lean.js similarity index 94% rename from assets/garden_synapse_index.md.B9mv0QMw.lean.js rename to assets/garden_synapse_index.md.CSt75VkQ.lean.js index 7e3a9157..7125a178 100644 --- a/assets/garden_synapse_index.md.B9mv0QMw.lean.js +++ b/assets/garden_synapse_index.md.CSt75VkQ.lean.js @@ -1 +1 @@ -import{d as s}from"./chunks/git.data.BUKN53Ta.js";import{u as r,c as o,j as e,a,k as n,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Synapse",-1),i=["innerHTML"],p=e("hr",null,null,-1),d=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/incremental-social/"},"Incremental Social")])],-1),u=e("p",null,[e("a",{href:"https://github.com/element-hq/synapse",target:"_blank",rel:"noreferrer"},"Synapse"),a(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),a(" server software for the "),e("a",{href:"/garden/matrix/"},"Matrix"),a(" protocol")],-1),x=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"}'),_={name:"garden/synapse/index.md"},S=Object.assign(_,{setup(h){const t=r();return(f,m)=>(l(),o("div",null,[c,e("p",null,[a("2 words, ~0 minute read. "),e("span",{innerHTML:n(s)[`site/${n(t).page.value.relativePath}`]},null,8,i)]),p,d,u]))}});export{x as __pageData,S as default}; +import{d as s}from"./chunks/git.data.pqelWCHe.js";import{u as r,c as o,j as e,a,k as n,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Synapse",-1),i=["innerHTML"],p=e("hr",null,null,-1),d=e("blockquote",null,[e("p",null,[a("Referenced by: "),e("a",{href:"/garden/incremental-social/"},"Incremental Social")])],-1),u=e("p",null,[e("a",{href:"https://github.com/element-hq/synapse",target:"_blank",rel:"noreferrer"},"Synapse"),a(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),a(" server software for the "),e("a",{href:"/garden/matrix/"},"Matrix"),a(" protocol")],-1),x=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"}'),_={name:"garden/synapse/index.md"},S=Object.assign(_,{setup(h){const t=r();return(f,m)=>(l(),o("div",null,[c,e("p",null,[a("2 words, ~0 minute read. "),e("span",{innerHTML:n(s)[`site/${n(t).page.value.relativePath}`]},null,8,i)]),p,d,u]))}});export{x as __pageData,S as default}; diff --git a/assets/garden_the-beginner-s-guide_index.md.CoXWcRiO.js b/assets/garden_the-beginner-s-guide_index.md.aoBc3wIS.js similarity index 96% rename from assets/garden_the-beginner-s-guide_index.md.CoXWcRiO.js rename to assets/garden_the-beginner-s-guide_index.md.aoBc3wIS.js index 22d30971..4f0fc43f 100644 --- a/assets/garden_the-beginner-s-guide_index.md.CoXWcRiO.js +++ b/assets/garden_the-beginner-s-guide_index.md.aoBc3wIS.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as s,j as e,a as i,k as a,a5 as o,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"The Beginner's Guide",-1),u=["innerHTML"],c=o('

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),b=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"}`),p={name:"garden/the-beginner-s-guide/index.md"},v=Object.assign(p,{setup(h){const r=n();return(_,g)=>(l(),s("div",null,[d,e("p",null,[i("70 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,u)]),c]))}});export{b as __pageData,v as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as s,j as e,a as i,k as a,a5 as o,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"The Beginner's Guide",-1),u=["innerHTML"],c=o('

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),b=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"}`),p={name:"garden/the-beginner-s-guide/index.md"},v=Object.assign(p,{setup(h){const r=n();return(_,g)=>(l(),s("div",null,[d,e("p",null,[i("70 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,u)]),c]))}});export{b as __pageData,v as default}; diff --git a/assets/garden_the-beginner-s-guide_index.md.CoXWcRiO.lean.js b/assets/garden_the-beginner-s-guide_index.md.aoBc3wIS.lean.js similarity index 92% rename from assets/garden_the-beginner-s-guide_index.md.CoXWcRiO.lean.js rename to assets/garden_the-beginner-s-guide_index.md.aoBc3wIS.lean.js index cc060b77..8d2c1f38 100644 --- a/assets/garden_the-beginner-s-guide_index.md.CoXWcRiO.lean.js +++ b/assets/garden_the-beginner-s-guide_index.md.aoBc3wIS.lean.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as s,j as e,a as i,k as a,a5 as o,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"The Beginner's Guide",-1),u=["innerHTML"],c=o("",7),b=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"}`),p={name:"garden/the-beginner-s-guide/index.md"},v=Object.assign(p,{setup(h){const r=n();return(_,g)=>(l(),s("div",null,[d,e("p",null,[i("70 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,u)]),c]))}});export{b as __pageData,v as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as s,j as e,a as i,k as a,a5 as o,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"The Beginner's Guide",-1),u=["innerHTML"],c=o("",7),b=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"}`),p={name:"garden/the-beginner-s-guide/index.md"},v=Object.assign(p,{setup(h){const r=n();return(_,g)=>(l(),s("div",null,[d,e("p",null,[i("70 words, ~0 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,u)]),c]))}});export{b as __pageData,v as default}; diff --git a/assets/garden_the-cozy-web_index.md.B9Bc79u-.js b/assets/garden_the-cozy-web_index.md.BucEyy_I.js similarity index 95% rename from assets/garden_the-cozy-web_index.md.B9Bc79u-.js rename to assets/garden_the-cozy-web_index.md.BucEyy_I.js index abf01c95..369e3dd2 100644 --- a/assets/garden_the-cozy-web_index.md.B9Bc79u-.js +++ b/assets/garden_the-cozy-web_index.md.BucEyy_I.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as n,j as e,a as s,k as a,a5 as i,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"The Cozy Web",-1),h=["innerHTML"],p=i('

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),m=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"}'),c={name:"garden/the-cozy-web/index.md"},y=Object.assign(c,{setup(_){const t=o();return(b,f)=>(l(),n("div",null,[d,e("p",null,[s("45 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,h)]),p]))}});export{m as __pageData,y as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as n,j as e,a as s,k as a,a5 as i,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"The Cozy Web",-1),h=["innerHTML"],p=i('

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),m=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"}'),c={name:"garden/the-cozy-web/index.md"},y=Object.assign(c,{setup(_){const t=o();return(b,f)=>(l(),n("div",null,[d,e("p",null,[s("45 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,h)]),p]))}});export{m as __pageData,y as default}; diff --git a/assets/garden_the-cozy-web_index.md.B9Bc79u-.lean.js b/assets/garden_the-cozy-web_index.md.BucEyy_I.lean.js similarity index 91% rename from assets/garden_the-cozy-web_index.md.B9Bc79u-.lean.js rename to assets/garden_the-cozy-web_index.md.BucEyy_I.lean.js index 0d1580ff..4b94bdc9 100644 --- a/assets/garden_the-cozy-web_index.md.B9Bc79u-.lean.js +++ b/assets/garden_the-cozy-web_index.md.BucEyy_I.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as n,j as e,a as s,k as a,a5 as i,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"The Cozy Web",-1),h=["innerHTML"],p=i("",6),m=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"}'),c={name:"garden/the-cozy-web/index.md"},y=Object.assign(c,{setup(_){const t=o();return(b,f)=>(l(),n("div",null,[d,e("p",null,[s("45 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,h)]),p]))}});export{m as __pageData,y as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as n,j as e,a as s,k as a,a5 as i,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"The Cozy Web",-1),h=["innerHTML"],p=i("",6),m=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"}'),c={name:"garden/the-cozy-web/index.md"},y=Object.assign(c,{setup(_){const t=o();return(b,f)=>(l(),n("div",null,[d,e("p",null,[s("45 words, ~0 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,h)]),p]))}});export{m as __pageData,y as default}; diff --git a/assets/garden_the-indieweb_amplification_index.md.jlLNuI0B.js b/assets/garden_the-indieweb_amplification_index.md.feCX0iGU.js similarity index 95% rename from assets/garden_the-indieweb_amplification_index.md.jlLNuI0B.js rename to assets/garden_the-indieweb_amplification_index.md.feCX0iGU.js index 66819ad6..fa846227 100644 --- a/assets/garden_the-indieweb_amplification_index.md.jlLNuI0B.js +++ b/assets/garden_the-indieweb_amplification_index.md.feCX0iGU.js @@ -1 +1 @@ -import{d as i}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as o,j as e,a as t,k as a,o as r}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"The IndieWeb/Amplification",-1),d=["innerHTML"],c=e("hr",null,null,-1),h=e("p",null,"Refers to reblogging (and re-hosting, sometimes) of someone else's content on your own site",-1),p=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"),t(" discusses some ideas and best practices for amplification")],-1),m=e("p",null,[t("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),T=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"}'),u={name:"garden/the-indieweb/amplification/index.md"},x=Object.assign(u,{setup(f){const n=s();return(_,b)=>(r(),o("div",null,[l,e("p",null,[t("57 words, ~0 minute read. "),e("span",{innerHTML:a(i)[`site/${a(n).page.value.relativePath}`]},null,8,d)]),c,h,p,m]))}});export{T as __pageData,x as default}; +import{d as i}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as o,j as e,a as t,k as a,o as r}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"The IndieWeb/Amplification",-1),d=["innerHTML"],c=e("hr",null,null,-1),h=e("p",null,"Refers to reblogging (and re-hosting, sometimes) of someone else's content on your own site",-1),p=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"),t(" discusses some ideas and best practices for amplification")],-1),m=e("p",null,[t("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),T=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"}'),u={name:"garden/the-indieweb/amplification/index.md"},x=Object.assign(u,{setup(f){const n=s();return(_,b)=>(r(),o("div",null,[l,e("p",null,[t("57 words, ~0 minute read. "),e("span",{innerHTML:a(i)[`site/${a(n).page.value.relativePath}`]},null,8,d)]),c,h,p,m]))}});export{T as __pageData,x as default}; diff --git a/assets/garden_the-indieweb_amplification_index.md.jlLNuI0B.lean.js b/assets/garden_the-indieweb_amplification_index.md.feCX0iGU.lean.js similarity index 95% rename from assets/garden_the-indieweb_amplification_index.md.jlLNuI0B.lean.js rename to assets/garden_the-indieweb_amplification_index.md.feCX0iGU.lean.js index 66819ad6..fa846227 100644 --- a/assets/garden_the-indieweb_amplification_index.md.jlLNuI0B.lean.js +++ b/assets/garden_the-indieweb_amplification_index.md.feCX0iGU.lean.js @@ -1 +1 @@ -import{d as i}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as o,j as e,a as t,k as a,o as r}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"The IndieWeb/Amplification",-1),d=["innerHTML"],c=e("hr",null,null,-1),h=e("p",null,"Refers to reblogging (and re-hosting, sometimes) of someone else's content on your own site",-1),p=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"),t(" discusses some ideas and best practices for amplification")],-1),m=e("p",null,[t("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),T=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"}'),u={name:"garden/the-indieweb/amplification/index.md"},x=Object.assign(u,{setup(f){const n=s();return(_,b)=>(r(),o("div",null,[l,e("p",null,[t("57 words, ~0 minute read. "),e("span",{innerHTML:a(i)[`site/${a(n).page.value.relativePath}`]},null,8,d)]),c,h,p,m]))}});export{T as __pageData,x as default}; +import{d as i}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as o,j as e,a as t,k as a,o as r}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"The IndieWeb/Amplification",-1),d=["innerHTML"],c=e("hr",null,null,-1),h=e("p",null,"Refers to reblogging (and re-hosting, sometimes) of someone else's content on your own site",-1),p=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"),t(" discusses some ideas and best practices for amplification")],-1),m=e("p",null,[t("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),T=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"}'),u={name:"garden/the-indieweb/amplification/index.md"},x=Object.assign(u,{setup(f){const n=s();return(_,b)=>(r(),o("div",null,[l,e("p",null,[t("57 words, ~0 minute read. "),e("span",{innerHTML:a(i)[`site/${a(n).page.value.relativePath}`]},null,8,d)]),c,h,p,m]))}});export{T as __pageData,x as default}; diff --git a/assets/garden_the-indieweb_signature-blocks_index.md.CDtNXTYD.js b/assets/garden_the-indieweb_signature-blocks_index.md.Cl2M6pHI.js similarity index 93% rename from assets/garden_the-indieweb_signature-blocks_index.md.CDtNXTYD.js rename to assets/garden_the-indieweb_signature-blocks_index.md.Cl2M6pHI.js index c08e2169..cbcfbcb5 100644 --- a/assets/garden_the-indieweb_signature-blocks_index.md.CDtNXTYD.js +++ b/assets/garden_the-indieweb_signature-blocks_index.md.Cl2M6pHI.js @@ -1 +1 @@ -import{d as s}from"./chunks/git.data.BUKN53Ta.js";import{u as i,c as r,j as e,a as t,k as a,o}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"The IndieWeb/Signature Blocks",-1),d=["innerHTML"],c=e("hr",null,null,-1),u=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),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"}'),p={name:"garden/the-indieweb/signature-blocks/index.md"},k=Object.assign(p,{setup(h){const n=i();return(_,g)=>(o(),r("div",null,[l,e("p",null,[t("14 words, ~0 minute read. "),e("span",{innerHTML:a(s)[`site/${a(n).page.value.relativePath}`]},null,8,d)]),c,u]))}});export{f as __pageData,k as default}; +import{d as s}from"./chunks/git.data.pqelWCHe.js";import{u as i,c as r,j as e,a as t,k as a,o}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"The IndieWeb/Signature Blocks",-1),d=["innerHTML"],c=e("hr",null,null,-1),u=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),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"}'),p={name:"garden/the-indieweb/signature-blocks/index.md"},k=Object.assign(p,{setup(h){const n=i();return(_,g)=>(o(),r("div",null,[l,e("p",null,[t("14 words, ~0 minute read. "),e("span",{innerHTML:a(s)[`site/${a(n).page.value.relativePath}`]},null,8,d)]),c,u]))}});export{f as __pageData,k as default}; diff --git a/assets/garden_the-indieweb_signature-blocks_index.md.CDtNXTYD.lean.js b/assets/garden_the-indieweb_signature-blocks_index.md.Cl2M6pHI.lean.js similarity index 93% rename from assets/garden_the-indieweb_signature-blocks_index.md.CDtNXTYD.lean.js rename to assets/garden_the-indieweb_signature-blocks_index.md.Cl2M6pHI.lean.js index c08e2169..cbcfbcb5 100644 --- a/assets/garden_the-indieweb_signature-blocks_index.md.CDtNXTYD.lean.js +++ b/assets/garden_the-indieweb_signature-blocks_index.md.Cl2M6pHI.lean.js @@ -1 +1 @@ -import{d as s}from"./chunks/git.data.BUKN53Ta.js";import{u as i,c as r,j as e,a as t,k as a,o}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"The IndieWeb/Signature Blocks",-1),d=["innerHTML"],c=e("hr",null,null,-1),u=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),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"}'),p={name:"garden/the-indieweb/signature-blocks/index.md"},k=Object.assign(p,{setup(h){const n=i();return(_,g)=>(o(),r("div",null,[l,e("p",null,[t("14 words, ~0 minute read. "),e("span",{innerHTML:a(s)[`site/${a(n).page.value.relativePath}`]},null,8,d)]),c,u]))}});export{f as __pageData,k as default}; +import{d as s}from"./chunks/git.data.pqelWCHe.js";import{u as i,c as r,j as e,a as t,k as a,o}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"The IndieWeb/Signature Blocks",-1),d=["innerHTML"],c=e("hr",null,null,-1),u=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),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"}'),p={name:"garden/the-indieweb/signature-blocks/index.md"},k=Object.assign(p,{setup(h){const n=i();return(_,g)=>(o(),r("div",null,[l,e("p",null,[t("14 words, ~0 minute read. "),e("span",{innerHTML:a(s)[`site/${a(n).page.value.relativePath}`]},null,8,d)]),c,u]))}});export{f as __pageData,k as default}; diff --git a/assets/garden_the-small-web_index.md.7Rrvcn6K.js b/assets/garden_the-small-web_index.md.D9cvWfOu.js similarity index 99% rename from assets/garden_the-small-web_index.md.7Rrvcn6K.js rename to assets/garden_the-small-web_index.md.D9cvWfOu.js index f6fd4b12..1a24a86c 100644 --- a/assets/garden_the-small-web_index.md.7Rrvcn6K.js +++ b/assets/garden_the-small-web_index.md.D9cvWfOu.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as l,c as s,j as e,a as i,k as a,a5 as o,o as n}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"The Small Web",-1),d=["innerHTML"],b=o('

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

The web has lost its soul

You should check out the indie web

',35),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"}'),c={name:"garden/the-small-web/index.md"},k=Object.assign(c,{setup(u){const t=l();return(p,g)=>(n(),s("div",null,[h,e("p",null,[i("437 words, ~2 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,d)]),b]))}});export{w as __pageData,k as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as l,c as s,j as e,a as i,k as a,a5 as o,o as n}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"The Small Web",-1),d=["innerHTML"],b=o('

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

The web has lost its soul

You should check out the indie web

',35),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"}'),c={name:"garden/the-small-web/index.md"},k=Object.assign(c,{setup(u){const t=l();return(p,g)=>(n(),s("div",null,[h,e("p",null,[i("437 words, ~2 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,d)]),b]))}});export{w as __pageData,k as default}; diff --git a/assets/garden_the-small-web_index.md.7Rrvcn6K.lean.js b/assets/garden_the-small-web_index.md.D9cvWfOu.lean.js similarity index 92% rename from assets/garden_the-small-web_index.md.7Rrvcn6K.lean.js rename to assets/garden_the-small-web_index.md.D9cvWfOu.lean.js index 4751404e..635f553d 100644 --- a/assets/garden_the-small-web_index.md.7Rrvcn6K.lean.js +++ b/assets/garden_the-small-web_index.md.D9cvWfOu.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as l,c as s,j as e,a as i,k as a,a5 as o,o as n}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"The Small Web",-1),d=["innerHTML"],b=o("",35),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"}'),c={name:"garden/the-small-web/index.md"},k=Object.assign(c,{setup(u){const t=l();return(p,g)=>(n(),s("div",null,[h,e("p",null,[i("437 words, ~2 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,d)]),b]))}});export{w as __pageData,k as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as l,c as s,j as e,a as i,k as a,a5 as o,o as n}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"The Small Web",-1),d=["innerHTML"],b=o("",35),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"}'),c={name:"garden/the-small-web/index.md"},k=Object.assign(c,{setup(u){const t=l();return(p,g)=>(n(),s("div",null,[h,e("p",null,[i("437 words, ~2 minute read. "),e("span",{innerHTML:a(r)[`site/${a(t).page.value.relativePath}`]},null,8,d)]),b]))}});export{w as __pageData,k as default}; diff --git a/assets/garden_this-knowledge-hub_index.md.Chvg19jP.js b/assets/garden_this-knowledge-hub_index.md.BLVYkkb3.js similarity index 97% rename from assets/garden_this-knowledge-hub_index.md.Chvg19jP.js rename to assets/garden_this-knowledge-hub_index.md.BLVYkkb3.js index b7deff2d..e1518c4c 100644 --- a/assets/garden_this-knowledge-hub_index.md.Chvg19jP.js +++ b/assets/garden_this-knowledge-hub_index.md.BLVYkkb3.js @@ -1 +1 @@ -import{d as s}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as i,j as e,a as r,k as a,a5 as l,o}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"This Knowledge Hub",-1),h=["innerHTML"],g=l('

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

I want to utilize the strategies described in Andy's working notes to help improve my digital garden

Suggested pages:

',11),b=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"}'),p={name:"garden/this-knowledge-hub/index.md"},y=Object.assign(p,{setup(u){const t=n();return(c,m)=>(o(),i("div",null,[d,e("p",null,[r("135 words, ~1 minute read. "),e("span",{innerHTML:a(s)[`site/${a(t).page.value.relativePath}`]},null,8,h)]),g]))}});export{b as __pageData,y as default}; +import{d as s}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as i,j as e,a as r,k as a,a5 as l,o}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"This Knowledge Hub",-1),h=["innerHTML"],g=l('

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

I want to utilize the strategies described in Andy's working notes to help improve my digital garden

Suggested pages:

',11),b=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"}'),p={name:"garden/this-knowledge-hub/index.md"},y=Object.assign(p,{setup(u){const t=n();return(c,m)=>(o(),i("div",null,[d,e("p",null,[r("135 words, ~1 minute read. "),e("span",{innerHTML:a(s)[`site/${a(t).page.value.relativePath}`]},null,8,h)]),g]))}});export{b as __pageData,y as default}; diff --git a/assets/garden_this-knowledge-hub_index.md.Chvg19jP.lean.js b/assets/garden_this-knowledge-hub_index.md.BLVYkkb3.lean.js similarity index 92% rename from assets/garden_this-knowledge-hub_index.md.Chvg19jP.lean.js rename to assets/garden_this-knowledge-hub_index.md.BLVYkkb3.lean.js index 714455f5..53f074bc 100644 --- a/assets/garden_this-knowledge-hub_index.md.Chvg19jP.lean.js +++ b/assets/garden_this-knowledge-hub_index.md.BLVYkkb3.lean.js @@ -1 +1 @@ -import{d as s}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as i,j as e,a as r,k as a,a5 as l,o}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"This Knowledge Hub",-1),h=["innerHTML"],g=l("",11),b=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"}'),p={name:"garden/this-knowledge-hub/index.md"},y=Object.assign(p,{setup(u){const t=n();return(c,m)=>(o(),i("div",null,[d,e("p",null,[r("135 words, ~1 minute read. "),e("span",{innerHTML:a(s)[`site/${a(t).page.value.relativePath}`]},null,8,h)]),g]))}});export{b as __pageData,y as default}; +import{d as s}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as i,j as e,a as r,k as a,a5 as l,o}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"This Knowledge Hub",-1),h=["innerHTML"],g=l("",11),b=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"}'),p={name:"garden/this-knowledge-hub/index.md"},y=Object.assign(p,{setup(u){const t=n();return(c,m)=>(o(),i("div",null,[d,e("p",null,[r("135 words, ~1 minute read. "),e("span",{innerHTML:a(s)[`site/${a(t).page.value.relativePath}`]},null,8,h)]),g]))}});export{b as __pageData,y as default}; diff --git a/assets/garden_v-ecs_index.md._CuDqvCK.js b/assets/garden_v-ecs_index.md.CYqFpmde.js similarity index 97% rename from assets/garden_v-ecs_index.md._CuDqvCK.js rename to assets/garden_v-ecs_index.md.CYqFpmde.js index c260a286..c5ee52fb 100644 --- a/assets/garden_v-ecs_index.md._CuDqvCK.js +++ b/assets/garden_v-ecs_index.md.CYqFpmde.js @@ -1 +1 @@ -import{u as s,c as o,j as e,a as n,k as a,a5 as r,o as i,am as l,an as d,ao as c}from"./chunks/framework.BIC8H_hJ.js";import{d as p}from"./chunks/git.data.BUKN53Ta.js";const m=e("h1",{class:"p-name"},"V-ecs",-1),h=["innerHTML"],g=r('

Tags: My Projects

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.

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".

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

',10),T=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"}'),u={name:"garden/v-ecs/index.md"},b=Object.assign(u,{setup(_){const t=s();return(f,v)=>(i(),o("div",null,[m,e("p",null,[n("209 words, ~1 minute read. "),e("span",{innerHTML:a(p)[`site/${a(t).page.value.relativePath}`]},null,8,h)]),g]))}});export{T as __pageData,b as default}; +import{u as s,c as o,j as e,a as n,k as a,a5 as r,o as i,am as l,an as d,ao as c}from"./chunks/framework.BIC8H_hJ.js";import{d as p}from"./chunks/git.data.pqelWCHe.js";const m=e("h1",{class:"p-name"},"V-ecs",-1),h=["innerHTML"],g=r('

Tags: My Projects

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.

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".

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

',10),T=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"}'),u={name:"garden/v-ecs/index.md"},b=Object.assign(u,{setup(_){const t=s();return(f,v)=>(i(),o("div",null,[m,e("p",null,[n("209 words, ~1 minute read. "),e("span",{innerHTML:a(p)[`site/${a(t).page.value.relativePath}`]},null,8,h)]),g]))}});export{T as __pageData,b as default}; diff --git a/assets/garden_v-ecs_index.md._CuDqvCK.lean.js b/assets/garden_v-ecs_index.md.CYqFpmde.lean.js similarity index 91% rename from assets/garden_v-ecs_index.md._CuDqvCK.lean.js rename to assets/garden_v-ecs_index.md.CYqFpmde.lean.js index 8e6ffd69..42e6139d 100644 --- a/assets/garden_v-ecs_index.md._CuDqvCK.lean.js +++ b/assets/garden_v-ecs_index.md.CYqFpmde.lean.js @@ -1 +1 @@ -import{u as s,c as o,j as e,a as n,k as a,a5 as r,o as i,am as l,an as d,ao as c}from"./chunks/framework.BIC8H_hJ.js";import{d as p}from"./chunks/git.data.BUKN53Ta.js";const m=e("h1",{class:"p-name"},"V-ecs",-1),h=["innerHTML"],g=r("",10),T=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"}'),u={name:"garden/v-ecs/index.md"},b=Object.assign(u,{setup(_){const t=s();return(f,v)=>(i(),o("div",null,[m,e("p",null,[n("209 words, ~1 minute read. "),e("span",{innerHTML:a(p)[`site/${a(t).page.value.relativePath}`]},null,8,h)]),g]))}});export{T as __pageData,b as default}; +import{u as s,c as o,j as e,a as n,k as a,a5 as r,o as i,am as l,an as d,ao as c}from"./chunks/framework.BIC8H_hJ.js";import{d as p}from"./chunks/git.data.pqelWCHe.js";const m=e("h1",{class:"p-name"},"V-ecs",-1),h=["innerHTML"],g=r("",10),T=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"}'),u={name:"garden/v-ecs/index.md"},b=Object.assign(u,{setup(_){const t=s();return(f,v)=>(i(),o("div",null,[m,e("p",null,[n("209 words, ~1 minute read. "),e("span",{innerHTML:a(p)[`site/${a(t).page.value.relativePath}`]},null,8,h)]),g]))}});export{T as __pageData,b as default}; diff --git a/assets/garden_video-game-monetization_index.md.COJLTxgq.js b/assets/garden_video-game-monetization_index.md.Cxek416m.js similarity index 97% rename from assets/garden_video-game-monetization_index.md.COJLTxgq.js rename to assets/garden_video-game-monetization_index.md.Cxek416m.js index d453a9f9..f7fe29cd 100644 --- a/assets/garden_video-game-monetization_index.md.COJLTxgq.js +++ b/assets/garden_video-game-monetization_index.md.Cxek416m.js @@ -1 +1 @@ -import{d as i}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as n,j as e,a as r,k as a,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Video Game Monetization",-1),m=["innerHTML"],h=s('

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),b=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"}'),p={name:"garden/video-game-monetization/index.md"},A=Object.assign(p,{setup(c){const t=o();return(u,g)=>(l(),n("div",null,[d,e("p",null,[r("123 words, ~1 minute read. "),e("span",{innerHTML:a(i)[`site/${a(t).page.value.relativePath}`]},null,8,m)]),h]))}});export{b as __pageData,A as default}; +import{d as i}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as n,j as e,a as r,k as a,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Video Game Monetization",-1),m=["innerHTML"],h=s('

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),b=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"}'),p={name:"garden/video-game-monetization/index.md"},A=Object.assign(p,{setup(c){const t=o();return(u,g)=>(l(),n("div",null,[d,e("p",null,[r("123 words, ~1 minute read. "),e("span",{innerHTML:a(i)[`site/${a(t).page.value.relativePath}`]},null,8,m)]),h]))}});export{b as __pageData,A as default}; diff --git a/assets/garden_video-game-monetization_index.md.COJLTxgq.lean.js b/assets/garden_video-game-monetization_index.md.Cxek416m.lean.js similarity index 92% rename from assets/garden_video-game-monetization_index.md.COJLTxgq.lean.js rename to assets/garden_video-game-monetization_index.md.Cxek416m.lean.js index 02c3a9bd..ee3972e6 100644 --- a/assets/garden_video-game-monetization_index.md.COJLTxgq.lean.js +++ b/assets/garden_video-game-monetization_index.md.Cxek416m.lean.js @@ -1 +1 @@ -import{d as i}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as n,j as e,a as r,k as a,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Video Game Monetization",-1),m=["innerHTML"],h=s("",17),b=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"}'),p={name:"garden/video-game-monetization/index.md"},A=Object.assign(p,{setup(c){const t=o();return(u,g)=>(l(),n("div",null,[d,e("p",null,[r("123 words, ~1 minute read. "),e("span",{innerHTML:a(i)[`site/${a(t).page.value.relativePath}`]},null,8,m)]),h]))}});export{b as __pageData,A as default}; +import{d as i}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as n,j as e,a as r,k as a,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Video Game Monetization",-1),m=["innerHTML"],h=s("",17),b=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"}'),p={name:"garden/video-game-monetization/index.md"},A=Object.assign(p,{setup(c){const t=o();return(u,g)=>(l(),n("div",null,[d,e("p",null,[r("123 words, ~1 minute read. "),e("span",{innerHTML:a(i)[`site/${a(t).page.value.relativePath}`]},null,8,m)]),h]))}});export{b as __pageData,A as default}; diff --git a/assets/garden_vitepress_index.md.CMbASq96.js b/assets/garden_vitepress_index.md.CDF2emtN.js similarity index 94% rename from assets/garden_vitepress_index.md.CMbASq96.js rename to assets/garden_vitepress_index.md.CDF2emtN.js index 3d8cfdb9..34a08496 100644 --- a/assets/garden_vitepress_index.md.CMbASq96.js +++ b/assets/garden_vitepress_index.md.CDF2emtN.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as i,j as e,a as t,k as s,o}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Vitepress",-1),d=["innerHTML"],p=e("hr",null,null,-1),c=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/this-knowledge-hub/"},"This Knowledge Hub")])],-1),u=e("p",null,[e("a",{href:"https://vitepress.dev",target:"_blank",rel:"noreferrer"},"Vitepress"),t(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),t(" static site generator")],-1),b=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"}'),_={name:"garden/vitepress/index.md"},x=Object.assign(_,{setup(h){const a=n();return(f,g)=>(o(),i("div",null,[l,e("p",null,[t("4 words, ~0 minute read. "),e("span",{innerHTML:s(r)[`site/${s(a).page.value.relativePath}`]},null,8,d)]),p,c,u]))}});export{b as __pageData,x as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as i,j as e,a as t,k as s,o}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Vitepress",-1),d=["innerHTML"],p=e("hr",null,null,-1),c=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/this-knowledge-hub/"},"This Knowledge Hub")])],-1),u=e("p",null,[e("a",{href:"https://vitepress.dev",target:"_blank",rel:"noreferrer"},"Vitepress"),t(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),t(" static site generator")],-1),b=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"}'),_={name:"garden/vitepress/index.md"},x=Object.assign(_,{setup(h){const a=n();return(f,g)=>(o(),i("div",null,[l,e("p",null,[t("4 words, ~0 minute read. "),e("span",{innerHTML:s(r)[`site/${s(a).page.value.relativePath}`]},null,8,d)]),p,c,u]))}});export{b as __pageData,x as default}; diff --git a/assets/garden_vitepress_index.md.CMbASq96.lean.js b/assets/garden_vitepress_index.md.CDF2emtN.lean.js similarity index 94% rename from assets/garden_vitepress_index.md.CMbASq96.lean.js rename to assets/garden_vitepress_index.md.CDF2emtN.lean.js index 3d8cfdb9..34a08496 100644 --- a/assets/garden_vitepress_index.md.CMbASq96.lean.js +++ b/assets/garden_vitepress_index.md.CDF2emtN.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as i,j as e,a as t,k as s,o}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Vitepress",-1),d=["innerHTML"],p=e("hr",null,null,-1),c=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/this-knowledge-hub/"},"This Knowledge Hub")])],-1),u=e("p",null,[e("a",{href:"https://vitepress.dev",target:"_blank",rel:"noreferrer"},"Vitepress"),t(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),t(" static site generator")],-1),b=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"}'),_={name:"garden/vitepress/index.md"},x=Object.assign(_,{setup(h){const a=n();return(f,g)=>(o(),i("div",null,[l,e("p",null,[t("4 words, ~0 minute read. "),e("span",{innerHTML:s(r)[`site/${s(a).page.value.relativePath}`]},null,8,d)]),p,c,u]))}});export{b as __pageData,x as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as i,j as e,a as t,k as s,o}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Vitepress",-1),d=["innerHTML"],p=e("hr",null,null,-1),c=e("blockquote",null,[e("p",null,[t("Referenced by: "),e("a",{href:"/garden/this-knowledge-hub/"},"This Knowledge Hub")])],-1),u=e("p",null,[e("a",{href:"https://vitepress.dev",target:"_blank",rel:"noreferrer"},"Vitepress"),t(" is an "),e("a",{href:"/garden/open-source/"},"Open Source"),t(" static site generator")],-1),b=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"}'),_={name:"garden/vitepress/index.md"},x=Object.assign(_,{setup(h){const a=n();return(f,g)=>(o(),i("div",null,[l,e("p",null,[t("4 words, ~0 minute read. "),e("span",{innerHTML:s(r)[`site/${s(a).page.value.relativePath}`]},null,8,d)]),p,c,u]))}});export{b as __pageData,x as default}; diff --git a/assets/garden_wanderstop_index.md.CPbtJHdi.js b/assets/garden_wanderstop_index.md.B4wnUY7H.js similarity index 94% rename from assets/garden_wanderstop_index.md.CPbtJHdi.js rename to assets/garden_wanderstop_index.md.B4wnUY7H.js index ec6d0498..a6e32bfc 100644 --- a/assets/garden_wanderstop_index.md.CPbtJHdi.js +++ b/assets/garden_wanderstop_index.md.B4wnUY7H.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as o,j as e,a,k as t,o as d}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Wanderstop",-1),i=["innerHTML"],p=e("hr",null,null,-1),c=e("blockquote",null,[e("p",null,[a("Tags: "),e("a",{href:"/garden/davey-wreden/"},"Davey Wreden")])],-1),u=e("p",null,[e("a",{href:"https://www.wanderstopgame.com/",target:"_blank",rel:"noreferrer"},"Wanderstop"),a(" is the first game by "),e("a",{href:"/garden/ivy-road/"},"Ivy Road"),a(". It's a narrative focused cozy game")],-1),w=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"}'),_={name:"garden/wanderstop/index.md"},x=Object.assign(_,{setup(h){const n=s();return(m,f)=>(d(),o("div",null,[l,e("p",null,[a("8 words, ~0 minute read. "),e("span",{innerHTML:t(r)[`site/${t(n).page.value.relativePath}`]},null,8,i)]),p,c,u]))}});export{w as __pageData,x as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as o,j as e,a,k as t,o as d}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Wanderstop",-1),i=["innerHTML"],p=e("hr",null,null,-1),c=e("blockquote",null,[e("p",null,[a("Tags: "),e("a",{href:"/garden/davey-wreden/"},"Davey Wreden")])],-1),u=e("p",null,[e("a",{href:"https://www.wanderstopgame.com/",target:"_blank",rel:"noreferrer"},"Wanderstop"),a(" is the first game by "),e("a",{href:"/garden/ivy-road/"},"Ivy Road"),a(". It's a narrative focused cozy game")],-1),w=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"}'),_={name:"garden/wanderstop/index.md"},x=Object.assign(_,{setup(h){const n=s();return(m,f)=>(d(),o("div",null,[l,e("p",null,[a("8 words, ~0 minute read. "),e("span",{innerHTML:t(r)[`site/${t(n).page.value.relativePath}`]},null,8,i)]),p,c,u]))}});export{w as __pageData,x as default}; diff --git a/assets/garden_wanderstop_index.md.CPbtJHdi.lean.js b/assets/garden_wanderstop_index.md.B4wnUY7H.lean.js similarity index 94% rename from assets/garden_wanderstop_index.md.CPbtJHdi.lean.js rename to assets/garden_wanderstop_index.md.B4wnUY7H.lean.js index ec6d0498..a6e32bfc 100644 --- a/assets/garden_wanderstop_index.md.CPbtJHdi.lean.js +++ b/assets/garden_wanderstop_index.md.B4wnUY7H.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as s,c as o,j as e,a,k as t,o as d}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Wanderstop",-1),i=["innerHTML"],p=e("hr",null,null,-1),c=e("blockquote",null,[e("p",null,[a("Tags: "),e("a",{href:"/garden/davey-wreden/"},"Davey Wreden")])],-1),u=e("p",null,[e("a",{href:"https://www.wanderstopgame.com/",target:"_blank",rel:"noreferrer"},"Wanderstop"),a(" is the first game by "),e("a",{href:"/garden/ivy-road/"},"Ivy Road"),a(". It's a narrative focused cozy game")],-1),w=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"}'),_={name:"garden/wanderstop/index.md"},x=Object.assign(_,{setup(h){const n=s();return(m,f)=>(d(),o("div",null,[l,e("p",null,[a("8 words, ~0 minute read. "),e("span",{innerHTML:t(r)[`site/${t(n).page.value.relativePath}`]},null,8,i)]),p,c,u]))}});export{w as __pageData,x as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as s,c as o,j as e,a,k as t,o as d}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Wanderstop",-1),i=["innerHTML"],p=e("hr",null,null,-1),c=e("blockquote",null,[e("p",null,[a("Tags: "),e("a",{href:"/garden/davey-wreden/"},"Davey Wreden")])],-1),u=e("p",null,[e("a",{href:"https://www.wanderstopgame.com/",target:"_blank",rel:"noreferrer"},"Wanderstop"),a(" is the first game by "),e("a",{href:"/garden/ivy-road/"},"Ivy Road"),a(". It's a narrative focused cozy game")],-1),w=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"}'),_={name:"garden/wanderstop/index.md"},x=Object.assign(_,{setup(h){const n=s();return(m,f)=>(d(),o("div",null,[l,e("p",null,[a("8 words, ~0 minute read. "),e("span",{innerHTML:t(r)[`site/${t(n).page.value.relativePath}`]},null,8,i)]),p,c,u]))}});export{w as __pageData,x as default}; diff --git a/assets/garden_webrings_index.md.YTbtPCL5.js b/assets/garden_webrings_index.md.BHMjqXQ4.js similarity index 96% rename from assets/garden_webrings_index.md.YTbtPCL5.js rename to assets/garden_webrings_index.md.BHMjqXQ4.js index 84d6bad5..ab47a428 100644 --- a/assets/garden_webrings_index.md.YTbtPCL5.js +++ b/assets/garden_webrings_index.md.BHMjqXQ4.js @@ -1 +1 @@ -import{d as i}from"./chunks/git.data.BUKN53Ta.js";import{u as l,c as r,j as e,a as o,k as a,a5 as s,o as n}from"./chunks/framework.BIC8H_hJ.js";const m=e("h1",{class:"p-name"},"Webrings",-1),c=["innerHTML"],u=s('

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),f=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"}'),d={name:"garden/webrings/index.md"},w=Object.assign(d,{setup(h){const t=l();return(g,p)=>(n(),r("div",null,[m,e("p",null,[o("139 words, ~1 minute read. "),e("span",{innerHTML:a(i)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),u]))}});export{f as __pageData,w as default}; +import{d as i}from"./chunks/git.data.pqelWCHe.js";import{u as l,c as r,j as e,a as o,k as a,a5 as s,o as n}from"./chunks/framework.BIC8H_hJ.js";const m=e("h1",{class:"p-name"},"Webrings",-1),c=["innerHTML"],u=s('

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),f=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"}'),d={name:"garden/webrings/index.md"},w=Object.assign(d,{setup(h){const t=l();return(g,p)=>(n(),r("div",null,[m,e("p",null,[o("139 words, ~1 minute read. "),e("span",{innerHTML:a(i)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),u]))}});export{f as __pageData,w as default}; diff --git a/assets/garden_webrings_index.md.YTbtPCL5.lean.js b/assets/garden_webrings_index.md.BHMjqXQ4.lean.js similarity index 91% rename from assets/garden_webrings_index.md.YTbtPCL5.lean.js rename to assets/garden_webrings_index.md.BHMjqXQ4.lean.js index 1076af06..fd4d243a 100644 --- a/assets/garden_webrings_index.md.YTbtPCL5.lean.js +++ b/assets/garden_webrings_index.md.BHMjqXQ4.lean.js @@ -1 +1 @@ -import{d as i}from"./chunks/git.data.BUKN53Ta.js";import{u as l,c as r,j as e,a as o,k as a,a5 as s,o as n}from"./chunks/framework.BIC8H_hJ.js";const m=e("h1",{class:"p-name"},"Webrings",-1),c=["innerHTML"],u=s("",6),f=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"}'),d={name:"garden/webrings/index.md"},w=Object.assign(d,{setup(h){const t=l();return(g,p)=>(n(),r("div",null,[m,e("p",null,[o("139 words, ~1 minute read. "),e("span",{innerHTML:a(i)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),u]))}});export{f as __pageData,w as default}; +import{d as i}from"./chunks/git.data.pqelWCHe.js";import{u as l,c as r,j as e,a as o,k as a,a5 as s,o as n}from"./chunks/framework.BIC8H_hJ.js";const m=e("h1",{class:"p-name"},"Webrings",-1),c=["innerHTML"],u=s("",6),f=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"}'),d={name:"garden/webrings/index.md"},w=Object.assign(d,{setup(h){const t=l();return(g,p)=>(n(),r("div",null,[m,e("p",null,[o("139 words, ~1 minute read. "),e("span",{innerHTML:a(i)[`site/${a(t).page.value.relativePath}`]},null,8,c)]),u]))}});export{f as __pageData,w as default}; diff --git a/assets/garden_weird_index.md.BDMicidw.js b/assets/garden_weird_index.md.D2B2Yk0i.js similarity index 97% rename from assets/garden_weird_index.md.BDMicidw.js rename to assets/garden_weird_index.md.D2B2Yk0i.js index b183e77e..481531fd 100644 --- a/assets/garden_weird_index.md.BDMicidw.js +++ b/assets/garden_weird_index.md.D2B2Yk0i.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as i,c as n,j as e,a as s,k as a,a5 as o,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Weird",-1),c=["innerHTML"],h=o('

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),v=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"}'),p={name:"garden/weird/index.md"},b=Object.assign(p,{setup(u){const r=i();return(f,m)=>(l(),n("div",null,[d,e("p",null,[s("114 words, ~1 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),h]))}});export{v as __pageData,b as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as i,c as n,j as e,a as s,k as a,a5 as o,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Weird",-1),c=["innerHTML"],h=o('

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),v=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"}'),p={name:"garden/weird/index.md"},b=Object.assign(p,{setup(u){const r=i();return(f,m)=>(l(),n("div",null,[d,e("p",null,[s("114 words, ~1 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),h]))}});export{v as __pageData,b as default}; diff --git a/assets/garden_weird_index.md.BDMicidw.lean.js b/assets/garden_weird_index.md.D2B2Yk0i.lean.js similarity index 91% rename from assets/garden_weird_index.md.BDMicidw.lean.js rename to assets/garden_weird_index.md.D2B2Yk0i.lean.js index 0ff6e172..17bb3e61 100644 --- a/assets/garden_weird_index.md.BDMicidw.lean.js +++ b/assets/garden_weird_index.md.D2B2Yk0i.lean.js @@ -1 +1 @@ -import{d as t}from"./chunks/git.data.BUKN53Ta.js";import{u as i,c as n,j as e,a as s,k as a,a5 as o,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Weird",-1),c=["innerHTML"],h=o("",7),v=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"}'),p={name:"garden/weird/index.md"},b=Object.assign(p,{setup(u){const r=i();return(f,m)=>(l(),n("div",null,[d,e("p",null,[s("114 words, ~1 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),h]))}});export{v as __pageData,b as default}; +import{d as t}from"./chunks/git.data.pqelWCHe.js";import{u as i,c as n,j as e,a as s,k as a,a5 as o,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Weird",-1),c=["innerHTML"],h=o("",7),v=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"}'),p={name:"garden/weird/index.md"},b=Object.assign(p,{setup(u){const r=i();return(f,m)=>(l(),n("div",null,[d,e("p",null,[s("114 words, ~1 minute read. "),e("span",{innerHTML:a(t)[`site/${a(r).page.value.relativePath}`]},null,8,c)]),h]))}});export{v as __pageData,b as default}; diff --git a/assets/guide-to-incrementals_design_criticism_index.md.B54w0CP9.js b/assets/guide-to-incrementals_design_criticism_index.md.BcdAQ_MC.js similarity index 98% rename from assets/guide-to-incrementals_design_criticism_index.md.B54w0CP9.js rename to assets/guide-to-incrementals_design_criticism_index.md.BcdAQ_MC.js index a7009032..667d90c9 100644 --- a/assets/guide-to-incrementals_design_criticism_index.md.B54w0CP9.js +++ b/assets/guide-to-incrementals_design_criticism_index.md.BcdAQ_MC.js @@ -1 +1 @@ -import{d as i}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as o,j as e,a as s,k as t,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Guide to Incrementals/Navigating Criticism",-1),d=["innerHTML"],u=r('

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),v=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"}'),m={name:"guide-to-incrementals/design/criticism/index.md"},b=Object.assign(m,{setup(h){const a=n();return(g,p)=>(l(),o("div",null,[c,e("p",null,[s("747 words, ~4 minute read. "),e("span",{innerHTML:t(i)[`site/${t(a).page.value.relativePath}`]},null,8,d)]),u]))}});export{v as __pageData,b as default}; +import{d as i}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as o,j as e,a as s,k as t,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Guide to Incrementals/Navigating Criticism",-1),d=["innerHTML"],u=r('

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),v=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"}'),m={name:"guide-to-incrementals/design/criticism/index.md"},b=Object.assign(m,{setup(h){const a=n();return(g,p)=>(l(),o("div",null,[c,e("p",null,[s("747 words, ~4 minute read. "),e("span",{innerHTML:t(i)[`site/${t(a).page.value.relativePath}`]},null,8,d)]),u]))}});export{v as __pageData,b as default}; diff --git a/assets/guide-to-incrementals_design_criticism_index.md.B54w0CP9.lean.js b/assets/guide-to-incrementals_design_criticism_index.md.BcdAQ_MC.lean.js similarity index 93% rename from assets/guide-to-incrementals_design_criticism_index.md.B54w0CP9.lean.js rename to assets/guide-to-incrementals_design_criticism_index.md.BcdAQ_MC.lean.js index be77746c..c4388f4c 100644 --- a/assets/guide-to-incrementals_design_criticism_index.md.B54w0CP9.lean.js +++ b/assets/guide-to-incrementals_design_criticism_index.md.BcdAQ_MC.lean.js @@ -1 +1 @@ -import{d as i}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as o,j as e,a as s,k as t,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Guide to Incrementals/Navigating Criticism",-1),d=["innerHTML"],u=r("",11),v=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"}'),m={name:"guide-to-incrementals/design/criticism/index.md"},b=Object.assign(m,{setup(h){const a=n();return(g,p)=>(l(),o("div",null,[c,e("p",null,[s("747 words, ~4 minute read. "),e("span",{innerHTML:t(i)[`site/${t(a).page.value.relativePath}`]},null,8,d)]),u]))}});export{v as __pageData,b as default}; +import{d as i}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as o,j as e,a as s,k as t,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"Guide to Incrementals/Navigating Criticism",-1),d=["innerHTML"],u=r("",11),v=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"}'),m={name:"guide-to-incrementals/design/criticism/index.md"},b=Object.assign(m,{setup(h){const a=n();return(g,p)=>(l(),o("div",null,[c,e("p",null,[s("747 words, ~4 minute read. "),e("span",{innerHTML:t(i)[`site/${t(a).page.value.relativePath}`]},null,8,d)]),u]))}});export{v as __pageData,b as default}; diff --git a/assets/guide-to-incrementals_index.md.DJ4GL0o_.js b/assets/guide-to-incrementals_index.md.Dfajo0A4.js similarity index 98% rename from assets/guide-to-incrementals_index.md.DJ4GL0o_.js rename to assets/guide-to-incrementals_index.md.Dfajo0A4.js index 90ca55be..bb24e0e5 100644 --- a/assets/guide-to-incrementals_index.md.DJ4GL0o_.js +++ b/assets/guide-to-incrementals_index.md.Dfajo0A4.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as i,c as o,j as e,a as s,k as a,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Guide to Incrementals",-1),m=["innerHTML"],c=r('

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),v=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"}'),h={name:"guide-to-incrementals/index.md"},y=Object.assign(h,{setup(g){const t=i();return(u,p)=>(l(),o("div",null,[d,e("p",null,[s("251 words, ~1 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,m)]),c]))}});export{v as __pageData,y as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as i,c as o,j as e,a as s,k as a,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Guide to Incrementals",-1),m=["innerHTML"],c=r('

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),v=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"}'),h={name:"guide-to-incrementals/index.md"},y=Object.assign(h,{setup(g){const t=i();return(u,p)=>(l(),o("div",null,[d,e("p",null,[s("251 words, ~1 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,m)]),c]))}});export{v as __pageData,y as default}; diff --git a/assets/guide-to-incrementals_index.md.DJ4GL0o_.lean.js b/assets/guide-to-incrementals_index.md.Dfajo0A4.lean.js similarity index 92% rename from assets/guide-to-incrementals_index.md.DJ4GL0o_.lean.js rename to assets/guide-to-incrementals_index.md.Dfajo0A4.lean.js index acacf56c..c2ddd784 100644 --- a/assets/guide-to-incrementals_index.md.DJ4GL0o_.lean.js +++ b/assets/guide-to-incrementals_index.md.Dfajo0A4.lean.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as i,c as o,j as e,a as s,k as a,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Guide to Incrementals",-1),m=["innerHTML"],c=r("",11),v=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"}'),h={name:"guide-to-incrementals/index.md"},y=Object.assign(h,{setup(g){const t=i();return(u,p)=>(l(),o("div",null,[d,e("p",null,[s("251 words, ~1 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,m)]),c]))}});export{v as __pageData,y as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as i,c as o,j as e,a as s,k as a,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const d=e("h1",{class:"p-name"},"Guide to Incrementals",-1),m=["innerHTML"],c=r("",11),v=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"}'),h={name:"guide-to-incrementals/index.md"},y=Object.assign(h,{setup(g){const t=i();return(u,p)=>(l(),o("div",null,[d,e("p",null,[s("251 words, ~1 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,m)]),c]))}});export{v as __pageData,y as default}; diff --git a/assets/guide-to-incrementals_ludology_appeal-developers_index.md.DoI27elo.js b/assets/guide-to-incrementals_ludology_appeal-developers_index.md.BEo9sXWJ.js similarity index 98% rename from assets/guide-to-incrementals_ludology_appeal-developers_index.md.DoI27elo.js rename to assets/guide-to-incrementals_ludology_appeal-developers_index.md.BEo9sXWJ.js index d2f53554..95173071 100644 --- a/assets/guide-to-incrementals_ludology_appeal-developers_index.md.DoI27elo.js +++ b/assets/guide-to-incrementals_ludology_appeal-developers_index.md.BEo9sXWJ.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as i,j as e,a as r,k as a,a5 as l,o as s}from"./chunks/framework.BIC8H_hJ.js";const m=e("h1",{class:"p-name"},"Guide to Incrementals/Appeal to Developers",-1),d=["innerHTML"],c=l('

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),b=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"}'),p={name:"guide-to-incrementals/ludology/appeal-developers/index.md"},v=Object.assign(p,{setup(h){const t=o();return(u,g)=>(s(),i("div",null,[m,e("p",null,[r("636 words, ~3 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,d)]),c]))}});export{b as __pageData,v as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as i,j as e,a as r,k as a,a5 as l,o as s}from"./chunks/framework.BIC8H_hJ.js";const m=e("h1",{class:"p-name"},"Guide to Incrementals/Appeal to Developers",-1),d=["innerHTML"],c=l('

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),b=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"}'),p={name:"guide-to-incrementals/ludology/appeal-developers/index.md"},v=Object.assign(p,{setup(h){const t=o();return(u,g)=>(s(),i("div",null,[m,e("p",null,[r("636 words, ~3 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,d)]),c]))}});export{b as __pageData,v as default}; diff --git a/assets/guide-to-incrementals_ludology_appeal-developers_index.md.DoI27elo.lean.js b/assets/guide-to-incrementals_ludology_appeal-developers_index.md.BEo9sXWJ.lean.js similarity index 93% rename from assets/guide-to-incrementals_ludology_appeal-developers_index.md.DoI27elo.lean.js rename to assets/guide-to-incrementals_ludology_appeal-developers_index.md.BEo9sXWJ.lean.js index ad182cf5..61eb9f21 100644 --- a/assets/guide-to-incrementals_ludology_appeal-developers_index.md.DoI27elo.lean.js +++ b/assets/guide-to-incrementals_ludology_appeal-developers_index.md.BEo9sXWJ.lean.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as i,j as e,a as r,k as a,a5 as l,o as s}from"./chunks/framework.BIC8H_hJ.js";const m=e("h1",{class:"p-name"},"Guide to Incrementals/Appeal to Developers",-1),d=["innerHTML"],c=l("",13),b=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"}'),p={name:"guide-to-incrementals/ludology/appeal-developers/index.md"},v=Object.assign(p,{setup(h){const t=o();return(u,g)=>(s(),i("div",null,[m,e("p",null,[r("636 words, ~3 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,d)]),c]))}});export{b as __pageData,v as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as i,j as e,a as r,k as a,a5 as l,o as s}from"./chunks/framework.BIC8H_hJ.js";const m=e("h1",{class:"p-name"},"Guide to Incrementals/Appeal to Developers",-1),d=["innerHTML"],c=l("",13),b=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"}'),p={name:"guide-to-incrementals/ludology/appeal-developers/index.md"},v=Object.assign(p,{setup(h){const t=o();return(u,g)=>(s(),i("div",null,[m,e("p",null,[r("636 words, ~3 minute read. "),e("span",{innerHTML:a(n)[`site/${a(t).page.value.relativePath}`]},null,8,d)]),c]))}});export{b as __pageData,v as default}; diff --git a/assets/guide-to-incrementals_ludology_appeal-gamers_index.md.CESZSCKq.js b/assets/guide-to-incrementals_ludology_appeal-gamers_index.md.ChZkyZEi.js similarity index 99% rename from assets/guide-to-incrementals_ludology_appeal-gamers_index.md.CESZSCKq.js rename to assets/guide-to-incrementals_ludology_appeal-gamers_index.md.ChZkyZEi.js index 3e6bc32b..f8015424 100644 --- a/assets/guide-to-incrementals_ludology_appeal-gamers_index.md.CESZSCKq.js +++ b/assets/guide-to-incrementals_ludology_appeal-gamers_index.md.ChZkyZEi.js @@ -1 +1 @@ -import{d as i}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as o,j as e,a as s,k as t,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"Guide to Incrementals/Appeal to Players",-1),m=["innerHTML"],g=r('

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),b=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"}'),d={name:"guide-to-incrementals/ludology/appeal-gamers/index.md"},w=Object.assign(d,{setup(c){const a=n();return(p,u)=>(l(),o("div",null,[h,e("p",null,[s("2400 words, ~13 minute read. "),e("span",{innerHTML:t(i)[`site/${t(a).page.value.relativePath}`]},null,8,m)]),g]))}});export{b as __pageData,w as default}; +import{d as i}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as o,j as e,a as s,k as t,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"Guide to Incrementals/Appeal to Players",-1),m=["innerHTML"],g=r('

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),b=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"}'),d={name:"guide-to-incrementals/ludology/appeal-gamers/index.md"},w=Object.assign(d,{setup(c){const a=n();return(p,u)=>(l(),o("div",null,[h,e("p",null,[s("2400 words, ~13 minute read. "),e("span",{innerHTML:t(i)[`site/${t(a).page.value.relativePath}`]},null,8,m)]),g]))}});export{b as __pageData,w as default}; diff --git a/assets/guide-to-incrementals_ludology_appeal-gamers_index.md.CESZSCKq.lean.js b/assets/guide-to-incrementals_ludology_appeal-gamers_index.md.ChZkyZEi.lean.js similarity index 93% rename from assets/guide-to-incrementals_ludology_appeal-gamers_index.md.CESZSCKq.lean.js rename to assets/guide-to-incrementals_ludology_appeal-gamers_index.md.ChZkyZEi.lean.js index 41c6d304..da51d1f5 100644 --- a/assets/guide-to-incrementals_ludology_appeal-gamers_index.md.CESZSCKq.lean.js +++ b/assets/guide-to-incrementals_ludology_appeal-gamers_index.md.ChZkyZEi.lean.js @@ -1 +1 @@ -import{d as i}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as o,j as e,a as s,k as t,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"Guide to Incrementals/Appeal to Players",-1),m=["innerHTML"],g=r("",28),b=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"}'),d={name:"guide-to-incrementals/ludology/appeal-gamers/index.md"},w=Object.assign(d,{setup(c){const a=n();return(p,u)=>(l(),o("div",null,[h,e("p",null,[s("2400 words, ~13 minute read. "),e("span",{innerHTML:t(i)[`site/${t(a).page.value.relativePath}`]},null,8,m)]),g]))}});export{b as __pageData,w as default}; +import{d as i}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as o,j as e,a as s,k as t,a5 as r,o as l}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"Guide to Incrementals/Appeal to Players",-1),m=["innerHTML"],g=r("",28),b=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"}'),d={name:"guide-to-incrementals/ludology/appeal-gamers/index.md"},w=Object.assign(d,{setup(c){const a=n();return(p,u)=>(l(),o("div",null,[h,e("p",null,[s("2400 words, ~13 minute read. "),e("span",{innerHTML:t(i)[`site/${t(a).page.value.relativePath}`]},null,8,m)]),g]))}});export{b as __pageData,w as default}; diff --git a/assets/guide-to-incrementals_ludology_content_index.md.BkzTaqAg.js b/assets/guide-to-incrementals_ludology_content_index.md.OQ2PhKlg.js similarity index 99% rename from assets/guide-to-incrementals_ludology_content_index.md.BkzTaqAg.js rename to assets/guide-to-incrementals_ludology_content_index.md.OQ2PhKlg.js index ea6468fd..642198b0 100644 --- a/assets/guide-to-incrementals_ludology_content_index.md.BkzTaqAg.js +++ b/assets/guide-to-incrementals_ludology_content_index.md.OQ2PhKlg.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as i,j as e,a as s,k as t,a5 as r,o as h}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Guide to Incrementals/What is Content?",-1),c=["innerHTML"],u=r('

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),b=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"}'),m={name:"guide-to-incrementals/ludology/content/index.md"},w=Object.assign(m,{setup(d){const a=o();return(g,p)=>(h(),i("div",null,[l,e("p",null,[s("2092 words, ~11 minute read. "),e("span",{innerHTML:t(n)[`site/${t(a).page.value.relativePath}`]},null,8,c)]),u]))}});export{b as __pageData,w as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as i,j as e,a as s,k as t,a5 as r,o as h}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Guide to Incrementals/What is Content?",-1),c=["innerHTML"],u=r('

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),b=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"}'),m={name:"guide-to-incrementals/ludology/content/index.md"},w=Object.assign(m,{setup(d){const a=o();return(g,p)=>(h(),i("div",null,[l,e("p",null,[s("2092 words, ~11 minute read. "),e("span",{innerHTML:t(n)[`site/${t(a).page.value.relativePath}`]},null,8,c)]),u]))}});export{b as __pageData,w as default}; diff --git a/assets/guide-to-incrementals_ludology_content_index.md.BkzTaqAg.lean.js b/assets/guide-to-incrementals_ludology_content_index.md.OQ2PhKlg.lean.js similarity index 93% rename from assets/guide-to-incrementals_ludology_content_index.md.BkzTaqAg.lean.js rename to assets/guide-to-incrementals_ludology_content_index.md.OQ2PhKlg.lean.js index b17a254e..a136c407 100644 --- a/assets/guide-to-incrementals_ludology_content_index.md.BkzTaqAg.lean.js +++ b/assets/guide-to-incrementals_ludology_content_index.md.OQ2PhKlg.lean.js @@ -1 +1 @@ -import{d as n}from"./chunks/git.data.BUKN53Ta.js";import{u as o,c as i,j as e,a as s,k as t,a5 as r,o as h}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Guide to Incrementals/What is Content?",-1),c=["innerHTML"],u=r("",24),b=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"}'),m={name:"guide-to-incrementals/ludology/content/index.md"},w=Object.assign(m,{setup(d){const a=o();return(g,p)=>(h(),i("div",null,[l,e("p",null,[s("2092 words, ~11 minute read. "),e("span",{innerHTML:t(n)[`site/${t(a).page.value.relativePath}`]},null,8,c)]),u]))}});export{b as __pageData,w as default}; +import{d as n}from"./chunks/git.data.pqelWCHe.js";import{u as o,c as i,j as e,a as s,k as t,a5 as r,o as h}from"./chunks/framework.BIC8H_hJ.js";const l=e("h1",{class:"p-name"},"Guide to Incrementals/What is Content?",-1),c=["innerHTML"],u=r("",24),b=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"}'),m={name:"guide-to-incrementals/ludology/content/index.md"},w=Object.assign(m,{setup(d){const a=o();return(g,p)=>(h(),i("div",null,[l,e("p",null,[s("2092 words, ~11 minute read. "),e("span",{innerHTML:t(n)[`site/${t(a).page.value.relativePath}`]},null,8,c)]),u]))}});export{b as __pageData,w as default}; diff --git a/assets/guide-to-incrementals_ludology_definition_index.md.D4iM7G5n.js b/assets/guide-to-incrementals_ludology_definition_index.md.C2J-KDOq.js similarity index 99% rename from assets/guide-to-incrementals_ludology_definition_index.md.D4iM7G5n.js rename to assets/guide-to-incrementals_ludology_definition_index.md.C2J-KDOq.js index cdbad689..083ab9ad 100644 --- a/assets/guide-to-incrementals_ludology_definition_index.md.D4iM7G5n.js +++ b/assets/guide-to-incrementals_ludology_definition_index.md.C2J-KDOq.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as o,j as e,a as i,k as t,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"Guide to Incrementals/Defining the Genre",-1),m=["innerHTML"],g=s('

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),y=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"}'),c={name:"guide-to-incrementals/ludology/definition/index.md"},w=Object.assign(c,{setup(u){const a=n();return(d,p)=>(l(),o("div",null,[h,e("p",null,[i("3429 words, ~19 minute read. "),e("span",{innerHTML:t(r)[`site/${t(a).page.value.relativePath}`]},null,8,m)]),g]))}});export{y as __pageData,w as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as o,j as e,a as i,k as t,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"Guide to Incrementals/Defining the Genre",-1),m=["innerHTML"],g=s('

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),y=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"}'),c={name:"guide-to-incrementals/ludology/definition/index.md"},w=Object.assign(c,{setup(u){const a=n();return(d,p)=>(l(),o("div",null,[h,e("p",null,[i("3429 words, ~19 minute read. "),e("span",{innerHTML:t(r)[`site/${t(a).page.value.relativePath}`]},null,8,m)]),g]))}});export{y as __pageData,w as default}; diff --git a/assets/guide-to-incrementals_ludology_definition_index.md.D4iM7G5n.lean.js b/assets/guide-to-incrementals_ludology_definition_index.md.C2J-KDOq.lean.js similarity index 93% rename from assets/guide-to-incrementals_ludology_definition_index.md.D4iM7G5n.lean.js rename to assets/guide-to-incrementals_ludology_definition_index.md.C2J-KDOq.lean.js index 336cc285..4d872cd3 100644 --- a/assets/guide-to-incrementals_ludology_definition_index.md.D4iM7G5n.lean.js +++ b/assets/guide-to-incrementals_ludology_definition_index.md.C2J-KDOq.lean.js @@ -1 +1 @@ -import{d as r}from"./chunks/git.data.BUKN53Ta.js";import{u as n,c as o,j as e,a as i,k as t,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"Guide to Incrementals/Defining the Genre",-1),m=["innerHTML"],g=s("",64),y=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"}'),c={name:"guide-to-incrementals/ludology/definition/index.md"},w=Object.assign(c,{setup(u){const a=n();return(d,p)=>(l(),o("div",null,[h,e("p",null,[i("3429 words, ~19 minute read. "),e("span",{innerHTML:t(r)[`site/${t(a).page.value.relativePath}`]},null,8,m)]),g]))}});export{y as __pageData,w as default}; +import{d as r}from"./chunks/git.data.pqelWCHe.js";import{u as n,c as o,j as e,a as i,k as t,a5 as s,o as l}from"./chunks/framework.BIC8H_hJ.js";const h=e("h1",{class:"p-name"},"Guide to Incrementals/Defining the Genre",-1),m=["innerHTML"],g=s("",64),y=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"}'),c={name:"guide-to-incrementals/ludology/definition/index.md"},w=Object.assign(c,{setup(u){const a=n();return(d,p)=>(l(),o("div",null,[h,e("p",null,[i("3429 words, ~19 minute read. "),e("span",{innerHTML:t(r)[`site/${t(a).page.value.relativePath}`]},null,8,m)]),g]))}});export{y as __pageData,w as default}; diff --git a/assets/now_index.md.-Sctb59C.js b/assets/now_index.md.4imACR-M.js similarity index 97% rename from assets/now_index.md.-Sctb59C.js rename to assets/now_index.md.4imACR-M.js index ccc2f56f..e0f363b7 100644 --- a/assets/now_index.md.-Sctb59C.js +++ b/assets/now_index.md.4imACR-M.js @@ -1 +1 @@ -import{d as o}from"./chunks/git.data.BUKN53Ta.js";import{u as t,c as i,j as e,a as r,k as a,a5 as l,o as s}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"/now",-1),h=["innerHTML"],d=l('

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),w=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"}'),m={name:"now/index.md"},_=Object.assign(m,{setup(p){const n=t();return(u,g)=>(s(),i("div",null,[c,e("p",null,[r("212 words, ~1 minute read. "),e("span",{innerHTML:a(o)[`site/${a(n).page.value.relativePath}`]},null,8,h)]),d]))}});export{w as __pageData,_ as default}; +import{d as o}from"./chunks/git.data.pqelWCHe.js";import{u as t,c as i,j as e,a as r,k as a,a5 as l,o as s}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"/now",-1),h=["innerHTML"],d=l('

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),w=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"}'),m={name:"now/index.md"},_=Object.assign(m,{setup(p){const n=t();return(u,g)=>(s(),i("div",null,[c,e("p",null,[r("212 words, ~1 minute read. "),e("span",{innerHTML:a(o)[`site/${a(n).page.value.relativePath}`]},null,8,h)]),d]))}});export{w as __pageData,_ as default}; diff --git a/assets/now_index.md.-Sctb59C.lean.js b/assets/now_index.md.4imACR-M.lean.js similarity index 90% rename from assets/now_index.md.-Sctb59C.lean.js rename to assets/now_index.md.4imACR-M.lean.js index 81bd62b1..bfe31047 100644 --- a/assets/now_index.md.-Sctb59C.lean.js +++ b/assets/now_index.md.4imACR-M.lean.js @@ -1 +1 @@ -import{d as o}from"./chunks/git.data.BUKN53Ta.js";import{u as t,c as i,j as e,a as r,k as a,a5 as l,o as s}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"/now",-1),h=["innerHTML"],d=l("",16),w=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"}'),m={name:"now/index.md"},_=Object.assign(m,{setup(p){const n=t();return(u,g)=>(s(),i("div",null,[c,e("p",null,[r("212 words, ~1 minute read. "),e("span",{innerHTML:a(o)[`site/${a(n).page.value.relativePath}`]},null,8,h)]),d]))}});export{w as __pageData,_ as default}; +import{d as o}from"./chunks/git.data.pqelWCHe.js";import{u as t,c as i,j as e,a as r,k as a,a5 as l,o as s}from"./chunks/framework.BIC8H_hJ.js";const c=e("h1",{class:"p-name"},"/now",-1),h=["innerHTML"],d=l("",16),w=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"}'),m={name:"now/index.md"},_=Object.assign(m,{setup(p){const n=t();return(u,g)=>(s(),i("div",null,[c,e("p",null,[r("212 words, ~1 minute read. "),e("span",{innerHTML:a(o)[`site/${a(n).page.value.relativePath}`]},null,8,h)]),d]))}});export{w as __pageData,_ as default}; diff --git a/assets/style.D_J3kCje.css b/assets/style.-DCkroXk.css similarity index 90% rename from assets/style.D_J3kCje.css rename to assets/style.-DCkroXk.css index 90badcf0..38f3e34b 100644 --- a/assets/style.D_J3kCje.css +++ b/assets/style.-DCkroXk.css @@ -1 +1 @@ -:root{--vp-c-white: #ffffff;--vp-c-black: #000000;--vp-c-neutral: var(--vp-c-black);--vp-c-neutral-inverse: var(--vp-c-white)}.dark{--vp-c-neutral: var(--vp-c-white);--vp-c-neutral-inverse: var(--vp-c-black)}:root{--vp-c-gray-1: #dddde3;--vp-c-gray-2: #e4e4e9;--vp-c-gray-3: #ebebef;--vp-c-gray-soft: rgba(142, 150, 170, .14);--vp-c-indigo-1: #3451b2;--vp-c-indigo-2: #3a5ccc;--vp-c-indigo-3: #5672cd;--vp-c-indigo-soft: rgba(100, 108, 255, .14);--vp-c-purple-1: #6f42c1;--vp-c-purple-2: #7e4cc9;--vp-c-purple-3: #8e5cd9;--vp-c-purple-soft: rgba(159, 122, 234, .14);--vp-c-green-1: #18794e;--vp-c-green-2: #299764;--vp-c-green-3: #30a46c;--vp-c-green-soft: rgba(16, 185, 129, .14);--vp-c-yellow-1: #915930;--vp-c-yellow-2: #946300;--vp-c-yellow-3: #9f6a00;--vp-c-yellow-soft: rgba(234, 179, 8, .14);--vp-c-red-1: #b8272c;--vp-c-red-2: #d5393e;--vp-c-red-3: #e0575b;--vp-c-red-soft: rgba(244, 63, 94, .14);--vp-c-sponsor: #db2777}.dark{--vp-c-gray-1: #515c67;--vp-c-gray-2: #414853;--vp-c-gray-3: #32363f;--vp-c-gray-soft: rgba(101, 117, 133, .16);--vp-c-indigo-1: #a8b1ff;--vp-c-indigo-2: #5c73e7;--vp-c-indigo-3: #3e63dd;--vp-c-indigo-soft: rgba(100, 108, 255, .16);--vp-c-purple-1: #c8abfa;--vp-c-purple-2: #a879e6;--vp-c-purple-3: #8e5cd9;--vp-c-purple-soft: rgba(159, 122, 234, .16);--vp-c-green-1: #3dd68c;--vp-c-green-2: #30a46c;--vp-c-green-3: #298459;--vp-c-green-soft: rgba(16, 185, 129, .16);--vp-c-yellow-1: #f9b44e;--vp-c-yellow-2: #da8b17;--vp-c-yellow-3: #a46a0a;--vp-c-yellow-soft: rgba(234, 179, 8, .16);--vp-c-red-1: #f66f81;--vp-c-red-2: #f14158;--vp-c-red-3: #b62a3c;--vp-c-red-soft: rgba(244, 63, 94, .16)}:root{--vp-c-bg: #ffffff;--vp-c-bg-alt: #f6f6f7;--vp-c-bg-elv: #ffffff;--vp-c-bg-soft: #f6f6f7}.dark{--vp-c-bg: #1b1b1f;--vp-c-bg-alt: #161618;--vp-c-bg-elv: #202127;--vp-c-bg-soft: #202127}:root{--vp-c-border: #c2c2c4;--vp-c-divider: #e2e2e3;--vp-c-gutter: #e2e2e3}.dark{--vp-c-border: #3c3f44;--vp-c-divider: #2e2e32;--vp-c-gutter: #000000}:root{--vp-c-text-1: rgba(60, 60, 67);--vp-c-text-2: rgba(60, 60, 67, .78);--vp-c-text-3: rgba(60, 60, 67, .56)}.dark{--vp-c-text-1: rgba(255, 255, 245, .86);--vp-c-text-2: rgba(235, 235, 245, .6);--vp-c-text-3: rgba(235, 235, 245, .38)}:root{--vp-c-default-1: var(--vp-c-gray-1);--vp-c-default-2: var(--vp-c-gray-2);--vp-c-default-3: var(--vp-c-gray-3);--vp-c-default-soft: var(--vp-c-gray-soft);--vp-c-brand-1: var(--vp-c-indigo-1);--vp-c-brand-2: var(--vp-c-indigo-2);--vp-c-brand-3: var(--vp-c-indigo-3);--vp-c-brand-soft: var(--vp-c-indigo-soft);--vp-c-brand: var(--vp-c-brand-1);--vp-c-tip-1: var(--vp-c-brand-1);--vp-c-tip-2: var(--vp-c-brand-2);--vp-c-tip-3: var(--vp-c-brand-3);--vp-c-tip-soft: var(--vp-c-brand-soft);--vp-c-note-1: var(--vp-c-brand-1);--vp-c-note-2: var(--vp-c-brand-2);--vp-c-note-3: var(--vp-c-brand-3);--vp-c-note-soft: var(--vp-c-brand-soft);--vp-c-success-1: var(--vp-c-green-1);--vp-c-success-2: var(--vp-c-green-2);--vp-c-success-3: var(--vp-c-green-3);--vp-c-success-soft: var(--vp-c-green-soft);--vp-c-important-1: var(--vp-c-purple-1);--vp-c-important-2: var(--vp-c-purple-2);--vp-c-important-3: var(--vp-c-purple-3);--vp-c-important-soft: var(--vp-c-purple-soft);--vp-c-warning-1: var(--vp-c-yellow-1);--vp-c-warning-2: var(--vp-c-yellow-2);--vp-c-warning-3: var(--vp-c-yellow-3);--vp-c-warning-soft: var(--vp-c-yellow-soft);--vp-c-danger-1: var(--vp-c-red-1);--vp-c-danger-2: var(--vp-c-red-2);--vp-c-danger-3: var(--vp-c-red-3);--vp-c-danger-soft: var(--vp-c-red-soft);--vp-c-caution-1: var(--vp-c-red-1);--vp-c-caution-2: var(--vp-c-red-2);--vp-c-caution-3: var(--vp-c-red-3);--vp-c-caution-soft: var(--vp-c-red-soft)}:root{--vp-font-family-base: "Inter", ui-sans-serif, system-ui, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Noto Color Emoji";--vp-font-family-mono: ui-monospace, "Menlo", "Monaco", "Consolas", "Liberation Mono", "Courier New", monospace;font-optical-sizing:auto}:root:where(:lang(zh)){--vp-font-family-base: "Punctuation SC", "Inter", ui-sans-serif, system-ui, "PingFang SC", "Noto Sans CJK SC", "Noto Sans SC", "Heiti SC", "Microsoft YaHei", "DengXian", sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Noto Color Emoji"}:root{--vp-shadow-1: 0 1px 2px rgba(0, 0, 0, .04), 0 1px 2px rgba(0, 0, 0, .06);--vp-shadow-2: 0 3px 12px rgba(0, 0, 0, .07), 0 1px 4px rgba(0, 0, 0, .07);--vp-shadow-3: 0 12px 32px rgba(0, 0, 0, .1), 0 2px 6px rgba(0, 0, 0, .08);--vp-shadow-4: 0 14px 44px rgba(0, 0, 0, .12), 0 3px 9px rgba(0, 0, 0, .12);--vp-shadow-5: 0 18px 56px rgba(0, 0, 0, .16), 0 4px 12px rgba(0, 0, 0, .16)}:root{--vp-z-index-footer: 10;--vp-z-index-local-nav: 20;--vp-z-index-nav: 30;--vp-z-index-layout-top: 40;--vp-z-index-backdrop: 50;--vp-z-index-sidebar: 60}@media (min-width: 960px){:root{--vp-z-index-sidebar: 25}}:root{--vp-layout-max-width: 1440px}:root{--vp-header-anchor-symbol: "#"}:root{--vp-code-line-height: 1.7;--vp-code-font-size: .875em;--vp-code-color: var(--vp-c-brand-1);--vp-code-link-color: var(--vp-c-brand-1);--vp-code-link-hover-color: var(--vp-c-brand-2);--vp-code-bg: var(--vp-c-default-soft);--vp-code-block-color: var(--vp-c-text-2);--vp-code-block-bg: var(--vp-c-bg-alt);--vp-code-block-divider-color: var(--vp-c-gutter);--vp-code-lang-color: var(--vp-c-text-3);--vp-code-line-highlight-color: var(--vp-c-default-soft);--vp-code-line-number-color: var(--vp-c-text-3);--vp-code-line-diff-add-color: var(--vp-c-success-soft);--vp-code-line-diff-add-symbol-color: var(--vp-c-success-1);--vp-code-line-diff-remove-color: var(--vp-c-danger-soft);--vp-code-line-diff-remove-symbol-color: var(--vp-c-danger-1);--vp-code-line-warning-color: var(--vp-c-warning-soft);--vp-code-line-error-color: var(--vp-c-danger-soft);--vp-code-copy-code-border-color: var(--vp-c-divider);--vp-code-copy-code-bg: var(--vp-c-bg-soft);--vp-code-copy-code-hover-border-color: var(--vp-c-divider);--vp-code-copy-code-hover-bg: var(--vp-c-bg);--vp-code-copy-code-active-text: var(--vp-c-text-2);--vp-code-copy-copied-text-content: "Copied";--vp-code-tab-divider: var(--vp-code-block-divider-color);--vp-code-tab-text-color: var(--vp-c-text-2);--vp-code-tab-bg: var(--vp-code-block-bg);--vp-code-tab-hover-text-color: var(--vp-c-text-1);--vp-code-tab-active-text-color: var(--vp-c-text-1);--vp-code-tab-active-bar-color: var(--vp-c-brand-1)}:root{--vp-button-brand-border: transparent;--vp-button-brand-text: var(--vp-c-white);--vp-button-brand-bg: var(--vp-c-brand-3);--vp-button-brand-hover-border: transparent;--vp-button-brand-hover-text: var(--vp-c-white);--vp-button-brand-hover-bg: var(--vp-c-brand-2);--vp-button-brand-active-border: transparent;--vp-button-brand-active-text: var(--vp-c-white);--vp-button-brand-active-bg: var(--vp-c-brand-1);--vp-button-alt-border: transparent;--vp-button-alt-text: var(--vp-c-text-1);--vp-button-alt-bg: var(--vp-c-default-3);--vp-button-alt-hover-border: transparent;--vp-button-alt-hover-text: var(--vp-c-text-1);--vp-button-alt-hover-bg: var(--vp-c-default-2);--vp-button-alt-active-border: transparent;--vp-button-alt-active-text: var(--vp-c-text-1);--vp-button-alt-active-bg: var(--vp-c-default-1);--vp-button-sponsor-border: var(--vp-c-text-2);--vp-button-sponsor-text: var(--vp-c-text-2);--vp-button-sponsor-bg: transparent;--vp-button-sponsor-hover-border: var(--vp-c-sponsor);--vp-button-sponsor-hover-text: var(--vp-c-sponsor);--vp-button-sponsor-hover-bg: transparent;--vp-button-sponsor-active-border: var(--vp-c-sponsor);--vp-button-sponsor-active-text: var(--vp-c-sponsor);--vp-button-sponsor-active-bg: transparent}:root{--vp-custom-block-font-size: 14px;--vp-custom-block-code-font-size: 13px;--vp-custom-block-info-border: transparent;--vp-custom-block-info-text: var(--vp-c-text-1);--vp-custom-block-info-bg: var(--vp-c-default-soft);--vp-custom-block-info-code-bg: var(--vp-c-default-soft);--vp-custom-block-note-border: transparent;--vp-custom-block-note-text: var(--vp-c-text-1);--vp-custom-block-note-bg: var(--vp-c-default-soft);--vp-custom-block-note-code-bg: var(--vp-c-default-soft);--vp-custom-block-tip-border: transparent;--vp-custom-block-tip-text: var(--vp-c-text-1);--vp-custom-block-tip-bg: var(--vp-c-tip-soft);--vp-custom-block-tip-code-bg: var(--vp-c-tip-soft);--vp-custom-block-important-border: transparent;--vp-custom-block-important-text: var(--vp-c-text-1);--vp-custom-block-important-bg: var(--vp-c-important-soft);--vp-custom-block-important-code-bg: var(--vp-c-important-soft);--vp-custom-block-warning-border: transparent;--vp-custom-block-warning-text: var(--vp-c-text-1);--vp-custom-block-warning-bg: var(--vp-c-warning-soft);--vp-custom-block-warning-code-bg: var(--vp-c-warning-soft);--vp-custom-block-danger-border: transparent;--vp-custom-block-danger-text: var(--vp-c-text-1);--vp-custom-block-danger-bg: var(--vp-c-danger-soft);--vp-custom-block-danger-code-bg: var(--vp-c-danger-soft);--vp-custom-block-caution-border: transparent;--vp-custom-block-caution-text: var(--vp-c-text-1);--vp-custom-block-caution-bg: var(--vp-c-caution-soft);--vp-custom-block-caution-code-bg: var(--vp-c-caution-soft);--vp-custom-block-details-border: var(--vp-custom-block-info-border);--vp-custom-block-details-text: var(--vp-custom-block-info-text);--vp-custom-block-details-bg: var(--vp-custom-block-info-bg);--vp-custom-block-details-code-bg: var(--vp-custom-block-info-code-bg)}:root{--vp-input-border-color: var(--vp-c-border);--vp-input-bg-color: var(--vp-c-bg-alt);--vp-input-switch-bg-color: var(--vp-c-default-soft)}:root{--vp-nav-height: 64px;--vp-nav-bg-color: var(--vp-c-bg);--vp-nav-screen-bg-color: var(--vp-c-bg);--vp-nav-logo-height: 24px}.hide-nav{--vp-nav-height: 0px}.hide-nav .VPSidebar{--vp-nav-height: 22px}:root{--vp-local-nav-bg-color: var(--vp-c-bg)}:root{--vp-sidebar-width: 272px;--vp-sidebar-bg-color: var(--vp-c-bg-alt)}:root{--vp-backdrop-bg-color: rgba(0, 0, 0, .6)}:root{--vp-home-hero-name-color: var(--vp-c-brand-1);--vp-home-hero-name-background: transparent;--vp-home-hero-image-background-image: none;--vp-home-hero-image-filter: none}:root{--vp-badge-info-border: transparent;--vp-badge-info-text: var(--vp-c-text-2);--vp-badge-info-bg: var(--vp-c-default-soft);--vp-badge-tip-border: transparent;--vp-badge-tip-text: var(--vp-c-tip-1);--vp-badge-tip-bg: var(--vp-c-tip-soft);--vp-badge-warning-border: transparent;--vp-badge-warning-text: var(--vp-c-warning-1);--vp-badge-warning-bg: var(--vp-c-warning-soft);--vp-badge-danger-border: transparent;--vp-badge-danger-text: var(--vp-c-danger-1);--vp-badge-danger-bg: var(--vp-c-danger-soft)}:root{--vp-carbon-ads-text-color: var(--vp-c-text-1);--vp-carbon-ads-poweredby-color: var(--vp-c-text-2);--vp-carbon-ads-bg-color: var(--vp-c-bg-soft);--vp-carbon-ads-hover-text-color: var(--vp-c-brand-1);--vp-carbon-ads-hover-poweredby-color: var(--vp-c-text-1)}:root{--vp-local-search-bg: var(--vp-c-bg);--vp-local-search-result-bg: var(--vp-c-bg);--vp-local-search-result-border: var(--vp-c-divider);--vp-local-search-result-selected-bg: var(--vp-c-bg);--vp-local-search-result-selected-border: var(--vp-c-brand-1);--vp-local-search-highlight-bg: var(--vp-c-brand-1);--vp-local-search-highlight-text: var(--vp-c-neutral-inverse)}@media (prefers-reduced-motion: reduce){*,:before,:after{animation-delay:-1ms!important;animation-duration:1ms!important;animation-iteration-count:1!important;background-attachment:initial!important;scroll-behavior:auto!important;transition-duration:0s!important;transition-delay:0s!important}}*,:before,:after{box-sizing:border-box}html{line-height:1.4;font-size:16px;-webkit-text-size-adjust:100%}html.dark{color-scheme:dark}body{margin:0;width:100%;min-width:320px;min-height:100vh;line-height:24px;font-family:var(--vp-font-family-base);font-size:16px;font-weight:400;color:var(--vp-c-text-1);background-color:var(--vp-c-bg);font-synthesis:style;text-rendering:optimizeLegibility;-webkit-font-smoothing:antialiased;-moz-osx-font-smoothing:grayscale}main{display:block}h1,h2,h3,h4,h5,h6{margin:0;line-height:24px;font-size:16px;font-weight:400}p{margin:0}strong,b{font-weight:600}a,area,button,[role=button],input,label,select,summary,textarea{touch-action:manipulation}a{color:inherit;text-decoration:inherit}ol,ul{list-style:none;margin:0;padding:0}blockquote{margin:0}pre,code,kbd,samp{font-family:var(--vp-font-family-mono)}img,svg,video,canvas,audio,iframe,embed,object{display:block}figure{margin:0}img,video{max-width:100%;height:auto}button,input,optgroup,select,textarea{border:0;padding:0;line-height:inherit;color:inherit}button{padding:0;font-family:inherit;background-color:transparent;background-image:none}button:enabled,[role=button]:enabled{cursor:pointer}button:focus,button:focus-visible{outline:1px dotted;outline:4px auto -webkit-focus-ring-color}button:focus:not(:focus-visible){outline:none!important}input:focus,textarea:focus,select:focus{outline:none}table{border-collapse:collapse}input{background-color:transparent}input:-ms-input-placeholder,textarea:-ms-input-placeholder{color:var(--vp-c-text-3)}input::-ms-input-placeholder,textarea::-ms-input-placeholder{color:var(--vp-c-text-3)}input::placeholder,textarea::placeholder{color:var(--vp-c-text-3)}input::-webkit-outer-spin-button,input::-webkit-inner-spin-button{-webkit-appearance:none;margin:0}input[type=number]{-moz-appearance:textfield}textarea{resize:vertical}select{-webkit-appearance:none}fieldset{margin:0;padding:0}h1,h2,h3,h4,h5,h6,li,p{overflow-wrap:break-word}vite-error-overlay{z-index:9999}mjx-container{display:inline-block;margin:auto 2px -2px}mjx-container>svg{display:inline-block;margin:auto}[class^=vpi-],[class*=" vpi-"],.vp-icon{width:1em;height:1em}[class^=vpi-].bg,[class*=" vpi-"].bg,.vp-icon.bg{background-size:100% 100%;background-color:transparent}[class^=vpi-]:not(.bg),[class*=" vpi-"]:not(.bg),.vp-icon:not(.bg){-webkit-mask:var(--icon) no-repeat;mask:var(--icon) no-repeat;-webkit-mask-size:100% 100%;mask-size:100% 100%;background-color:currentColor;color:inherit}.vpi-align-left{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='M21 6H3M15 12H3M17 18H3'/%3E%3C/svg%3E")}.vpi-arrow-right,.vpi-arrow-down,.vpi-arrow-left,.vpi-arrow-up{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='M5 12h14M12 5l7 7-7 7'/%3E%3C/svg%3E")}.vpi-chevron-right,.vpi-chevron-down,.vpi-chevron-left,.vpi-chevron-up{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='m9 18 6-6-6-6'/%3E%3C/svg%3E")}.vpi-chevron-down,.vpi-arrow-down{transform:rotate(90deg)}.vpi-chevron-left,.vpi-arrow-left{transform:rotate(180deg)}.vpi-chevron-up,.vpi-arrow-up{transform:rotate(-90deg)}.vpi-square-pen{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='M12 3H5a2 2 0 0 0-2 2v14a2 2 0 0 0 2 2h14a2 2 0 0 0 2-2v-7'/%3E%3Cpath d='M18.375 2.625a2.121 2.121 0 1 1 3 3L12 15l-4 1 1-4Z'/%3E%3C/svg%3E")}.vpi-plus{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='M5 12h14M12 5v14'/%3E%3C/svg%3E")}.vpi-sun{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Ccircle cx='12' cy='12' r='4'/%3E%3Cpath d='M12 2v2M12 20v2M4.93 4.93l1.41 1.41M17.66 17.66l1.41 1.41M2 12h2M20 12h2M6.34 17.66l-1.41 1.41M19.07 4.93l-1.41 1.41'/%3E%3C/svg%3E")}.vpi-moon{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='M12 3a6 6 0 0 0 9 9 9 9 0 1 1-9-9Z'/%3E%3C/svg%3E")}.vpi-more-horizontal{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Ccircle cx='12' cy='12' r='1'/%3E%3Ccircle cx='19' cy='12' r='1'/%3E%3Ccircle cx='5' cy='12' r='1'/%3E%3C/svg%3E")}.vpi-languages{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='m5 8 6 6M4 14l6-6 2-3M2 5h12M7 2h1M22 22l-5-10-5 10M14 18h6'/%3E%3C/svg%3E")}.vpi-heart{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='M19 14c1.49-1.46 3-3.21 3-5.5A5.5 5.5 0 0 0 16.5 3c-1.76 0-3 .5-4.5 2-1.5-1.5-2.74-2-4.5-2A5.5 5.5 0 0 0 2 8.5c0 2.3 1.5 4.05 3 5.5l7 7Z'/%3E%3C/svg%3E")}.vpi-search{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Ccircle cx='11' cy='11' r='8'/%3E%3Cpath d='m21 21-4.3-4.3'/%3E%3C/svg%3E")}.vpi-layout-list{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Crect width='7' height='7' x='3' y='3' rx='1'/%3E%3Crect width='7' height='7' x='3' y='14' rx='1'/%3E%3Cpath d='M14 4h7M14 9h7M14 15h7M14 20h7'/%3E%3C/svg%3E")}.vpi-delete{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='M20 5H9l-7 7 7 7h11a2 2 0 0 0 2-2V7a2 2 0 0 0-2-2ZM18 9l-6 6M12 9l6 6'/%3E%3C/svg%3E")}.vpi-corner-down-left{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='m9 10-5 5 5 5'/%3E%3Cpath d='M20 4v7a4 4 0 0 1-4 4H4'/%3E%3C/svg%3E")}:root{--vp-icon-copy: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='rgba(128,128,128,1)' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Crect width='8' height='4' x='8' y='2' rx='1' ry='1'/%3E%3Cpath d='M16 4h2a2 2 0 0 1 2 2v14a2 2 0 0 1-2 2H6a2 2 0 0 1-2-2V6a2 2 0 0 1 2-2h2'/%3E%3C/svg%3E");--vp-icon-copied: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='rgba(128,128,128,1)' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Crect width='8' height='4' x='8' y='2' rx='1' ry='1'/%3E%3Cpath d='M16 4h2a2 2 0 0 1 2 2v14a2 2 0 0 1-2 2H6a2 2 0 0 1-2-2V6a2 2 0 0 1 2-2h2'/%3E%3Cpath d='m9 14 2 2 4-4'/%3E%3C/svg%3E")}.vpi-social-discord{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M20.317 4.37a19.791 19.791 0 0 0-4.885-1.515.074.074 0 0 0-.079.037c-.21.375-.444.864-.608 1.25a18.27 18.27 0 0 0-5.487 0 12.64 12.64 0 0 0-.617-1.25.077.077 0 0 0-.079-.037A19.736 19.736 0 0 0 3.677 4.37a.07.07 0 0 0-.032.027C.533 9.046-.32 13.58.099 18.057a.082.082 0 0 0 .031.057 19.9 19.9 0 0 0 5.993 3.03.078.078 0 0 0 .084-.028c.462-.63.874-1.295 1.226-1.994a.076.076 0 0 0-.041-.106 13.107 13.107 0 0 1-1.872-.892.077.077 0 0 1-.008-.128 10.2 10.2 0 0 0 .372-.292.074.074 0 0 1 .077-.01c3.928 1.793 8.18 1.793 12.062 0a.074.074 0 0 1 .078.01c.12.098.246.198.373.292a.077.077 0 0 1-.006.127 12.299 12.299 0 0 1-1.873.892.077.077 0 0 0-.041.107c.36.698.772 1.362 1.225 1.993a.076.076 0 0 0 .084.028 19.839 19.839 0 0 0 6.002-3.03.077.077 0 0 0 .032-.054c.5-5.177-.838-9.674-3.549-13.66a.061.061 0 0 0-.031-.03zM8.02 15.33c-1.183 0-2.157-1.085-2.157-2.419 0-1.333.956-2.419 2.157-2.419 1.21 0 2.176 1.096 2.157 2.42 0 1.333-.956 2.418-2.157 2.418zm7.975 0c-1.183 0-2.157-1.085-2.157-2.419 0-1.333.955-2.419 2.157-2.419 1.21 0 2.176 1.096 2.157 2.42 0 1.333-.946 2.418-2.157 2.418Z'/%3E%3C/svg%3E")}.vpi-social-facebook{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M9.101 23.691v-7.98H6.627v-3.667h2.474v-1.58c0-4.085 1.848-5.978 5.858-5.978.401 0 .955.042 1.468.103a8.68 8.68 0 0 1 1.141.195v3.325a8.623 8.623 0 0 0-.653-.036 26.805 26.805 0 0 0-.733-.009c-.707 0-1.259.096-1.675.309a1.686 1.686 0 0 0-.679.622c-.258.42-.374.995-.374 1.752v1.297h3.919l-.386 2.103-.287 1.564h-3.246v8.245C19.396 23.238 24 18.179 24 12.044c0-6.627-5.373-12-12-12s-12 5.373-12 12c0 5.628 3.874 10.35 9.101 11.647Z'/%3E%3C/svg%3E")}.vpi-social-github{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M12 .297c-6.63 0-12 5.373-12 12 0 5.303 3.438 9.8 8.205 11.385.6.113.82-.258.82-.577 0-.285-.01-1.04-.015-2.04-3.338.724-4.042-1.61-4.042-1.61C4.422 18.07 3.633 17.7 3.633 17.7c-1.087-.744.084-.729.084-.729 1.205.084 1.838 1.236 1.838 1.236 1.07 1.835 2.809 1.305 3.495.998.108-.776.417-1.305.76-1.605-2.665-.3-5.466-1.332-5.466-5.93 0-1.31.465-2.38 1.235-3.22-.135-.303-.54-1.523.105-3.176 0 0 1.005-.322 3.3 1.23.96-.267 1.98-.399 3-.405 1.02.006 2.04.138 3 .405 2.28-1.552 3.285-1.23 3.285-1.23.645 1.653.24 2.873.12 3.176.765.84 1.23 1.91 1.23 3.22 0 4.61-2.805 5.625-5.475 5.92.42.36.81 1.096.81 2.22 0 1.606-.015 2.896-.015 3.286 0 .315.21.69.825.57C20.565 22.092 24 17.592 24 12.297c0-6.627-5.373-12-12-12'/%3E%3C/svg%3E")}.vpi-social-instagram{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M7.03.084c-1.277.06-2.149.264-2.91.563a5.874 5.874 0 0 0-2.124 1.388 5.878 5.878 0 0 0-1.38 2.127C.321 4.926.12 5.8.064 7.076.008 8.354-.005 8.764.001 12.023c.007 3.259.021 3.667.083 4.947.061 1.277.264 2.149.563 2.911.308.789.72 1.457 1.388 2.123a5.872 5.872 0 0 0 2.129 1.38c.763.295 1.636.496 2.913.552 1.278.056 1.689.069 4.947.063 3.257-.007 3.668-.021 4.947-.082 1.28-.06 2.147-.265 2.91-.563a5.881 5.881 0 0 0 2.123-1.388 5.881 5.881 0 0 0 1.38-2.129c.295-.763.496-1.636.551-2.912.056-1.28.07-1.69.063-4.948-.006-3.258-.02-3.667-.081-4.947-.06-1.28-.264-2.148-.564-2.911a5.892 5.892 0 0 0-1.387-2.123 5.857 5.857 0 0 0-2.128-1.38C19.074.322 18.202.12 16.924.066 15.647.009 15.236-.006 11.977 0 8.718.008 8.31.021 7.03.084m.14 21.693c-1.17-.05-1.805-.245-2.228-.408a3.736 3.736 0 0 1-1.382-.895 3.695 3.695 0 0 1-.9-1.378c-.165-.423-.363-1.058-.417-2.228-.06-1.264-.072-1.644-.08-4.848-.006-3.204.006-3.583.061-4.848.05-1.169.246-1.805.408-2.228.216-.561.477-.96.895-1.382a3.705 3.705 0 0 1 1.379-.9c.423-.165 1.057-.361 2.227-.417 1.265-.06 1.644-.072 4.848-.08 3.203-.006 3.583.006 4.85.062 1.168.05 1.804.244 2.227.408.56.216.96.475 1.382.895.421.42.681.817.9 1.378.165.422.362 1.056.417 2.227.06 1.265.074 1.645.08 4.848.005 3.203-.006 3.583-.061 4.848-.051 1.17-.245 1.805-.408 2.23-.216.56-.477.96-.896 1.38a3.705 3.705 0 0 1-1.378.9c-.422.165-1.058.362-2.226.418-1.266.06-1.645.072-4.85.079-3.204.007-3.582-.006-4.848-.06m9.783-16.192a1.44 1.44 0 1 0 1.437-1.442 1.44 1.44 0 0 0-1.437 1.442M5.839 12.012a6.161 6.161 0 1 0 12.323-.024 6.162 6.162 0 0 0-12.323.024M8 12.008A4 4 0 1 1 12.008 16 4 4 0 0 1 8 12.008'/%3E%3C/svg%3E")}.vpi-social-linkedin{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M20.447 20.452h-3.554v-5.569c0-1.328-.027-3.037-1.852-3.037-1.853 0-2.136 1.445-2.136 2.939v5.667H9.351V9h3.414v1.561h.046c.477-.9 1.637-1.85 3.37-1.85 3.601 0 4.267 2.37 4.267 5.455v6.286zM5.337 7.433a2.062 2.062 0 0 1-2.063-2.065 2.064 2.064 0 1 1 2.063 2.065zm1.782 13.019H3.555V9h3.564v11.452zM22.225 0H1.771C.792 0 0 .774 0 1.729v20.542C0 23.227.792 24 1.771 24h20.451C23.2 24 24 23.227 24 22.271V1.729C24 .774 23.2 0 22.222 0h.003z'/%3E%3C/svg%3E")}.vpi-social-mastodon{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M23.268 5.313c-.35-2.578-2.617-4.61-5.304-5.004C17.51.242 15.792 0 11.813 0h-.03c-3.98 0-4.835.242-5.288.309C3.882.692 1.496 2.518.917 5.127.64 6.412.61 7.837.661 9.143c.074 1.874.088 3.745.26 5.611.118 1.24.325 2.47.62 3.68.55 2.237 2.777 4.098 4.96 4.857 2.336.792 4.849.923 7.256.38.265-.061.527-.132.786-.213.585-.184 1.27-.39 1.774-.753a.057.057 0 0 0 .023-.043v-1.809a.052.052 0 0 0-.02-.041.053.053 0 0 0-.046-.01 20.282 20.282 0 0 1-4.709.545c-2.73 0-3.463-1.284-3.674-1.818a5.593 5.593 0 0 1-.319-1.433.053.053 0 0 1 .066-.054c1.517.363 3.072.546 4.632.546.376 0 .75 0 1.125-.01 1.57-.044 3.224-.124 4.768-.422.038-.008.077-.015.11-.024 2.435-.464 4.753-1.92 4.989-5.604.008-.145.03-1.52.03-1.67.002-.512.167-3.63-.024-5.545zm-3.748 9.195h-2.561V8.29c0-1.309-.55-1.976-1.67-1.976-1.23 0-1.846.79-1.846 2.35v3.403h-2.546V8.663c0-1.56-.617-2.35-1.848-2.35-1.112 0-1.668.668-1.67 1.977v6.218H4.822V8.102c0-1.31.337-2.35 1.011-3.12.696-.77 1.608-1.164 2.74-1.164 1.311 0 2.302.5 2.962 1.498l.638 1.06.638-1.06c.66-.999 1.65-1.498 2.96-1.498 1.13 0 2.043.395 2.74 1.164.675.77 1.012 1.81 1.012 3.12z'/%3E%3C/svg%3E")}.vpi-social-npm{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M1.763 0C.786 0 0 .786 0 1.763v20.474C0 23.214.786 24 1.763 24h20.474c.977 0 1.763-.786 1.763-1.763V1.763C24 .786 23.214 0 22.237 0zM5.13 5.323l13.837.019-.009 13.836h-3.464l.01-10.382h-3.456L12.04 19.17H5.113z'/%3E%3C/svg%3E")}.vpi-social-slack{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M5.042 15.165a2.528 2.528 0 0 1-2.52 2.523A2.528 2.528 0 0 1 0 15.165a2.527 2.527 0 0 1 2.522-2.52h2.52v2.52zm1.271 0a2.527 2.527 0 0 1 2.521-2.52 2.527 2.527 0 0 1 2.521 2.52v6.313A2.528 2.528 0 0 1 8.834 24a2.528 2.528 0 0 1-2.521-2.522v-6.313zM8.834 5.042a2.528 2.528 0 0 1-2.521-2.52A2.528 2.528 0 0 1 8.834 0a2.528 2.528 0 0 1 2.521 2.522v2.52H8.834zm0 1.271a2.528 2.528 0 0 1 2.521 2.521 2.528 2.528 0 0 1-2.521 2.521H2.522A2.528 2.528 0 0 1 0 8.834a2.528 2.528 0 0 1 2.522-2.521h6.312zm10.122 2.521a2.528 2.528 0 0 1 2.522-2.521A2.528 2.528 0 0 1 24 8.834a2.528 2.528 0 0 1-2.522 2.521h-2.522V8.834zm-1.268 0a2.528 2.528 0 0 1-2.523 2.521 2.527 2.527 0 0 1-2.52-2.521V2.522A2.527 2.527 0 0 1 15.165 0a2.528 2.528 0 0 1 2.523 2.522v6.312zm-2.523 10.122a2.528 2.528 0 0 1 2.523 2.522A2.528 2.528 0 0 1 15.165 24a2.527 2.527 0 0 1-2.52-2.522v-2.522h2.52zm0-1.268a2.527 2.527 0 0 1-2.52-2.523 2.526 2.526 0 0 1 2.52-2.52h6.313A2.527 2.527 0 0 1 24 15.165a2.528 2.528 0 0 1-2.522 2.523h-6.313z'/%3E%3C/svg%3E")}.vpi-social-twitter,.vpi-social-x{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M18.901 1.153h3.68l-8.04 9.19L24 22.846h-7.406l-5.8-7.584-6.638 7.584H.474l8.6-9.83L0 1.154h7.594l5.243 6.932ZM17.61 20.644h2.039L6.486 3.24H4.298Z'/%3E%3C/svg%3E")}.vpi-social-youtube{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M23.498 6.186a3.016 3.016 0 0 0-2.122-2.136C19.505 3.545 12 3.545 12 3.545s-7.505 0-9.377.505A3.017 3.017 0 0 0 .502 6.186C0 8.07 0 12 0 12s0 3.93.502 5.814a3.016 3.016 0 0 0 2.122 2.136c1.871.505 9.376.505 9.376.505s7.505 0 9.377-.505a3.015 3.015 0 0 0 2.122-2.136C24 15.93 24 12 24 12s0-3.93-.502-5.814zM9.545 15.568V8.432L15.818 12l-6.273 3.568z'/%3E%3C/svg%3E")}.visually-hidden{position:absolute;width:1px;height:1px;white-space:nowrap;clip:rect(0 0 0 0);clip-path:inset(50%);overflow:hidden}.custom-block{border:1px solid transparent;border-radius:8px;padding:16px 16px 8px;line-height:24px;font-size:var(--vp-custom-block-font-size);color:var(--vp-c-text-2)}.custom-block.info{border-color:var(--vp-custom-block-info-border);color:var(--vp-custom-block-info-text);background-color:var(--vp-custom-block-info-bg)}.custom-block.info a,.custom-block.info code{color:var(--vp-c-brand-1)}.custom-block.info a:hover,.custom-block.info a:hover>code{color:var(--vp-c-brand-2)}.custom-block.info code{background-color:var(--vp-custom-block-info-code-bg)}.custom-block.note{border-color:var(--vp-custom-block-note-border);color:var(--vp-custom-block-note-text);background-color:var(--vp-custom-block-note-bg)}.custom-block.note a,.custom-block.note code{color:var(--vp-c-brand-1)}.custom-block.note a:hover,.custom-block.note a:hover>code{color:var(--vp-c-brand-2)}.custom-block.note code{background-color:var(--vp-custom-block-note-code-bg)}.custom-block.tip{border-color:var(--vp-custom-block-tip-border);color:var(--vp-custom-block-tip-text);background-color:var(--vp-custom-block-tip-bg)}.custom-block.tip a,.custom-block.tip code{color:var(--vp-c-tip-1)}.custom-block.tip a:hover,.custom-block.tip a:hover>code{color:var(--vp-c-tip-2)}.custom-block.tip code{background-color:var(--vp-custom-block-tip-code-bg)}.custom-block.important{border-color:var(--vp-custom-block-important-border);color:var(--vp-custom-block-important-text);background-color:var(--vp-custom-block-important-bg)}.custom-block.important a,.custom-block.important code{color:var(--vp-c-important-1)}.custom-block.important a:hover,.custom-block.important a:hover>code{color:var(--vp-c-important-2)}.custom-block.important code{background-color:var(--vp-custom-block-important-code-bg)}.custom-block.warning{border-color:var(--vp-custom-block-warning-border);color:var(--vp-custom-block-warning-text);background-color:var(--vp-custom-block-warning-bg)}.custom-block.warning a,.custom-block.warning code{color:var(--vp-c-warning-1)}.custom-block.warning a:hover,.custom-block.warning a:hover>code{color:var(--vp-c-warning-2)}.custom-block.warning code{background-color:var(--vp-custom-block-warning-code-bg)}.custom-block.danger{border-color:var(--vp-custom-block-danger-border);color:var(--vp-custom-block-danger-text);background-color:var(--vp-custom-block-danger-bg)}.custom-block.danger a,.custom-block.danger code{color:var(--vp-c-danger-1)}.custom-block.danger a:hover,.custom-block.danger a:hover>code{color:var(--vp-c-danger-2)}.custom-block.danger code{background-color:var(--vp-custom-block-danger-code-bg)}.custom-block.caution{border-color:var(--vp-custom-block-caution-border);color:var(--vp-custom-block-caution-text);background-color:var(--vp-custom-block-caution-bg)}.custom-block.caution a,.custom-block.caution code{color:var(--vp-c-caution-1)}.custom-block.caution a:hover,.custom-block.caution a:hover>code{color:var(--vp-c-caution-2)}.custom-block.caution code{background-color:var(--vp-custom-block-caution-code-bg)}.custom-block.details{border-color:var(--vp-custom-block-details-border);color:var(--vp-custom-block-details-text);background-color:var(--vp-custom-block-details-bg)}.custom-block.details a{color:var(--vp-c-brand-1)}.custom-block.details a:hover,.custom-block.details a:hover>code{color:var(--vp-c-brand-2)}.custom-block.details code{background-color:var(--vp-custom-block-details-code-bg)}.custom-block-title{font-weight:600}.custom-block p+p{margin:8px 0}.custom-block.details summary{margin:0 0 8px;font-weight:700;cursor:pointer;-webkit-user-select:none;user-select:none}.custom-block.details summary+p{margin:8px 0}.custom-block a{color:inherit;font-weight:600;text-decoration:underline;text-underline-offset:2px;transition:opacity .25s}.custom-block a:hover{opacity:.75}.custom-block code{font-size:var(--vp-custom-block-code-font-size)}.custom-block.custom-block th,.custom-block.custom-block blockquote>p{font-size:var(--vp-custom-block-font-size);color:inherit}.dark .vp-code span{color:var(--shiki-dark, inherit)}html:not(.dark) .vp-code span{color:var(--shiki-light, inherit)}.vp-code-group{margin-top:16px}.vp-code-group .tabs{position:relative;display:flex;margin-right:-24px;margin-left:-24px;padding:0 12px;background-color:var(--vp-code-tab-bg);overflow-x:auto;overflow-y:hidden;box-shadow:inset 0 -1px var(--vp-code-tab-divider)}@media (min-width: 640px){.vp-code-group .tabs{margin-right:0;margin-left:0;border-radius:8px 8px 0 0}}.vp-code-group .tabs input{position:fixed;opacity:0;pointer-events:none}.vp-code-group .tabs label{position:relative;display:inline-block;border-bottom:1px solid transparent;padding:0 12px;line-height:48px;font-size:14px;font-weight:500;color:var(--vp-code-tab-text-color);white-space:nowrap;cursor:pointer;transition:color .25s}.vp-code-group .tabs label:after{position:absolute;right:8px;bottom:-1px;left:8px;z-index:1;height:2px;border-radius:2px;content:"";background-color:transparent;transition:background-color .25s}.vp-code-group label:hover{color:var(--vp-code-tab-hover-text-color)}.vp-code-group input:checked+label{color:var(--vp-code-tab-active-text-color)}.vp-code-group input:checked+label:after{background-color:var(--vp-code-tab-active-bar-color)}.vp-code-group div[class*=language-],.vp-block{display:none;margin-top:0!important;border-top-left-radius:0!important;border-top-right-radius:0!important}.vp-code-group div[class*=language-].active,.vp-block.active{display:block}.vp-block{padding:20px 24px}.vp-doc h1,.vp-doc h2,.vp-doc h3,.vp-doc h4,.vp-doc h5,.vp-doc h6{position:relative;font-weight:600;outline:none}.vp-doc h1{letter-spacing:-.02em;line-height:40px;font-size:28px}.vp-doc h2{margin:48px 0 16px;border-top:1px solid var(--vp-c-divider);padding-top:24px;letter-spacing:-.02em;line-height:32px;font-size:24px}.vp-doc h3{margin:32px 0 0;letter-spacing:-.01em;line-height:28px;font-size:20px}.vp-doc .header-anchor{position:absolute;top:0;left:0;margin-left:-.87em;font-weight:500;-webkit-user-select:none;user-select:none;opacity:0;text-decoration:none;transition:color .25s,opacity .25s}.vp-doc .header-anchor:before{content:var(--vp-header-anchor-symbol)}.vp-doc h1:hover .header-anchor,.vp-doc h1 .header-anchor:focus,.vp-doc h2:hover .header-anchor,.vp-doc h2 .header-anchor:focus,.vp-doc h3:hover .header-anchor,.vp-doc h3 .header-anchor:focus,.vp-doc h4:hover .header-anchor,.vp-doc h4 .header-anchor:focus,.vp-doc h5:hover .header-anchor,.vp-doc h5 .header-anchor:focus,.vp-doc h6:hover .header-anchor,.vp-doc h6 .header-anchor:focus{opacity:1}@media (min-width: 768px){.vp-doc h1{letter-spacing:-.02em;line-height:40px;font-size:32px}}.vp-doc h2 .header-anchor{top:24px}.vp-doc p,.vp-doc summary{margin:16px 0}.vp-doc p{line-height:28px}.vp-doc blockquote{margin:16px 0;border-left:2px solid var(--vp-c-divider);padding-left:16px;transition:border-color .5s}.vp-doc blockquote>p{margin:0;font-size:16px;color:var(--vp-c-text-2);transition:color .5s}.vp-doc a{font-weight:500;color:var(--vp-c-brand-1);text-decoration:underline;text-underline-offset:2px;transition:color .25s,opacity .25s}.vp-doc a:hover{color:var(--vp-c-brand-2)}.vp-doc strong{font-weight:600}.vp-doc ul,.vp-doc ol{padding-left:1.25rem;margin:16px 0}.vp-doc ul{list-style:disc}.vp-doc ol{list-style:decimal}.vp-doc li+li{margin-top:8px}.vp-doc li>ol,.vp-doc li>ul{margin:8px 0 0}.vp-doc table{display:block;border-collapse:collapse;margin:20px 0;overflow-x:auto}.vp-doc tr{background-color:var(--vp-c-bg);border-top:1px solid var(--vp-c-divider);transition:background-color .5s}.vp-doc tr:nth-child(2n){background-color:var(--vp-c-bg-soft)}.vp-doc th,.vp-doc td{border:1px solid var(--vp-c-divider);padding:8px 16px}.vp-doc th{text-align:left;font-size:14px;font-weight:600;color:var(--vp-c-text-2);background-color:var(--vp-c-bg-soft)}.vp-doc td{font-size:14px}.vp-doc hr{margin:16px 0;border:none;border-top:1px solid var(--vp-c-divider)}.vp-doc .custom-block{margin:16px 0}.vp-doc .custom-block p{margin:8px 0;line-height:24px}.vp-doc .custom-block p:first-child{margin:0}.vp-doc .custom-block div[class*=language-]{margin:8px 0;border-radius:8px}.vp-doc .custom-block div[class*=language-] code{font-weight:400;background-color:transparent}.vp-doc .custom-block .vp-code-group .tabs{margin:0;border-radius:8px 8px 0 0}.vp-doc :not(pre,h1,h2,h3,h4,h5,h6)>code{font-size:var(--vp-code-font-size);color:var(--vp-code-color)}.vp-doc :not(pre)>code{border-radius:4px;padding:3px 6px;background-color:var(--vp-code-bg);transition:color .25s,background-color .5s}.vp-doc a>code{color:var(--vp-code-link-color)}.vp-doc a:hover>code{color:var(--vp-code-link-hover-color)}.vp-doc h1>code,.vp-doc h2>code,.vp-doc h3>code{font-size:.9em}.vp-doc div[class*=language-],.vp-block{position:relative;margin:16px -24px;background-color:var(--vp-code-block-bg);overflow-x:auto;transition:background-color .5s}@media (min-width: 640px){.vp-doc div[class*=language-],.vp-block{border-radius:8px;margin:16px 0}}@media (max-width: 639px){.vp-doc li div[class*=language-]{border-radius:8px 0 0 8px}}.vp-doc div[class*=language-]+div[class*=language-],.vp-doc div[class$=-api]+div[class*=language-],.vp-doc div[class*=language-]+div[class$=-api]>div[class*=language-]{margin-top:-8px}.vp-doc [class*=language-] pre,.vp-doc [class*=language-] code{direction:ltr;text-align:left;white-space:pre;word-spacing:normal;word-break:normal;word-wrap:normal;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-hyphens:none;-moz-hyphens:none;-ms-hyphens:none;hyphens:none}.vp-doc [class*=language-] pre{position:relative;z-index:1;margin:0;padding:20px 0;background:transparent;overflow-x:auto}.vp-doc [class*=language-] code{display:block;padding:0 24px;width:fit-content;min-width:100%;line-height:var(--vp-code-line-height);font-size:var(--vp-code-font-size);color:var(--vp-code-block-color);transition:color .5s}.vp-doc [class*=language-] code .highlighted{background-color:var(--vp-code-line-highlight-color);transition:background-color .5s;margin:0 -24px;padding:0 24px;width:calc(100% + 48px);display:inline-block}.vp-doc [class*=language-] code .highlighted.error{background-color:var(--vp-code-line-error-color)}.vp-doc [class*=language-] code .highlighted.warning{background-color:var(--vp-code-line-warning-color)}.vp-doc [class*=language-] code .diff{transition:background-color .5s;margin:0 -24px;padding:0 24px;width:calc(100% + 48px);display:inline-block}.vp-doc [class*=language-] code .diff:before{position:absolute;left:10px}.vp-doc [class*=language-] .has-focused-lines .line:not(.has-focus){filter:blur(.095rem);opacity:.4;transition:filter .35s,opacity .35s}.vp-doc [class*=language-] .has-focused-lines .line:not(.has-focus){opacity:.7;transition:filter .35s,opacity .35s}.vp-doc [class*=language-]:hover .has-focused-lines .line:not(.has-focus){filter:blur(0);opacity:1}.vp-doc [class*=language-] code .diff.remove{background-color:var(--vp-code-line-diff-remove-color);opacity:.7}.vp-doc [class*=language-] code .diff.remove:before{content:"-";color:var(--vp-code-line-diff-remove-symbol-color)}.vp-doc [class*=language-] code .diff.add{background-color:var(--vp-code-line-diff-add-color)}.vp-doc [class*=language-] code .diff.add:before{content:"+";color:var(--vp-code-line-diff-add-symbol-color)}.vp-doc div[class*=language-].line-numbers-mode{padding-left:32px}.vp-doc .line-numbers-wrapper{position:absolute;top:0;bottom:0;left:0;z-index:3;border-right:1px solid var(--vp-code-block-divider-color);padding-top:20px;width:32px;text-align:center;font-family:var(--vp-font-family-mono);line-height:var(--vp-code-line-height);font-size:var(--vp-code-font-size);color:var(--vp-code-line-number-color);transition:border-color .5s,color .5s}.vp-doc [class*=language-]>button.copy{direction:ltr;position:absolute;top:12px;right:12px;z-index:3;border:1px solid var(--vp-code-copy-code-border-color);border-radius:4px;width:40px;height:40px;background-color:var(--vp-code-copy-code-bg);opacity:0;cursor:pointer;background-image:var(--vp-icon-copy);background-position:50%;background-size:20px;background-repeat:no-repeat;transition:border-color .25s,background-color .25s,opacity .25s}.vp-doc [class*=language-]:hover>button.copy,.vp-doc [class*=language-]>button.copy:focus{opacity:1}.vp-doc [class*=language-]>button.copy:hover,.vp-doc [class*=language-]>button.copy.copied{border-color:var(--vp-code-copy-code-hover-border-color);background-color:var(--vp-code-copy-code-hover-bg)}.vp-doc [class*=language-]>button.copy.copied,.vp-doc [class*=language-]>button.copy:hover.copied{border-radius:0 4px 4px 0;background-color:var(--vp-code-copy-code-hover-bg);background-image:var(--vp-icon-copied)}.vp-doc [class*=language-]>button.copy.copied:before,.vp-doc [class*=language-]>button.copy:hover.copied:before{position:relative;top:-1px;transform:translate(calc(-100% - 1px));display:flex;justify-content:center;align-items:center;border:1px solid var(--vp-code-copy-code-hover-border-color);border-right:0;border-radius:4px 0 0 4px;padding:0 10px;width:fit-content;height:40px;text-align:center;font-size:12px;font-weight:500;color:var(--vp-code-copy-code-active-text);background-color:var(--vp-code-copy-code-hover-bg);white-space:nowrap;content:var(--vp-code-copy-copied-text-content)}.vp-doc [class*=language-]>span.lang{position:absolute;top:2px;right:8px;z-index:2;font-size:12px;font-weight:500;color:var(--vp-code-lang-color);transition:color .4s,opacity .4s}.vp-doc [class*=language-]:hover>button.copy+span.lang,.vp-doc [class*=language-]>button.copy:focus+span.lang{opacity:0}.vp-doc .VPTeamMembers{margin-top:24px}.vp-doc .VPTeamMembers.small.count-1 .container{margin:0!important;max-width:calc((100% - 24px)/2)!important}.vp-doc .VPTeamMembers.small.count-2 .container,.vp-doc .VPTeamMembers.small.count-3 .container{max-width:100%!important}.vp-doc .VPTeamMembers.medium.count-1 .container{margin:0!important;max-width:calc((100% - 24px)/2)!important}:is(.vp-external-link-icon,.vp-doc a[href*="://"],.vp-doc a[target=_blank]):not(.no-icon):after{display:inline-block;margin-top:-1px;margin-left:4px;width:11px;height:11px;background:currentColor;color:var(--vp-c-text-3);flex-shrink:0;--icon: url("data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' %3E%3Cpath d='M0 0h24v24H0V0z' fill='none' /%3E%3Cpath d='M9 5v2h6.59L4 18.59 5.41 20 17 8.41V15h2V5H9z' /%3E%3C/svg%3E");-webkit-mask-image:var(--icon);mask-image:var(--icon)}.vp-external-link-icon:after{content:""}.external-link-icon-enabled :is(.vp-doc a[href*="://"],.vp-doc a[target=_blank]):after{content:"";color:currentColor}.vp-sponsor{border-radius:16px;overflow:hidden}.vp-sponsor.aside{border-radius:12px}.vp-sponsor-section+.vp-sponsor-section{margin-top:4px}.vp-sponsor-tier{margin:0 0 4px!important;text-align:center;letter-spacing:1px!important;line-height:24px;width:100%;font-weight:600;color:var(--vp-c-text-2);background-color:var(--vp-c-bg-soft)}.vp-sponsor.normal .vp-sponsor-tier{padding:13px 0 11px;font-size:14px}.vp-sponsor.aside .vp-sponsor-tier{padding:9px 0 7px;font-size:12px}.vp-sponsor-grid+.vp-sponsor-tier{margin-top:4px}.vp-sponsor-grid{display:flex;flex-wrap:wrap;gap:4px}.vp-sponsor-grid.xmini .vp-sponsor-grid-link{height:64px}.vp-sponsor-grid.xmini .vp-sponsor-grid-image{max-width:64px;max-height:22px}.vp-sponsor-grid.mini .vp-sponsor-grid-link{height:72px}.vp-sponsor-grid.mini .vp-sponsor-grid-image{max-width:96px;max-height:24px}.vp-sponsor-grid.small .vp-sponsor-grid-link{height:96px}.vp-sponsor-grid.small .vp-sponsor-grid-image{max-width:96px;max-height:24px}.vp-sponsor-grid.medium .vp-sponsor-grid-link{height:112px}.vp-sponsor-grid.medium .vp-sponsor-grid-image{max-width:120px;max-height:36px}.vp-sponsor-grid.big .vp-sponsor-grid-link{height:184px}.vp-sponsor-grid.big .vp-sponsor-grid-image{max-width:192px;max-height:56px}.vp-sponsor-grid[data-vp-grid="2"] .vp-sponsor-grid-item{width:calc((100% - 4px)/2)}.vp-sponsor-grid[data-vp-grid="3"] .vp-sponsor-grid-item{width:calc((100% - 4px * 2) / 3)}.vp-sponsor-grid[data-vp-grid="4"] .vp-sponsor-grid-item{width:calc((100% - 12px)/4)}.vp-sponsor-grid[data-vp-grid="5"] .vp-sponsor-grid-item{width:calc((100% - 16px)/5)}.vp-sponsor-grid[data-vp-grid="6"] .vp-sponsor-grid-item{width:calc((100% - 4px * 5) / 6)}.vp-sponsor-grid-item{flex-shrink:0;width:100%;background-color:var(--vp-c-bg-soft);transition:background-color .25s}.vp-sponsor-grid-item:hover{background-color:var(--vp-c-default-soft)}.vp-sponsor-grid-item:hover .vp-sponsor-grid-image{filter:grayscale(0) invert(0)}.vp-sponsor-grid-item.empty:hover{background-color:var(--vp-c-bg-soft)}.dark .vp-sponsor-grid-item:hover{background-color:var(--vp-c-white)}.dark .vp-sponsor-grid-item.empty:hover{background-color:var(--vp-c-bg-soft)}.vp-sponsor-grid-link{display:flex}.vp-sponsor-grid-box{display:flex;justify-content:center;align-items:center;width:100%}.vp-sponsor-grid-image{max-width:100%;filter:grayscale(1);transition:filter .25s}.dark .vp-sponsor-grid-image{filter:grayscale(1) invert(1)}.VPBadge{display:inline-block;margin-left:2px;border:1px solid transparent;border-radius:12px;padding:0 10px;line-height:22px;font-size:12px;font-weight:500;transform:translateY(-2px)}.VPBadge.small{padding:0 6px;line-height:18px;font-size:10px;transform:translateY(-8px)}.VPDocFooter .VPBadge{display:none}.vp-doc h1>.VPBadge{margin-top:4px;vertical-align:top}.vp-doc h2>.VPBadge{margin-top:3px;padding:0 8px;vertical-align:top}.vp-doc h3>.VPBadge{vertical-align:middle}.vp-doc h4>.VPBadge,.vp-doc h5>.VPBadge,.vp-doc h6>.VPBadge{vertical-align:middle;line-height:18px}.VPBadge.info{border-color:var(--vp-badge-info-border);color:var(--vp-badge-info-text);background-color:var(--vp-badge-info-bg)}.VPBadge.tip{border-color:var(--vp-badge-tip-border);color:var(--vp-badge-tip-text);background-color:var(--vp-badge-tip-bg)}.VPBadge.warning{border-color:var(--vp-badge-warning-border);color:var(--vp-badge-warning-text);background-color:var(--vp-badge-warning-bg)}.VPBadge.danger{border-color:var(--vp-badge-danger-border);color:var(--vp-badge-danger-text);background-color:var(--vp-badge-danger-bg)}.VPBackdrop[data-v-c79a1216]{position:fixed;top:0;right:0;bottom:0;left:0;z-index:var(--vp-z-index-backdrop);background:var(--vp-backdrop-bg-color);transition:opacity .5s}.VPBackdrop.fade-enter-from[data-v-c79a1216],.VPBackdrop.fade-leave-to[data-v-c79a1216]{opacity:0}.VPBackdrop.fade-leave-active[data-v-c79a1216]{transition-duration:.25s}@media (min-width: 1280px){.VPBackdrop[data-v-c79a1216]{display:none}}.NotFound[data-v-d6be1790]{padding:64px 24px 96px;text-align:center}@media (min-width: 768px){.NotFound[data-v-d6be1790]{padding:96px 32px 168px}}.code[data-v-d6be1790]{line-height:64px;font-size:64px;font-weight:600}.title[data-v-d6be1790]{padding-top:12px;letter-spacing:2px;line-height:20px;font-size:20px;font-weight:700}.divider[data-v-d6be1790]{margin:24px auto 18px;width:64px;height:1px;background-color:var(--vp-c-divider)}.quote[data-v-d6be1790]{margin:0 auto;max-width:256px;font-size:14px;font-weight:500;color:var(--vp-c-text-2)}.action[data-v-d6be1790]{padding-top:20px}.link[data-v-d6be1790]{display:inline-block;border:1px solid var(--vp-c-brand-1);border-radius:16px;padding:3px 16px;font-size:14px;font-weight:500;color:var(--vp-c-brand-1);transition:border-color .25s,color .25s}.link[data-v-d6be1790]:hover{border-color:var(--vp-c-brand-2);color:var(--vp-c-brand-2)}.root[data-v-b933a997]{position:relative;z-index:1}.nested[data-v-b933a997]{padding-right:16px;padding-left:16px}.outline-link[data-v-b933a997]{display:block;line-height:32px;font-size:14px;font-weight:400;color:var(--vp-c-text-2);white-space:nowrap;overflow:hidden;text-overflow:ellipsis;transition:color .5s}.outline-link[data-v-b933a997]:hover,.outline-link.active[data-v-b933a997]{color:var(--vp-c-text-1);transition:color .25s}.outline-link.nested[data-v-b933a997]{padding-left:13px}.VPDocAsideOutline[data-v-a5bbad30]{display:none}.VPDocAsideOutline.has-outline[data-v-a5bbad30]{display:block}.content[data-v-a5bbad30]{position:relative;border-left:1px solid var(--vp-c-divider);padding-left:16px;font-size:13px;font-weight:500}.outline-marker[data-v-a5bbad30]{position:absolute;top:32px;left:-1px;z-index:0;opacity:0;width:2px;border-radius:2px;height:18px;background-color:var(--vp-c-brand-1);transition:top .25s cubic-bezier(0,1,.5,1),background-color .5s,opacity .25s}.outline-title[data-v-a5bbad30]{line-height:32px;font-size:14px;font-weight:600}.VPDocAside[data-v-3f215769]{display:flex;flex-direction:column;flex-grow:1}.spacer[data-v-3f215769]{flex-grow:1}.VPDocAside[data-v-3f215769] .spacer+.VPDocAsideSponsors,.VPDocAside[data-v-3f215769] .spacer+.VPDocAsideCarbonAds{margin-top:24px}.VPDocAside[data-v-3f215769] .VPDocAsideSponsors+.VPDocAsideCarbonAds{margin-top:16px}.VPLastUpdated[data-v-7e05ebdb]{line-height:24px;font-size:14px;font-weight:500;color:var(--vp-c-text-2)}@media (min-width: 640px){.VPLastUpdated[data-v-7e05ebdb]{line-height:32px;font-size:14px;font-weight:500}}.VPDocFooter[data-v-d4a0bba5]{margin-top:64px}.edit-info[data-v-d4a0bba5]{padding-bottom:18px}@media (min-width: 640px){.edit-info[data-v-d4a0bba5]{display:flex;justify-content:space-between;align-items:center;padding-bottom:14px}}.edit-link-button[data-v-d4a0bba5]{display:flex;align-items:center;border:0;line-height:32px;font-size:14px;font-weight:500;color:var(--vp-c-brand-1);transition:color .25s}.edit-link-button[data-v-d4a0bba5]:hover{color:var(--vp-c-brand-2)}.edit-link-icon[data-v-d4a0bba5]{margin-right:8px}.prev-next[data-v-d4a0bba5]{border-top:1px solid var(--vp-c-divider);padding-top:24px;display:grid;grid-row-gap:8px}@media (min-width: 640px){.prev-next[data-v-d4a0bba5]{grid-template-columns:repeat(2,1fr);grid-column-gap:16px}}.pager-link[data-v-d4a0bba5]{display:block;border:1px solid var(--vp-c-divider);border-radius:8px;padding:11px 16px 13px;width:100%;height:100%;transition:border-color .25s}.pager-link[data-v-d4a0bba5]:hover{border-color:var(--vp-c-brand-1)}.pager-link.next[data-v-d4a0bba5]{margin-left:auto;text-align:right}.desc[data-v-d4a0bba5]{display:block;line-height:20px;font-size:12px;font-weight:500;color:var(--vp-c-text-2)}.title[data-v-d4a0bba5]{display:block;line-height:20px;font-size:14px;font-weight:500;color:var(--vp-c-brand-1);transition:color .25s}.VPDoc[data-v-39a288b8]{padding:32px 24px 96px;width:100%}@media (min-width: 768px){.VPDoc[data-v-39a288b8]{padding:48px 32px 128px}}@media (min-width: 960px){.VPDoc[data-v-39a288b8]{padding:48px 32px 0}.VPDoc:not(.has-sidebar) .container[data-v-39a288b8]{display:flex;justify-content:center;max-width:992px}.VPDoc:not(.has-sidebar) .content[data-v-39a288b8]{max-width:752px}}@media (min-width: 1280px){.VPDoc .container[data-v-39a288b8]{display:flex;justify-content:center}.VPDoc .aside[data-v-39a288b8]{display:block}}@media (min-width: 1440px){.VPDoc:not(.has-sidebar) .content[data-v-39a288b8]{max-width:784px}.VPDoc:not(.has-sidebar) .container[data-v-39a288b8]{max-width:1104px}}.container[data-v-39a288b8]{margin:0 auto;width:100%}.aside[data-v-39a288b8]{position:relative;display:none;order:2;flex-grow:1;padding-left:32px;width:100%;max-width:256px}.left-aside[data-v-39a288b8]{order:1;padding-left:unset;padding-right:32px}.aside-container[data-v-39a288b8]{position:fixed;top:0;padding-top:calc(var(--vp-nav-height) + var(--vp-layout-top-height, 0px) + var(--vp-doc-top-height, 0px) + 48px);width:224px;height:100vh;overflow-x:hidden;overflow-y:auto;scrollbar-width:none}.aside-container[data-v-39a288b8]::-webkit-scrollbar{display:none}.aside-curtain[data-v-39a288b8]{position:fixed;bottom:0;z-index:10;width:224px;height:32px;background:linear-gradient(transparent,var(--vp-c-bg) 70%)}.aside-content[data-v-39a288b8]{display:flex;flex-direction:column;min-height:calc(100vh - (var(--vp-nav-height) + var(--vp-layout-top-height, 0px) + 48px));padding-bottom:32px}.content[data-v-39a288b8]{position:relative;margin:0 auto;width:100%}@media (min-width: 960px){.content[data-v-39a288b8]{padding:0 32px 128px}}@media (min-width: 1280px){.content[data-v-39a288b8]{order:1;margin:0;min-width:640px}}.content-container[data-v-39a288b8]{margin:0 auto}.VPDoc.has-aside .content-container[data-v-39a288b8]{max-width:688px}.VPButton[data-v-cad61b99]{display:inline-block;border:1px solid transparent;text-align:center;font-weight:600;white-space:nowrap;transition:color .25s,border-color .25s,background-color .25s}.VPButton[data-v-cad61b99]:active{transition:color .1s,border-color .1s,background-color .1s}.VPButton.medium[data-v-cad61b99]{border-radius:20px;padding:0 20px;line-height:38px;font-size:14px}.VPButton.big[data-v-cad61b99]{border-radius:24px;padding:0 24px;line-height:46px;font-size:16px}.VPButton.brand[data-v-cad61b99]{border-color:var(--vp-button-brand-border);color:var(--vp-button-brand-text);background-color:var(--vp-button-brand-bg)}.VPButton.brand[data-v-cad61b99]:hover{border-color:var(--vp-button-brand-hover-border);color:var(--vp-button-brand-hover-text);background-color:var(--vp-button-brand-hover-bg)}.VPButton.brand[data-v-cad61b99]:active{border-color:var(--vp-button-brand-active-border);color:var(--vp-button-brand-active-text);background-color:var(--vp-button-brand-active-bg)}.VPButton.alt[data-v-cad61b99]{border-color:var(--vp-button-alt-border);color:var(--vp-button-alt-text);background-color:var(--vp-button-alt-bg)}.VPButton.alt[data-v-cad61b99]:hover{border-color:var(--vp-button-alt-hover-border);color:var(--vp-button-alt-hover-text);background-color:var(--vp-button-alt-hover-bg)}.VPButton.alt[data-v-cad61b99]:active{border-color:var(--vp-button-alt-active-border);color:var(--vp-button-alt-active-text);background-color:var(--vp-button-alt-active-bg)}.VPButton.sponsor[data-v-cad61b99]{border-color:var(--vp-button-sponsor-border);color:var(--vp-button-sponsor-text);background-color:var(--vp-button-sponsor-bg)}.VPButton.sponsor[data-v-cad61b99]:hover{border-color:var(--vp-button-sponsor-hover-border);color:var(--vp-button-sponsor-hover-text);background-color:var(--vp-button-sponsor-hover-bg)}.VPButton.sponsor[data-v-cad61b99]:active{border-color:var(--vp-button-sponsor-active-border);color:var(--vp-button-sponsor-active-text);background-color:var(--vp-button-sponsor-active-bg)}html:not(.dark) .VPImage.dark[data-v-8426fc1a]{display:none}.dark .VPImage.light[data-v-8426fc1a]{display:none}.VPHero[data-v-303bb580]{margin-top:calc((var(--vp-nav-height) + var(--vp-layout-top-height, 0px)) * -1);padding:calc(var(--vp-nav-height) + var(--vp-layout-top-height, 0px) + 48px) 24px 48px}@media (min-width: 640px){.VPHero[data-v-303bb580]{padding:calc(var(--vp-nav-height) + var(--vp-layout-top-height, 0px) + 80px) 48px 64px}}@media (min-width: 960px){.VPHero[data-v-303bb580]{padding:calc(var(--vp-nav-height) + var(--vp-layout-top-height, 0px) + 80px) 64px 64px}}.container[data-v-303bb580]{display:flex;flex-direction:column;margin:0 auto;max-width:1152px}@media (min-width: 960px){.container[data-v-303bb580]{flex-direction:row}}.main[data-v-303bb580]{position:relative;z-index:10;order:2;flex-grow:1;flex-shrink:0}.VPHero.has-image .container[data-v-303bb580]{text-align:center}@media (min-width: 960px){.VPHero.has-image .container[data-v-303bb580]{text-align:left}}@media (min-width: 960px){.main[data-v-303bb580]{order:1;width:calc((100% / 3) * 2)}.VPHero.has-image .main[data-v-303bb580]{max-width:592px}}.name[data-v-303bb580],.text[data-v-303bb580]{max-width:392px;letter-spacing:-.4px;line-height:40px;font-size:32px;font-weight:700;white-space:pre-wrap}.VPHero.has-image .name[data-v-303bb580],.VPHero.has-image .text[data-v-303bb580]{margin:0 auto}.name[data-v-303bb580]{color:var(--vp-home-hero-name-color)}.clip[data-v-303bb580]{background:var(--vp-home-hero-name-background);-webkit-background-clip:text;background-clip:text;-webkit-text-fill-color:var(--vp-home-hero-name-color)}@media (min-width: 640px){.name[data-v-303bb580],.text[data-v-303bb580]{max-width:576px;line-height:56px;font-size:48px}}@media (min-width: 960px){.name[data-v-303bb580],.text[data-v-303bb580]{line-height:64px;font-size:56px}.VPHero.has-image .name[data-v-303bb580],.VPHero.has-image .text[data-v-303bb580]{margin:0}}.tagline[data-v-303bb580]{padding-top:8px;max-width:392px;line-height:28px;font-size:18px;font-weight:500;white-space:pre-wrap;color:var(--vp-c-text-2)}.VPHero.has-image .tagline[data-v-303bb580]{margin:0 auto}@media (min-width: 640px){.tagline[data-v-303bb580]{padding-top:12px;max-width:576px;line-height:32px;font-size:20px}}@media (min-width: 960px){.tagline[data-v-303bb580]{line-height:36px;font-size:24px}.VPHero.has-image .tagline[data-v-303bb580]{margin:0}}.actions[data-v-303bb580]{display:flex;flex-wrap:wrap;margin:-6px;padding-top:24px}.VPHero.has-image .actions[data-v-303bb580]{justify-content:center}@media (min-width: 640px){.actions[data-v-303bb580]{padding-top:32px}}@media (min-width: 960px){.VPHero.has-image .actions[data-v-303bb580]{justify-content:flex-start}}.action[data-v-303bb580]{flex-shrink:0;padding:6px}.image[data-v-303bb580]{order:1;margin:-76px -24px -48px}@media (min-width: 640px){.image[data-v-303bb580]{margin:-108px -24px -48px}}@media (min-width: 960px){.image[data-v-303bb580]{flex-grow:1;order:2;margin:0;min-height:100%}}.image-container[data-v-303bb580]{position:relative;margin:0 auto;width:320px;height:320px}@media (min-width: 640px){.image-container[data-v-303bb580]{width:392px;height:392px}}@media (min-width: 960px){.image-container[data-v-303bb580]{display:flex;justify-content:center;align-items:center;width:100%;height:100%;transform:translate(-32px,-32px)}}.image-bg[data-v-303bb580]{position:absolute;top:50%;left:50%;border-radius:50%;width:192px;height:192px;background-image:var(--vp-home-hero-image-background-image);filter:var(--vp-home-hero-image-filter);transform:translate(-50%,-50%)}@media (min-width: 640px){.image-bg[data-v-303bb580]{width:256px;height:256px}}@media (min-width: 960px){.image-bg[data-v-303bb580]{width:320px;height:320px}}[data-v-303bb580] .image-src{position:absolute;top:50%;left:50%;max-width:192px;max-height:192px;transform:translate(-50%,-50%)}@media (min-width: 640px){[data-v-303bb580] .image-src{max-width:256px;max-height:256px}}@media (min-width: 960px){[data-v-303bb580] .image-src{max-width:320px;max-height:320px}}.VPFeature[data-v-a3976bdc]{display:block;border:1px solid var(--vp-c-bg-soft);border-radius:12px;height:100%;background-color:var(--vp-c-bg-soft);transition:border-color .25s,background-color .25s}.VPFeature.link[data-v-a3976bdc]:hover{border-color:var(--vp-c-brand-1)}.box[data-v-a3976bdc]{display:flex;flex-direction:column;padding:24px;height:100%}.box[data-v-a3976bdc]>.VPImage{margin-bottom:20px}.icon[data-v-a3976bdc]{display:flex;justify-content:center;align-items:center;margin-bottom:20px;border-radius:6px;background-color:var(--vp-c-default-soft);width:48px;height:48px;font-size:24px;transition:background-color .25s}.title[data-v-a3976bdc]{line-height:24px;font-size:16px;font-weight:600}.details[data-v-a3976bdc]{flex-grow:1;padding-top:8px;line-height:24px;font-size:14px;font-weight:500;color:var(--vp-c-text-2)}.link-text[data-v-a3976bdc]{padding-top:8px}.link-text-value[data-v-a3976bdc]{display:flex;align-items:center;font-size:14px;font-weight:500;color:var(--vp-c-brand-1)}.link-text-icon[data-v-a3976bdc]{margin-left:6px}.VPFeatures[data-v-a6181336]{position:relative;padding:0 24px}@media (min-width: 640px){.VPFeatures[data-v-a6181336]{padding:0 48px}}@media (min-width: 960px){.VPFeatures[data-v-a6181336]{padding:0 64px}}.container[data-v-a6181336]{margin:0 auto;max-width:1152px}.items[data-v-a6181336]{display:flex;flex-wrap:wrap;margin:-8px}.item[data-v-a6181336]{padding:8px;width:100%}@media (min-width: 640px){.item.grid-2[data-v-a6181336],.item.grid-4[data-v-a6181336],.item.grid-6[data-v-a6181336]{width:50%}}@media (min-width: 768px){.item.grid-2[data-v-a6181336],.item.grid-4[data-v-a6181336]{width:50%}.item.grid-3[data-v-a6181336],.item.grid-6[data-v-a6181336]{width:calc(100% / 3)}}@media (min-width: 960px){.item.grid-4[data-v-a6181336]{width:25%}}.container[data-v-8e2d4988]{margin:auto;width:100%;max-width:1280px;padding:0 24px}@media (min-width: 640px){.container[data-v-8e2d4988]{padding:0 48px}}@media (min-width: 960px){.container[data-v-8e2d4988]{width:100%;padding:0 64px}}.vp-doc[data-v-8e2d4988] .VPHomeSponsors,.vp-doc[data-v-8e2d4988] .VPTeamPage{margin-left:var(--vp-offset, calc(50% - 50vw) );margin-right:var(--vp-offset, calc(50% - 50vw) )}.vp-doc[data-v-8e2d4988] .VPHomeSponsors h2{border-top:none;letter-spacing:normal}.vp-doc[data-v-8e2d4988] .VPHomeSponsors a,.vp-doc[data-v-8e2d4988] .VPTeamPage a{text-decoration:none}.VPHome[data-v-686f80a6]{margin-bottom:96px}@media (min-width: 768px){.VPHome[data-v-686f80a6]{margin-bottom:128px}}.VPContent[data-v-1428d186]{flex-grow:1;flex-shrink:0;margin:var(--vp-layout-top-height, 0px) auto 0;width:100%}.VPContent.is-home[data-v-1428d186]{width:100%;max-width:100%}.VPContent.has-sidebar[data-v-1428d186]{margin:0}@media (min-width: 960px){.VPContent[data-v-1428d186]{padding-top:var(--vp-nav-height)}.VPContent.has-sidebar[data-v-1428d186]{margin:var(--vp-layout-top-height, 0px) 0 0;padding-left:var(--vp-sidebar-width)}}@media (min-width: 1440px){.VPContent.has-sidebar[data-v-1428d186]{padding-right:calc((100vw - var(--vp-layout-max-width)) / 2);padding-left:calc((100vw - var(--vp-layout-max-width)) / 2 + var(--vp-sidebar-width))}}.VPFooter[data-v-e315a0ad]{position:relative;z-index:var(--vp-z-index-footer);border-top:1px solid var(--vp-c-gutter);padding:32px 24px;background-color:var(--vp-c-bg)}.VPFooter.has-sidebar[data-v-e315a0ad]{display:none}.VPFooter[data-v-e315a0ad] a{text-decoration-line:underline;text-underline-offset:2px;transition:color .25s}.VPFooter[data-v-e315a0ad] a:hover{color:var(--vp-c-text-1)}@media (min-width: 768px){.VPFooter[data-v-e315a0ad]{padding:32px}}.container[data-v-e315a0ad]{margin:0 auto;max-width:var(--vp-layout-max-width);text-align:center}.message[data-v-e315a0ad],.copyright[data-v-e315a0ad]{line-height:24px;font-size:14px;font-weight:500;color:var(--vp-c-text-2)}.VPLocalNavOutlineDropdown[data-v-17a5e62e]{padding:12px 20px 11px}@media (min-width: 960px){.VPLocalNavOutlineDropdown[data-v-17a5e62e]{padding:12px 36px 11px}}.VPLocalNavOutlineDropdown button[data-v-17a5e62e]{display:block;font-size:12px;font-weight:500;line-height:24px;color:var(--vp-c-text-2);transition:color .5s;position:relative}.VPLocalNavOutlineDropdown button[data-v-17a5e62e]:hover{color:var(--vp-c-text-1);transition:color .25s}.VPLocalNavOutlineDropdown button.open[data-v-17a5e62e]{color:var(--vp-c-text-1)}.icon[data-v-17a5e62e]{display:inline-block;vertical-align:middle;margin-left:2px;font-size:14px;transform:rotate(0);transition:transform .25s}@media (min-width: 960px){.VPLocalNavOutlineDropdown button[data-v-17a5e62e]{font-size:14px}.icon[data-v-17a5e62e]{font-size:16px}}.open>.icon[data-v-17a5e62e]{transform:rotate(90deg)}.items[data-v-17a5e62e]{position:absolute;top:40px;right:16px;left:16px;display:grid;gap:1px;border:1px solid var(--vp-c-border);border-radius:8px;background-color:var(--vp-c-gutter);max-height:calc(var(--vp-vh, 100vh) - 86px);overflow:hidden auto;box-shadow:var(--vp-shadow-3)}@media (min-width: 960px){.items[data-v-17a5e62e]{right:auto;left:calc(var(--vp-sidebar-width) + 32px);width:320px}}.header[data-v-17a5e62e]{background-color:var(--vp-c-bg-soft)}.top-link[data-v-17a5e62e]{display:block;padding:0 16px;line-height:48px;font-size:14px;font-weight:500;color:var(--vp-c-brand-1)}.outline[data-v-17a5e62e]{padding:8px 0;background-color:var(--vp-c-bg-soft)}.flyout-enter-active[data-v-17a5e62e]{transition:all .2s ease-out}.flyout-leave-active[data-v-17a5e62e]{transition:all .15s ease-in}.flyout-enter-from[data-v-17a5e62e],.flyout-leave-to[data-v-17a5e62e]{opacity:0;transform:translateY(-16px)}.VPLocalNav[data-v-a6f0e41e]{position:sticky;top:0;left:0;z-index:var(--vp-z-index-local-nav);border-bottom:1px solid var(--vp-c-gutter);padding-top:var(--vp-layout-top-height, 0px);width:100%;background-color:var(--vp-local-nav-bg-color)}.VPLocalNav.fixed[data-v-a6f0e41e]{position:fixed}@media (min-width: 960px){.VPLocalNav[data-v-a6f0e41e]{top:var(--vp-nav-height)}.VPLocalNav.has-sidebar[data-v-a6f0e41e]{padding-left:var(--vp-sidebar-width)}.VPLocalNav.empty[data-v-a6f0e41e]{display:none}}@media (min-width: 1280px){.VPLocalNav[data-v-a6f0e41e]{display:none}}@media (min-width: 1440px){.VPLocalNav.has-sidebar[data-v-a6f0e41e]{padding-left:calc((100vw - var(--vp-layout-max-width)) / 2 + var(--vp-sidebar-width))}}.container[data-v-a6f0e41e]{display:flex;justify-content:space-between;align-items:center}.menu[data-v-a6f0e41e]{display:flex;align-items:center;padding:12px 24px 11px;line-height:24px;font-size:12px;font-weight:500;color:var(--vp-c-text-2);transition:color .5s}.menu[data-v-a6f0e41e]:hover{color:var(--vp-c-text-1);transition:color .25s}@media (min-width: 768px){.menu[data-v-a6f0e41e]{padding:0 32px}}@media (min-width: 960px){.menu[data-v-a6f0e41e]{display:none}}.menu-icon[data-v-a6f0e41e]{margin-right:8px;font-size:14px}.VPOutlineDropdown[data-v-a6f0e41e]{padding:12px 24px 11px}@media (min-width: 768px){.VPOutlineDropdown[data-v-a6f0e41e]{padding:12px 32px 11px}}.VPSwitch[data-v-1d5665e3]{position:relative;border-radius:11px;display:block;width:40px;height:22px;flex-shrink:0;border:1px solid var(--vp-input-border-color);background-color:var(--vp-input-switch-bg-color);transition:border-color .25s!important}.VPSwitch[data-v-1d5665e3]:hover{border-color:var(--vp-c-brand-1)}.check[data-v-1d5665e3]{position:absolute;top:1px;left:1px;width:18px;height:18px;border-radius:50%;background-color:var(--vp-c-neutral-inverse);box-shadow:var(--vp-shadow-1);transition:transform .25s!important}.icon[data-v-1d5665e3]{position:relative;display:block;width:18px;height:18px;border-radius:50%;overflow:hidden}.icon[data-v-1d5665e3] [class^=vpi-]{position:absolute;top:3px;left:3px;width:12px;height:12px;color:var(--vp-c-text-2)}.dark .icon[data-v-1d5665e3] [class^=vpi-]{color:var(--vp-c-text-1);transition:opacity .25s!important}.sun[data-v-d1f28634]{opacity:1}.moon[data-v-d1f28634],.dark .sun[data-v-d1f28634]{opacity:0}.dark .moon[data-v-d1f28634]{opacity:1}.dark .VPSwitchAppearance[data-v-d1f28634] .check{transform:translate(18px)}.VPNavBarAppearance[data-v-e6aabb21]{display:none}@media (min-width: 1280px){.VPNavBarAppearance[data-v-e6aabb21]{display:flex;align-items:center}}.VPMenuGroup+.VPMenuLink[data-v-43f1e123]{margin:12px -12px 0;border-top:1px solid var(--vp-c-divider);padding:12px 12px 0}.link[data-v-43f1e123]{display:block;border-radius:6px;padding:0 12px;line-height:32px;font-size:14px;font-weight:500;color:var(--vp-c-text-1);white-space:nowrap;transition:background-color .25s,color .25s}.link[data-v-43f1e123]:hover{color:var(--vp-c-brand-1);background-color:var(--vp-c-default-soft)}.link.active[data-v-43f1e123]{color:var(--vp-c-brand-1)}.VPMenuGroup[data-v-69e747b5]{margin:12px -12px 0;border-top:1px solid var(--vp-c-divider);padding:12px 12px 0}.VPMenuGroup[data-v-69e747b5]:first-child{margin-top:0;border-top:0;padding-top:0}.VPMenuGroup+.VPMenuGroup[data-v-69e747b5]{margin-top:12px;border-top:1px solid var(--vp-c-divider)}.title[data-v-69e747b5]{padding:0 12px;line-height:32px;font-size:14px;font-weight:600;color:var(--vp-c-text-2);white-space:nowrap;transition:color .25s}.VPMenu[data-v-e7ea1737]{border-radius:12px;padding:12px;min-width:128px;border:1px solid var(--vp-c-divider);background-color:var(--vp-c-bg-elv);box-shadow:var(--vp-shadow-3);transition:background-color .5s;max-height:calc(100vh - var(--vp-nav-height));overflow-y:auto}.VPMenu[data-v-e7ea1737] .group{margin:0 -12px;padding:0 12px 12px}.VPMenu[data-v-e7ea1737] .group+.group{border-top:1px solid var(--vp-c-divider);padding:11px 12px 12px}.VPMenu[data-v-e7ea1737] .group:last-child{padding-bottom:0}.VPMenu[data-v-e7ea1737] .group+.item{border-top:1px solid var(--vp-c-divider);padding:11px 16px 0}.VPMenu[data-v-e7ea1737] .item{padding:0 16px;white-space:nowrap}.VPMenu[data-v-e7ea1737] .label{flex-grow:1;line-height:28px;font-size:12px;font-weight:500;color:var(--vp-c-text-2);transition:color .5s}.VPMenu[data-v-e7ea1737] .action{padding-left:24px}.VPFlyout[data-v-b6c34ac9]{position:relative}.VPFlyout[data-v-b6c34ac9]:hover{color:var(--vp-c-brand-1);transition:color .25s}.VPFlyout:hover .text[data-v-b6c34ac9]{color:var(--vp-c-text-2)}.VPFlyout:hover .icon[data-v-b6c34ac9]{fill:var(--vp-c-text-2)}.VPFlyout.active .text[data-v-b6c34ac9]{color:var(--vp-c-brand-1)}.VPFlyout.active:hover .text[data-v-b6c34ac9]{color:var(--vp-c-brand-2)}.VPFlyout:hover .menu[data-v-b6c34ac9],.button[aria-expanded=true]+.menu[data-v-b6c34ac9]{opacity:1;visibility:visible;transform:translateY(0)}.button[aria-expanded=false]+.menu[data-v-b6c34ac9]{opacity:0;visibility:hidden;transform:translateY(0)}.button[data-v-b6c34ac9]{display:flex;align-items:center;padding:0 12px;height:var(--vp-nav-height);color:var(--vp-c-text-1);transition:color .5s}.text[data-v-b6c34ac9]{display:flex;align-items:center;line-height:var(--vp-nav-height);font-size:14px;font-weight:500;color:var(--vp-c-text-1);transition:color .25s}.option-icon[data-v-b6c34ac9]{margin-right:0;font-size:16px}.text-icon[data-v-b6c34ac9]{margin-left:4px;font-size:14px}.icon[data-v-b6c34ac9]{font-size:20px;transition:fill .25s}.menu[data-v-b6c34ac9]{position:absolute;top:calc(var(--vp-nav-height) / 2 + 20px);right:0;opacity:0;visibility:hidden;transition:opacity .25s,visibility .25s,transform .25s}.VPSocialLink[data-v-eee4e7cb]{display:flex;justify-content:center;align-items:center;width:36px;height:36px;color:var(--vp-c-text-2);transition:color .5s}.VPSocialLink[data-v-eee4e7cb]:hover{color:var(--vp-c-text-1);transition:color .25s}.VPSocialLink[data-v-eee4e7cb]>svg,.VPSocialLink[data-v-eee4e7cb]>[class^=vpi-social-]{width:20px;height:20px;fill:currentColor}.VPSocialLinks[data-v-7bc22406]{display:flex;justify-content:center}.VPNavBarExtra[data-v-d0bd9dde]{display:none;margin-right:-12px}@media (min-width: 768px){.VPNavBarExtra[data-v-d0bd9dde]{display:block}}@media (min-width: 1280px){.VPNavBarExtra[data-v-d0bd9dde]{display:none}}.trans-title[data-v-d0bd9dde]{padding:0 24px 0 12px;line-height:32px;font-size:14px;font-weight:700;color:var(--vp-c-text-1)}.item.appearance[data-v-d0bd9dde],.item.social-links[data-v-d0bd9dde]{display:flex;align-items:center;padding:0 12px}.item.appearance[data-v-d0bd9dde]{min-width:176px}.appearance-action[data-v-d0bd9dde]{margin-right:-2px}.social-links-list[data-v-d0bd9dde]{margin:-4px -8px}.VPNavBarHamburger[data-v-e5dd9c1c]{display:flex;justify-content:center;align-items:center;width:48px;height:var(--vp-nav-height)}@media (min-width: 768px){.VPNavBarHamburger[data-v-e5dd9c1c]{display:none}}.container[data-v-e5dd9c1c]{position:relative;width:16px;height:14px;overflow:hidden}.VPNavBarHamburger:hover .top[data-v-e5dd9c1c]{top:0;left:0;transform:translate(4px)}.VPNavBarHamburger:hover .middle[data-v-e5dd9c1c]{top:6px;left:0;transform:translate(0)}.VPNavBarHamburger:hover .bottom[data-v-e5dd9c1c]{top:12px;left:0;transform:translate(8px)}.VPNavBarHamburger.active .top[data-v-e5dd9c1c]{top:6px;transform:translate(0) rotate(225deg)}.VPNavBarHamburger.active .middle[data-v-e5dd9c1c]{top:6px;transform:translate(16px)}.VPNavBarHamburger.active .bottom[data-v-e5dd9c1c]{top:6px;transform:translate(0) rotate(135deg)}.VPNavBarHamburger.active:hover .top[data-v-e5dd9c1c],.VPNavBarHamburger.active:hover .middle[data-v-e5dd9c1c],.VPNavBarHamburger.active:hover .bottom[data-v-e5dd9c1c]{background-color:var(--vp-c-text-2);transition:top .25s,background-color .25s,transform .25s}.top[data-v-e5dd9c1c],.middle[data-v-e5dd9c1c],.bottom[data-v-e5dd9c1c]{position:absolute;width:16px;height:2px;background-color:var(--vp-c-text-1);transition:top .25s,background-color .5s,transform .25s}.top[data-v-e5dd9c1c]{top:0;left:0;transform:translate(0)}.middle[data-v-e5dd9c1c]{top:6px;left:0;transform:translate(8px)}.bottom[data-v-e5dd9c1c]{top:12px;left:0;transform:translate(4px)}.VPNavBarMenuLink[data-v-9c663999]{display:flex;align-items:center;padding:0 12px;line-height:var(--vp-nav-height);font-size:14px;font-weight:500;color:var(--vp-c-text-1);transition:color .25s}.VPNavBarMenuLink.active[data-v-9c663999],.VPNavBarMenuLink[data-v-9c663999]:hover{color:var(--vp-c-brand-1)}.VPNavBarMenu[data-v-7f418b0f]{display:none}@media (min-width: 768px){.VPNavBarMenu[data-v-7f418b0f]{display:flex}}/*! @docsearch/css 3.6.0 | MIT License | © Algolia, Inc. and contributors | https://docsearch.algolia.com */:root{--docsearch-primary-color:#5468ff;--docsearch-text-color:#1c1e21;--docsearch-spacing:12px;--docsearch-icon-stroke-width:1.4;--docsearch-highlight-color:var(--docsearch-primary-color);--docsearch-muted-color:#969faf;--docsearch-container-background:rgba(101,108,133,.8);--docsearch-logo-color:#5468ff;--docsearch-modal-width:560px;--docsearch-modal-height:600px;--docsearch-modal-background:#f5f6f7;--docsearch-modal-shadow:inset 1px 1px 0 0 hsla(0,0%,100%,.5),0 3px 8px 0 #555a64;--docsearch-searchbox-height:56px;--docsearch-searchbox-background:#ebedf0;--docsearch-searchbox-focus-background:#fff;--docsearch-searchbox-shadow:inset 0 0 0 2px var(--docsearch-primary-color);--docsearch-hit-height:56px;--docsearch-hit-color:#444950;--docsearch-hit-active-color:#fff;--docsearch-hit-background:#fff;--docsearch-hit-shadow:0 1px 3px 0 #d4d9e1;--docsearch-key-gradient:linear-gradient(-225deg,#d5dbe4,#f8f8f8);--docsearch-key-shadow:inset 0 -2px 0 0 #cdcde6,inset 0 0 1px 1px #fff,0 1px 2px 1px rgba(30,35,90,.4);--docsearch-key-pressed-shadow:inset 0 -2px 0 0 #cdcde6,inset 0 0 1px 1px #fff,0 1px 1px 0 rgba(30,35,90,.4);--docsearch-footer-height:44px;--docsearch-footer-background:#fff;--docsearch-footer-shadow:0 -1px 0 0 #e0e3e8,0 -3px 6px 0 rgba(69,98,155,.12)}html[data-theme=dark]{--docsearch-text-color:#f5f6f7;--docsearch-container-background:rgba(9,10,17,.8);--docsearch-modal-background:#15172a;--docsearch-modal-shadow:inset 1px 1px 0 0 #2c2e40,0 3px 8px 0 #000309;--docsearch-searchbox-background:#090a11;--docsearch-searchbox-focus-background:#000;--docsearch-hit-color:#bec3c9;--docsearch-hit-shadow:none;--docsearch-hit-background:#090a11;--docsearch-key-gradient:linear-gradient(-26.5deg,#565872,#31355b);--docsearch-key-shadow:inset 0 -2px 0 0 #282d55,inset 0 0 1px 1px #51577d,0 2px 2px 0 rgba(3,4,9,.3);--docsearch-key-pressed-shadow:inset 0 -2px 0 0 #282d55,inset 0 0 1px 1px #51577d,0 1px 1px 0 rgba(3,4,9,.30196078431372547);--docsearch-footer-background:#1e2136;--docsearch-footer-shadow:inset 0 1px 0 0 rgba(73,76,106,.5),0 -4px 8px 0 rgba(0,0,0,.2);--docsearch-logo-color:#fff;--docsearch-muted-color:#7f8497}.DocSearch-Button{align-items:center;background:var(--docsearch-searchbox-background);border:0;border-radius:40px;color:var(--docsearch-muted-color);cursor:pointer;display:flex;font-weight:500;height:36px;justify-content:space-between;margin:0 0 0 16px;padding:0 8px;-webkit-user-select:none;user-select:none}.DocSearch-Button:active,.DocSearch-Button:focus,.DocSearch-Button:hover{background:var(--docsearch-searchbox-focus-background);box-shadow:var(--docsearch-searchbox-shadow);color:var(--docsearch-text-color);outline:none}.DocSearch-Button-Container{align-items:center;display:flex}.DocSearch-Search-Icon{stroke-width:1.6}.DocSearch-Button .DocSearch-Search-Icon{color:var(--docsearch-text-color)}.DocSearch-Button-Placeholder{font-size:1rem;padding:0 12px 0 6px}.DocSearch-Button-Keys{display:flex;min-width:calc(40px + .8em)}.DocSearch-Button-Key{align-items:center;background:var(--docsearch-key-gradient);border-radius:3px;box-shadow:var(--docsearch-key-shadow);color:var(--docsearch-muted-color);display:flex;height:18px;justify-content:center;margin-right:.4em;position:relative;padding:0 0 2px;border:0;top:-1px;width:20px}.DocSearch-Button-Key--pressed{transform:translate3d(0,1px,0);box-shadow:var(--docsearch-key-pressed-shadow)}@media (max-width:768px){.DocSearch-Button-Keys,.DocSearch-Button-Placeholder{display:none}}.DocSearch--active{overflow:hidden!important}.DocSearch-Container,.DocSearch-Container *{box-sizing:border-box}.DocSearch-Container{background-color:var(--docsearch-container-background);height:100vh;left:0;position:fixed;top:0;width:100vw;z-index:200}.DocSearch-Container a{text-decoration:none}.DocSearch-Link{-webkit-appearance:none;-moz-appearance:none;appearance:none;background:none;border:0;color:var(--docsearch-highlight-color);cursor:pointer;font:inherit;margin:0;padding:0}.DocSearch-Modal{background:var(--docsearch-modal-background);border-radius:6px;box-shadow:var(--docsearch-modal-shadow);flex-direction:column;margin:60px auto auto;max-width:var(--docsearch-modal-width);position:relative}.DocSearch-SearchBar{display:flex;padding:var(--docsearch-spacing) var(--docsearch-spacing) 0}.DocSearch-Form{align-items:center;background:var(--docsearch-searchbox-focus-background);border-radius:4px;box-shadow:var(--docsearch-searchbox-shadow);display:flex;height:var(--docsearch-searchbox-height);margin:0;padding:0 var(--docsearch-spacing);position:relative;width:100%}.DocSearch-Input{-webkit-appearance:none;-moz-appearance:none;appearance:none;background:transparent;border:0;color:var(--docsearch-text-color);flex:1;font:inherit;font-size:1.2em;height:100%;outline:none;padding:0 0 0 8px;width:80%}.DocSearch-Input::placeholder{color:var(--docsearch-muted-color);opacity:1}.DocSearch-Input::-webkit-search-cancel-button,.DocSearch-Input::-webkit-search-decoration,.DocSearch-Input::-webkit-search-results-button,.DocSearch-Input::-webkit-search-results-decoration{display:none}.DocSearch-LoadingIndicator,.DocSearch-MagnifierLabel,.DocSearch-Reset{margin:0;padding:0}.DocSearch-MagnifierLabel,.DocSearch-Reset{align-items:center;color:var(--docsearch-highlight-color);display:flex;justify-content:center}.DocSearch-Container--Stalled .DocSearch-MagnifierLabel,.DocSearch-LoadingIndicator{display:none}.DocSearch-Container--Stalled .DocSearch-LoadingIndicator{align-items:center;color:var(--docsearch-highlight-color);display:flex;justify-content:center}@media screen and (prefers-reduced-motion:reduce){.DocSearch-Reset{animation:none;-webkit-appearance:none;-moz-appearance:none;appearance:none;background:none;border:0;border-radius:50%;color:var(--docsearch-icon-color);cursor:pointer;right:0;stroke-width:var(--docsearch-icon-stroke-width)}}.DocSearch-Reset{animation:fade-in .1s ease-in forwards;-webkit-appearance:none;-moz-appearance:none;appearance:none;background:none;border:0;border-radius:50%;color:var(--docsearch-icon-color);cursor:pointer;padding:2px;right:0;stroke-width:var(--docsearch-icon-stroke-width)}.DocSearch-Reset[hidden]{display:none}.DocSearch-Reset:hover{color:var(--docsearch-highlight-color)}.DocSearch-LoadingIndicator svg,.DocSearch-MagnifierLabel svg{height:24px;width:24px}.DocSearch-Cancel{display:none}.DocSearch-Dropdown{max-height:calc(var(--docsearch-modal-height) - var(--docsearch-searchbox-height) - var(--docsearch-spacing) - var(--docsearch-footer-height));min-height:var(--docsearch-spacing);overflow-y:auto;overflow-y:overlay;padding:0 var(--docsearch-spacing);scrollbar-color:var(--docsearch-muted-color) var(--docsearch-modal-background);scrollbar-width:thin}.DocSearch-Dropdown::-webkit-scrollbar{width:12px}.DocSearch-Dropdown::-webkit-scrollbar-track{background:transparent}.DocSearch-Dropdown::-webkit-scrollbar-thumb{background-color:var(--docsearch-muted-color);border:3px solid var(--docsearch-modal-background);border-radius:20px}.DocSearch-Dropdown ul{list-style:none;margin:0;padding:0}.DocSearch-Label{font-size:.75em;line-height:1.6em}.DocSearch-Help,.DocSearch-Label{color:var(--docsearch-muted-color)}.DocSearch-Help{font-size:.9em;margin:0;-webkit-user-select:none;user-select:none}.DocSearch-Title{font-size:1.2em}.DocSearch-Logo a{display:flex}.DocSearch-Logo svg{color:var(--docsearch-logo-color);margin-left:8px}.DocSearch-Hits:last-of-type{margin-bottom:24px}.DocSearch-Hits mark{background:none;color:var(--docsearch-highlight-color)}.DocSearch-HitsFooter{color:var(--docsearch-muted-color);display:flex;font-size:.85em;justify-content:center;margin-bottom:var(--docsearch-spacing);padding:var(--docsearch-spacing)}.DocSearch-HitsFooter a{border-bottom:1px solid;color:inherit}.DocSearch-Hit{border-radius:4px;display:flex;padding-bottom:4px;position:relative}@media screen and (prefers-reduced-motion:reduce){.DocSearch-Hit--deleting{transition:none}}.DocSearch-Hit--deleting{opacity:0;transition:all .25s linear}@media screen and (prefers-reduced-motion:reduce){.DocSearch-Hit--favoriting{transition:none}}.DocSearch-Hit--favoriting{transform:scale(0);transform-origin:top center;transition:all .25s linear;transition-delay:.25s}.DocSearch-Hit a{background:var(--docsearch-hit-background);border-radius:4px;box-shadow:var(--docsearch-hit-shadow);display:block;padding-left:var(--docsearch-spacing);width:100%}.DocSearch-Hit-source{background:var(--docsearch-modal-background);color:var(--docsearch-highlight-color);font-size:.85em;font-weight:600;line-height:32px;margin:0 -4px;padding:8px 4px 0;position:sticky;top:0;z-index:10}.DocSearch-Hit-Tree{color:var(--docsearch-muted-color);height:var(--docsearch-hit-height);opacity:.5;stroke-width:var(--docsearch-icon-stroke-width);width:24px}.DocSearch-Hit[aria-selected=true] a{background-color:var(--docsearch-highlight-color)}.DocSearch-Hit[aria-selected=true] mark{text-decoration:underline}.DocSearch-Hit-Container{align-items:center;color:var(--docsearch-hit-color);display:flex;flex-direction:row;height:var(--docsearch-hit-height);padding:0 var(--docsearch-spacing) 0 0}.DocSearch-Hit-icon{height:20px;width:20px}.DocSearch-Hit-action,.DocSearch-Hit-icon{color:var(--docsearch-muted-color);stroke-width:var(--docsearch-icon-stroke-width)}.DocSearch-Hit-action{align-items:center;display:flex;height:22px;width:22px}.DocSearch-Hit-action svg{display:block;height:18px;width:18px}.DocSearch-Hit-action+.DocSearch-Hit-action{margin-left:6px}.DocSearch-Hit-action-button{-webkit-appearance:none;-moz-appearance:none;appearance:none;background:none;border:0;border-radius:50%;color:inherit;cursor:pointer;padding:2px}svg.DocSearch-Hit-Select-Icon{display:none}.DocSearch-Hit[aria-selected=true] .DocSearch-Hit-Select-Icon{display:block}.DocSearch-Hit-action-button:focus,.DocSearch-Hit-action-button:hover{background:#0003;transition:background-color .1s ease-in}@media screen and (prefers-reduced-motion:reduce){.DocSearch-Hit-action-button:focus,.DocSearch-Hit-action-button:hover{transition:none}}.DocSearch-Hit-action-button:focus path,.DocSearch-Hit-action-button:hover path{fill:#fff}.DocSearch-Hit-content-wrapper{display:flex;flex:1 1 auto;flex-direction:column;font-weight:500;justify-content:center;line-height:1.2em;margin:0 8px;overflow-x:hidden;position:relative;text-overflow:ellipsis;white-space:nowrap;width:80%}.DocSearch-Hit-title{font-size:.9em}.DocSearch-Hit-path{color:var(--docsearch-muted-color);font-size:.75em}.DocSearch-Hit[aria-selected=true] .DocSearch-Hit-action,.DocSearch-Hit[aria-selected=true] .DocSearch-Hit-icon,.DocSearch-Hit[aria-selected=true] .DocSearch-Hit-path,.DocSearch-Hit[aria-selected=true] .DocSearch-Hit-text,.DocSearch-Hit[aria-selected=true] .DocSearch-Hit-title,.DocSearch-Hit[aria-selected=true] .DocSearch-Hit-Tree,.DocSearch-Hit[aria-selected=true] mark{color:var(--docsearch-hit-active-color)!important}@media screen and (prefers-reduced-motion:reduce){.DocSearch-Hit-action-button:focus,.DocSearch-Hit-action-button:hover{background:#0003;transition:none}}.DocSearch-ErrorScreen,.DocSearch-NoResults,.DocSearch-StartScreen{font-size:.9em;margin:0 auto;padding:36px 0;text-align:center;width:80%}.DocSearch-Screen-Icon{color:var(--docsearch-muted-color);padding-bottom:12px}.DocSearch-NoResults-Prefill-List{display:inline-block;padding-bottom:24px;text-align:left}.DocSearch-NoResults-Prefill-List ul{display:inline-block;padding:8px 0 0}.DocSearch-NoResults-Prefill-List li{list-style-position:inside;list-style-type:"» "}.DocSearch-Prefill{-webkit-appearance:none;-moz-appearance:none;appearance:none;background:none;border:0;border-radius:1em;color:var(--docsearch-highlight-color);cursor:pointer;display:inline-block;font-size:1em;font-weight:700;padding:0}.DocSearch-Prefill:focus,.DocSearch-Prefill:hover{outline:none;text-decoration:underline}.DocSearch-Footer{align-items:center;background:var(--docsearch-footer-background);border-radius:0 0 8px 8px;box-shadow:var(--docsearch-footer-shadow);display:flex;flex-direction:row-reverse;flex-shrink:0;height:var(--docsearch-footer-height);justify-content:space-between;padding:0 var(--docsearch-spacing);position:relative;-webkit-user-select:none;user-select:none;width:100%;z-index:300}.DocSearch-Commands{color:var(--docsearch-muted-color);display:flex;list-style:none;margin:0;padding:0}.DocSearch-Commands li{align-items:center;display:flex}.DocSearch-Commands li:not(:last-of-type){margin-right:.8em}.DocSearch-Commands-Key{align-items:center;background:var(--docsearch-key-gradient);border-radius:2px;box-shadow:var(--docsearch-key-shadow);display:flex;height:18px;justify-content:center;margin-right:.4em;padding:0 0 1px;color:var(--docsearch-muted-color);border:0;width:20px}.DocSearch-VisuallyHiddenForAccessibility{clip:rect(0 0 0 0);clip-path:inset(50%);height:1px;overflow:hidden;position:absolute;white-space:nowrap;width:1px}@media (max-width:768px){:root{--docsearch-spacing:10px;--docsearch-footer-height:40px}.DocSearch-Dropdown{height:100%}.DocSearch-Container{height:100vh;height:-webkit-fill-available;height:calc(var(--docsearch-vh, 1vh)*100);position:absolute}.DocSearch-Footer{border-radius:0;bottom:0;position:absolute}.DocSearch-Hit-content-wrapper{display:flex;position:relative;width:80%}.DocSearch-Modal{border-radius:0;box-shadow:none;height:100vh;height:-webkit-fill-available;height:calc(var(--docsearch-vh, 1vh)*100);margin:0;max-width:100%;width:100%}.DocSearch-Dropdown{max-height:calc(var(--docsearch-vh, 1vh)*100 - var(--docsearch-searchbox-height) - var(--docsearch-spacing) - var(--docsearch-footer-height))}.DocSearch-Cancel{-webkit-appearance:none;-moz-appearance:none;appearance:none;background:none;border:0;color:var(--docsearch-highlight-color);cursor:pointer;display:inline-block;flex:none;font:inherit;font-size:1em;font-weight:500;margin-left:var(--docsearch-spacing);outline:none;overflow:hidden;padding:0;-webkit-user-select:none;user-select:none;white-space:nowrap}.DocSearch-Commands,.DocSearch-Hit-Tree{display:none}}@keyframes fade-in{0%{opacity:0}to{opacity:1}}[class*=DocSearch]{--docsearch-primary-color: var(--vp-c-brand-1);--docsearch-highlight-color: var(--docsearch-primary-color);--docsearch-text-color: var(--vp-c-text-1);--docsearch-muted-color: var(--vp-c-text-2);--docsearch-searchbox-shadow: none;--docsearch-searchbox-background: transparent;--docsearch-searchbox-focus-background: transparent;--docsearch-key-gradient: transparent;--docsearch-key-shadow: none;--docsearch-modal-background: var(--vp-c-bg-soft);--docsearch-footer-background: var(--vp-c-bg)}.dark [class*=DocSearch]{--docsearch-modal-shadow: none;--docsearch-footer-shadow: none;--docsearch-logo-color: var(--vp-c-text-2);--docsearch-hit-background: var(--vp-c-default-soft);--docsearch-hit-color: var(--vp-c-text-2);--docsearch-hit-shadow: none}.DocSearch-Button{display:flex;justify-content:center;align-items:center;margin:0;padding:0;width:48px;height:55px;background:transparent;transition:border-color .25s}.DocSearch-Button:hover{background:transparent}.DocSearch-Button:focus{outline:1px dotted;outline:5px auto -webkit-focus-ring-color}.DocSearch-Button-Key--pressed{transform:none;box-shadow:none}.DocSearch-Button:focus:not(:focus-visible){outline:none!important}@media (min-width: 768px){.DocSearch-Button{justify-content:flex-start;border:1px solid transparent;border-radius:8px;padding:0 10px 0 12px;width:100%;height:40px;background-color:var(--vp-c-bg-alt)}.DocSearch-Button:hover{border-color:var(--vp-c-brand-1);background:var(--vp-c-bg-alt)}}.DocSearch-Button .DocSearch-Button-Container{display:flex;align-items:center}.DocSearch-Button .DocSearch-Search-Icon{position:relative;width:16px;height:16px;color:var(--vp-c-text-1);fill:currentColor;transition:color .5s}.DocSearch-Button:hover .DocSearch-Search-Icon{color:var(--vp-c-text-1)}@media (min-width: 768px){.DocSearch-Button .DocSearch-Search-Icon{top:1px;margin-right:8px;width:14px;height:14px;color:var(--vp-c-text-2)}}.DocSearch-Button .DocSearch-Button-Placeholder{display:none;margin-top:2px;padding:0 16px 0 0;font-size:13px;font-weight:500;color:var(--vp-c-text-2);transition:color .5s}.DocSearch-Button:hover .DocSearch-Button-Placeholder{color:var(--vp-c-text-1)}@media (min-width: 768px){.DocSearch-Button .DocSearch-Button-Placeholder{display:inline-block}}.DocSearch-Button .DocSearch-Button-Keys{direction:ltr;display:none;min-width:auto}@media (min-width: 768px){.DocSearch-Button .DocSearch-Button-Keys{display:flex;align-items:center}}.DocSearch-Button .DocSearch-Button-Key{display:block;margin:2px 0 0;border:1px solid var(--vp-c-divider);border-right:none;border-radius:4px 0 0 4px;padding-left:6px;min-width:0;width:auto;height:22px;line-height:22px;font-family:var(--vp-font-family-base);font-size:12px;font-weight:500;transition:color .5s,border-color .5s}.DocSearch-Button .DocSearch-Button-Key+.DocSearch-Button-Key{border-right:1px solid var(--vp-c-divider);border-left:none;border-radius:0 4px 4px 0;padding-left:2px;padding-right:6px}.DocSearch-Button .DocSearch-Button-Key:first-child{font-size:0!important}.DocSearch-Button .DocSearch-Button-Key:first-child:after{content:"Ctrl";font-size:12px;letter-spacing:normal;color:var(--docsearch-muted-color)}.mac .DocSearch-Button .DocSearch-Button-Key:first-child:after{content:"⌘"}.DocSearch-Button .DocSearch-Button-Key:first-child>*{display:none}.DocSearch-Search-Icon{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' stroke-width='1.6' viewBox='0 0 20 20'%3E%3Cpath fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' d='m14.386 14.386 4.088 4.088-4.088-4.088A7.533 7.533 0 1 1 3.733 3.733a7.533 7.533 0 0 1 10.653 10.653z'/%3E%3C/svg%3E")}.VPNavBarSearch{display:flex;align-items:center}@media (min-width: 768px){.VPNavBarSearch{flex-grow:1;padding-left:24px}}@media (min-width: 960px){.VPNavBarSearch{padding-left:32px}}.dark .DocSearch-Footer{border-top:1px solid var(--vp-c-divider)}.DocSearch-Form{border:1px solid var(--vp-c-brand-1);background-color:var(--vp-c-white)}.dark .DocSearch-Form{background-color:var(--vp-c-default-soft)}.DocSearch-Screen-Icon>svg{margin:auto}.VPNavBarSocialLinks[data-v-0394ad82]{display:none}@media (min-width: 1280px){.VPNavBarSocialLinks[data-v-0394ad82]{display:flex;align-items:center}}.title[data-v-ab179fa1]{display:flex;align-items:center;border-bottom:1px solid transparent;width:100%;height:var(--vp-nav-height);font-size:16px;font-weight:600;color:var(--vp-c-text-1);transition:opacity .25s}@media (min-width: 960px){.title[data-v-ab179fa1]{flex-shrink:0}.VPNavBarTitle.has-sidebar .title[data-v-ab179fa1]{border-bottom-color:var(--vp-c-divider)}}[data-v-ab179fa1] .logo{margin-right:8px;height:var(--vp-nav-logo-height)}.VPNavBarTranslations[data-v-88af2de4]{display:none}@media (min-width: 1280px){.VPNavBarTranslations[data-v-88af2de4]{display:flex;align-items:center}}.title[data-v-88af2de4]{padding:0 24px 0 12px;line-height:32px;font-size:14px;font-weight:700;color:var(--vp-c-text-1)}.VPNavBar[data-v-ccf7ddec]{position:relative;height:var(--vp-nav-height);pointer-events:none;white-space:nowrap;transition:background-color .5s}.VPNavBar[data-v-ccf7ddec]:not(.home){background-color:var(--vp-nav-bg-color)}@media (min-width: 960px){.VPNavBar[data-v-ccf7ddec]:not(.home){background-color:transparent}.VPNavBar[data-v-ccf7ddec]:not(.has-sidebar):not(.home.top){background-color:var(--vp-nav-bg-color)}}.wrapper[data-v-ccf7ddec]{padding:0 8px 0 24px}@media (min-width: 768px){.wrapper[data-v-ccf7ddec]{padding:0 32px}}@media (min-width: 960px){.VPNavBar.has-sidebar .wrapper[data-v-ccf7ddec]{padding:0}}.container[data-v-ccf7ddec]{display:flex;justify-content:space-between;margin:0 auto;max-width:calc(var(--vp-layout-max-width) - 64px);height:var(--vp-nav-height);pointer-events:none}.container>.title[data-v-ccf7ddec],.container>.content[data-v-ccf7ddec]{pointer-events:none}.container[data-v-ccf7ddec] *{pointer-events:auto}@media (min-width: 960px){.VPNavBar.has-sidebar .container[data-v-ccf7ddec]{max-width:100%}}.title[data-v-ccf7ddec]{flex-shrink:0;height:calc(var(--vp-nav-height) - 1px);transition:background-color .5s}@media (min-width: 960px){.VPNavBar.has-sidebar .title[data-v-ccf7ddec]{position:absolute;top:0;left:0;z-index:2;padding:0 32px;width:var(--vp-sidebar-width);height:var(--vp-nav-height);background-color:transparent}}@media (min-width: 1440px){.VPNavBar.has-sidebar .title[data-v-ccf7ddec]{padding-left:max(32px,calc((100% - (var(--vp-layout-max-width) - 64px)) / 2));width:calc((100% - (var(--vp-layout-max-width) - 64px)) / 2 + var(--vp-sidebar-width) - 32px)}}.content[data-v-ccf7ddec]{flex-grow:1}@media (min-width: 960px){.VPNavBar.has-sidebar .content[data-v-ccf7ddec]{position:relative;z-index:1;padding-right:32px;padding-left:var(--vp-sidebar-width)}}@media (min-width: 1440px){.VPNavBar.has-sidebar .content[data-v-ccf7ddec]{padding-right:calc((100vw - var(--vp-layout-max-width)) / 2 + 32px);padding-left:calc((100vw - var(--vp-layout-max-width)) / 2 + var(--vp-sidebar-width))}}.content-body[data-v-ccf7ddec]{display:flex;justify-content:flex-end;align-items:center;height:var(--vp-nav-height);transition:background-color .5s}@media (min-width: 960px){.VPNavBar:not(.home.top) .content-body[data-v-ccf7ddec]{position:relative;background-color:var(--vp-nav-bg-color)}.VPNavBar:not(.has-sidebar):not(.home.top) .content-body[data-v-ccf7ddec]{background-color:transparent}}@media (max-width: 767px){.content-body[data-v-ccf7ddec]{column-gap:.5rem}}.menu+.translations[data-v-ccf7ddec]:before,.menu+.appearance[data-v-ccf7ddec]:before,.menu+.social-links[data-v-ccf7ddec]:before,.translations+.appearance[data-v-ccf7ddec]:before,.appearance+.social-links[data-v-ccf7ddec]:before{margin-right:8px;margin-left:8px;width:1px;height:24px;background-color:var(--vp-c-divider);content:""}.menu+.appearance[data-v-ccf7ddec]:before,.translations+.appearance[data-v-ccf7ddec]:before{margin-right:16px}.appearance+.social-links[data-v-ccf7ddec]:before{margin-left:16px}.social-links[data-v-ccf7ddec]{margin-right:-8px}.divider[data-v-ccf7ddec]{width:100%;height:1px}@media (min-width: 960px){.VPNavBar.has-sidebar .divider[data-v-ccf7ddec]{padding-left:var(--vp-sidebar-width)}}@media (min-width: 1440px){.VPNavBar.has-sidebar .divider[data-v-ccf7ddec]{padding-left:calc((100vw - var(--vp-layout-max-width)) / 2 + var(--vp-sidebar-width))}}.divider-line[data-v-ccf7ddec]{width:100%;height:1px;transition:background-color .5s}.VPNavBar:not(.home) .divider-line[data-v-ccf7ddec]{background-color:var(--vp-c-gutter)}@media (min-width: 960px){.VPNavBar:not(.home.top) .divider-line[data-v-ccf7ddec]{background-color:var(--vp-c-gutter)}.VPNavBar:not(.has-sidebar):not(.home.top) .divider[data-v-ccf7ddec]{background-color:var(--vp-c-gutter)}}.VPNavScreenAppearance[data-v-2d7af913]{display:flex;justify-content:space-between;align-items:center;border-radius:8px;padding:12px 14px 12px 16px;background-color:var(--vp-c-bg-soft)}.text[data-v-2d7af913]{line-height:24px;font-size:12px;font-weight:500;color:var(--vp-c-text-2)}.VPNavScreenMenuLink[data-v-7f31e1f6]{display:block;border-bottom:1px solid var(--vp-c-divider);padding:12px 0 11px;line-height:24px;font-size:14px;font-weight:500;color:var(--vp-c-text-1);transition:border-color .25s,color .25s}.VPNavScreenMenuLink[data-v-7f31e1f6]:hover{color:var(--vp-c-brand-1)}.VPNavScreenMenuGroupLink[data-v-19976ae1]{display:block;margin-left:12px;line-height:32px;font-size:14px;font-weight:400;color:var(--vp-c-text-1);transition:color .25s}.VPNavScreenMenuGroupLink[data-v-19976ae1]:hover{color:var(--vp-c-brand-1)}.VPNavScreenMenuGroupSection[data-v-8133b170]{display:block}.title[data-v-8133b170]{line-height:32px;font-size:13px;font-weight:700;color:var(--vp-c-text-2);transition:color .25s}.VPNavScreenMenuGroup[data-v-ff6087d4]{border-bottom:1px solid var(--vp-c-divider);height:48px;overflow:hidden;transition:border-color .5s}.VPNavScreenMenuGroup .items[data-v-ff6087d4]{visibility:hidden}.VPNavScreenMenuGroup.open .items[data-v-ff6087d4]{visibility:visible}.VPNavScreenMenuGroup.open[data-v-ff6087d4]{padding-bottom:10px;height:auto}.VPNavScreenMenuGroup.open .button[data-v-ff6087d4]{padding-bottom:6px;color:var(--vp-c-brand-1)}.VPNavScreenMenuGroup.open .button-icon[data-v-ff6087d4]{transform:rotate(45deg)}.button[data-v-ff6087d4]{display:flex;justify-content:space-between;align-items:center;padding:12px 4px 11px 0;width:100%;line-height:24px;font-size:14px;font-weight:500;color:var(--vp-c-text-1);transition:color .25s}.button[data-v-ff6087d4]:hover{color:var(--vp-c-brand-1)}.button-icon[data-v-ff6087d4]{transition:transform .25s}.group[data-v-ff6087d4]:first-child{padding-top:0}.group+.group[data-v-ff6087d4],.group+.item[data-v-ff6087d4]{padding-top:4px}.VPNavScreenTranslations[data-v-858fe1a4]{height:24px;overflow:hidden}.VPNavScreenTranslations.open[data-v-858fe1a4]{height:auto}.title[data-v-858fe1a4]{display:flex;align-items:center;font-size:14px;font-weight:500;color:var(--vp-c-text-1)}.icon[data-v-858fe1a4]{font-size:16px}.icon.lang[data-v-858fe1a4]{margin-right:8px}.icon.chevron[data-v-858fe1a4]{margin-left:4px}.list[data-v-858fe1a4]{padding:4px 0 0 24px}.link[data-v-858fe1a4]{line-height:32px;font-size:13px;color:var(--vp-c-text-1)}.VPNavScreen[data-v-cc5739dd]{position:fixed;top:calc(var(--vp-nav-height) + var(--vp-layout-top-height, 0px) + 1px);right:0;bottom:0;left:0;padding:0 32px;width:100%;background-color:var(--vp-nav-screen-bg-color);overflow-y:auto;transition:background-color .5s;pointer-events:auto}.VPNavScreen.fade-enter-active[data-v-cc5739dd],.VPNavScreen.fade-leave-active[data-v-cc5739dd]{transition:opacity .25s}.VPNavScreen.fade-enter-active .container[data-v-cc5739dd],.VPNavScreen.fade-leave-active .container[data-v-cc5739dd]{transition:transform .25s ease}.VPNavScreen.fade-enter-from[data-v-cc5739dd],.VPNavScreen.fade-leave-to[data-v-cc5739dd]{opacity:0}.VPNavScreen.fade-enter-from .container[data-v-cc5739dd],.VPNavScreen.fade-leave-to .container[data-v-cc5739dd]{transform:translateY(-8px)}@media (min-width: 768px){.VPNavScreen[data-v-cc5739dd]{display:none}}.container[data-v-cc5739dd]{margin:0 auto;padding:24px 0 96px;max-width:288px}.menu+.translations[data-v-cc5739dd],.menu+.appearance[data-v-cc5739dd],.translations+.appearance[data-v-cc5739dd]{margin-top:24px}.menu+.social-links[data-v-cc5739dd]{margin-top:16px}.appearance+.social-links[data-v-cc5739dd]{margin-top:16px}.VPNav[data-v-ae24b3ad]{position:relative;top:var(--vp-layout-top-height, 0px);left:0;z-index:var(--vp-z-index-nav);width:100%;pointer-events:none;transition:background-color .5s}@media (min-width: 960px){.VPNav[data-v-ae24b3ad]{position:fixed}}.VPSidebarItem.level-0[data-v-b8d55f3b]{padding-bottom:24px}.VPSidebarItem.collapsed.level-0[data-v-b8d55f3b]{padding-bottom:10px}.item[data-v-b8d55f3b]{position:relative;display:flex;width:100%}.VPSidebarItem.collapsible>.item[data-v-b8d55f3b]{cursor:pointer}.indicator[data-v-b8d55f3b]{position:absolute;top:6px;bottom:6px;left:-17px;width:2px;border-radius:2px;transition:background-color .25s}.VPSidebarItem.level-2.is-active>.item>.indicator[data-v-b8d55f3b],.VPSidebarItem.level-3.is-active>.item>.indicator[data-v-b8d55f3b],.VPSidebarItem.level-4.is-active>.item>.indicator[data-v-b8d55f3b],.VPSidebarItem.level-5.is-active>.item>.indicator[data-v-b8d55f3b]{background-color:var(--vp-c-brand-1)}.link[data-v-b8d55f3b]{display:flex;align-items:center;flex-grow:1}.text[data-v-b8d55f3b]{flex-grow:1;padding:4px 0;line-height:24px;font-size:14px;transition:color .25s}.VPSidebarItem.level-0 .text[data-v-b8d55f3b]{font-weight:700;color:var(--vp-c-text-1)}.VPSidebarItem.level-1 .text[data-v-b8d55f3b],.VPSidebarItem.level-2 .text[data-v-b8d55f3b],.VPSidebarItem.level-3 .text[data-v-b8d55f3b],.VPSidebarItem.level-4 .text[data-v-b8d55f3b],.VPSidebarItem.level-5 .text[data-v-b8d55f3b]{font-weight:500;color:var(--vp-c-text-2)}.VPSidebarItem.level-0.is-link>.item>.link:hover .text[data-v-b8d55f3b],.VPSidebarItem.level-1.is-link>.item>.link:hover .text[data-v-b8d55f3b],.VPSidebarItem.level-2.is-link>.item>.link:hover .text[data-v-b8d55f3b],.VPSidebarItem.level-3.is-link>.item>.link:hover .text[data-v-b8d55f3b],.VPSidebarItem.level-4.is-link>.item>.link:hover .text[data-v-b8d55f3b],.VPSidebarItem.level-5.is-link>.item>.link:hover .text[data-v-b8d55f3b]{color:var(--vp-c-brand-1)}.VPSidebarItem.level-0.has-active>.item>.text[data-v-b8d55f3b],.VPSidebarItem.level-1.has-active>.item>.text[data-v-b8d55f3b],.VPSidebarItem.level-2.has-active>.item>.text[data-v-b8d55f3b],.VPSidebarItem.level-3.has-active>.item>.text[data-v-b8d55f3b],.VPSidebarItem.level-4.has-active>.item>.text[data-v-b8d55f3b],.VPSidebarItem.level-5.has-active>.item>.text[data-v-b8d55f3b],.VPSidebarItem.level-0.has-active>.item>.link>.text[data-v-b8d55f3b],.VPSidebarItem.level-1.has-active>.item>.link>.text[data-v-b8d55f3b],.VPSidebarItem.level-2.has-active>.item>.link>.text[data-v-b8d55f3b],.VPSidebarItem.level-3.has-active>.item>.link>.text[data-v-b8d55f3b],.VPSidebarItem.level-4.has-active>.item>.link>.text[data-v-b8d55f3b],.VPSidebarItem.level-5.has-active>.item>.link>.text[data-v-b8d55f3b]{color:var(--vp-c-text-1)}.VPSidebarItem.level-0.is-active>.item .link>.text[data-v-b8d55f3b],.VPSidebarItem.level-1.is-active>.item .link>.text[data-v-b8d55f3b],.VPSidebarItem.level-2.is-active>.item .link>.text[data-v-b8d55f3b],.VPSidebarItem.level-3.is-active>.item .link>.text[data-v-b8d55f3b],.VPSidebarItem.level-4.is-active>.item .link>.text[data-v-b8d55f3b],.VPSidebarItem.level-5.is-active>.item .link>.text[data-v-b8d55f3b]{color:var(--vp-c-brand-1)}.caret[data-v-b8d55f3b]{display:flex;justify-content:center;align-items:center;margin-right:-7px;width:32px;height:32px;color:var(--vp-c-text-3);cursor:pointer;transition:color .25s;flex-shrink:0}.item:hover .caret[data-v-b8d55f3b]{color:var(--vp-c-text-2)}.item:hover .caret[data-v-b8d55f3b]:hover{color:var(--vp-c-text-1)}.caret-icon[data-v-b8d55f3b]{font-size:18px;transform:rotate(90deg);transition:transform .25s}.VPSidebarItem.collapsed .caret-icon[data-v-b8d55f3b]{transform:rotate(0)}.VPSidebarItem.level-1 .items[data-v-b8d55f3b],.VPSidebarItem.level-2 .items[data-v-b8d55f3b],.VPSidebarItem.level-3 .items[data-v-b8d55f3b],.VPSidebarItem.level-4 .items[data-v-b8d55f3b],.VPSidebarItem.level-5 .items[data-v-b8d55f3b]{border-left:1px solid var(--vp-c-divider);padding-left:16px}.VPSidebarItem.collapsed .items[data-v-b8d55f3b]{display:none}.VPSidebar[data-v-575e6a36]{position:fixed;top:var(--vp-layout-top-height, 0px);bottom:0;left:0;z-index:var(--vp-z-index-sidebar);padding:32px 32px 96px;width:calc(100vw - 64px);max-width:320px;background-color:var(--vp-sidebar-bg-color);opacity:0;box-shadow:var(--vp-c-shadow-3);overflow-x:hidden;overflow-y:auto;transform:translate(-100%);transition:opacity .5s,transform .25s ease;overscroll-behavior:contain}.VPSidebar.open[data-v-575e6a36]{opacity:1;visibility:visible;transform:translate(0);transition:opacity .25s,transform .5s cubic-bezier(.19,1,.22,1)}.dark .VPSidebar[data-v-575e6a36]{box-shadow:var(--vp-shadow-1)}@media (min-width: 960px){.VPSidebar[data-v-575e6a36]{padding-top:var(--vp-nav-height);width:var(--vp-sidebar-width);max-width:100%;background-color:var(--vp-sidebar-bg-color);opacity:1;visibility:visible;box-shadow:none;transform:translate(0)}}@media (min-width: 1440px){.VPSidebar[data-v-575e6a36]{padding-left:max(32px,calc((100% - (var(--vp-layout-max-width) - 64px)) / 2));width:calc((100% - (var(--vp-layout-max-width) - 64px)) / 2 + var(--vp-sidebar-width) - 32px)}}@media (min-width: 960px){.curtain[data-v-575e6a36]{position:sticky;top:-64px;left:0;z-index:1;margin-top:calc(var(--vp-nav-height) * -1);margin-right:-32px;margin-left:-32px;height:var(--vp-nav-height);background-color:var(--vp-sidebar-bg-color)}}.nav[data-v-575e6a36]{outline:0}.group+.group[data-v-575e6a36]{border-top:1px solid var(--vp-c-divider);padding-top:10px}@media (min-width: 960px){.group[data-v-575e6a36]{padding-top:10px;width:calc(var(--vp-sidebar-width) - 64px)}}.VPSkipLink[data-v-0f60ec36]{top:8px;left:8px;padding:8px 16px;z-index:999;border-radius:8px;font-size:12px;font-weight:700;text-decoration:none;color:var(--vp-c-brand-1);box-shadow:var(--vp-shadow-3);background-color:var(--vp-c-bg)}.VPSkipLink[data-v-0f60ec36]:focus{height:auto;width:auto;clip:auto;clip-path:none}@media (min-width: 1280px){.VPSkipLink[data-v-0f60ec36]{top:14px;left:16px}}.Layout[data-v-5d98c3a5]{display:flex;flex-direction:column;min-height:100vh}.VPHomeSponsors[data-v-3d121b4a]{border-top:1px solid var(--vp-c-gutter);padding-top:88px!important}.VPHomeSponsors[data-v-3d121b4a]{margin:96px 0}@media (min-width: 768px){.VPHomeSponsors[data-v-3d121b4a]{margin:128px 0}}.VPHomeSponsors[data-v-3d121b4a]{padding:0 24px}@media (min-width: 768px){.VPHomeSponsors[data-v-3d121b4a]{padding:0 48px}}@media (min-width: 960px){.VPHomeSponsors[data-v-3d121b4a]{padding:0 64px}}.container[data-v-3d121b4a]{margin:0 auto;max-width:1152px}.love[data-v-3d121b4a]{margin:0 auto;width:fit-content;font-size:28px;color:var(--vp-c-text-3)}.icon[data-v-3d121b4a]{display:inline-block}.message[data-v-3d121b4a]{margin:0 auto;padding-top:10px;max-width:320px;text-align:center;line-height:24px;font-size:16px;font-weight:500;color:var(--vp-c-text-2)}.sponsors[data-v-3d121b4a]{padding-top:32px}.action[data-v-3d121b4a]{padding-top:40px;text-align:center}.VPTeamPage[data-v-7c57f839]{margin:96px 0}@media (min-width: 768px){.VPTeamPage[data-v-7c57f839]{margin:128px 0}}.VPHome .VPTeamPageTitle[data-v-7c57f839-s]{border-top:1px solid var(--vp-c-gutter);padding-top:88px!important}.VPTeamPageSection+.VPTeamPageSection[data-v-7c57f839-s],.VPTeamMembers+.VPTeamPageSection[data-v-7c57f839-s]{margin-top:64px}.VPTeamMembers+.VPTeamMembers[data-v-7c57f839-s]{margin-top:24px}@media (min-width: 768px){.VPTeamPageTitle+.VPTeamPageSection[data-v-7c57f839-s]{margin-top:16px}.VPTeamPageSection+.VPTeamPageSection[data-v-7c57f839-s],.VPTeamMembers+.VPTeamPageSection[data-v-7c57f839-s]{margin-top:96px}}.VPTeamMembers[data-v-7c57f839-s]{padding:0 24px}@media (min-width: 768px){.VPTeamMembers[data-v-7c57f839-s]{padding:0 48px}}@media (min-width: 960px){.VPTeamMembers[data-v-7c57f839-s]{padding:0 64px}}.VPTeamPageTitle[data-v-bf2cbdac]{padding:48px 32px;text-align:center}@media (min-width: 768px){.VPTeamPageTitle[data-v-bf2cbdac]{padding:64px 48px 48px}}@media (min-width: 960px){.VPTeamPageTitle[data-v-bf2cbdac]{padding:80px 64px 48px}}.title[data-v-bf2cbdac]{letter-spacing:0;line-height:44px;font-size:36px;font-weight:500}@media (min-width: 768px){.title[data-v-bf2cbdac]{letter-spacing:-.5px;line-height:56px;font-size:48px}}.lead[data-v-bf2cbdac]{margin:0 auto;max-width:512px;padding-top:12px;line-height:24px;font-size:16px;font-weight:500;color:var(--vp-c-text-2)}@media (min-width: 768px){.lead[data-v-bf2cbdac]{max-width:592px;letter-spacing:.15px;line-height:28px;font-size:20px}}.VPTeamPageSection[data-v-b1a88750]{padding:0 32px}@media (min-width: 768px){.VPTeamPageSection[data-v-b1a88750]{padding:0 48px}}@media (min-width: 960px){.VPTeamPageSection[data-v-b1a88750]{padding:0 64px}}.title[data-v-b1a88750]{position:relative;margin:0 auto;max-width:1152px;text-align:center;color:var(--vp-c-text-2)}.title-line[data-v-b1a88750]{position:absolute;top:16px;left:0;width:100%;height:1px;background-color:var(--vp-c-divider)}.title-text[data-v-b1a88750]{position:relative;display:inline-block;padding:0 24px;letter-spacing:0;line-height:32px;font-size:20px;font-weight:500;background-color:var(--vp-c-bg)}.lead[data-v-b1a88750]{margin:0 auto;max-width:480px;padding-top:12px;text-align:center;line-height:24px;font-size:16px;font-weight:500;color:var(--vp-c-text-2)}.members[data-v-b1a88750]{padding-top:40px}.VPTeamMembersItem[data-v-f3fa364a]{display:flex;flex-direction:column;gap:2px;border-radius:12px;width:100%;height:100%;overflow:hidden}.VPTeamMembersItem.small .profile[data-v-f3fa364a]{padding:32px}.VPTeamMembersItem.small .data[data-v-f3fa364a]{padding-top:20px}.VPTeamMembersItem.small .avatar[data-v-f3fa364a]{width:64px;height:64px}.VPTeamMembersItem.small .name[data-v-f3fa364a]{line-height:24px;font-size:16px}.VPTeamMembersItem.small .affiliation[data-v-f3fa364a]{padding-top:4px;line-height:20px;font-size:14px}.VPTeamMembersItem.small .desc[data-v-f3fa364a]{padding-top:12px;line-height:20px;font-size:14px}.VPTeamMembersItem.small .links[data-v-f3fa364a]{margin:0 -16px -20px;padding:10px 0 0}.VPTeamMembersItem.medium .profile[data-v-f3fa364a]{padding:48px 32px}.VPTeamMembersItem.medium .data[data-v-f3fa364a]{padding-top:24px;text-align:center}.VPTeamMembersItem.medium .avatar[data-v-f3fa364a]{width:96px;height:96px}.VPTeamMembersItem.medium .name[data-v-f3fa364a]{letter-spacing:.15px;line-height:28px;font-size:20px}.VPTeamMembersItem.medium .affiliation[data-v-f3fa364a]{padding-top:4px;font-size:16px}.VPTeamMembersItem.medium .desc[data-v-f3fa364a]{padding-top:16px;max-width:288px;font-size:16px}.VPTeamMembersItem.medium .links[data-v-f3fa364a]{margin:0 -16px -12px;padding:16px 12px 0}.profile[data-v-f3fa364a]{flex-grow:1;background-color:var(--vp-c-bg-soft)}.data[data-v-f3fa364a]{text-align:center}.avatar[data-v-f3fa364a]{position:relative;flex-shrink:0;margin:0 auto;border-radius:50%;box-shadow:var(--vp-shadow-3)}.avatar-img[data-v-f3fa364a]{position:absolute;top:0;right:0;bottom:0;left:0;border-radius:50%;object-fit:cover}.name[data-v-f3fa364a]{margin:0;font-weight:600}.affiliation[data-v-f3fa364a]{margin:0;font-weight:500;color:var(--vp-c-text-2)}.org.link[data-v-f3fa364a]{color:var(--vp-c-text-2);transition:color .25s}.org.link[data-v-f3fa364a]:hover{color:var(--vp-c-brand-1)}.desc[data-v-f3fa364a]{margin:0 auto}.desc[data-v-f3fa364a] a{font-weight:500;color:var(--vp-c-brand-1);text-decoration-style:dotted;transition:color .25s}.links[data-v-f3fa364a]{display:flex;justify-content:center;height:56px}.sp-link[data-v-f3fa364a]{display:flex;justify-content:center;align-items:center;text-align:center;padding:16px;font-size:14px;font-weight:500;color:var(--vp-c-sponsor);background-color:var(--vp-c-bg-soft);transition:color .25s,background-color .25s}.sp .sp-link.link[data-v-f3fa364a]:hover,.sp .sp-link.link[data-v-f3fa364a]:focus{outline:none;color:var(--vp-c-white);background-color:var(--vp-c-sponsor)}.sp-icon[data-v-f3fa364a]{margin-right:8px;font-size:16px}.VPTeamMembers.small .container[data-v-6cb0dbc4]{grid-template-columns:repeat(auto-fit,minmax(224px,1fr))}.VPTeamMembers.small.count-1 .container[data-v-6cb0dbc4]{max-width:276px}.VPTeamMembers.small.count-2 .container[data-v-6cb0dbc4]{max-width:576px}.VPTeamMembers.small.count-3 .container[data-v-6cb0dbc4]{max-width:876px}.VPTeamMembers.medium .container[data-v-6cb0dbc4]{grid-template-columns:repeat(auto-fit,minmax(256px,1fr))}@media (min-width: 375px){.VPTeamMembers.medium .container[data-v-6cb0dbc4]{grid-template-columns:repeat(auto-fit,minmax(288px,1fr))}}.VPTeamMembers.medium.count-1 .container[data-v-6cb0dbc4]{max-width:368px}.VPTeamMembers.medium.count-2 .container[data-v-6cb0dbc4]{max-width:760px}.container[data-v-6cb0dbc4]{display:grid;gap:24px;margin:0 auto;max-width:1152px}@font-face{font-family:Inter;font-style:normal;font-weight:100 900;font-display:swap;src:url(/assets/inter-roman-cyrillic-ext.BBPuwvHQ.woff2) format("woff2");unicode-range:U+0460-052F,U+1C80-1C88,U+20B4,U+2DE0-2DFF,U+A640-A69F,U+FE2E-FE2F}@font-face{font-family:Inter;font-style:normal;font-weight:100 900;font-display:swap;src:url(/assets/inter-roman-cyrillic.C5lxZ8CY.woff2) format("woff2");unicode-range:U+0301,U+0400-045F,U+0490-0491,U+04B0-04B1,U+2116}@font-face{font-family:Inter;font-style:normal;font-weight:100 900;font-display:swap;src:url(/assets/inter-roman-greek-ext.CqjqNYQ-.woff2) format("woff2");unicode-range:U+1F00-1FFF}@font-face{font-family:Inter;font-style:normal;font-weight:100 900;font-display:swap;src:url(/assets/inter-roman-greek.BBVDIX6e.woff2) format("woff2");unicode-range:U+0370-0377,U+037A-037F,U+0384-038A,U+038C,U+038E-03A1,U+03A3-03FF}@font-face{font-family:Inter;font-style:normal;font-weight:100 900;font-display:swap;src:url(/assets/inter-roman-vietnamese.BjW4sHH5.woff2) format("woff2");unicode-range:U+0102-0103,U+0110-0111,U+0128-0129,U+0168-0169,U+01A0-01A1,U+01AF-01B0,U+0300-0301,U+0303-0304,U+0308-0309,U+0323,U+0329,U+1EA0-1EF9,U+20AB}@font-face{font-family:Inter;font-style:normal;font-weight:100 900;font-display:swap;src:url(/assets/inter-roman-latin-ext.4ZJIpNVo.woff2) format("woff2");unicode-range:U+0100-02AF,U+0304,U+0308,U+0329,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:Inter;font-style:normal;font-weight:100 900;font-display:swap;src:url(/assets/inter-roman-latin.Di8DUHzh.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+2074,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}@font-face{font-family:Inter;font-style:italic;font-weight:100 900;font-display:swap;src:url(/assets/inter-italic-cyrillic-ext.r48I6akx.woff2) format("woff2");unicode-range:U+0460-052F,U+1C80-1C88,U+20B4,U+2DE0-2DFF,U+A640-A69F,U+FE2E-FE2F}@font-face{font-family:Inter;font-style:italic;font-weight:100 900;font-display:swap;src:url(/assets/inter-italic-cyrillic.By2_1cv3.woff2) format("woff2");unicode-range:U+0301,U+0400-045F,U+0490-0491,U+04B0-04B1,U+2116}@font-face{font-family:Inter;font-style:italic;font-weight:100 900;font-display:swap;src:url(/assets/inter-italic-greek-ext.1u6EdAuj.woff2) format("woff2");unicode-range:U+1F00-1FFF}@font-face{font-family:Inter;font-style:italic;font-weight:100 900;font-display:swap;src:url(/assets/inter-italic-greek.DJ8dCoTZ.woff2) format("woff2");unicode-range:U+0370-0377,U+037A-037F,U+0384-038A,U+038C,U+038E-03A1,U+03A3-03FF}@font-face{font-family:Inter;font-style:italic;font-weight:100 900;font-display:swap;src:url(/assets/inter-italic-vietnamese.BSbpV94h.woff2) format("woff2");unicode-range:U+0102-0103,U+0110-0111,U+0128-0129,U+0168-0169,U+01A0-01A1,U+01AF-01B0,U+0300-0301,U+0303-0304,U+0308-0309,U+0323,U+0329,U+1EA0-1EF9,U+20AB}@font-face{font-family:Inter;font-style:italic;font-weight:100 900;font-display:swap;src:url(/assets/inter-italic-latin-ext.CN1xVJS-.woff2) format("woff2");unicode-range:U+0100-02AF,U+0304,U+0308,U+0329,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:Inter;font-style:italic;font-weight:100 900;font-display:swap;src:url(/assets/inter-italic-latin.C2AdPX0b.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+2074,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}@font-face{font-family:Punctuation SC;font-weight:400;src:local("PingFang SC Regular"),local("Noto Sans CJK SC"),local("Microsoft YaHei");unicode-range:U+201C,U+201D,U+2018,U+2019,U+2E3A,U+2014,U+2013,U+2026,U+00B7,U+007E,U+002F}@font-face{font-family:Punctuation SC;font-weight:500;src:local("PingFang SC Medium"),local("Noto Sans CJK SC"),local("Microsoft YaHei");unicode-range:U+201C,U+201D,U+2018,U+2019,U+2E3A,U+2014,U+2013,U+2026,U+00B7,U+007E,U+002F}@font-face{font-family:Punctuation SC;font-weight:600;src:local("PingFang SC Semibold"),local("Noto Sans CJK SC Bold"),local("Microsoft YaHei Bold");unicode-range:U+201C,U+201D,U+2018,U+2019,U+2E3A,U+2014,U+2013,U+2026,U+00B7,U+007E,U+002F}@font-face{font-family:Punctuation SC;font-weight:700;src:local("PingFang SC Semibold"),local("Noto Sans CJK SC Bold"),local("Microsoft YaHei Bold");unicode-range:U+201C,U+201D,U+2018,U+2019,U+2E3A,U+2014,U+2013,U+2026,U+00B7,U+007E,U+002F}:root{--vp-nolebase-highlight-targeted-heading-color: var(--vp-custom-block-tip-text);--vp-nolebase-highlight-targeted-heading-bg: var(--vp-custom-block-tip-bg)}@keyframes vp-nolebase-highlight-targeted-heading-animation{0%{background-color:transparent;box-shadow:0 0 0 8px transparent}10%,35%{color:var(--vp-nolebase-highlight-targeted-heading-color);border-color:transparent;border-radius:4px;background-color:var(--vp-nolebase-highlight-targeted-heading-bg);box-shadow:0 0 0 8px var(--vp-nolebase-highlight-targeted-heading-bg)}99%{background-color:transparent;border-radius:4px;box-shadow:0 0 0 8px transparent}to{border-radius:0;background-color:transparent;box-shadow:none}}.VPNolebaseHighlightTargetedHeadingAnimated{animation:vp-nolebase-highlight-targeted-heading-animation 1.5s ease-in-out}*,:before,:after{--un-rotate:0;--un-rotate-x:0;--un-rotate-y:0;--un-rotate-z:0;--un-scale-x:1;--un-scale-y:1;--un-scale-z:1;--un-skew-x:0;--un-skew-y:0;--un-translate-x:0;--un-translate-y:0;--un-translate-z:0;--un-pan-x: ;--un-pan-y: ;--un-pinch-zoom: ;--un-scroll-snap-strictness:proximity;--un-ordinal: ;--un-slashed-zero: ;--un-numeric-figure: ;--un-numeric-spacing: ;--un-numeric-fraction: ;--un-border-spacing-x:0;--un-border-spacing-y:0;--un-ring-offset-shadow:0 0 rgb(0 0 0 / 0);--un-ring-shadow:0 0 rgb(0 0 0 / 0);--un-shadow-inset: ;--un-shadow:0 0 rgb(0 0 0 / 0);--un-ring-inset: ;--un-ring-offset-width:0px;--un-ring-offset-color:#fff;--un-ring-width:0px;--un-ring-color:rgb(147 197 253 / .5);--un-blur: ;--un-brightness: ;--un-contrast: ;--un-drop-shadow: ;--un-grayscale: ;--un-hue-rotate: ;--un-invert: ;--un-saturate: ;--un-sepia: ;--un-backdrop-blur: ;--un-backdrop-brightness: ;--un-backdrop-contrast: ;--un-backdrop-grayscale: ;--un-backdrop-hue-rotate: ;--un-backdrop-invert: ;--un-backdrop-opacity: ;--un-backdrop-saturate: ;--un-backdrop-sepia: }::backdrop{--un-rotate:0;--un-rotate-x:0;--un-rotate-y:0;--un-rotate-z:0;--un-scale-x:1;--un-scale-y:1;--un-scale-z:1;--un-skew-x:0;--un-skew-y:0;--un-translate-x:0;--un-translate-y:0;--un-translate-z:0;--un-pan-x: ;--un-pan-y: ;--un-pinch-zoom: ;--un-scroll-snap-strictness:proximity;--un-ordinal: ;--un-slashed-zero: ;--un-numeric-figure: ;--un-numeric-spacing: ;--un-numeric-fraction: ;--un-border-spacing-x:0;--un-border-spacing-y:0;--un-ring-offset-shadow:0 0 rgb(0 0 0 / 0);--un-ring-shadow:0 0 rgb(0 0 0 / 0);--un-shadow-inset: ;--un-shadow:0 0 rgb(0 0 0 / 0);--un-ring-inset: ;--un-ring-offset-width:0px;--un-ring-offset-color:#fff;--un-ring-width:0px;--un-ring-color:rgb(147 197 253 / .5);--un-blur: ;--un-brightness: ;--un-contrast: ;--un-drop-shadow: ;--un-grayscale: ;--un-hue-rotate: ;--un-invert: ;--un-saturate: ;--un-sepia: ;--un-backdrop-blur: ;--un-backdrop-brightness: ;--un-backdrop-contrast: ;--un-backdrop-grayscale: ;--un-backdrop-hue-rotate: ;--un-backdrop-invert: ;--un-backdrop-opacity: ;--un-backdrop-saturate: ;--un-backdrop-sepia: }@font-face{font-family:"Baloo 2";font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/baloo2/v21/wXK0E3kTposypRydzVT08TS3JnAmtdgazZpp_led7Q.woff2) format("woff2");unicode-range:U+0900-097F,U+1CD0-1CF9,U+200C-200D,U+20A8,U+20B9,U+20F0,U+25CC,U+A830-A839,U+A8E0-A8FF,U+11B00-11B09}@font-face{font-family:"Baloo 2";font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/baloo2/v21/wXK0E3kTposypRydzVT08TS3JnAmtdgazZpn_led7Q.woff2) format("woff2");unicode-range:U+0102-0103,U+0110-0111,U+0128-0129,U+0168-0169,U+01A0-01A1,U+01AF-01B0,U+0300-0301,U+0303-0304,U+0308-0309,U+0323,U+0329,U+1EA0-1EF9,U+20AB}@font-face{font-family:"Baloo 2";font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/baloo2/v21/wXK0E3kTposypRydzVT08TS3JnAmtdgazZpm_led7Q.woff2) format("woff2");unicode-range:U+0100-02AF,U+0304,U+0308,U+0329,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:"Baloo 2";font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/baloo2/v21/wXK0E3kTposypRydzVT08TS3JnAmtdgazZpo_lc.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+2074,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}@font-face{font-family:Chakra Petch;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/chakrapetch/v11/cIf6MapbsEk7TDLdtEz1BwkWi6pgeL4.woff2) format("woff2");unicode-range:U+0E01-0E5B,U+200C-200D,U+25CC}@font-face{font-family:Chakra Petch;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/chakrapetch/v11/cIf6MapbsEk7TDLdtEz1BwkWkKpgeL4.woff2) format("woff2");unicode-range:U+0102-0103,U+0110-0111,U+0128-0129,U+0168-0169,U+01A0-01A1,U+01AF-01B0,U+0300-0301,U+0303-0304,U+0308-0309,U+0323,U+0329,U+1EA0-1EF9,U+20AB}@font-face{font-family:Chakra Petch;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/chakrapetch/v11/cIf6MapbsEk7TDLdtEz1BwkWkapgeL4.woff2) format("woff2");unicode-range:U+0100-02AF,U+0304,U+0308,U+0329,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:Chakra Petch;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/chakrapetch/v11/cIf6MapbsEk7TDLdtEz1BwkWn6pg.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+2074,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}@font-face{font-family:Jura;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/jura/v31/z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZurR_ibHw.woff2) format("woff2");unicode-range:U+0460-052F,U+1C80-1C88,U+20B4,U+2DE0-2DFF,U+A640-A69F,U+FE2E-FE2F}@font-face{font-family:Jura;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/jura/v31/z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZuiR_ibHw.woff2) format("woff2");unicode-range:U+0301,U+0400-045F,U+0490-0491,U+04B0-04B1,U+2116}@font-face{font-family:Jura;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/jura/v31/z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZuqR_ibHw.woff2) format("woff2");unicode-range:U+1F00-1FFF}@font-face{font-family:Jura;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/jura/v31/z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZulR_ibHw.woff2) format("woff2");unicode-range:U+0370-0377,U+037A-037F,U+0384-038A,U+038C,U+038E-03A1,U+03A3-03FF}@font-face{font-family:Jura;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/jura/v31/z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZvuR_ibHw.woff2) format("woff2");unicode-range:U+200C-200D,U+2010,U+25CC,U+A900-A92F}@font-face{font-family:Jura;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/jura/v31/z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZupR_ibHw.woff2) format("woff2");unicode-range:U+0102-0103,U+0110-0111,U+0128-0129,U+0168-0169,U+01A0-01A1,U+01AF-01B0,U+0300-0301,U+0303-0304,U+0308-0309,U+0323,U+0329,U+1EA0-1EF9,U+20AB}@font-face{font-family:Jura;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/jura/v31/z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZuoR_ibHw.woff2) format("woff2");unicode-range:U+0100-02AF,U+0304,U+0308,U+0329,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:Jura;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/jura/v31/z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZumR_g.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+2074,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}@font-face{font-family:Noto Sans;font-style:normal;font-weight:400;font-stretch:normal;font-display:swap;src:url(https://fonts.gstatic.com/s/notosans/v36/o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9X6VLKzA.woff2) format("woff2");unicode-range:U+0460-052F,U+1C80-1C88,U+20B4,U+2DE0-2DFF,U+A640-A69F,U+FE2E-FE2F}@font-face{font-family:Noto Sans;font-style:normal;font-weight:400;font-stretch:normal;font-display:swap;src:url(https://fonts.gstatic.com/s/notosans/v36/o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9e6VLKzA.woff2) format("woff2");unicode-range:U+0301,U+0400-045F,U+0490-0491,U+04B0-04B1,U+2116}@font-face{font-family:Noto Sans;font-style:normal;font-weight:400;font-stretch:normal;font-display:swap;src:url(https://fonts.gstatic.com/s/notosans/v36/o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9b6VLKzA.woff2) format("woff2");unicode-range:U+0900-097F,U+1CD0-1CF9,U+200C-200D,U+20A8,U+20B9,U+20F0,U+25CC,U+A830-A839,U+A8E0-A8FF,U+11B00-11B09}@font-face{font-family:Noto Sans;font-style:normal;font-weight:400;font-stretch:normal;font-display:swap;src:url(https://fonts.gstatic.com/s/notosans/v36/o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9W6VLKzA.woff2) format("woff2");unicode-range:U+1F00-1FFF}@font-face{font-family:Noto Sans;font-style:normal;font-weight:400;font-stretch:normal;font-display:swap;src:url(https://fonts.gstatic.com/s/notosans/v36/o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9Z6VLKzA.woff2) format("woff2");unicode-range:U+0370-0377,U+037A-037F,U+0384-038A,U+038C,U+038E-03A1,U+03A3-03FF}@font-face{font-family:Noto Sans;font-style:normal;font-weight:400;font-stretch:normal;font-display:swap;src:url(https://fonts.gstatic.com/s/notosans/v36/o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9V6VLKzA.woff2) format("woff2");unicode-range:U+0102-0103,U+0110-0111,U+0128-0129,U+0168-0169,U+01A0-01A1,U+01AF-01B0,U+0300-0301,U+0303-0304,U+0308-0309,U+0323,U+0329,U+1EA0-1EF9,U+20AB}@font-face{font-family:Noto Sans;font-style:normal;font-weight:400;font-stretch:normal;font-display:swap;src:url(https://fonts.gstatic.com/s/notosans/v36/o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9U6VLKzA.woff2) format("woff2");unicode-range:U+0100-02AF,U+0304,U+0308,U+0329,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:Noto Sans;font-style:normal;font-weight:400;font-stretch:normal;font-display:swap;src:url(https://fonts.gstatic.com/s/notosans/v36/o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6VI.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+2074,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}@font-face{font-family:Roboto;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu72xKOzY.woff2) format("woff2");unicode-range:U+0460-052F,U+1C80-1C88,U+20B4,U+2DE0-2DFF,U+A640-A69F,U+FE2E-FE2F}@font-face{font-family:Roboto;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu5mxKOzY.woff2) format("woff2");unicode-range:U+0301,U+0400-045F,U+0490-0491,U+04B0-04B1,U+2116}@font-face{font-family:Roboto;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu7mxKOzY.woff2) format("woff2");unicode-range:U+1F00-1FFF}@font-face{font-family:Roboto;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4WxKOzY.woff2) format("woff2");unicode-range:U+0370-0377,U+037A-037F,U+0384-038A,U+038C,U+038E-03A1,U+03A3-03FF}@font-face{font-family:Roboto;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu7WxKOzY.woff2) format("woff2");unicode-range:U+0102-0103,U+0110-0111,U+0128-0129,U+0168-0169,U+01A0-01A1,U+01AF-01B0,U+0300-0301,U+0303-0304,U+0308-0309,U+0323,U+0329,U+1EA0-1EF9,U+20AB}@font-face{font-family:Roboto;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu7GxKOzY.woff2) format("woff2");unicode-range:U+0100-02AF,U+0304,U+0308,U+0329,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:Roboto;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxK.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+2074,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}.ease-in-out{transition-timing-function:cubic-bezier(.4,0,.2,1)}html{overflow-x:hidden}:root{--vp-c-bg: #3B4252;--vp-c-bg-elv: #434C5E;--vp-font-family-base: Itim;--vp-font-family-mono: Roboto Mono;--vp-layout-max-width: 1080px;--vp-nav-height: 48px}footer{color:var(--vp-c-default-1)}footer a[href^=http]:after{color:var(--vp-c-border)!important}.title{justify-content:center;border:none!important;position:unset!important;padding:0!important;width:unset!important}.title span{font-size:x-large}.search{padding-left:0;display:flex;flex-grow:0!important;padding-left:unset!important}.DocSearch-Button{margin:auto;width:unset;border:none!important}.DocSearch-Button-Placeholder{margin-top:unset!important;padding:unset!important;font-size:unset!important;font-weight:unset!important;color:unset!important;margin-right:8px}.VPNavBarMenu{align-items:flex-end}.VPNavBarMenuLink{line-height:unset!important;font-size:unset!important;font-weight:unset!important;color:unset!important}ul>li>ul{position:relative}ul>li>ul:before{position:absolute;content:"";width:2px;background:var(--vp-c-text-1);opacity:.3;left:-16px;top:8px;bottom:8px}.aside{display:none!important}.img-container{padding:15px;position:relative;height:11lh;width:fit-content;margin:auto}.img-container img{clip-path:polygon(18px 0%,100% 0,100% calc(100% - 18px),calc(100% - 18px) 100%,0 100%,0% 18px);height:100%;object-fit:contain;background:#fff}.img-container:after,.img-container:before{content:"";display:block;position:absolute;border:50px solid transparent;transform:rotate(135deg)}.img-container:after{bottom:-60px;right:-65px;box-shadow:0 7px 6px -9px #000}.img-container:before{top:-60px;left:-65px;box-shadow:0 -7px 6px -9px #000}.VPDoc{padding:0 32px!important}.vp-doc a:not(.u-uid){color:unset;text-decoration:unset;font-weight:unset;text-underline-offset:unset;margin:0 -.4em;padding:.1em .4em;border-radius:.8em .3em;background:transparent;background-image:linear-gradient(to right,#ffe1000d,#ffe10059 4%,#ffe10026);-webkit-box-decoration-break:clone;box-decoration-break:clone}.vp-doc a:not(.u-uid):hover{color:unset;background-image:linear-gradient(to right,#ffe1001a,#ffe100b3 4%,#ffe1004d)}.vp-doc a[href^=http]:after{content:"";display:inline-block;margin-top:-1px;margin-left:4px;width:11px;height:11px;background:currentColor;color:var(--vp-c-text-3);flex-shrink:0;--icon: url("data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' %3E%3Cpath d='M0 0h24v24H0V0z' fill='none' /%3E%3Cpath d='M9 5v2h6.59L4 18.59 5.41 20 17 8.41V15h2V5H9z' /%3E%3C/svg%3E");-webkit-mask-image:var(--icon);mask-image:var(--icon)}.VPNav{left:96px!important;right:32px!important;width:unset!important;position:absolute!important;overflow:hidden}.wrapper{padding:0!important}.VPNavBar{background-color:unset!important}.VPNav .container{align-items:flex-end}.VPNav .content{padding:0!important}.VPNav .content-body{height:unset!important;align-items:flex-end!important;column-gap:unset!important}.VPNavBarHamburger{width:unset!important}.title{height:unset!important}a.title,.VPNavBarMenuLink,.VPNavBarSocialLinks a,.DocSearch-Button,.VPNav button{height:36px!important;border-radius:10px 10px 0 0;padding:8px 8px 16px!important;margin-bottom:-8px!important}.VPNav a:hover,.DocSearch-Button:hover,.VPNav button:hover{margin-bottom:unset!important}a.title{background-color:#0ff}.DocSearch-Button{background-color:#ff0!important}.VPNav .VPNavBarMenuLink[href="https://moddingtree.com"]{background-color:#0f0}.VPNav .VPNavBarMenuLink[href="https://incremental.social"]{background:#f0f}.VPNav button{background:red}.VPNav .VPNavBarSocialLinks [href="https://code.incremental.social/thepaperpilot"]{background:#f70}.VPNav .VPNavBarSocialLinks [href="https://matrix.to/#/@thepaperpilot:incremental.social"]{background:#3c9a3c}.VPNav .VPNavBarSocialLinks [href="https://incremental.social/u/thepaperpilot"]{background:#a75aff}.VPNav .divider{display:none!important}.VPSocialLinks{align-items:flex-end!important;margin-right:0!important}.VPSocialLinks:before{display:none}.VPNavBarExtra{display:none!important}.VPNavBarSocialLinks{display:flex!important}.VPNavScreenSocialLinks a,.VPNavScreenMenuLink,.VPNavScreenMenuLink:after{color:var(--vp-c-bg-alt)!important}@media (max-width: 500px){.VPNavBarSocialLinks{display:none!important}}@media (min-width: 501px){.VPNavScreenSocialLinks{display:none!important}}@media (max-width: 400px){.title span{width:60px}.title span:before{content:"Home ."}}.VPContent{padding-top:0!important;margin-top:var(--vp-nav-height)!important;padding-right:calc((100vw - var(--vp-layout-max-width)) / 2)!important;padding-left:calc((100vw - var(--vp-layout-max-width)) / 2)!important}@media (min-width: 960px){.VPNav{right:calc(max(0px,(100vw - var(--vp-layout-max-width)) / 2) + 32px)!important;left:calc(max(-15px,(100vw - var(--vp-layout-max-width)) / 2 + var(--vp-sidebar-width)) + 32px)!important}.VPContent{padding-left:calc((100vw - var(--vp-layout-max-width)) / 2 + var(--vp-sidebar-width))!important}}.vp-doc .header-anchor{margin-left:calc(-1em - 23px)}.vp-doc :not(h1)>.header-anchor{top:24px}.VPSidebar{opacity:1!important;transition:.5s ease-out!important;box-shadow:0 0 10px 1px #0003!important}.VPLocalNav{position:fixed!important;border-bottom:none!important;background-color:unset!important;pointer-events:none}.VPLocalNav .container{align-items:flex-start!important;flex-direction:column!important}.VPLocalNav>.container>*{pointer-events:all}.VPLocalNav .menu{background:#7afcff;box-shadow:0 0 5px 1px #0003;margin-top:10px;height:30px;width:90px;padding:0 0 0 8px!important}.VPLocalNav button:not(.menu){background:#ff7eb9;padding:4px 30px 4px 8px;box-shadow:0 0 5px 1px #0003}.VPLocalNavOutlineDropdown{padding:0!important;margin-top:10px}.VPLocalNavOutlineDropdown button{padding:0!important;width:90px;height:30px}.curtain{display:none}@media (max-width: 840px){.DocSearch-Button-Keys{display:none!important}}@media (max-width: 959px){.VPSidebar{margin-left:-1000px!important;padding:30px 30px 30px 1030px!important;box-sizing:content-box;background:linear-gradient(to bottom,var(--vp-sidebar-bg-color) 29px,var(--vp-c-divider) 1px);background-size:100% 30px;line-height:30px;width:calc(100vw - 128px)}}.aside-curtain{display:none!important}@media (min-width: 960px){.VPSidebar{transform:rotate(1.4deg)!important;top:1em!important;bottom:unset!important;--vp-sidebar-width: 250px !important;background:#feff9c!important;padding:30px!important;width:var(--vp-sidebar-width)!important;margin-left:max(-15px,calc((100% - (var(--vp-layout-max-width) - 60px)) / 2))!important;max-height:40vh;transition-duration:0s!important}.VPLocalNavOutlineDropdown{display:none}.VPDoc .aside{display:block!important;transform:rotate(1.4deg)!important;position:fixed;top:calc(40vh + 2em);left:0;--vp-sidebar-width: 250px !important;background:#feff9c!important;width:var(--vp-sidebar-width)!important;padding:0!important;margin-left:max(-15px,calc((100% - (var(--vp-layout-max-width) - 60px)) / 2))!important;max-height:40vh;overflow-y:auto}.VPDoc .aside-container{position:unset!important;height:unset!important;overflow:unset!important;padding-top:unset!important;width:unset!important}.VPDoc .aside-content{min-height:unset!important;padding:0!important}.VPDoc .aside-content .content{padding:30px!important}.outline-title{font-size:14px;font-weight:700!important;line-height:30px!important}.VPDoc .aside ul>li>ul:before{display:none}}.VPContent .container{background:linear-gradient(to bottom,var(--vp-sidebar-bg-color) 29px,var(--vp-c-divider) 1px);background-size:100% 30px;line-height:30px;box-shadow:0 0 10px 1px #0003!important}.VPContent .content{padding:0 30px!important}.content-container{border-left:double 7px var(--vp-c-divider);padding:30px 0 30px 8px;max-width:unset!important}article{padding-top:30px}.vp-doc .h-feed article{padding-top:0!important}.vp-doc h2+.e-content{margin-top:0!important}.VPDoc h1,.VPDoc h2,.VPDoc h3,.VPDoc h4,.VPDoc h5,.VPDoc h6{margin:0!important;padding:0!important;line-height:30px!important}.VPDoc h1+p{margin-top:0!important}.VPDoc h2,.VPDoc h3,.VPDoc h4,.VPDoc h5,.VPDoc h6{margin-top:-3px!important;padding-top:23px!important;border-top-style:solid!important;border-top-width:10px!important;border-image:url(/button.svg) 10 10 10 10 stretch stretch!important}ul{margin:0!important}li+li{margin:0!important}.VPDoc p{padding:0!important;margin:30px 0!important;line-height:30px!important}blockquote{margin:30px 0!important}blockquote:first-child,blockquote:first-child p{margin-top:0!important}.VPDoc :has(+hr),.VPDoc :has(+h2),.VPDoc :has(+h3),.VPDoc :has(+h4),.VPDoc :has(+h5),.VPDoc :has(+h6),.VPDoc :has(+ul){margin-bottom:0!important}hr{margin-top:-3px!important;margin-bottom:-7px!important;border-top-style:solid!important;border-top-width:10px!important;border-image:url(/button.svg) 10 10 10 10 stretch stretch!important;height:0px!important}.text{line-height:30px!important;padding:0!important;margin:0!important}.group{padding-top:0!important}.group+.group{border-top-style:solid!important;border-top-width:10px!important;border-image:url(/button.svg) 10 10 10 10 stretch stretch!important;padding-top:23px!important;margin-top:-3px!important}table{margin:30px 0!important}#app .vp-doc tr{background-color:var(--vp-c-gray-2)}#app .vp-doc tr:nth-child(2n){background-color:var(--vp-c-bg-soft)}#app .vp-doc th,#app .vp-doc td{font-size:unset!important;font-weight:unset!important;color:unset!important;padding:0 8px!important;line-height:29px}.VPSidebarItem{padding-bottom:0!important}p:last-child{margin-bottom:0!important}.hero{width:60%;margin:auto}footer img{height:1lh;display:inline;border-radius:50%;margin:0 .25em;vertical-align:bottom}@property --anim-bg{syntax: ""; initial-value: transparent; inherits: false;}@keyframes vp-nolebase-highlight-targeted-heading-animation{0%{--anim-bg: transparent}10%,35%{--anim-bg: var(--vp-c-brand-soft)}99%{--anim-bg: transparent}to{--anim-bg: transparent}}.VPNolebaseHighlightTargetedHeadingAnimated{animation:vp-nolebase-highlight-targeted-heading-animation 1.5s ease-in-out;background:linear-gradient(0deg,var(--anim-bg) 55%,transparent 45%) repeat-x}footer[data-v-25629fb0]{padding:2em;z-index:26;position:relative;font-size:small;background:var(--vp-c-bg-elv)}.VPLocalSearchBox[data-v-639d7ab9]{position:fixed;z-index:100;top:0;right:0;bottom:0;left:0;display:flex}.backdrop[data-v-639d7ab9]{position:absolute;top:0;right:0;bottom:0;left:0;background:var(--vp-backdrop-bg-color);transition:opacity .5s}.shell[data-v-639d7ab9]{position:relative;padding:12px;margin:64px auto;display:flex;flex-direction:column;gap:16px;background:var(--vp-local-search-bg);width:min(100vw - 60px,900px);height:min-content;max-height:min(100vh - 128px,900px);border-radius:6px}@media (max-width: 767px){.shell[data-v-639d7ab9]{margin:0;width:100vw;height:100vh;max-height:none;border-radius:0}}.search-bar[data-v-639d7ab9]{border:1px solid var(--vp-c-divider);border-radius:4px;display:flex;align-items:center;padding:0 12px;cursor:text}@media (max-width: 767px){.search-bar[data-v-639d7ab9]{padding:0 8px}}.search-bar[data-v-639d7ab9]:focus-within{border-color:var(--vp-c-brand-1)}.local-search-icon[data-v-639d7ab9]{display:block;font-size:18px}.navigate-icon[data-v-639d7ab9]{display:block;font-size:14px}.search-icon[data-v-639d7ab9]{margin:8px}@media (max-width: 767px){.search-icon[data-v-639d7ab9]{display:none}}.search-input[data-v-639d7ab9]{padding:6px 12px;font-size:inherit;width:100%}@media (max-width: 767px){.search-input[data-v-639d7ab9]{padding:6px 4px}}.search-actions[data-v-639d7ab9]{display:flex;gap:4px}@media (any-pointer: coarse){.search-actions[data-v-639d7ab9]{gap:8px}}@media (min-width: 769px){.search-actions.before[data-v-639d7ab9]{display:none}}.search-actions button[data-v-639d7ab9]{padding:8px}.search-actions button[data-v-639d7ab9]:not([disabled]):hover,.toggle-layout-button.detailed-list[data-v-639d7ab9]{color:var(--vp-c-brand-1)}.search-actions button.clear-button[data-v-639d7ab9]:disabled{opacity:.37}.search-keyboard-shortcuts[data-v-639d7ab9]{font-size:.8rem;opacity:75%;display:flex;flex-wrap:wrap;gap:16px;line-height:14px}.search-keyboard-shortcuts span[data-v-639d7ab9]{display:flex;align-items:center;gap:4px}@media (max-width: 767px){.search-keyboard-shortcuts[data-v-639d7ab9]{display:none}}.search-keyboard-shortcuts kbd[data-v-639d7ab9]{background:#8080801a;border-radius:4px;padding:3px 6px;min-width:24px;display:inline-block;text-align:center;vertical-align:middle;border:1px solid rgba(128,128,128,.15);box-shadow:0 2px 2px #0000001a}.results[data-v-639d7ab9]{display:flex;flex-direction:column;gap:6px;overflow-x:hidden;overflow-y:auto;overscroll-behavior:contain}.result[data-v-639d7ab9]{display:flex;align-items:center;gap:8px;border-radius:4px;transition:none;line-height:1rem;border:solid 2px var(--vp-local-search-result-border);outline:none}.result>div[data-v-639d7ab9]{margin:12px;width:100%;overflow:hidden}@media (max-width: 767px){.result>div[data-v-639d7ab9]{margin:8px}}.titles[data-v-639d7ab9]{display:flex;flex-wrap:wrap;gap:4px;position:relative;z-index:1001;padding:2px 0}.title[data-v-639d7ab9]{display:flex;align-items:center;gap:4px}.title.main[data-v-639d7ab9]{font-weight:500}.title-icon[data-v-639d7ab9]{opacity:.5;font-weight:500;color:var(--vp-c-brand-1)}.title svg[data-v-639d7ab9]{opacity:.5}.result.selected[data-v-639d7ab9]{--vp-local-search-result-bg: var(--vp-local-search-result-selected-bg);border-color:var(--vp-local-search-result-selected-border)}.excerpt-wrapper[data-v-639d7ab9]{position:relative}.excerpt[data-v-639d7ab9]{opacity:75%;pointer-events:none;max-height:140px;overflow:hidden;position:relative;opacity:.5;margin-top:4px}.result.selected .excerpt[data-v-639d7ab9]{opacity:1}.excerpt[data-v-639d7ab9] *{font-size:.8rem!important;line-height:130%!important}.titles[data-v-639d7ab9] mark,.excerpt[data-v-639d7ab9] mark{background-color:var(--vp-local-search-highlight-bg);color:var(--vp-local-search-highlight-text);border-radius:2px;padding:0 2px}.excerpt[data-v-639d7ab9] .vp-code-group .tabs{display:none}.excerpt[data-v-639d7ab9] .vp-code-group div[class*=language-]{border-radius:8px!important}.excerpt-gradient-bottom[data-v-639d7ab9]{position:absolute;bottom:-1px;left:0;width:100%;height:8px;background:linear-gradient(transparent,var(--vp-local-search-result-bg));z-index:1000}.excerpt-gradient-top[data-v-639d7ab9]{position:absolute;top:-1px;left:0;width:100%;height:8px;background:linear-gradient(var(--vp-local-search-result-bg),transparent);z-index:1000}.result.selected .titles[data-v-639d7ab9],.result.selected .title-icon[data-v-639d7ab9]{color:var(--vp-c-brand-1)!important}.no-results[data-v-639d7ab9]{font-size:.9rem;text-align:center;padding:12px}svg[data-v-639d7ab9]{flex:none} +:root{--vp-c-white: #ffffff;--vp-c-black: #000000;--vp-c-neutral: var(--vp-c-black);--vp-c-neutral-inverse: var(--vp-c-white)}.dark{--vp-c-neutral: var(--vp-c-white);--vp-c-neutral-inverse: var(--vp-c-black)}:root{--vp-c-gray-1: #dddde3;--vp-c-gray-2: #e4e4e9;--vp-c-gray-3: #ebebef;--vp-c-gray-soft: rgba(142, 150, 170, .14);--vp-c-indigo-1: #3451b2;--vp-c-indigo-2: #3a5ccc;--vp-c-indigo-3: #5672cd;--vp-c-indigo-soft: rgba(100, 108, 255, .14);--vp-c-purple-1: #6f42c1;--vp-c-purple-2: #7e4cc9;--vp-c-purple-3: #8e5cd9;--vp-c-purple-soft: rgba(159, 122, 234, .14);--vp-c-green-1: #18794e;--vp-c-green-2: #299764;--vp-c-green-3: #30a46c;--vp-c-green-soft: rgba(16, 185, 129, .14);--vp-c-yellow-1: #915930;--vp-c-yellow-2: #946300;--vp-c-yellow-3: #9f6a00;--vp-c-yellow-soft: rgba(234, 179, 8, .14);--vp-c-red-1: #b8272c;--vp-c-red-2: #d5393e;--vp-c-red-3: #e0575b;--vp-c-red-soft: rgba(244, 63, 94, .14);--vp-c-sponsor: #db2777}.dark{--vp-c-gray-1: #515c67;--vp-c-gray-2: #414853;--vp-c-gray-3: #32363f;--vp-c-gray-soft: rgba(101, 117, 133, .16);--vp-c-indigo-1: #a8b1ff;--vp-c-indigo-2: #5c73e7;--vp-c-indigo-3: #3e63dd;--vp-c-indigo-soft: rgba(100, 108, 255, .16);--vp-c-purple-1: #c8abfa;--vp-c-purple-2: #a879e6;--vp-c-purple-3: #8e5cd9;--vp-c-purple-soft: rgba(159, 122, 234, .16);--vp-c-green-1: #3dd68c;--vp-c-green-2: #30a46c;--vp-c-green-3: #298459;--vp-c-green-soft: rgba(16, 185, 129, .16);--vp-c-yellow-1: #f9b44e;--vp-c-yellow-2: #da8b17;--vp-c-yellow-3: #a46a0a;--vp-c-yellow-soft: rgba(234, 179, 8, .16);--vp-c-red-1: #f66f81;--vp-c-red-2: #f14158;--vp-c-red-3: #b62a3c;--vp-c-red-soft: rgba(244, 63, 94, .16)}:root{--vp-c-bg: #ffffff;--vp-c-bg-alt: #f6f6f7;--vp-c-bg-elv: #ffffff;--vp-c-bg-soft: #f6f6f7}.dark{--vp-c-bg: #1b1b1f;--vp-c-bg-alt: #161618;--vp-c-bg-elv: #202127;--vp-c-bg-soft: #202127}:root{--vp-c-border: #c2c2c4;--vp-c-divider: #e2e2e3;--vp-c-gutter: #e2e2e3}.dark{--vp-c-border: #3c3f44;--vp-c-divider: #2e2e32;--vp-c-gutter: #000000}:root{--vp-c-text-1: rgba(60, 60, 67);--vp-c-text-2: rgba(60, 60, 67, .78);--vp-c-text-3: rgba(60, 60, 67, .56)}.dark{--vp-c-text-1: rgba(255, 255, 245, .86);--vp-c-text-2: rgba(235, 235, 245, .6);--vp-c-text-3: rgba(235, 235, 245, .38)}:root{--vp-c-default-1: var(--vp-c-gray-1);--vp-c-default-2: var(--vp-c-gray-2);--vp-c-default-3: var(--vp-c-gray-3);--vp-c-default-soft: var(--vp-c-gray-soft);--vp-c-brand-1: var(--vp-c-indigo-1);--vp-c-brand-2: var(--vp-c-indigo-2);--vp-c-brand-3: var(--vp-c-indigo-3);--vp-c-brand-soft: var(--vp-c-indigo-soft);--vp-c-brand: var(--vp-c-brand-1);--vp-c-tip-1: var(--vp-c-brand-1);--vp-c-tip-2: var(--vp-c-brand-2);--vp-c-tip-3: var(--vp-c-brand-3);--vp-c-tip-soft: var(--vp-c-brand-soft);--vp-c-note-1: var(--vp-c-brand-1);--vp-c-note-2: var(--vp-c-brand-2);--vp-c-note-3: var(--vp-c-brand-3);--vp-c-note-soft: var(--vp-c-brand-soft);--vp-c-success-1: var(--vp-c-green-1);--vp-c-success-2: var(--vp-c-green-2);--vp-c-success-3: var(--vp-c-green-3);--vp-c-success-soft: var(--vp-c-green-soft);--vp-c-important-1: var(--vp-c-purple-1);--vp-c-important-2: var(--vp-c-purple-2);--vp-c-important-3: var(--vp-c-purple-3);--vp-c-important-soft: var(--vp-c-purple-soft);--vp-c-warning-1: var(--vp-c-yellow-1);--vp-c-warning-2: var(--vp-c-yellow-2);--vp-c-warning-3: var(--vp-c-yellow-3);--vp-c-warning-soft: var(--vp-c-yellow-soft);--vp-c-danger-1: var(--vp-c-red-1);--vp-c-danger-2: var(--vp-c-red-2);--vp-c-danger-3: var(--vp-c-red-3);--vp-c-danger-soft: var(--vp-c-red-soft);--vp-c-caution-1: var(--vp-c-red-1);--vp-c-caution-2: var(--vp-c-red-2);--vp-c-caution-3: var(--vp-c-red-3);--vp-c-caution-soft: var(--vp-c-red-soft)}:root{--vp-font-family-base: "Inter", ui-sans-serif, system-ui, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Noto Color Emoji";--vp-font-family-mono: ui-monospace, "Menlo", "Monaco", "Consolas", "Liberation Mono", "Courier New", monospace;font-optical-sizing:auto}:root:where(:lang(zh)){--vp-font-family-base: "Punctuation SC", "Inter", ui-sans-serif, system-ui, "PingFang SC", "Noto Sans CJK SC", "Noto Sans SC", "Heiti SC", "Microsoft YaHei", "DengXian", sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Noto Color Emoji"}:root{--vp-shadow-1: 0 1px 2px rgba(0, 0, 0, .04), 0 1px 2px rgba(0, 0, 0, .06);--vp-shadow-2: 0 3px 12px rgba(0, 0, 0, .07), 0 1px 4px rgba(0, 0, 0, .07);--vp-shadow-3: 0 12px 32px rgba(0, 0, 0, .1), 0 2px 6px rgba(0, 0, 0, .08);--vp-shadow-4: 0 14px 44px rgba(0, 0, 0, .12), 0 3px 9px rgba(0, 0, 0, .12);--vp-shadow-5: 0 18px 56px rgba(0, 0, 0, .16), 0 4px 12px rgba(0, 0, 0, .16)}:root{--vp-z-index-footer: 10;--vp-z-index-local-nav: 20;--vp-z-index-nav: 30;--vp-z-index-layout-top: 40;--vp-z-index-backdrop: 50;--vp-z-index-sidebar: 60}@media (min-width: 960px){:root{--vp-z-index-sidebar: 25}}:root{--vp-layout-max-width: 1440px}:root{--vp-header-anchor-symbol: "#"}:root{--vp-code-line-height: 1.7;--vp-code-font-size: .875em;--vp-code-color: var(--vp-c-brand-1);--vp-code-link-color: var(--vp-c-brand-1);--vp-code-link-hover-color: var(--vp-c-brand-2);--vp-code-bg: var(--vp-c-default-soft);--vp-code-block-color: var(--vp-c-text-2);--vp-code-block-bg: var(--vp-c-bg-alt);--vp-code-block-divider-color: var(--vp-c-gutter);--vp-code-lang-color: var(--vp-c-text-3);--vp-code-line-highlight-color: var(--vp-c-default-soft);--vp-code-line-number-color: var(--vp-c-text-3);--vp-code-line-diff-add-color: var(--vp-c-success-soft);--vp-code-line-diff-add-symbol-color: var(--vp-c-success-1);--vp-code-line-diff-remove-color: var(--vp-c-danger-soft);--vp-code-line-diff-remove-symbol-color: var(--vp-c-danger-1);--vp-code-line-warning-color: var(--vp-c-warning-soft);--vp-code-line-error-color: var(--vp-c-danger-soft);--vp-code-copy-code-border-color: var(--vp-c-divider);--vp-code-copy-code-bg: var(--vp-c-bg-soft);--vp-code-copy-code-hover-border-color: var(--vp-c-divider);--vp-code-copy-code-hover-bg: var(--vp-c-bg);--vp-code-copy-code-active-text: var(--vp-c-text-2);--vp-code-copy-copied-text-content: "Copied";--vp-code-tab-divider: var(--vp-code-block-divider-color);--vp-code-tab-text-color: var(--vp-c-text-2);--vp-code-tab-bg: var(--vp-code-block-bg);--vp-code-tab-hover-text-color: var(--vp-c-text-1);--vp-code-tab-active-text-color: var(--vp-c-text-1);--vp-code-tab-active-bar-color: var(--vp-c-brand-1)}:root{--vp-button-brand-border: transparent;--vp-button-brand-text: var(--vp-c-white);--vp-button-brand-bg: var(--vp-c-brand-3);--vp-button-brand-hover-border: transparent;--vp-button-brand-hover-text: var(--vp-c-white);--vp-button-brand-hover-bg: var(--vp-c-brand-2);--vp-button-brand-active-border: transparent;--vp-button-brand-active-text: var(--vp-c-white);--vp-button-brand-active-bg: var(--vp-c-brand-1);--vp-button-alt-border: transparent;--vp-button-alt-text: var(--vp-c-text-1);--vp-button-alt-bg: var(--vp-c-default-3);--vp-button-alt-hover-border: transparent;--vp-button-alt-hover-text: var(--vp-c-text-1);--vp-button-alt-hover-bg: var(--vp-c-default-2);--vp-button-alt-active-border: transparent;--vp-button-alt-active-text: var(--vp-c-text-1);--vp-button-alt-active-bg: var(--vp-c-default-1);--vp-button-sponsor-border: var(--vp-c-text-2);--vp-button-sponsor-text: var(--vp-c-text-2);--vp-button-sponsor-bg: transparent;--vp-button-sponsor-hover-border: var(--vp-c-sponsor);--vp-button-sponsor-hover-text: var(--vp-c-sponsor);--vp-button-sponsor-hover-bg: transparent;--vp-button-sponsor-active-border: var(--vp-c-sponsor);--vp-button-sponsor-active-text: var(--vp-c-sponsor);--vp-button-sponsor-active-bg: transparent}:root{--vp-custom-block-font-size: 14px;--vp-custom-block-code-font-size: 13px;--vp-custom-block-info-border: transparent;--vp-custom-block-info-text: var(--vp-c-text-1);--vp-custom-block-info-bg: var(--vp-c-default-soft);--vp-custom-block-info-code-bg: var(--vp-c-default-soft);--vp-custom-block-note-border: transparent;--vp-custom-block-note-text: var(--vp-c-text-1);--vp-custom-block-note-bg: var(--vp-c-default-soft);--vp-custom-block-note-code-bg: var(--vp-c-default-soft);--vp-custom-block-tip-border: transparent;--vp-custom-block-tip-text: var(--vp-c-text-1);--vp-custom-block-tip-bg: var(--vp-c-tip-soft);--vp-custom-block-tip-code-bg: var(--vp-c-tip-soft);--vp-custom-block-important-border: transparent;--vp-custom-block-important-text: var(--vp-c-text-1);--vp-custom-block-important-bg: var(--vp-c-important-soft);--vp-custom-block-important-code-bg: var(--vp-c-important-soft);--vp-custom-block-warning-border: transparent;--vp-custom-block-warning-text: var(--vp-c-text-1);--vp-custom-block-warning-bg: var(--vp-c-warning-soft);--vp-custom-block-warning-code-bg: var(--vp-c-warning-soft);--vp-custom-block-danger-border: transparent;--vp-custom-block-danger-text: var(--vp-c-text-1);--vp-custom-block-danger-bg: var(--vp-c-danger-soft);--vp-custom-block-danger-code-bg: var(--vp-c-danger-soft);--vp-custom-block-caution-border: transparent;--vp-custom-block-caution-text: var(--vp-c-text-1);--vp-custom-block-caution-bg: var(--vp-c-caution-soft);--vp-custom-block-caution-code-bg: var(--vp-c-caution-soft);--vp-custom-block-details-border: var(--vp-custom-block-info-border);--vp-custom-block-details-text: var(--vp-custom-block-info-text);--vp-custom-block-details-bg: var(--vp-custom-block-info-bg);--vp-custom-block-details-code-bg: var(--vp-custom-block-info-code-bg)}:root{--vp-input-border-color: var(--vp-c-border);--vp-input-bg-color: var(--vp-c-bg-alt);--vp-input-switch-bg-color: var(--vp-c-default-soft)}:root{--vp-nav-height: 64px;--vp-nav-bg-color: var(--vp-c-bg);--vp-nav-screen-bg-color: var(--vp-c-bg);--vp-nav-logo-height: 24px}.hide-nav{--vp-nav-height: 0px}.hide-nav .VPSidebar{--vp-nav-height: 22px}:root{--vp-local-nav-bg-color: var(--vp-c-bg)}:root{--vp-sidebar-width: 272px;--vp-sidebar-bg-color: var(--vp-c-bg-alt)}:root{--vp-backdrop-bg-color: rgba(0, 0, 0, .6)}:root{--vp-home-hero-name-color: var(--vp-c-brand-1);--vp-home-hero-name-background: transparent;--vp-home-hero-image-background-image: none;--vp-home-hero-image-filter: none}:root{--vp-badge-info-border: transparent;--vp-badge-info-text: var(--vp-c-text-2);--vp-badge-info-bg: var(--vp-c-default-soft);--vp-badge-tip-border: transparent;--vp-badge-tip-text: var(--vp-c-tip-1);--vp-badge-tip-bg: var(--vp-c-tip-soft);--vp-badge-warning-border: transparent;--vp-badge-warning-text: var(--vp-c-warning-1);--vp-badge-warning-bg: var(--vp-c-warning-soft);--vp-badge-danger-border: transparent;--vp-badge-danger-text: var(--vp-c-danger-1);--vp-badge-danger-bg: var(--vp-c-danger-soft)}:root{--vp-carbon-ads-text-color: var(--vp-c-text-1);--vp-carbon-ads-poweredby-color: var(--vp-c-text-2);--vp-carbon-ads-bg-color: var(--vp-c-bg-soft);--vp-carbon-ads-hover-text-color: var(--vp-c-brand-1);--vp-carbon-ads-hover-poweredby-color: var(--vp-c-text-1)}:root{--vp-local-search-bg: var(--vp-c-bg);--vp-local-search-result-bg: var(--vp-c-bg);--vp-local-search-result-border: var(--vp-c-divider);--vp-local-search-result-selected-bg: var(--vp-c-bg);--vp-local-search-result-selected-border: var(--vp-c-brand-1);--vp-local-search-highlight-bg: var(--vp-c-brand-1);--vp-local-search-highlight-text: var(--vp-c-neutral-inverse)}@media (prefers-reduced-motion: reduce){*,:before,:after{animation-delay:-1ms!important;animation-duration:1ms!important;animation-iteration-count:1!important;background-attachment:initial!important;scroll-behavior:auto!important;transition-duration:0s!important;transition-delay:0s!important}}*,:before,:after{box-sizing:border-box}html{line-height:1.4;font-size:16px;-webkit-text-size-adjust:100%}html.dark{color-scheme:dark}body{margin:0;width:100%;min-width:320px;min-height:100vh;line-height:24px;font-family:var(--vp-font-family-base);font-size:16px;font-weight:400;color:var(--vp-c-text-1);background-color:var(--vp-c-bg);font-synthesis:style;text-rendering:optimizeLegibility;-webkit-font-smoothing:antialiased;-moz-osx-font-smoothing:grayscale}main{display:block}h1,h2,h3,h4,h5,h6{margin:0;line-height:24px;font-size:16px;font-weight:400}p{margin:0}strong,b{font-weight:600}a,area,button,[role=button],input,label,select,summary,textarea{touch-action:manipulation}a{color:inherit;text-decoration:inherit}ol,ul{list-style:none;margin:0;padding:0}blockquote{margin:0}pre,code,kbd,samp{font-family:var(--vp-font-family-mono)}img,svg,video,canvas,audio,iframe,embed,object{display:block}figure{margin:0}img,video{max-width:100%;height:auto}button,input,optgroup,select,textarea{border:0;padding:0;line-height:inherit;color:inherit}button{padding:0;font-family:inherit;background-color:transparent;background-image:none}button:enabled,[role=button]:enabled{cursor:pointer}button:focus,button:focus-visible{outline:1px dotted;outline:4px auto -webkit-focus-ring-color}button:focus:not(:focus-visible){outline:none!important}input:focus,textarea:focus,select:focus{outline:none}table{border-collapse:collapse}input{background-color:transparent}input:-ms-input-placeholder,textarea:-ms-input-placeholder{color:var(--vp-c-text-3)}input::-ms-input-placeholder,textarea::-ms-input-placeholder{color:var(--vp-c-text-3)}input::placeholder,textarea::placeholder{color:var(--vp-c-text-3)}input::-webkit-outer-spin-button,input::-webkit-inner-spin-button{-webkit-appearance:none;margin:0}input[type=number]{-moz-appearance:textfield}textarea{resize:vertical}select{-webkit-appearance:none}fieldset{margin:0;padding:0}h1,h2,h3,h4,h5,h6,li,p{overflow-wrap:break-word}vite-error-overlay{z-index:9999}mjx-container{display:inline-block;margin:auto 2px -2px}mjx-container>svg{display:inline-block;margin:auto}[class^=vpi-],[class*=" vpi-"],.vp-icon{width:1em;height:1em}[class^=vpi-].bg,[class*=" vpi-"].bg,.vp-icon.bg{background-size:100% 100%;background-color:transparent}[class^=vpi-]:not(.bg),[class*=" vpi-"]:not(.bg),.vp-icon:not(.bg){-webkit-mask:var(--icon) no-repeat;mask:var(--icon) no-repeat;-webkit-mask-size:100% 100%;mask-size:100% 100%;background-color:currentColor;color:inherit}.vpi-align-left{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='M21 6H3M15 12H3M17 18H3'/%3E%3C/svg%3E")}.vpi-arrow-right,.vpi-arrow-down,.vpi-arrow-left,.vpi-arrow-up{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='M5 12h14M12 5l7 7-7 7'/%3E%3C/svg%3E")}.vpi-chevron-right,.vpi-chevron-down,.vpi-chevron-left,.vpi-chevron-up{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='m9 18 6-6-6-6'/%3E%3C/svg%3E")}.vpi-chevron-down,.vpi-arrow-down{transform:rotate(90deg)}.vpi-chevron-left,.vpi-arrow-left{transform:rotate(180deg)}.vpi-chevron-up,.vpi-arrow-up{transform:rotate(-90deg)}.vpi-square-pen{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='M12 3H5a2 2 0 0 0-2 2v14a2 2 0 0 0 2 2h14a2 2 0 0 0 2-2v-7'/%3E%3Cpath d='M18.375 2.625a2.121 2.121 0 1 1 3 3L12 15l-4 1 1-4Z'/%3E%3C/svg%3E")}.vpi-plus{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='M5 12h14M12 5v14'/%3E%3C/svg%3E")}.vpi-sun{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Ccircle cx='12' cy='12' r='4'/%3E%3Cpath d='M12 2v2M12 20v2M4.93 4.93l1.41 1.41M17.66 17.66l1.41 1.41M2 12h2M20 12h2M6.34 17.66l-1.41 1.41M19.07 4.93l-1.41 1.41'/%3E%3C/svg%3E")}.vpi-moon{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='M12 3a6 6 0 0 0 9 9 9 9 0 1 1-9-9Z'/%3E%3C/svg%3E")}.vpi-more-horizontal{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Ccircle cx='12' cy='12' r='1'/%3E%3Ccircle cx='19' cy='12' r='1'/%3E%3Ccircle cx='5' cy='12' r='1'/%3E%3C/svg%3E")}.vpi-languages{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='m5 8 6 6M4 14l6-6 2-3M2 5h12M7 2h1M22 22l-5-10-5 10M14 18h6'/%3E%3C/svg%3E")}.vpi-heart{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='M19 14c1.49-1.46 3-3.21 3-5.5A5.5 5.5 0 0 0 16.5 3c-1.76 0-3 .5-4.5 2-1.5-1.5-2.74-2-4.5-2A5.5 5.5 0 0 0 2 8.5c0 2.3 1.5 4.05 3 5.5l7 7Z'/%3E%3C/svg%3E")}.vpi-search{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Ccircle cx='11' cy='11' r='8'/%3E%3Cpath d='m21 21-4.3-4.3'/%3E%3C/svg%3E")}.vpi-layout-list{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Crect width='7' height='7' x='3' y='3' rx='1'/%3E%3Crect width='7' height='7' x='3' y='14' rx='1'/%3E%3Cpath d='M14 4h7M14 9h7M14 15h7M14 20h7'/%3E%3C/svg%3E")}.vpi-delete{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='M20 5H9l-7 7 7 7h11a2 2 0 0 0 2-2V7a2 2 0 0 0-2-2ZM18 9l-6 6M12 9l6 6'/%3E%3C/svg%3E")}.vpi-corner-down-left{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Cpath d='m9 10-5 5 5 5'/%3E%3Cpath d='M20 4v7a4 4 0 0 1-4 4H4'/%3E%3C/svg%3E")}:root{--vp-icon-copy: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='rgba(128,128,128,1)' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Crect width='8' height='4' x='8' y='2' rx='1' ry='1'/%3E%3Cpath d='M16 4h2a2 2 0 0 1 2 2v14a2 2 0 0 1-2 2H6a2 2 0 0 1-2-2V6a2 2 0 0 1 2-2h2'/%3E%3C/svg%3E");--vp-icon-copied: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' fill='none' stroke='rgba(128,128,128,1)' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' viewBox='0 0 24 24'%3E%3Crect width='8' height='4' x='8' y='2' rx='1' ry='1'/%3E%3Cpath d='M16 4h2a2 2 0 0 1 2 2v14a2 2 0 0 1-2 2H6a2 2 0 0 1-2-2V6a2 2 0 0 1 2-2h2'/%3E%3Cpath d='m9 14 2 2 4-4'/%3E%3C/svg%3E")}.vpi-social-discord{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M20.317 4.37a19.791 19.791 0 0 0-4.885-1.515.074.074 0 0 0-.079.037c-.21.375-.444.864-.608 1.25a18.27 18.27 0 0 0-5.487 0 12.64 12.64 0 0 0-.617-1.25.077.077 0 0 0-.079-.037A19.736 19.736 0 0 0 3.677 4.37a.07.07 0 0 0-.032.027C.533 9.046-.32 13.58.099 18.057a.082.082 0 0 0 .031.057 19.9 19.9 0 0 0 5.993 3.03.078.078 0 0 0 .084-.028c.462-.63.874-1.295 1.226-1.994a.076.076 0 0 0-.041-.106 13.107 13.107 0 0 1-1.872-.892.077.077 0 0 1-.008-.128 10.2 10.2 0 0 0 .372-.292.074.074 0 0 1 .077-.01c3.928 1.793 8.18 1.793 12.062 0a.074.074 0 0 1 .078.01c.12.098.246.198.373.292a.077.077 0 0 1-.006.127 12.299 12.299 0 0 1-1.873.892.077.077 0 0 0-.041.107c.36.698.772 1.362 1.225 1.993a.076.076 0 0 0 .084.028 19.839 19.839 0 0 0 6.002-3.03.077.077 0 0 0 .032-.054c.5-5.177-.838-9.674-3.549-13.66a.061.061 0 0 0-.031-.03zM8.02 15.33c-1.183 0-2.157-1.085-2.157-2.419 0-1.333.956-2.419 2.157-2.419 1.21 0 2.176 1.096 2.157 2.42 0 1.333-.956 2.418-2.157 2.418zm7.975 0c-1.183 0-2.157-1.085-2.157-2.419 0-1.333.955-2.419 2.157-2.419 1.21 0 2.176 1.096 2.157 2.42 0 1.333-.946 2.418-2.157 2.418Z'/%3E%3C/svg%3E")}.vpi-social-facebook{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M9.101 23.691v-7.98H6.627v-3.667h2.474v-1.58c0-4.085 1.848-5.978 5.858-5.978.401 0 .955.042 1.468.103a8.68 8.68 0 0 1 1.141.195v3.325a8.623 8.623 0 0 0-.653-.036 26.805 26.805 0 0 0-.733-.009c-.707 0-1.259.096-1.675.309a1.686 1.686 0 0 0-.679.622c-.258.42-.374.995-.374 1.752v1.297h3.919l-.386 2.103-.287 1.564h-3.246v8.245C19.396 23.238 24 18.179 24 12.044c0-6.627-5.373-12-12-12s-12 5.373-12 12c0 5.628 3.874 10.35 9.101 11.647Z'/%3E%3C/svg%3E")}.vpi-social-github{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M12 .297c-6.63 0-12 5.373-12 12 0 5.303 3.438 9.8 8.205 11.385.6.113.82-.258.82-.577 0-.285-.01-1.04-.015-2.04-3.338.724-4.042-1.61-4.042-1.61C4.422 18.07 3.633 17.7 3.633 17.7c-1.087-.744.084-.729.084-.729 1.205.084 1.838 1.236 1.838 1.236 1.07 1.835 2.809 1.305 3.495.998.108-.776.417-1.305.76-1.605-2.665-.3-5.466-1.332-5.466-5.93 0-1.31.465-2.38 1.235-3.22-.135-.303-.54-1.523.105-3.176 0 0 1.005-.322 3.3 1.23.96-.267 1.98-.399 3-.405 1.02.006 2.04.138 3 .405 2.28-1.552 3.285-1.23 3.285-1.23.645 1.653.24 2.873.12 3.176.765.84 1.23 1.91 1.23 3.22 0 4.61-2.805 5.625-5.475 5.92.42.36.81 1.096.81 2.22 0 1.606-.015 2.896-.015 3.286 0 .315.21.69.825.57C20.565 22.092 24 17.592 24 12.297c0-6.627-5.373-12-12-12'/%3E%3C/svg%3E")}.vpi-social-instagram{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M7.03.084c-1.277.06-2.149.264-2.91.563a5.874 5.874 0 0 0-2.124 1.388 5.878 5.878 0 0 0-1.38 2.127C.321 4.926.12 5.8.064 7.076.008 8.354-.005 8.764.001 12.023c.007 3.259.021 3.667.083 4.947.061 1.277.264 2.149.563 2.911.308.789.72 1.457 1.388 2.123a5.872 5.872 0 0 0 2.129 1.38c.763.295 1.636.496 2.913.552 1.278.056 1.689.069 4.947.063 3.257-.007 3.668-.021 4.947-.082 1.28-.06 2.147-.265 2.91-.563a5.881 5.881 0 0 0 2.123-1.388 5.881 5.881 0 0 0 1.38-2.129c.295-.763.496-1.636.551-2.912.056-1.28.07-1.69.063-4.948-.006-3.258-.02-3.667-.081-4.947-.06-1.28-.264-2.148-.564-2.911a5.892 5.892 0 0 0-1.387-2.123 5.857 5.857 0 0 0-2.128-1.38C19.074.322 18.202.12 16.924.066 15.647.009 15.236-.006 11.977 0 8.718.008 8.31.021 7.03.084m.14 21.693c-1.17-.05-1.805-.245-2.228-.408a3.736 3.736 0 0 1-1.382-.895 3.695 3.695 0 0 1-.9-1.378c-.165-.423-.363-1.058-.417-2.228-.06-1.264-.072-1.644-.08-4.848-.006-3.204.006-3.583.061-4.848.05-1.169.246-1.805.408-2.228.216-.561.477-.96.895-1.382a3.705 3.705 0 0 1 1.379-.9c.423-.165 1.057-.361 2.227-.417 1.265-.06 1.644-.072 4.848-.08 3.203-.006 3.583.006 4.85.062 1.168.05 1.804.244 2.227.408.56.216.96.475 1.382.895.421.42.681.817.9 1.378.165.422.362 1.056.417 2.227.06 1.265.074 1.645.08 4.848.005 3.203-.006 3.583-.061 4.848-.051 1.17-.245 1.805-.408 2.23-.216.56-.477.96-.896 1.38a3.705 3.705 0 0 1-1.378.9c-.422.165-1.058.362-2.226.418-1.266.06-1.645.072-4.85.079-3.204.007-3.582-.006-4.848-.06m9.783-16.192a1.44 1.44 0 1 0 1.437-1.442 1.44 1.44 0 0 0-1.437 1.442M5.839 12.012a6.161 6.161 0 1 0 12.323-.024 6.162 6.162 0 0 0-12.323.024M8 12.008A4 4 0 1 1 12.008 16 4 4 0 0 1 8 12.008'/%3E%3C/svg%3E")}.vpi-social-linkedin{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M20.447 20.452h-3.554v-5.569c0-1.328-.027-3.037-1.852-3.037-1.853 0-2.136 1.445-2.136 2.939v5.667H9.351V9h3.414v1.561h.046c.477-.9 1.637-1.85 3.37-1.85 3.601 0 4.267 2.37 4.267 5.455v6.286zM5.337 7.433a2.062 2.062 0 0 1-2.063-2.065 2.064 2.064 0 1 1 2.063 2.065zm1.782 13.019H3.555V9h3.564v11.452zM22.225 0H1.771C.792 0 0 .774 0 1.729v20.542C0 23.227.792 24 1.771 24h20.451C23.2 24 24 23.227 24 22.271V1.729C24 .774 23.2 0 22.222 0h.003z'/%3E%3C/svg%3E")}.vpi-social-mastodon{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M23.268 5.313c-.35-2.578-2.617-4.61-5.304-5.004C17.51.242 15.792 0 11.813 0h-.03c-3.98 0-4.835.242-5.288.309C3.882.692 1.496 2.518.917 5.127.64 6.412.61 7.837.661 9.143c.074 1.874.088 3.745.26 5.611.118 1.24.325 2.47.62 3.68.55 2.237 2.777 4.098 4.96 4.857 2.336.792 4.849.923 7.256.38.265-.061.527-.132.786-.213.585-.184 1.27-.39 1.774-.753a.057.057 0 0 0 .023-.043v-1.809a.052.052 0 0 0-.02-.041.053.053 0 0 0-.046-.01 20.282 20.282 0 0 1-4.709.545c-2.73 0-3.463-1.284-3.674-1.818a5.593 5.593 0 0 1-.319-1.433.053.053 0 0 1 .066-.054c1.517.363 3.072.546 4.632.546.376 0 .75 0 1.125-.01 1.57-.044 3.224-.124 4.768-.422.038-.008.077-.015.11-.024 2.435-.464 4.753-1.92 4.989-5.604.008-.145.03-1.52.03-1.67.002-.512.167-3.63-.024-5.545zm-3.748 9.195h-2.561V8.29c0-1.309-.55-1.976-1.67-1.976-1.23 0-1.846.79-1.846 2.35v3.403h-2.546V8.663c0-1.56-.617-2.35-1.848-2.35-1.112 0-1.668.668-1.67 1.977v6.218H4.822V8.102c0-1.31.337-2.35 1.011-3.12.696-.77 1.608-1.164 2.74-1.164 1.311 0 2.302.5 2.962 1.498l.638 1.06.638-1.06c.66-.999 1.65-1.498 2.96-1.498 1.13 0 2.043.395 2.74 1.164.675.77 1.012 1.81 1.012 3.12z'/%3E%3C/svg%3E")}.vpi-social-npm{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M1.763 0C.786 0 0 .786 0 1.763v20.474C0 23.214.786 24 1.763 24h20.474c.977 0 1.763-.786 1.763-1.763V1.763C24 .786 23.214 0 22.237 0zM5.13 5.323l13.837.019-.009 13.836h-3.464l.01-10.382h-3.456L12.04 19.17H5.113z'/%3E%3C/svg%3E")}.vpi-social-slack{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M5.042 15.165a2.528 2.528 0 0 1-2.52 2.523A2.528 2.528 0 0 1 0 15.165a2.527 2.527 0 0 1 2.522-2.52h2.52v2.52zm1.271 0a2.527 2.527 0 0 1 2.521-2.52 2.527 2.527 0 0 1 2.521 2.52v6.313A2.528 2.528 0 0 1 8.834 24a2.528 2.528 0 0 1-2.521-2.522v-6.313zM8.834 5.042a2.528 2.528 0 0 1-2.521-2.52A2.528 2.528 0 0 1 8.834 0a2.528 2.528 0 0 1 2.521 2.522v2.52H8.834zm0 1.271a2.528 2.528 0 0 1 2.521 2.521 2.528 2.528 0 0 1-2.521 2.521H2.522A2.528 2.528 0 0 1 0 8.834a2.528 2.528 0 0 1 2.522-2.521h6.312zm10.122 2.521a2.528 2.528 0 0 1 2.522-2.521A2.528 2.528 0 0 1 24 8.834a2.528 2.528 0 0 1-2.522 2.521h-2.522V8.834zm-1.268 0a2.528 2.528 0 0 1-2.523 2.521 2.527 2.527 0 0 1-2.52-2.521V2.522A2.527 2.527 0 0 1 15.165 0a2.528 2.528 0 0 1 2.523 2.522v6.312zm-2.523 10.122a2.528 2.528 0 0 1 2.523 2.522A2.528 2.528 0 0 1 15.165 24a2.527 2.527 0 0 1-2.52-2.522v-2.522h2.52zm0-1.268a2.527 2.527 0 0 1-2.52-2.523 2.526 2.526 0 0 1 2.52-2.52h6.313A2.527 2.527 0 0 1 24 15.165a2.528 2.528 0 0 1-2.522 2.523h-6.313z'/%3E%3C/svg%3E")}.vpi-social-twitter,.vpi-social-x{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M18.901 1.153h3.68l-8.04 9.19L24 22.846h-7.406l-5.8-7.584-6.638 7.584H.474l8.6-9.83L0 1.154h7.594l5.243 6.932ZM17.61 20.644h2.039L6.486 3.24H4.298Z'/%3E%3C/svg%3E")}.vpi-social-youtube{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath d='M23.498 6.186a3.016 3.016 0 0 0-2.122-2.136C19.505 3.545 12 3.545 12 3.545s-7.505 0-9.377.505A3.017 3.017 0 0 0 .502 6.186C0 8.07 0 12 0 12s0 3.93.502 5.814a3.016 3.016 0 0 0 2.122 2.136c1.871.505 9.376.505 9.376.505s7.505 0 9.377-.505a3.015 3.015 0 0 0 2.122-2.136C24 15.93 24 12 24 12s0-3.93-.502-5.814zM9.545 15.568V8.432L15.818 12l-6.273 3.568z'/%3E%3C/svg%3E")}.visually-hidden{position:absolute;width:1px;height:1px;white-space:nowrap;clip:rect(0 0 0 0);clip-path:inset(50%);overflow:hidden}.custom-block{border:1px solid transparent;border-radius:8px;padding:16px 16px 8px;line-height:24px;font-size:var(--vp-custom-block-font-size);color:var(--vp-c-text-2)}.custom-block.info{border-color:var(--vp-custom-block-info-border);color:var(--vp-custom-block-info-text);background-color:var(--vp-custom-block-info-bg)}.custom-block.info a,.custom-block.info code{color:var(--vp-c-brand-1)}.custom-block.info a:hover,.custom-block.info a:hover>code{color:var(--vp-c-brand-2)}.custom-block.info code{background-color:var(--vp-custom-block-info-code-bg)}.custom-block.note{border-color:var(--vp-custom-block-note-border);color:var(--vp-custom-block-note-text);background-color:var(--vp-custom-block-note-bg)}.custom-block.note a,.custom-block.note code{color:var(--vp-c-brand-1)}.custom-block.note a:hover,.custom-block.note a:hover>code{color:var(--vp-c-brand-2)}.custom-block.note code{background-color:var(--vp-custom-block-note-code-bg)}.custom-block.tip{border-color:var(--vp-custom-block-tip-border);color:var(--vp-custom-block-tip-text);background-color:var(--vp-custom-block-tip-bg)}.custom-block.tip a,.custom-block.tip code{color:var(--vp-c-tip-1)}.custom-block.tip a:hover,.custom-block.tip a:hover>code{color:var(--vp-c-tip-2)}.custom-block.tip code{background-color:var(--vp-custom-block-tip-code-bg)}.custom-block.important{border-color:var(--vp-custom-block-important-border);color:var(--vp-custom-block-important-text);background-color:var(--vp-custom-block-important-bg)}.custom-block.important a,.custom-block.important code{color:var(--vp-c-important-1)}.custom-block.important a:hover,.custom-block.important a:hover>code{color:var(--vp-c-important-2)}.custom-block.important code{background-color:var(--vp-custom-block-important-code-bg)}.custom-block.warning{border-color:var(--vp-custom-block-warning-border);color:var(--vp-custom-block-warning-text);background-color:var(--vp-custom-block-warning-bg)}.custom-block.warning a,.custom-block.warning code{color:var(--vp-c-warning-1)}.custom-block.warning a:hover,.custom-block.warning a:hover>code{color:var(--vp-c-warning-2)}.custom-block.warning code{background-color:var(--vp-custom-block-warning-code-bg)}.custom-block.danger{border-color:var(--vp-custom-block-danger-border);color:var(--vp-custom-block-danger-text);background-color:var(--vp-custom-block-danger-bg)}.custom-block.danger a,.custom-block.danger code{color:var(--vp-c-danger-1)}.custom-block.danger a:hover,.custom-block.danger a:hover>code{color:var(--vp-c-danger-2)}.custom-block.danger code{background-color:var(--vp-custom-block-danger-code-bg)}.custom-block.caution{border-color:var(--vp-custom-block-caution-border);color:var(--vp-custom-block-caution-text);background-color:var(--vp-custom-block-caution-bg)}.custom-block.caution a,.custom-block.caution code{color:var(--vp-c-caution-1)}.custom-block.caution a:hover,.custom-block.caution a:hover>code{color:var(--vp-c-caution-2)}.custom-block.caution code{background-color:var(--vp-custom-block-caution-code-bg)}.custom-block.details{border-color:var(--vp-custom-block-details-border);color:var(--vp-custom-block-details-text);background-color:var(--vp-custom-block-details-bg)}.custom-block.details a{color:var(--vp-c-brand-1)}.custom-block.details a:hover,.custom-block.details a:hover>code{color:var(--vp-c-brand-2)}.custom-block.details code{background-color:var(--vp-custom-block-details-code-bg)}.custom-block-title{font-weight:600}.custom-block p+p{margin:8px 0}.custom-block.details summary{margin:0 0 8px;font-weight:700;cursor:pointer;-webkit-user-select:none;user-select:none}.custom-block.details summary+p{margin:8px 0}.custom-block a{color:inherit;font-weight:600;text-decoration:underline;text-underline-offset:2px;transition:opacity .25s}.custom-block a:hover{opacity:.75}.custom-block code{font-size:var(--vp-custom-block-code-font-size)}.custom-block.custom-block th,.custom-block.custom-block blockquote>p{font-size:var(--vp-custom-block-font-size);color:inherit}.dark .vp-code span{color:var(--shiki-dark, inherit)}html:not(.dark) .vp-code span{color:var(--shiki-light, inherit)}.vp-code-group{margin-top:16px}.vp-code-group .tabs{position:relative;display:flex;margin-right:-24px;margin-left:-24px;padding:0 12px;background-color:var(--vp-code-tab-bg);overflow-x:auto;overflow-y:hidden;box-shadow:inset 0 -1px var(--vp-code-tab-divider)}@media (min-width: 640px){.vp-code-group .tabs{margin-right:0;margin-left:0;border-radius:8px 8px 0 0}}.vp-code-group .tabs input{position:fixed;opacity:0;pointer-events:none}.vp-code-group .tabs label{position:relative;display:inline-block;border-bottom:1px solid transparent;padding:0 12px;line-height:48px;font-size:14px;font-weight:500;color:var(--vp-code-tab-text-color);white-space:nowrap;cursor:pointer;transition:color .25s}.vp-code-group .tabs label:after{position:absolute;right:8px;bottom:-1px;left:8px;z-index:1;height:2px;border-radius:2px;content:"";background-color:transparent;transition:background-color .25s}.vp-code-group label:hover{color:var(--vp-code-tab-hover-text-color)}.vp-code-group input:checked+label{color:var(--vp-code-tab-active-text-color)}.vp-code-group input:checked+label:after{background-color:var(--vp-code-tab-active-bar-color)}.vp-code-group div[class*=language-],.vp-block{display:none;margin-top:0!important;border-top-left-radius:0!important;border-top-right-radius:0!important}.vp-code-group div[class*=language-].active,.vp-block.active{display:block}.vp-block{padding:20px 24px}.vp-doc h1,.vp-doc h2,.vp-doc h3,.vp-doc h4,.vp-doc h5,.vp-doc h6{position:relative;font-weight:600;outline:none}.vp-doc h1{letter-spacing:-.02em;line-height:40px;font-size:28px}.vp-doc h2{margin:48px 0 16px;border-top:1px solid var(--vp-c-divider);padding-top:24px;letter-spacing:-.02em;line-height:32px;font-size:24px}.vp-doc h3{margin:32px 0 0;letter-spacing:-.01em;line-height:28px;font-size:20px}.vp-doc .header-anchor{position:absolute;top:0;left:0;margin-left:-.87em;font-weight:500;-webkit-user-select:none;user-select:none;opacity:0;text-decoration:none;transition:color .25s,opacity .25s}.vp-doc .header-anchor:before{content:var(--vp-header-anchor-symbol)}.vp-doc h1:hover .header-anchor,.vp-doc h1 .header-anchor:focus,.vp-doc h2:hover .header-anchor,.vp-doc h2 .header-anchor:focus,.vp-doc h3:hover .header-anchor,.vp-doc h3 .header-anchor:focus,.vp-doc h4:hover .header-anchor,.vp-doc h4 .header-anchor:focus,.vp-doc h5:hover .header-anchor,.vp-doc h5 .header-anchor:focus,.vp-doc h6:hover .header-anchor,.vp-doc h6 .header-anchor:focus{opacity:1}@media (min-width: 768px){.vp-doc h1{letter-spacing:-.02em;line-height:40px;font-size:32px}}.vp-doc h2 .header-anchor{top:24px}.vp-doc p,.vp-doc summary{margin:16px 0}.vp-doc p{line-height:28px}.vp-doc blockquote{margin:16px 0;border-left:2px solid var(--vp-c-divider);padding-left:16px;transition:border-color .5s}.vp-doc blockquote>p{margin:0;font-size:16px;color:var(--vp-c-text-2);transition:color .5s}.vp-doc a{font-weight:500;color:var(--vp-c-brand-1);text-decoration:underline;text-underline-offset:2px;transition:color .25s,opacity .25s}.vp-doc a:hover{color:var(--vp-c-brand-2)}.vp-doc strong{font-weight:600}.vp-doc ul,.vp-doc ol{padding-left:1.25rem;margin:16px 0}.vp-doc ul{list-style:disc}.vp-doc ol{list-style:decimal}.vp-doc li+li{margin-top:8px}.vp-doc li>ol,.vp-doc li>ul{margin:8px 0 0}.vp-doc table{display:block;border-collapse:collapse;margin:20px 0;overflow-x:auto}.vp-doc tr{background-color:var(--vp-c-bg);border-top:1px solid var(--vp-c-divider);transition:background-color .5s}.vp-doc tr:nth-child(2n){background-color:var(--vp-c-bg-soft)}.vp-doc th,.vp-doc td{border:1px solid var(--vp-c-divider);padding:8px 16px}.vp-doc th{text-align:left;font-size:14px;font-weight:600;color:var(--vp-c-text-2);background-color:var(--vp-c-bg-soft)}.vp-doc td{font-size:14px}.vp-doc hr{margin:16px 0;border:none;border-top:1px solid var(--vp-c-divider)}.vp-doc .custom-block{margin:16px 0}.vp-doc .custom-block p{margin:8px 0;line-height:24px}.vp-doc .custom-block p:first-child{margin:0}.vp-doc .custom-block div[class*=language-]{margin:8px 0;border-radius:8px}.vp-doc .custom-block div[class*=language-] code{font-weight:400;background-color:transparent}.vp-doc .custom-block .vp-code-group .tabs{margin:0;border-radius:8px 8px 0 0}.vp-doc :not(pre,h1,h2,h3,h4,h5,h6)>code{font-size:var(--vp-code-font-size);color:var(--vp-code-color)}.vp-doc :not(pre)>code{border-radius:4px;padding:3px 6px;background-color:var(--vp-code-bg);transition:color .25s,background-color .5s}.vp-doc a>code{color:var(--vp-code-link-color)}.vp-doc a:hover>code{color:var(--vp-code-link-hover-color)}.vp-doc h1>code,.vp-doc h2>code,.vp-doc h3>code{font-size:.9em}.vp-doc div[class*=language-],.vp-block{position:relative;margin:16px -24px;background-color:var(--vp-code-block-bg);overflow-x:auto;transition:background-color .5s}@media (min-width: 640px){.vp-doc div[class*=language-],.vp-block{border-radius:8px;margin:16px 0}}@media (max-width: 639px){.vp-doc li div[class*=language-]{border-radius:8px 0 0 8px}}.vp-doc div[class*=language-]+div[class*=language-],.vp-doc div[class$=-api]+div[class*=language-],.vp-doc div[class*=language-]+div[class$=-api]>div[class*=language-]{margin-top:-8px}.vp-doc [class*=language-] pre,.vp-doc [class*=language-] code{direction:ltr;text-align:left;white-space:pre;word-spacing:normal;word-break:normal;word-wrap:normal;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-hyphens:none;-moz-hyphens:none;-ms-hyphens:none;hyphens:none}.vp-doc [class*=language-] pre{position:relative;z-index:1;margin:0;padding:20px 0;background:transparent;overflow-x:auto}.vp-doc [class*=language-] code{display:block;padding:0 24px;width:fit-content;min-width:100%;line-height:var(--vp-code-line-height);font-size:var(--vp-code-font-size);color:var(--vp-code-block-color);transition:color .5s}.vp-doc [class*=language-] code .highlighted{background-color:var(--vp-code-line-highlight-color);transition:background-color .5s;margin:0 -24px;padding:0 24px;width:calc(100% + 48px);display:inline-block}.vp-doc [class*=language-] code .highlighted.error{background-color:var(--vp-code-line-error-color)}.vp-doc [class*=language-] code .highlighted.warning{background-color:var(--vp-code-line-warning-color)}.vp-doc [class*=language-] code .diff{transition:background-color .5s;margin:0 -24px;padding:0 24px;width:calc(100% + 48px);display:inline-block}.vp-doc [class*=language-] code .diff:before{position:absolute;left:10px}.vp-doc [class*=language-] .has-focused-lines .line:not(.has-focus){filter:blur(.095rem);opacity:.4;transition:filter .35s,opacity .35s}.vp-doc [class*=language-] .has-focused-lines .line:not(.has-focus){opacity:.7;transition:filter .35s,opacity .35s}.vp-doc [class*=language-]:hover .has-focused-lines .line:not(.has-focus){filter:blur(0);opacity:1}.vp-doc [class*=language-] code .diff.remove{background-color:var(--vp-code-line-diff-remove-color);opacity:.7}.vp-doc [class*=language-] code .diff.remove:before{content:"-";color:var(--vp-code-line-diff-remove-symbol-color)}.vp-doc [class*=language-] code .diff.add{background-color:var(--vp-code-line-diff-add-color)}.vp-doc [class*=language-] code .diff.add:before{content:"+";color:var(--vp-code-line-diff-add-symbol-color)}.vp-doc div[class*=language-].line-numbers-mode{padding-left:32px}.vp-doc .line-numbers-wrapper{position:absolute;top:0;bottom:0;left:0;z-index:3;border-right:1px solid var(--vp-code-block-divider-color);padding-top:20px;width:32px;text-align:center;font-family:var(--vp-font-family-mono);line-height:var(--vp-code-line-height);font-size:var(--vp-code-font-size);color:var(--vp-code-line-number-color);transition:border-color .5s,color .5s}.vp-doc [class*=language-]>button.copy{direction:ltr;position:absolute;top:12px;right:12px;z-index:3;border:1px solid var(--vp-code-copy-code-border-color);border-radius:4px;width:40px;height:40px;background-color:var(--vp-code-copy-code-bg);opacity:0;cursor:pointer;background-image:var(--vp-icon-copy);background-position:50%;background-size:20px;background-repeat:no-repeat;transition:border-color .25s,background-color .25s,opacity .25s}.vp-doc [class*=language-]:hover>button.copy,.vp-doc [class*=language-]>button.copy:focus{opacity:1}.vp-doc [class*=language-]>button.copy:hover,.vp-doc [class*=language-]>button.copy.copied{border-color:var(--vp-code-copy-code-hover-border-color);background-color:var(--vp-code-copy-code-hover-bg)}.vp-doc [class*=language-]>button.copy.copied,.vp-doc [class*=language-]>button.copy:hover.copied{border-radius:0 4px 4px 0;background-color:var(--vp-code-copy-code-hover-bg);background-image:var(--vp-icon-copied)}.vp-doc [class*=language-]>button.copy.copied:before,.vp-doc [class*=language-]>button.copy:hover.copied:before{position:relative;top:-1px;transform:translate(calc(-100% - 1px));display:flex;justify-content:center;align-items:center;border:1px solid var(--vp-code-copy-code-hover-border-color);border-right:0;border-radius:4px 0 0 4px;padding:0 10px;width:fit-content;height:40px;text-align:center;font-size:12px;font-weight:500;color:var(--vp-code-copy-code-active-text);background-color:var(--vp-code-copy-code-hover-bg);white-space:nowrap;content:var(--vp-code-copy-copied-text-content)}.vp-doc [class*=language-]>span.lang{position:absolute;top:2px;right:8px;z-index:2;font-size:12px;font-weight:500;color:var(--vp-code-lang-color);transition:color .4s,opacity .4s}.vp-doc [class*=language-]:hover>button.copy+span.lang,.vp-doc [class*=language-]>button.copy:focus+span.lang{opacity:0}.vp-doc .VPTeamMembers{margin-top:24px}.vp-doc .VPTeamMembers.small.count-1 .container{margin:0!important;max-width:calc((100% - 24px)/2)!important}.vp-doc .VPTeamMembers.small.count-2 .container,.vp-doc .VPTeamMembers.small.count-3 .container{max-width:100%!important}.vp-doc .VPTeamMembers.medium.count-1 .container{margin:0!important;max-width:calc((100% - 24px)/2)!important}:is(.vp-external-link-icon,.vp-doc a[href*="://"],.vp-doc a[target=_blank]):not(.no-icon):after{display:inline-block;margin-top:-1px;margin-left:4px;width:11px;height:11px;background:currentColor;color:var(--vp-c-text-3);flex-shrink:0;--icon: url("data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' %3E%3Cpath d='M0 0h24v24H0V0z' fill='none' /%3E%3Cpath d='M9 5v2h6.59L4 18.59 5.41 20 17 8.41V15h2V5H9z' /%3E%3C/svg%3E");-webkit-mask-image:var(--icon);mask-image:var(--icon)}.vp-external-link-icon:after{content:""}.external-link-icon-enabled :is(.vp-doc a[href*="://"],.vp-doc a[target=_blank]):after{content:"";color:currentColor}.vp-sponsor{border-radius:16px;overflow:hidden}.vp-sponsor.aside{border-radius:12px}.vp-sponsor-section+.vp-sponsor-section{margin-top:4px}.vp-sponsor-tier{margin:0 0 4px!important;text-align:center;letter-spacing:1px!important;line-height:24px;width:100%;font-weight:600;color:var(--vp-c-text-2);background-color:var(--vp-c-bg-soft)}.vp-sponsor.normal .vp-sponsor-tier{padding:13px 0 11px;font-size:14px}.vp-sponsor.aside .vp-sponsor-tier{padding:9px 0 7px;font-size:12px}.vp-sponsor-grid+.vp-sponsor-tier{margin-top:4px}.vp-sponsor-grid{display:flex;flex-wrap:wrap;gap:4px}.vp-sponsor-grid.xmini .vp-sponsor-grid-link{height:64px}.vp-sponsor-grid.xmini .vp-sponsor-grid-image{max-width:64px;max-height:22px}.vp-sponsor-grid.mini .vp-sponsor-grid-link{height:72px}.vp-sponsor-grid.mini .vp-sponsor-grid-image{max-width:96px;max-height:24px}.vp-sponsor-grid.small .vp-sponsor-grid-link{height:96px}.vp-sponsor-grid.small .vp-sponsor-grid-image{max-width:96px;max-height:24px}.vp-sponsor-grid.medium .vp-sponsor-grid-link{height:112px}.vp-sponsor-grid.medium .vp-sponsor-grid-image{max-width:120px;max-height:36px}.vp-sponsor-grid.big .vp-sponsor-grid-link{height:184px}.vp-sponsor-grid.big .vp-sponsor-grid-image{max-width:192px;max-height:56px}.vp-sponsor-grid[data-vp-grid="2"] .vp-sponsor-grid-item{width:calc((100% - 4px)/2)}.vp-sponsor-grid[data-vp-grid="3"] .vp-sponsor-grid-item{width:calc((100% - 4px * 2) / 3)}.vp-sponsor-grid[data-vp-grid="4"] .vp-sponsor-grid-item{width:calc((100% - 12px)/4)}.vp-sponsor-grid[data-vp-grid="5"] .vp-sponsor-grid-item{width:calc((100% - 16px)/5)}.vp-sponsor-grid[data-vp-grid="6"] .vp-sponsor-grid-item{width:calc((100% - 4px * 5) / 6)}.vp-sponsor-grid-item{flex-shrink:0;width:100%;background-color:var(--vp-c-bg-soft);transition:background-color .25s}.vp-sponsor-grid-item:hover{background-color:var(--vp-c-default-soft)}.vp-sponsor-grid-item:hover .vp-sponsor-grid-image{filter:grayscale(0) invert(0)}.vp-sponsor-grid-item.empty:hover{background-color:var(--vp-c-bg-soft)}.dark .vp-sponsor-grid-item:hover{background-color:var(--vp-c-white)}.dark .vp-sponsor-grid-item.empty:hover{background-color:var(--vp-c-bg-soft)}.vp-sponsor-grid-link{display:flex}.vp-sponsor-grid-box{display:flex;justify-content:center;align-items:center;width:100%}.vp-sponsor-grid-image{max-width:100%;filter:grayscale(1);transition:filter .25s}.dark .vp-sponsor-grid-image{filter:grayscale(1) invert(1)}.VPBadge{display:inline-block;margin-left:2px;border:1px solid transparent;border-radius:12px;padding:0 10px;line-height:22px;font-size:12px;font-weight:500;transform:translateY(-2px)}.VPBadge.small{padding:0 6px;line-height:18px;font-size:10px;transform:translateY(-8px)}.VPDocFooter .VPBadge{display:none}.vp-doc h1>.VPBadge{margin-top:4px;vertical-align:top}.vp-doc h2>.VPBadge{margin-top:3px;padding:0 8px;vertical-align:top}.vp-doc h3>.VPBadge{vertical-align:middle}.vp-doc h4>.VPBadge,.vp-doc h5>.VPBadge,.vp-doc h6>.VPBadge{vertical-align:middle;line-height:18px}.VPBadge.info{border-color:var(--vp-badge-info-border);color:var(--vp-badge-info-text);background-color:var(--vp-badge-info-bg)}.VPBadge.tip{border-color:var(--vp-badge-tip-border);color:var(--vp-badge-tip-text);background-color:var(--vp-badge-tip-bg)}.VPBadge.warning{border-color:var(--vp-badge-warning-border);color:var(--vp-badge-warning-text);background-color:var(--vp-badge-warning-bg)}.VPBadge.danger{border-color:var(--vp-badge-danger-border);color:var(--vp-badge-danger-text);background-color:var(--vp-badge-danger-bg)}.VPBackdrop[data-v-c79a1216]{position:fixed;top:0;right:0;bottom:0;left:0;z-index:var(--vp-z-index-backdrop);background:var(--vp-backdrop-bg-color);transition:opacity .5s}.VPBackdrop.fade-enter-from[data-v-c79a1216],.VPBackdrop.fade-leave-to[data-v-c79a1216]{opacity:0}.VPBackdrop.fade-leave-active[data-v-c79a1216]{transition-duration:.25s}@media (min-width: 1280px){.VPBackdrop[data-v-c79a1216]{display:none}}.NotFound[data-v-d6be1790]{padding:64px 24px 96px;text-align:center}@media (min-width: 768px){.NotFound[data-v-d6be1790]{padding:96px 32px 168px}}.code[data-v-d6be1790]{line-height:64px;font-size:64px;font-weight:600}.title[data-v-d6be1790]{padding-top:12px;letter-spacing:2px;line-height:20px;font-size:20px;font-weight:700}.divider[data-v-d6be1790]{margin:24px auto 18px;width:64px;height:1px;background-color:var(--vp-c-divider)}.quote[data-v-d6be1790]{margin:0 auto;max-width:256px;font-size:14px;font-weight:500;color:var(--vp-c-text-2)}.action[data-v-d6be1790]{padding-top:20px}.link[data-v-d6be1790]{display:inline-block;border:1px solid var(--vp-c-brand-1);border-radius:16px;padding:3px 16px;font-size:14px;font-weight:500;color:var(--vp-c-brand-1);transition:border-color .25s,color .25s}.link[data-v-d6be1790]:hover{border-color:var(--vp-c-brand-2);color:var(--vp-c-brand-2)}.root[data-v-b933a997]{position:relative;z-index:1}.nested[data-v-b933a997]{padding-right:16px;padding-left:16px}.outline-link[data-v-b933a997]{display:block;line-height:32px;font-size:14px;font-weight:400;color:var(--vp-c-text-2);white-space:nowrap;overflow:hidden;text-overflow:ellipsis;transition:color .5s}.outline-link[data-v-b933a997]:hover,.outline-link.active[data-v-b933a997]{color:var(--vp-c-text-1);transition:color .25s}.outline-link.nested[data-v-b933a997]{padding-left:13px}.VPDocAsideOutline[data-v-a5bbad30]{display:none}.VPDocAsideOutline.has-outline[data-v-a5bbad30]{display:block}.content[data-v-a5bbad30]{position:relative;border-left:1px solid var(--vp-c-divider);padding-left:16px;font-size:13px;font-weight:500}.outline-marker[data-v-a5bbad30]{position:absolute;top:32px;left:-1px;z-index:0;opacity:0;width:2px;border-radius:2px;height:18px;background-color:var(--vp-c-brand-1);transition:top .25s cubic-bezier(0,1,.5,1),background-color .5s,opacity .25s}.outline-title[data-v-a5bbad30]{line-height:32px;font-size:14px;font-weight:600}.VPDocAside[data-v-3f215769]{display:flex;flex-direction:column;flex-grow:1}.spacer[data-v-3f215769]{flex-grow:1}.VPDocAside[data-v-3f215769] .spacer+.VPDocAsideSponsors,.VPDocAside[data-v-3f215769] .spacer+.VPDocAsideCarbonAds{margin-top:24px}.VPDocAside[data-v-3f215769] .VPDocAsideSponsors+.VPDocAsideCarbonAds{margin-top:16px}.VPLastUpdated[data-v-7e05ebdb]{line-height:24px;font-size:14px;font-weight:500;color:var(--vp-c-text-2)}@media (min-width: 640px){.VPLastUpdated[data-v-7e05ebdb]{line-height:32px;font-size:14px;font-weight:500}}.VPDocFooter[data-v-d4a0bba5]{margin-top:64px}.edit-info[data-v-d4a0bba5]{padding-bottom:18px}@media (min-width: 640px){.edit-info[data-v-d4a0bba5]{display:flex;justify-content:space-between;align-items:center;padding-bottom:14px}}.edit-link-button[data-v-d4a0bba5]{display:flex;align-items:center;border:0;line-height:32px;font-size:14px;font-weight:500;color:var(--vp-c-brand-1);transition:color .25s}.edit-link-button[data-v-d4a0bba5]:hover{color:var(--vp-c-brand-2)}.edit-link-icon[data-v-d4a0bba5]{margin-right:8px}.prev-next[data-v-d4a0bba5]{border-top:1px solid var(--vp-c-divider);padding-top:24px;display:grid;grid-row-gap:8px}@media (min-width: 640px){.prev-next[data-v-d4a0bba5]{grid-template-columns:repeat(2,1fr);grid-column-gap:16px}}.pager-link[data-v-d4a0bba5]{display:block;border:1px solid var(--vp-c-divider);border-radius:8px;padding:11px 16px 13px;width:100%;height:100%;transition:border-color .25s}.pager-link[data-v-d4a0bba5]:hover{border-color:var(--vp-c-brand-1)}.pager-link.next[data-v-d4a0bba5]{margin-left:auto;text-align:right}.desc[data-v-d4a0bba5]{display:block;line-height:20px;font-size:12px;font-weight:500;color:var(--vp-c-text-2)}.title[data-v-d4a0bba5]{display:block;line-height:20px;font-size:14px;font-weight:500;color:var(--vp-c-brand-1);transition:color .25s}.VPDoc[data-v-39a288b8]{padding:32px 24px 96px;width:100%}@media (min-width: 768px){.VPDoc[data-v-39a288b8]{padding:48px 32px 128px}}@media (min-width: 960px){.VPDoc[data-v-39a288b8]{padding:48px 32px 0}.VPDoc:not(.has-sidebar) .container[data-v-39a288b8]{display:flex;justify-content:center;max-width:992px}.VPDoc:not(.has-sidebar) .content[data-v-39a288b8]{max-width:752px}}@media (min-width: 1280px){.VPDoc .container[data-v-39a288b8]{display:flex;justify-content:center}.VPDoc .aside[data-v-39a288b8]{display:block}}@media (min-width: 1440px){.VPDoc:not(.has-sidebar) .content[data-v-39a288b8]{max-width:784px}.VPDoc:not(.has-sidebar) .container[data-v-39a288b8]{max-width:1104px}}.container[data-v-39a288b8]{margin:0 auto;width:100%}.aside[data-v-39a288b8]{position:relative;display:none;order:2;flex-grow:1;padding-left:32px;width:100%;max-width:256px}.left-aside[data-v-39a288b8]{order:1;padding-left:unset;padding-right:32px}.aside-container[data-v-39a288b8]{position:fixed;top:0;padding-top:calc(var(--vp-nav-height) + var(--vp-layout-top-height, 0px) + var(--vp-doc-top-height, 0px) + 48px);width:224px;height:100vh;overflow-x:hidden;overflow-y:auto;scrollbar-width:none}.aside-container[data-v-39a288b8]::-webkit-scrollbar{display:none}.aside-curtain[data-v-39a288b8]{position:fixed;bottom:0;z-index:10;width:224px;height:32px;background:linear-gradient(transparent,var(--vp-c-bg) 70%)}.aside-content[data-v-39a288b8]{display:flex;flex-direction:column;min-height:calc(100vh - (var(--vp-nav-height) + var(--vp-layout-top-height, 0px) + 48px));padding-bottom:32px}.content[data-v-39a288b8]{position:relative;margin:0 auto;width:100%}@media (min-width: 960px){.content[data-v-39a288b8]{padding:0 32px 128px}}@media (min-width: 1280px){.content[data-v-39a288b8]{order:1;margin:0;min-width:640px}}.content-container[data-v-39a288b8]{margin:0 auto}.VPDoc.has-aside .content-container[data-v-39a288b8]{max-width:688px}.VPButton[data-v-cad61b99]{display:inline-block;border:1px solid transparent;text-align:center;font-weight:600;white-space:nowrap;transition:color .25s,border-color .25s,background-color .25s}.VPButton[data-v-cad61b99]:active{transition:color .1s,border-color .1s,background-color .1s}.VPButton.medium[data-v-cad61b99]{border-radius:20px;padding:0 20px;line-height:38px;font-size:14px}.VPButton.big[data-v-cad61b99]{border-radius:24px;padding:0 24px;line-height:46px;font-size:16px}.VPButton.brand[data-v-cad61b99]{border-color:var(--vp-button-brand-border);color:var(--vp-button-brand-text);background-color:var(--vp-button-brand-bg)}.VPButton.brand[data-v-cad61b99]:hover{border-color:var(--vp-button-brand-hover-border);color:var(--vp-button-brand-hover-text);background-color:var(--vp-button-brand-hover-bg)}.VPButton.brand[data-v-cad61b99]:active{border-color:var(--vp-button-brand-active-border);color:var(--vp-button-brand-active-text);background-color:var(--vp-button-brand-active-bg)}.VPButton.alt[data-v-cad61b99]{border-color:var(--vp-button-alt-border);color:var(--vp-button-alt-text);background-color:var(--vp-button-alt-bg)}.VPButton.alt[data-v-cad61b99]:hover{border-color:var(--vp-button-alt-hover-border);color:var(--vp-button-alt-hover-text);background-color:var(--vp-button-alt-hover-bg)}.VPButton.alt[data-v-cad61b99]:active{border-color:var(--vp-button-alt-active-border);color:var(--vp-button-alt-active-text);background-color:var(--vp-button-alt-active-bg)}.VPButton.sponsor[data-v-cad61b99]{border-color:var(--vp-button-sponsor-border);color:var(--vp-button-sponsor-text);background-color:var(--vp-button-sponsor-bg)}.VPButton.sponsor[data-v-cad61b99]:hover{border-color:var(--vp-button-sponsor-hover-border);color:var(--vp-button-sponsor-hover-text);background-color:var(--vp-button-sponsor-hover-bg)}.VPButton.sponsor[data-v-cad61b99]:active{border-color:var(--vp-button-sponsor-active-border);color:var(--vp-button-sponsor-active-text);background-color:var(--vp-button-sponsor-active-bg)}html:not(.dark) .VPImage.dark[data-v-8426fc1a]{display:none}.dark .VPImage.light[data-v-8426fc1a]{display:none}.VPHero[data-v-303bb580]{margin-top:calc((var(--vp-nav-height) + var(--vp-layout-top-height, 0px)) * -1);padding:calc(var(--vp-nav-height) + var(--vp-layout-top-height, 0px) + 48px) 24px 48px}@media (min-width: 640px){.VPHero[data-v-303bb580]{padding:calc(var(--vp-nav-height) + var(--vp-layout-top-height, 0px) + 80px) 48px 64px}}@media (min-width: 960px){.VPHero[data-v-303bb580]{padding:calc(var(--vp-nav-height) + var(--vp-layout-top-height, 0px) + 80px) 64px 64px}}.container[data-v-303bb580]{display:flex;flex-direction:column;margin:0 auto;max-width:1152px}@media (min-width: 960px){.container[data-v-303bb580]{flex-direction:row}}.main[data-v-303bb580]{position:relative;z-index:10;order:2;flex-grow:1;flex-shrink:0}.VPHero.has-image .container[data-v-303bb580]{text-align:center}@media (min-width: 960px){.VPHero.has-image .container[data-v-303bb580]{text-align:left}}@media (min-width: 960px){.main[data-v-303bb580]{order:1;width:calc((100% / 3) * 2)}.VPHero.has-image .main[data-v-303bb580]{max-width:592px}}.name[data-v-303bb580],.text[data-v-303bb580]{max-width:392px;letter-spacing:-.4px;line-height:40px;font-size:32px;font-weight:700;white-space:pre-wrap}.VPHero.has-image .name[data-v-303bb580],.VPHero.has-image .text[data-v-303bb580]{margin:0 auto}.name[data-v-303bb580]{color:var(--vp-home-hero-name-color)}.clip[data-v-303bb580]{background:var(--vp-home-hero-name-background);-webkit-background-clip:text;background-clip:text;-webkit-text-fill-color:var(--vp-home-hero-name-color)}@media (min-width: 640px){.name[data-v-303bb580],.text[data-v-303bb580]{max-width:576px;line-height:56px;font-size:48px}}@media (min-width: 960px){.name[data-v-303bb580],.text[data-v-303bb580]{line-height:64px;font-size:56px}.VPHero.has-image .name[data-v-303bb580],.VPHero.has-image .text[data-v-303bb580]{margin:0}}.tagline[data-v-303bb580]{padding-top:8px;max-width:392px;line-height:28px;font-size:18px;font-weight:500;white-space:pre-wrap;color:var(--vp-c-text-2)}.VPHero.has-image .tagline[data-v-303bb580]{margin:0 auto}@media (min-width: 640px){.tagline[data-v-303bb580]{padding-top:12px;max-width:576px;line-height:32px;font-size:20px}}@media (min-width: 960px){.tagline[data-v-303bb580]{line-height:36px;font-size:24px}.VPHero.has-image .tagline[data-v-303bb580]{margin:0}}.actions[data-v-303bb580]{display:flex;flex-wrap:wrap;margin:-6px;padding-top:24px}.VPHero.has-image .actions[data-v-303bb580]{justify-content:center}@media (min-width: 640px){.actions[data-v-303bb580]{padding-top:32px}}@media (min-width: 960px){.VPHero.has-image .actions[data-v-303bb580]{justify-content:flex-start}}.action[data-v-303bb580]{flex-shrink:0;padding:6px}.image[data-v-303bb580]{order:1;margin:-76px -24px -48px}@media (min-width: 640px){.image[data-v-303bb580]{margin:-108px -24px -48px}}@media (min-width: 960px){.image[data-v-303bb580]{flex-grow:1;order:2;margin:0;min-height:100%}}.image-container[data-v-303bb580]{position:relative;margin:0 auto;width:320px;height:320px}@media (min-width: 640px){.image-container[data-v-303bb580]{width:392px;height:392px}}@media (min-width: 960px){.image-container[data-v-303bb580]{display:flex;justify-content:center;align-items:center;width:100%;height:100%;transform:translate(-32px,-32px)}}.image-bg[data-v-303bb580]{position:absolute;top:50%;left:50%;border-radius:50%;width:192px;height:192px;background-image:var(--vp-home-hero-image-background-image);filter:var(--vp-home-hero-image-filter);transform:translate(-50%,-50%)}@media (min-width: 640px){.image-bg[data-v-303bb580]{width:256px;height:256px}}@media (min-width: 960px){.image-bg[data-v-303bb580]{width:320px;height:320px}}[data-v-303bb580] .image-src{position:absolute;top:50%;left:50%;max-width:192px;max-height:192px;transform:translate(-50%,-50%)}@media (min-width: 640px){[data-v-303bb580] .image-src{max-width:256px;max-height:256px}}@media (min-width: 960px){[data-v-303bb580] .image-src{max-width:320px;max-height:320px}}.VPFeature[data-v-a3976bdc]{display:block;border:1px solid var(--vp-c-bg-soft);border-radius:12px;height:100%;background-color:var(--vp-c-bg-soft);transition:border-color .25s,background-color .25s}.VPFeature.link[data-v-a3976bdc]:hover{border-color:var(--vp-c-brand-1)}.box[data-v-a3976bdc]{display:flex;flex-direction:column;padding:24px;height:100%}.box[data-v-a3976bdc]>.VPImage{margin-bottom:20px}.icon[data-v-a3976bdc]{display:flex;justify-content:center;align-items:center;margin-bottom:20px;border-radius:6px;background-color:var(--vp-c-default-soft);width:48px;height:48px;font-size:24px;transition:background-color .25s}.title[data-v-a3976bdc]{line-height:24px;font-size:16px;font-weight:600}.details[data-v-a3976bdc]{flex-grow:1;padding-top:8px;line-height:24px;font-size:14px;font-weight:500;color:var(--vp-c-text-2)}.link-text[data-v-a3976bdc]{padding-top:8px}.link-text-value[data-v-a3976bdc]{display:flex;align-items:center;font-size:14px;font-weight:500;color:var(--vp-c-brand-1)}.link-text-icon[data-v-a3976bdc]{margin-left:6px}.VPFeatures[data-v-a6181336]{position:relative;padding:0 24px}@media (min-width: 640px){.VPFeatures[data-v-a6181336]{padding:0 48px}}@media (min-width: 960px){.VPFeatures[data-v-a6181336]{padding:0 64px}}.container[data-v-a6181336]{margin:0 auto;max-width:1152px}.items[data-v-a6181336]{display:flex;flex-wrap:wrap;margin:-8px}.item[data-v-a6181336]{padding:8px;width:100%}@media (min-width: 640px){.item.grid-2[data-v-a6181336],.item.grid-4[data-v-a6181336],.item.grid-6[data-v-a6181336]{width:50%}}@media (min-width: 768px){.item.grid-2[data-v-a6181336],.item.grid-4[data-v-a6181336]{width:50%}.item.grid-3[data-v-a6181336],.item.grid-6[data-v-a6181336]{width:calc(100% / 3)}}@media (min-width: 960px){.item.grid-4[data-v-a6181336]{width:25%}}.container[data-v-8e2d4988]{margin:auto;width:100%;max-width:1280px;padding:0 24px}@media (min-width: 640px){.container[data-v-8e2d4988]{padding:0 48px}}@media (min-width: 960px){.container[data-v-8e2d4988]{width:100%;padding:0 64px}}.vp-doc[data-v-8e2d4988] .VPHomeSponsors,.vp-doc[data-v-8e2d4988] .VPTeamPage{margin-left:var(--vp-offset, calc(50% - 50vw) );margin-right:var(--vp-offset, calc(50% - 50vw) )}.vp-doc[data-v-8e2d4988] .VPHomeSponsors h2{border-top:none;letter-spacing:normal}.vp-doc[data-v-8e2d4988] .VPHomeSponsors a,.vp-doc[data-v-8e2d4988] .VPTeamPage a{text-decoration:none}.VPHome[data-v-686f80a6]{margin-bottom:96px}@media (min-width: 768px){.VPHome[data-v-686f80a6]{margin-bottom:128px}}.VPContent[data-v-1428d186]{flex-grow:1;flex-shrink:0;margin:var(--vp-layout-top-height, 0px) auto 0;width:100%}.VPContent.is-home[data-v-1428d186]{width:100%;max-width:100%}.VPContent.has-sidebar[data-v-1428d186]{margin:0}@media (min-width: 960px){.VPContent[data-v-1428d186]{padding-top:var(--vp-nav-height)}.VPContent.has-sidebar[data-v-1428d186]{margin:var(--vp-layout-top-height, 0px) 0 0;padding-left:var(--vp-sidebar-width)}}@media (min-width: 1440px){.VPContent.has-sidebar[data-v-1428d186]{padding-right:calc((100vw - var(--vp-layout-max-width)) / 2);padding-left:calc((100vw - var(--vp-layout-max-width)) / 2 + var(--vp-sidebar-width))}}.VPFooter[data-v-e315a0ad]{position:relative;z-index:var(--vp-z-index-footer);border-top:1px solid var(--vp-c-gutter);padding:32px 24px;background-color:var(--vp-c-bg)}.VPFooter.has-sidebar[data-v-e315a0ad]{display:none}.VPFooter[data-v-e315a0ad] a{text-decoration-line:underline;text-underline-offset:2px;transition:color .25s}.VPFooter[data-v-e315a0ad] a:hover{color:var(--vp-c-text-1)}@media (min-width: 768px){.VPFooter[data-v-e315a0ad]{padding:32px}}.container[data-v-e315a0ad]{margin:0 auto;max-width:var(--vp-layout-max-width);text-align:center}.message[data-v-e315a0ad],.copyright[data-v-e315a0ad]{line-height:24px;font-size:14px;font-weight:500;color:var(--vp-c-text-2)}.VPLocalNavOutlineDropdown[data-v-17a5e62e]{padding:12px 20px 11px}@media (min-width: 960px){.VPLocalNavOutlineDropdown[data-v-17a5e62e]{padding:12px 36px 11px}}.VPLocalNavOutlineDropdown button[data-v-17a5e62e]{display:block;font-size:12px;font-weight:500;line-height:24px;color:var(--vp-c-text-2);transition:color .5s;position:relative}.VPLocalNavOutlineDropdown button[data-v-17a5e62e]:hover{color:var(--vp-c-text-1);transition:color .25s}.VPLocalNavOutlineDropdown button.open[data-v-17a5e62e]{color:var(--vp-c-text-1)}.icon[data-v-17a5e62e]{display:inline-block;vertical-align:middle;margin-left:2px;font-size:14px;transform:rotate(0);transition:transform .25s}@media (min-width: 960px){.VPLocalNavOutlineDropdown button[data-v-17a5e62e]{font-size:14px}.icon[data-v-17a5e62e]{font-size:16px}}.open>.icon[data-v-17a5e62e]{transform:rotate(90deg)}.items[data-v-17a5e62e]{position:absolute;top:40px;right:16px;left:16px;display:grid;gap:1px;border:1px solid var(--vp-c-border);border-radius:8px;background-color:var(--vp-c-gutter);max-height:calc(var(--vp-vh, 100vh) - 86px);overflow:hidden auto;box-shadow:var(--vp-shadow-3)}@media (min-width: 960px){.items[data-v-17a5e62e]{right:auto;left:calc(var(--vp-sidebar-width) + 32px);width:320px}}.header[data-v-17a5e62e]{background-color:var(--vp-c-bg-soft)}.top-link[data-v-17a5e62e]{display:block;padding:0 16px;line-height:48px;font-size:14px;font-weight:500;color:var(--vp-c-brand-1)}.outline[data-v-17a5e62e]{padding:8px 0;background-color:var(--vp-c-bg-soft)}.flyout-enter-active[data-v-17a5e62e]{transition:all .2s ease-out}.flyout-leave-active[data-v-17a5e62e]{transition:all .15s ease-in}.flyout-enter-from[data-v-17a5e62e],.flyout-leave-to[data-v-17a5e62e]{opacity:0;transform:translateY(-16px)}.VPLocalNav[data-v-a6f0e41e]{position:sticky;top:0;left:0;z-index:var(--vp-z-index-local-nav);border-bottom:1px solid var(--vp-c-gutter);padding-top:var(--vp-layout-top-height, 0px);width:100%;background-color:var(--vp-local-nav-bg-color)}.VPLocalNav.fixed[data-v-a6f0e41e]{position:fixed}@media (min-width: 960px){.VPLocalNav[data-v-a6f0e41e]{top:var(--vp-nav-height)}.VPLocalNav.has-sidebar[data-v-a6f0e41e]{padding-left:var(--vp-sidebar-width)}.VPLocalNav.empty[data-v-a6f0e41e]{display:none}}@media (min-width: 1280px){.VPLocalNav[data-v-a6f0e41e]{display:none}}@media (min-width: 1440px){.VPLocalNav.has-sidebar[data-v-a6f0e41e]{padding-left:calc((100vw - var(--vp-layout-max-width)) / 2 + var(--vp-sidebar-width))}}.container[data-v-a6f0e41e]{display:flex;justify-content:space-between;align-items:center}.menu[data-v-a6f0e41e]{display:flex;align-items:center;padding:12px 24px 11px;line-height:24px;font-size:12px;font-weight:500;color:var(--vp-c-text-2);transition:color .5s}.menu[data-v-a6f0e41e]:hover{color:var(--vp-c-text-1);transition:color .25s}@media (min-width: 768px){.menu[data-v-a6f0e41e]{padding:0 32px}}@media (min-width: 960px){.menu[data-v-a6f0e41e]{display:none}}.menu-icon[data-v-a6f0e41e]{margin-right:8px;font-size:14px}.VPOutlineDropdown[data-v-a6f0e41e]{padding:12px 24px 11px}@media (min-width: 768px){.VPOutlineDropdown[data-v-a6f0e41e]{padding:12px 32px 11px}}.VPSwitch[data-v-1d5665e3]{position:relative;border-radius:11px;display:block;width:40px;height:22px;flex-shrink:0;border:1px solid var(--vp-input-border-color);background-color:var(--vp-input-switch-bg-color);transition:border-color .25s!important}.VPSwitch[data-v-1d5665e3]:hover{border-color:var(--vp-c-brand-1)}.check[data-v-1d5665e3]{position:absolute;top:1px;left:1px;width:18px;height:18px;border-radius:50%;background-color:var(--vp-c-neutral-inverse);box-shadow:var(--vp-shadow-1);transition:transform .25s!important}.icon[data-v-1d5665e3]{position:relative;display:block;width:18px;height:18px;border-radius:50%;overflow:hidden}.icon[data-v-1d5665e3] [class^=vpi-]{position:absolute;top:3px;left:3px;width:12px;height:12px;color:var(--vp-c-text-2)}.dark .icon[data-v-1d5665e3] [class^=vpi-]{color:var(--vp-c-text-1);transition:opacity .25s!important}.sun[data-v-d1f28634]{opacity:1}.moon[data-v-d1f28634],.dark .sun[data-v-d1f28634]{opacity:0}.dark .moon[data-v-d1f28634]{opacity:1}.dark .VPSwitchAppearance[data-v-d1f28634] .check{transform:translate(18px)}.VPNavBarAppearance[data-v-e6aabb21]{display:none}@media (min-width: 1280px){.VPNavBarAppearance[data-v-e6aabb21]{display:flex;align-items:center}}.VPMenuGroup+.VPMenuLink[data-v-43f1e123]{margin:12px -12px 0;border-top:1px solid var(--vp-c-divider);padding:12px 12px 0}.link[data-v-43f1e123]{display:block;border-radius:6px;padding:0 12px;line-height:32px;font-size:14px;font-weight:500;color:var(--vp-c-text-1);white-space:nowrap;transition:background-color .25s,color .25s}.link[data-v-43f1e123]:hover{color:var(--vp-c-brand-1);background-color:var(--vp-c-default-soft)}.link.active[data-v-43f1e123]{color:var(--vp-c-brand-1)}.VPMenuGroup[data-v-69e747b5]{margin:12px -12px 0;border-top:1px solid var(--vp-c-divider);padding:12px 12px 0}.VPMenuGroup[data-v-69e747b5]:first-child{margin-top:0;border-top:0;padding-top:0}.VPMenuGroup+.VPMenuGroup[data-v-69e747b5]{margin-top:12px;border-top:1px solid var(--vp-c-divider)}.title[data-v-69e747b5]{padding:0 12px;line-height:32px;font-size:14px;font-weight:600;color:var(--vp-c-text-2);white-space:nowrap;transition:color .25s}.VPMenu[data-v-e7ea1737]{border-radius:12px;padding:12px;min-width:128px;border:1px solid var(--vp-c-divider);background-color:var(--vp-c-bg-elv);box-shadow:var(--vp-shadow-3);transition:background-color .5s;max-height:calc(100vh - var(--vp-nav-height));overflow-y:auto}.VPMenu[data-v-e7ea1737] .group{margin:0 -12px;padding:0 12px 12px}.VPMenu[data-v-e7ea1737] .group+.group{border-top:1px solid var(--vp-c-divider);padding:11px 12px 12px}.VPMenu[data-v-e7ea1737] .group:last-child{padding-bottom:0}.VPMenu[data-v-e7ea1737] .group+.item{border-top:1px solid var(--vp-c-divider);padding:11px 16px 0}.VPMenu[data-v-e7ea1737] .item{padding:0 16px;white-space:nowrap}.VPMenu[data-v-e7ea1737] .label{flex-grow:1;line-height:28px;font-size:12px;font-weight:500;color:var(--vp-c-text-2);transition:color .5s}.VPMenu[data-v-e7ea1737] .action{padding-left:24px}.VPFlyout[data-v-b6c34ac9]{position:relative}.VPFlyout[data-v-b6c34ac9]:hover{color:var(--vp-c-brand-1);transition:color .25s}.VPFlyout:hover .text[data-v-b6c34ac9]{color:var(--vp-c-text-2)}.VPFlyout:hover .icon[data-v-b6c34ac9]{fill:var(--vp-c-text-2)}.VPFlyout.active .text[data-v-b6c34ac9]{color:var(--vp-c-brand-1)}.VPFlyout.active:hover .text[data-v-b6c34ac9]{color:var(--vp-c-brand-2)}.VPFlyout:hover .menu[data-v-b6c34ac9],.button[aria-expanded=true]+.menu[data-v-b6c34ac9]{opacity:1;visibility:visible;transform:translateY(0)}.button[aria-expanded=false]+.menu[data-v-b6c34ac9]{opacity:0;visibility:hidden;transform:translateY(0)}.button[data-v-b6c34ac9]{display:flex;align-items:center;padding:0 12px;height:var(--vp-nav-height);color:var(--vp-c-text-1);transition:color .5s}.text[data-v-b6c34ac9]{display:flex;align-items:center;line-height:var(--vp-nav-height);font-size:14px;font-weight:500;color:var(--vp-c-text-1);transition:color .25s}.option-icon[data-v-b6c34ac9]{margin-right:0;font-size:16px}.text-icon[data-v-b6c34ac9]{margin-left:4px;font-size:14px}.icon[data-v-b6c34ac9]{font-size:20px;transition:fill .25s}.menu[data-v-b6c34ac9]{position:absolute;top:calc(var(--vp-nav-height) / 2 + 20px);right:0;opacity:0;visibility:hidden;transition:opacity .25s,visibility .25s,transform .25s}.VPSocialLink[data-v-eee4e7cb]{display:flex;justify-content:center;align-items:center;width:36px;height:36px;color:var(--vp-c-text-2);transition:color .5s}.VPSocialLink[data-v-eee4e7cb]:hover{color:var(--vp-c-text-1);transition:color .25s}.VPSocialLink[data-v-eee4e7cb]>svg,.VPSocialLink[data-v-eee4e7cb]>[class^=vpi-social-]{width:20px;height:20px;fill:currentColor}.VPSocialLinks[data-v-7bc22406]{display:flex;justify-content:center}.VPNavBarExtra[data-v-d0bd9dde]{display:none;margin-right:-12px}@media (min-width: 768px){.VPNavBarExtra[data-v-d0bd9dde]{display:block}}@media (min-width: 1280px){.VPNavBarExtra[data-v-d0bd9dde]{display:none}}.trans-title[data-v-d0bd9dde]{padding:0 24px 0 12px;line-height:32px;font-size:14px;font-weight:700;color:var(--vp-c-text-1)}.item.appearance[data-v-d0bd9dde],.item.social-links[data-v-d0bd9dde]{display:flex;align-items:center;padding:0 12px}.item.appearance[data-v-d0bd9dde]{min-width:176px}.appearance-action[data-v-d0bd9dde]{margin-right:-2px}.social-links-list[data-v-d0bd9dde]{margin:-4px -8px}.VPNavBarHamburger[data-v-e5dd9c1c]{display:flex;justify-content:center;align-items:center;width:48px;height:var(--vp-nav-height)}@media (min-width: 768px){.VPNavBarHamburger[data-v-e5dd9c1c]{display:none}}.container[data-v-e5dd9c1c]{position:relative;width:16px;height:14px;overflow:hidden}.VPNavBarHamburger:hover .top[data-v-e5dd9c1c]{top:0;left:0;transform:translate(4px)}.VPNavBarHamburger:hover .middle[data-v-e5dd9c1c]{top:6px;left:0;transform:translate(0)}.VPNavBarHamburger:hover .bottom[data-v-e5dd9c1c]{top:12px;left:0;transform:translate(8px)}.VPNavBarHamburger.active .top[data-v-e5dd9c1c]{top:6px;transform:translate(0) rotate(225deg)}.VPNavBarHamburger.active .middle[data-v-e5dd9c1c]{top:6px;transform:translate(16px)}.VPNavBarHamburger.active .bottom[data-v-e5dd9c1c]{top:6px;transform:translate(0) rotate(135deg)}.VPNavBarHamburger.active:hover .top[data-v-e5dd9c1c],.VPNavBarHamburger.active:hover .middle[data-v-e5dd9c1c],.VPNavBarHamburger.active:hover .bottom[data-v-e5dd9c1c]{background-color:var(--vp-c-text-2);transition:top .25s,background-color .25s,transform .25s}.top[data-v-e5dd9c1c],.middle[data-v-e5dd9c1c],.bottom[data-v-e5dd9c1c]{position:absolute;width:16px;height:2px;background-color:var(--vp-c-text-1);transition:top .25s,background-color .5s,transform .25s}.top[data-v-e5dd9c1c]{top:0;left:0;transform:translate(0)}.middle[data-v-e5dd9c1c]{top:6px;left:0;transform:translate(8px)}.bottom[data-v-e5dd9c1c]{top:12px;left:0;transform:translate(4px)}.VPNavBarMenuLink[data-v-9c663999]{display:flex;align-items:center;padding:0 12px;line-height:var(--vp-nav-height);font-size:14px;font-weight:500;color:var(--vp-c-text-1);transition:color .25s}.VPNavBarMenuLink.active[data-v-9c663999],.VPNavBarMenuLink[data-v-9c663999]:hover{color:var(--vp-c-brand-1)}.VPNavBarMenu[data-v-7f418b0f]{display:none}@media (min-width: 768px){.VPNavBarMenu[data-v-7f418b0f]{display:flex}}/*! @docsearch/css 3.6.0 | MIT License | © Algolia, Inc. and contributors | https://docsearch.algolia.com */:root{--docsearch-primary-color:#5468ff;--docsearch-text-color:#1c1e21;--docsearch-spacing:12px;--docsearch-icon-stroke-width:1.4;--docsearch-highlight-color:var(--docsearch-primary-color);--docsearch-muted-color:#969faf;--docsearch-container-background:rgba(101,108,133,.8);--docsearch-logo-color:#5468ff;--docsearch-modal-width:560px;--docsearch-modal-height:600px;--docsearch-modal-background:#f5f6f7;--docsearch-modal-shadow:inset 1px 1px 0 0 hsla(0,0%,100%,.5),0 3px 8px 0 #555a64;--docsearch-searchbox-height:56px;--docsearch-searchbox-background:#ebedf0;--docsearch-searchbox-focus-background:#fff;--docsearch-searchbox-shadow:inset 0 0 0 2px var(--docsearch-primary-color);--docsearch-hit-height:56px;--docsearch-hit-color:#444950;--docsearch-hit-active-color:#fff;--docsearch-hit-background:#fff;--docsearch-hit-shadow:0 1px 3px 0 #d4d9e1;--docsearch-key-gradient:linear-gradient(-225deg,#d5dbe4,#f8f8f8);--docsearch-key-shadow:inset 0 -2px 0 0 #cdcde6,inset 0 0 1px 1px #fff,0 1px 2px 1px rgba(30,35,90,.4);--docsearch-key-pressed-shadow:inset 0 -2px 0 0 #cdcde6,inset 0 0 1px 1px #fff,0 1px 1px 0 rgba(30,35,90,.4);--docsearch-footer-height:44px;--docsearch-footer-background:#fff;--docsearch-footer-shadow:0 -1px 0 0 #e0e3e8,0 -3px 6px 0 rgba(69,98,155,.12)}html[data-theme=dark]{--docsearch-text-color:#f5f6f7;--docsearch-container-background:rgba(9,10,17,.8);--docsearch-modal-background:#15172a;--docsearch-modal-shadow:inset 1px 1px 0 0 #2c2e40,0 3px 8px 0 #000309;--docsearch-searchbox-background:#090a11;--docsearch-searchbox-focus-background:#000;--docsearch-hit-color:#bec3c9;--docsearch-hit-shadow:none;--docsearch-hit-background:#090a11;--docsearch-key-gradient:linear-gradient(-26.5deg,#565872,#31355b);--docsearch-key-shadow:inset 0 -2px 0 0 #282d55,inset 0 0 1px 1px #51577d,0 2px 2px 0 rgba(3,4,9,.3);--docsearch-key-pressed-shadow:inset 0 -2px 0 0 #282d55,inset 0 0 1px 1px #51577d,0 1px 1px 0 rgba(3,4,9,.30196078431372547);--docsearch-footer-background:#1e2136;--docsearch-footer-shadow:inset 0 1px 0 0 rgba(73,76,106,.5),0 -4px 8px 0 rgba(0,0,0,.2);--docsearch-logo-color:#fff;--docsearch-muted-color:#7f8497}.DocSearch-Button{align-items:center;background:var(--docsearch-searchbox-background);border:0;border-radius:40px;color:var(--docsearch-muted-color);cursor:pointer;display:flex;font-weight:500;height:36px;justify-content:space-between;margin:0 0 0 16px;padding:0 8px;-webkit-user-select:none;user-select:none}.DocSearch-Button:active,.DocSearch-Button:focus,.DocSearch-Button:hover{background:var(--docsearch-searchbox-focus-background);box-shadow:var(--docsearch-searchbox-shadow);color:var(--docsearch-text-color);outline:none}.DocSearch-Button-Container{align-items:center;display:flex}.DocSearch-Search-Icon{stroke-width:1.6}.DocSearch-Button .DocSearch-Search-Icon{color:var(--docsearch-text-color)}.DocSearch-Button-Placeholder{font-size:1rem;padding:0 12px 0 6px}.DocSearch-Button-Keys{display:flex;min-width:calc(40px + .8em)}.DocSearch-Button-Key{align-items:center;background:var(--docsearch-key-gradient);border-radius:3px;box-shadow:var(--docsearch-key-shadow);color:var(--docsearch-muted-color);display:flex;height:18px;justify-content:center;margin-right:.4em;position:relative;padding:0 0 2px;border:0;top:-1px;width:20px}.DocSearch-Button-Key--pressed{transform:translate3d(0,1px,0);box-shadow:var(--docsearch-key-pressed-shadow)}@media (max-width:768px){.DocSearch-Button-Keys,.DocSearch-Button-Placeholder{display:none}}.DocSearch--active{overflow:hidden!important}.DocSearch-Container,.DocSearch-Container *{box-sizing:border-box}.DocSearch-Container{background-color:var(--docsearch-container-background);height:100vh;left:0;position:fixed;top:0;width:100vw;z-index:200}.DocSearch-Container a{text-decoration:none}.DocSearch-Link{-webkit-appearance:none;-moz-appearance:none;appearance:none;background:none;border:0;color:var(--docsearch-highlight-color);cursor:pointer;font:inherit;margin:0;padding:0}.DocSearch-Modal{background:var(--docsearch-modal-background);border-radius:6px;box-shadow:var(--docsearch-modal-shadow);flex-direction:column;margin:60px auto auto;max-width:var(--docsearch-modal-width);position:relative}.DocSearch-SearchBar{display:flex;padding:var(--docsearch-spacing) var(--docsearch-spacing) 0}.DocSearch-Form{align-items:center;background:var(--docsearch-searchbox-focus-background);border-radius:4px;box-shadow:var(--docsearch-searchbox-shadow);display:flex;height:var(--docsearch-searchbox-height);margin:0;padding:0 var(--docsearch-spacing);position:relative;width:100%}.DocSearch-Input{-webkit-appearance:none;-moz-appearance:none;appearance:none;background:transparent;border:0;color:var(--docsearch-text-color);flex:1;font:inherit;font-size:1.2em;height:100%;outline:none;padding:0 0 0 8px;width:80%}.DocSearch-Input::placeholder{color:var(--docsearch-muted-color);opacity:1}.DocSearch-Input::-webkit-search-cancel-button,.DocSearch-Input::-webkit-search-decoration,.DocSearch-Input::-webkit-search-results-button,.DocSearch-Input::-webkit-search-results-decoration{display:none}.DocSearch-LoadingIndicator,.DocSearch-MagnifierLabel,.DocSearch-Reset{margin:0;padding:0}.DocSearch-MagnifierLabel,.DocSearch-Reset{align-items:center;color:var(--docsearch-highlight-color);display:flex;justify-content:center}.DocSearch-Container--Stalled .DocSearch-MagnifierLabel,.DocSearch-LoadingIndicator{display:none}.DocSearch-Container--Stalled .DocSearch-LoadingIndicator{align-items:center;color:var(--docsearch-highlight-color);display:flex;justify-content:center}@media screen and (prefers-reduced-motion:reduce){.DocSearch-Reset{animation:none;-webkit-appearance:none;-moz-appearance:none;appearance:none;background:none;border:0;border-radius:50%;color:var(--docsearch-icon-color);cursor:pointer;right:0;stroke-width:var(--docsearch-icon-stroke-width)}}.DocSearch-Reset{animation:fade-in .1s ease-in forwards;-webkit-appearance:none;-moz-appearance:none;appearance:none;background:none;border:0;border-radius:50%;color:var(--docsearch-icon-color);cursor:pointer;padding:2px;right:0;stroke-width:var(--docsearch-icon-stroke-width)}.DocSearch-Reset[hidden]{display:none}.DocSearch-Reset:hover{color:var(--docsearch-highlight-color)}.DocSearch-LoadingIndicator svg,.DocSearch-MagnifierLabel svg{height:24px;width:24px}.DocSearch-Cancel{display:none}.DocSearch-Dropdown{max-height:calc(var(--docsearch-modal-height) - var(--docsearch-searchbox-height) - var(--docsearch-spacing) - var(--docsearch-footer-height));min-height:var(--docsearch-spacing);overflow-y:auto;overflow-y:overlay;padding:0 var(--docsearch-spacing);scrollbar-color:var(--docsearch-muted-color) var(--docsearch-modal-background);scrollbar-width:thin}.DocSearch-Dropdown::-webkit-scrollbar{width:12px}.DocSearch-Dropdown::-webkit-scrollbar-track{background:transparent}.DocSearch-Dropdown::-webkit-scrollbar-thumb{background-color:var(--docsearch-muted-color);border:3px solid var(--docsearch-modal-background);border-radius:20px}.DocSearch-Dropdown ul{list-style:none;margin:0;padding:0}.DocSearch-Label{font-size:.75em;line-height:1.6em}.DocSearch-Help,.DocSearch-Label{color:var(--docsearch-muted-color)}.DocSearch-Help{font-size:.9em;margin:0;-webkit-user-select:none;user-select:none}.DocSearch-Title{font-size:1.2em}.DocSearch-Logo a{display:flex}.DocSearch-Logo svg{color:var(--docsearch-logo-color);margin-left:8px}.DocSearch-Hits:last-of-type{margin-bottom:24px}.DocSearch-Hits mark{background:none;color:var(--docsearch-highlight-color)}.DocSearch-HitsFooter{color:var(--docsearch-muted-color);display:flex;font-size:.85em;justify-content:center;margin-bottom:var(--docsearch-spacing);padding:var(--docsearch-spacing)}.DocSearch-HitsFooter a{border-bottom:1px solid;color:inherit}.DocSearch-Hit{border-radius:4px;display:flex;padding-bottom:4px;position:relative}@media screen and (prefers-reduced-motion:reduce){.DocSearch-Hit--deleting{transition:none}}.DocSearch-Hit--deleting{opacity:0;transition:all .25s linear}@media screen and (prefers-reduced-motion:reduce){.DocSearch-Hit--favoriting{transition:none}}.DocSearch-Hit--favoriting{transform:scale(0);transform-origin:top center;transition:all .25s linear;transition-delay:.25s}.DocSearch-Hit a{background:var(--docsearch-hit-background);border-radius:4px;box-shadow:var(--docsearch-hit-shadow);display:block;padding-left:var(--docsearch-spacing);width:100%}.DocSearch-Hit-source{background:var(--docsearch-modal-background);color:var(--docsearch-highlight-color);font-size:.85em;font-weight:600;line-height:32px;margin:0 -4px;padding:8px 4px 0;position:sticky;top:0;z-index:10}.DocSearch-Hit-Tree{color:var(--docsearch-muted-color);height:var(--docsearch-hit-height);opacity:.5;stroke-width:var(--docsearch-icon-stroke-width);width:24px}.DocSearch-Hit[aria-selected=true] a{background-color:var(--docsearch-highlight-color)}.DocSearch-Hit[aria-selected=true] mark{text-decoration:underline}.DocSearch-Hit-Container{align-items:center;color:var(--docsearch-hit-color);display:flex;flex-direction:row;height:var(--docsearch-hit-height);padding:0 var(--docsearch-spacing) 0 0}.DocSearch-Hit-icon{height:20px;width:20px}.DocSearch-Hit-action,.DocSearch-Hit-icon{color:var(--docsearch-muted-color);stroke-width:var(--docsearch-icon-stroke-width)}.DocSearch-Hit-action{align-items:center;display:flex;height:22px;width:22px}.DocSearch-Hit-action svg{display:block;height:18px;width:18px}.DocSearch-Hit-action+.DocSearch-Hit-action{margin-left:6px}.DocSearch-Hit-action-button{-webkit-appearance:none;-moz-appearance:none;appearance:none;background:none;border:0;border-radius:50%;color:inherit;cursor:pointer;padding:2px}svg.DocSearch-Hit-Select-Icon{display:none}.DocSearch-Hit[aria-selected=true] .DocSearch-Hit-Select-Icon{display:block}.DocSearch-Hit-action-button:focus,.DocSearch-Hit-action-button:hover{background:#0003;transition:background-color .1s ease-in}@media screen and (prefers-reduced-motion:reduce){.DocSearch-Hit-action-button:focus,.DocSearch-Hit-action-button:hover{transition:none}}.DocSearch-Hit-action-button:focus path,.DocSearch-Hit-action-button:hover path{fill:#fff}.DocSearch-Hit-content-wrapper{display:flex;flex:1 1 auto;flex-direction:column;font-weight:500;justify-content:center;line-height:1.2em;margin:0 8px;overflow-x:hidden;position:relative;text-overflow:ellipsis;white-space:nowrap;width:80%}.DocSearch-Hit-title{font-size:.9em}.DocSearch-Hit-path{color:var(--docsearch-muted-color);font-size:.75em}.DocSearch-Hit[aria-selected=true] .DocSearch-Hit-action,.DocSearch-Hit[aria-selected=true] .DocSearch-Hit-icon,.DocSearch-Hit[aria-selected=true] .DocSearch-Hit-path,.DocSearch-Hit[aria-selected=true] .DocSearch-Hit-text,.DocSearch-Hit[aria-selected=true] .DocSearch-Hit-title,.DocSearch-Hit[aria-selected=true] .DocSearch-Hit-Tree,.DocSearch-Hit[aria-selected=true] mark{color:var(--docsearch-hit-active-color)!important}@media screen and (prefers-reduced-motion:reduce){.DocSearch-Hit-action-button:focus,.DocSearch-Hit-action-button:hover{background:#0003;transition:none}}.DocSearch-ErrorScreen,.DocSearch-NoResults,.DocSearch-StartScreen{font-size:.9em;margin:0 auto;padding:36px 0;text-align:center;width:80%}.DocSearch-Screen-Icon{color:var(--docsearch-muted-color);padding-bottom:12px}.DocSearch-NoResults-Prefill-List{display:inline-block;padding-bottom:24px;text-align:left}.DocSearch-NoResults-Prefill-List ul{display:inline-block;padding:8px 0 0}.DocSearch-NoResults-Prefill-List li{list-style-position:inside;list-style-type:"» "}.DocSearch-Prefill{-webkit-appearance:none;-moz-appearance:none;appearance:none;background:none;border:0;border-radius:1em;color:var(--docsearch-highlight-color);cursor:pointer;display:inline-block;font-size:1em;font-weight:700;padding:0}.DocSearch-Prefill:focus,.DocSearch-Prefill:hover{outline:none;text-decoration:underline}.DocSearch-Footer{align-items:center;background:var(--docsearch-footer-background);border-radius:0 0 8px 8px;box-shadow:var(--docsearch-footer-shadow);display:flex;flex-direction:row-reverse;flex-shrink:0;height:var(--docsearch-footer-height);justify-content:space-between;padding:0 var(--docsearch-spacing);position:relative;-webkit-user-select:none;user-select:none;width:100%;z-index:300}.DocSearch-Commands{color:var(--docsearch-muted-color);display:flex;list-style:none;margin:0;padding:0}.DocSearch-Commands li{align-items:center;display:flex}.DocSearch-Commands li:not(:last-of-type){margin-right:.8em}.DocSearch-Commands-Key{align-items:center;background:var(--docsearch-key-gradient);border-radius:2px;box-shadow:var(--docsearch-key-shadow);display:flex;height:18px;justify-content:center;margin-right:.4em;padding:0 0 1px;color:var(--docsearch-muted-color);border:0;width:20px}.DocSearch-VisuallyHiddenForAccessibility{clip:rect(0 0 0 0);clip-path:inset(50%);height:1px;overflow:hidden;position:absolute;white-space:nowrap;width:1px}@media (max-width:768px){:root{--docsearch-spacing:10px;--docsearch-footer-height:40px}.DocSearch-Dropdown{height:100%}.DocSearch-Container{height:100vh;height:-webkit-fill-available;height:calc(var(--docsearch-vh, 1vh)*100);position:absolute}.DocSearch-Footer{border-radius:0;bottom:0;position:absolute}.DocSearch-Hit-content-wrapper{display:flex;position:relative;width:80%}.DocSearch-Modal{border-radius:0;box-shadow:none;height:100vh;height:-webkit-fill-available;height:calc(var(--docsearch-vh, 1vh)*100);margin:0;max-width:100%;width:100%}.DocSearch-Dropdown{max-height:calc(var(--docsearch-vh, 1vh)*100 - var(--docsearch-searchbox-height) - var(--docsearch-spacing) - var(--docsearch-footer-height))}.DocSearch-Cancel{-webkit-appearance:none;-moz-appearance:none;appearance:none;background:none;border:0;color:var(--docsearch-highlight-color);cursor:pointer;display:inline-block;flex:none;font:inherit;font-size:1em;font-weight:500;margin-left:var(--docsearch-spacing);outline:none;overflow:hidden;padding:0;-webkit-user-select:none;user-select:none;white-space:nowrap}.DocSearch-Commands,.DocSearch-Hit-Tree{display:none}}@keyframes fade-in{0%{opacity:0}to{opacity:1}}[class*=DocSearch]{--docsearch-primary-color: var(--vp-c-brand-1);--docsearch-highlight-color: var(--docsearch-primary-color);--docsearch-text-color: var(--vp-c-text-1);--docsearch-muted-color: var(--vp-c-text-2);--docsearch-searchbox-shadow: none;--docsearch-searchbox-background: transparent;--docsearch-searchbox-focus-background: transparent;--docsearch-key-gradient: transparent;--docsearch-key-shadow: none;--docsearch-modal-background: var(--vp-c-bg-soft);--docsearch-footer-background: var(--vp-c-bg)}.dark [class*=DocSearch]{--docsearch-modal-shadow: none;--docsearch-footer-shadow: none;--docsearch-logo-color: var(--vp-c-text-2);--docsearch-hit-background: var(--vp-c-default-soft);--docsearch-hit-color: var(--vp-c-text-2);--docsearch-hit-shadow: none}.DocSearch-Button{display:flex;justify-content:center;align-items:center;margin:0;padding:0;width:48px;height:55px;background:transparent;transition:border-color .25s}.DocSearch-Button:hover{background:transparent}.DocSearch-Button:focus{outline:1px dotted;outline:5px auto -webkit-focus-ring-color}.DocSearch-Button-Key--pressed{transform:none;box-shadow:none}.DocSearch-Button:focus:not(:focus-visible){outline:none!important}@media (min-width: 768px){.DocSearch-Button{justify-content:flex-start;border:1px solid transparent;border-radius:8px;padding:0 10px 0 12px;width:100%;height:40px;background-color:var(--vp-c-bg-alt)}.DocSearch-Button:hover{border-color:var(--vp-c-brand-1);background:var(--vp-c-bg-alt)}}.DocSearch-Button .DocSearch-Button-Container{display:flex;align-items:center}.DocSearch-Button .DocSearch-Search-Icon{position:relative;width:16px;height:16px;color:var(--vp-c-text-1);fill:currentColor;transition:color .5s}.DocSearch-Button:hover .DocSearch-Search-Icon{color:var(--vp-c-text-1)}@media (min-width: 768px){.DocSearch-Button .DocSearch-Search-Icon{top:1px;margin-right:8px;width:14px;height:14px;color:var(--vp-c-text-2)}}.DocSearch-Button .DocSearch-Button-Placeholder{display:none;margin-top:2px;padding:0 16px 0 0;font-size:13px;font-weight:500;color:var(--vp-c-text-2);transition:color .5s}.DocSearch-Button:hover .DocSearch-Button-Placeholder{color:var(--vp-c-text-1)}@media (min-width: 768px){.DocSearch-Button .DocSearch-Button-Placeholder{display:inline-block}}.DocSearch-Button .DocSearch-Button-Keys{direction:ltr;display:none;min-width:auto}@media (min-width: 768px){.DocSearch-Button .DocSearch-Button-Keys{display:flex;align-items:center}}.DocSearch-Button .DocSearch-Button-Key{display:block;margin:2px 0 0;border:1px solid var(--vp-c-divider);border-right:none;border-radius:4px 0 0 4px;padding-left:6px;min-width:0;width:auto;height:22px;line-height:22px;font-family:var(--vp-font-family-base);font-size:12px;font-weight:500;transition:color .5s,border-color .5s}.DocSearch-Button .DocSearch-Button-Key+.DocSearch-Button-Key{border-right:1px solid var(--vp-c-divider);border-left:none;border-radius:0 4px 4px 0;padding-left:2px;padding-right:6px}.DocSearch-Button .DocSearch-Button-Key:first-child{font-size:0!important}.DocSearch-Button .DocSearch-Button-Key:first-child:after{content:"Ctrl";font-size:12px;letter-spacing:normal;color:var(--docsearch-muted-color)}.mac .DocSearch-Button .DocSearch-Button-Key:first-child:after{content:"⌘"}.DocSearch-Button .DocSearch-Button-Key:first-child>*{display:none}.DocSearch-Search-Icon{--icon: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' stroke-width='1.6' viewBox='0 0 20 20'%3E%3Cpath fill='none' stroke='currentColor' stroke-linecap='round' stroke-linejoin='round' d='m14.386 14.386 4.088 4.088-4.088-4.088A7.533 7.533 0 1 1 3.733 3.733a7.533 7.533 0 0 1 10.653 10.653z'/%3E%3C/svg%3E")}.VPNavBarSearch{display:flex;align-items:center}@media (min-width: 768px){.VPNavBarSearch{flex-grow:1;padding-left:24px}}@media (min-width: 960px){.VPNavBarSearch{padding-left:32px}}.dark .DocSearch-Footer{border-top:1px solid var(--vp-c-divider)}.DocSearch-Form{border:1px solid var(--vp-c-brand-1);background-color:var(--vp-c-white)}.dark .DocSearch-Form{background-color:var(--vp-c-default-soft)}.DocSearch-Screen-Icon>svg{margin:auto}.VPNavBarSocialLinks[data-v-0394ad82]{display:none}@media (min-width: 1280px){.VPNavBarSocialLinks[data-v-0394ad82]{display:flex;align-items:center}}.title[data-v-ab179fa1]{display:flex;align-items:center;border-bottom:1px solid transparent;width:100%;height:var(--vp-nav-height);font-size:16px;font-weight:600;color:var(--vp-c-text-1);transition:opacity .25s}@media (min-width: 960px){.title[data-v-ab179fa1]{flex-shrink:0}.VPNavBarTitle.has-sidebar .title[data-v-ab179fa1]{border-bottom-color:var(--vp-c-divider)}}[data-v-ab179fa1] .logo{margin-right:8px;height:var(--vp-nav-logo-height)}.VPNavBarTranslations[data-v-88af2de4]{display:none}@media (min-width: 1280px){.VPNavBarTranslations[data-v-88af2de4]{display:flex;align-items:center}}.title[data-v-88af2de4]{padding:0 24px 0 12px;line-height:32px;font-size:14px;font-weight:700;color:var(--vp-c-text-1)}.VPNavBar[data-v-ccf7ddec]{position:relative;height:var(--vp-nav-height);pointer-events:none;white-space:nowrap;transition:background-color .5s}.VPNavBar[data-v-ccf7ddec]:not(.home){background-color:var(--vp-nav-bg-color)}@media (min-width: 960px){.VPNavBar[data-v-ccf7ddec]:not(.home){background-color:transparent}.VPNavBar[data-v-ccf7ddec]:not(.has-sidebar):not(.home.top){background-color:var(--vp-nav-bg-color)}}.wrapper[data-v-ccf7ddec]{padding:0 8px 0 24px}@media (min-width: 768px){.wrapper[data-v-ccf7ddec]{padding:0 32px}}@media (min-width: 960px){.VPNavBar.has-sidebar .wrapper[data-v-ccf7ddec]{padding:0}}.container[data-v-ccf7ddec]{display:flex;justify-content:space-between;margin:0 auto;max-width:calc(var(--vp-layout-max-width) - 64px);height:var(--vp-nav-height);pointer-events:none}.container>.title[data-v-ccf7ddec],.container>.content[data-v-ccf7ddec]{pointer-events:none}.container[data-v-ccf7ddec] *{pointer-events:auto}@media (min-width: 960px){.VPNavBar.has-sidebar .container[data-v-ccf7ddec]{max-width:100%}}.title[data-v-ccf7ddec]{flex-shrink:0;height:calc(var(--vp-nav-height) - 1px);transition:background-color .5s}@media (min-width: 960px){.VPNavBar.has-sidebar .title[data-v-ccf7ddec]{position:absolute;top:0;left:0;z-index:2;padding:0 32px;width:var(--vp-sidebar-width);height:var(--vp-nav-height);background-color:transparent}}@media (min-width: 1440px){.VPNavBar.has-sidebar .title[data-v-ccf7ddec]{padding-left:max(32px,calc((100% - (var(--vp-layout-max-width) - 64px)) / 2));width:calc((100% - (var(--vp-layout-max-width) - 64px)) / 2 + var(--vp-sidebar-width) - 32px)}}.content[data-v-ccf7ddec]{flex-grow:1}@media (min-width: 960px){.VPNavBar.has-sidebar .content[data-v-ccf7ddec]{position:relative;z-index:1;padding-right:32px;padding-left:var(--vp-sidebar-width)}}@media (min-width: 1440px){.VPNavBar.has-sidebar .content[data-v-ccf7ddec]{padding-right:calc((100vw - var(--vp-layout-max-width)) / 2 + 32px);padding-left:calc((100vw - var(--vp-layout-max-width)) / 2 + var(--vp-sidebar-width))}}.content-body[data-v-ccf7ddec]{display:flex;justify-content:flex-end;align-items:center;height:var(--vp-nav-height);transition:background-color .5s}@media (min-width: 960px){.VPNavBar:not(.home.top) .content-body[data-v-ccf7ddec]{position:relative;background-color:var(--vp-nav-bg-color)}.VPNavBar:not(.has-sidebar):not(.home.top) .content-body[data-v-ccf7ddec]{background-color:transparent}}@media (max-width: 767px){.content-body[data-v-ccf7ddec]{column-gap:.5rem}}.menu+.translations[data-v-ccf7ddec]:before,.menu+.appearance[data-v-ccf7ddec]:before,.menu+.social-links[data-v-ccf7ddec]:before,.translations+.appearance[data-v-ccf7ddec]:before,.appearance+.social-links[data-v-ccf7ddec]:before{margin-right:8px;margin-left:8px;width:1px;height:24px;background-color:var(--vp-c-divider);content:""}.menu+.appearance[data-v-ccf7ddec]:before,.translations+.appearance[data-v-ccf7ddec]:before{margin-right:16px}.appearance+.social-links[data-v-ccf7ddec]:before{margin-left:16px}.social-links[data-v-ccf7ddec]{margin-right:-8px}.divider[data-v-ccf7ddec]{width:100%;height:1px}@media (min-width: 960px){.VPNavBar.has-sidebar .divider[data-v-ccf7ddec]{padding-left:var(--vp-sidebar-width)}}@media (min-width: 1440px){.VPNavBar.has-sidebar .divider[data-v-ccf7ddec]{padding-left:calc((100vw - var(--vp-layout-max-width)) / 2 + var(--vp-sidebar-width))}}.divider-line[data-v-ccf7ddec]{width:100%;height:1px;transition:background-color .5s}.VPNavBar:not(.home) .divider-line[data-v-ccf7ddec]{background-color:var(--vp-c-gutter)}@media (min-width: 960px){.VPNavBar:not(.home.top) .divider-line[data-v-ccf7ddec]{background-color:var(--vp-c-gutter)}.VPNavBar:not(.has-sidebar):not(.home.top) .divider[data-v-ccf7ddec]{background-color:var(--vp-c-gutter)}}.VPNavScreenAppearance[data-v-2d7af913]{display:flex;justify-content:space-between;align-items:center;border-radius:8px;padding:12px 14px 12px 16px;background-color:var(--vp-c-bg-soft)}.text[data-v-2d7af913]{line-height:24px;font-size:12px;font-weight:500;color:var(--vp-c-text-2)}.VPNavScreenMenuLink[data-v-7f31e1f6]{display:block;border-bottom:1px solid var(--vp-c-divider);padding:12px 0 11px;line-height:24px;font-size:14px;font-weight:500;color:var(--vp-c-text-1);transition:border-color .25s,color .25s}.VPNavScreenMenuLink[data-v-7f31e1f6]:hover{color:var(--vp-c-brand-1)}.VPNavScreenMenuGroupLink[data-v-19976ae1]{display:block;margin-left:12px;line-height:32px;font-size:14px;font-weight:400;color:var(--vp-c-text-1);transition:color .25s}.VPNavScreenMenuGroupLink[data-v-19976ae1]:hover{color:var(--vp-c-brand-1)}.VPNavScreenMenuGroupSection[data-v-8133b170]{display:block}.title[data-v-8133b170]{line-height:32px;font-size:13px;font-weight:700;color:var(--vp-c-text-2);transition:color .25s}.VPNavScreenMenuGroup[data-v-ff6087d4]{border-bottom:1px solid var(--vp-c-divider);height:48px;overflow:hidden;transition:border-color .5s}.VPNavScreenMenuGroup .items[data-v-ff6087d4]{visibility:hidden}.VPNavScreenMenuGroup.open .items[data-v-ff6087d4]{visibility:visible}.VPNavScreenMenuGroup.open[data-v-ff6087d4]{padding-bottom:10px;height:auto}.VPNavScreenMenuGroup.open .button[data-v-ff6087d4]{padding-bottom:6px;color:var(--vp-c-brand-1)}.VPNavScreenMenuGroup.open .button-icon[data-v-ff6087d4]{transform:rotate(45deg)}.button[data-v-ff6087d4]{display:flex;justify-content:space-between;align-items:center;padding:12px 4px 11px 0;width:100%;line-height:24px;font-size:14px;font-weight:500;color:var(--vp-c-text-1);transition:color .25s}.button[data-v-ff6087d4]:hover{color:var(--vp-c-brand-1)}.button-icon[data-v-ff6087d4]{transition:transform .25s}.group[data-v-ff6087d4]:first-child{padding-top:0}.group+.group[data-v-ff6087d4],.group+.item[data-v-ff6087d4]{padding-top:4px}.VPNavScreenTranslations[data-v-858fe1a4]{height:24px;overflow:hidden}.VPNavScreenTranslations.open[data-v-858fe1a4]{height:auto}.title[data-v-858fe1a4]{display:flex;align-items:center;font-size:14px;font-weight:500;color:var(--vp-c-text-1)}.icon[data-v-858fe1a4]{font-size:16px}.icon.lang[data-v-858fe1a4]{margin-right:8px}.icon.chevron[data-v-858fe1a4]{margin-left:4px}.list[data-v-858fe1a4]{padding:4px 0 0 24px}.link[data-v-858fe1a4]{line-height:32px;font-size:13px;color:var(--vp-c-text-1)}.VPNavScreen[data-v-cc5739dd]{position:fixed;top:calc(var(--vp-nav-height) + var(--vp-layout-top-height, 0px) + 1px);right:0;bottom:0;left:0;padding:0 32px;width:100%;background-color:var(--vp-nav-screen-bg-color);overflow-y:auto;transition:background-color .5s;pointer-events:auto}.VPNavScreen.fade-enter-active[data-v-cc5739dd],.VPNavScreen.fade-leave-active[data-v-cc5739dd]{transition:opacity .25s}.VPNavScreen.fade-enter-active .container[data-v-cc5739dd],.VPNavScreen.fade-leave-active .container[data-v-cc5739dd]{transition:transform .25s ease}.VPNavScreen.fade-enter-from[data-v-cc5739dd],.VPNavScreen.fade-leave-to[data-v-cc5739dd]{opacity:0}.VPNavScreen.fade-enter-from .container[data-v-cc5739dd],.VPNavScreen.fade-leave-to .container[data-v-cc5739dd]{transform:translateY(-8px)}@media (min-width: 768px){.VPNavScreen[data-v-cc5739dd]{display:none}}.container[data-v-cc5739dd]{margin:0 auto;padding:24px 0 96px;max-width:288px}.menu+.translations[data-v-cc5739dd],.menu+.appearance[data-v-cc5739dd],.translations+.appearance[data-v-cc5739dd]{margin-top:24px}.menu+.social-links[data-v-cc5739dd]{margin-top:16px}.appearance+.social-links[data-v-cc5739dd]{margin-top:16px}.VPNav[data-v-ae24b3ad]{position:relative;top:var(--vp-layout-top-height, 0px);left:0;z-index:var(--vp-z-index-nav);width:100%;pointer-events:none;transition:background-color .5s}@media (min-width: 960px){.VPNav[data-v-ae24b3ad]{position:fixed}}.VPSidebarItem.level-0[data-v-b8d55f3b]{padding-bottom:24px}.VPSidebarItem.collapsed.level-0[data-v-b8d55f3b]{padding-bottom:10px}.item[data-v-b8d55f3b]{position:relative;display:flex;width:100%}.VPSidebarItem.collapsible>.item[data-v-b8d55f3b]{cursor:pointer}.indicator[data-v-b8d55f3b]{position:absolute;top:6px;bottom:6px;left:-17px;width:2px;border-radius:2px;transition:background-color .25s}.VPSidebarItem.level-2.is-active>.item>.indicator[data-v-b8d55f3b],.VPSidebarItem.level-3.is-active>.item>.indicator[data-v-b8d55f3b],.VPSidebarItem.level-4.is-active>.item>.indicator[data-v-b8d55f3b],.VPSidebarItem.level-5.is-active>.item>.indicator[data-v-b8d55f3b]{background-color:var(--vp-c-brand-1)}.link[data-v-b8d55f3b]{display:flex;align-items:center;flex-grow:1}.text[data-v-b8d55f3b]{flex-grow:1;padding:4px 0;line-height:24px;font-size:14px;transition:color .25s}.VPSidebarItem.level-0 .text[data-v-b8d55f3b]{font-weight:700;color:var(--vp-c-text-1)}.VPSidebarItem.level-1 .text[data-v-b8d55f3b],.VPSidebarItem.level-2 .text[data-v-b8d55f3b],.VPSidebarItem.level-3 .text[data-v-b8d55f3b],.VPSidebarItem.level-4 .text[data-v-b8d55f3b],.VPSidebarItem.level-5 .text[data-v-b8d55f3b]{font-weight:500;color:var(--vp-c-text-2)}.VPSidebarItem.level-0.is-link>.item>.link:hover .text[data-v-b8d55f3b],.VPSidebarItem.level-1.is-link>.item>.link:hover .text[data-v-b8d55f3b],.VPSidebarItem.level-2.is-link>.item>.link:hover .text[data-v-b8d55f3b],.VPSidebarItem.level-3.is-link>.item>.link:hover .text[data-v-b8d55f3b],.VPSidebarItem.level-4.is-link>.item>.link:hover .text[data-v-b8d55f3b],.VPSidebarItem.level-5.is-link>.item>.link:hover .text[data-v-b8d55f3b]{color:var(--vp-c-brand-1)}.VPSidebarItem.level-0.has-active>.item>.text[data-v-b8d55f3b],.VPSidebarItem.level-1.has-active>.item>.text[data-v-b8d55f3b],.VPSidebarItem.level-2.has-active>.item>.text[data-v-b8d55f3b],.VPSidebarItem.level-3.has-active>.item>.text[data-v-b8d55f3b],.VPSidebarItem.level-4.has-active>.item>.text[data-v-b8d55f3b],.VPSidebarItem.level-5.has-active>.item>.text[data-v-b8d55f3b],.VPSidebarItem.level-0.has-active>.item>.link>.text[data-v-b8d55f3b],.VPSidebarItem.level-1.has-active>.item>.link>.text[data-v-b8d55f3b],.VPSidebarItem.level-2.has-active>.item>.link>.text[data-v-b8d55f3b],.VPSidebarItem.level-3.has-active>.item>.link>.text[data-v-b8d55f3b],.VPSidebarItem.level-4.has-active>.item>.link>.text[data-v-b8d55f3b],.VPSidebarItem.level-5.has-active>.item>.link>.text[data-v-b8d55f3b]{color:var(--vp-c-text-1)}.VPSidebarItem.level-0.is-active>.item .link>.text[data-v-b8d55f3b],.VPSidebarItem.level-1.is-active>.item .link>.text[data-v-b8d55f3b],.VPSidebarItem.level-2.is-active>.item .link>.text[data-v-b8d55f3b],.VPSidebarItem.level-3.is-active>.item .link>.text[data-v-b8d55f3b],.VPSidebarItem.level-4.is-active>.item .link>.text[data-v-b8d55f3b],.VPSidebarItem.level-5.is-active>.item .link>.text[data-v-b8d55f3b]{color:var(--vp-c-brand-1)}.caret[data-v-b8d55f3b]{display:flex;justify-content:center;align-items:center;margin-right:-7px;width:32px;height:32px;color:var(--vp-c-text-3);cursor:pointer;transition:color .25s;flex-shrink:0}.item:hover .caret[data-v-b8d55f3b]{color:var(--vp-c-text-2)}.item:hover .caret[data-v-b8d55f3b]:hover{color:var(--vp-c-text-1)}.caret-icon[data-v-b8d55f3b]{font-size:18px;transform:rotate(90deg);transition:transform .25s}.VPSidebarItem.collapsed .caret-icon[data-v-b8d55f3b]{transform:rotate(0)}.VPSidebarItem.level-1 .items[data-v-b8d55f3b],.VPSidebarItem.level-2 .items[data-v-b8d55f3b],.VPSidebarItem.level-3 .items[data-v-b8d55f3b],.VPSidebarItem.level-4 .items[data-v-b8d55f3b],.VPSidebarItem.level-5 .items[data-v-b8d55f3b]{border-left:1px solid var(--vp-c-divider);padding-left:16px}.VPSidebarItem.collapsed .items[data-v-b8d55f3b]{display:none}.VPSidebar[data-v-575e6a36]{position:fixed;top:var(--vp-layout-top-height, 0px);bottom:0;left:0;z-index:var(--vp-z-index-sidebar);padding:32px 32px 96px;width:calc(100vw - 64px);max-width:320px;background-color:var(--vp-sidebar-bg-color);opacity:0;box-shadow:var(--vp-c-shadow-3);overflow-x:hidden;overflow-y:auto;transform:translate(-100%);transition:opacity .5s,transform .25s ease;overscroll-behavior:contain}.VPSidebar.open[data-v-575e6a36]{opacity:1;visibility:visible;transform:translate(0);transition:opacity .25s,transform .5s cubic-bezier(.19,1,.22,1)}.dark .VPSidebar[data-v-575e6a36]{box-shadow:var(--vp-shadow-1)}@media (min-width: 960px){.VPSidebar[data-v-575e6a36]{padding-top:var(--vp-nav-height);width:var(--vp-sidebar-width);max-width:100%;background-color:var(--vp-sidebar-bg-color);opacity:1;visibility:visible;box-shadow:none;transform:translate(0)}}@media (min-width: 1440px){.VPSidebar[data-v-575e6a36]{padding-left:max(32px,calc((100% - (var(--vp-layout-max-width) - 64px)) / 2));width:calc((100% - (var(--vp-layout-max-width) - 64px)) / 2 + var(--vp-sidebar-width) - 32px)}}@media (min-width: 960px){.curtain[data-v-575e6a36]{position:sticky;top:-64px;left:0;z-index:1;margin-top:calc(var(--vp-nav-height) * -1);margin-right:-32px;margin-left:-32px;height:var(--vp-nav-height);background-color:var(--vp-sidebar-bg-color)}}.nav[data-v-575e6a36]{outline:0}.group+.group[data-v-575e6a36]{border-top:1px solid var(--vp-c-divider);padding-top:10px}@media (min-width: 960px){.group[data-v-575e6a36]{padding-top:10px;width:calc(var(--vp-sidebar-width) - 64px)}}.VPSkipLink[data-v-0f60ec36]{top:8px;left:8px;padding:8px 16px;z-index:999;border-radius:8px;font-size:12px;font-weight:700;text-decoration:none;color:var(--vp-c-brand-1);box-shadow:var(--vp-shadow-3);background-color:var(--vp-c-bg)}.VPSkipLink[data-v-0f60ec36]:focus{height:auto;width:auto;clip:auto;clip-path:none}@media (min-width: 1280px){.VPSkipLink[data-v-0f60ec36]{top:14px;left:16px}}.Layout[data-v-5d98c3a5]{display:flex;flex-direction:column;min-height:100vh}.VPHomeSponsors[data-v-3d121b4a]{border-top:1px solid var(--vp-c-gutter);padding-top:88px!important}.VPHomeSponsors[data-v-3d121b4a]{margin:96px 0}@media (min-width: 768px){.VPHomeSponsors[data-v-3d121b4a]{margin:128px 0}}.VPHomeSponsors[data-v-3d121b4a]{padding:0 24px}@media (min-width: 768px){.VPHomeSponsors[data-v-3d121b4a]{padding:0 48px}}@media (min-width: 960px){.VPHomeSponsors[data-v-3d121b4a]{padding:0 64px}}.container[data-v-3d121b4a]{margin:0 auto;max-width:1152px}.love[data-v-3d121b4a]{margin:0 auto;width:fit-content;font-size:28px;color:var(--vp-c-text-3)}.icon[data-v-3d121b4a]{display:inline-block}.message[data-v-3d121b4a]{margin:0 auto;padding-top:10px;max-width:320px;text-align:center;line-height:24px;font-size:16px;font-weight:500;color:var(--vp-c-text-2)}.sponsors[data-v-3d121b4a]{padding-top:32px}.action[data-v-3d121b4a]{padding-top:40px;text-align:center}.VPTeamPage[data-v-7c57f839]{margin:96px 0}@media (min-width: 768px){.VPTeamPage[data-v-7c57f839]{margin:128px 0}}.VPHome .VPTeamPageTitle[data-v-7c57f839-s]{border-top:1px solid var(--vp-c-gutter);padding-top:88px!important}.VPTeamPageSection+.VPTeamPageSection[data-v-7c57f839-s],.VPTeamMembers+.VPTeamPageSection[data-v-7c57f839-s]{margin-top:64px}.VPTeamMembers+.VPTeamMembers[data-v-7c57f839-s]{margin-top:24px}@media (min-width: 768px){.VPTeamPageTitle+.VPTeamPageSection[data-v-7c57f839-s]{margin-top:16px}.VPTeamPageSection+.VPTeamPageSection[data-v-7c57f839-s],.VPTeamMembers+.VPTeamPageSection[data-v-7c57f839-s]{margin-top:96px}}.VPTeamMembers[data-v-7c57f839-s]{padding:0 24px}@media (min-width: 768px){.VPTeamMembers[data-v-7c57f839-s]{padding:0 48px}}@media (min-width: 960px){.VPTeamMembers[data-v-7c57f839-s]{padding:0 64px}}.VPTeamPageTitle[data-v-bf2cbdac]{padding:48px 32px;text-align:center}@media (min-width: 768px){.VPTeamPageTitle[data-v-bf2cbdac]{padding:64px 48px 48px}}@media (min-width: 960px){.VPTeamPageTitle[data-v-bf2cbdac]{padding:80px 64px 48px}}.title[data-v-bf2cbdac]{letter-spacing:0;line-height:44px;font-size:36px;font-weight:500}@media (min-width: 768px){.title[data-v-bf2cbdac]{letter-spacing:-.5px;line-height:56px;font-size:48px}}.lead[data-v-bf2cbdac]{margin:0 auto;max-width:512px;padding-top:12px;line-height:24px;font-size:16px;font-weight:500;color:var(--vp-c-text-2)}@media (min-width: 768px){.lead[data-v-bf2cbdac]{max-width:592px;letter-spacing:.15px;line-height:28px;font-size:20px}}.VPTeamPageSection[data-v-b1a88750]{padding:0 32px}@media (min-width: 768px){.VPTeamPageSection[data-v-b1a88750]{padding:0 48px}}@media (min-width: 960px){.VPTeamPageSection[data-v-b1a88750]{padding:0 64px}}.title[data-v-b1a88750]{position:relative;margin:0 auto;max-width:1152px;text-align:center;color:var(--vp-c-text-2)}.title-line[data-v-b1a88750]{position:absolute;top:16px;left:0;width:100%;height:1px;background-color:var(--vp-c-divider)}.title-text[data-v-b1a88750]{position:relative;display:inline-block;padding:0 24px;letter-spacing:0;line-height:32px;font-size:20px;font-weight:500;background-color:var(--vp-c-bg)}.lead[data-v-b1a88750]{margin:0 auto;max-width:480px;padding-top:12px;text-align:center;line-height:24px;font-size:16px;font-weight:500;color:var(--vp-c-text-2)}.members[data-v-b1a88750]{padding-top:40px}.VPTeamMembersItem[data-v-f3fa364a]{display:flex;flex-direction:column;gap:2px;border-radius:12px;width:100%;height:100%;overflow:hidden}.VPTeamMembersItem.small .profile[data-v-f3fa364a]{padding:32px}.VPTeamMembersItem.small .data[data-v-f3fa364a]{padding-top:20px}.VPTeamMembersItem.small .avatar[data-v-f3fa364a]{width:64px;height:64px}.VPTeamMembersItem.small .name[data-v-f3fa364a]{line-height:24px;font-size:16px}.VPTeamMembersItem.small .affiliation[data-v-f3fa364a]{padding-top:4px;line-height:20px;font-size:14px}.VPTeamMembersItem.small .desc[data-v-f3fa364a]{padding-top:12px;line-height:20px;font-size:14px}.VPTeamMembersItem.small .links[data-v-f3fa364a]{margin:0 -16px -20px;padding:10px 0 0}.VPTeamMembersItem.medium .profile[data-v-f3fa364a]{padding:48px 32px}.VPTeamMembersItem.medium .data[data-v-f3fa364a]{padding-top:24px;text-align:center}.VPTeamMembersItem.medium .avatar[data-v-f3fa364a]{width:96px;height:96px}.VPTeamMembersItem.medium .name[data-v-f3fa364a]{letter-spacing:.15px;line-height:28px;font-size:20px}.VPTeamMembersItem.medium .affiliation[data-v-f3fa364a]{padding-top:4px;font-size:16px}.VPTeamMembersItem.medium .desc[data-v-f3fa364a]{padding-top:16px;max-width:288px;font-size:16px}.VPTeamMembersItem.medium .links[data-v-f3fa364a]{margin:0 -16px -12px;padding:16px 12px 0}.profile[data-v-f3fa364a]{flex-grow:1;background-color:var(--vp-c-bg-soft)}.data[data-v-f3fa364a]{text-align:center}.avatar[data-v-f3fa364a]{position:relative;flex-shrink:0;margin:0 auto;border-radius:50%;box-shadow:var(--vp-shadow-3)}.avatar-img[data-v-f3fa364a]{position:absolute;top:0;right:0;bottom:0;left:0;border-radius:50%;object-fit:cover}.name[data-v-f3fa364a]{margin:0;font-weight:600}.affiliation[data-v-f3fa364a]{margin:0;font-weight:500;color:var(--vp-c-text-2)}.org.link[data-v-f3fa364a]{color:var(--vp-c-text-2);transition:color .25s}.org.link[data-v-f3fa364a]:hover{color:var(--vp-c-brand-1)}.desc[data-v-f3fa364a]{margin:0 auto}.desc[data-v-f3fa364a] a{font-weight:500;color:var(--vp-c-brand-1);text-decoration-style:dotted;transition:color .25s}.links[data-v-f3fa364a]{display:flex;justify-content:center;height:56px}.sp-link[data-v-f3fa364a]{display:flex;justify-content:center;align-items:center;text-align:center;padding:16px;font-size:14px;font-weight:500;color:var(--vp-c-sponsor);background-color:var(--vp-c-bg-soft);transition:color .25s,background-color .25s}.sp .sp-link.link[data-v-f3fa364a]:hover,.sp .sp-link.link[data-v-f3fa364a]:focus{outline:none;color:var(--vp-c-white);background-color:var(--vp-c-sponsor)}.sp-icon[data-v-f3fa364a]{margin-right:8px;font-size:16px}.VPTeamMembers.small .container[data-v-6cb0dbc4]{grid-template-columns:repeat(auto-fit,minmax(224px,1fr))}.VPTeamMembers.small.count-1 .container[data-v-6cb0dbc4]{max-width:276px}.VPTeamMembers.small.count-2 .container[data-v-6cb0dbc4]{max-width:576px}.VPTeamMembers.small.count-3 .container[data-v-6cb0dbc4]{max-width:876px}.VPTeamMembers.medium .container[data-v-6cb0dbc4]{grid-template-columns:repeat(auto-fit,minmax(256px,1fr))}@media (min-width: 375px){.VPTeamMembers.medium .container[data-v-6cb0dbc4]{grid-template-columns:repeat(auto-fit,minmax(288px,1fr))}}.VPTeamMembers.medium.count-1 .container[data-v-6cb0dbc4]{max-width:368px}.VPTeamMembers.medium.count-2 .container[data-v-6cb0dbc4]{max-width:760px}.container[data-v-6cb0dbc4]{display:grid;gap:24px;margin:0 auto;max-width:1152px}@font-face{font-family:Inter;font-style:normal;font-weight:100 900;font-display:swap;src:url(/assets/inter-roman-cyrillic-ext.BBPuwvHQ.woff2) format("woff2");unicode-range:U+0460-052F,U+1C80-1C88,U+20B4,U+2DE0-2DFF,U+A640-A69F,U+FE2E-FE2F}@font-face{font-family:Inter;font-style:normal;font-weight:100 900;font-display:swap;src:url(/assets/inter-roman-cyrillic.C5lxZ8CY.woff2) format("woff2");unicode-range:U+0301,U+0400-045F,U+0490-0491,U+04B0-04B1,U+2116}@font-face{font-family:Inter;font-style:normal;font-weight:100 900;font-display:swap;src:url(/assets/inter-roman-greek-ext.CqjqNYQ-.woff2) format("woff2");unicode-range:U+1F00-1FFF}@font-face{font-family:Inter;font-style:normal;font-weight:100 900;font-display:swap;src:url(/assets/inter-roman-greek.BBVDIX6e.woff2) format("woff2");unicode-range:U+0370-0377,U+037A-037F,U+0384-038A,U+038C,U+038E-03A1,U+03A3-03FF}@font-face{font-family:Inter;font-style:normal;font-weight:100 900;font-display:swap;src:url(/assets/inter-roman-vietnamese.BjW4sHH5.woff2) format("woff2");unicode-range:U+0102-0103,U+0110-0111,U+0128-0129,U+0168-0169,U+01A0-01A1,U+01AF-01B0,U+0300-0301,U+0303-0304,U+0308-0309,U+0323,U+0329,U+1EA0-1EF9,U+20AB}@font-face{font-family:Inter;font-style:normal;font-weight:100 900;font-display:swap;src:url(/assets/inter-roman-latin-ext.4ZJIpNVo.woff2) format("woff2");unicode-range:U+0100-02AF,U+0304,U+0308,U+0329,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:Inter;font-style:normal;font-weight:100 900;font-display:swap;src:url(/assets/inter-roman-latin.Di8DUHzh.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+2074,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}@font-face{font-family:Inter;font-style:italic;font-weight:100 900;font-display:swap;src:url(/assets/inter-italic-cyrillic-ext.r48I6akx.woff2) format("woff2");unicode-range:U+0460-052F,U+1C80-1C88,U+20B4,U+2DE0-2DFF,U+A640-A69F,U+FE2E-FE2F}@font-face{font-family:Inter;font-style:italic;font-weight:100 900;font-display:swap;src:url(/assets/inter-italic-cyrillic.By2_1cv3.woff2) format("woff2");unicode-range:U+0301,U+0400-045F,U+0490-0491,U+04B0-04B1,U+2116}@font-face{font-family:Inter;font-style:italic;font-weight:100 900;font-display:swap;src:url(/assets/inter-italic-greek-ext.1u6EdAuj.woff2) format("woff2");unicode-range:U+1F00-1FFF}@font-face{font-family:Inter;font-style:italic;font-weight:100 900;font-display:swap;src:url(/assets/inter-italic-greek.DJ8dCoTZ.woff2) format("woff2");unicode-range:U+0370-0377,U+037A-037F,U+0384-038A,U+038C,U+038E-03A1,U+03A3-03FF}@font-face{font-family:Inter;font-style:italic;font-weight:100 900;font-display:swap;src:url(/assets/inter-italic-vietnamese.BSbpV94h.woff2) format("woff2");unicode-range:U+0102-0103,U+0110-0111,U+0128-0129,U+0168-0169,U+01A0-01A1,U+01AF-01B0,U+0300-0301,U+0303-0304,U+0308-0309,U+0323,U+0329,U+1EA0-1EF9,U+20AB}@font-face{font-family:Inter;font-style:italic;font-weight:100 900;font-display:swap;src:url(/assets/inter-italic-latin-ext.CN1xVJS-.woff2) format("woff2");unicode-range:U+0100-02AF,U+0304,U+0308,U+0329,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:Inter;font-style:italic;font-weight:100 900;font-display:swap;src:url(/assets/inter-italic-latin.C2AdPX0b.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+2074,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}@font-face{font-family:Punctuation SC;font-weight:400;src:local("PingFang SC Regular"),local("Noto Sans CJK SC"),local("Microsoft YaHei");unicode-range:U+201C,U+201D,U+2018,U+2019,U+2E3A,U+2014,U+2013,U+2026,U+00B7,U+007E,U+002F}@font-face{font-family:Punctuation SC;font-weight:500;src:local("PingFang SC Medium"),local("Noto Sans CJK SC"),local("Microsoft YaHei");unicode-range:U+201C,U+201D,U+2018,U+2019,U+2E3A,U+2014,U+2013,U+2026,U+00B7,U+007E,U+002F}@font-face{font-family:Punctuation SC;font-weight:600;src:local("PingFang SC Semibold"),local("Noto Sans CJK SC Bold"),local("Microsoft YaHei Bold");unicode-range:U+201C,U+201D,U+2018,U+2019,U+2E3A,U+2014,U+2013,U+2026,U+00B7,U+007E,U+002F}@font-face{font-family:Punctuation SC;font-weight:700;src:local("PingFang SC Semibold"),local("Noto Sans CJK SC Bold"),local("Microsoft YaHei Bold");unicode-range:U+201C,U+201D,U+2018,U+2019,U+2E3A,U+2014,U+2013,U+2026,U+00B7,U+007E,U+002F}:root{--vp-nolebase-highlight-targeted-heading-color: var(--vp-custom-block-tip-text);--vp-nolebase-highlight-targeted-heading-bg: var(--vp-custom-block-tip-bg)}@keyframes vp-nolebase-highlight-targeted-heading-animation{0%{background-color:transparent;box-shadow:0 0 0 8px transparent}10%,35%{color:var(--vp-nolebase-highlight-targeted-heading-color);border-color:transparent;border-radius:4px;background-color:var(--vp-nolebase-highlight-targeted-heading-bg);box-shadow:0 0 0 8px var(--vp-nolebase-highlight-targeted-heading-bg)}99%{background-color:transparent;border-radius:4px;box-shadow:0 0 0 8px transparent}to{border-radius:0;background-color:transparent;box-shadow:none}}.VPNolebaseHighlightTargetedHeadingAnimated{animation:vp-nolebase-highlight-targeted-heading-animation 1.5s ease-in-out}*,:before,:after{--un-rotate:0;--un-rotate-x:0;--un-rotate-y:0;--un-rotate-z:0;--un-scale-x:1;--un-scale-y:1;--un-scale-z:1;--un-skew-x:0;--un-skew-y:0;--un-translate-x:0;--un-translate-y:0;--un-translate-z:0;--un-pan-x: ;--un-pan-y: ;--un-pinch-zoom: ;--un-scroll-snap-strictness:proximity;--un-ordinal: ;--un-slashed-zero: ;--un-numeric-figure: ;--un-numeric-spacing: ;--un-numeric-fraction: ;--un-border-spacing-x:0;--un-border-spacing-y:0;--un-ring-offset-shadow:0 0 rgb(0 0 0 / 0);--un-ring-shadow:0 0 rgb(0 0 0 / 0);--un-shadow-inset: ;--un-shadow:0 0 rgb(0 0 0 / 0);--un-ring-inset: ;--un-ring-offset-width:0px;--un-ring-offset-color:#fff;--un-ring-width:0px;--un-ring-color:rgb(147 197 253 / .5);--un-blur: ;--un-brightness: ;--un-contrast: ;--un-drop-shadow: ;--un-grayscale: ;--un-hue-rotate: ;--un-invert: ;--un-saturate: ;--un-sepia: ;--un-backdrop-blur: ;--un-backdrop-brightness: ;--un-backdrop-contrast: ;--un-backdrop-grayscale: ;--un-backdrop-hue-rotate: ;--un-backdrop-invert: ;--un-backdrop-opacity: ;--un-backdrop-saturate: ;--un-backdrop-sepia: }::backdrop{--un-rotate:0;--un-rotate-x:0;--un-rotate-y:0;--un-rotate-z:0;--un-scale-x:1;--un-scale-y:1;--un-scale-z:1;--un-skew-x:0;--un-skew-y:0;--un-translate-x:0;--un-translate-y:0;--un-translate-z:0;--un-pan-x: ;--un-pan-y: ;--un-pinch-zoom: ;--un-scroll-snap-strictness:proximity;--un-ordinal: ;--un-slashed-zero: ;--un-numeric-figure: ;--un-numeric-spacing: ;--un-numeric-fraction: ;--un-border-spacing-x:0;--un-border-spacing-y:0;--un-ring-offset-shadow:0 0 rgb(0 0 0 / 0);--un-ring-shadow:0 0 rgb(0 0 0 / 0);--un-shadow-inset: ;--un-shadow:0 0 rgb(0 0 0 / 0);--un-ring-inset: ;--un-ring-offset-width:0px;--un-ring-offset-color:#fff;--un-ring-width:0px;--un-ring-color:rgb(147 197 253 / .5);--un-blur: ;--un-brightness: ;--un-contrast: ;--un-drop-shadow: ;--un-grayscale: ;--un-hue-rotate: ;--un-invert: ;--un-saturate: ;--un-sepia: ;--un-backdrop-blur: ;--un-backdrop-brightness: ;--un-backdrop-contrast: ;--un-backdrop-grayscale: ;--un-backdrop-hue-rotate: ;--un-backdrop-invert: ;--un-backdrop-opacity: ;--un-backdrop-saturate: ;--un-backdrop-sepia: }@font-face{font-family:"Baloo 2";font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/baloo2/v21/wXK0E3kTposypRydzVT08TS3JnAmtdgazZpp_led7Q.woff2) format("woff2");unicode-range:U+0900-097F,U+1CD0-1CF9,U+200C-200D,U+20A8,U+20B9,U+20F0,U+25CC,U+A830-A839,U+A8E0-A8FF,U+11B00-11B09}@font-face{font-family:"Baloo 2";font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/baloo2/v21/wXK0E3kTposypRydzVT08TS3JnAmtdgazZpn_led7Q.woff2) format("woff2");unicode-range:U+0102-0103,U+0110-0111,U+0128-0129,U+0168-0169,U+01A0-01A1,U+01AF-01B0,U+0300-0301,U+0303-0304,U+0308-0309,U+0323,U+0329,U+1EA0-1EF9,U+20AB}@font-face{font-family:"Baloo 2";font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/baloo2/v21/wXK0E3kTposypRydzVT08TS3JnAmtdgazZpm_led7Q.woff2) format("woff2");unicode-range:U+0100-02AF,U+0304,U+0308,U+0329,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:"Baloo 2";font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/baloo2/v21/wXK0E3kTposypRydzVT08TS3JnAmtdgazZpo_lc.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+2074,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}@font-face{font-family:Chakra Petch;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/chakrapetch/v11/cIf6MapbsEk7TDLdtEz1BwkWi6pgeL4.woff2) format("woff2");unicode-range:U+0E01-0E5B,U+200C-200D,U+25CC}@font-face{font-family:Chakra Petch;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/chakrapetch/v11/cIf6MapbsEk7TDLdtEz1BwkWkKpgeL4.woff2) format("woff2");unicode-range:U+0102-0103,U+0110-0111,U+0128-0129,U+0168-0169,U+01A0-01A1,U+01AF-01B0,U+0300-0301,U+0303-0304,U+0308-0309,U+0323,U+0329,U+1EA0-1EF9,U+20AB}@font-face{font-family:Chakra Petch;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/chakrapetch/v11/cIf6MapbsEk7TDLdtEz1BwkWkapgeL4.woff2) format("woff2");unicode-range:U+0100-02AF,U+0304,U+0308,U+0329,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:Chakra Petch;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/chakrapetch/v11/cIf6MapbsEk7TDLdtEz1BwkWn6pg.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+2074,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}@font-face{font-family:Jura;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/jura/v31/z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZurR_ibHw.woff2) format("woff2");unicode-range:U+0460-052F,U+1C80-1C88,U+20B4,U+2DE0-2DFF,U+A640-A69F,U+FE2E-FE2F}@font-face{font-family:Jura;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/jura/v31/z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZuiR_ibHw.woff2) format("woff2");unicode-range:U+0301,U+0400-045F,U+0490-0491,U+04B0-04B1,U+2116}@font-face{font-family:Jura;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/jura/v31/z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZuqR_ibHw.woff2) format("woff2");unicode-range:U+1F00-1FFF}@font-face{font-family:Jura;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/jura/v31/z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZulR_ibHw.woff2) format("woff2");unicode-range:U+0370-0377,U+037A-037F,U+0384-038A,U+038C,U+038E-03A1,U+03A3-03FF}@font-face{font-family:Jura;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/jura/v31/z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZvuR_ibHw.woff2) format("woff2");unicode-range:U+200C-200D,U+2010,U+25CC,U+A900-A92F}@font-face{font-family:Jura;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/jura/v31/z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZupR_ibHw.woff2) format("woff2");unicode-range:U+0102-0103,U+0110-0111,U+0128-0129,U+0168-0169,U+01A0-01A1,U+01AF-01B0,U+0300-0301,U+0303-0304,U+0308-0309,U+0323,U+0329,U+1EA0-1EF9,U+20AB}@font-face{font-family:Jura;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/jura/v31/z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZuoR_ibHw.woff2) format("woff2");unicode-range:U+0100-02AF,U+0304,U+0308,U+0329,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:Jura;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/jura/v31/z7NOdRfiaC4Vd8hhoPzfb5vBTP1d7ZumR_g.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+2074,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}@font-face{font-family:Noto Sans;font-style:normal;font-weight:400;font-stretch:normal;font-display:swap;src:url(https://fonts.gstatic.com/s/notosans/v36/o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9X6VLKzA.woff2) format("woff2");unicode-range:U+0460-052F,U+1C80-1C88,U+20B4,U+2DE0-2DFF,U+A640-A69F,U+FE2E-FE2F}@font-face{font-family:Noto Sans;font-style:normal;font-weight:400;font-stretch:normal;font-display:swap;src:url(https://fonts.gstatic.com/s/notosans/v36/o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9e6VLKzA.woff2) format("woff2");unicode-range:U+0301,U+0400-045F,U+0490-0491,U+04B0-04B1,U+2116}@font-face{font-family:Noto Sans;font-style:normal;font-weight:400;font-stretch:normal;font-display:swap;src:url(https://fonts.gstatic.com/s/notosans/v36/o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9b6VLKzA.woff2) format("woff2");unicode-range:U+0900-097F,U+1CD0-1CF9,U+200C-200D,U+20A8,U+20B9,U+20F0,U+25CC,U+A830-A839,U+A8E0-A8FF,U+11B00-11B09}@font-face{font-family:Noto Sans;font-style:normal;font-weight:400;font-stretch:normal;font-display:swap;src:url(https://fonts.gstatic.com/s/notosans/v36/o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9W6VLKzA.woff2) format("woff2");unicode-range:U+1F00-1FFF}@font-face{font-family:Noto Sans;font-style:normal;font-weight:400;font-stretch:normal;font-display:swap;src:url(https://fonts.gstatic.com/s/notosans/v36/o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9Z6VLKzA.woff2) format("woff2");unicode-range:U+0370-0377,U+037A-037F,U+0384-038A,U+038C,U+038E-03A1,U+03A3-03FF}@font-face{font-family:Noto Sans;font-style:normal;font-weight:400;font-stretch:normal;font-display:swap;src:url(https://fonts.gstatic.com/s/notosans/v36/o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9V6VLKzA.woff2) format("woff2");unicode-range:U+0102-0103,U+0110-0111,U+0128-0129,U+0168-0169,U+01A0-01A1,U+01AF-01B0,U+0300-0301,U+0303-0304,U+0308-0309,U+0323,U+0329,U+1EA0-1EF9,U+20AB}@font-face{font-family:Noto Sans;font-style:normal;font-weight:400;font-stretch:normal;font-display:swap;src:url(https://fonts.gstatic.com/s/notosans/v36/o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9U6VLKzA.woff2) format("woff2");unicode-range:U+0100-02AF,U+0304,U+0308,U+0329,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:Noto Sans;font-style:normal;font-weight:400;font-stretch:normal;font-display:swap;src:url(https://fonts.gstatic.com/s/notosans/v36/o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6VI.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+2074,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}@font-face{font-family:Roboto;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu72xKOzY.woff2) format("woff2");unicode-range:U+0460-052F,U+1C80-1C88,U+20B4,U+2DE0-2DFF,U+A640-A69F,U+FE2E-FE2F}@font-face{font-family:Roboto;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu5mxKOzY.woff2) format("woff2");unicode-range:U+0301,U+0400-045F,U+0490-0491,U+04B0-04B1,U+2116}@font-face{font-family:Roboto;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu7mxKOzY.woff2) format("woff2");unicode-range:U+1F00-1FFF}@font-face{font-family:Roboto;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4WxKOzY.woff2) format("woff2");unicode-range:U+0370-0377,U+037A-037F,U+0384-038A,U+038C,U+038E-03A1,U+03A3-03FF}@font-face{font-family:Roboto;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu7WxKOzY.woff2) format("woff2");unicode-range:U+0102-0103,U+0110-0111,U+0128-0129,U+0168-0169,U+01A0-01A1,U+01AF-01B0,U+0300-0301,U+0303-0304,U+0308-0309,U+0323,U+0329,U+1EA0-1EF9,U+20AB}@font-face{font-family:Roboto;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu7GxKOzY.woff2) format("woff2");unicode-range:U+0100-02AF,U+0304,U+0308,U+0329,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:Roboto;font-style:normal;font-weight:400;font-display:swap;src:url(https://fonts.gstatic.com/s/roboto/v30/KFOmCnqEu92Fr1Mu4mxK.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+2074,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}.ease-in-out{transition-timing-function:cubic-bezier(.4,0,.2,1)}html{overflow-x:hidden}:root{--vp-c-bg: #3B4252;--vp-c-bg-elv: #434C5E;--vp-font-family-base: Itim;--vp-font-family-mono: Roboto Mono;--vp-layout-max-width: 1080px;--vp-nav-height: 48px}footer{color:var(--vp-c-default-1)}footer a[href^=http]:after{color:var(--vp-c-border)!important}.title{justify-content:center;border:none!important;position:unset!important;padding:0!important;width:unset!important}.title span{font-size:x-large}.search{padding-left:0;display:flex;flex-grow:0!important;padding-left:unset!important}.DocSearch-Button{margin:auto;width:unset;border:none!important}.DocSearch-Button-Placeholder{margin-top:unset!important;padding:unset!important;font-size:unset!important;font-weight:unset!important;color:unset!important;margin-right:8px}.VPNavBarMenu{align-items:flex-end}.VPNavBarMenuLink{line-height:unset!important;font-size:unset!important;font-weight:unset!important;color:unset!important}ul>li>ul{position:relative}ul>li>ul:before{position:absolute;content:"";width:2px;background:var(--vp-c-text-1);opacity:.3;left:-16px;top:8px;bottom:8px}.aside{display:none!important}.img-container{padding:15px;position:relative;height:11lh;width:fit-content;margin:auto}.img-container img{clip-path:polygon(18px 0%,100% 0,100% calc(100% - 18px),calc(100% - 18px) 100%,0 100%,0% 18px);height:100%;object-fit:contain;background:#fff}.img-container:after,.img-container:before{content:"";display:block;position:absolute;border:50px solid transparent;transform:rotate(135deg)}.img-container:after{bottom:-60px;right:-65px;box-shadow:0 7px 6px -9px #000}.img-container:before{top:-60px;left:-65px;box-shadow:0 -7px 6px -9px #000}.VPDoc{padding:0 32px!important}.vp-doc a{color:unset;text-decoration:unset;font-weight:unset;text-underline-offset:unset;margin:0 -.4em;padding:.1em .4em;border-radius:.8em .3em;background:transparent;background-image:linear-gradient(to right,#ffe1000d,#ffe10059 4%,#ffe10026);-webkit-box-decoration-break:clone;box-decoration-break:clone}.vp-doc a:hover{color:unset;background-image:linear-gradient(to right,#ffe1001a,#ffe100b3 4%,#ffe1004d)}.vp-doc a[href^=http]:after{content:"";display:inline-block;margin-top:-1px;margin-left:4px;width:11px;height:11px;background:currentColor;color:var(--vp-c-text-3);flex-shrink:0;--icon: url("data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' %3E%3Cpath d='M0 0h24v24H0V0z' fill='none' /%3E%3Cpath d='M9 5v2h6.59L4 18.59 5.41 20 17 8.41V15h2V5H9z' /%3E%3C/svg%3E");-webkit-mask-image:var(--icon);mask-image:var(--icon)}.VPNav{left:96px!important;right:32px!important;width:unset!important;position:absolute!important;overflow:hidden}.wrapper{padding:0!important}.VPNavBar{background-color:unset!important}.VPNav .container{align-items:flex-end}.VPNav .content{padding:0!important}.VPNav .content-body{height:unset!important;align-items:flex-end!important;column-gap:unset!important}.VPNavBarHamburger{width:unset!important}.title{height:unset!important}a.title,.VPNavBarMenuLink,.VPNavBarSocialLinks a,.DocSearch-Button,.VPNav button{height:36px!important;border-radius:10px 10px 0 0;padding:8px 8px 16px!important;margin-bottom:-8px!important}.VPNav a:hover,.DocSearch-Button:hover,.VPNav button:hover{margin-bottom:unset!important}a.title{background-color:#0ff}.DocSearch-Button{background-color:#ff0!important}.VPNav .VPNavBarMenuLink[href="https://moddingtree.com"]{background-color:#0f0}.VPNav .VPNavBarMenuLink[href="https://incremental.social"]{background:#f0f}.VPNav button{background:red}.VPNav .VPNavBarSocialLinks [href="https://code.incremental.social/thepaperpilot"]{background:#f70}.VPNav .VPNavBarSocialLinks [href="https://matrix.to/#/@thepaperpilot:incremental.social"]{background:#3c9a3c}.VPNav .VPNavBarSocialLinks [href="https://incremental.social/u/thepaperpilot"]{background:#a75aff}.VPNav .divider{display:none!important}.VPSocialLinks{align-items:flex-end!important;margin-right:0!important}.VPSocialLinks:before{display:none}.VPNavBarExtra{display:none!important}.VPNavBarSocialLinks{display:flex!important}.VPNavScreenSocialLinks a,.VPNavScreenMenuLink,.VPNavScreenMenuLink:after{color:var(--vp-c-bg-alt)!important}@media (max-width: 500px){.VPNavBarSocialLinks{display:none!important}}@media (min-width: 501px){.VPNavScreenSocialLinks{display:none!important}}@media (max-width: 400px){.title span{width:60px}.title span:before{content:"Home ."}}.VPContent{padding-top:0!important;margin-top:var(--vp-nav-height)!important;padding-right:calc((100vw - var(--vp-layout-max-width)) / 2)!important;padding-left:calc((100vw - var(--vp-layout-max-width)) / 2)!important}@media (min-width: 960px){.VPNav{right:calc(max(0px,(100vw - var(--vp-layout-max-width)) / 2) + 32px)!important;left:calc(max(-15px,(100vw - var(--vp-layout-max-width)) / 2 + var(--vp-sidebar-width)) + 32px)!important}.VPContent{padding-left:calc((100vw - var(--vp-layout-max-width)) / 2 + var(--vp-sidebar-width))!important}}.vp-doc .header-anchor{margin-left:calc(-1em - 23px)}.vp-doc :not(h1)>.header-anchor{top:24px}.VPSidebar{opacity:1!important;transition:.5s ease-out!important;box-shadow:0 0 10px 1px #0003!important}.VPLocalNav{position:fixed!important;border-bottom:none!important;background-color:unset!important;pointer-events:none}.VPLocalNav .container{align-items:flex-start!important;flex-direction:column!important}.VPLocalNav>.container>*{pointer-events:all}.VPLocalNav .menu{background:#7afcff;box-shadow:0 0 5px 1px #0003;margin-top:10px;height:30px;width:90px;padding:0 0 0 8px!important}.VPLocalNav button:not(.menu){background:#ff7eb9;padding:4px 30px 4px 8px;box-shadow:0 0 5px 1px #0003}.VPLocalNavOutlineDropdown{padding:0!important;margin-top:10px}.VPLocalNavOutlineDropdown button{padding:0!important;width:90px;height:30px}.curtain{display:none}@media (max-width: 840px){.DocSearch-Button-Keys{display:none!important}}@media (max-width: 959px){.VPSidebar{margin-left:-1000px!important;padding:30px 30px 30px 1030px!important;box-sizing:content-box;background:linear-gradient(to bottom,var(--vp-sidebar-bg-color) 29px,var(--vp-c-divider) 1px);background-size:100% 30px;line-height:30px;width:calc(100vw - 128px)}}.aside-curtain{display:none!important}@media (min-width: 960px){.VPSidebar{transform:rotate(1.4deg)!important;top:1em!important;bottom:unset!important;--vp-sidebar-width: 250px !important;background:#feff9c!important;padding:30px!important;width:var(--vp-sidebar-width)!important;margin-left:max(-15px,calc((100% - (var(--vp-layout-max-width) - 60px)) / 2))!important;max-height:40vh;transition-duration:0s!important}.VPLocalNavOutlineDropdown{display:none}.VPDoc .aside{display:block!important;transform:rotate(1.4deg)!important;position:fixed;top:calc(40vh + 2em);left:0;--vp-sidebar-width: 250px !important;background:#feff9c!important;width:var(--vp-sidebar-width)!important;padding:0!important;margin-left:max(-15px,calc((100% - (var(--vp-layout-max-width) - 60px)) / 2))!important;max-height:40vh;overflow-y:auto}.VPDoc .aside-container{position:unset!important;height:unset!important;overflow:unset!important;padding-top:unset!important;width:unset!important}.VPDoc .aside-content{min-height:unset!important;padding:0!important}.VPDoc .aside-content .content{padding:30px!important}.outline-title{font-size:14px;font-weight:700!important;line-height:30px!important}.VPDoc .aside ul>li>ul:before{display:none}}.VPContent .container{background:linear-gradient(to bottom,var(--vp-sidebar-bg-color) 29px,var(--vp-c-divider) 1px);background-size:100% 30px;line-height:30px;box-shadow:0 0 10px 1px #0003!important}.VPContent .content{padding:0 30px!important}.content-container{border-left:double 7px var(--vp-c-divider);padding:30px 0 30px 8px;max-width:unset!important}article{padding-top:30px}.vp-doc .h-feed article{padding-top:0!important}.vp-doc h2+.e-content{margin-top:0!important}.VPDoc h1,.VPDoc h2,.VPDoc h3,.VPDoc h4,.VPDoc h5,.VPDoc h6{margin:0!important;padding:0!important;line-height:30px!important}.VPDoc h1+p{margin-top:0!important}.VPDoc h2,.VPDoc h3,.VPDoc h4,.VPDoc h5,.VPDoc h6{margin-top:-3px!important;padding-top:23px!important;border-top-style:solid!important;border-top-width:10px!important;border-image:url(/button.svg) 10 10 10 10 stretch stretch!important}ul{margin:0!important}li+li{margin:0!important}.VPDoc p{padding:0!important;margin:30px 0!important;line-height:30px!important}blockquote{margin:30px 0!important}blockquote:first-child,blockquote:first-child p{margin-top:0!important}.VPDoc :has(+hr),.VPDoc :has(+h2),.VPDoc :has(+h3),.VPDoc :has(+h4),.VPDoc :has(+h5),.VPDoc :has(+h6),.VPDoc :has(+ul){margin-bottom:0!important}hr{margin-top:-3px!important;margin-bottom:-7px!important;border-top-style:solid!important;border-top-width:10px!important;border-image:url(/button.svg) 10 10 10 10 stretch stretch!important;height:0px!important}.text{line-height:30px!important;padding:0!important;margin:0!important}.group{padding-top:0!important}.group+.group{border-top-style:solid!important;border-top-width:10px!important;border-image:url(/button.svg) 10 10 10 10 stretch stretch!important;padding-top:23px!important;margin-top:-3px!important}table{margin:30px 0!important}#app .vp-doc tr{background-color:var(--vp-c-gray-2)}#app .vp-doc tr:nth-child(2n){background-color:var(--vp-c-bg-soft)}#app .vp-doc th,#app .vp-doc td{font-size:unset!important;font-weight:unset!important;color:unset!important;padding:0 8px!important;line-height:29px}.VPSidebarItem{padding-bottom:0!important}p:last-child{margin-bottom:0!important}.hero{width:60%;margin:auto}footer img{height:1lh;display:inline;border-radius:50%;margin:0 .25em;vertical-align:bottom}@property --anim-bg{syntax: ""; initial-value: transparent; inherits: false;}@keyframes vp-nolebase-highlight-targeted-heading-animation{0%{--anim-bg: transparent}10%,35%{--anim-bg: var(--vp-c-brand-soft)}99%{--anim-bg: transparent}to{--anim-bg: transparent}}.VPNolebaseHighlightTargetedHeadingAnimated{animation:vp-nolebase-highlight-targeted-heading-animation 1.5s ease-in-out;background:linear-gradient(0deg,var(--anim-bg) 55%,transparent 45%) repeat-x}footer[data-v-a3638063]{padding:2em;z-index:26;position:relative;font-size:small;background:var(--vp-c-bg-elv)}.VPLocalSearchBox[data-v-639d7ab9]{position:fixed;z-index:100;top:0;right:0;bottom:0;left:0;display:flex}.backdrop[data-v-639d7ab9]{position:absolute;top:0;right:0;bottom:0;left:0;background:var(--vp-backdrop-bg-color);transition:opacity .5s}.shell[data-v-639d7ab9]{position:relative;padding:12px;margin:64px auto;display:flex;flex-direction:column;gap:16px;background:var(--vp-local-search-bg);width:min(100vw - 60px,900px);height:min-content;max-height:min(100vh - 128px,900px);border-radius:6px}@media (max-width: 767px){.shell[data-v-639d7ab9]{margin:0;width:100vw;height:100vh;max-height:none;border-radius:0}}.search-bar[data-v-639d7ab9]{border:1px solid var(--vp-c-divider);border-radius:4px;display:flex;align-items:center;padding:0 12px;cursor:text}@media (max-width: 767px){.search-bar[data-v-639d7ab9]{padding:0 8px}}.search-bar[data-v-639d7ab9]:focus-within{border-color:var(--vp-c-brand-1)}.local-search-icon[data-v-639d7ab9]{display:block;font-size:18px}.navigate-icon[data-v-639d7ab9]{display:block;font-size:14px}.search-icon[data-v-639d7ab9]{margin:8px}@media (max-width: 767px){.search-icon[data-v-639d7ab9]{display:none}}.search-input[data-v-639d7ab9]{padding:6px 12px;font-size:inherit;width:100%}@media (max-width: 767px){.search-input[data-v-639d7ab9]{padding:6px 4px}}.search-actions[data-v-639d7ab9]{display:flex;gap:4px}@media (any-pointer: coarse){.search-actions[data-v-639d7ab9]{gap:8px}}@media (min-width: 769px){.search-actions.before[data-v-639d7ab9]{display:none}}.search-actions button[data-v-639d7ab9]{padding:8px}.search-actions button[data-v-639d7ab9]:not([disabled]):hover,.toggle-layout-button.detailed-list[data-v-639d7ab9]{color:var(--vp-c-brand-1)}.search-actions button.clear-button[data-v-639d7ab9]:disabled{opacity:.37}.search-keyboard-shortcuts[data-v-639d7ab9]{font-size:.8rem;opacity:75%;display:flex;flex-wrap:wrap;gap:16px;line-height:14px}.search-keyboard-shortcuts span[data-v-639d7ab9]{display:flex;align-items:center;gap:4px}@media (max-width: 767px){.search-keyboard-shortcuts[data-v-639d7ab9]{display:none}}.search-keyboard-shortcuts kbd[data-v-639d7ab9]{background:#8080801a;border-radius:4px;padding:3px 6px;min-width:24px;display:inline-block;text-align:center;vertical-align:middle;border:1px solid rgba(128,128,128,.15);box-shadow:0 2px 2px #0000001a}.results[data-v-639d7ab9]{display:flex;flex-direction:column;gap:6px;overflow-x:hidden;overflow-y:auto;overscroll-behavior:contain}.result[data-v-639d7ab9]{display:flex;align-items:center;gap:8px;border-radius:4px;transition:none;line-height:1rem;border:solid 2px var(--vp-local-search-result-border);outline:none}.result>div[data-v-639d7ab9]{margin:12px;width:100%;overflow:hidden}@media (max-width: 767px){.result>div[data-v-639d7ab9]{margin:8px}}.titles[data-v-639d7ab9]{display:flex;flex-wrap:wrap;gap:4px;position:relative;z-index:1001;padding:2px 0}.title[data-v-639d7ab9]{display:flex;align-items:center;gap:4px}.title.main[data-v-639d7ab9]{font-weight:500}.title-icon[data-v-639d7ab9]{opacity:.5;font-weight:500;color:var(--vp-c-brand-1)}.title svg[data-v-639d7ab9]{opacity:.5}.result.selected[data-v-639d7ab9]{--vp-local-search-result-bg: var(--vp-local-search-result-selected-bg);border-color:var(--vp-local-search-result-selected-border)}.excerpt-wrapper[data-v-639d7ab9]{position:relative}.excerpt[data-v-639d7ab9]{opacity:75%;pointer-events:none;max-height:140px;overflow:hidden;position:relative;opacity:.5;margin-top:4px}.result.selected .excerpt[data-v-639d7ab9]{opacity:1}.excerpt[data-v-639d7ab9] *{font-size:.8rem!important;line-height:130%!important}.titles[data-v-639d7ab9] mark,.excerpt[data-v-639d7ab9] mark{background-color:var(--vp-local-search-highlight-bg);color:var(--vp-local-search-highlight-text);border-radius:2px;padding:0 2px}.excerpt[data-v-639d7ab9] .vp-code-group .tabs{display:none}.excerpt[data-v-639d7ab9] .vp-code-group div[class*=language-]{border-radius:8px!important}.excerpt-gradient-bottom[data-v-639d7ab9]{position:absolute;bottom:-1px;left:0;width:100%;height:8px;background:linear-gradient(transparent,var(--vp-local-search-result-bg));z-index:1000}.excerpt-gradient-top[data-v-639d7ab9]{position:absolute;top:-1px;left:0;width:100%;height:8px;background:linear-gradient(var(--vp-local-search-result-bg),transparent);z-index:1000}.result.selected .titles[data-v-639d7ab9],.result.selected .title-icon[data-v-639d7ab9]{color:var(--vp-c-brand-1)!important}.no-results[data-v-639d7ab9]{font-size:.9rem;text-align:center;padding:12px}svg[data-v-639d7ab9]{flex:none} diff --git a/changelog/atom b/changelog/atom index ddd5ea39..d1ee5a1e 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-18T17:45:20.955Z + 2024-06-18T17:54:16.105Z https://github.com/jpmonette/feed The Paper Pilot @@ -13,6 +13,25 @@ A feed of updates made to my digital garden! All rights reserved 2024, The Paper Pilot + + <![CDATA[ 2 files changed, 8 insertions(+), 4 deletions(-)]]> + https://code.incremental.social/thepaperpilot/pages/commit/b18e47a2eff9b8710f5538734b0863be16425aa5 + + 2024-06-16T00:00:00.000Z + + + + +Page +Changes + + + +the-small-web10 ++++++---- +this-knowledge-hub2 ++ + +]]> + <![CDATA[ 6 files changed, 4 insertions(+), 8 deletions(-)]]> https://code.incremental.social/thepaperpilot/pages/commit/dda6a24ea0446bddebb1da8d636c876340bea20e @@ -169,30 +188,6 @@ fedi-v23 +- the-small-web81 +++++++++++++++++++++++++++--------------------- -]]> - - - <![CDATA[ 7 files changed, 21 insertions(+), 21 deletions(-)]]> - https://code.incremental.social/thepaperpilot/pages/commit/411de1d59fe75b3e56de49dd5209b0b0b9a8616c - - 2024-06-18T00:00:00.000Z - - - - -Page -Changes - - - -guide-to-incrementals/appeal-to-developers6 +++--- -guide-to-incrementals/appeal-to-players6 +++--- -guide-to-incrementals/defining-the-genre6 +++--- -guide-to-incrementals/navigating-criticism6 +++--- -guide-to-incrementals/what-is-content6 +++--- -the-indieweb/amplification6 +++--- -the-indieweb/signature-blocks6 +++--- - ]]> @@ -273,11 +268,11 @@ ]]> - <![CDATA[ 2 files changed, 8 insertions(+), 4 deletions(-)]]> - https://code.incremental.social/thepaperpilot/pages/commit/b18e47a2eff9b8710f5538734b0863be16425aa5 - - 2024-06-16T00:00:00.000Z - + <![CDATA[ 7 files changed, 21 insertions(+), 21 deletions(-)]]> + https://code.incremental.social/thepaperpilot/pages/commit/411de1d59fe75b3e56de49dd5209b0b0b9a8616c + + 2024-06-18T00:00:00.000Z + @@ -286,8 +281,13 @@ -the-small-web10 ++++++---- -this-knowledge-hub2 ++ +guide-to-incrementals/appeal-to-developers6 +++--- +guide-to-incrementals/appeal-to-players6 +++--- +guide-to-incrementals/defining-the-genre6 +++--- +guide-to-incrementals/navigating-criticism6 +++--- +guide-to-incrementals/what-is-content6 +++--- +the-indieweb/amplification6 +++--- +the-indieweb/signature-blocks6 +++--- ]]> diff --git a/changelog/index.html b/changelog/index.html index 9234e438..783cd7df 100644 --- a/changelog/index.html +++ b/changelog/index.html @@ -6,12 +6,12 @@ Site Changelog | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
The Paper Pilot

Site 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!

60 files changed, 513 insertions(+), 93 deletions(-)

Pushed on
PageChanges
activitypub9 +++++++-
advent-incremental9 +++++++-
artificial-intelligence9 +++++++-
atproto9 +++++++-
babble-buds9 +++++++-
capture-the-citadel11 +++++++--
chat-glue9 +++++++-
chronological9 +++++++-
cinny9 +++++++-
command-palettes9 +++++++-
commune9 +++++++-
davey-wreden9 +++++++-
decentralized9 +++++++-
dice-armor27 ++++++++++++++--------
digital-gardens9 +++++++-
federated-identity9 +++++++-
fedi-v29 +++++++-
fediverse9 +++++++-
forgejo9 +++++++-
freeform-vs-chronological-dichotomy9 +++++++-
freeform9 +++++++-
game-dev-tree9 +++++++-
garden-rss9 +++++++-
.../appeal-to-developers13 ++++++++---
guide-to-incrementals/appeal-to-players13 ++++++++---
guide-to-incrementals/defining-the-genre13 ++++++++---
guide-to-incrementals9 +++++++-
.../navigating-criticism13 ++++++++---
guide-to-incrementals/what-is-content13 ++++++++---
incremental-social9 +++++++-
ivy-road9 +++++++-
kronos9 +++++++-
life-is-strange13 ++++++++---
logseq9 +++++++-
matrix9 +++++++-
mbin9 +++++++-
mtx9 +++++++-
my-personal-website9 +++++++-
my-projects9 +++++++-
nostr9 +++++++-
open-source9 +++++++-
opti-speech17 ++++++++++----
planar-pioneers9 +++++++-
pre-order-bonuses9 +++++++-
premium-currency9 +++++++-
profectus9 +++++++-
social-media9 +++++++-
synapse9 +++++++-
the-beginner-s-guide9 +++++++-
the-cozy-web9 +++++++-
the-indieweb/amplification13 ++++++++---
the-indieweb/signature-blocks13 ++++++++---
the-small-web9 +++++++-
this-knowledge-hub9 +++++++-
v-ecs15 ++++++++----
video-game-monetization9 +++++++-
vitepress9 +++++++-
wanderstop9 +++++++-
webrings9 +++++++-
weird9 +++++++-

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 ++
Any and all opinions listed here are 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

Site 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!

60 files changed, 513 insertions(+), 93 deletions(-)

Pushed on
PageChanges
activitypub9 +++++++-
advent-incremental9 +++++++-
artificial-intelligence9 +++++++-
atproto9 +++++++-
babble-buds9 +++++++-
capture-the-citadel11 +++++++--
chat-glue9 +++++++-
chronological9 +++++++-
cinny9 +++++++-
command-palettes9 +++++++-
commune9 +++++++-
davey-wreden9 +++++++-
decentralized9 +++++++-
dice-armor27 ++++++++++++++--------
digital-gardens9 +++++++-
federated-identity9 +++++++-
fedi-v29 +++++++-
fediverse9 +++++++-
forgejo9 +++++++-
freeform-vs-chronological-dichotomy9 +++++++-
freeform9 +++++++-
game-dev-tree9 +++++++-
garden-rss9 +++++++-
.../appeal-to-developers13 ++++++++---
guide-to-incrementals/appeal-to-players13 ++++++++---
guide-to-incrementals/defining-the-genre13 ++++++++---
guide-to-incrementals9 +++++++-
.../navigating-criticism13 ++++++++---
guide-to-incrementals/what-is-content13 ++++++++---
incremental-social9 +++++++-
ivy-road9 +++++++-
kronos9 +++++++-
life-is-strange13 ++++++++---
logseq9 +++++++-
matrix9 +++++++-
mbin9 +++++++-
mtx9 +++++++-
my-personal-website9 +++++++-
my-projects9 +++++++-
nostr9 +++++++-
open-source9 +++++++-
opti-speech17 ++++++++++----
planar-pioneers9 +++++++-
pre-order-bonuses9 +++++++-
premium-currency9 +++++++-
profectus9 +++++++-
social-media9 +++++++-
synapse9 +++++++-
the-beginner-s-guide9 +++++++-
the-cozy-web9 +++++++-
the-indieweb/amplification13 ++++++++---
the-indieweb/signature-blocks13 ++++++++---
the-small-web9 +++++++-
this-knowledge-hub9 +++++++-
v-ecs15 ++++++++----
video-game-monetization9 +++++++-
vitepress9 +++++++-
wanderstop9 +++++++-
webrings9 +++++++-
weird9 +++++++-

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 ++
Any and all opinions listed here are 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 dba026ab..5963d38c 100644 --- a/changelog/json +++ b/changelog/json @@ -9,6 +9,14 @@ "url": "https://www.thepaperpilot.org/" }, "items": [ + { + "id": "https://code.incremental.social/thepaperpilot/pages/commit/b18e47a2eff9b8710f5538734b0863be16425aa5", + "content_html": "\n\n\n\n\n\n\n\n\n\n\n
PageChanges
the-small-web10 ++++++----
this-knowledge-hub2 ++
", + "url": "https://code.incremental.social/thepaperpilot/pages/commit/b18e47a2eff9b8710f5538734b0863be16425aa5", + "title": " 2 files changed, 8 insertions(+), 4 deletions(-)", + "summary": " 2 files changed, 8 insertions(+), 4 deletions(-)", + "date_modified": "2024-06-16T00:00:00.000Z" + }, { "id": "https://code.incremental.social/thepaperpilot/pages/commit/dda6a24ea0446bddebb1da8d636c876340bea20e", "content_html": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
PageChanges
chat-glue2 +-
commune2 +-
fedi-v22 +-
guide-to-incrementals2 --
my-personal-website2 +-
my-projects2 --
", @@ -65,14 +73,6 @@ "summary": " 3 files changed, 48 insertions(+), 38 deletions(-)", "date_modified": "2024-06-06T00:00:00.000Z" }, - { - "id": "https://code.incremental.social/thepaperpilot/pages/commit/411de1d59fe75b3e56de49dd5209b0b0b9a8616c", - "content_html": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
PageChanges
guide-to-incrementals/appeal-to-developers6 +++---
guide-to-incrementals/appeal-to-players6 +++---
guide-to-incrementals/defining-the-genre6 +++---
guide-to-incrementals/navigating-criticism6 +++---
guide-to-incrementals/what-is-content6 +++---
the-indieweb/amplification6 +++---
the-indieweb/signature-blocks6 +++---
", - "url": "https://code.incremental.social/thepaperpilot/pages/commit/411de1d59fe75b3e56de49dd5209b0b0b9a8616c", - "title": " 7 files changed, 21 insertions(+), 21 deletions(-)", - "summary": " 7 files changed, 21 insertions(+), 21 deletions(-)", - "date_modified": "2024-06-18T00:00:00.000Z" - }, { "id": "https://code.incremental.social/thepaperpilot/pages/commit/14a570c17b9fb881c611ae5e1aad8e4200ca8b30", "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\n\n\n\n\n\n\n\n\n\n\n\n\n
PageChanges
activitypub9 +++++++-
advent-incremental9 +++++++-
artificial-intelligence9 +++++++-
atproto9 +++++++-
babble-buds9 +++++++-
capture-the-citadel11 +++++++--
chat-glue9 +++++++-
chronological9 +++++++-
cinny9 +++++++-
command-palettes9 +++++++-
commune9 +++++++-
davey-wreden9 +++++++-
decentralized9 +++++++-
dice-armor27 ++++++++++++++--------
digital-gardens9 +++++++-
federated-identity9 +++++++-
fedi-v29 +++++++-
fediverse9 +++++++-
forgejo9 +++++++-
freeform-vs-chronological-dichotomy9 +++++++-
freeform9 +++++++-
game-dev-tree9 +++++++-
garden-rss9 +++++++-
.../appeal-to-developers13 ++++++++---
guide-to-incrementals/appeal-to-players13 ++++++++---
guide-to-incrementals/defining-the-genre13 ++++++++---
guide-to-incrementals9 +++++++-
.../navigating-criticism13 ++++++++---
guide-to-incrementals/what-is-content13 ++++++++---
incremental-social9 +++++++-
ivy-road9 +++++++-
kronos9 +++++++-
life-is-strange13 ++++++++---
logseq9 +++++++-
matrix9 +++++++-
mbin9 +++++++-
mtx9 +++++++-
my-personal-website9 +++++++-
my-projects9 +++++++-
nostr9 +++++++-
open-source9 +++++++-
opti-speech17 ++++++++++----
planar-pioneers9 +++++++-
pre-order-bonuses9 +++++++-
premium-currency9 +++++++-
profectus9 +++++++-
social-media9 +++++++-
synapse9 +++++++-
the-beginner-s-guide9 +++++++-
the-cozy-web9 +++++++-
the-indieweb/amplification13 ++++++++---
the-indieweb/signature-blocks13 ++++++++---
the-small-web9 +++++++-
this-knowledge-hub9 +++++++-
v-ecs15 ++++++++----
video-game-monetization9 +++++++-
vitepress9 +++++++-
wanderstop9 +++++++-
webrings9 +++++++-
weird9 +++++++-
", @@ -82,12 +82,12 @@ "date_modified": "2024-06-18T00:00:00.000Z" }, { - "id": "https://code.incremental.social/thepaperpilot/pages/commit/b18e47a2eff9b8710f5538734b0863be16425aa5", - "content_html": "\n\n\n\n\n\n\n\n\n\n\n
PageChanges
the-small-web10 ++++++----
this-knowledge-hub2 ++
", - "url": "https://code.incremental.social/thepaperpilot/pages/commit/b18e47a2eff9b8710f5538734b0863be16425aa5", - "title": " 2 files changed, 8 insertions(+), 4 deletions(-)", - "summary": " 2 files changed, 8 insertions(+), 4 deletions(-)", - "date_modified": "2024-06-16T00:00:00.000Z" + "id": "https://code.incremental.social/thepaperpilot/pages/commit/411de1d59fe75b3e56de49dd5209b0b0b9a8616c", + "content_html": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
PageChanges
guide-to-incrementals/appeal-to-developers6 +++---
guide-to-incrementals/appeal-to-players6 +++---
guide-to-incrementals/defining-the-genre6 +++---
guide-to-incrementals/navigating-criticism6 +++---
guide-to-incrementals/what-is-content6 +++---
the-indieweb/amplification6 +++---
the-indieweb/signature-blocks6 +++---
", + "url": "https://code.incremental.social/thepaperpilot/pages/commit/411de1d59fe75b3e56de49dd5209b0b0b9a8616c", + "title": " 7 files changed, 21 insertions(+), 21 deletions(-)", + "summary": " 7 files changed, 21 insertions(+), 21 deletions(-)", + "date_modified": "2024-06-18T00:00:00.000Z" }, { "id": "https://code.incremental.social/thepaperpilot/pages/commit/fe175090d3fc0cfa81754ec5b19a184005e31d8c", diff --git a/changelog/rss b/changelog/rss index 13ad1739..9cf11414 100644 --- a/changelog/rss +++ b/changelog/rss @@ -4,12 +4,31 @@ The Paper Pilot's Digital Garden Changelog https://www.thepaperpilot.org/changelog/ A feed of updates made to my digital garden! - Tue, 18 Jun 2024 17:45:20 GMT + Tue, 18 Jun 2024 17:54:16 GMT https://validator.w3.org/feed/docs/rss2.html https://github.com/jpmonette/feed en All rights reserved 2024, The Paper Pilot + + <![CDATA[ 2 files changed, 8 insertions(+), 4 deletions(-)]]> + https://code.incremental.social/thepaperpilot/pages/commit/b18e47a2eff9b8710f5538734b0863be16425aa5 + https://code.incremental.social/thepaperpilot/pages/commit/b18e47a2eff9b8710f5538734b0863be16425aa5 + Sun, 16 Jun 2024 00:00:00 GMT + + + + +Page +Changes + + + +the-small-web10 ++++++---- +this-knowledge-hub2 ++ + +]]> + <![CDATA[ 6 files changed, 4 insertions(+), 8 deletions(-)]]> https://code.incremental.social/thepaperpilot/pages/commit/dda6a24ea0446bddebb1da8d636c876340bea20e @@ -166,30 +185,6 @@ fedi-v23 +- the-small-web81 +++++++++++++++++++++++++++--------------------- -]]> - - - <![CDATA[ 7 files changed, 21 insertions(+), 21 deletions(-)]]> - https://code.incremental.social/thepaperpilot/pages/commit/411de1d59fe75b3e56de49dd5209b0b0b9a8616c - https://code.incremental.social/thepaperpilot/pages/commit/411de1d59fe75b3e56de49dd5209b0b0b9a8616c - Tue, 18 Jun 2024 00:00:00 GMT - - - - -Page -Changes - - - -guide-to-incrementals/appeal-to-developers6 +++--- -guide-to-incrementals/appeal-to-players6 +++--- -guide-to-incrementals/defining-the-genre6 +++--- -guide-to-incrementals/navigating-criticism6 +++--- -guide-to-incrementals/what-is-content6 +++--- -the-indieweb/amplification6 +++--- -the-indieweb/signature-blocks6 +++--- - ]]> @@ -270,11 +265,11 @@ ]]> - <![CDATA[ 2 files changed, 8 insertions(+), 4 deletions(-)]]> - https://code.incremental.social/thepaperpilot/pages/commit/b18e47a2eff9b8710f5538734b0863be16425aa5 - https://code.incremental.social/thepaperpilot/pages/commit/b18e47a2eff9b8710f5538734b0863be16425aa5 - Sun, 16 Jun 2024 00:00:00 GMT - + <![CDATA[ 7 files changed, 21 insertions(+), 21 deletions(-)]]> + https://code.incremental.social/thepaperpilot/pages/commit/411de1d59fe75b3e56de49dd5209b0b0b9a8616c + https://code.incremental.social/thepaperpilot/pages/commit/411de1d59fe75b3e56de49dd5209b0b0b9a8616c + Tue, 18 Jun 2024 00:00:00 GMT + @@ -283,8 +278,13 @@ -the-small-web10 ++++++---- -this-knowledge-hub2 ++ +guide-to-incrementals/appeal-to-developers6 +++--- +guide-to-incrementals/appeal-to-players6 +++--- +guide-to-incrementals/defining-the-genre6 +++--- +guide-to-incrementals/navigating-criticism6 +++--- +guide-to-incrementals/what-is-content6 +++--- +the-indieweb/amplification6 +++--- +the-indieweb/signature-blocks6 +++--- ]]> diff --git a/garden/activitypub/index.html b/garden/activitypub/index.html index bd6f0006..4224b2d2 100644 --- a/garden/activitypub/index.html +++ b/garden/activitypub/index.html @@ -6,14 +6,14 @@ ActivityPub | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

ActivityPub

8 words, ~0 minute read. Planted +

The Paper Pilot

ActivityPub

8 words, ~0 minute read. Planted . Last tended to -.

Referenced by: Fediverse

Tags: Decentralized

ActivityPub is a protocol for Federated Social Media

Any and all opinions listed here are 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

Any and all opinions listed here are 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 2f96bac3..b225da10 100644 --- a/garden/advent-incremental/index.html +++ b/garden/advent-incremental/index.html @@ -6,14 +6,14 @@ Advent Incremental | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Advent Incremental

104 words, ~1 minute read. Planted +

The Paper Pilot

Advent Incremental

104 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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 67265dee..c44f8d5d 100644 --- a/garden/artificial-intelligence/index.html +++ b/garden/artificial-intelligence/index.html @@ -6,14 +6,14 @@ Artificial Intelligence | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Artificial Intelligence

101 words, ~1 minute read. Planted +

The Paper Pilot

Artificial Intelligence

101 words, ~1 minute read. Planted . Last tended to -.

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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 11189676..730b1117 100644 --- a/garden/atproto/index.html +++ b/garden/atproto/index.html @@ -6,14 +6,14 @@ ATProto | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

ATProto

31 words, ~0 minute read. Planted +

The Paper Pilot

ATProto

31 words, ~0 minute read. Planted . Last tended to -.

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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 d80e9e02..489ec23f 100644 --- a/garden/babble-buds/index.html +++ b/garden/babble-buds/index.html @@ -6,14 +6,14 @@ Babble Buds | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Babble Buds

113 words, ~1 minute read. Planted +

The Paper Pilot

Babble Buds

113 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
Any and all opinions listed here are 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
Any and all opinions listed here are 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 c54a0d74..10c1fe33 100644 --- a/garden/capture-the-citadel/index.html +++ b/garden/capture-the-citadel/index.html @@ -6,14 +6,14 @@ Capture the Citadel | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Capture the Citadel

39 words, ~0 minute read. Planted +

The Paper Pilot

Capture the Citadel

39 words, ~0 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.

Any and all opinions listed here are 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.

Any and all opinions listed here are 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 a96e68d2..134e7178 100644 --- a/garden/chat-glue/index.html +++ b/garden/chat-glue/index.html @@ -6,14 +6,14 @@ Chat Glue | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Chat Glue

23 words, ~0 minute read. Planted +

The Paper Pilot

Chat Glue

23 words, ~0 minute read. Planted . 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.

Any and all opinions listed here are 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, 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.

Any and all opinions listed here are 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 f2c2f38b..2e6d1ccd 100644 --- a/garden/chronological/index.html +++ b/garden/chronological/index.html @@ -6,14 +6,14 @@ Chronological | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Chronological

73 words, ~0 minute read. Planted +

The Paper Pilot

Chronological

73 words, ~0 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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 793d693f..c08ab4f4 100644 --- a/garden/cinny/index.html +++ b/garden/cinny/index.html @@ -6,14 +6,14 @@ Cinny | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Cinny

3 words, ~0 minute read. Planted +

The Paper Pilot

Cinny

3 words, ~0 minute read. Planted . Last tended to -.

Referenced by: Incremental Social

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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 06ef075f..0d7222eb 100644 --- a/garden/command-palettes/index.html +++ b/garden/command-palettes/index.html @@ -6,14 +6,14 @@ Command Palettes | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Command Palettes

117 words, ~1 minute read. Planted +

The Paper Pilot

Command Palettes

117 words, ~1 minute read. Planted . Last tended to -.

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
Any and all opinions listed here are 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
Any and all opinions listed here are 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 a3fbafdc..9f763e30 100644 --- a/garden/commune/index.html +++ b/garden/commune/index.html @@ -6,14 +6,14 @@ Commune | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Commune

144 words, ~1 minute read. Planted +

The Paper Pilot

Commune

144 words, ~1 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
Any and all opinions listed here are 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: 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
Any and all opinions listed here are 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 13520002..2a30b9be 100644 --- a/garden/davey-wreden/index.html +++ b/garden/davey-wreden/index.html @@ -6,14 +6,14 @@ Davey Wreden | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Davey Wreden

37 words, ~0 minute read. Planted +

The Paper Pilot
Any and all opinions listed here are 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:

Any and all opinions listed here are 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 d345ddb9..3dd870fe 100644 --- a/garden/decentralized/index.html +++ b/garden/decentralized/index.html @@ -6,14 +6,14 @@ Decentralized | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Decentralized

80 words, ~0 minute read. Planted +

The Paper Pilot

Decentralized

80 words, ~0 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
Any and all opinions listed here are 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
Any and all opinions listed here are 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 6354f709..bd023daf 100644 --- a/garden/dice-armor/index.html +++ b/garden/dice-armor/index.html @@ -6,14 +6,14 @@ Dice Armor | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Dice Armor

963 words, ~5 minute read. Planted +

The Paper Pilot

Dice Armor

963 words, ~5 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).

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.

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.

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.

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.

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.

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.

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.

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.

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

Any and all opinions listed here are 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).

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.

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.

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.

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.

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.

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.

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.

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.

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

Any and all opinions listed here are 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 e4787a2e..9f478550 100644 --- a/garden/digital-gardens/index.html +++ b/garden/digital-gardens/index.html @@ -6,14 +6,14 @@ Digital Gardens | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Digital Gardens

63 words, ~0 minute read. Planted +

The Paper Pilot

Digital Gardens

63 words, ~0 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:

Any and all opinions listed here are 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:

Any and all opinions listed here are 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 c77f8ba8..570c8ef9 100644 --- a/garden/federated-identity/index.html +++ b/garden/federated-identity/index.html @@ -6,14 +6,14 @@ Federated Identity | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Federated Identity

68 words, ~0 minute read. Planted +

The Paper Pilot

Federated Identity

68 words, ~0 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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 1b073d1e..bdf527d9 100644 --- a/garden/fedi-v2/index.html +++ b/garden/fedi-v2/index.html @@ -6,14 +6,14 @@ Fedi v2 | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Fedi v2

1274 words, ~7 minute read. Planted +

The Paper Pilot

Fedi v2

1274 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
Any and all opinions listed here are 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: 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
Any and all opinions listed here are 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 18660adf..0d551d5f 100644 --- a/garden/fediverse/index.html +++ b/garden/fediverse/index.html @@ -6,14 +6,14 @@ Fediverse | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Fediverse

29 words, ~0 minute read. Planted +

The Paper Pilot

Fediverse

29 words, ~0 minute read. Planted . Last tended to -.

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:

Any and all opinions listed here are 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:

Any and all opinions listed here are 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 15f8e7eb..1cc580c0 100644 --- a/garden/forgejo/index.html +++ b/garden/forgejo/index.html @@ -6,14 +6,14 @@ Forgejo | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Forgejo

5 words, ~0 minute read. Planted +

The Paper Pilot

Forgejo

5 words, ~0 minute read. Planted . Last tended to -.

Referenced by: Incremental Social

Forgejo is an Open Source code repository hosting software

Any and all opinions listed here are 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

Any and all opinions listed here are 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 775a8c5c..c3077f9c 100644 --- a/garden/freeform-vs-chronological-dichotomy/index.html +++ b/garden/freeform-vs-chronological-dichotomy/index.html @@ -6,14 +6,14 @@ Freeform vs Chronological Dichotomy | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Freeform vs Chronological Dichotomy

10 words, ~0 minute read. Planted +

The Paper Pilot

Freeform vs Chronological Dichotomy

10 words, ~0 minute read. Planted . Last tended to -.

Referenced by: Chronological, Freeform

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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 7e87aa1c..35b99c26 100644 --- a/garden/freeform/index.html +++ b/garden/freeform/index.html @@ -6,14 +6,14 @@ Freeform | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Freeform

46 words, ~0 minute read. Planted +

The Paper Pilot

Freeform

46 words, ~0 minute read. Planted . Last tended to -.

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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 6c4f1d97..c786fcdf 100644 --- a/garden/game-dev-tree/index.html +++ b/garden/game-dev-tree/index.html @@ -6,14 +6,14 @@ Game Dev Tree | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Game Dev Tree

34 words, ~0 minute read. Planted +

The Paper Pilot

Game Dev Tree

34 words, ~0 minute read. Planted . Last tended to -.

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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 3eeb7e04..9d127d9f 100644 --- a/garden/garden-rss/index.html +++ b/garden/garden-rss/index.html @@ -6,14 +6,14 @@ Garden-RSS | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Garden-RSS

59 words, ~0 minute read. Planted +

The Paper Pilot

Garden-RSS

59 words, ~0 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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 e1383770..447644bc 100644 --- a/garden/guide-to-incrementals/appeal-to-developers/index.html +++ b/garden/guide-to-incrementals/appeal-to-developers/index.html @@ -6,14 +6,14 @@ Guide to Incrementals/Appeal to Developers | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Guide to Incrementals/Appeal to Developers

636 words, ~3 minute read. Planted +

The Paper Pilot

Guide to Incrementals/Appeal to Developers

636 words, ~3 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.

Any and all opinions listed here are 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.

Any and all opinions listed here are 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 240dffce..ca8116db 100644 --- a/garden/guide-to-incrementals/appeal-to-players/index.html +++ b/garden/guide-to-incrementals/appeal-to-players/index.html @@ -6,14 +6,14 @@ Guide to Incrementals/Appeal to Players | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Guide to Incrementals/Appeal to Players

2400 words, ~13 minute read. Planted +

The Paper Pilot

Guide to Incrementals/Appeal to Players

2400 words, ~13 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.

Any and all opinions listed here are 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.

Any and all opinions listed here are 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 3ad4d9da..f9ef6554 100644 --- a/garden/guide-to-incrementals/defining-the-genre/index.html +++ b/garden/guide-to-incrementals/defining-the-genre/index.html @@ -6,14 +6,14 @@ Guide to Incrementals/Defining the Genre | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Guide to Incrementals/Defining the Genre

3429 words, ~19 minute read. Planted +

The Paper Pilot

Guide to Incrementals/Defining the Genre

3429 words, ~19 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.

Any and all opinions listed here are 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.

Any and all opinions listed here are 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 36241002..0f14725b 100644 --- a/garden/guide-to-incrementals/index.html +++ b/garden/guide-to-incrementals/index.html @@ -6,14 +6,14 @@ Guide to Incrementals | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Guide to Incrementals

251 words, ~1 minute read. Planted +

The Paper Pilot

Guide to Incrementals

251 words, ~1 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 ​

Any and all opinions listed here are 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 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 ​

Any and all opinions listed here are 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 d6ef6eb2..832ca4f9 100644 --- a/garden/guide-to-incrementals/navigating-criticism/index.html +++ b/garden/guide-to-incrementals/navigating-criticism/index.html @@ -6,14 +6,14 @@ Guide to Incrementals/Navigating Criticism | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Guide to Incrementals/Navigating Criticism

747 words, ~4 minute read. Planted +

The Paper Pilot

Guide to Incrementals/Navigating Criticism

747 words, ~4 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.

Any and all opinions listed here are 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.

Any and all opinions listed here are 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 f92bc1b1..805c49b8 100644 --- a/garden/guide-to-incrementals/what-is-content/index.html +++ b/garden/guide-to-incrementals/what-is-content/index.html @@ -6,14 +6,14 @@ Guide to Incrementals/What is Content? | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Guide to Incrementals/What is Content?

2092 words, ~11 minute read. Planted +

The Paper Pilot

Guide to Incrementals/What is Content?

2092 words, ~11 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.

Any and all opinions listed here are 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.

Any and all opinions listed here are 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 6a469ad4..103e8d4c 100644 --- a/garden/incremental-social/index.html +++ b/garden/incremental-social/index.html @@ -6,14 +6,14 @@ Incremental Social | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot
Any and all opinions listed here are 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 ebbf9fdd..3b0d635f 100644 --- a/garden/ivy-road/index.html +++ b/garden/ivy-road/index.html @@ -6,14 +6,14 @@ Ivy Road | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Ivy Road

6 words, ~0 minute read. Planted +

The Paper Pilot

Ivy Road

6 words, ~0 minute read. Planted . Last tended to -.

Referenced by: Davey Wreden, Wanderstop

Tags: Davey Wreden

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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 95605c03..037e13bb 100644 --- a/garden/kronos/index.html +++ b/garden/kronos/index.html @@ -6,14 +6,14 @@ Kronos | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Kronos

60 words, ~0 minute read. Planted +

The Paper Pilot

Kronos

60 words, ~0 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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 049c1a36..b7ebc6a2 100644 --- a/garden/life-is-strange/index.html +++ b/garden/life-is-strange/index.html @@ -6,14 +6,14 @@ Life is Strange | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Life is Strange

654 words, ~4 minute read. Planted +

The Paper Pilot

Life is Strange

654 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
Any and all opinions listed here are 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
Any and all opinions listed here are 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 a3fd0846..ae32837c 100644 --- a/garden/logseq/index.html +++ b/garden/logseq/index.html @@ -6,14 +6,14 @@ Logseq | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Logseq

3 words, ~0 minute read. Planted +

The Paper Pilot

Logseq

3 words, ~0 minute read. Planted . Last tended to -.

Referenced by: Command Palettes, This Knowledge Hub

Logseq is an Open Source outlining software

Any and all opinions listed here are 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

Any and all opinions listed here are 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 dbeeed33..d5f7c4ee 100644 --- a/garden/matrix/index.html +++ b/garden/matrix/index.html @@ -6,14 +6,14 @@ Matrix | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Matrix

2 words, ~0 minute read. Planted +

The Paper Pilot

Matrix

2 words, ~0 minute read. Planted . Last tended to -.

Referenced by: Cinny, Commune, Synapse

Matrix is a protocol for Decentralized messaging

Any and all opinions listed here are 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

Any and all opinions listed here are 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 e56bfc5a..e48877d8 100644 --- a/garden/mbin/index.html +++ b/garden/mbin/index.html @@ -6,14 +6,14 @@ Mbin | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Mbin

12 words, ~0 minute read. Planted +

The Paper Pilot

Mbin

12 words, ~0 minute read. Planted . Last tended to -.

Referenced by: Incremental Social

Mbin is an Open Source Fediverse software

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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 c2470a00..21290ddc 100644 --- a/garden/mtx/index.html +++ b/garden/mtx/index.html @@ -6,14 +6,14 @@ MTX | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

MTX

10 words, ~0 minute read. Planted +

The Paper Pilot

MTX

10 words, ~0 minute read. Planted . Last tended to -.

Referenced by: Premium Currency, Video Game Monetization

Purchaseable items in video games that cost real life currencies

Any and all opinions listed here are 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

Any and all opinions listed here are 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 d58c86dc..932c1fbe 100644 --- a/garden/my-personal-website/index.html +++ b/garden/my-personal-website/index.html @@ -6,14 +6,14 @@ My Personal Website | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

My Personal Website

10 words, ~0 minute read. Planted +

The Paper Pilot

My Personal Website

10 words, ~0 minute read. Planted . Last tended to -.

Referenced by: The Small Web

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

Any and all opinions listed here are 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 Personal Websites for myself, available at https://thepaperpilot.org

Any and all opinions listed here are 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 4341f97d..5c97f738 100644 --- a/garden/my-projects/index.html +++ b/garden/my-projects/index.html @@ -6,14 +6,14 @@ My Projects | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

My Projects

72 words, ~0 minute read. Planted +

The Paper Pilot

My Projects

72 words, ~0 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) ​

Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .
- +.

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) ​

Any and all opinions listed here are 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 9d6bca69..a83dcf13 100644 --- a/garden/nostr/index.html +++ b/garden/nostr/index.html @@ -6,14 +6,14 @@ Nostr | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Nostr

8 words, ~0 minute read. Planted +

The Paper Pilot

Nostr

8 words, ~0 minute read. Planted . Last tended to -.

Referenced by: Fediverse

Tags: Decentralized

Nostr is a protocol for Federated Social Media

Any and all opinions listed here are 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

Any and all opinions listed here are 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 9e746a01..451a7666 100644 --- a/garden/open-source/index.html +++ b/garden/open-source/index.html @@ -6,14 +6,14 @@ Open Source | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Open Source

25 words, ~0 minute read. Planted +

The Paper Pilot

Open Source

25 words, ~0 minute read. Planted . Last tended to -.

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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 32136b1e..42328c60 100644 --- a/garden/opti-speech/index.html +++ b/garden/opti-speech/index.html @@ -6,14 +6,14 @@ Opti-Speech | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Opti-Speech

312 words, ~2 minute read. Planted +

The Paper Pilot

Opti-Speech

312 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).

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.

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

Any and all opinions listed here are 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).

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.

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

Any and all opinions listed here are 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 a94f8482..dd40079e 100644 --- a/garden/planar-pioneers/index.html +++ b/garden/planar-pioneers/index.html @@ -6,14 +6,14 @@ Planar Pioneers | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Planar Pioneers

25 words, ~0 minute read. Planted +

The Paper Pilot

Planar Pioneers

25 words, ~0 minute read. Planted . Last tended to -.

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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 28e6763b..5a0bb3b6 100644 --- a/garden/pre-order-bonuses/index.html +++ b/garden/pre-order-bonuses/index.html @@ -6,14 +6,14 @@ Pre-Order Bonuses | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Pre-Order Bonuses

98 words, ~1 minute read. Planted +

The Paper Pilot

Pre-Order Bonuses

98 words, ~1 minute read. Planted . Last tended to -.

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
Any and all opinions listed here are 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
Any and all opinions listed here are 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 13a8df24..d42b2af3 100644 --- a/garden/premium-currency/index.html +++ b/garden/premium-currency/index.html @@ -6,14 +6,14 @@ Premium Currency | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Premium Currency

71 words, ~0 minute read. Planted +

The Paper Pilot

Premium Currency

71 words, ~0 minute read. Planted . Last tended to -.

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)
Any and all opinions listed here are 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)
Any and all opinions listed here are 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 4a64f059..909dbec5 100644 --- a/garden/profectus/index.html +++ b/garden/profectus/index.html @@ -6,14 +6,14 @@ Profectus | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Profectus

73 words, ~0 minute read. Planted +

The Paper Pilot

Profectus

73 words, ~0 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
Any and all opinions listed here are 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
Any and all opinions listed here are 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 623c2336..8d99e6ce 100644 --- a/garden/social-media/index.html +++ b/garden/social-media/index.html @@ -6,14 +6,14 @@ Social Media | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Social Media

98 words, ~1 minute read. Planted +

The Paper Pilot

Social Media

98 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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 5ebc4baf..bb500d77 100644 --- a/garden/synapse/index.html +++ b/garden/synapse/index.html @@ -6,14 +6,14 @@ Synapse | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Synapse

2 words, ~0 minute read. Planted +

The Paper Pilot

Synapse

2 words, ~0 minute read. Planted . Last tended to -.

Referenced by: Incremental Social

Synapse is an Open Source server software for the Matrix protocol

Any and all opinions listed here are 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

Any and all opinions listed here are 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 b361d8ac..e26966f6 100644 --- a/garden/the-beginner-s-guide/index.html +++ b/garden/the-beginner-s-guide/index.html @@ -6,14 +6,14 @@ The Beginner's Guide | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

The Beginner's Guide

70 words, ~0 minute read. Planted +

The Paper Pilot

The Beginner's Guide

70 words, ~0 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:

Any and all opinions listed here are 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:

Any and all opinions listed here are 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 fd0157e5..6c46292c 100644 --- a/garden/the-cozy-web/index.html +++ b/garden/the-cozy-web/index.html @@ -6,14 +6,14 @@ The Cozy Web | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

The Cozy Web

45 words, ~0 minute read. Planted +

The Paper Pilot

The Cozy Web

45 words, ~0 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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 dee86c57..9447d5ef 100644 --- a/garden/the-indieweb/amplification/index.html +++ b/garden/the-indieweb/amplification/index.html @@ -6,14 +6,14 @@ The IndieWeb/Amplification | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

The IndieWeb/Amplification

57 words, ~0 minute read. Planted +

The Paper Pilot

The IndieWeb/Amplification

57 words, ~0 minute read. Planted . Last tended to -.

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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 4ef64f16..9caba195 100644 --- a/garden/the-indieweb/signature-blocks/index.html +++ b/garden/the-indieweb/signature-blocks/index.html @@ -6,14 +6,14 @@ The IndieWeb/Signature Blocks | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

The IndieWeb/Signature Blocks

14 words, ~0 minute read. Planted +

The Paper Pilot

The IndieWeb/Signature Blocks

14 words, ~0 minute read. Planted . Last tended to -.

A proposal I want to write for posting signed content on your IndieWeb website

Any and all opinions listed here are 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

Any and all opinions listed here are 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 66623420..11b64a58 100644 --- a/garden/the-small-web/index.html +++ b/garden/the-small-web/index.html @@ -6,14 +6,14 @@ The Small Web | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

The Small Web

437 words, ~2 minute read. Planted +

The Paper Pilot

The Small Web

437 words, ~2 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

The web has lost its soul

You should check out the indie web

Any and all opinions listed here are 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: /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

The web has lost its soul

You should check out the indie web

Any and all opinions listed here are 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 9c39f3c4..cb3b79e0 100644 --- a/garden/this-knowledge-hub/index.html +++ b/garden/this-knowledge-hub/index.html @@ -6,14 +6,14 @@ This Knowledge Hub | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

This Knowledge Hub

135 words, ~1 minute read. Planted +

The Paper Pilot

This Knowledge Hub

135 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

I want to utilize the strategies described in Andy's working notes to help improve my digital garden

Suggested pages:

Any and all opinions listed here are 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

I want to utilize the strategies described in Andy's working notes to help improve my digital garden

Suggested pages:

Any and all opinions listed here are 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 07e3e192..f4270a7d 100644 --- a/garden/v-ecs/index.html +++ b/garden/v-ecs/index.html @@ -6,14 +6,14 @@ V-ecs | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

V-ecs

209 words, ~1 minute read. Planted +

The Paper Pilot

V-ecs

209 words, ~1 minute read. Planted . Last tended to -.

Tags: My Projects

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.

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".

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

Any and all opinions listed here are 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

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.

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".

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

Any and all opinions listed here are 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 2af91856..ac3a75b8 100644 --- a/garden/video-game-monetization/index.html +++ b/garden/video-game-monetization/index.html @@ -6,14 +6,14 @@ Video Game Monetization | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Video Game Monetization

123 words, ~1 minute read. Planted +

The Paper Pilot

Video Game Monetization

123 words, ~1 minute read. Planted . Last tended to -.

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
Any and all opinions listed here are 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
Any and all opinions listed here are 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 1204b4c9..3d2c8b64 100644 --- a/garden/vitepress/index.html +++ b/garden/vitepress/index.html @@ -6,14 +6,14 @@ Vitepress | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Vitepress

4 words, ~0 minute read. Planted +

The Paper Pilot

Vitepress

4 words, ~0 minute read. Planted . Last tended to -.

Referenced by: This Knowledge Hub

Vitepress is an Open Source static site generator

Any and all opinions listed here are 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

Any and all opinions listed here are 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 a4a5979d..d7bc54d8 100644 --- a/garden/wanderstop/index.html +++ b/garden/wanderstop/index.html @@ -6,14 +6,14 @@ Wanderstop | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Wanderstop

8 words, ~0 minute read. Planted +

The Paper Pilot

Wanderstop

8 words, ~0 minute read. Planted . Last tended to -.

Tags: Davey Wreden

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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 cc97cbdb..809425d7 100644 --- a/garden/webrings/index.html +++ b/garden/webrings/index.html @@ -6,14 +6,14 @@ Webrings | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Webrings

139 words, ~1 minute read. Planted +

The Paper Pilot

Webrings

139 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?
Any and all opinions listed here are 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?
Any and all opinions listed here are 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 8cf12c40..622df5cd 100644 --- a/garden/weird/index.html +++ b/garden/weird/index.html @@ -6,14 +6,14 @@ Weird | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Weird

114 words, ~1 minute read. Planted +

The Paper Pilot

Weird

114 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

Any and all opinions listed here are 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

Any and all opinions listed here are 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 58fbfe76..6d422262 100644 --- a/guide-to-incrementals/design/criticism/index.html +++ b/guide-to-incrementals/design/criticism/index.html @@ -6,14 +6,14 @@ Guide to Incrementals/Navigating Criticism | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Guide to Incrementals/Navigating Criticism

747 words, ~4 minute read. Planted +

The Paper Pilot

Guide to Incrementals/Navigating Criticism

747 words, ~4 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.

Any and all opinions listed here are 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.

Any and all opinions listed here are 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 2dc584d0..aa45b2ba 100644 --- a/guide-to-incrementals/index.html +++ b/guide-to-incrementals/index.html @@ -6,14 +6,14 @@ Guide to Incrementals | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Guide to Incrementals

251 words, ~1 minute read. Planted +

The Paper Pilot

Guide to Incrementals

251 words, ~1 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 ​

Any and all opinions listed here are 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 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 ​

Any and all opinions listed here are 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 ef1e61b2..0d70d3d8 100644 --- a/guide-to-incrementals/ludology/appeal-developers/index.html +++ b/guide-to-incrementals/ludology/appeal-developers/index.html @@ -6,14 +6,14 @@ Guide to Incrementals/Appeal to Developers | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Guide to Incrementals/Appeal to Developers

636 words, ~3 minute read. Planted +

The Paper Pilot

Guide to Incrementals/Appeal to Developers

636 words, ~3 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.

Any and all opinions listed here are 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.

Any and all opinions listed here are 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 eb75eee2..83c23873 100644 --- a/guide-to-incrementals/ludology/appeal-gamers/index.html +++ b/guide-to-incrementals/ludology/appeal-gamers/index.html @@ -6,14 +6,14 @@ Guide to Incrementals/Appeal to Players | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Guide to Incrementals/Appeal to Players

2400 words, ~13 minute read. Planted +

The Paper Pilot

Guide to Incrementals/Appeal to Players

2400 words, ~13 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.

Any and all opinions listed here are 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.

Any and all opinions listed here are 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 423e43ea..52de1225 100644 --- a/guide-to-incrementals/ludology/content/index.html +++ b/guide-to-incrementals/ludology/content/index.html @@ -6,14 +6,14 @@ Guide to Incrementals/What is Content? | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Guide to Incrementals/What is Content?

2092 words, ~11 minute read. Planted +

The Paper Pilot

Guide to Incrementals/What is Content?

2092 words, ~11 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.

Any and all opinions listed here are 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.

Any and all opinions listed here are 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 171b32a3..3d33f966 100644 --- a/guide-to-incrementals/ludology/definition/index.html +++ b/guide-to-incrementals/ludology/definition/index.html @@ -6,14 +6,14 @@ Guide to Incrementals/Defining the Genre | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

Guide to Incrementals/Defining the Genre

3429 words, ~19 minute read. Planted +

The Paper Pilot

Guide to Incrementals/Defining the Genre

3429 words, ~19 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.

Any and all opinions listed here are 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.

Any and all opinions listed here are 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 b1420ca4..3a5c85fe 100644 --- a/hashmap.json +++ b/hashmap.json @@ -1 +1 @@ -{"garden_federated-identity_index.md":"30v88T8v","guide-to-incrementals_ludology_content_index.md":"BkzTaqAg","garden_game-dev-tree_index.md":"BHrjr9mU","garden_chat-glue_index.md":"CBv9u4YB","garden_atproto_index.md":"C4ax3TK3","garden_guide-to-incrementals_index.md":"ELvcPBGG","about_index.md":"BG_5Z8Zw","index.md":"3muxv5ry","garden_guide-to-incrementals_navigating-criticism_index.md":"Dl7LDZ8M","garden_mbin_index.md":"LX2QNMDg","garden_guide-to-incrementals_appeal-to-players_index.md":"BVOWwfyv","garden_babble-buds_index.md":"C6pXaSnx","garden_the-indieweb_amplification_index.md":"jlLNuI0B","garden_capture-the-citadel_index.md":"152H3gwW","garden_guide-to-incrementals_what-is-content_index.md":"CwKYJWZw","garden_artificial-intelligence_index.md":"D_IxpRAg","garden_logseq_index.md":"B3Y44Cac","garden_kronos_index.md":"BPoR1tPW","garden_incremental-social_index.md":"DbJXv224","garden_command-palettes_index.md":"A3RBTTKb","garden_garden-rss_index.md":"MseAvfYU","garden_freeform-vs-chronological-dichotomy_index.md":"J7Z6S5W3","garden_fedi-v2_index.md":"g4qaD9AG","garden_digital-gardens_index.md":"CA3uP89H","garden_forgejo_index.md":"DAIAC7z7","garden_freeform_index.md":"C7x-jEUs","garden_guide-to-incrementals_appeal-to-developers_index.md":"CAI69wax","garden_life-is-strange_index.md":"BihXPWLv","garden_decentralized_index.md":"DMoi2uh1","garden_pre-order-bonuses_index.md":"CNCIw0CK","garden_webrings_index.md":"YTbtPCL5","garden_synapse_index.md":"B9mv0QMw","garden_v-ecs_index.md":"_CuDqvCK","garden_social-media_index.md":"BklGV2fi","garden_the-indieweb_signature-blocks_index.md":"CDtNXTYD","guide-to-incrementals_index.md":"DJ4GL0o_","garden_this-knowledge-hub_index.md":"Chvg19jP","public_gamedevtree_docs_!general-info.md":"BEe1QWpT","garden_premium-currency_index.md":"CdZaDSOd","garden_my-projects_index.md":"WruDkTLa","garden_fediverse_index.md":"Dw1EGARy","guide-to-incrementals_ludology_definition_index.md":"D4iM7G5n","garden_open-source_index.md":"C491r43H","public_gamedevtree_2.0-format-changes.md":"Ln8OHXLK","garden_video-game-monetization_index.md":"COJLTxgq","guide-to-incrementals_design_criticism_index.md":"B54w0CP9","garden_profectus_index.md":"BC07-N6d","public_gamedevtree_changelog.md":"BEzzFifp","garden_guide-to-incrementals_defining-the-genre_index.md":"DnJeFnvy","garden_activitypub_index.md":"Dv6GWpX1","garden_opti-speech_index.md":"DN4EnHzm","garden_commune_index.md":"PJf709s_","garden_davey-wreden_index.md":"aaY4xWmC","public_gamedevtree_readme.md":"BfpG_Bbp","garden_the-small-web_index.md":"7Rrvcn6K","garden_cinny_index.md":"BWUHPipG","public_lit_readme.md":"D7v9HqFL","public_gamedevtree_docs_getting-started.md":"CKgytkrs","changelog_index.md":"Dn3otd2Y","garden_ivy-road_index.md":"p78T1xXN","garden_the-cozy-web_index.md":"B9Bc79u-","garden_the-beginner-s-guide_index.md":"CoXWcRiO","garden_weird_index.md":"BDMicidw","public_kronos_docs_infoboxes.md":"C8vJg96j","garden_vitepress_index.md":"CMbASq96","public_gamedevtree_docs_updating-tmt.md":"BeVNV-Mx","public_kronos_old things_2.0-format-changes.md":"BtPYjwI8","public_kronos_docs_grids.md":"dVNUAZqL","public_kronos_readme.md":"DYr6QcoT","public_kronos_docs_custom-tab-layouts.md":"jdv_HNa6","public_lit_old things_2.0-format-changes.md":"D2j9ILHH","garden_nostr_index.md":"DeFQ_p4c","garden_wanderstop_index.md":"CPbtJHdi","garden_advent-incremental_index.md":"BMlqKZHu","garden_my-personal-website_index.md":"DyFNC0MU","now_index.md":"-Sctb59C","garden_matrix_index.md":"BEX0nAgV","guide-to-incrementals_ludology_appeal-gamers_index.md":"CESZSCKq","public_gamedevtree_docs_infoboxes.md":"DnPfTXHt","public_gamedevtree_docs_basic-layer-breakdown.md":"B9R3rct9","public_gamedevtree_docs_milestones.md":"D0RVnIvR","public_kronos_docs_getting-started.md":"D_Kei6xe","garden_planar-pioneers_index.md":"CMufsH2U","guide-to-incrementals_ludology_appeal-developers_index.md":"DoI27elo","garden_chronological_index.md":"CL1_BH-C","public_gamedevtree_docs_achievements.md":"Dws6AERf","public_gamedevtree_docs_layer-features.md":"BPBdbh-z","public_kronos_docs_bars.md":"BvYvqoBs","public_gamedevtree_docs_upgrades.md":"D8Eo_Cnp","public_kronos_docs_!general-info.md":"5rkaQMOp","garden_mtx_index.md":"8LNgjod3","public_lit_docs_custom-tab-layouts.md":"CKAQik3E","public_gamedevtree_docs_main-mod-info.md":"bkhR0WSc","public_gamedevtree_docs_subtabs-and-microtabs.md":"CILgz0_s","garden_dice-armor_index.md":"DvezVt4e","public_kronos_docs_achievements.md":"DrCW15Xk","public_kronos_changelog.md":"Dvl4pkUG","public_kronos_docs_buyables.md":"yYFkZBbk","public_kronos_docs_basic-layer-breakdown.md":"DGppoFrI","public_kronos_docs_milestones.md":"EJNENSVA","public_kronos_docs_clickables.md":"D4xqtHCs","public_kronos_docs_layer-features.md":"z0yuKiFe","public_lit_docs_milestones.md":"BuFl4guY","public_lit_docs_subtabs-and-microtabs.md":"C4r4aVZy","public_lit_docs_updating-tmt.md":"5Wwn7JmT","public_lit_docs_trees-and-tree-customization.md":"xH_hxECk","public_lit_docs_getting-started.md":"D0wSP6E1","public_lit_docs_infoboxes.md":"D-I-8bE6","public_gamedevtree_docs_buyables.md":"VV-nsBv-","public_gamedevtree_docs_challenges.md":"DVS5W4rR","public_kronos_docs_main-mod-info.md":"BiS8GkQO","public_lit_changelog.md":"vHJaqGAk","public_lit_docs_!general-info.md":"D9elUAAf","public_lit_docs_bars.md":"DUUCdWTB","public_lit_docs_buyables.md":"B_QAHdTD","public_lit_docs_challenges.md":"CXR-LYbd","public_lit_docs_basic-layer-breakdown.md":"B9dO-Py7","public_gamedevtree_docs_bars.md":"CH1CktIT","public_lit_docs_layer-features.md":"BDedzAxr","public_kronos_docs_subtabs-and-microtabs.md":"xn1GwguC","public_kronos_docs_updating-tmt.md":"D7j5-Gml","public_kronos_docs_trees-and-tree-customization.md":"BVCDgYnD","public_kronos_docs_upgrades.md":"BJh7DmUt","public_lit_docs_upgrades.md":"D5WUVAIu","public_lit_docs_clickables.md":"DOdKRGUh","public_gamedevtree_docs_clickables.md":"Dm3kZIsz","public_gamedevtree_docs_custom-tab-layouts.md":"Cb49LWxc","public_kronos_docs_challenges.md":"DWFXxR37","public_kronos_docs_particles.md":"Bl9JEYco","public_lit_docs_achievements.md":"6W7i-5zk","public_lit_docs_main-mod-info.md":"DINWj5SN"} +{"garden_cinny_index.md":"BHU0bIv4","garden_command-palettes_index.md":"COD9mgbL","garden_commune_index.md":"ClMeApsd","garden_freeform-vs-chronological-dichotomy_index.md":"RXz6V-VC","garden_dice-armor_index.md":"DyblR0tT","garden_freeform_index.md":"C1K0FSr_","garden_decentralized_index.md":"CjAdL8Q4","garden_game-dev-tree_index.md":"jNux2X3x","garden_davey-wreden_index.md":"DagLHB1k","garden_guide-to-incrementals_appeal-to-developers_index.md":"K8NRU4Sg","garden_garden-rss_index.md":"DzOOAEz6","garden_the-indieweb_amplification_index.md":"feCX0iGU","garden_guide-to-incrementals_defining-the-genre_index.md":"BHfFhLBp","garden_mtx_index.md":"CH_HN224","garden_wanderstop_index.md":"B4wnUY7H","garden_webrings_index.md":"BHMjqXQ4","garden_my-projects_index.md":"PcKN-fzF","garden_opti-speech_index.md":"B-Gx7i7-","garden_weird_index.md":"D2B2Yk0i","garden_open-source_index.md":"DuvAPmO4","guide-to-incrementals_design_criticism_index.md":"BcdAQ_MC","garden_planar-pioneers_index.md":"Bxqtb01r","guide-to-incrementals_index.md":"Dfajo0A4","garden_matrix_index.md":"DuLU0VEp","guide-to-incrementals_ludology_appeal-gamers_index.md":"ChZkyZEi","guide-to-incrementals_ludology_appeal-developers_index.md":"BEo9sXWJ","garden_advent-incremental_index.md":"COneCCEO","garden_chat-glue_index.md":"DUkteB-2","garden_babble-buds_index.md":"DKuN95VU","garden_atproto_index.md":"yx1RGhM6","garden_capture-the-citadel_index.md":"CzSxLzbg","garden_artificial-intelligence_index.md":"Bns_28Jh","public_gamedevtree_docs_getting-started.md":"CKgytkrs","garden_guide-to-incrementals_index.md":"dW5Hwzwj","garden_federated-identity_index.md":"Bx0G2BEh","garden_activitypub_index.md":"mGHaIpWs","garden_profectus_index.md":"zl6sD7ik","garden_forgejo_index.md":"DskPgq7f","garden_guide-to-incrementals_navigating-criticism_index.md":"NsATwqk1","garden_synapse_index.md":"CSt75VkQ","garden_incremental-social_index.md":"DaKqcO1b","garden_ivy-road_index.md":"DEYj6m9c","garden_pre-order-bonuses_index.md":"C4h9RmIa","public_gamedevtree_docs_main-mod-info.md":"bkhR0WSc","garden_the-indieweb_signature-blocks_index.md":"Cl2M6pHI","garden_the-cozy-web_index.md":"BucEyy_I","guide-to-incrementals_ludology_content_index.md":"OQ2PhKlg","garden_premium-currency_index.md":"Dx5rwYTw","public_gamedevtree_docs_upgrades.md":"D8Eo_Cnp","about_index.md":"Bj378-Tn","public_kronos_old things_2.0-format-changes.md":"BtPYjwI8","changelog_index.md":"Dn3otd2Y","public_kronos_readme.md":"DYr6QcoT","public_gamedevtree_docs_buyables.md":"VV-nsBv-","public_lit_readme.md":"D7v9HqFL","garden_digital-gardens_index.md":"DlYNcbZT","garden_social-media_index.md":"Bc71elCV","garden_nostr_index.md":"CSTpQOla","index.md":"3muxv5ry","garden_kronos_index.md":"fo69wtFv","garden_the-beginner-s-guide_index.md":"aoBc3wIS","public_gamedevtree_docs_updating-tmt.md":"BeVNV-Mx","garden_chronological_index.md":"BMnS4jcy","public_gamedevtree_docs_infoboxes.md":"DnPfTXHt","garden_guide-to-incrementals_what-is-content_index.md":"DH0-e6tX","public_lit_old things_2.0-format-changes.md":"D2j9ILHH","public_gamedevtree_2.0-format-changes.md":"Ln8OHXLK","garden_this-knowledge-hub_index.md":"BLVYkkb3","public_gamedevtree_docs_!general-info.md":"BEe1QWpT","public_gamedevtree_docs_bars.md":"CH1CktIT","public_gamedevtree_docs_achievements.md":"Dws6AERf","garden_life-is-strange_index.md":"CYMELw9c","public_kronos_docs_achievements.md":"DrCW15Xk","public_gamedevtree_changelog.md":"BEzzFifp","public_gamedevtree_docs_layer-features.md":"BPBdbh-z","public_kronos_docs_!general-info.md":"5rkaQMOp","public_kronos_docs_milestones.md":"EJNENSVA","public_lit_docs_bars.md":"DUUCdWTB","public_kronos_docs_particles.md":"Bl9JEYco","public_lit_docs_basic-layer-breakdown.md":"B9dO-Py7","public_kronos_docs_subtabs-and-microtabs.md":"xn1GwguC","public_lit_docs_buyables.md":"B_QAHdTD","public_kronos_docs_trees-and-tree-customization.md":"BVCDgYnD","public_lit_docs_layer-features.md":"BDedzAxr","public_lit_docs_getting-started.md":"D0wSP6E1","public_lit_docs_challenges.md":"CXR-LYbd","public_lit_docs_clickables.md":"DOdKRGUh","public_lit_docs_custom-tab-layouts.md":"CKAQik3E","public_lit_docs_!general-info.md":"D9elUAAf","public_gamedevtree_docs_basic-layer-breakdown.md":"B9R3rct9","public_lit_changelog.md":"vHJaqGAk","public_lit_docs_trees-and-tree-customization.md":"xH_hxECk","garden_fedi-v2_index.md":"DE3mE6fu","public_lit_docs_infoboxes.md":"D-I-8bE6","public_lit_docs_achievements.md":"6W7i-5zk","public_kronos_docs_bars.md":"BvYvqoBs","public_kronos_docs_clickables.md":"D4xqtHCs","garden_my-personal-website_index.md":"DM_scmXw","public_kronos_docs_updating-tmt.md":"D7j5-Gml","public_gamedevtree_docs_milestones.md":"D0RVnIvR","garden_v-ecs_index.md":"CYqFpmde","public_lit_docs_milestones.md":"BuFl4guY","public_kronos_docs_layer-features.md":"z0yuKiFe","public_lit_docs_upgrades.md":"D5WUVAIu","public_kronos_docs_infoboxes.md":"C8vJg96j","garden_logseq_index.md":"DPP8FcR8","public_kronos_docs_buyables.md":"yYFkZBbk","public_lit_docs_subtabs-and-microtabs.md":"C4r4aVZy","public_kronos_docs_main-mod-info.md":"BiS8GkQO","public_kronos_docs_getting-started.md":"D_Kei6xe","public_kronos_docs_challenges.md":"DWFXxR37","guide-to-incrementals_ludology_definition_index.md":"C2J-KDOq","garden_fediverse_index.md":"p2zOMqpI","garden_vitepress_index.md":"CDF2emtN","garden_guide-to-incrementals_appeal-to-players_index.md":"BtS-sAfk","garden_mbin_index.md":"ZZDbXLwf","public_gamedevtree_docs_clickables.md":"Dm3kZIsz","public_lit_docs_main-mod-info.md":"DINWj5SN","public_gamedevtree_docs_challenges.md":"DVS5W4rR","public_kronos_docs_custom-tab-layouts.md":"jdv_HNa6","public_gamedevtree_docs_custom-tab-layouts.md":"Cb49LWxc","public_kronos_docs_basic-layer-breakdown.md":"DGppoFrI","garden_video-game-monetization_index.md":"Cxek416m","garden_the-small-web_index.md":"D9cvWfOu","public_gamedevtree_docs_subtabs-and-microtabs.md":"CILgz0_s","public_lit_docs_updating-tmt.md":"5Wwn7JmT","now_index.md":"4imACR-M","public_gamedevtree_readme.md":"BfpG_Bbp","public_kronos_docs_upgrades.md":"BJh7DmUt","public_kronos_docs_grids.md":"dVNUAZqL","public_kronos_changelog.md":"Dvl4pkUG"} diff --git a/index.html b/index.html index eb280a8a..71219c9f 100644 --- a/index.html +++ b/index.html @@ -6,12 +6,12 @@ Hello! | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
The Paper Pilot

Hello! ​

I'm Anthony, or The Paper Pilot, and welcome to my digital garden!

This is a public website collecting all my (public) thoughts and projects all in one place. There are a lot of pages here, that link to each other wiki-style. I suggest starting your browsing with one of the recommended pages that most closely align with your interests 😃.

Any and all opinions listed here are 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

Hello! ​

I'm Anthony, or The Paper Pilot, and welcome to my digital garden!

This is a public website collecting all my (public) thoughts and projects all in one place. There are a lot of pages here, that link to each other wiki-style. I suggest starting your browsing with one of the recommended pages that most closely align with your interests 😃.

Any and all opinions listed here are 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 b035272f..2e6fa8f5 100644 --- a/now/index.html +++ b/now/index.html @@ -6,14 +6,14 @@ /now | The Paper Pilot - + - + - - - + + + @@ -25,10 +25,10 @@ -
The Paper Pilot

/now

212 words, ~1 minute read. Planted +

The Paper Pilot

/now

212 words, ~1 minute read. Planted . Last tended to -.

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.

Any and all opinions listed here are 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 "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.

Any and all opinions listed here are 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/2.0-format-changes.html b/public/gamedevtree/2.0-format-changes.html index 15764ca4..4a0b9772 100644 --- a/public/gamedevtree/2.0-format-changes.html +++ b/public/gamedevtree/2.0-format-changes.html @@ -6,12 +6,12 @@ 2.0 format changes | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
The Paper Pilot

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
Any and all opinions listed here are 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

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
Any and all opinions listed here are 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 9df2774a..b7f9930a 100644 --- a/public/gamedevtree/README.html +++ b/public/gamedevtree/README.html @@ -6,12 +6,12 @@ The-Modding-Tree | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
The Paper Pilot

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.

Any and all opinions listed here are 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

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.

Any and all opinions listed here are 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 0eab5223..808d1b22 100644 --- a/public/gamedevtree/changelog.html +++ b/public/gamedevtree/changelog.html @@ -6,12 +6,12 @@ The Game Dev Tree changelog: | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
The Paper Pilot

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
Any and all opinions listed here are 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

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
Any and all opinions listed here are 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 ac547f00..e81e4266 100644 --- a/public/gamedevtree/docs/!general-info.html +++ b/public/gamedevtree/docs/!general-info.html @@ -6,12 +6,12 @@ The-Modding-Tree | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
The Paper Pilot

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.
Any and all opinions listed here are 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

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.
Any and all opinions listed here are 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 b566a276..6382135d 100644 --- a/public/gamedevtree/docs/achievements.html +++ b/public/gamedevtree/docs/achievements.html @@ -6,12 +6,12 @@ Achievements | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
The Paper Pilot

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: {
+    
The Paper Pilot
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: {
@@ -32,8 +32,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.
Any and all opinions listed here are 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.

Any and all opinions listed here are 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 4271fdfe..d0a5ccd4 100644 --- a/public/gamedevtree/docs/bars.html +++ b/public/gamedevtree/docs/bars.html @@ -6,12 +6,12 @@ Bars | The Paper Pilot - + - + - + @@ -24,14 +24,14 @@ -
The Paper Pilot

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: {
+    
The Paper Pilot
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".
Any and all opinions listed here are 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".

Any and all opinions listed here are 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 0057c76d..c9769f73 100644 --- a/public/gamedevtree/docs/basic-layer-breakdown.html +++ b/public/gamedevtree/docs/basic-layer-breakdown.html @@ -6,12 +6,12 @@ Basic layer breakdown | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
The Paper Pilot

Basic layer breakdown ​

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

js
    p: {
+    
The Paper Pilot
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.
@@ -51,8 +51,8 @@
         },
 
         layerShown() {return true},             // Returns a bool for if this layer's node should be visible in the tree.
-    },
Any and all opinions listed here are my own and not representative of my employers; future, past and present.
Resume (not actively seeking new opportunities).
Site built from this commit on .

-    
+    },
Any and all opinions listed here are 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 4dd77832..1f3cffb9 100644 --- a/public/gamedevtree/docs/buyables.html +++ b/public/gamedevtree/docs/buyables.html @@ -6,12 +6,12 @@ Buyables | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
The Paper Pilot

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: {
+    
The Paper Pilot
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.
@@ -37,8 +37,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.
Any and all opinions listed here are 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.

Any and all opinions listed here are 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 60ac49f1..f0203dc5 100644 --- a/public/gamedevtree/docs/challenges.html +++ b/public/gamedevtree/docs/challenges.html @@ -6,12 +6,12 @@ Challenges | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
The Paper Pilot

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: {
+    
The Paper Pilot
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: {
@@ -32,8 +32,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.
Any and all opinions listed here are 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.

Any and all opinions listed here are 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 6060a6c0..b1e9e4dd 100644 --- a/public/gamedevtree/docs/clickables.html +++ b/public/gamedevtree/docs/clickables.html @@ -6,12 +6,12 @@ Clickables | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
The Paper Pilot

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: {
+    
The Paper Pilot
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.
@@ -36,8 +36,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.
Any and all opinions listed here are 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.

Any and all opinions listed here are 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 0b3b9a29..2d9658ab 100644 --- a/public/gamedevtree/docs/custom-tab-layouts.html +++ b/public/gamedevtree/docs/custom-tab-layouts.html @@ -6,12 +6,12 @@ Custom tab layouts | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
The Paper Pilot

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",
+    
The Paper Pilot
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",
@@ -32,8 +32,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.
Any and all opinions listed here are 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.

Any and all opinions listed here are 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 7ddd3d8e..bedfc01d 100644 --- a/public/gamedevtree/docs/getting-started.html +++ b/public/gamedevtree/docs/getting-started.html @@ -6,12 +6,12 @@ Getting started | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
The Paper Pilot

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.

Any and all opinions listed here are 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

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.

Any and all opinions listed here are 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 899b27bc..cd0659cc 100644 --- a/public/gamedevtree/docs/infoboxes.html +++ b/public/gamedevtree/docs/infoboxes.html @@ -6,12 +6,12 @@ Infoboxes | The Paper Pilot - + - + - + @@ -24,14 +24,14 @@ -
The Paper Pilot

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: {
+    
The Paper Pilot
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".
Any and all opinions listed here are 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".

Any and all opinions listed here are 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 d84912d5..f09e09e8 100644 --- a/public/gamedevtree/docs/layer-features.html +++ b/public/gamedevtree/docs/layer-features.html @@ -6,12 +6,12 @@ Layer Features | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
The Paper Pilot

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
+    
    The Paper Pilot
    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.
@@ -39,8 +39,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.
    Any and all opinions listed here are 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.

Any and all opinions listed here are 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 5ea2f51b..d10107cb 100644 --- a/public/gamedevtree/docs/main-mod-info.html +++ b/public/gamedevtree/docs/main-mod-info.html @@ -6,12 +6,12 @@ mod.js | The Paper Pilot - + - + - + @@ -24,12 +24,12 @@ -
The Paper Pilot

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)
+    
The Paper Pilot
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).
Any and all opinions listed here are 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).
Any and all opinions listed here are 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 aa61ee1b..3654ed23 100644 --- a/public/gamedevtree/docs/milestones.html +++ b/public/gamedevtree/docs/milestones.html @@ -6,12 +6,12 @@ Milestones | The Paper Pilot - + - + - + @@ -24,14 +24,14 @@ -
The Paper Pilot

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: {
+    
The Paper Pilot
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.
Any and all opinions listed here are 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.

    • Any and all opinions listed here are 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 f312ac70..115e5307 100644 --- a/public/gamedevtree/docs/subtabs-and-microtabs.html +++ b/public/gamedevtree/docs/subtabs-and-microtabs.html @@ -6,12 +6,12 @@ Subtabs and Microtabs | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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*
         },
@@ -46,8 +46,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.)
    Any and all opinions listed here are 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.)

    Any and all opinions listed here are 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 4e8de538..e06817c9 100644 --- a/public/gamedevtree/docs/updating-tmt.html +++ b/public/gamedevtree/docs/updating-tmt.html @@ -6,12 +6,12 @@ Updating The Modding Tree | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
    The Paper Pilot

    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.

    Any and all opinions listed here are 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

    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.

    Any and all opinions listed here are 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 fafe47ce..7850d1f7 100644 --- a/public/gamedevtree/docs/upgrades.html +++ b/public/gamedevtree/docs/upgrades.html @@ -6,12 +6,12 @@ Upgrades | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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: {
@@ -32,8 +32,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.
    Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 6e7a9fac..a8453e68 100644 --- a/public/kronos/Old Things/2.0-format-changes.html +++ b/public/kronos/Old Things/2.0-format-changes.html @@ -6,12 +6,12 @@ 2.0 format changes | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
    The Paper Pilot

    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
    Any and all opinions listed here are 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

    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
    Any and all opinions listed here are 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 d9ed1003..12517802 100644 --- a/public/kronos/README.html +++ b/public/kronos/README.html @@ -6,12 +6,12 @@ Kronos | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
    The Paper Pilot

    Kronos ​

    Play here.

    Updating the website:

    • git submodule update --remote
    • git add -A
    • git commit -m "Updated kronos"
    • git push
    Any and all opinions listed here are 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

    Kronos ​

    Play here.

    Updating the website:

    • git submodule update --remote
    • git add -A
    • git commit -m "Updated kronos"
    • git push
    Any and all opinions listed here are 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 a312d927..94700861 100644 --- a/public/kronos/changelog.html +++ b/public/kronos/changelog.html @@ -6,12 +6,12 @@ The Modding Tree changelog: | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
    The Paper Pilot

    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.
    Any and all opinions listed here are 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

    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.
    Any and all opinions listed here are 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 b063c64c..92fdf642 100644 --- a/public/kronos/docs/!general-info.html +++ b/public/kronos/docs/!general-info.html @@ -6,12 +6,12 @@ The-Modding-Tree | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
    The Paper Pilot

    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.
    Any and all opinions listed here are 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

    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.
    Any and all opinions listed here are 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 8961102c..d309935a 100644 --- a/public/kronos/docs/achievements.html +++ b/public/kronos/docs/achievements.html @@ -6,12 +6,12 @@ Achievements | The Paper Pilot - + - + - + @@ -24,14 +24,14 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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.
    Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 2eb745ab..8a050aa7 100644 --- a/public/kronos/docs/bars.html +++ b/public/kronos/docs/bars.html @@ -6,12 +6,12 @@ Bars | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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,
@@ -33,8 +33,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".
    Any and all opinions listed here are 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".

    Any and all opinions listed here are 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 2064acb4..4a24e7b2 100644 --- a/public/kronos/docs/basic-layer-breakdown.html +++ b/public/kronos/docs/basic-layer-breakdown.html @@ -6,12 +6,12 @@ Basic layer breakdown | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    Basic layer breakdown ​

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

    js
    addLayer("p", {
+    
    The Paper Pilot
    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.
@@ -55,8 +55,8 @@
     upgrades: {
         // Look in the upgrades docs to see what goes here!
     },
-})
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    
-    
+})
    Any and all opinions listed here are 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 662e5321..477830cb 100644 --- a/public/kronos/docs/buyables.html +++ b/public/kronos/docs/buyables.html @@ -6,12 +6,12 @@ Buyables | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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" },
@@ -36,8 +36,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.
    Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 b2f487a5..588320ce 100644 --- a/public/kronos/docs/challenges.html +++ b/public/kronos/docs/challenges.html @@ -6,12 +6,12 @@ Challenges | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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",
@@ -32,8 +32,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)
    Any and all opinions listed here are 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)

    Any and all opinions listed here are 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 8aafec3d..848f4b44 100644 --- a/public/kronos/docs/clickables.html +++ b/public/kronos/docs/clickables.html @@ -6,12 +6,12 @@ Clickables | The Paper Pilot - + - + - + @@ -24,14 +24,14 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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.
    Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 10feba12..4be02820 100644 --- a/public/kronos/docs/custom-tab-layouts.html +++ b/public/kronos/docs/custom-tab-layouts.html @@ -6,12 +6,12 @@ Custom tab layouts | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: [
+    
    The Paper Pilot
    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",
@@ -37,8 +37,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.
    Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 0d93ce08..667209d7 100644 --- a/public/kronos/docs/getting-started.html +++ b/public/kronos/docs/getting-started.html @@ -6,12 +6,12 @@ Getting started | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
    The Paper Pilot

    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.

    Any and all opinions listed here are 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

    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.

    Any and all opinions listed here are 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 f872a35a..5a527d82 100644 --- a/public/kronos/docs/grids.html +++ b/public/kronos/docs/grids.html @@ -6,12 +6,12 @@ Grids | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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) {
@@ -44,8 +44,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.
    Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 ce25bfbf..24bf3642 100644 --- a/public/kronos/docs/infoboxes.html +++ b/public/kronos/docs/infoboxes.html @@ -6,12 +6,12 @@ Infoboxes | The Paper Pilot - + - + - + @@ -24,15 +24,15 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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".
    Any and all opinions listed here are 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".

    Any and all opinions listed here are 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 3abdf936..f3e636ba 100644 --- a/public/kronos/docs/layer-features.html +++ b/public/kronos/docs/layer-features.html @@ -6,12 +6,12 @@ Layer Features | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: [
+    
      The Paper Pilot
      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
@@ -34,8 +34,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.
      Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 201b7c87..f6b892f1 100644 --- a/public/kronos/docs/main-mod-info.html +++ b/public/kronos/docs/main-mod-info.html @@ -6,12 +6,12 @@ mod.js | The Paper Pilot - + - + - + @@ -24,12 +24,12 @@ -
    The Paper Pilot

    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)
+    
    The Paper Pilot
    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.
    Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 9ff54b06..e968f35a 100644 --- a/public/kronos/docs/milestones.html +++ b/public/kronos/docs/milestones.html @@ -6,12 +6,12 @@ Milestones | The Paper Pilot - + - + - + @@ -24,15 +24,15 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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.
    Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 0a0255f1..8c780473 100644 --- a/public/kronos/docs/particles.html +++ b/public/kronos/docs/particles.html @@ -6,12 +6,12 @@ Particles | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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
    
+    
    The Paper Pilot
    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,
@@ -34,8 +34,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).
    Any and all opinions listed here are 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).
    Any and all opinions listed here are 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 8fc44cdd..6d3bfd42 100644 --- a/public/kronos/docs/subtabs-and-microtabs.html +++ b/public/kronos/docs/subtabs-and-microtabs.html @@ -6,12 +6,12 @@ Subtabs and Microtabs | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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*
@@ -48,8 +48,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.
    Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 10ab4c55..1c284684 100644 --- a/public/kronos/docs/trees-and-tree-customization.html +++ b/public/kronos/docs/trees-and-tree-customization.html @@ -6,12 +6,12 @@ Trees and tree customization | The Paper Pilot - + - + - + @@ -24,10 +24,10 @@ -
    The Paper Pilot

    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"],
+    
    The Paper Pilot
    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.
    Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 59a49e38..638f2571 100644 --- a/public/kronos/docs/updating-tmt.html +++ b/public/kronos/docs/updating-tmt.html @@ -6,12 +6,12 @@ Updating The Modding Tree | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
    The Paper Pilot

    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.

    Any and all opinions listed here are 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

    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.

    Any and all opinions listed here are 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 6b48e104..01332b7c 100644 --- a/public/kronos/docs/upgrades.html +++ b/public/kronos/docs/upgrades.html @@ -6,12 +6,12 @@ Upgrades | The Paper Pilot - + - + - + @@ -24,15 +24,15 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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
    Any and all opinions listed here are 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

    Any and all opinions listed here are 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 7641d165..eb8de84c 100644 --- a/public/lit/Old Things/2.0-format-changes.html +++ b/public/lit/Old Things/2.0-format-changes.html @@ -6,12 +6,12 @@ 2.0 format changes | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
    The Paper Pilot

    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
    Any and all opinions listed here are 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

    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
    Any and all opinions listed here are 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 cffb9d5e..aeb4ef98 100644 --- a/public/lit/README.html +++ b/public/lit/README.html @@ -6,12 +6,12 @@ Kronos | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
    The Paper Pilot

    Kronos ​

    Play here.

    Updating the website:

    • git submodule update --remote
    • git add -A
    • git commit -m "Updated kronos"
    • git push
    Any and all opinions listed here are 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

    Kronos ​

    Play here.

    Updating the website:

    • git submodule update --remote
    • git add -A
    • git commit -m "Updated kronos"
    • git push
    Any and all opinions listed here are 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 8cf8156c..2d93f687 100644 --- a/public/lit/changelog.html +++ b/public/lit/changelog.html @@ -6,12 +6,12 @@ The Modding Tree changelog: | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
    The Paper Pilot

    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.
    Any and all opinions listed here are 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

    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.
    Any and all opinions listed here are 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 f176bad9..60bdb93e 100644 --- a/public/lit/docs/!general-info.html +++ b/public/lit/docs/!general-info.html @@ -6,12 +6,12 @@ The-Modding-Tree | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
    The Paper Pilot

    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!
    Any and all opinions listed here are 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

    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!
    Any and all opinions listed here are 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 32bf2cfe..4465f05a 100644 --- a/public/lit/docs/achievements.html +++ b/public/lit/docs/achievements.html @@ -6,12 +6,12 @@ Achievements | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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: {
@@ -32,8 +32,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.
    Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 202c8e67..83f9e7dc 100644 --- a/public/lit/docs/bars.html +++ b/public/lit/docs/bars.html @@ -6,12 +6,12 @@ Bars | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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,
@@ -33,8 +33,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".
    Any and all opinions listed here are 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".

    Any and all opinions listed here are 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 11728836..f9940236 100644 --- a/public/lit/docs/basic-layer-breakdown.html +++ b/public/lit/docs/basic-layer-breakdown.html @@ -6,12 +6,12 @@ Basic layer breakdown | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    Basic layer breakdown ​

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

    js
    addLayer("p", {
+    
    The Paper Pilot
    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.
@@ -51,8 +51,8 @@
     },
 
     layerShown() { return true }            // Returns a bool for if this layer's node should be visible in the tree.
-})
    Any and all opinions listed here are my own and not representative of my employers; future, past and present.
    Resume (not actively seeking new opportunities).
    Site built from this commit on .
    
-    
+})
    Any and all opinions listed here are 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 987011dd..84eb4e25 100644 --- a/public/lit/docs/buyables.html +++ b/public/lit/docs/buyables.html @@ -6,12 +6,12 @@ Buyables | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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: {
@@ -38,8 +38,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.
    Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 60cf7a1d..418b7ffc 100644 --- a/public/lit/docs/challenges.html +++ b/public/lit/docs/challenges.html @@ -6,12 +6,12 @@ Challenges | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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: {
@@ -34,8 +34,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)
    Any and all opinions listed here are 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)

    Any and all opinions listed here are 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 a2d681d7..055c4598 100644 --- a/public/lit/docs/clickables.html +++ b/public/lit/docs/clickables.html @@ -6,12 +6,12 @@ Clickables | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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: {
@@ -32,8 +32,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.
    Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 56f9daf3..f23d0d83 100644 --- a/public/lit/docs/custom-tab-layouts.html +++ b/public/lit/docs/custom-tab-layouts.html @@ -6,12 +6,12 @@ Custom tab layouts | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: [
+    
    The Paper Pilot
    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",
@@ -37,8 +37,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.
    Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 bda6e950..bf9eef03 100644 --- a/public/lit/docs/getting-started.html +++ b/public/lit/docs/getting-started.html @@ -6,12 +6,12 @@ Getting started | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
    The Paper Pilot

    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.

    Any and all opinions listed here are 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

    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.

    Any and all opinions listed here are 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 336c8004..a47323b6 100644 --- a/public/lit/docs/infoboxes.html +++ b/public/lit/docs/infoboxes.html @@ -6,12 +6,12 @@ Infoboxes | The Paper Pilot - + - + - + @@ -24,15 +24,15 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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".
    Any and all opinions listed here are 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".

    Any and all opinions listed here are 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 0ffe8682..88fcbd67 100644 --- a/public/lit/docs/layer-features.html +++ b/public/lit/docs/layer-features.html @@ -6,12 +6,12 @@ Layer Features | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: [
+    
      The Paper Pilot
      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
@@ -33,8 +33,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.
      Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 840c4a3b..e7138077 100644 --- a/public/lit/docs/main-mod-info.html +++ b/public/lit/docs/main-mod-info.html @@ -6,12 +6,12 @@ mod.js | The Paper Pilot - + - + - + @@ -24,12 +24,12 @@ -
    The Paper Pilot

    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)
+    
    The Paper Pilot
    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).
    Any and all opinions listed here are 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).
    Any and all opinions listed here are 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 0f07f1b2..ae447c15 100644 --- a/public/lit/docs/milestones.html +++ b/public/lit/docs/milestones.html @@ -6,12 +6,12 @@ Milestones | The Paper Pilot - + - + - + @@ -24,15 +24,15 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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.
    Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 3f75967d..2b12468a 100644 --- a/public/lit/docs/subtabs-and-microtabs.html +++ b/public/lit/docs/subtabs-and-microtabs.html @@ -6,12 +6,12 @@ Subtabs and Microtabs | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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*
@@ -48,8 +48,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.
    Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 35d51298..38bdf3b4 100644 --- a/public/lit/docs/trees-and-tree-customization.html +++ b/public/lit/docs/trees-and-tree-customization.html @@ -6,12 +6,12 @@ Trees and tree customization | The Paper Pilot - + - + - + @@ -24,10 +24,10 @@ -
    The Paper Pilot

    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"],
+    
    The Paper Pilot
    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.
    Any and all opinions listed here are 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.

    Any and all opinions listed here are 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 f2d2c88e..2bf47655 100644 --- a/public/lit/docs/updating-tmt.html +++ b/public/lit/docs/updating-tmt.html @@ -6,12 +6,12 @@ Updating The Modding Tree | The Paper Pilot - + - + - + @@ -24,8 +24,8 @@ -
    The Paper Pilot

    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.

    Any and all opinions listed here are 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

    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.

    Any and all opinions listed here are 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 a8fed6b4..71b6e18c 100644 --- a/public/lit/docs/upgrades.html +++ b/public/lit/docs/upgrades.html @@ -6,12 +6,12 @@ Upgrades | The Paper Pilot - + - + - + @@ -24,7 +24,7 @@ -
    The Paper Pilot

    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: {
+    
    The Paper Pilot
    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: {
@@ -33,8 +33,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
    Any and all opinions listed here are 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

    Any and all opinions listed here are 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